Oracle XML Gateway Overview

Introduction

• Oracle XML Gateway is a set of services that allows easy integration with the Oracle E-Business Suite to support XML messaging.

• With Oracle XML Gateway services, you are assured consistent XML message    implementation when integrating with the Oracle E-Business Suite.

• The majority of messages delivered with the Oracle E-Business Suite are mapped using the Open  Application Group (OAG) standard.

XML Gateway Features

• The services supported by Oracle XML Gateway are grouped into four functional areas as follows:

         Message Designer

         XML Gateway Setup

         Execution Engine

         Transport Agent

• Message Designers:

    Use this wizard-guided tool to define message maps containing the RDBMS-to-XML or

    XML-to-XML data transformations.

•  Utilizes Servlet-Based Transport Agent:

     The servlet-based Transport Agent delivers and receives XML messages using

     SMTP, HTTP, or HTTPS protocols. Protocol types which can be used are as below:

XML Gateway Message Designer

• It is a Wizard Guided Tool used to define message maps. A message map represents the relationship between the source and target data elements.
• Each message map consists of a data source and data target representing where the data is coming from and where it is mapped to.
• There are Two Types of Data Definitions: RDBMS Data Definition & XML Data Definition
• RDBMS-based data definitions can be based on database tables, database views, Application Open Interface tables, or Application APIs.
• XML-based data definitions can be based on an XML Document Type Definition(DTD).
• In Message Designer we are doing two things:

          1. Map Source Data Structure to Target Data Structure

          2. Map Source Data Element to Target Data Element

Define Hub

• A hub is an integration point within your network (either your intranet or the internet). Hubs are typically used to route documents to and from trading partners.
• If we define the hub as the trading partner, you can identify all the buyers and sellers who are conducting business on the hub as Trading Partners to the hub.
• Before defining a hub, you must first complete these setup steps:

               Define System Profile Values

               Define XML Gateway Responsibility

               Define the utl_file_dir parameters

Define Transactions

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

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

      ii. Identification of the queue from which to retrieve inbound messages

For Outbound and Inbound XML we can refer  ECX_OUTQUEUE and ECX_DOCLOGS tables.

Trading Partner Setup

• Trading Partner Setup plays a vital role in XML Gateway Messaging. 
• It 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.
• In the XML Gateway, the term "Trading Partner" refers to an entity such as a customer, supplier, bank branch, or internal  locations at a particular address with which you exchange messages.
• The Trading Partner Setup form requires an entry for each Transaction Type and Transaction Subtype associated with this trading partner.