Inbound HTTP Integration

There are various options for sending integration messages into Transportation and Global Trade Management Cloud using HTTP:

• Standard Transmission XML integration: Requires XML which conforms to the XML schemas described within the Transmission Schema section.
• Transformed Non-standard or external XML format: A custom XSLT stylesheet can be applied to inbound XML to convert to the standard Transmission format. See the Transform Inbound XML with XSL section for additional details.
• Direct Load of standard Transmission: Used for optimised pre-load of business objects without triggering internal workflow or automation agents. Refer to the DirLoad section for additional details.

The specific URL path to call for each of the supported cases depends on the desired method of authentication. There are currently the following options:

• HTTP Authentication (Basic)
• OAuth 2

HTTP Authentication (Basic)

All integration messages using HTTP as the transport should use HTTPS URLs i.e. secured by Transport Layer Security (TLS).

The internal Transportation and Global Trade Management user credentials must be passed in the HTTP Authorization header (RFC 7617) i.e. not the Cloud SSO credentials. The following URL endpoints must be targeted (relative the Cloud server/port):

Endpoints and Relative URLs

Endpoint	Relative URL
Standard Transmission XML	GC3/glog.integration.servlet.WMServlet
Transformed	GC3/glog.integration.servlet.TransformerServlet
Direct Load	GC3/glog.integration.servlet.DirLoadServlet

OAuth 2

The Transportation and Global Trade Management application also supports OAuth 2 Client Credentials authentication. The Oracle Identity Cloud Service (IDCS) processes the authentication request and provides the access token that is used to access the application integration servlets.

See the OAuth 2 section of the Security chapter for configuration details.

The following URL endpoints must be targeted (relative the Cloud server/port):

Endpoints and Relative URLs

Endpoint	Relative URL
Standard Transmission XML	logisticsXmlApi/Transmission
Transformed	logisticsXmlApi/Transformer
Direct Load	logisticsXmlApi/DirLoad

Note: The supported content types for HTTP messages (corresponding to the Content-Type HTTP header parameter) are text/xml and application/xml.

Transform Inbound XML with XSL

You can configure Transportation and Global Trade Management Cloud to transform your inbound transmissions from another XML schema to a valid Transmission XML. To do this:

1. Create a Stylesheet Content record in the Transportation and Global Trade Management Cloud Database.
2. Include this processing instruction in the beginning of every transmission that Transportation and Global Trade Management Cloud needs to transform: <?gc3-int-translate stylesheet_name="stylesheet_name"?>, stylesheet name is the GID of the required Stylesheet Content record prefixed with "db:". You can include multiple processing instructions in one transmission, in which case, Transportation and Global Trade Management Cloud will transform in the order the processing instructions appear in the transmission.
3. Post XML documents to http://hostname/GC3/glog.integration.servlet.TransformerServlet instead of http://hostname/GC3/glog.integration.servlet.WMServlet.

Note: The use of uploaded (file-system based) stylesheets instead of Stylesheet Content is still supported for backward compatibility but is deprecated and their use should be replaced with Stylesheet Content as soon as possible. Support for file-system based stylesheets will be removed in a future version.