WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring JMS resources for the synchronous SOAP over JMS endpoint listener

Why and when to perform this task

The synchronous SOAP over Java Message Service (JMS) endpoint listeners 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. To install and configure the JMS provider, then install the synchronous SOAP over JMS endpoint listeners, complete the following steps:

Steps for this task

  1. Optional: If you are not using the default messaging provider, install a JMS provider. You might have already installed a JMS provider when you installed WebSphere Application Server. If not, install one now as described in Installing and configuring a JMS provider.
  2. Use the administrative console to create and configure queue connection factories and queue destinations as described, for the most common JMS providers, in topics available from within Using asynchronous messaging. Create two connection factories (one for each endpoint listener) and two queues. The JMS resources and JNDI names that the synchronous 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 EAR files.
    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)
  3. Configure the underlying destination for each JMS queue.

    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.

    Otherwise, configure these destinations as described in the documentation for your JMS provider.

  4. 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, 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 EAR files. You must also stop then restart the application server.
    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 (including the default messaging 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 synchronous 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 EAR files.
    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
  5. Save your changes to the master configuration.
  6. Bind the JMS resources by stopping then restarting the application server.
You are now ready to install the synchronous SOAP over JMS endpoint listener applications (soapjmschannel1.ear and soapjmschannel2.ear) as described in Installing the SIBWS and endpoint listener applications.
Related concepts
Endpoint listeners and inbound ports - entry points to the service integration bus
Related tasks
Creating a new endpoint listener configuration
Modifying an existing endpoint listener configuration
Deleting endpoint listener configurations
Related reference
Endpoint listener configuration details

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjw_epl_soapjms.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)