Configuring an OJMS Message Service Provider

OJMS Destination and Connection Factory Names

The actual JNDI names for the JMS destination and connection factory depend on your OJMS installation as shown in Table 23-2.

The values for the variables in Table 23-2 are defined as follows:

• <ProviderName>: the JNDI name of the data source that is providing OJMS service (see "Identify the JNDI Name of the Oracle AQ JMS Data Source")

• <QName>: the name of the queue you created in the database (see step 3 b in "Installing and Configuring the OJMS Provider").

• <QCFName>: the name of the queue connection factory. You may specify any arbitrary name.

• <TName>: the name of the topic you created in the database (see step 3 b in "Installing and Configuring the OJMS Provider").

• <TCFName>: the name of the topic connection factory. You may specify any arbitrary name.

Installing and Configuring the OJMS Provider

1. You or your DBA must install Oracle AQ according to the Oracle Streams Advanced Queuing User's Guide and Reference. and generic database manuals.

2. You or your DBA should create an RDBMS user through which the MDB connects to the database and grant this user appropriate access privileges to perform OJMS operations.

   The privileges that you need depend on what functionality you are requesting. Refer to the Oracle Streams Advanced Queuing User's Guide and Reference. for more information on privileges necessary for each type of function.

   The following example creates jmsuser, which must be created within its own schema, with privileges required for Oracle AQ operations. You must be a SYS DBA to execute these statements.

   DROP USER jmsuser CASCADE ;
   
   GRANT connect, resource,AQ_ADMINISTRATOR_ROLE TO jmsuser IDENTIFIED BY jmsuser ;
   GRANT execute ON sys.dbms_aqadm  TO  jmsuser;
   GRANT execute ON sys.dbms_aq     TO  jmsuser;
   GRANT execute ON sys.dbms_aqin   TO  jmsuser;
   GRANT execute ON sys.dbms_aqjms  TO  jmsuser;
   
   connect jmsuser/jmsuser;
   
   

   You may need to grant other privileges, such as two-phase commit or system administration privileges, based on what the user needs. See the JTA chapter in the Oracle Containers for J2EE Services Guide for the two-phase commit privileges.

3. You or your DBA should create the tables and queues to support the JMS Destination objects.

   Refer to the Oracle Streams Advanced Queuing User's Guide and Reference. for more information on the DBMS_AQADM packages and Oracle AQ messages types.

   1. Create the tables that handle the JMS Destination (queue or topic).

      In OJMS, both topics and queues use a queue table. The rpTestMdb JMS example creates a single table: rpTestQTab for a queue.

      To create the queue table, execute the following SQL:

      DBMS_AQADM.CREATE_QUEUE_TABLE(
              Queue_table            => 'rpTestQTab',
              Queue_payload_type     => 'SYS.AQ$_JMS_MESSAGE',
              sort_list => 'PRIORITY,ENQ_TIME',
              multiple_consumers  => false,
              compatible             => '8.1.5');
      
      

      The multiple_consumers parameter denotes whether there are multiple consumers or not; thus, is always false for a queue and true for a topic.

   2. Create the JMS Destination. If you are creating a topic, you must add each subscriber for the topic. The rpTestMdb JMS example requires a single queue—rpTestQueue.

      The following creates a queue called rpTestQueue within the queue table rpTestQTab. After creation, the queue is started.

      DBMS_AQADM.CREATE_QUEUE(
            Queue_name          => 'rpTestQueue',
            Queue_table         => 'rpTestQTab');
      
      DBMS_AQADM.START_QUEUE(
            queue_name         => 'rpTestQueue');
      
      

      If you wanted to add a topic, then the following example shows how you can create a topic called rpTestTopic within the topic table rpTestTTab. After creation, two durable subscribers are added to the topic. Finally, the topic is started and a user is granted a privilege to it.

      
      

      Note: Oracle AQ uses the DBMS_AQADM.CREATE_QUEUE method to create both queues and topics.

      
      

      DBMS_AQADM.CREATE_QUEUE_TABLE(
              Queue_table            => 'rpTestTTab',
              Queue_payload_type     => 'SYS.AQ$_JMS_MESSAGE',
              multiple_consumers  => true,
              compatible             => '8.1.5');
      DBMS_AQADM.CREATE_QUEUE( 'rpTestTopic', 'rpTestTTab');
      DBMS_AQADM.ADD_SUBSCRIBER('rpTestTopic',                          sys.aq$_agent('MDSUB', null, null));
      DBMS_AQADM.ADD_SUBSCRIBER('rpTestTopic',                          sys.aq$_agent('MDSUB2', null, null));
      DBMS_AQADM.START_QUEUE('rpTestTopic');
      

      
      

      Note: The names defined here must be the same names used to define the queue or topic in the orion-ejb-jar.xml file.

      
      

Configuring data-sources.xml

Configure a data source for the database where the OJMS provider is installed. The JMS topics and queues use database tables and queues to facilitate messaging. The type of data source you use depends on the functionality you want.

<data-source
  class="oracle.j2ee.sql.DriverManagerDataSource"
  name="OracleDS"
  location="jdbc/CartEmulatedOracleCoreDS"
  xa-location="jdbc/xa/CartEmulatedOracleXADS"
  ejb-location="jdbc/CartEmulatedDS"
  connection-driver="oracle.jdbc.driver.OracleDriver"
  username="myuser"
  password="mypasswd"
  url="jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mysun)
   (PORT=5521))(CONNECT_DATA=(SID=orcl)))"
  inactivity-timeout="30"
/>

<data-source
  class="oracle.j2ee.sql.DriverManagerDataSource"
  name="OracleDS"
  location="jdbc/emulatedOracleCoreDS"
  xa-location="jdbc/xa/emulatedOracleXADS"
  ejb-location="jdbc/emulatedDS"
  connection-driver="oracle.jdbc.driver.OracleDriver"
  username="jmsuser"
  password="jmsuser"
  url="jdbc:oracle:thin:@myhost.foo.com:1521:mydb"
/>

<resource-provider class="oracle.jms.OjmsContext" name="myProvider">
  <description> OJMS/AQ </description>
  <property name="datasource" value="jdbc/emulatedDS"></property>
</resource-provider>