Using a JMS Destination

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 JMS XML 25-5 ■ JNDI URL: JMS_RESOURCE?d=DTD_FILEs=SCHEMAJMS_ DESTINATION=JMS_DESTINATION_NAME. The JNDI URL properties are described in Table 25–2 . ■ JNDI Resource: Logical name of the JNDI resource corresponding to your JMS Queue or Topic connection factory. Example If using an LDAP directory as the JNDI provider, you should use the following parameters: ■ JNDI Driver: com.sun.jndi.ldap.LdapCtxFactory ■ JNDI URL: ldap:ldap_host:portdn?d=DTD_ FILEs=SCHEMAJMS_DESTINATION=JMS_DESTINATION_NAME ■ JNDI Resource: Name of the connection factory Note: 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. Table 25–2 JNDI URL Properties Parameter Value Notes d DTD File location DTD File location relative or absolute in UNC format. Use slash “” in the path name and not backslash “\” in the file path. This parameter is mandatory. re Root element Name of the element to take as the root table of the schema. This value is case sensitive. This parameter can be used for reverse-engineering a specific message definition from a WSDL file, or when several possible root elements exist in a XSD file. ro true | false If true, the XML file is opened in read only mode. s schema name Name of the relational schema where the XML file will be loaded.This value must match the one set for the physical schema attached to this data server. This parameter is mandatory. cs true | false Load the XML file in case sensitive or insensitive mode. For case insensitive mode, all element names in the DTD file should be distinct Ex: Abc and abc in the same file are banned. The case sensitive parameter is a permanent parameter for the schema. It CANNOT be changed after schema creation. Please note that when opening the XML file in insensitive mode, case will be preserved for the XML file. JMSXML_ ROWSEPARA TOR 5B23245D Hexadecimal code of the string used as a line separator line break for different XML contents. Default value is 5B23245D which corresponds to the string []. JMS_ DESTINATIO N JNDI Queue name or Topic name JNDI Name of the JMS Queue or Topic. This parameter is mandatory. tna boolean true|false Transform Non Ascii. Set to false to keep non-ascii characters. Default is true. This parameter is not mandatory. 25-6 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator