Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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:

  1. Install the EagleInstaller
  2. 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 Eagle Installer first (eagle_default_deploy_demand stream).

Install Monthly Release Components

There are various combinations of components for the user to choose. For standard deployment, Installer provides the pick list when deploying from Artifactories as follows:

  • 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

  1. downloading the corresponding archives from artifactory
  2. dropping the archive to the backend staging folder
  3. 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 URL 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 to install MC2:

All older deploys or specific components can follow the process above.

  • No labels