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 JMS provider that is embedded in WebSphere® Application Server, or another provider such as WebSphere MQ - 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:

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 connection factory and a queue for each endpoint listener that you plan to install. For example if you plan to install 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 install the endpoint listener applications.

    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 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 with the default messaging provider, use the administrative console to create and configure the activation specifications as described in Configuring a JMS activation specification for MDBs used by the default messaging provider. 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 install the endpoint listener applications. You must also stop then restart the application server.
    Table 2. Default JMS resource and expected associated name
    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 Adding 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 install the endpoint listener applications.
    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 install the synchronous SOAP over JMS endpoint listener applications (soapjmschannel1.ear and soapjmschannel2.ear) as described in Installing the SIBus Web services and endpoint listener applications.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 6:22:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-express-dist&topic=tjw_epl_soapjms
File name: tjw_epl_soapjms.html