8.5.3 Managing a generic JMS provider
WAS supports the use of third-party JMS providers within its run time environment through the use a generic JMS provider. However, unlike the default messaging and WebSphere MQ JMS providers, a generic JMS provider must be defined to WAS before any JMS resources can be configured for that provider. Defining a generic JMS provider to WebSphere ensures that the JMS provider classes are available on the appserver classpath at run time.
A generic JMS provider is recommended in the following situations:
| -
| A non-WebSphere MQ messaging system already exists in the environment, and into which the WebSphere installation is required to integrate directly.
|
| -
| A non-WebSphere MQ JMS provider supports functionality that is not available using the default messaging or WebSphere MQ JMS providers, and which would be useful for the user's messaging environment.
|
|
WAS also supports the use of third-party JMS providers that are implemented as J2EE Connector Architecture resource adapters. The JMS resources for such JMS providers are configured using the generic resource adapter configuration windows.
If the third-party JMS provider is not implemented as a J2EE Connector Architecture resource adapter, we recommend that it supports the JMS Application Server Facilities described in 8.2.12, Application Server Facilities.
|
|
