There are multiple ways to obtain the current deployed version of each component:
Using
1049952406Get the version from the
1049952406Execute a query via
1049952406Check the 1049952406 Installed Version Check#w_config after the deployment of each component
...
To use System management Center:
From System Management Center click on the "Diagnostics" → Queries.
Filter by the version column and run.
...
Anchor | ||||
---|---|---|---|---|
|
...
To use the stream in MCC:
From MCC navigate to Message Streams.
Under the Streams Query panel filter the Stream Name by “eagle_mc_server_support ”
Right-click on the stream “eagle_mc_server_support”
Select “Run Now with Tags”
Right-click on the stream “eagle_mc_server_support”
Select "Show Messages" => "Last 50 Messages".
Anchor | ||||
---|---|---|---|---|
|
Retrieve the latest installed version of each component by running the following SQL in any available SQL tools.
To use SQL:
Latest Version SQL
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
select v1.PRODUCT_TYPE, v1.VERSION, SUBSTR(v1.COMMENTS,1,100), -- v1.Comments, v1.UPDATE_DATE from PACE_MASTERDBO.EAGLE_PRODUCT_VERSION v1 where v1.PRODUCT_TYPE in ('kafkaservice', 'EAGLEML-WITHOUT-OVERLAYS', 'EAGLEINSTALLER', 'IMPORTSERVICERULES', 'EXTRACTSERVICERULES', 'pypy', 'pyruleservice', 'EAGLEML', 'MC2') and not exists ( select v2.rowid from PACE_MASTERDBO.EAGLE_PRODUCT_VERSION v2 where v1.PRODUCT_TYPE = v2.PRODUCT_TYPE and v1.update_date < v2.UPDATE_DATE) order by v1.UPDATE_DATE desc |
...
To check the w_config.inc(MCE):
Open the Center Editor and navigate to the following file: /eagle_ml-2-0_custom_cm/w_config_version.inc
Check the EagleML and MC version numbers listed in this file and DB information. The values should match.
Reference the w_config.inc File (for any Installations)
To determine which EagleML version in an environment:
Open the 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:
<!--EagleML-without-overlays-[VERSION].zip-->
...
Old Release Naming Convention
In 2015, there had been 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.
For example, September 2015 EagleML month end package was released on October 7th 2015:
<!--BR-EAGLEML_PRD_20151007.1-->
...
In this example, the value was BR-EAGLEML_PRD_20151007.1.
...
This indicated that this environment contained the September 2015 month end release.
Example of a post-2015 release:
<!--BR-EAGLEML_PRD_20160610.1-->
This indicates that this environment has the June 2016 month end release installed.
Note |
---|
A query may be created in System Management Center with the above SQL. In v17 and in v2015R2.17 on, the query "System – EagleML Version check" is shipped with the core Eagle packages. |