Enabling a JMS provider's proprietary API
Some JMS providers provide an alternative interface to the standard JMS specification for particular JMS API calls. In these cases, IBM® supplies a Java™ class to interface with that proprietary API.
About this task
For example, BEA WebLogic uses a component called a Client Interposed Transaction Manager to allow a JMS client to obtain a reference to the XAResource that is associated with a user transaction.
If the WebSphere®
IBM Integration JMS nodes use BEA WebLogic as the JMS provider, and the
nodes must participate in a globally coordinated message flow, you must modify the policy properties
that are associated with that vendor (see JMS Providers policy (JMSProviders)). The following table shows
the properties that have been added to the policy for BEA WebLogic.
| JMS provider | Property | Purpose | Default value |
|---|---|---|---|
| BEA_WebLogic | Proprietary API handler | The name of the IBM supplied Java class to interface with a JMS provider's proprietary API. | com.ibm.broker.apihandler. BEAWebLogicAPIHandler |
| Proprietary API attribute 1 | The Initial Context Factory class name for the vendor | weblogic.jndi. WLInitialContextFactory | |
| Proprietary API attribute 2 | The URL of the WebLogic bindings | URL JNDI bindings | |
| Proprietary API attribute 3 | The DNS name of the JMS server | Server name |
In the list of JMS provider policy templates, the name of the IBM supplied Java class is set to the default value for the Proprietary API handler property. Typically, you do not need to change this value, unless you are instructed to do so by an IBM Service team representative.
Procedure
- Use the Policy editor to modify values of the properties for this JMS provider.
- If you have defined a JMS provider policy, set the value for the Proprietary API handler property manually.