Start for Starting with the September 2018 release of 2018, there are the following recommended standard deployment processes to install EAGLEML EagleML and MC2 additional services either from Eagle Access Artifactory, from Eagle R&D Artifactory , or deploy from folder. These standard deployment processes will ensure that the corresponding version is properly updated in Databasethe database.For any deployment, there are 2 steps processes when deploy a monthly release:
...
Artifactory Accessible Deployment
For regions accessible to artifactory, deploy using the following standard deploy
Install the Installer
For any new release installation, always deploy the Eagle Installer first.
...
Install the monthly release components
There are various combination of components for users to choose the necessary installation as required. For standard deployment, Installer providers the following standard pick list to simply the installation when deploy from Artifactories:
- EAGLEML
- EagleML-without-overlays
- All services
- All services without overlay
- Others
The following section are example snapshots when deploy from Eagle Access Artifactory:
EAGLEML
Deploy only EAGLEML from artifactory.
...
EagleML-without-overlays
Deploy only EagleML-without-overlays.
...
All services
Deploy EagleML, extractservicerules, importservicerules, and all mc2 components.
...
- EAGLEML
- Extractservicerules
- Importserviceerules
- Mc2
- Pyruleserice
- pypy
All services without overlay
...
- EAGLEML-without-overlays
- Extractservicerules
- Importserviceerules
- Mc2
- Pyruleserice
- pypy
Folder Deployment for Artifactory Inaccessible regions
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
...
Drop the files to one of the host of backend staging folder of the region
...
Deploy all services from folder using MCC
...
Folder Deployment for Artifactory Inaccessible regions
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
...
Drop the files to one of the host of backend staging folder of the region
...
Deploy all services from folder using MCC
...
- If you are about to perform a clean deployment, please refer to First Time (Clean) Deployment.
Skip this step if you have Eagle Installer already installed. - Depending on whether you have Artifactory access or not, choose ether:
Artifactory Accessible Deployment or
Folder Deployment for Artifactory Inaccessible Regions - Complete the Post Install steps to check the installed components.