Configuration and Administration
glog.integration Properties
To control the behavior of Oracle Transportation Management, you can change settings in the glog.properties file or the appropriate property set.
Properties are case sensitive and case sensitivity may cause them to appear in a different order in Oracle Transportation Management.
|
Property |
New in Version |
Description |
|---|---|---|
|
20A |
Specifies if the outbound transaction order element should include transaction order line allocation details. The default value is false. Set it to true to include transaction order line allocation details. |
|
|
22B |
Use this property to increase Global Trade Management screening performance. Default: true Note: The properties 'glog.integration.Location.syncLocationCreation' and 'glog.integration.Contact.syncContactCreation' should be set to false. |
|
|
6.3.5 |
Determines if buy shipment related details display in the outbound Billing XML when performing Send Bill Interface on a bill or if only sell shipment related details display. By default only sell shipment related details will be visible (default is false). If you want buy shipment related details displayed, then set the property to true. |
|
|
|
With conversion of a collection of string buffers, the size of each collection member is controlled by this property (1000 is the default). Since data for each collection member requires continuous memory, this property can further restrict the max size of continuous memory during XML building process. |
|
|
|
This is a set of properties that restricts changing data text to upper case. This property is associated with the following property "glog.integration.enableCaseChange". Valid values for this property are element names. Some data such as arguments should stay in the format (case) they are in. For example, since the argument name and argument value is not to be changed, you would set the following properties:
|
|
|
glog.integration.Claim.Location.IncludeContactGroupLocations |
|
Specifies if the outbound Claim element should include Location details for Contacts within Contact Groups referenced in the Claim (e.g. involved parties, notify contact, etc.) |
|
|
Controls the number of attempts to query for XML for the Oracle centric XML such as RATE_OFFERING, RATE_GEO, and FLIGHT_INSTANCE. An error was detected where no data may be returned on a connection, but may be returned on another connection. This property will control how many attempts are made. |
|
|
20B |
When enabled, all contacts being created in a single application server will be synchronized. |
|
|
5.5 CU5 |
Allows handling of " and ' XML entity references via web service calls. Default: FALSE |
|
|
glog.integration.dataqueue.inbound glog.integration.dataqueue.inboundDXI glog.integration.dataqueue.transport.ftp glog.integration.dataqueue.transport.http glog.integration.dataqueue.transport.queue |
6.0 |
Overrides the name of the data queue. If you have created an integration data queue, you must declare the name of the data queue in one of these properties. For example, if you needed to configure the Integration Out Transport - FTP data queue you would create a copy of it and edit the copy. Then indicate the name of the copy in a property , such as: glog.integration.dataqueue.transport.ftp=GUEST.MY_TRANSPORT_FTP_COPY |
|
6.2.1 |
Defines the method used to process internal events resulting from processing the data queue event. The default is "execute". Refer to Integration Guide in the Oracle Help Center for more details. |
|
|
|
Determines if, when a queue is inactive, the process should go ahead and raise the topic to the MemoryEventQueue. If false, topic will be ignored. Default: true |
|
|
6.3.1 |
Use this property to change the root element tag for exported data. |
|
|
19 |
Controls the default country value for situations where a country is not defined. |
|
|
|
This sets the default XSL stylesheet for Oracle Transportation Management to apply to all inbound transmissions. |
|
|
on - enable DirLoadServlet support for the transaction code delete. off - (default) disable DirLoadServlet support for the transaction code delete. |
||
|
on - enable DirLoadServlet support for the transaction code insertupdate. off - (default) disable DirLoadServlet support for the transaction code insertupdate. |
||
|
on - enable DirLoadServlet support for the transaction code update. off - (default) disable DirLoadServlet support for the transaction code update. |
||
|
|
Integration requires that data is in upper case. Usually, the user interface in Oracle Transportation Management forces data into upper case. Data imported from Oracle's E-Business Suite (EBS) is usually in mixed case. This property if set to True, will change the text to upper case. You can limit what is changed with the glog.integration.casechange.element property. |
|
|
6.0 |
When set to TRUE the old data elements for all inbound interfaces can be used. |
|
|
|
When set to TRUE, outbound XML will be formatted to remove white spaces (spaces, tabs, line feeds, etc.). Default: FALSE |
|
|
6.2 |
Indicates the hosts that should be connected too directly and not through the proxy server. |
|
|
6.2 |
Indicates the proxy server and port that the FTP protocol handler will use. |
|
|
6.2 |
Indicates the proxy server and port that the FTP protocol handler will use. |
|
|
glog.integration.lifetime.transaction.enableEvents glog.integration.lifetime.transactionout.enableEvents |
Specifies if any of the lifetime events for the transmission should be raised. Preserves backward compatibility. Default: false |
|
|
glog.integration.location.childOperationalLocation.allowRecursion |
21C |
An error is generated during export when locations are created with operational locations referring to the same parent location. This can also happen when there is a circular dependency on the locations. To control recursion during export, this property has been introduced. Default: false. When false, the system limits the nesting level of child operational location to 1. When set to true , the recursive behavior is enabled. |
|
6.2.3 |
When enabled, all locations being created in a single application server will be synchronized. |
|
|
|
Controls how the transaction success message is recorded in the integration log table. The logging can be disabled to improve performance. Possible values are:
|
|
|
6.2.3 |
Suppresses the Transmission Received (inbound) and Transmission Sent (outbound)integration log messages. Possible values are:
|
|
|
6.3.5 |
To use OTM or GTM contact interface, perform the following configuration: Contact with GTM details glog.notify.XMLBuilder.glog.server.workflow.notify.contact.ContactEventContext =gtm.server.workflow.notify.GtmStandardXMLBuilder glog.integration.notification.contactEntity.isGtm=true Contact (default) glog.notify.XMLBuilder.glog.server.workflow.notify.contact.ContactEventContext =glog.server.workflow.notify.StandardXMLBuilder glog.integration.notification.contactEntity.isGtm=false |
|
|
22B |
Sets the default communication method in the Notify Type field for the Send Interface Transmission actions. Default: HTTP |
|
|
6.4.3 |
Some transactions may be Long Running. This property provides the default number of transactions needed to make the action long running. Default: 100. |
|
|
|
Specifies the default time zone for the OrderMoveReplace interface when the OrderMoveReplace.TimeZoneGid element is not specified. |
|
|
|
This property indicates if the default value should be from the property or retrieved from the source location for the order release. Possible values are [property|release]. If the value is property, then the defaultTimeZone property is used as the default. |
|
|
5.5 CU6 |
This property can be configured to set a default value for the ship_unit_origin column on the order_release table. Values for this property are R, B, and U. This is optional and on an as-needed basis.
R - Release B - Base (Order base) U - User
When new release comes in via integration, this property has no impact. When an update to a release is sent in via integration and if ship_unit_origin is null in the database, then the value of this property will be saved in the database for the ship_unit_origin column . For example, you set there property to B and the ship_unit_origin is null. When the order release is updated via integration the B from the property will be entered in the ship_unit_origin column. If the property is not set, then the ship_unit_origin column will not be updated. |
|
|
|
Controls whether the default outbound XML Profiles are used. The default profiles are defined for each interface in the INT_GLOG_XML_ELEMENT table. These profiles are overridden by specifying a profile for the external system. useDefaultProfiles - specifies if the profiles are used enableDefaultProfileCache - specifies if caching is enabled glog.integration.outXmlProfile.useDefaultProfiles = true glog.integration.outXmlProfile.enableDefaultProfileCache = true |
|
|
|
This property is related to EBS Integration. Set to False. This property overrides the default namespace properties. |
|
|
|
Provides an approach to relax the foreign key relationship to allow for shipments to refer to orders not within Oracle Transportation Management, as well as supporting the removal of the order release line without having to delete records. Default: false. |
|
|
6.1 |
If set to "true", this property controls the creation of locations so that the creation is sequential rather than multiple threads attempting to create the same location at the same time. Defaults to false. This property should be set to true only if you experience DUPLICATE KEY ERROR DUE TO SIMULTANEOUS LOCATION UPDATES. Otherwise, since the system forces location creation to be done sequentially, there can be some contention. |
|
|
6.1 |
When the release XML is sent, and this property is set to 1, the ShipFromLocationRef and ShipToLocationRef elements will send out full Location information rather than just the Location GID. This happens only when the release is not included in the shipment XML. Defaults to 0. |
|
|
5.5 CU4 |
1 - Allows the RemoteQueryReply element to be wrapped in the GLogXMLElement. This allows users to send more than one RIQ into Oracle Transportation Management using the RemoteQuery interface. Since the RemoteQueryReply interface only sends one reply back, it will drop the additional RIQs. With this property set to 1, it will wrap the reply in the XML transmission which will send all the RIQs back in the reply. The default is 0. The element Transmission/TransmissionHeader/QueryReplyFormat when given in the XML to be uploaded provides an override to the property. |
|
|
5.5 CU4 |
This allows you to specify the unit of measure for the RIQQueryReply response to RIQQuery XML in integration (RemoteQueryReply/RIQQueryReply/RIQResult/TransitTime element). Possible values for the property are as follows:
The default is "H" for hours if not specified. |
|
|
6.3 |
Enables rounding of the RIQResult/TransitTime when running the RemoteQuery/RIQQuery inbound integration. The property must be set to true to enable rounding. Default: false. |
|
|
6.1 |
If set to TRUE, this property controls the creation of packaged items to be sequential rather than multiple threads attempting to create the same packaged item at the same time. This property should be set to true only if you experience a duplicate key error due to simultaneous packaged item updates. Defaults to false. |
|
|
|
This property is related to EBS Integration. Default is false. The RC Transaction Code generally applies to child elements. This property enables the logic to null out the data in the parent element as well. Default: true. |
|
|
glog.integration.RIQQuery.FlexCommodityQualifierGid.defaultFAK |
6.2 |
This property affects the classification process in rate inquiry integration. When set to false (default) the Flex Commodity Qualifier in Rate Inquiry will not default to FAK (Freight All Kinds). When set to true, the Flex Commodity Qualifier in Rate Inquiry will default to FAK. |
|
|
Specifies how the content of the IMessageText element is formatted. Possible options are as follows:
|
|
|
|
This controls how the elements are formatted. Valid values are: comment, CDATA, normal. |
|
|
6.2 |
This property gets the Sender System ID (URL) and inserts it into the Transmission Header for an outbound XML. The property defaults to the Oracle Transportation Management webserver URL, but is editable. The format is in the form of: http://$webserver$:$webserver.port$ Any valid URL will work. |
|
|
|
These properties improve the error reporting functionality during the Integration staging of the Transmission XML through WMServlet. The functionality can be configured to send back a TransmissionAck with the echoed TransmissionHeader, Stack Trace, and the original XML sent. |
|
|
glog.integration.servlet.TransmissionStageError.elementName = StackTrace |
This property specifies if the response is a StackTrace or TransmissionAck. |
|
|
glog.integration.servlet.TransmissionStageError.includeTransmissionText |
This property indicates if the full transmission is sent back. Valid values are True or False. |
|
|
glog.integration.servlet.TransmissionStageError.senderrorEmail = false glog.integration.servlet.TransmissionStageError.erroremailFrom = glog.integration.servlet.TransmissionStageError.erroremailSubject = glog.integration.servlet.TransmissionStageError.errorEmailTo = Transmission XML Stage Error |
The following properties specify if an email should be sent and to whom. You can also set the email properties to a support email address to monitor when exceptions occur. |
|
|
6.2 |
When set to TRUE, the default, this causes orphaned ship units to be deleted when they are removed from a shipment using the ActualShipment interface with a TransactionCode = RC or DR. |
|
|
|
When set to true, the system uses the insert_date column as the select criteria to find the shipments to be purged. Then the purge is executed by EJB and not by the database. Defaults to false. |
|
|
|
Provides an approach to use temporary keys to allow for shipments to refer to orders external to Oracle Transportation Management, as well as supporting the removal of the order release line without having to delete records. Default: false. |
|
|
|
Specifies whether the packaged item details from the release are included in the outbound shipment. |
|
|
glog.integration.Shipment.PackagedItem.includeFromTransOrderLine |
|
Specifies whether the packaged item details from the TransOrderLine are included in the outbound shipment. |
|
glog.integration.Shipment.PackagedItem.includeFromTransOrderShipUnit |
|
Specifies whether the packaged item details from the TransOrder ShipUnit are included in the outbound shipment. |
|
22A |
Controls whether complete location data or just the Location GID is included with the ShipmentStop element. When this property is set to true, the complete location information will be included. Defaults to false. |
|
| glog.integration.shipmentStatus.isLookupTimeZoneByLocation | 23C |
This property specifies whether to get the time zone based on LocationRefnumQualifierGid and LocationID or LocationGid elements. Default: true |
|
glog.integration.shipment.shipunit.mapReleaseShipUnitFromShipUnitLines |
6.2 |
Sets the ship_unit_gid on the s_ship_unit_table referencing the order release ship unit when the field is empty in the XML. The value is taken from the ship unit lines. This property is needed for the EBS integration to effectively clean up the orphaned ship units and update the reference to the release ship unit. |
|
22C |
For a SAW (Shipment As Work) integration, there is an integration command as well as an agent action that can be set to do persist only. This property also controls that behavior. When enabled, business logic will not be performed and the shipment XML will be persisted as is. Default = true. |
|
|
|
Provides a default value for the responsible party in the Shipment Status interface if it is not provided in the XML. Default: CARRIER |
|
|
true - Enable ShipmentStatus interface to lookup the SSStopSequenceNum using the LocationRefnumQualifierGid and LocationID elements false - You must supply the stop number for the shipment status. Default: false. Note: Previously, you could set the property value to 0 or 1. Now, you will only be able to set the property value to true or false. For backward compatibility, the application supports the property value 0 or 1 if already set. |
||
|
true -Generate an error, if glog.integration.ShipmentStatus.findSSStopNumByLocationID is enabled and the LocationID is missing from the ShipmentStatus interface. false - No error is generated, even if glog.integration.ShipmentStatus.findSSStopNumByLocationID is enabled and the LocationID is missing from the ShipmentStatus interface. Default: false. Note: Previously, you could set the property value to 0 or 1. Now, you will only be able to set the property value to true or false. For backward compatibility, the application supports the property value 0 or 1 if already set. Note: This must be set to false if you pass both LocationID and LocationName in the same transaction. Otherwise, the transaction will error out even though it is a non stop related event. |
||
| glog.integration.shipmentStatus.lookupTimeZone |
When this property value is set to true, the application translates timeZone of the timezone gid "Local" to a real timeZone if there is sufficient stop level information available. Note: Previously, you could set the property value to 0 or 1. Now, you will only be able to set the property value to true or false. For backward compatibility, the application supports the property value 0 or 1 if already set. |
|
|
6.2.3 |
When set to true, it will skip the Byte Order Mark, if present in the XML, while reading the inbound XML via HTTP or through the UI. Default: False |
|
|
glog.integration.tenderresponse.shipmentSourceLocationTimeZone |
5.5 CU3 |
When set to True, the shipment source location's time zone will be used. When a carrier responds to the tender with pickup date changes (using a Tender Response XML), Oracle Transportation Management calculates/converts the date/time for pickup if no timezone is entered in the Tender Response XML. |
|
20A |
A Topic interface request may be immediately executed or published. If published, there may be a small delay in processing the topic as it's made available to all servers in the cluster. If true, the topic is published for all servers; if false, it is executed on the current server. |
|
|
6.0 |
To suppress storing the RemoteQuery XML in the table, set the property to True. It will still store a record in the i_transaction table, but the size of the storage should be reduced. |
|
|
|
Specifies the XSL transformation engine to use in integration. Possible values are sax or cocoon. |
|
|
Specifies the mode to use for building outbound Staging Transmissions. The field indicates whether to build up the XML in the i_transmission table as each transaction is added, or to wait until the Transmission completion process is initiated for the Transmission. Options are: B: append the transaction to the transmission field as each transaction is added TH: the field should initially only contain the TransmissionHeader, and the concatenation will occur at completion. |
||
|
Default: True This improves the building of transmissions by not maintaining the individual transactions. There is a process to concatenate the individual transactions into the transmission when complete. |
||
| 22A |
Set this to true to acknowledge an inbound transmission immediately rather than only when all contained transactions have been staged for later processing. Although this capability, referenced as "pre-staging," provides a quicker acknowledgment to the sending client, a greater benefit will be noticed when the number of transactions contained within the transmissions are large. In these use cases, it has been possible that client processes can time out before the transmission acknowledgment (TransmissionAck) has been returned. When enabled it will apply to ALL inbound transmissions. I.e. it is not possible to use the new pre-staging logic for specific transmissions. See the Cloud Integration Guide for more details. Default: False |
|
|
This creates a staging transmission where transactions can be added until the transmission needs to be sent. This allows the Issue Allocation process to be run frequently, but only initiate the sending of the transaction when needed. The default is True to enable staging. |
||
|
6.0 |
To suppress storing the full Transmission XML, set this property to True. Note that the TransmissionHeader will be stored in the i_transmission table when this property is enabled. It will still store a record in the i_transmission table, but the size of the storage should be reduced. |
|
|
6.3 |
Controls the maximum number characters in the Persisted XML of a transmission or Transaction XML of a transaction allowed to be viewed before it is written out to a file. It also control the size of the transmission details displayed in the UI, such as when viewing details of a transmission. Default: 2000000 |
|
|
glog.integration.transmissionHeader.logStagingProcessErrAsWarning |
|
Controls whether the TransmissionHeader.StagingInfo.StagingProcess.IntSavedQuery will have their errors logged as warnings. If they are logged as errors, then the Transmission STATUS will be marked as ERROR when completed. |
|
glog.integration.transmissionHeader.logStagingQueryErrAsWarning |
|
Controls whether the TransmissionHeader.StagingInfo.StagingQuery.IntSavedQuery will have their errors logged as warnings. If they are logged as errors, then the Transmission STATUS will be marked as ERROR when completed. |
|
|
The following property specifies the status of the Transmission when an error occurs during the initial Stage processing where the StagingQuery and StagingProcess, and Transmission.Refnum is handled. |
|
|
Use this property to override the system default time zone for controlling the time conversions for the TransOrder/TransOrderHeader/EffectiveDate and ExpirationDate elements. When the property is set, it will be assumed that the effective data and expiration date fields are provided in that time zone. |
||
|
You can synchronize the processing of the packaged item in the TransOrderLine. You enable this by setting the property to true. Note that there is performance implications with sequencing the processing of the PackagedItems within the TransOrderLine. Doing so prevents two independent TransOrders that are being processed from creating the same PackagedItem in the TransOrderLine. |
||
|
|
Controls where Oracle Transportation Management sends Billing transmissions. http://<server_name>/servlets/<ClassNameOfServletThatReceivesFinancialRelatedXML> |
|
|
|
Controls where Oracle Transportation Management sends Voucher transmissions. http://<server_name>/servlets/<ClassNameOfServletThatReceivesFinancialRelatedXML> |
|
|
|
Controls whether the ObjectGid(s) that are found via the IntSavedQuery or other search logic should be re-used for a Transaction when a Transaction is re-processed. This will enable only the ObjectGid(s) that were not processed to be re-processed. The ObjectGid(s) are stored in the i_transaction_detail table and will be re-used when this property is true. When the property is false, the i_transaction_detail records will be deleted and the query will be re-run to generate a new set of ObjectGid(s). |
|
|
The default behavior regarding the validation of inbound XML transmissions is controlled by the glog.integration.validation property. OnPersistErrorOnly - (Default) Oracle Transportation Management only validates fully after a database persistence error occurs. However, when the data is invalid, Oracle Transportation Management goes back and validates the XML in order to provide user-friendly error messages stated in terms of the XML rather than in database terms. None - the only errors issued will be Oracle persistence errors. Full -Every inbound XML transmission is subjected to full validation. This causes the appserver to issue many SQL queries to validate foreign key constraints. This is the Oracle Transportation Management 3.0 behavior. |
||
|
Decides if the FKNotFoundErrorText error message will format the GID as String (e.g. GUEST.1) or as XML (e.g. <Gid><DomainName>GUEST</DomainName><Xid>1</Xid></Gid>) |
||
|
These are properties to override the general glog.integration.validation behavior and reset for a specific interface. Valid values are OnPersistErrorOnly, None, and Full. e.g: glog.integration.validation.transactionackinterface for TransactionAck exceptions are: glog.integration.validation.ShipmentInterface for PlannedShipment, ActualShipment, and TenderOffer glog.integration.validation.orderinterface for TransOrder |
||
|
22A |
When set to true, ensures that the username and password are sent in an outbound SOAP message as the standard Web Service Security Username Token. This supports external WSDLs which do not declare an attached policy but need to be accessed via a WSDL URL. The corresponding Web Service must also have the Use Web Service Security field selected. Default: false. |
|
|
|
If all service messages are for objects in one domain, set this default and it is not required in every message. Values: domain names |
|
|
|
If true default domain name will be taken from OTM user passed in message or as security credentials. If false the value in the glog.integration.webservice.execute.defaultDomain property will be used. |
|
|
glog.integration.webservice.handler.jws.outbound.useAbsoluteURI |
6.2.4 |
When set to True an absolute URI will be sent. |
|
6.2 |
Allows you to specify https as a valid scheme for retrieving the WSDL from the application server using an https URL. Default: http. Valid values are http and https. |
|
|
19B |
Controls whether the "View WSDL Content" link appears in the Retrieve WSDLs page. Default: false |
|
|
6.4.2 |
The Soap Attachments API for Java (SAAJ) used by the Web Services framework in Weblogic 12.1.3 has changed from previous versions. This has caused a change in the SOAP HTTP XML message payload which has caused customer issues. This property will reinstate the SAAJ API used by earlier versions. By default the new feature is active. To disable the change, set this property to true. To enable this feature, set the following properties on the application server startup command: -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl -Djavax.xml.soap.SOAPFactory=weblogic.xml.saaj.SOAPFactoryImpl |
|
|
6.3.7 |
You can override the host and port that is present in the WSDL for each of the OTM/GTM web services retrieved via the Retrieve WSDLs page. Previously this would always show one of the internal application server details. This can now be overridden by setting this property. For example, glog.integration.wsdl.url=http://example.com:7577. |
|
|
glog.integration.xml.userConversion.dbxml = <stylesheet content GID> glog.integration.xml.userConversion.transmission = <stylesheet content GID> |
20C |
The integration implementer has the capability to define a custom XSLT stylesheet stored in the Stylesheet Content table and use it to correct any invalid XML messages that would otherwise be rejected. The feature is available for inbound Transmission and DBXML XML requests and is enabled by setting one of these properties to have the value of the Stylesheet Content GID created to perform the correction. For more information on using this property and the required stylesheet, see Using a Stylesheet to Correct Inbound XML Messages (Doc ID 2680823.1). |
|
|
Specifies the character used to indicate a field should be nulled out in the database. |
|
|
6.2 |
Set this property to True to see required elements and elements from the template in outbound XML. When set to false, or not present, the outbound XML contains elements from XML template only. If you would like to see required elements as well, then you must add this property to the glog.properties file and set the value to true. |
Related Topics
If you have any questions or comments about this documentation page, please Contact Oracle Documentation. 