About EagleML Overlay Files

There are several overlay files that are packaged as part of the EagleML monthly release. These overlay files contain information that is necessary for EagleML functionality.
The overlay files included are as follows:

• estar\tpe\dynamic\custdat\eagle\star\account\pan-addentity-v7.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\account\pan-addentity-v7_new.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\account\pan-chgentity.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\admin\pan-adduser.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\admin\pan-chguser.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\pan-addsecmasterswircontr1-new-edit.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\reference\pan-addfactorca.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\reference\pan-addsecmastermultilegswap.custom.xml

• estar\tpe\dynamic\custdat\eagle\star\reference\pan-ccodeval.custom.xml

If you use any of these files for additional overlay changes and are installing EagleML using the manual installation steps, you need to manually reapply your versions of the file(s) after the install. If you are installing EagleML using the Artifactory or automated install process, there is logic to help address this issue. Currently, the Artifactory or automated install process treats the EagleML overlays as custom overlays provided you don't already have the file as a custom overlay.

If you are already using this as a custom overlay, the install process compares the files and if there is a difference in the files, it preserves your custom overlay and renames the EagleML overlay to a new extension. In addition, a warning is raised to alert you of the difference and enable you to review and merge content if necessary.

About Overlay Warnings

Warnings will be displayed in the status results of the main installer stream eagle_mc-server_installer.    

Here is an example of what you would see in the status results:

Overlays are considered a warning only, not an error.