For regions without access to artifactory, the standard deploy recommendation is by
- downloading the corresponding archives from artifactory
- dropping the archive to the backend staging folder
- deploy from MCC deploy on demand
For folder deployment, is it always necessary to deploy the EagleInstaller from the same monthly release first.
Following are examples of folder deployment from Eagle Access Artifactory to deploy Installer and All Services for September, 2018 release.
Download Installer and corresponding components
PGH artifcatory:
Eagle Installer URL:
http://artifactory-pgh01.eagleinvsys.com:8081/artifactory/webapp/#/artifacts/browse/tree/General/rd-release-local-cache/EagleInstaller/[RELEASE]/EagleInstaller-[RELEASE].zip
EagleML release without overlays:
http://artifactory-pgh01.eagleinvsys.com:8081/artifactory/webapp/#/artifacts/browse/tree/General/rd-release-local-cache/EagleML-without-overlays/[RELEASE]/EagleML-without-overlays-[RELEASE].zip
Drop the files to one of the backend staging folder of the region
Drop both zip files into the following stating folder: data/msgcenter/cmw_staging_folder/
Deploy all services from folder using MCC
Deploy the Installer from folder first:
After completion, deploy mc2.zip to install MC2:
All older deploys or specific components can follow the process above.