WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with a third-party messaging provider > Manage messaging with a third-party non-JCA messaging provider

Define a third-party non-JCA messaging provider

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 we have existing investments.

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 WAS. To choose the provider that is best suited to your 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 v1.1 specification. We can configure any third-party non-JCA messaging provider that supports the JMS v1.1 unified connection factory.

To administer a third-party non-JCA messaging provider, we use the client supplied by the third party. Use dmgr console to administer the connection factories and destinations that are within WAS, but we cannot use the dmgr console to administer the JMS provider itself, or any of its resources that are outside of WAS.

1. Start the dmgr console.
2. In the navigation pane, click Resources > JMS->JMS providers. The existing messaging providers are displayed, including the default messaging provider and the WebSphere MQ messaging provider.
3. 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.

4. 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.

5. Optional: Click Apply. This enables you to specify additional properties.

6. Optional: Specify other properties for the messaging provider.

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

7. Click OK.

8. Save the changes to the master configuration.
9. To have the changed configuration take effect, stop then restart the application server.

We can now configure JMS resources for the messaging provider, as described in Configure JMS resources for a third-party non-JCA messaging provider.

Related

List JMS resources for a third-party non-JCA messaging provider
Configure JMS resources for a third-party non-JCA messaging provider

Reference:

JMS provider settings
JMS provider settings

+

Search Tips   |   Advanced Search