Use this
task to define a third-party non-JCA messaging
provider to WebSphere® Application Server. You might want to do this, for example, if you have existing investments.
Before you begin
Before you define a third-party non-JCA messaging provider,
you might want to check whether your requirement can be met by the
default messaging provider or the WebSphere MQ
messaging provider that are supplied with WebSphere Application
Server. To choose the provider that is best suited to your needs,
see Choosing a messaging provider.
To work with message-driven beans, the third-party non-JCA messaging provider must include Application Server Facility (ASF), an optional feature that is part of the JMS Version 1.1 specification.
About this task
You can configure any third-party non-JCA messaging provider that supports the JMS Version 1.1 unified connection factory.
To administer a third-party non-JCA messaging provider, you use the client that is supplied by the third party. You use the administrative console to administer the connection factories and destinations that are within WebSphere Application Server, but you cannot use the administrative console to administer the JMS provider itself, or any of its resources that are outside of WebSphere Application Server.
Procedure
- Start the administrative console.
- In the navigation pane, click . The existing messaging providers are displayed, including
the default messaging provider and the WebSphere MQ
messaging provider.
- To define a new
third-party non-JCA messaging provider,
click New in the content pane. Otherwise, to
change the definition of an existing messaging provider, click the
name of the provider.
- 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 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 can
now configure JMS resources for your messaging provider,
as described in
Configuring JMS resources for a third-party non-JCA messaging provider.