Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | Application Server Support | Application Server Support When You Use webMethods Broker as a JMS Provider | Application Server Usage Notes
 
Application Server Usage Notes
These technical considerations apply when you use webMethods Broker as a JMS provider with any of the supported application servers.
*Tuning the configuration properties when you use webMethods Broker as a JMS provider. Adjusting these properties, which are located in the WmJMSConfig class, may be useful in the situations described below. For more information, see Properties Specific to webMethods Broker Used as a JMS Provider and the webMethods Broker API for JMS Reference for the WmJMSConfig class.
*If you need multiple durable subscribers to share the same clientID, change the clientIDSharing setting as follows:
com.webmethods.jms.clientIDSharing=true
Sharing the clientID was allowed by default in releases prior to 6.5; however, in the current release, you must set this property for multiple durable subscribers to share the same clientID.
*To improve the response time for detecting disconnections between a Broker and a client:
com.webmethods.jms.broker.keepAliveTimeout=30
com.webmethods.jms.broker.keepAliveAttempts=100
com.webmethods.jms.broker.keepAliveInterval=30
com.webmethods.jms.keepAliveInterval=30
*Setting the Broker recover mode. The default setting for the Broker recover mode is restricted. When you use webMethods Broker as a JMS provider with application servers, it needs to be changed to global.
Use the JMSAdmin command-line tool (described in The JMSAdmin Command-Line Tool), or the Broker user interface in My webMethods to change the setting.
set recoverMode=global
For more information about setting the Broker recover mode with the JMSAdmin command-line tool, see Set RecoverMode. For information about setting the Broker recover mode through My webMethods, see Administering webMethods Broker .