...
Table of Contents | ||
---|---|---|
|
After you have checked that streams are enabled in the environment, drop the following XML message into eagle_ml-2-0_default_cm_w_setup stream:
Code Block | ||
---|---|---|
| ||
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="ReferenceTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" xsi:type="ReferenceTransactionMessage">
<header>
<messageId>SetupEagleVersion</messageId>
<sentBy>MTADMIN</sentBy>
<creationTimestamp/>
</header>
<referenceTransaction>
<header>
<objectType>SetupEagleVersion</objectType>
</header>
</referenceTransaction>
</EagleML> |
Wait for end of processing and restart MC services.
Info | ||
---|---|---|
| ||
This message can also be found and copied from eagle_ml-2-0_cm/in/xml/w_setup_eagle_version.xml file in the corresponding commented section. |
As a result, Message Center
...
will re-generate binds as the core procedure might have changed. This step can be performed isolated (without version and folder structure updates) by sending to eagle_ml-2-0_default_cm_w_setup stream
...
title | the following message (click to expand): |
---|
Referencing the w_config_version.inc File (for any Installations)
- Open Message Center Editor and proceed to the following file: /eagle_ml-2-0_custom_cm/w_config_version.inc
Check EagleML and MC version numbers listed in this file and DB information - they should match expected values.
Referencing the w_config.
iniinc File (for any Installations)
To determine which EagleML version you have in your environment:
- Open Message Center Editor and proceed to the following file: /eagle_ml-2-0_cm/w_config.inc.
The information about which EagleML version is installed is located in the top line of this file.
For example:Code Block language text <!--EagleML-without-BR-EAGLEML_PRD_20160610overlays-2019.01.11.1-->
In this example, you see BR-EAGLEML_PRD_20160610.1. This indicates that this environment contains the June 2016 month end stays for January 2019 EagleML release.
Info title Important Note In 2016, we changed the naming convention for EagleML releases. The release is now named by the actual month delivered on.
The EagleML/EJM Monthly is targeted for release by the end of day Friday on the first full week of the month. So, for example, the EagleML June 2016 release was delivered on June 10th.
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
In 2015, we had a different naming convention. The release was named for the previous month and the release date for a month end release was typically the first Wednesday after the first Tuesday of the following month. So for example, September 2015 EagleML month end package was released on October 7th 2015:
In this example, you see BR-EAGLEML_PRD_20151007.1. This indicated that this environment contained the September 2015 month end release. Example of a post-2015 release:
It indicates that this environment has June 2016 month end release installed. |
Referencing the Eagle Product Version Table (for Artifactory & Automated Install Methods Only)
...
Info | ||
---|---|---|
| ||
You can create a query in System Management Center with the above SQL so that you can run this from the front end. In v2017 V17 and v2015R2.17 on, the query "System – EagleML Version check" is shipped with core Eagle. |
...