Property Files

Properties in Oracle Transportation Management can be controlled through files, property sets or the property screen tool. In addition to Oracle Transportation Management properties, there are also GTM properties, HERE properties, ALK properties, and Oracle Maps Cloud Service (formerly known as elocation) Properties.

Property Files

One method of maintaining properties is through the use of property files. Oracle Transportation Management contains a number of files with settings that control OTM's behavior. When using property files, make all your changes in the glog.properties file.

There are many properties within the glog.properties file. To make it easier to organize them, they are generally grouped like this: glog.group.subgroup.property. The documentation follows the same grouping as in the glog.properties file.

An encrypted value can be used in the properties file for sensitive information such as passwords.

Note: Properties are case sensitive with capitalizations showing earlier in the list, but they are alphabetized here.

Property Sets

For users without access to property files, a subset of properties can be maintained through the use of property sets. Property sets are controlled through the UI, and the property settings are stored in the system database. This method of managing properties is suited for cloud architecture.

Note that "reserved" properties may not be modified via property sets. These properties could impact the system's ability to restart and are reserved for IT users with access to property files. If you try to add or modify a reserved property from within a property set you will receive an error. Certain users may have access to some reserved properties.

Note: In general, you should not set a property to null or no value. Instead, remove the property from the property set.

Property Screen

From the Technical Support menu (Configuration and Administration > Technical Support > Diagnostics and Tools > Configuration), a DBA user may access UI or business component properties via the property screen. This screen allows property values to be quickly viewed. Properties that are neither reserved nor read-only can be modified via this screen. Note that these properties are not persisted; they will be lost on the next restart of the system. Changes to properties via the Property Screen should be viewed as a “what if” feature. Any permanent changes need to be made to a property set or property file.

GLOG properties

• glog.action
• glog.advancedlayout
• glog.agent
• glog.agentAction
• glog.appointment
• glog.as
• glog.askOTM
• glog.asset
• glog.audit
• glog.authentication
• glog.bipreports
• glog.BNInvPartyForOrderBase
• glog.bnRules
• glog.BNShipmentContext
• glog.bulkplan
• glog.business
• glog.cache
• glog.connection
• glog.coroute
• glog.crossMachineLock
• glog.csv
• glog.currency
• glog.customPath
• glog.database
• glog.dataquery
• glog.dataqueue
• glog.datasource
• glog.dbupdate
• glog.diag
• glog.diagnostics
• glog.distance
• glog.dns
• glog.dock
• glog.document
• glog.droplistcache
• glog.event
• glog.eventQueueMonitor
• glog.eventReason
• glog.explanation
• glog.ExternalDistance.Engine
• glog.fax
• glog.filetracking
• glog.finder
• glog.firewall
• glog.freight_forwarding
• glog.fti
• glog.fusion
• glog.gatehouse
• glog.httppost
• glog.icap
• glog.instrumentation
• glog.integration
• glog.invoice
• glog.ivr
• glog.jdbc
• glog.job
• glog.lifetimeEventNotify
• glog.local
• glog.log
• glog.login
• glog.lrt
• glog.machinelearning
• glog.mail
• glog.map
• glog.mbean
• glog.mediator
• glog.mergerule
• glog.message
• glog.metric
• glog.migrationProject
• glog.mip
• glog.mobile
• glog.monitorprofile
• glog.notify
• glog.ntier
• glog.obiee
• glog.objectLock
• glog.objectLockDatabase
• glog.oci
• glog.odi
• glog.optimization
• glog.order
• glog.order_base
• glog.order_movement
• glog.order_release
• glog.otm
• glog.pcmiler
• glog.perfevent
• glog.pk
• glog.preferences
• glog.print
• glog.process
• glog.processcontrol
• glog.procurement
• glog.properties
• glog.purge
• glog.query
• glog.quote
• glog.RateFactor
• glog.RateGeoCostUnitBreaks.display.max
• glog.rateware
• glog.RatingEngine
• glog.releasemethod
• glog.report
• glog.reqdoc
• glog.riq
• glog.roeqRule
• glog.savedquery
• glog.scalability
• glog.scenariobulkplan
• glog.security
• glog.sell
• glog.sellshipment
• glog.server
• glog.service
• glog.servprov
• glog.session
• glog.settlement
• glog.shipgroup
• glog.shipment
• glog.shipmentstatus
• glog.signedServlet
• glog.sku
• glog.sms
• glog.socket
• glog.sql
• glog.sqlServlet
• glog.startup
• glog.status
• glog.steptender
• glog.stylesheet
• glog.tender
• glog.textfile
• glog.thread
• glog.threadlocal
• glog.threadMonitor
• glog.timechart
• glog.timestamp
• glog.timezone
• glog.trackConnections
• glog.trackCursors
• glog.trackingevent
• glog.trailerbuild
• glog.transactionMediation
• glog.transmissionOrdering
• glog.ui
• glog.uom
• glog.util
• glog.vpd
• glog.web
• glog.webserver
• glog.webservice
• glog.workflow
• glog.xlane

GTM Properties

See GTM Property Files.

HERE Properties

See HERE Properties.

ALK Properties

See ALK Properties.

Oracle Maps Cloud Service Properties

See Oracle Maps Cloud Service (formerly known as elocation) Properties.

Non-Standard

The following properties do not follow the standard naming convention:

• aa_webserver: See glog.fti Properties.
• alk properties: See ALK Properties.
• ALLOW_ADVANCED_ANALYTICS: See glog.fti Properties.
• here properties: See HERE Properties.
• isAllowedGTIAnalytics: See glog.fti Properties.

• ldap.debugUserNames: Set to true to stop suppressing user parameters.

  Note: To protect hosted systems, these properties cannot be modified in the cloud without a service request.

• ldap.debugPasswords: Set to true to stop suppressing password parameters.

  Note: To protect hosted systems, these properties cannot be modified in the cloud without a service request.

• OracleSpatial: See OracleSpatial Properties for more details.

Related Topics

Property Sets

Data Flow to Transportation Intelligence