Administering JMS Import bindings

You can administer JMS Imports bindings to tune, or set special features of the resource. The administrative tasks are performed using the WebSphere® administrative console.

Before you begin

You must have permission to make and save changes to the profile on the administrative console.

Why and when to perform this task

The JMS Import must be installed as part of a Service Component Architecture (SCA) application in your WebSphere Process Server profile.

Steps for this task

  1. Open the default messaging provider settings panel in the administrative console.

    Expand JMS Providers, click Default Messaging (Resources > JMS Providers > Default Messaging).

  2. Set the scope to Server. The resources your JMS Import uses are created at the Server level. Set the Scope to Server in order to view and administer these resources.
    Note: If you created the resources for the JMS Import, you might have done so at a different scope level, set the scope accordingly.
  3. Optional: Administer JMS connection factories (Resources > JMS Providers > Default Messaging > JMS connection factory).

    Click on JMS connection factory, in the list of connection factories. This panel shows a list of JMS connection factories with a summary of their configuration properties. Click on the JMS connection factory that you want to administer, or click New to create a new connection factory.

    Use the subsequent panel to browse or change the configuration properties of the selected JMS connection factory for use with the default messaging JMS provider. These configuration properties control how connections are created to associated JMS queues and topics.

    You set these properties in the bindings for the resource reference of the application. If you do not want to modify the bindings for an existing application, locate this connection factory in the J2C panels where you can find these properties.

    A JMS connection factory is used to create connections to the associated JMS provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.

  4. Optional: Administer JMS queue connection factories (Resources > JMS Providers > Default Messaging > JMS queue connection factory).

    Click on JMS queue connection factory, in the list of connection factories. This panel shows a list of JMS queue connection factories with a summary of their configuration properties. To administer a queue connection factory click on it, or click New to create a new one.

    Use the subsequent panel to browse or change the configuration properties of the selected JMS queue connection factory for use with the default messaging JMS provider. These configuration properties control how connections are created to associated JMS queues.

    You set these properties in the bindings for the resource reference of the application. If you do not want to modify the bindings for an existing application, locate this connection factory in the J2C panels where you can find these properties.

    A JMS queue connection factory is used to create connections to the associated JMS provider of JMS queues, for point-to-point messaging. Use queue connection factory administrative objects to manage JMS queue connection factories for the default messaging provider.

  5. Optional: Administer JMS topic connection factories (Resources > JMS Providers > Default Messaging > JMS topic connection factory).

    Click on JMS topic connection factory, in the list of connection factories. This panel shows a list of JMS topic connection factories with a summary of their configuration properties. Click on the JMS topic connection factory that you want to administer, or click New to create a new connection factory.

    Use the subsequent panel to browse or change the configuration properties of the selected JMS topic connection factory for use with the default messaging JMS provider. These configuration properties control how connections are created to associated JMS topics.

    You set these properties in the bindings for the resource reference of the application. If you do not want to modify the bindings for an existing application, locate this connection factory in the J2C panels where you can find these properties.

    A JMS topic connection factory is used to create connections to the associated JMS provider of JMS topics, for publish/subscribe messaging. Use topic connection factory administrative objects to manage JMS topic connection factories for the default messaging provider.

  6. Optional: Administer JMS queues (Resources > JMS Providers > Default Messaging > JMS queue).

    Click on JMS queue, in the list of destinations. This panel shows a list of JMS queues with a summary of their configuration properties. Click on the JMS queue that you want to administer, or click New to create a new JMS queue.

    Use the subsequent panel to change or enter settings for the JMS queue.

    A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.

  7. Optional: Administer JMS topics (Resources > JMS Providers > Default Messaging > JMS topic).

    Click on JMS topic, in the list of destinations. This panel shows a list of JMS topics with a summary of their configuration properties. Click on the JMS topic that you want to administer, or click New to create a new JMS topic.

    Use the subsequent panel to change or enter settings for the JMS topic.

    A JMS topic is used as a destination for publish/subscribe messaging. Use topic destination administrative objects to manage JMS topics for the default messaging provider.

  8. Optional: Administer JMS activation specifications (Resources > JMS Providers > Default Messaging > JMS activation specification).

    Click on JMS activation specification, in the list of activation specifications. The panel shows a list of JMS activation specifications with a summary of their configuration properties.

    A JMS activation specification is associated with one or more message-driven beans (MDB) and provides the configuration necessary for them to receive messages. A JMS activation specification is used to provide configuration information when a JMS endpoint (message-driven bean application) is deployed and activated against the default messaging provider.

    Click on the JMS activation specification that you wish to administer or click New to create a new JMS activation specification.

What to do next

Save your changes to the master profile and if necessary restart WebSphere Process Server.

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)