Starting with September 2018 release, there are the following recommended standard deployment processes to install EagleML and additional services either from Eagle Access Artifactory, from Eagle R&D Artifactory or from folder. These standard deployment processes will ensure the corresponding version is properly updated in Database.
For any deployment, there are 2 steps to install the monthly release:

Install the EagleInstaller
Install EagleML monthly release components

In this page:

Artifactory Accessible Deployment

For regions accessible to artifactory, deploy using the following standard sequence.

Install the Installer

For any new release installation, always deploy the Eagle Installer first (eagle_default_deploy_demand stream).

Install 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 shows examples of deployment 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 Overlays

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:
http://artifactory-pgh01.eagleinvsys.com:8081/artifactory/webapp/#/artifacts/browse/tree/General/rd-release-local-cache/EagleInstaller/2018.09.14.1/EagleInstaller-2018.09.14.1.zip

Download mc2.zip from the following urn for all services package:
http://artifactory-pgh01.eagleinvsys.com:8081/artifactory/webapp/#/artifacts/browse/tree/General/rd-release-local-cache/com/eagleinvsys/mc2/2018.09.14.1/mc2-2018.09.14.1.zip

Drop the files to one of the host of 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.

All older deploy or specified component can follow above process.

Folder Deployment for Artifactory Inaccessible regions