Results Returned While Collecting OTM Version Information Are Misleading (Doc ID 1280798.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 6.1.0 to 6.2.3 - Release: 6.1 to 6.2
Information in this document applies to any platform.

Symptoms

Within OTM you have the ability to collect some valuable information about an OTM instance.

In order to collect this data you need to log into the instance as DBA.ADMIN and go to Configuration and Administration > Technical Support > Configuration Collection

From this screen you can collect quite a bit of useful information about the OTM instance.

One type of collection you can run is for OTM VERSION information. To run this collection you select it from the list and use the ">" button to move it to the selected side of the screen and press the "Collect" button.

The screen that is displayed is intended to check the 3rdparty library files you have loaded on the Web and App Servers and what additional RU or one off patches are also installed.

When checking the 3rdparty library files two checks are run, one to see if you have the updated libraries needed to help improve UI performance, the ThirdParty-standard-patched.md5 section, and the second that does a more general check on all of the 3rdparty libraries needed, the ThirdParty.md5 section.

Some of the information displayed in both of these sections are misleading since the collection is checking for some of the files in the < OTM Home >/glog/gc3webapp/WEB-INF/lib directory even though they are not suppose to be installed.

If you look at the ThirdParty-standard-patched.md5 section you will see jaxen-full.jar listed. If you have the libraries installed to improve UI performance you should see a "match" in the 3rdParty column, but show "not found" in the Lib column. This is correct since the OTM installation instructions show jaxen-full.jar only needs to be installed < OTM Home >/glog/gc3webapp/WEB-INF/lib/3rdparty directory. The standard.jar file should show "match" on both the 3rdParty and the Lib columns.

The next section,ThirdParty.md5, shows the status of all of the required jars.

If you have the libraries installed to improve UI performance you should see there is a "match" for everything in the 3rdParty column except standard.jar. This is because the ThirdParty.md5 check is looking for the older standard.jar file, not the new one checked in the previous section. The only file that should show a "match" in both the 3rdParty and Lib columns is the jstl.jar file.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms