External System - Main

Open this page using Admin > Integration > External System.

Note: This page is not available if both the External Message and the Open Market Interchange modules are turned off.

Description of Page

Enter a unique External System and Description.

CAUTION: Important! When adding new records, carefully consider the naming convention of the external system code. Refer to System Data Naming Convention for more information.

Use the field Our Name In Their System to specify the identity of your organization (i.e., your external system identifier) in the external system.

Note: The workflow process profile and notification download profile are only applicable to products that support workflow and notification. They and are not visible in the product if the Open Market Interchange module is turned off.

If this external system sends inbound communications through notification upload staging, the type of workflow process that is created is controlled by the sender's W/F (Workflow) Process Profile.

If you send notifications to this external system, select a Notification DL (download) Profile that is used to define the configuration of the outgoing messages.

Note: The remaining fields are not visible if the External Message module is turned off.

Set Usage to Template External System for external systems whose outbound message type configuration is inherited by other external systems.

If the outbound message type configuration should be inherited from a template external system, define the Template External System. If this field is specified, the outbound message type collection displays the data defined for the template system as display-only.

The Outbound Message Type accordion contains an entry for every type of outbound message defined for this external system. For each type of outbound message identify its Outbound Message Type.

Define the Processing Method for messages of this type. Valid values are Batch, Real-time, SOA and XAI.

Define an appropriate Message Sender if the processing method is XAI or Real-time.

Namespace Option is used when your message should include a namespace in the resulting XML. The valid option are Standard Namespace and Configured on Sender. If the value is Standard Namespace, the system will generate a namespace for the resulting WSDL with the following value: http://ouaf.oracle.com/outbound/AAA_​BBB, where AAA is the external system code and BBB is the outbound message type code. If the value is Configured on Sender, then the value of the namespace is taken from the sender context with context type Message Namespace URI.

Define an appropriate Batch Control if the processing method is Batch.

If the message sender is one with a message class of RTJSONSNDR, indicate the JSON Conversion Method. The valid values are Base JSON Conversion, Standard API Conversion and XSL Transformation. Refer to Real Time Message Configuration for more information about these methods and the additional configuration that may be applicable.

If the JSON Conversion Method is Base JSON Conversion, the Request Schema is enabled. Populate a data area that defines the schema for the XML format to convert the outbound message’s BO schema to prior to performing the JSON conversion. Refer to Real Time Message Configuration for more information.

The Message XSL is the schema used to transform information from the format produced by the system to a format understood by the sender, who receives a message of this type. This is not applicable for Processing Method of SOA. Refer to Referencing an XSL for information about configuring where the XSL is defined.

Enter the file name of the appropriate W3C Schema if you want to validate the message built for outbound messages for this external system / outbound message type prior to being routed to their destination. Refer to Outbound Message Schema Validation for more information. This is not applicable for Processing Method of SOA. This feature is not available for cloud implementations.

If the JSON Conversion Method is Base JSON Conversion, the Response Schema is enabled. Populate a data area that defines the schema for the XML format that the JSON message is initially converted to. The XML is then converted to BO XML. Refer to Real Time Message Configuration for more information.

Response XSL will only be displayed when the processing method is Real-time. Refer to Real Time Messages for more information on how it is used. Refer to Referencing an XSL for information about configuring where the XSL is defined.