Post Install - Verify Manifest Files (Automated Install Only)

Note

This step only applies if you installed via the automated EagleML installation process.

When the EagleML monthly package gets created, four “manifest” files are added into it. (tpe/dynamic/eagleml)
There is one manifest file per package. By default the following four packages are covered:

eagle_default_libs.manifest
eagle_default_workflows.manifest
eagle_mc_installer.manifest
eagle_ml_2_0.manifest

The manifest files contain the list of all the rule files in the specific package and their checksum values. You can leverage these files if you used the automated install process.
You can validate package integrity at any time after the installation by doing a “run now” on the stream

eagle_ml-2-0_default_validatepackage

When you do this, it will scan the manifest files and compare stored checksums with actual ones found in your environment.
Any discrepancy will be reported in the status tab of the corresponding message as well as in “outgoing” tab.
The list of packages to validate is specified in the .sch rule attached to the validate stream. It is the four packages listed above by default.