Configuring JMS resources for the synchronous SOAP over JMS endpoint listener

Configure the synchronous SOAP over Java™ Message Service (JMS) endpoint listeners to use a JMS provider - either the default messaging provider, or another provider such as the WebSphere® MQ messaging provider - to pass SOAP messages over JMS.

Before you begin

If you have not already done so, choose a JMS messaging provider.

About this task

If you are defining a SOAP over JMS endpoint listener, you must first configure the following JMS resources for your JMS provider:
Note:
Listener ports are stabilized. For more information, read the article on stabilized features. Wherever possible, you should deploy your endpoint listener application to use an activation specification. You can use only activation specifications with the default messaging provider; you can use either activation specifications or listener ports with the WebSphere MQ messaging provider.

Procedure

  1. Use the administrative console to create and configure queue connection factories and queue destinations.

    For more information about how to do this for your messaging provider, see the related links.

    Create a queue connection factory and a queue destination for each endpoint listener that you plan to configure. For example, if you plan to configure both of the SOAP over JMS endpoint listeners that are supplied with WebSphere Application Server, create two connection factories (one for each endpoint listener) and two queues. The JMS resources and JNDI names that the supplied SOAP over JMS endpoint listeners expect by default are provided in the following table. If you use different resources and names in this step, then change the defaults when you subsequently configure the endpoint listener.

    Table 1. JMS resources and expected JNDI names
    JMS resource default JNDI name (endpoint listener 1) default JNDI name (endpoint listener 2) queue name (endpoint listener 1) queue name (endpoint listener 2)
    JMS queue connection factory jms/SOAPJMSFactory1 jms/SOAPJMSFactory2 Not required Not required
    JMS queue destination jms/SOAPJMSQueue1 jms/SOAPJMSQueue2 User defined (for example: SOAPJMSDestQueue1) User defined (for example: SOAPJMSDestQueue2)
  2. Configure the underlying destination for each JMS queue.

    Configure these destinations as described in the documentation for your JMS provider. If you are using the default messaging provider, use the administrative console to add the two new queue names specified in the previous table as destinations for your application server as described in Creating a queue for point-to-point messaging. The identifier for the destination should match that defined by the user as the queue name in the previous table.

  3. Configure the deployment details for the application.
    If you are using activation specifications, use the administrative console to create and configure the activation specifications as described in Configuring an activation specification for the default messaging provider or Creating an activation specification for the WebSphere MQ messaging provider by using the Create Activation Specification wizard. Create two activation specifications, one for each endpoint listener. The default JMS resources and associated names that the synchronous SOAP over JMS endpoint listeners expect are provided in the following table. However, you can use any JNDI name for the activation specification, provided that the EAR file has the same JNDI reference in the administrative console "Binding enterprise beans to listener port names or activation specification JNDI names" panel. If you use different resources and names in this step, change the defaults when you subsequently configure the endpoint listener. You must also stop then restart the application server.
    Table 2. Default JMS resource and associated name expected
    JMS resource default JNDI name (endpoint listener 1) default JNDI name (endpoint listener 2) destination JNDI name (endpoint listener 1) destination JNDI name (endpoint listener 2)
    activation specification eis/SOAPJMSChannel1 eis/SOAPJMSChannel2 jms/SOAPJMSQueue1 jms/SOAPJMSQueue2
    If you are using listener ports with any supported JMS provider, use the administrative console to create and configure the listener ports in the message listener service as described in Creating a new listener port. Create two listener ports (one for each endpoint listener). The default JMS resources and associated names that the supplied SOAP over JMS endpoint listeners expect are provided in the following table. If you use different resources and names in this step, then change the defaults when you subsequently configure the endpoint listener.
    Table 3. Default JMS resources and expected names
    JMS resource default name (for use with SOAP over JMS endpoint listener 1) default name (for use with SOAP over JMS endpoint listener 2)
    listener port SOAPJMSPort1 SOAPJMSPort2
    connection factory jms/SOAPJMSFactory1 jms/SOAPJMSFactory2
    destination jms/SOAPJMSQueue1 jms/SOAPJMSQueue2
  4. Save your changes to the master configuration.
  5. Bind the JMS resources by stopping then restarting the application server.

What to do next

You are now ready to create a new SOAP over JMS endpoint listener configuration.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tjw_epl_soapjms
File name: tjw_epl_soapjms.html