Use this task to define a new messaging provider to WebSphere Process Server,
for use instead of the default messaging provider or instead of WebSphere
MQ, if you have this installed.
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.
Why and when to perform this task
To define a new generic messaging provider to
WebSphere Process Server,
use the administrative console to complete the following steps:
Steps for this task
- In the navigation pane, click JMS Providers > Generic.
This displays the existing generic messaging providers in the content pane.
- 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.
- 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.
- Optional: Click Apply. This
enables you to specify additional properties.
- 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.
- Click OK.
- Save the changes to the master configuration.
- To have the changed configuration take effect, stop then restart
the application server.
What to do next
You are now in position to configure JMS resources for the generic
messaging provider.