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 10 Next »

There are multiple ways to obtain the current deployed version of each component:

Use System Management Center

You can use the System Management Center SQL to obtain the current deployed version of each component.

To use System management Center:

  1. From System Management Center click on the "Diagnostics" → Queries.

  2. Filter by the version column and run.



Use Stream in MCC

A quick way to validate the installation is to run the eagle_mc_server_support stream. In the Message Center Console, select the eagle_mc_server_support stream, right click and select "Run With Overrides" or "Run Now With Tags", and then select the values shown below:

To use the stream in MCC:

  1. From MCC navigate to Message Streams.

  2. Under the Streams Query panel filter the Stream Name by “eagle_mc_server_support ”

  3. Right-click on the stream “eagle_mc_server_support”

  4. Select “Run Now with Tags”


  5. Right-click on the stream “eagle_mc_server_support”

  6. Select "Show Messages" => "Last 50 Messages".


Use SQL

Retrieve the latest installed version of each component by running the following SQL in any available SQL tools.

To use SQL:

Latest Version SQL
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


Check the w_config.inc (MCE)

Referencing the w_config_version.inc File (for any Installations)

To check the w_config.inc(MCE): 

  1. Open the  Center Editor and navigate to the following file: /eagle_ml-2-0_custom_cm/w_config_version.inc
  2. 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:

  1. Open the Message Center Editor and proceed to the following file: /eagle_ml-2-0_cm/w_config.inc.
  2. The information about which EagleML version is installed is located in the top line of  this file.
    For example: 

  3. <!--EagleML-without-overlays-[VERSION].zip--> 

     In 2016, the naming convention for EagleML releases was changed. The release is 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 March 2019 release was delivered on March 8th.


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.

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.



  • No labels