WAS v8.5 > Deploy applications > Deploy client applications > Deploy a Java EE client application > Deploy a Java EE client application > Configure Java messaging client resources

Configure new JMS providers with the Application Client Resource Configuration Tool

We can create new JMS provider configurations for the Application Client. The Application Client makes use of a messaging service through the JMS interfaces.

During this task, you create new JMS provider configurations for the Application Client. The Application Client makes use of a messaging service through the JMS interfaces. A JMS provider provides two kinds of Java EE resources. One is a JMS connection factory, and the other is a JMS destination.

In a separate administrative task, install the JMS client on the client machine where your particular application client resides. The messaging product vendor must provide an implementation of the JMS client. For more information, see your messaging product documentation.

1. Start the Application Client Resource Configuration Tool and open the EAR file for which to configure the new JMS provider. The EAR file contents are displayed in a tree view.

2. From the tree, select the JAR file in which to configure the new JMS provider.

3. Expand the JAR file to view its contents.
4. Right-click Messaging Providers. Complete one of the following actions:
   • Right click the folder and select New.

   • On the menu bar, click Edit > New.

5. In the resulting property dialog, configure the JMS provider properties.

6. Click OK when finished.

7. Click File > Save on the menu bar to save your changes.

Example

The following code example illustrates how to configure JMS Provider, JMS Connection Factory and JMS Destination settings for application clients.

<resources.jms:JMSProvider xmi:id="JMSProvider_3" name="genericJMSProvider:name" 
description="genericJMSProvider:description" 
externalInitialContextFactory="genericJMSProvider:contextFactoryClass" 
externalProviderURL="genericJMSProvider:providerUrl"> <classpath>genericJMSProvider:classpath</classpath> <factories xmi:type="resources.jms:GenericJMSDestination" 
xmi:id="GenericJMSDestination_1" name="jmsDestination:name" 
jndiName="jmsDestination:jndiName" description="jmsDestination:description" 
externalJNDIName="jmsDestination:externalJndiName" type="QUEUE"> <propertySet xmi:id="J2EEResourcePropertySet_15"> <resourceProperties xmi:id="J2EEResourceProperty_17" name="jmsDestination:customName" 
value="jmsDestination:customValue"/> </propertySet> </factories> <factories xmi:type="resources.jms:GenericJMSConnectionFactory" 
xmi:id="GenericJMSConnectionFactory_1" name="jmsCF:name" jndiName="jmsCF:jndiName" 
description="jmsCF:description" userID="jmsCF:user" password="{xor}NTIsHBllMT4yOg==" 
externalJNDIName="jmsCF:externalJndiName" type="QUEUE"> <propertySet xmi:id="J2EEResourcePropertySet_16"> <resourceProperties xmi:id="J2EEResourceProperty_18" name="jmsCF:customName" 
value="jmsCF:customValue"/> </propertySet> </factories> <propertySet xmi:id="J2EEResourcePropertySet_17"> <resourceProperties xmi:id="J2EEResourceProperty_19" 
name="genericJMSProvider:customName" value="genericJMSProvider:customValue"/> </propertySet> </resources.jms:JMSProvider>

Required fields include:

• JMS Provider Properties page: name, and at least one protocol provider
• JMS Connection Factory Properties page: name, jndiName, destination type
• JMS Destination Properties page: name, jndiName, destination type

Special cases:

• The destination type must be QUEUE, or TOPIC.

Related

Start the Application Client Resource Configuration Tool and opening an EAR file

Reference:

Default Provider connection factory settings
Generic JMS destination settings for application clients
WebSphere MQ Provider queue connection factory settings for application clients
WebSphere MQ Provider queue destination settings for application clients
Generic JMS connection factory settings for application clients

+

Search Tips   |   Advanced Search