1. E-Business Suite Integration Guide
  2. Related Properties or Parameters

Related Properties or Parameters

The required configuration to be done on GTM side for EBS-GTM integration can be done using either properties or parameter set as of GTM 6.4.3. The following properties are deprecated as of 6.4.3 and will be completely removed in the future release.

  • gtm.integration.enableParserInServlets
  • gtm.use.instance.name.for.domain.mapping
  • gtm.itm.use.stylesheetcontent.table
  • gtm.itm.defaultEBSinstance.ITEM_SYNC
  • gtm.itm.defaultEBSinstance.PARTY_SYNC
  • gtm.itm.defaultEBSinstance.SHIPMENT_COMPLIIANCE
  • gtm.itm.defaultEBSinstance.ORDER_COMPLIANCE
  • gtm.itm.acknowledgement

So, you should try to configure the related parameters using the parameter set method.

gtm.use.instance.name.for.domain.mapping

Set this property to “true” to map Oracle E-Business Suite instances to separate sets of stylesheets. If you set this property to “true”, the instance name from the incoming request using request.getRemoteHost() is used to determine the instance name. By default, this property is set to “false”.

Each instance must have the four style sheet properties copied and presented with either the new paths or the style sheet content IDs.

By default,the following properties map an Oracle E-Business Suite instance to its XSL files used for mapping. Mapping activity is nothing but transforming Oracle E-Business Suite ITM XML to Oracle Global Trade Management XML as per Integration schema.

gtm.itm.defaultEBSinstance.ITEM_SYNC=gtm/itm/ItemSync.xsl
gtm.itm.defaultEBSinstance.PARTY_SYNC=gtm/itm/PartySync.xsl
gtm.itm.defaultEBSinstance.SHIPMENT_COMPLIIANCE= gtm/itm/ShipmentSync.xsl
gtm.itm.defaultEBSinstance.ORDER_COMPLIANCE= gtm/itm/OrderSync.xsl

<defaultEBSinstance> is a dummy that is used when the 'gtm.use.instance.name.for.domain.mapping' property is set to false.

The procedure to have different Oracle E-Business Suite instances inserting records in different domains is as follows:

  • You can copy the default XSLs to a different folder. Inside the copied XSLs, you could modify the domain in common.XSL.
  • You could potentially change mapping code as required for that instance.
  • Provide the following four properties like above with <defaultEBSinstance> replaced with instance name.

This way, you can have multiple Oracle E-Business Suite instances mapped to different domains on a single Oracle Global Trade Management instance.

gtm.itm.use.stylesheetcontent.table=false

Set this property to “true” to map Oracle E-Business Suite instances to XSL files from the stylesheet content table. By default, this property is set to “false”.

The same properties can be modified to map an Oracle E-Business Suite instance to its stylesheet contents (XSL files) used for mapping.

  • 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

The procedure to have different Oracle E-Business Suite instances inserting records in different domains is as follows:

  • You can access the stylesheet contents from the Transportation and Global Trade Management Cloud UI via Business Process Automation > Power Data >Event Management > StyleSheet Content.
  • You can search for the default stylesheet contents based on the request type (ITEM_SYNC, PARTY_SYNC, SHIPMENT_COMPLIANCE, ORDER_COMPLIANCE).
  • You can export the default XSL provided. By default, the domain name is GUEST. In the XSL, you can replace the domain name in the below tag with the required domain name.
    <xsl:variable name="domain">GUEST</xsl:variable>
  • You could potentially change mapping code as required for that instance.
  • You can create a new style sheet content in any domain you require. You can upload the modified XSL.
  • Provide the following four properties like above with <defaultEBSinstance> replaced with instance name with the corresponding style sheet content ID.

This way, you can have multiple Oracle E-Business Suite instances mapped to different domains on a single Oracle Global Trade Management instance.

Note: For Cloud systems, EBS-GTM integration works only when the property “gtm.itm.use.stylesheetcontent.table” is set to true and the corresponding mapping files point to the appropriate stylesheet contents.

Using Parameter Set

You can access the required parameters to set up EBS-GTM transformation stylesheets as part of "DEFAULT" parameter set under "GTM EBS INTEGRATION" section. Copy the "DEFAULT" parameter set, then change the parameter values under "GTM EBS INTEGRATION" section and save by entering a Domain Name and a Parameter Set ID. Configure this newly created Parameter Set in domain settings > parameter set.

The parameter "GTM EBS INTEGRATION CONFIG ID" takes a Logic Configuration ID as the parameter value. The default value of the parameter is "GTM EBS INTEGRATION DEFAULT" that has the parameters related to stylesheets. The parameter value can be either file path or stylesheet content. You can create/configure logic configuration via Master Data > Power Data > Configurations > Logic Configuration.

Note: The property "gtm.use.instance.name.for.domain.mapping=false" is not provided as part of the logic configuration as now domain information is available as part of authentication itself. The request gets redirected to that specific domain, reads the related parameter set, and uses the values for the required stylesheets.