Documente Academic
Documente Profesional
Documente Cultură
0
IBM Integration Bus, Version 10.0.0.19 Operating Systems: AIX, HP-Itanium, Linux, Solaris,
Windows, z/OS
You can configure the JMS nodes to communicate with Oracle AQ (Oracle 11g and above). This
communication requires an LDAP 3 compliant server to hold definitions for JNDI lookup by the
JMS nodes.
Procedure
1. Complete the following steps in Oracle AQ, referring to Oracle documentation for the
specific details of each step.
a. You must install the Oracle Internet Directory Server (OID) to host the JNDI
administered objects for Oracle AQ.
b Create the database tables to hold the JMS queues and topics
b. Create the database tables to hold the JMS queues and topics.
c. Create the JMS queues and topics and associate them with the tables created in
step 1b.
2. Add definitions for the JMS connections to the LDAP server to permit the integration node
JMS nodes to complete JND lookup and connect to the Oracle AQ server.
a. Register JMS connection factories with the OID LDAP server by using the
administrative tools provided by Oracle.
b. The following diagram describes the shape of the directory tree for JNDI
administered objects for Oracle AQ.
3. Copy the Oracle AQ JMS client JAR files to a local directory that is accessible by the
integration node.
4. Modify the JMSProviders configurable service for Oracle AQ; for example:
mqsichangeproperties MyBroker -c JMSProviders -o Oracle_AQ
-n jarsURL,
InitialContextFactory,
jndiBindingsLocation
-v location of the Oracle Jars,
com.sun.jndi.ldap.LdapCtxFactory,
j p p y,
ldap://LDAP_server_address:LDAP_listener_port
5. Configure the properties on the JMS Connection tab of the JMS node (input, output, or
reply node) as shown in the following example. For more information about these
properties, see JMSInput node.
For all nodes that refer to the JMSProviders configurable service, if this property is set
on the configurable service, it overrides the property that is set on the node.
For all nodes that refer to the JMSProviders configurable service, if this property is set
on the configurable service, it overrides the property that is set on the node.
Set the Connection factory name property. This name must be the fully qualified
path in the LDAP directory; for example:
cn=QCF,cn=oracledbconnections,cn=ORCL,cn=OracleContext,
ou=MyDept,o=MyCompany
Where
6. On the Basic tab, configure the JMS destinations (queue or topic) properties.
Set the Source queue property on the JMSInput node. This queue must be the fully
qualified path in the LDAP directory; for example:
cn=JMS.Queue,cn=oracleDBQueues,cn=ORCL,cn=OracleContext,
ou=MyDept,o=MyCompany
Where
7. Before the message flow starts, ensure that the JMS connection has been established by
using the Windows Event Viewer.
Related concepts
Connection to different JMS providers
Related tasks
Configuring the integration node to enable a JMS provider's proprietary API
Related reference
JMSInput node
mqsicreateconfigurableservice command
mqsichangeproperties command