Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | Application Server Support | Application Server Support When You Use webMethods Broker as a JMS Provider | Sample IBM WebSphere Application Server Configuration through JCA | Configuring IBM WebSphere Application Server 7.0
 
Configuring IBM WebSphere Application Server 7.0
You can configure the WebSphere Application Server 7.0 to use webMethods Broker as a JMS provider, by using the WebSphere console to configure webMethods Broker as a generic JMS provider.
For more information, refer to the topic “Configuring a Generic JMS Provider” in the WebSphere 7.0 documentation.
*To configure the IBM WebSphere Application Server 7.0
1. Launch the WebSphere console on the browser and log in to the server.
2. Add the webMethods Resource Adapter for JMS to the WebSphere Application Server. To do this, go to Resources > Resource Adapters and click Install RAR. In the RAR list, select webm-jmsra.rar.
3. On the Resource Adapters page, select webMethods Resource Adapter for JMS from the Resource Adapter list.
4. Configure the resource adapter as follows:
a. If the application server supports XA, open the custom properties page for the resource adapter and set the supportsXA property to true.
b. Create a new Activation Specification. Open the J2C Activation Specification page and click New. Provide a name for the activation specification that will be used by the WebSphere Application Server and click Apply.
a. On the J2C Activation Specification page, click Custom Properties.
b. If the application server supports XA, set the supportsXA property to true.
c. Set the destination type property to javax.jms.Topic.
d. Enter a destination property name.
e. If you use JNDI, specify the following additional settings:
Parameter
Specify...
providerIntegrationMode
JNDI as the value.
jndiProperties
Your JNDI settings.
For example:
java.naming.factory.initial=com.webmethods.
jms.naming.WmJmsNamingCtxFactory,java.namin
g.provider.url=wmjmsnaming://Broker#1@local
host:6849/JMSAdminTest,com.webmethods.jms.
naming.clientgroup=admin
c. Set connectionFactoryJndiName to reflect the connection factory from which the MDB will receive messages.
d. Set destinationJndiName to reflect the destination from which the MDB will receive messages.
Use the above activation specification in MDB to receive and send messages to Broker.
5. Click Apply and OK.
6. Save your configuration in the console to apply changes to the master configuration.
7. Restart the WebSphere Application Server.