Setting Properties when Sending a Message

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. 25-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator Ask your system administrator for the location of the DTD file describing the XML content.

25.3 Setting up the Topology

Setting up the Topology consists of: 1. Creating a JMS XML Data Server 2. Creating a JMS XML Physical Schema

25.3.1 Creating a JMS XML Data Server

An JMS XML data server corresponds to one JMS providerrouter that is accessible through your local network. There are two types of JMS XML data servers: JMS Queue XML and JMS Topic XML. ■ A JMS Queue XML data server is used to connect a single queue in the JMS router to integrate XML messages. ■ A JMS Topic XML data server is used to connect a single Topic in the JMS router to integrate XML messages. The Oracle Data Integrator JMS driver loads the messages that contains the XML content into a relational schema in memory. This schema represents the hierarchical structure of the XML message and enables unloading the relational structure back to the JMS messages.

25.3.1.1 Creation of the Data Server

Create a data server either for the JMS Queue XML technology or for the JMS Topic XML technology using the standard procedure, as described in Creating a Data Server of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. The creation process for a JMS XML Queue or JMS Topic XML data server is identical to the creation process of an XML data server except that you need to define a JNDI connection with JMS XML specific information in the JNDI URL. See Section 5.3.1, Creating an XML Data Server for more information. This section details only the fields required or specific for defining a JMS Queue XML or JMS Topic XML data server. 1. In the Definition tab: ■ Name: Name of the data server as it will appear in Oracle Data Integrator. ■ UserPassword: Not used here. Leave these fields empty. 2. In the JNDI tab: ■ JNDI Authentication: From the list, select the authentication mode. ■ JNDI User: Enter the username to connect to the JNDI directory not mandatory. ■ Password: This users password not mandatory. ■ JNDI Protocol: From the list, select the JNDI protocol not mandatory. ■ JNDI Driver: Name of the initial context factory java class to connect to the JNDI provider, for example: com.sun.jndi.ldap.LdapCtxFactory