For the purpose of this example, the AQ table will be run by the Oracle user "AQ_ADMIN/AQ_ADMIN" created on a database named "O920NT":

CONNECT system/manager CREATE USER aq_admin IDENTIFIED BY aq_admin DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp; ALTER USER aq_admin QUOTA UNLIMITED ON users; GRANT aq_administrator_role TO aq_admin; GRANT connect TO aq_admin; GRANT create type TO aq_admin; EXECUTE dbms_aqadm.grant_type_access('aq_admin'); CONNECT aq_admin/aq_admin BEGIN DBMS_AQADM.CREATE_QUEUE_TABLE( queue_table => 'JMS_TEXT' , queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE' , sort_list => '' , comment => '' , multiple_consumers => FALSE , message_grouping => DBMS_AQADM.NONE , non_repudiation => DBMS_AQADM.NONE , storage_clause => '' , compatible => '8.1' , primary_instance => '0' , secondary_instance => '0' ); COMMIT; END; / SHOW ERRORS BEGIN DBMS_AQADM.CREATE_QUEUE( queue_name => 'JOB_QUEUE' , queue_table => 'JMS_TEXT' , queue_type => DBMS_AQADM.NORMAL_QUEUE , max_retries => '5' , retry_delay => '0' , retention_time => '0' , comment => '' ); COMMIT; END; / SHOW ERRORS BEGIN DBMS_AQADM.START_QUEUE('aq_admin.job_queue', TRUE, TRUE); COMMIT; END; / SHOW ERRORS

NOTE:

• A special table named "JMS_TEXT" will be created in the designated schema in order to support the TextMessage type of JMS.
• A JMS Queue, named "JMS_QUEUE" will then be created using the "JMS_TEXT" table as its queue table.
• Lastly, the "JMS_QUEUE" queue will be started. (using its full schema.object notation)

Now, edit the data-sources.xml file located in $ORACLE_HOME/j2ee//config/data-sources.xml.
(e.g. $ORACLE_HOME/j2ee/home/config/data-sources.xml)

Add the following data-source, which should reference the schema containing the Queue defined above:

<data-source class="com.evermind.sql.DriverManagerDataSource" name="aq_admin_o920nt" location="jdbc/aq_admin_o920nt" xa-location="jdbc/xa/aq_admin_o920nt" ejb-location="jdbc/aq_admin_o920nt" connection-driver="oracle.jdbc.driver.OracleDriver" username="aq_admin" password="aq_admin" url="jdbc:oracle:thin:@bartman:1521:O920NT" inactivity-timeout="30" />

NOTE:

• The username, password and JDBC URL must be correctly set to reference the database and schema where the queue was setup.
• This entry will be mapped within the JNDI namespace at the path provided as the location attribute, which for this example is "aq_admin_o920nt". In this example application, the data source will be used as the target for SQL insert statements issued by the Message Driven Bean (MDB) to add rows to the "dataset" table. It will also be used by the listDataSet servlet to display the current contents of this table.

Insert the following definition into the "application.xml" file. This file is located in $ORACLE_HOME/j2ee//config directory.
(e.g. $ORACLE_HOME/j2ee/home/config/application.xml)

<resource-provider class="oracle.jms.OjmsContext" name="ojms"> <description>OJMS Context Using a datasource</description> <property name="url" value="jdbc:oracle:thin:aq_admin/aq_admin@bartman:1521:O920NT" /> <property name="username" value="aq_admin" /> <property name="password" value="aq_admin" /> </resource-provider>

NOTE:

• The class "oracle.jms.OjmsContext" implements the Oracle AQ-JMS functionality and the name attribute will be used later to reference Oracle AQ-JMS resources such as Queue's and Queue Connection Factories from the JNDI namespace.
• The value of the url, username and password attributes needs to be consistent with the database schema from step [1] where we create the Oracle AQ resources.