What is Oracle Transportation Management (OTM)

What is Oracle Transportation Management (OTM)?

OTM stands for Oracle Transportation Management, it is a software/product/solution designed to automate logistics business processes like optimizing shipping costs, sending tender requests to service providers (carriers) and similar other functionalities related to logisitcs business.

Oracle Transportation Management History:

-Oracle Transport Management (OTM) is a product acquired from a company called Global Logistics, Inc (G-LOG)
-OTM was initially called GC3 (Global Command and Control Center)
-G-LOG was founded in May 1999 by Tim Sensing.
-Fedex was the first customer for GC3.
-G-Log was acquired by Oracle Corporation in November 2005.

Modules of Oracle Transportation Management:

-Forwarding and Brokerage Operations.
-Operational Planning.
-Sourcing.
-Freight Payment, Billing and Claims.
-Logistics Inventory Visibility
-Cooperative Routing
-Fleet Management.
-In-Memory Logistics Command Center.
-Fusion Transport Intelligence.

Versions of Oracle Transportation Management:

6.3.4 - June 2014
6.2
6.1 - May 2011
6.0 - April 2009
5.5 - August 2009
5.0 - January 2007

OTM Important Log files

OTM Important Log files

=>OTM web server log file Location

cd $OTM_HOME/logs/tomcat
-rw-r--r--. 1 oracle dba    0 Nov  9 10:55 startup.out
-rw-r--r--. 1 oracle dba  51K Nov  9 10:54 shutdown.log.0
-rw-r--r--. 1 oracle dba 2.3M Nov  9 11:49 console.log.0

=>OTM App server log file location

cd $OTM_HOME/logs/weblogic
-rw-r--r--. 1 oracle dba 865K Nov  9 10:56 weblogic.log
-rw-r--r--. 1 oracle dba 2.2M Nov  9 11:30 console.log.0

How many ways we can do OTM Installation

How many ways we can do OTM Installation?

We can do OTM installation in three ways:

1) GUI
./otmv635_<platform>.bin

2) CONSOLE
./otmv635_<platform>.bin –i console

3) SILENT
./otmv635_<platform>.bin –i silent –f installer.properties

Oracle Transport Management OTM Database Users

Oracle Transport Management OTM Database Users

-Archive
This user owns the DMP tables used for archiving the data. May not be deleted.

-GLOGDBA
This user has access to functions and packages owned by glogowner and reportowner, but does not itself own any tables, views, functions, or packages. It must call the vpd.set_user stored procedure to set user context to view data. May not be deleted.

-GLOGOWNER
This user owns OTM tables, views, functions and packages, can create or alter data structures within the database and can manipulate data. May not be deleted.

-GLOGLOAD
Used for loading data into glogowner and reportowner schemas. May not be deleted.

-DIR_XML_USER
This user should be use for Direct XML integration. This user has the minimum privileges to successfully insert XML transmissions into database objects when using the Direct XML integration feature.

-REPORTOWNER
This user owns the tables, views, functions and packages required for reporting, and can read the data. May not be deleted.

-GLOBALREPORTUSER
This user has read access to all the data in OTM. It is mainly used for reporting. May not be deleted.

-HDOWNER
This user owns FTI tables, views, functions and packages, can create or alter data structures within the database and can manipulate data. May not be deleted.

OTM Important Configuration Files

OTM Important Configuration Files

-File Path/File name
<OTM_HOME>/glog/config/glog.properties
Description
The main configuration/properties file for the OTM, GTM and FTI applications. This is the only properties file that should be changed.

Contains
Various URLs for the application server and third party servers
Various Ports
Database Users
Database User passwords
Application version

-File Path/File name
<OTM_HOME>/weblogic/weblogic.conf
Description
The configuration file used for the application launcher to start WebLogic.

Contains
Environment variables
Product Directory information
Launcher host and port
JVM system properties and arguments
WebLogic arguments
User system password
WebLogic instance name
WebLogic URL

-File Path/File name
<OTM_HOME>/tomcat/tomcat.conf
Description
The configuration file used for the application launcher to start tomcat.

Contains
Environment variables
Product Directory information
Launcher host and port
JVM system properties and arguments
Encoded passwords
Tomcat arguments

-File Path/File name
<OTM_HOME>/tomcat/conf/server.xml
Description
The configuration file for the Tomcat servlet container

Contains
IP Address for the web container and associated ports
Context Path

-File Path/File name
<OTM_HOME>/glog/gc3webapp/WEB-INF/web.xml
Description
A Tomcat configuration file for web applications.

Contains
Session Timeout
Security Role Mapping
Security Filters for Parameter Validation, Cross Site Request Filter, etc.
Servlet mapping

-File Path/File name
<OTM_HOME>/weblogic/domains/otm/config/config.xml (config.xml.fresh)
Description
The configuration file for the Oracle WebLogic Application Server

Contains
Server name
Listening ports
IP Address(es)
User name
Password
Key Store Information
Security Configuration Information

Running OTM Scripts From Oracle SR's

Running OTM Scripts From Oracle SR's

If you want to run scripts provided by Oracle like otm_analyzer.sql, place this script first in $OTM_HOME/glog/oracle/script8.

From SQL Plus login to GLOGOWNER Schema.
At sqlplus prompt run @otm_analyzer.sql

Above script will create output in the same folder.

Note:
The OTM Analyzer is used for Analysis and Performance Monitoring is a self-service health-check script that reviews Product related data, analyzes current configurations and settings for the environment, provides solutions for known issues, feedback and recommendations on best practices.

Analyzers are designed by Support to proactively assist you to better diagnose and maintain your Oracle Application environments. Analyzers may also be used as data collection tools by Support Engineers.

How to configure mapviewer in OTM

How to configure mapviewer in OTM?

1)Shutdown OTM services

2)Take backup of glog.properties

3)Modify below parameters in OTM configuration file.
eg:
glog.mapServer=elocation.oracle.com
glog.map.service_name=elocation_mercator
glog.map.basemap=elocation_mercator.world_map

4)Start OTM services and access maps in OTM.

How to change GLOGOWNER user password

How to change GLOGOWNER user password?

Glogowner default password is glogowner, you can change as per requirement.

The application doesn't login directly as glogowner, it logs in as glogdba and glogload,
so you can change the glogowner password without updating any property files. You'll just need to remember it when patching.
sqlplus "/as sysdba"
SQL> alter user glogowner identified by yourpassword;

Note : Changing glogowner password doesn't require any service to be shutdown.
The same way you can change the password of archive,reportowner and xmlreport user password.

How Do I Alter The Session Time Before User Is Logged Out Of OTM Due To Inactivity?

How Do I Alter The Session Time Before User Is Logged Out Of OTM Due To Inactivity? 

Applies To:
Oracle Transportation Management - Version 5.5 and later

Goal:
How can we alter the user session time out to change how long a user can be inactive before being logged off automatically?

Solution:

The default session timeout for the Oracle Transportation Management web server is 30 minutes. If you leave Oracle Transportation Management idle for 30 minutes, your session will timeout and you will need to log in again. For some Oracle Transportation Management installations, you may want to increase this timeout. Please note that increasing the session timeout will increase the load on your web server and may decrease the number of simultaneous users that can access the system. We don‟t recommend setting this above 60 minutes.

1) Shutdown OTM services.

2) Take backup of web.xml file in below location:

To change this setting, edit the web.xml files on your Oracle Transportation Management web server. These files are located on your web server(s): <otm_install_path>/appserver/applications/GC3App.ear/WLStartup/WEB-INF/web.xml and <otm_install_path>/glog/gc3webapp.ear/GC3.war/WEB-INF/web.xml. Edit the following line in each file:

Below Parameter should be edited in above files:
<session-timeout>30</session-timeout>

3) Change the setting from 30 to your desired timeout period, in minutes. Restart the Oracle Transportation Management instance.

Note: The default session timeout for the OTM Web Server is 30 minutes.
If you leave OTM idle for 30 minutes, your session will timeout and you will need to log in again.

Reference metalink Doc ID 1333246.1