Running Business Processes and Composite Applications 10.5 | Running Business Processes and Composite Applications | Administering My webMethods Server | My webMethods Server Clustering | Modifying the Cluster Configuration | Configuring My webMethods Server to use the database for JMS communication | Considerations when using the database as a JMS provider
 
Considerations when using the database as a JMS provider
My webMethods Server clusters and CDS require the use of a JMS provider for synchronization between the nodes. The default JSM provider for synchronization between My webMethods Server nodes, and between My webMethods Server and Integration Server when using CDS, is Universal Messaging.
You can configure My webMethods Server to use the database as a JMS provider for cluster synchronization, as described in Configuring My webMethods Server to use the database for JMS communication. The following considerations apply when using the database as a JMS provider:
*My webMethods Server uses the production database for cluster messaging. You cannot configure a separate datasource for JMS.
*When the cluster nodes exchange a large number of events, the load on the production database increases. This might affect overall cluster performance.
*My webMethods Server does not provide JMS failover capability, and relies on the failover capabilities of the JMS provider.
Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.