
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
The valid values are:
none – No optimization so all domains are used.
currentDomain – Status types from the current domain only are used.
childDomains – Status types from the current and child domains are used.
grantedDomains – Status types from all granted domains are used.
The following property controls how many domains will be included before the logic reverts to the
same behavior as “none”:
glog.query.statusOptimizationDomainMax=value
Manager Layout Producer Configuration
The XML document for an object is created by a series of "producers". These producers are associated
with objects within Oracle Transportation Management. Each manager in Oracle Transportation
Management has an XML document associated with it. When you create a custom manager layout you
can create or remove fields from that manager. The system creates an XML document containing
relevant data that is displayed in that manager. However the XML document may contain data that is
no longer needed in a custom manager that has had a lot of fields removed. By deleting the
associated producers from the custom manager the XML document will be smaller, allowing the page
to load more quickly. Refer to the “Manager Layout: Producers” topic in online help for more
information.
Parameterized Saved Queries
The UI finder mechanism in Oracle Transportation Management is a generic engine which enables
flexible querying of any business object in Oracle Transportation Management. A SQL query is
generated dynamically based on the user’s input in the finder query page. Due to the potential
complexity of the queries and the generic nature of the engine, it is not possible to always generate
SQL which will perform optimally when executed. Saved queries provided a mechanism for an end-
user to create a query using custom SQL. Users can create a saved query using SQL that is formatted
in a manner which performs more efficiently. This also provides a mechanism to specify a hint in the
SQL which will get passed to the Oracle SQL optimizer.
In addition to a standard saved query, there is an ability to create a saved query with parameters that
can be fulfilled at runtime. For more information on this topic refer to “How To Enable the Use of
Parameterized Saved Queries” in the online help.
Limiting Child Records in a Manager
The Oracle Transportation Management UI architecture is based on an XML document that is created
by querying a record and all of its related child records. In some scenarios the number of child records
can cause the XML document to be extremely large and therefore cause high memory usage and slow
performance. The number of child records returned is configurable via the glog.property:
glog.query.limit.glog.server.query.orderbase.QueryName=limit
The QueryName is the name of the corresponding query and the limit indicates the maximum number
of child records to return. If the number of child records exceeds this value, the manager will not
display any child records of this type.
For example:
glog.query.limit.glog.server.query.order.ShipUnitLineQuery=100
As of version 6.0 many, managers have these properties set by default.
Kommentare zu diesen Handbüchern