
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
The resulting list of values for a.property is now value1 and value3.
Workflow Example
A common example of multi-valued property use is the specification of thread count for a workflow
queue. The multi-valued properties that define workflow threads are given by:
glog.workflow.topicGroup=<queue name>,<thread count>
By monitoring workflow queue backup, you may need to increase the default thread count for a
specific queue. The batch queue, for example, handles many long-running batch processes. Assume
you wanted to increase the default thread count from 2 to 6. Simply adding the property:
glog.workflow.topicGroup=batch,6
is insufficient because it leaves the initial property declaration in place. The recommended approach is
to remove the initial declaration and then add the new one:
!remove glog.workflow.topicGroup=batch,2
glog.workflow.topicGroup=batch,6
Note that the !remove directive only works on properties that have been loaded. It must be declared
after the initial value has been included.
Property Macros
A property macro is a property whose value is used in the values for other properties. Any property
can be used by another via the following syntax:
<property>=[<prefix>]$<macro>$[<suffix>]
where <macro> is a previously declared property. When evaluating property macros, the property
macro must have been declared prior to its use. E.g., assume you have the following property files:
a.property=$a.macro$
!include standard.properties
another.property=$a.macro$
a.macro=test
glog.properties standard.properties
The evaluation of a.property has no value for a.macro. It is set to '$a.macro$'. But the value for
another.property is set properly to test.
Property File Management
Oracle Transportation Management ships with a set of property files in the
<otm_install_path>/glog/config directory, comprising the property heirarchy. The top-level file of
this hierarchy is glog.properties.
When instructed to change a property value, you will be instructed to make changes to only the web
server, only the application server, or both. In any case, be sure to make your changes to the
glog.properties file. All property changes made in any file other than glog.properties will be
over-written during every upgrade.
When adding, removing or modifying properties in the webserver's glog.properties file, make your
changes after the section starting with:
Comentarios a estos manuales