Integration Server 11.1 | Integration Server Administrator's Guide | Configuring Integration Server for JMS Messaging | Working with JMS Connection Aliases | Connecting to IBM webMethods Broker with the Native webMethods API
 
Connecting to IBM webMethods Broker with the Native webMethods API
When you use IBM webMethods Broker as the JMS provider, you can configure a JMS connection alias to use the native webMethods API. The native webMethods API provides a way to connect the Integration Server directly to the IBM webMethods Broker acting as the JMS provider. This eliminates the need for connection factories. Destinations can be created directly on the Broker and do not need to be stored in a JNDI provider. Consequently, you do not need to use a JNDI provider if all JMS connection aliases specify that the connection to IBM webMethods Broker should be made using the native webMethods API.
If you choose to use IBM webMethods Broker but do not want to connect natively (using the native webMethods API), you still need to use a JNDI provider.
Note:IBM webMethods Broker is deprecated. Consequently, the ability to configure JMS connection alias to use the native webMethods API is deprecated as well.