Configuration and Administration
GTM EBS Integration Properties
To control the behavior of Global Trade Management, you can change settings in the glog.properties file or the appropriate property set.
gtm.itm Properties
|
Property |
New in Version |
Description |
|---|---|---|
|
6.2 |
Properties to force which file to use to port EBS data to GTM compliance XML. Set these properties to a stylesheet content ID. Examples: gtm.itm.defaultEBSinstance.ITEM_SYNC=DEFAULT_ITEM_SYNC_STYLESHEET gtm.itm.defaultEBSinstance.PARTY_SYNC=DEFAULT_PARTY_SYNC_STYLESHEET gtm.itm.defaultEBSinstance.SHIPMENT_COMPLIIANCE=DEFAULT_SHIPMENT_COMPLIANCE_STYLESHEET gtm.itm.defaultEBSinstance.ORDER_COMPLIANCE=DEFAULT_ORDER_COMPLIANCE_STYLESHEET |
gtm.use Properties
|
Property |
New in Version |
Description |
|---|---|---|
|
6.4.3 |
This property is used to define whether functionalities related to EBS-GTM integration are configured via a parameter set or via properties. If the value of this property is 'true' then parameter set configurations are used. If 'false', then EBS-GTM integration properties are used. Note: The EBS-GTM integration properties are deprecated as of 6.4.3 release and will be removed in a future version. Default: false |
|
|
6.2 |
This property is used during EBS-GTM integration. It is assumed that only one EBS instance integrates with GTM and the data is created in only one domain by default. This property is set to "false" by default and it takes the EBS instance name as <defaultEBSinstance>. The XSLs used to transform EBS XMLs to GTM XMLs are mapped using the following properties:
If the property is set to "true", it means that multiple EBS instances can be mapped to GTM and every EBS instance integration can create data in different domains. The corresponding properties can be modified as following by taking the instance names EBS1 and EBS2 for mapping:
|
Related Topics
