XML Gateway Setups

1. Define System Profile Options – The required profile options are as below

1. ECX: Log File Path - The directory path for XML messages and log files. Log File Path where the XML messages and runtime log are stored .

2. ECX: XSLT File Path - The directory path for XSLT style sheets. 

3. ECX: System Administrator Email Address - XML Gateway System Administrator e-mail address.  

4. ECX: Server Time Zone – The time zone in which the database server is running. 

2. Assign XML Gateway Responsibility – Assign ‘XML Gateway’ Responsibility using System Administrator à Security à User à Define

3. Define UTL_FILE_DIR Parameter –

To use Oracle XML Gateway, you must first create directories where the XML message process log and XSLT style sheets will be stored. Oracle XML Gateway uses the UTL_FILE package to read and write to the server.

It is set up in the system.

4. Hub Definitions Form -

A hub is an integration point typically used to route documents to and from trading partners. The Hub Definitions form is used to define the hub and the authorized users conducting business via the hub. The hub users entered in this form will appear on the Trading Partner Setup form.

XML Gateway Responsibility à Define Hubs

Name: Required Field. Enter the Hub name.

Protocol Type: Required Field. Protocol Type is the communication protocol associated with the hub, such as SMTP or HTTP. Select a value from the seeded list of values. The description for the protocol type is displayed

Protocol Address: When protocol type is HTTP or HTTPS, protocol address is prompted.

Protocol Address is the complete URL (including service/servlet) where the Transport Agent, will attempt to post the XML Document. If the Protocol type is SMTP, the protocol address is an e-mail address.

Hub Users

Username (Required): Enter the user name of the trading partner conducting business via the hub.

Password (Required): Enter the password for this user.

Hub Entity Code (Required): Enter the hub entity code for this user. It is the code found in the XML envelope to identify the source of the message.

5. Define XML Standards Form -

XML Gateway Responsibility à Define XML Standards

This form defines standards bodies for XML messages, such as OAG (Open Applications Group), ROSETTANET etc. Most probably we will be using OAG as XML Standards so need not create any entry here.

6. Define Transactions Form - 

XML Gateway Responsibility à Define Transactions

Define Transactions form is used to define the transactions that will be used by the XML Gateway Execution Engine. We then associate these transactions with a trading partner in the Trading Partner Setup form. The Define Transactions form provides the following:

• A cross-reference between the external transaction identifiers and the internal Oracle transaction identifiers.

• Identification of the queue from which to retrieve inbound messages

Party Type (Required): Party Type defines the type of trading partner, such as Supplier, Customer, Bank, or internal locations (such as warehouses). Select a value from the list of values.

Transaction Type (Required): Transaction Type is the product short name for the base Oracle Application associated with the transaction, such as "AR" for Oracle Receivables.

Transaction Subtype (Required): Transaction Subtype is a code for a particular transaction within the application specified by the Transaction Type. The last position of the code represents the direction of the transaction: "I" for inbound, "O" for outbound.

Transaction Description: Enter a description for the transaction.

Standard Code (Required): The XML standard to be used for this transaction. The Standard Codes are set up in the Define XML Standards form. Choose the code from the list of values.

Direction (Required): Direction indicates if the message is inbound or outbound. Select "IN" for inbound messages, or "OUT" for outbound messages from the list of values.

External Transaction Type (Required): External Transaction Type is the primary external identifier for the XML message.

External Transaction Subtype (Required): External Transaction Subtype is the secondary external identifier for the XML message. The combination of the External Transaction Type and the External Transaction Subtype should cross-reference this message to the Oracle internal transaction identified by the Transaction Type and the Transaction Subtype.

Queue (Required for Inbound Messages): A queue is a table in a database where transactions are staged for processing. Default queues are defined during installation. Select a queue from the list of values. The field is disabled for outbound messages.

7. Define Lookup Values –

XML Gateway Responsibility à Define Lookup Values

Seeded lookup types are defined here which are used in XML Gateway.

8. Trading Partner Setup –

XML Gateway Responsibility à Define Trading Partners

The Trading Partner Setup form is used to:

• Set up trading partners for multiple operating units.

• Enable messages for the trading partner by identifying the internal and external transaction type and transaction subtype codes, and the XML standard associated with the message.

• Access the Trading Partner User Setup form.

• Access the Trading Partner Code Conversion form.

• Select a message map for the trading partner.

• Identify the communications protocol and address for a message. Optionally, the user can be selected from a hub.

Trading Partner Type (Required):

Trading Partner Type defines the type of trading partner, such as Supplier, Customer, Bank or internal location.

Trading Partner Name (Required):

Given the selection in the Trading Partner Type, the appropriate Trading Partner

Names are displayed in the Trading Partner Name list of values.

Trading Partner Site (Required):

Given the selection in the Trading Partner Name, the appropriate Trading Partner Sites are displayed in the list of values.

Company Admin Email (Required):

This is the e-mail address of the administration contact to receive e-mails regarding warnings and errors.

Trading Partner Details

These details are discussed earlier in the document.

9. Code Conversion

The Oracle XML Gateway code conversion function provides a method to cross-reference the codes defined in Oracle E-Business Suite to codes used by trading partners, the XML standard, or other standard codes in the transactions.

XML Gateway Responsibility à Define Code Conversion