Configuring an OracleAS JMS Message Service Provider

OracleAS JMS Destination and Connection Factory Names

The actual JNDI names for the JMS destination and connection factory are the ones you specify in the jms.xml file (see "Configuring jms.xml").

Table 23-1 lists the form of these names.

Configuring jms.xml

You configure OracleAS JMS options in the <OC4J_HOME>/j2ee/home/config/jms.xml file. In 10.1.3, the jms.xml is defined by the XML schema document (XSD) located at http://www.oracle.com/technology/oracleas/schema/jms-server-10_1.xsd.

Some of the options you can configure in the jms.xml file include:

• JMS Destination objects used by the MDB.

• Topic or queue in the jms.xml file to which the client sends all messages that are destined for the MDB.

• The name, location, and connection factory for either Destination type must be specified.

• If your MDB accesses a database for inquiries and so on, then you can configure the Data Source used. For information on data source configuration, see the Data Source chapter in the Oracle Containers for J2EE Services Guide.

• Path to a file in which OracleAS JMS events and errors are written.

Example 23-1 shows the jms.xml file configuration for an EJB 2.1 MDB that specifies a queue (named jms/Queue/rpTestQueue) that is used by the message-driven bean rpTestMdb (see Example 17-1). The queue connection factory is defined as jms/Queue/myQCF. In addition, a topic is defined named jms/Topic/rpTestTopic, with a connection factory of jms/Topic/myTCF.

<jms>
    <jms-server port="9128">
        <queue location="jms/Queue/rpTestQueue"></queue>
        <queue-connection-factory location="jms/Queue/myQCF"></queue-connection-factory>
        <topic location="jms/Topic/rpTestTopic"></topic>
        <topic-connection-factory location="jms/Topic/myTCF"></topic-connection-factory>
        <log>
             <!-- path to the log-file where JMS-events and errors are written -->
             <file path="../log/jms.log" />
        </log>
    </jms-server>
</jms>