Configure JMS resources in WebSphere Application Server

To configure JMS resources in WebSphere Application Server, we can either use the administrative console or wsadmin commands.


Java Message Service (JMS) applications typically rely on externally configured objects which describe how the application connects to its JMS provider and the destinations it accesses. JMS applications use the Java Naming Directory Interface (JNDI) to access the following types of object at runtime:

  • Activation specifications (used by Java EE application servers)
  • Unified connection factories (with JMS 1.1, domain-independent (unified) connection factories are preferred to domain-specific queue connection factories and topic connection factories)
  • Topic connection factories (used by JMS 1.0 applications)
  • Queue connection factories (used by JMS 1.0 applications)
  • Queues
  • Topics

Through the IBM MQ messaging provider in WebSphere Application Server, Java Message Service (JMS) messaging applications can use the IBM MQ system as an external provider of JMS messaging resources. To enable this approach, you configure the IBM MQ messaging provider in WebSphere Application Server to define JMS resources for connecting to any queue manager on the IBM MQ network.

We can use WebSphere Application Server to configure IBM MQ resources for applications (for example queue connection factories) and to manage messages and subscriptions associated with JMS destinations. You administer security through IBM MQ.

  • Configure JMS resources using the administrative console
    We can use the WebSphere Application Server administrative console to configure activation specifications, connection factories and destinations for the IBM MQ JMS provider.
  • Configure JMS resources using wsadmin scripting commands
    We can use WebSphere Application Server wsadmin scripting commands to create, modify, delete or show information about JMS activation specifications, connection factories, queues and topics. We can also display and manage the settings for the IBM MQ resource adapter.
  • Use JMS 2.0 shared subscriptions
    In WebSphere Application Server traditional Version 9.0, we can configure and use JMS 2.0 shared subscriptions with IBM MQ Version 9.0.
  • Use JMS 2.0 ConnectionFactory and Destination Lookup properties
    In WebSphere Application Server traditional Version 9.0, the ConnectionFactoryLookup and DestinationLookup properties of an activation specification can be provided with a JNDI name of an administered object to be used in preference to the other activation specification properties.

Parent topic: Configure JMS resources


Related information


WebSphere Application Server topics