JMS Message Structure Concepts

24-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator

24.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 .

24.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.

24.2.3 Connectivity Requirements

Oracle Data Integrator does not include specific drivers for JMS providers. Refer to the JMS Provider documentation for the connectivity requirement of this provider.

24.3 Setting up the Topology

Setting up the Topology consists of:

1. Creating a JMS Data Server

2. Creating a JMS Physical Schema

24.3.1 Creating a JMS Data Server

A JMS data server corresponds to one JMS providerrouter that is accessible through your local network. It exists two types of JMS data servers: JMS Queue and JMS Topic. ■ A JMS Queue data server is used to access several queues in the JMS router. ■ A JMS Topic data server is used to access several topics in the JMS router

24.3.1.1 Creation of the Data Server

Create a data server either for the JMS Queue technology or for the JMS Topic technology using the standard procedure, as described in Creating a Data Server of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. This section details only the fields required or specific for defining a JMS Queue or JMS Topic 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: Set this field to None. ■ JNDI User: Enter the username to connect to the JNDI directory optional step. JMS 24-5 ■ Password: This users password optional step. ■ JNDI Protocol: From the list, select the JNDI protocol optional step. ■ JNDI Driver: Name of the initial context factory java class to connect to the JNDI provider, for example: com.sun.jndi.ldap.LdapCtxFactory for LDAP ■ JNDI URL: JMS_RESOURCE, for example ldap:host:portdn for LDAP ■ JNDI Resource: Logical name of the JNDI resource corresponding to your JMS Queue or Topic connection factory. For example, specify QueueConnectionFactory if you want to access a message queue and TopicConnectionFactory if you want to access a topic. Note that these parameters are specific to the JNDI directory and the provider.

24.3.2 Creating a JMS Physical Schema

Create a JMS physical schema using the standard procedure, as described in Creating a Physical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. Create for this physical schema a logical schema using the standard procedure, as described in Creating a Logical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator and associate it in a given context.

24.4 Setting Up an Integration Project

Setting up a project using JMS follows the standard procedure. See Creating an Integration Project of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. It is recommended to import the following knowledge modules into your project for getting started with JMS: ■ IKM SQL to JMS Append ■ LKM JMS to SQL

24.5 Creating and Defining a JMS Model

This section contains the following topics: ■ Create a JMS Model ■ Defining the JMS Datastores Note: Only one physical schema is required per JMS data server. Note: It is not possible to reverse-engineer a JMS model. To create a datastore you have to create a JMS model and define the JMS datastores.