Configuring the integration node to enable 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 configurable services
properties that are associated with that vendor. The following table
shows the properties that have been added to the configurable service
for BEA WebLogic.
JMS provider | Property | Purpose | Default value |
---|---|---|---|
BEA_WebLogic | proprietaryAPIHandler | The name of the IBM supplied Java class to interface with a JMS provider's proprietary API. | com.ibm.broker.apihandler. BEAWebLogicAPIHandler |
proprietaryAPIAttr1 | The Initial Context Factory class name for the vendor | weblogic.jndi. WLInitialContextFactory | |
proprietaryAPIAttr2 | The URL of the WebLogic bindings | URL JNDI bindings | |
proprietaryAPIAttr3 | The DNS name of the JMS server | Server name |
In the list of JMS provider configurable services, the name of the IBM supplied Java class is set to the default value for the proprietaryAPIHandler property. Typically, you do not need to change this value, unless you are instructed to do so by an IBM Service team representative.