Oracle Transportation Management and Global Trade Management Version 6.3.x Installation Notes and Updates
(Doc ID 1506523.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Global Trade Management - Version 6.3.0 to 6.3.7 [Release 6.3] Oracle Transportation Sourcing - Version 6.3.0 to 6.3.7 [Release 6.3] Oracle Customs Management - Version 6.3.0 to 6.3.7 [Release 6.3] Oracle Transportation Cooperative Routing - Version 6.3.0 to 6.3.7 [Release 6.3] Oracle Logistics Inventory Visibility - Version 6.3.0 to 6.3.7 [Release 6.3] Information in this document applies to any platform.
Details
The purpose of the note is to provide a central place for the latest installation updates & notes to be collected for release 6.3 (such as changes to the installation process and/or migration scripts). Any corrections or clarifications are listed here.
Grab the jaxp-ri.jar file from the lib directory and copy to to the <otm_install_dir>/glog/gc3webapp/WEB-INF/lib/3rdparty
Modify the <otm_install_dir>/tomcat/bin/tomcat.conf and add the following line:
Prior to the Oracle Transportation Management 6.3 release there were two installers provided: an "upgrade" installer and a "full"installer. The upgrade installer was used to install the new version of the software on top of an earlier version of the software, whereas the full installer laid down the latest code into a new directory. Either installer allowed for the migration of custom properties from an earlier release.
As of OTM 6.3 there is no longer an upgrade installer provided. Instead, the process of upgrading from a prior version is to lay down new code into a new directory. After downloading the latest 6.3 release, it is necessary to follow the OTM Installation Guide in order to install the software.
The “Upgrading from a Prior Version” section provides details on additional steps necessary when upgrading from a prior version. One important step is to copy any customizations from your previous installation into the new installation. See the “Customizations Migration” section of Installation Guide for specific steps.
After the software has been installed and customizations have been migrated, it is necessary to apply database changes and migrate the database from a previous version. Please refer to the OTM Migration Guide for specific instructions, depending on the version from which you are migrating.
Installation/Upgrade Notes
Anyone that is not using “glogowner” for their “glogowner” users password will encounter error #1549061.1: "ORA-01017: invalid username/password; logon denied:" Error Generated in the import_content Logs.
Anyone that sets the Weblogic “system” user password to anything other than CHANGEME will encounter error #1549075.1: Unable to Start OTM 6.3.x After Initial Installation "weblogic.security.SecurityInitializationException: Authentication for user system denied" Generated in the Weblogic Console Logs.
When migrating from 6.3.0 to 6.3.1 you will see error #1553023.1: Running dbpatch_63.sh Fails on patch10173789 - 6.3 to 6.3.1 migration.
Web Services Security Policy Changes
Starting with Oracle Transportation Management version 6.3, web service calls both into and from the application to external services now use the full built-in capabilities of the WebLogic Server. Versions of Oracle Transportation Management prior to version 6.3 supported only a small subset of the Web Service Security v1.1 specification (WSS) and only as an optional feature i.e. the use of a web service security policy was not enforced.
The default configuration for web service security for inbound web service calls has changed and now enforces a policy which requires the use of the WSS Username Token Profile transported over HTTPS. Therefore, if you are using inbound web services on a version prior to 6.3 and wish to retain their current level of security, you will need to take action. It will be necessary to either modify the service client to conform to this policy or to configure a different default policy. Alternatively, you may choose to fully disable the use of a web service security policy, though for proper security this is not recommended. Please consult the "Web Service Configuration" section of the OTM Security Guide for more details on web service security policy configuration.
6.3.1
OTM 6.3 Installation Result From Object_count.sql Doesn't Match Documentation
There are discrepancies between the 6.3 Installation Guide and the results from using object_count.sql. These results are explained in 1558768.1.
Installation/Upgrade Notes
Anyone that is not using “glogowner” for their “glogowner” users password will encounter error #1549061.1: "ORA-01017: invalid username/password; logon denied:" Error Generated in the import_content Logs.
Anyone that sets the Weblogic “system” user password to anything other than CHANGEME will encounter error #1549075.1: Unable to Start OTM 6.3.x After Initial Installation "weblogic.security.SecurityInitializationException: Authentication for user system denied" Generated in the Weblogic Console Logs.
The following issue was also identified as a problem with new OTM 6.3.1 installations. #17383026: - GC3_VERSION RECORD IS NOT CREATED DURING INITIAL INSTALLATION. This is scheduled to be fixed in 6.3.3. The fix for this issue for version 6.3.1 is discussed in note 1584736.1: GC3_VERSION Table is not Populated After Initial Installation of OTM 6.3.1 or 6.3.2.
6.3.2
Installation/Upgrade Notes
Anyone that sets the Weblogic “system” user password to anything other than CHANGEME will encounter error #1549075.1: Unable to Start OTM 6.3.x After Initial Installation "weblogic.security.SecurityInitializationException: Authentication for user system denied" Generated in the Weblogic Console Logs.
You will need to apply a one-off patch for this issue: ORA-06512: AT "GLOGOWNER.VPD" ERROR GENERATED EDITING OBJECTS IN OTM 6.3.2. This is a known migration issue that will impact all clients. Details on this issue are found in 1584728.1 - "java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist" Error Generated Editing Some Objects in OTM 6.3.2.
The following issue was also identified as a problem with new OTM 6.3.2 installations. #17383026: - GC3_VERSION RECORD IS NOT CREATED DURING INITIAL INSTALLATION. This is scheduled to be fixed in 6.3.3. The fix for this issue for version 6.3.2 is discussed in note 1584736.1: GC3_VERSION Table is not Populated After Initial Installation of OTM 6.3.1 or 6.3.2.
6.3.3
Installation/Upgrade Notes
If you are using the RatewareXL integration prior to 6.3.3, the endpoint URL that you use to access RatewareXL has changed in 6.3.3. You need to complete the following when upgrading to a 6.3.3 (or later) release:
If you are using the 12c JDBC driver and either migrating from or have migrated from 6.3.4, 6.3.5, or 6.3.6 to 6.3.7, please see My Oracle Support Note 2058939.1.
If you are using OTM translations and either migrating to or have migrated to 6.3.7, please install Patch 23711246.
Contacts
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
