BINETIX NETWORK

Once BINETIX® PTM™ is successfully deployed on your system via The Installer, you can maintain the installation using the same Installer and starting one of the following handy tools:

1)Add or Remove Features - this tool allows you to change which features are installed. You can remove specific features in accordance with your need and demands. Detailed explanation of the available options is provided under Step 5 of the deployment navigator.

2)Repair/Reinstall - this tool helps you to repair errors in the most recent installation state, such as missing or corrupted files, shortcuts, registry, firewall and IIS entries (see the Introduction section of Solution's Deployment topic).

3)Remove/Uninstall - this tool should be used when you want to remove BINETIX® PTM™ product from your system.

Important Notes:

•In order to use some of the above tools you MUST execute the same installer package you have been using to deploy the application.

•Additionally, during the normal operation, BINETIX® PTMâ„¢ continuously monitors variety of system, user and security activities, and consequently generates daily Log-files. These Log-files could be used for troubleshooting and maintanance.

Please use the navigation arrows on the screen-shots frame below in order to forward and backward the repair process.

Please follow these simple steps:

1)Click on the "Repair/Reinstall" option to initiate the repair process;

2)Click on the "Repair" button to confirm your choice and to commence installation repairing, or click on the "Back" button to select other maintenance tool;

3)Click on the "Finish" button to exist the BINETIX® PTM™ Installer.

Please note: During the repair process the Installer WILL NOT:

•Change any Windows features already enabled on your system.

•Re-enable IIS 10 web-sites which are disabled/deactivated previously by the Installer (see the deployment introduction for more information).

•Start or stop Windows Firewall Service

•Turn ON/OFF Windows Firewall

•Enable File & Printer sharing

•Enable UPnP service

•Enable Remote Desktop

Please use the navigation arrows on the screen-shots frame below in order to forward and backward the removal (uninstallation) process.

Please follow these simple steps:

1)Click on the "Remove" option to initiate the removal process;

2)Click on the "Repair" button to confirm your choice and to commence repairing the installation, or click on the "Back" button to select other maintenance tool;

3)Click on the "Finish" button to exist the BINETIX® PTM™ Installer.

Please note: The Installer will try to remove all installed BINETIX® PTM™ components. However, this process will not affect any additional files or another system changes occurred during the product usage. Consequently, it is possible some directories, locked files or so, to remain untouched by the Installer after the removal process.

Furthermore, during the removal process the Installer WILL NOT:

•Change any Windows features already enabled on your system.

•Re-enable IIS 10 web-sites which are disabled/deactivated previously by the Installer (see the deployment introduction for more information).

•Start or stop Windows Firewall Service

•Turn ON/OFF Windows Firewall

•Enable File & Printer sharing

•Enable UPnP service

•Enable Remote Desktop

This section describes the directory structure and the Log-files location and format.

BINETIX® PTM™ generates multiple Log-files on daily basis. For better visibility and maintenance, these Log-files are grouped for by the system modules in separate directories for each month.

The standard location of the Log-files are typically setup for each module as follows:

➢System's Core: C:\Program Files\BINETIX\PTM\20xx\PTMWS\App_Data\Logs

➢Web Application: C:\Program Files\BINETIX\PTM\20xx\WebApp\App_Data\Logs

➢Maintenance: C:\Program Files\BINETIX\PTM\20xx\PTMMaintenance\App_Data\Logs

Within the Logs directory you will find number of sub-directories organized by operational months in format YYYY-MM.

Each monthly directory contains variety of daily Log-files saved in format <type>_YYMMDD.txt.

C:\Program Files\BINETIX\PTM\20xx\PTMWS\App_Data\Logs\2020-04\PTMWS_200403.txt

where <type> is an optional element of the Log's file name, intended for internal usage and better product maintenance.

Consider the following notes and tips:

a)Usually on production environment the Log-files can be accessed only by qualified people with appropriate security credentials. In case of necessity, please be advised by your security manager and/or system administrator;

b)In case of identified application issues during particular calendar day, please provide only these Log-files related to this particular day.

For example, issued related to the System's Core occurred on April 3rd, 2020 are saved in files like these:

oPTMWS_200403.txt

oPTMSecurity_200403.txt

oPTMPersistence_200406.txt

oPTMLib_200403.txt

oor so...

c)How to recognize where an issue most likely occurs?

Well, there is no rule here due to the significant functional complexity of BINETIX® PTM™ financial platform. However, our advice could be stipulated like this:

1)Firstly, focus your attention on the System's Core module, where the likelihood of functional issues is higher.

2)Report the issues as soon as possible within the day(s) when these issues are identified.

3)Collect and archive (in ZIP or 7z) only the daily Log-files within C:\Program Files\BINETIX\PTM\20xx\PTMWS\App_Data\Logs