[V5.1 and later]Installing the synchronous SOAP over JMS channel

 

Overview

The synchronous SOAP over Java Messaging Service (JMS) channels 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 channels, complete the following steps:

  1. 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 in Configuring JMS provider resources.Create two connection factories (one for each channel) and two destinations. The JMS resources and JNDI names that the synchronous SOAP over JMS channels 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 channel EAR files.

    JMS resource default JNDI name (channel 1) default JNDI name (channel 2)
    connection factory jms/SOAPJMSFactory1 jms/SOAPJMSFactory2
    destination jms/SOAPJMSQueue1 jms/SOAPJMSQueue2


  3. (Optional)   If you are using embedded messaging, use the administrative console to add the two new destinations to the list of JMS Server destination names for your appserver as described in Managing WebSphere internal JMS servers. Ensure that the Initial State is started.

  4. Use the administrative console to create and configure listener ports in the message listener service for your appserver as described in Adding a new listener port. Create two listener ports (one for each channel). The default JMS resources and associated names that the synchronous SOAP over JMS channels 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 channel EAR files.

    JMS resource default name (for use with SOAP over JMS channel 1) default name (for use with SOAP over JMS channel 2)
    listener port SOAPJMSPort1 SOAPJMSPort2
    connection factory jms/SOAPJMSFactory1 jms/SOAPJMSFactory2
    destination jms/SOAPJMSQueue1 jms/SOAPJMSQueue2


  5. Use the administrative console to create a new URL provider for your appserver as described in URL provider settings.Enter the property values provided in the following table:

    URL provider property value
    Name JMSHandler
    Stream Handler Class Name com.ibm.ws.protocol.Handler
    Protocol jms


  6. Install the synchronous SOAP over JMS channel applications (wsgwsoapjms1.ear and wsgwsoapjms2.ear) as described in the next to last step of Installing the gateway into an appserver that is part of a deployment manager cell and Installing the gateway into a stand-alone appserver.

  7. (Optional)   If you want to change the default values for listener port and connection factory for the synchronous SOAP over JMS channel applications, modify the installed applications by completing the following steps for each channel application:

    1. In the administrative console navigation pane, click Applications > Enterprise Applications. A list of all installed enterprise applications is displayed.

    2. Click the name of the channel application (for example SOAPJMSChannel1). Configuration details for the application are displayed.

    3. Scroll down through the configuration details to the Additional Properties pane, then click Provide Listener Ports for Messaging Beans. The Binding Enterprise Beans to Listener Port Name pane is displayed.

    4. Change the listener port value from (for example) SOAPJMSPort1 to the value that you configured in the message listener service in a previous step, then click OK to return to the Additional Properties pane.

    5. In the Additional Properties pane, click Map resource env entry references to resources.The Mapping Resource Environment References to Resources pane is displayed.

    6. Change the connection factory value from (for example) jms/SOAPJMSFactory1 to the value that you configured in the message listener service in a previous step, then click OK to return to the Additional Properties pane.

    7. Scroll up through the configuration details to the Messages pane, then click Save.The Save to Master Configuration pane is displayed.

    8. In the Save to Master Configuration pane, click Save. The changes have been committed and installed.

    9. Stop then restart the appserver.

 

What to do next

You are now ready to Deploy the synchronous SOAP over JMS channels to the gateway.


Related tasks
Installing the gateway-supplied channels
Related reference
Web services gateway - Channel deployment details