Using Property Values as Source Data

25-2 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator In the topology, each JMS destination is defined as a JMS XML TopicQueue data server with a single physical schema. A data serverphysical schema pair will be declared for each topic or queue delivering message in the XML format. The structure of the XML message mapped into a relational structure called the XML schema appears as a data model. Each datastore in this model represents a portion typically, an element type in the XML file. Processing Messages As each XML message corresponds to an Oracle Data Integrator model, the entire model must be used and loaded as one single unit when a JMS XML message is consumed or produced. The processing unit for an XML message is the package. It is not possible to declare the properties or header fields of the message in the model or use them as columns in an interface. They still can be used in message selectors, or be set through KM options. Consuming an XML message Processing an incoming XML message is performed in packages as follows: 1. Synchronize the JMS message to the XML schema: This operation reads the message and generates the XML schema. This is usually performed by the first interface accessing the message. 2. Extract the data: A sequence of interfaces use datastores from the XML schema as sources. This data is usable until the session is terminated, another message is read by a new Synchronize action, or the Commit JMS Read is performed. 3. Commit JMS Read: This operation validates the message consumption and deletes the XML schema. It should be performed by the last interface which extracts data from the XML message. Producing an XML message To produce an XML message, a package must be designed to perform the following tasks: 1. Initialize the XML schema: This operation creates an empty XML schema corresponding to the XML message to generate. This operation is usually performed in the first interface loading the structure. 2. Load the data: A sequence of interfaces loads data into the XML schema. 3. Synchronize the XML schema to JMS: This operation converts the XML schema to an XML message, and sends it to the JMS destination. This operation is usually performed by the last interface loading the schema. Filtering Messages It is possible to filter messages from a JMS XML destination by defining a Message Selector MESSAGE_SELECTOR KM option to filter messages on the server. This type of filter can use only the properties or header fields of the message. The filter is Note: This method is extremely similar to XML files processing. In JMS XML, the message payload is the XML file. See Chapter 5, XML Files and Appendix B, Oracle Data Integrator Driver for XML Reference for more information about XML Files processing and the XML Driver. JMS XML 25-3 processed by the server, reducing the amount of information read by Data Integrator. It is also possible to filter data in the interface using data extracted from the XML schema. These filters are processed in Data Integrator, after the message is synchronized to the XML schema.

25.1.2 Knowledge Modules

Oracle Data Integrator provides the Knowledge Modules KM listed in Table 25–1 for handling XML messages.

25.2 Installation and Configuration

Make sure you have read the information in this section before you start using the JMS Knowledge Modules: ■ System Requirements and Certifications ■ Technology Specific Requirements ■ Connectivity Requirements

25.2.1 System Requirements and Certifications

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing. The list of supported platforms and versions is available on Oracle Technical Network OTN: http:www.oracle.comtechnologyproductsoracle-data-integrator index.html .

25.2.2 Technology Specific Requirements

The JMS destinations are usually accessed via a JNDI service. The configuration and specific requirements for JNDI and JMS depends on the JMS Provider you are connecting to. Refer to the JMS Provider specific documentation for more details.

25.2.3 Connectivity Requirements

This section lists the requirements for connecting to a JMS XML database. Oracle Data Integrator does not include specific drivers for JMS providers. Refer to the JMS Provider documentation for the connectivity requirement of this provider. XML Configuration XML content is accessed through the Oracle Data Integrator JDBC for XML driver. The driver is installed with Oracle Data Integrator. Table 25–1 JMS XML Knowledge Modules Knowledge Module Description IKM SQL to JMS XML Append Integrates data into a JMS compliant message queue or topic in XML format from any ANSI SQL-92 standard compliant staging area. LKM JMS XML to SQL Loads data from a JMS compliant message queue or topic in XML to any ANSI SQL-92 standard compliant database used as a staging area.