My Oracle Support Banner

Oracle Transportation Management Version 6.0 Installation Notes and Updates (Doc ID 785595.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Transportation Management - Version 6.0 to 6.0.7 [Release 6]
Information in this document applies to any platform.
***Checked for relevance on 11-Aug-2014***

Details

The purpose of the note is to provide a central place for the latest installation updates & notes to be collected for release 6.0 (such as changes to the installation process and/or migration scripts). Any corrections or clarifications are listed here.

Actions

Note: Be sure you have the most recent version of the Administration Guide. There is a revision 3, (full part number E14514-03), dated July 2009. That version includes some changes from the original version not listed below.  The latest document is posted on OTN.


General Instructions on Upgrading OTM From One Release to Another

Note: These instructions do not apply when simply applying a new roll-up. 

Unless otherwise specified in release-specific instructions, please follow these steps when upgrading to a new OTM version:

  1. upgrade & migrate your data to the latest RU of your current version of OTM
  2. install the new OTM version
  3. install the latest RU of the new version
  4. migrate your data from the old version to the new version according to the new version's Administration Guide
  5. run any RU-specific instructions that come out of step #3

This will ensure that you have the most up-to-date copies of the migration scripts in place before running the migration itself. 

Example: 

Currently Version: 5.5.05.03 
Target Version: 6.0.3 

Steps

  1. Install and migrate to 5.5.05.07
  2. Install 6.0
  3. Install 6.0.3
  4. Run 6.0 migration scripts according to latest Administration Guide
  5. Run any 6.0.3-specific instructions

Known Issues

1) Issue: The instructions in the Admin Guide for changing passwords for 
WebLogic's system user are incorrect. Please follow the 
instructions below).

WebLogic creates no new users on its own, relying on the users Oracle Transportation Management creates:

User IDDefault PasswordNotes
system CHANGEME Used to start & stop the application as well as manage the WebLogic console. May not be deleted.
guest CHANGEME May not be deleted.

 
In order to change the ‘system’ user’s password, do the following:

1. Ensure that OTM Application and Web servers are down

2. Setup your environment by running <otm_install_path>/install/gc3env.sh on UNIX or    <otm_install_path>\install\gc3env.cmd on Windows.

3. cd to <otm_install_path>/oracle/script8

4. Run update_password.sh on UNIX or update_password.cmd on Windows with the following parameters: 
   • update_password.sh <glog_properties_path> <user> <password> <old-password> 
       o glog_properties_path: directory where glog.properties is, e.g. <otm_install_path>/glog/config 
       o user: system or guest 
       o password: the new password 
       o old-password: the existing password

5. Run the following command; this will give you the encoded value of the new password 
   • java glog.util.appclass.Base64Encoding <new-password> 
       o new-password: the new password

6. [system] On the application server, edit the file <otm_install_path>/weblogic/weblogic.conf 
   a. search for the string ‘var.WL_PW=CHANGEME’ and change the value of this to the new password 
   b. [system] add or replace the string ‘jvm.arg=-DGC3EncodedPassword=<encoded-password>’, where <encoded-password> is the result of the Java encoding step. 
   c. [guest] add or replace the string ‘jvm.arg=-DGuestEncodedPassword=<encoded-password>’, where <encoded-password> is the result of the Java encoding step.

7. On the Oracle Transportation Management web server(s) edit the file <otm_install_path>/tomcat/bin/tomcat.conf 
   a. [system] search for the string ‘-DGC3EncodedPassword=’ and change the value of this to the result of the Java encoding step. 
   b. [guest] search for the string ‘-DGuestEncodedPassword=’ and change the value of this to the result of the Java encoding step.

8. Restart Oracle Transportation Management

  ==============================================================

2)  Issue: Issue with creating Locations, Order Releases and Service Providers in new installs.
There is a My Oracle Support knowledge document specific to this issue. See 800895.1 for details on this issue as well as the resolution.

Note: This issue has been fixed in the latest version of the OTM 6.0 installer which was uploaded to eDelivery in May 2009. If you downloaded the OTM 6.0 installer before that time we recommend you download the newer version for your 6.0 installation.

 ===============================================================

3) Issue: dbupdate_60.sql script is not able to continue if a SQL command or PL/SQL block generates an error. 

Affects: OTM Database Migration from 5.5 to 6.0. 

Solution: 
Open dbupdate_60.sql file 
Insert below listed line right after "spool dbupdate_60_&dbname._&logdate..log" line 

"WHENEVER SQLERROR CONTINUE;" (without the double quote) 

Error will be recorded in the log file and rest of the commands will get executed. 

Or

Fix the issue which caused the error, rerun migration.

===============================================================

4) Issue: The Administration Guide is missing instructions for running the insert_security_roles.sql script. This script should be run after installing a new OTM 6.0 instance or migrating an exiting OTM 5.5 instance to OTM 6.0.

If the script is not run security related errors will be generated when running actions in the UI. See <Note 867321.1> for additional information.

============================================================== 

5) Issue: The Administration guide does not have complete command to update data content in the section "Migrate Oracle Transportation Management 5.5 CU5 Database to 6.0" on page 7-16. This affects: OTM Database Migration from 5.5 to 6.0 

Solution: Use new command as shown below to update data content during OTM database migration from 5.5. to 6.0. 

UNIX shell script: 

Old command: ./update_content.sh <otm_install_path>/glog/config 
New command: ./update_content.sh <otm_install_path>/glog/config V60 

Windows command line script: 

Old command: update_content.cmd <otm_install_path>\glog\config 
New command: update_content.cmd <otm_install_path>\glog\config V60 


6) Applies to: all 6.0 installs (new and upgrades) 

Linux, Solaris, HPUX & AIX: 

In the file $OTM/weblogic/weblogic.sh, this line: 

rm -f $GLOG_HOME/weblogic/domains/otm/configCache/* 

should be: 

rm -f $GLOG_HOME/weblogic/domains/otm/config/configCache/* 


Windows: 

In the file $OTM\weblogic\weblogic.bat, this line: 

del /q %GLOG_HOME%\weblogic\domains\otm\configCache\*.* 

should be: 

del /q %GLOG_HOME%\weblogic\domains\otm\config\configCache\*.* 

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!


In this Document
Details
Actions
 
General Instructions on Upgrading OTM From One Release to Another
 Known Issues
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.