WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Defining a generic messaging provider

Use this task to define a new messaging provider to WebSphere Application Server, for use instead of the default messaging provider or a WebSphere MQ as a messaging provider.

Before you begin

Before starting this task, you should have installed and configured the messaging provider and its resources by using the tools and information provided with the messaging provider.

About this task

To define a new generic messaging provider to WebSphere Application Server, use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click JMS Providers > Generic. This displays the existing generic messaging providers in the content pane.
  2. To define a new generic messaging provider, click New in the content pane. Otherwise, to change the definition of an existing messaging provider, click the name of the provider. This displays the properties used to define the messaging provider in the content pane.
  3. Specify the following required properties. You can specify other properties, as described in a later step.
    Name
    The name by which this messaging provider is known for administrative purposes within IBM WebSphere Application Server.
    External initial context factory
    The Java classname of the initial context factory for the JMS provider.
    External provider URL
    The JMS provider URL for external JNDI lookups.
  4. Optional: Click Apply. This enables you to specify additional properties.
  5. Optional: Specify other properties for the messaging provider.

    Under Additional Properties, you can use the Custom Properties link to specify custom properties for your initial context factory, in the form of standard javax.naming properties.

  6. Click OK.
  7. Save the changes to the master configuration.
  8. To have the changed configuration take effect, stop then restart the application server.

What to do next

You can now configure JMS resources for the generic messaging provider, as described in Configuring JMS resources for a generic messaging provider.



Related tasks
Configuring JMS resources for a generic messaging provider
Related information
JMS provider settings
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tmj_instp.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)