OTM Database
OTM Database
OTM Database
• glog.properties (<otm_install_path>/glog/config)
WebLogic only
• config.xml.fresh (<otm_install_path>/weblogic/domains/otm/config)
• weblogic.sh / weblogic.bat (<otm_install_path>/weblogic)
• weblogic.conf (<otm_install_path>/weblogic)
It is highly recommended that the database for OTM uses character semantics instead
of byte semantics to support multi-byte character encoding scheme.
OTM installations on multi-byte characterset languages such as Chinese and Japanese
must use character semantics.
The NLS_LENGTH_SEMANTICS initialization parameter determines whether a new
character datatype column uses byte for character semantics.
The default value of the parameter is BYTE.
You need to change the column length semantics before you install the otm database
because it is difficult to change the semantics after database has been
populated.
Add the following initial database parameter before starting the Oracle
Transportation Management schema installation:
NLS_LENGTH_SEMANTICS=CHAR
Users in OTM DB
*************************************************
users on the database.
• ARCHIVE
• GLOGDBA
• GLOGOWNER
• GLOGDEV
• GLOGLOAD
• REPORTOWNER
• GLOBALREPORTUSER
glogowner glogowner This user owns OTM tables, views, functions &
packages, can create or alter data structures within the database and can
manipulate data. May not be deleted.
glogdev glogdev This user has complete access to the data. There
is no need to call the vpd package to set user context when logged in as glogdev;
does not own any tables, views, functions or packages. May not be deleted.
reportowner reportowner This user owns the tables, views, functions and
packages required for reporting, and can read the data. May not be deleted.
globalreportuser globalreportuser This user has read access to all the data in
OTM. It is mainly used for XSQL reporting. May not be deleted.
The primary OTM database is OLTP type and also referred to OLTP(database on which
transactions happen).
A secondary database referred as ROD (replicated operational database) is also an
option
FAXmaker is an email-to-fax gateway that allows OTM to send out fax notifications.
Oracle Transportation Management sends an email via SMTP to a specific POP3
mailbox.
FAXmaker checks this mailbox at regular intervals and converts the emails within to
fax transmissions, if all security requirements are satisfied.
-----------------
# RightFax Settings - optional
glog.fax.defaultHandler.routingMode=to
glog.fax.defaultHandler.routingPicture=/name={lastName},{firstName}/fax={rawPhone}/
glog.fax.email=fax@company.com
----------------
pcmiler.host=pcmiler.company.com
pcmiler.port=8145
Uncomment and modify the following lines for PCMiler Rail:
pcmiler.rail.host=pcmilerrail.company.com
pcmiler.rail.port=2001
Once these changes have been made, restart your Oracle Transportation Management
instance
Logging
*******************************************************************************
To modify the Oracle Transportation Management logging options, you need to log
into your OTM instance as the DBA.ADMIN user.
Then Navigate through the following menus: Data Management > Power Data > General >
Log Files. Click Search to show all available log files
UOM
*******************************************************************************
Oracle Transportation Management uses U.S. units of measure when saving data to the
database.
Run the following SQL statement to find out what the current storage default is for
each UOM:
select TYPE,UOM_CODE,UOM_RANK,IS_STORAGE_DEFAULT from UOM where IS_STORAGE_DEFAULT
= ‘Y’
Run the following SQL statement to change the default storage in your system for
any UOM.
(This example changes the default UOM for LENGTH from current FT to M = meters):
3. You will also need to remove the ‘Y’ flag on the current length default of FT.
UPDATE UOM SET IS_STORAGE_DEFAULT = ‘N’ WHERE UOM_CODE = ‘FT’
The above is an example for length but the same SQL can be used to change the
defaults for DISTANCE, SPEED, TEMPERATURE, VOLUME, and WEIGHT.
BPEL Integration
****************************************************************************
BPEL Flows
Oracle Transportation Management provides BPEL integrations with EBS. These flows
can be found in <otm_install_path>/utils/integration/bpel/flows.
Each flow should have a README.TXT file in the zip file with further instructions.
Oracle Transportation Management Properties Files for EBS Integration through BPEL
If integrating with EBS through BPEL Process Manager, you need to include/uncomment
the ebs.properties file in the glog.properties file on the OTM Web and Application
servers.
These files are usually under <otm_install_path>\glog\config on Windows or
<otm_install_path>/glog/config on UNIX.
In the glog.properties file, you would uncomment the following:
#!include ebs.properties
Once this change has been made, restart your OTM instance.
If integrating with the BPEL Process Manager, but not necessarily integration with
EBS, you will need to enable a property in the glog.properties file on the OTM Web
and Application servers.
These files are usually under <otm_install_path>\glog\config on Windows or
<otm_install_path>/glog/config on UNIX.