OTM stands for Oracle Transportation Management.

It's sometimes still referred to

as G-Log, from the company founded in 1999 (Global Logistics). The product was
known as GC3 (Global Command and Control Center). Oracle acquired G-Log in
November of 2005.

Whereas OTM 5.5 ran on OAS (Oracle Application Server), OTM 6.1 utilizes WebLogic
("App Tier"). Both 5.5 and 6.1 have Apache and Tomcat web components ("Web Tier").
The backend is oracle DB. Our first OTM 6.0 lab instance was brought up in April
2009

###################################################################################
#################
OTM Object Lock

OTM uses a concept they call Object Lock which has a corresponding table which the
same name, It uses this to perform locking on various business objects within OTM
(IE Shipment, Order Release, Location, Tracking Events, etc)
Configuration for this is found as follows
Configuration and Admin -> System Admin -> Data Source Manager
Controls the connection string and pool settings for each data source
Object_Lock and Object_Lock_Backup will both appear here
Configuration and Admin -> System Admin -> Data Source Profile Manager
For the OTM "Data Function" ties it to a Data source
Object_Lock and Object_Lock_Backup will both appear here
SNI Configuration Notes:
For SNI we configure the Object Lock and Object Lock Backup data sources to each
have a special database service
This service is tied to a single DB RAC node, with a hot backup node
This was done because the object lock table gets hit with a huge amount of activity
and keeping it on a single node greatly reduced contention

Special Notes:
Object lock backup is only used when the system can no longer get a connection from
Object Lock, and it is only used to release the existing lock. Object Lock Backup
does not participate in acquiring new locks