The following Control Message may be sent to the eagle_ml-2-0_default_cm_control_message stream to execute the install:
<EagleML eaglemlVersion="2-0" eaglemlType eaglemlType="RunTaskRequest"
xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml eagleml-main-2-0.xsd"
xsi:type="RunTaskRequest" xmlns xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0">
<header>
<messageId>B80KJD006C7RUSGE</messageId>
<sentBy>http://www.eagleinvsys.com/</sentBy>
<sendTo>http://www.eagleinvsys.com/eagle_ml-2-0_default_cm_control_message
</sendTo>
<creationTimestamp>2018-02-09T12:40:00</creationTimestamp>
...
<correlationId correlationIdScheme="correlationIdScheme">B80KJD006C7RUSGE
</correlationId>
<businessTaskId correlationIdScheme="businessTaskIdScheme">deploy_EagleInstaller_artifactory
...
<value>eagleinvsys.jfrog.io/eagleinvsys/rd-release-cloud/EagleML-releases/
</value>
...
</taskParameters>
</EagleML>
| Info |
|---|
NOTE: In Eagle Access environments set the Artifactory Location to: |
artifactory-pgh01.eagleinvsys.com:8081/artifactory/rd-release-local/EagleML-releases/
Since the installer updates its own code, the EJM workflow may end with the “Set version” step. This is expected:
...