Configuring Java Message Service for WebSphere Application Server

Java™ Message Service (JMS) is the messaging standard that is used to send and receive messages from queues. This process enables distributed communication with external systems in a loosely coupled, reliable, and asynchronous manner. The JMS configuration is application server-specific. You must configure JMS queues within the environment and make them accessible through the Java Naming Directory Interface (JNDI).

Before you begin

Configuration of JMS requires the understanding of buses, connection factories, queues, activation specifications, and stores. To set up the JMS configuration, you must be familiar with the configuration details for your application server.

About this task

Integration with external systems is supported through two message order processing mechanisms that use message queues. The first is sequential message processing, where the message order is guaranteed. The second is continuous message processing, where the messages are processed in parallel with message-driven beans (MDBs). The order in which messages are processed by this mechanism is not guaranteed.

If you are setting up an environment with an integration cluster that is connected to one or more external systems, you need to configure the JMS for queue-based integration. You need to create queues that are accessible by the user interface, cron, and integration clusters. The report cluster does not require JMS queues.

  1. Creating data source providers and data sources
    Before you create service integration buses, you must create a data source provider. If you choose to use a database for the queue data, you must also create a data source.
  2. Creating buses for Java Message Service
    A service integration bus consists of member application servers that share a common infrastructure to exchange information.
  3. Creating connection factories for Java Message Service
    Connection factories are used by the bus to create connections with Java Message Service (JMS) providers. Connection factories are stored in a Java Naming and Directory Interface (JNDI) namespace. You create a connection factory for each of the buses.
  4. Creating queue destinations for Java Message Service
    You need to create queue bus destinations for each service integration bus. After the queue bus destinations are created, the queues are created for each destination.
  5. Creating queues for Java Message Service
    You configure queues based on the queue destinations, which are used to send and receive messages to queues. A queue bus destination defines the bus name and queue name for the queue. You create one queue for each destination based on the default Java Message Service (JMS) provider.
  6. Creating Java Message Service activation specifications
    A Java Message Service (JMS) activation specification is associated with a queue that uses message-driven beans (MDBs) to consume messages from the queue. The activation specification provides the information necessary for the queue to receive messages. For each continuous queue that you create, set up the activation specification at the cell scope.
  7. Java Message Service configuration for WebSphere Application Server
    If you are setting up an environment with an integration cluster that is connected to one or more external systems, you need to configure the Java Message Service (JMS) for queue-based integration. You need to create queues that are accessible by the user interface, cron, and integration clusters. The report cluster does not require JMS queues.
Parent topic: Creating and deploying clusters in WebSphere Application Server
Previous topic: Creating clusters in WebSphere Application Server
Next topic: Deploying EAR files for clusters in WebSphere Application Server
Related concepts:
Java Message Service configuration for WebSphere Application Server