Setting up JMS in IBM WebSphere Application Server

If you attach the Text Over JMS binding by using IBM® InfoSphere® Information Services Director in the IBM InfoSphere Information Server console, you must first configure messaging queues or topics within IBM WebSphere® Application Server. Queues and topics are the virtual places where messages are exchanged.

Before you begin

You must be using the Network Deployment edition of WebSphere Application Server to perform this task.

About this task

These topics document a simple example of creating JMS request and response queues or topics. Refer to the IBM WebSphere Application Server, Version 8.5 information center for details on setting up more complex configurations.

Creating a service integration bus in IBM WebSphere Application Server
The first step in setting up JMS in IBM WebSphere Application Server is to create the service integration bus, the virtual place where messages are exchanged. A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
Adding IBM InfoSphere Information Server as a member of the service integration bus
After you create a service integration bus, you must add IBM InfoSphere Information Server as a member. Bus members are the servers and clusters that have been added to the bus.
Defining queues and topics in the service integration bus
Queues and topic spaces are the two types of destinations within a bus. After you add IBM InfoSphere Information Server as a member of the bus, choose queue for point-to-point messaging, or topic space for publish and subscribe messaging. A bus destination is a virtual place within a service integration bus, to which applications attach as producers, consumers, or both to exchange messages.
Associating JMS queues and topics with the service integration bus queues and topic spaces
After you define the type of destination for your messages in the service bus, you must associate those queues or topic spaces with Java Message Service (JMS) queues or topics. A JMS queue is used as a destination for point-to-point messaging. A JMS topic is used for JMS publish and subscribe messaging. Use JMS destination administrative objects to manage JMS queues or topics for the default messaging provider.
Creating a JMS connection factory
After you associate the bus queues or topic spaces to the JMS queues or topics, you must create a Java Message Service (JMS) connection factory. A JMS connection factory is used to create connections to the associated JMS provider of JMS queues for point-to-point messaging, or JMS topics for publish and subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.
Creating a JMS activation specification
After you create the Java Message Service (JMS) connection factory, you must create the JMS activation specification. A JMS activation specification is associated with one or more message-driven beans (MDB) and provides the configuration necessary for them to receive messages.