In this article:
Checking Foresight Analytics Platform Integrity
Controlling Foresight Analytics Platform and Metadata Integrity
Foresight Analytics Platform and repository metadata integrity is controlled during:
Checking Foresight Analytics Platform Integrity
Foresight Analytics Platform integrity is checked if the Check Sums Every Time Foresight Analytics Platform Runs checkbox was selected during installing BI server of Foresight Analytics Platform in Windows OS.
NOTE. If during web application installation, checksum verification was not enabled, then to activate it, restart the installer and select the Check Sums Every Time Foresight Analytics Platform Runs checkbox.
Checksums for executable files are verified during loading. Every time Foresight Analytics Platform runs, the minimum set of executable files is loaded and while calling any functionality, additional libraries required for work are loaded. If integrity violation is detected, the user receives the corresponding message with description of corrupted files. The following work with Foresight Analytics Platform is locked.
To restore program integrity, the administrator’s involvement is required.
Executable files or their contents can be corrupted due to:
Malicious acts.
User errors.
Viruses.
Other reasons.
NOTE. Checksums are verified only when BI server installed in Windows OS is working. In Linux OS checksums are verified by operating system means.
Checking Repository Metadata Integrity
To check repository metadata integrity, the checksums are performed based on object contents. A checksum changes after object metadata modification. To verify object checksum, it should be performed. After checking the object for the second time, the previously performed checksum saved to a file is compared to the object checksum in the repository. If the checksum has been changed, this means that the object was changed.
Checking repository objects metadata integrity is available in the update manager.
IMPORTANT. Repository metadata integrity check must be executed only within one repository.
Performing Checkums
To perform object checksums in the update manager select the Perform Checksums item in the main menu or the context menu of the update structure or update object.
After executing the operations the checksums are performed for all objects in the update and are saved to the Checksums.crc file in the Downloads local computer folder.
Verifying Checksums
To verify checksums in the update manager:
Select the Verify Checksums item in the main menu or the context menu of the update structure or update object.
Select the file with the *.crc extension containing previously saved object checksums.
After executing the operations the Verifying Checksums dialog box opens with the results of verifying object checksums in the file with object checksums in the repository:
The dialog box displays a table with results of verifying object checksums. Names, identifiers, and verification status are displayed for objects.
Available status of checksums verification:
Identical. Object checksum was not changed.
Not Found. The object is absent in the repository.
CRC Error. Object checksum was changed.