InfoCenter Home >
4: Developing applications >
4.6: Java Technologies >
4.6.3: Java Message Service (JMS) overview >
4.6.3.3: Support of Java Message Service resources

4.6.3.3: Support of Java Message Service resources

Unlike other J2EE resources that are typically objects that run in and are part of the application server, JMS resources are external to WebSphere Application Server. This means administrators must first use a JMS provider's administration tool to create the connection factories and destinations, and to assign these objects with correct configuration attributes. After this step is completed, administrators can then use WebSphere Application Servers' administrative client to create JMS resource objects to reference the external objects.

In WebSphere Application Server Version 4.0, the MQSeries product is defined as the default JMS provider. However, since MQSeries is not shipped with WebSphere Application Server, this JMS provider is not installed on any node.
Since this provider is predefined, after you install the MQSeries product, you only need to go to the Nodes tab of the properties editor for the Provider to install it on the desired nodes.

The following steps describe how to implement JMS support in WebSphere Application Server:

  1. Configure a JMS provider. By default this will be the MQSeries product.
  2. Create the destination and connection factory with the JMS provider's admin tool.
    This will bind references to these objects in the JNDI namespace.
  3. Create corresponding JMS resources in WebSphere Application Server, declaring the location where they were bound by the JMS admin tool as an attribute.
    The RepositoryObject implementation for the resource binds the resource into the WebSphere Application Server namespace.
  4. Deploy the application, which resolves the JMS resource references with the JMS objects.
  5. Start the application server containing the application.
      At this point, the ResourceBinder object in the application server binds the JMS resource objects into the namespace.
  6. The application code performs a "lookup" on a JMS resource.
    The "lookup" finds the IndirectJNDILookup bound at the target WebSphere Application Server location, and uses it to perform a subsequent lookup of the actual resource in the provider's namespace.

Go to previous article: Using the JMS publish/subscribe messaging approach Go to next article: Support for the use of MQSeries Java Message Service resources

 

 
Go to previous article: Using the JMS publish/subscribe messaging approach Go to next article: Support for the use of MQSeries Java Message Service resources