Start for September release of 2018, there are the following recommended standard deployment processes to install EAGLEML and MC2 services either from Eagle Access Artifactory, from Eagle R&D Artifactory, or deploy from folder. These standard deployment processes will ensure the corresponding version is properly updated in Database.
For any deployment, there are 2 steps processes when deploy a monthly release:
- Install the EagleInstaller
- Install the monthly release components such as All services, EagleML, etc.
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.
The deploy components are:
- EAGLEML
- Extractservicerules
- Importserviceerules
- Mc2
- Pyruleserice
- pypy
All services without overlay
Deploy EagleML-without-overlays, extractservicerules, importservicerules, and all mc2 components.
The deploy components are:
- 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
Download Installer from the following URL:
Download mc2.zip from the following urn for all services package:
Drop the files to one of the host of backend staging folder of the region
Drop both zip file 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.
All older deploy or specified component can follow above process.
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
Download Installer from the following URL:
Download mc2.zip from the following urn for all services package:
Drop the files to one of the host of backend staging folder of the region
Drop both zip file 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
All folder deploy for specified component can follow above process.