Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - Invocation framework (WSIF) > Administer WSIF > Enable a WSIF client to invoke a web service through JMS
Manage messaging with a third-party or (deprecated) V5 default messaging provider
For messaging between application servers, most requirements are best met by either the default messaging provider or the WebSphere MQ messaging provider. However, you can instead use a third-party messaging provider (that is, use another company's product as the provider). You might want to do this, for example, if we have existing investments. For backwards compatibility with earlier releases, there is also support for the V5 default messaging provider. If you are not sure which provider combination is best suited to your needs, see Types of messaging providers.
Enterprise applications in WAS can use asynchronous messaging through services based on JMS messaging providers and their related messaging systems. These messaging providers conform to the JMS v1.1 specification.
The choice of provider depends on what your JMS application needs to do, and on other factors relating to your business environment and planned changes to that environment.
Procedure
- Choose a third-party messaging provider.
To administer a third-party messaging provider, you use either the resource adaptor (for a Java EE Connector Architecture (JCA) 1.5-compliant messaging provider) or the client (for a non-JCA messaging provider) that is supplied by the third party. You use the console to administer the activation specifications, connection factories and destinations that are within WAS, but you cannot use the administrative console to administer the JMS provider itself, or any of its resources that are outside of WAS.
To use message-driven beans, third-party messaging providers must either provide an inbound JCA 1.5-compliant resource adapter, or (for non-JCA messaging providers) include Application Server Facility (ASF), an optional feature that is part of the JMS v1.1 specification.
To work with a third-party provider, choose one of the following options:
- Manage messaging with a third-party JCA 1.5-compliant messaging provider.
- Manage messaging with a third-party non-JCA messaging provider.
- Choose the (deprecated) V5 default messaging provider.
This deprecated provider is identical to the WAS v5 default provider. Only the name has changed. It provides backwards compatibility that enables WAS v6 or later applications to connect to WAS v5 resources in a mixed cell. It also allows WAS v5 applications to connect to WAS Version 6 or later resources in a mixed cell.
To configure and manage messaging to interoperate with WAS v5, see Maintain (deprecated) v5 default messaging resources.
Related
Manage messaging with a third-party JCA 1.5-compliant messaging provider
Manage messaging with a third-party non-JCA messaging provider
Maintain (deprecated) v5 default messaging resources
Introduction: Messaging resources
Manage messaging with the WebSphere MQ messaging provider
Manage message-driven beans
Secure messaging
Tune messaging
Troubleshoot messaging
Program to use asynchronous messaging
Manage messaging with the default messaging provider
Choosing a messaging provider