In this page:
| Table of Contents |
|---|
Overview
| Info |
|---|
Please note, that JMS clients should - disable JMS, disable MC (before installation), - install EagleML release as described below, - bring up MC and then bring up JMS. |
For regions without access to artifactory, the standard deploy recommendation is by
...
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 EagleML or EagleML-without-overlays 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
...
Drop the files to one of the backend staging folder folders of the regionDrop
Deploy Using MCC
To do that, drop both zip files into the following stating folder: data/msgcenter/cmw_staging_folder/
Deploy all services from folder using MCCDeploy the Installer from folder first:
...
All older deploys or specific components can follow the process above.
Proceed to Post Install steps
Deploy Using NDFA
To deploy via NDFA
- drop the Installer archive into the backend incoming folder of the NDFA stream tpe\data\msgcenter\in\RAW\eagle_ml-2-0_default_cm_ndfa\incoming\
- drop either EagleML or EagleML-without-overlays archive into the backend incoming folder of the NDFA stream tpe\data\msgcenter\in\RAW\eagle_ml-2-0_default_cm_ndfa\incoming\
| Warning | ||
|---|---|---|
| ||
Do not drop these archives with MCC - Send Data to stream! MCC does not handle them correctly. Please use backend folder |
Proceed to Post Install steps