Outbound Integration and Notification

Web Services

You can send data from Oracle Transportation and Global Trade Management via a web service call. For proper security, the downstream system used in outbound integration should require a username and password for user authentication. If the downstream system uses the WS-Security Username Token Policy, the username and password should be specified when creating the Web Service EndPoint.

OutXMLProfile for Outbound Integration and Notification

Out XML Profiles allow you to generate outbound XML and exclude portions of outbound XML with a high degree of control. This is done by specifying what XML builder class files should be excluded when generating XML documents or by selecting an XML template on which you can base the outbound XML. Outbound XML includes integration and notification. Unnecessarily large outbound integration is a common cause of performance issues. Reducing the size of the XML will greatly reduce the load on the database and application server.

XSL Stylesheets for XML Document Generation and Email Notification

Oracle Transportation and Global Trade Management supports the ability to configure XML Document Generation and Email Notification via XSL stylesheet. The following steps should be followed to upload an XSL stylesheet and apply it to an External System or Contact Notification.

Create a Stylesheet Content record and upload the corresponding XSL file.
This page is located at Business Process Automation > Power Data > Event Management > Stylesheet Content.
Create a Stylesheet Profile record, specifying the previously created Stylesheet Content.
This page is located at Business Process Automation > Power Data > Event Management > Stylesheet.
Create/Edit Contact Notification by setting the Stylesheet for the 'Email' Communication Method to the Stylesheet Profile created in Step #2.
This page is located at Business Process Automation > Communication Management > Contact Notification.
For XML Document Generation, create/Edit External System by setting the Stylesheet Profile to the Stylesheet Profile created in Step #2.
This page is located at Business Process Automation > Communication Management > External Systems.

XSL Stylesheets to Customize Email Notifications

Oracle Transportation and Global Trade Management service supports the ability to download default XSL files for notifications. Please use the following steps to download default XSL files for customization.

Select Stylesheet Content: Select a default Stylesheet Content record and download the corresponding XSL file. This page is located at Business Process Automation > Power Data > Event Management > Stylesheet Content.
Customize the downloaded XSL file and upload the newly created file to Stylesheet Content. This page is located at Business Process Automation > Power Data > Event Management > Stylesheet Content.
To refer another stylesheet in an XSL file or to To import another stylesheet, which is already present in the database, then the import statement is to be given as below:
```
<xsl:import href="db:<STYLESHEET_CONTENT_GID>"/>
```

Note: db: specifies that the stylesheet to be imported should be looked up in the STYLESHEET_CONTENT table.

Outbound Integration and SSL Certificates

All outbound integration requires that the transport be protected using HTTPS. Communications over HTTPS are encrypted using SSL. These SSL communications are initiated using SSL Certificates. The SSL Certificates must be from a trusted signing authority (no self-signed certificates). It is possible that the list of trusted signing authorities in the Oracle Transportation and Global Trade Management Cloud will not contain the Certificate for your signing authority. In that case an SR will need to be raised to request the Certificate be reviewed for possible inclusion.

Only 1-way SSL handshaking is supported. 2-way SSL functionality is planned for a future release. For more information, see, Logistics Cloud: How to Configure Outbound Integration (Doc ID 2110592.1).

IP Allow List for Outbound Integration

All outbound integration is routed through a NAT Gateway. If you have a firewall with IP restrictions on inbound integration to your data center (outbound from Oracle Cloud), please see the following MOS Note for details on obtaining the IP Addresses.

What are the OCI Gen2 IP Addresses for Outbound Integration? (Doc ID 2662320.1)

Note: You'll need to request the IP range for both the Primary and Disaster Recovery Regions.

Note: There's an exception to this routing for traffic outbound to Oracle Integration Cloud endpoints. The traffic is going over the Service Gateway rather than the NAT Gateway by default. In this case, you need to open a Service Request with Oracle Transportation and Global Trade Management to change the routing of that traffic to go out of the NAT gateway instead of the Service Gateway.

Outbound Integration and PaaS/IaaS

The following instructions are intended to provide high-level information for integrating Transportation and Global Trade Management with an application hosted on Oracle Cloud Infrastructure PaaS/IaaS services. For more detail on this topic, please see the documentation corresponding to your particular PaaS service. Integration from Transportation and Global Trade Management to any other application hosted on an Oracle Cloud Infrastructure service must be performed via a publicly accessible IP address and publicly accessible ports. By default, access to Oracle Cloud Infrastructure Services are available via port 80 (HTTP) and 443 (HTTPS). If the service isn't provisioned with a public IP address, it will be necessary for you to reserve a public IP address for their service.

It is highly recommended that you register your service using a Public Domain Name and use the Domain Name in the URL, rather than the IP address. It is also recommended that you obtain an SSL Certificate for their Domain Name and require that all communication use HTTPS. Depending on the Certificate Authority used, it might be necessary to open a Service Request to have the SSL Certificate loaded into the Transportation and Global Trade Management instance.

You should test all URLs from outside of Transportation and Global Trade Management first using a web browser or a utility such as JDeveloper, SOAPUI, curl, or wget. For more details, please see the "Register a Custom Domain Name with a Third-Party Registration Vendor" and "Obtaining the SSL Certificate" topics in the Infrastructure as a Service documentation.

Note: If you're integrating with an instance of Oracle Integration Cloud (OIC) that's in the same region as your Transportation and Global Trade Management instance, you'll need to open a Service Request to have Cloud Operations properly route the outbound integration traffic to your OIC instance. This isn't necessary if the OIC instance is found in a different region.

Outbound REST Integration

In addition to the HTTP (POST) and SERVICE (SOAP Web service) communication methods there is now a REST option which can send out the JSON REST resource format and Transmission XML messages. The determination of which format to use is controlled by the content type defined on the target external system. See the REST API documentation for details.