Define a third-party non-JCA messaging provider
Use this task to define a third-party non-JCA messaging provider to WebSphere Application Server. We might want to do this, for example, if we have existing investments.
Before we define a third-party non-JCA messaging provider, we might want to check whether your requirement can be met by the default messaging provider or the IBM MQ messaging provider that are supplied with WAS. To choose the provider that is best suited to our needs, see Choose 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.
We 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, we use the client supplied by the third party. We use the administrative console to administer the connection factories and destinations that are within WAS, but we cannot use the administrative console to administer the JMS provider itself, or any of its resources that are outside of WAS.
Tasks
- Start the administrative console.
- In the navigation pane, click...
Resources > JMS->JMS providers. The existing messaging providers are displayed, including the default messaging provider and the IBM 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. We can specify other properties, as described in a later step.
- Name
- The name by which this messaging provider is known for administrative purposes within WAS.
- 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 us to specify additional properties.
- Optional: Specify other properties for the messaging provider.
Under Additional Properties, we can use the Custom Properties link to specify custom properties for our 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
We can now configure JMS resources for our messaging provider, as described in Configure JMS resources for a third-party non-JCA messaging provider.
List JMS resources for a third-party non-JCA messaging provider Configure JMS resources for a third-party non-JCA messaging provider JMS provider settings JMS provider settings