Integration Server 10.11 | Developing Data Synchronization Solutions with webMethods Mobile Support | Configuring webMethods Mobile Support | Considerations for Using Mobile Support in a Clustered Environment
 
Considerations for Using Mobile Support in a Clustered Environment
If you are using Mobile Support in a clustered Integration Server environment, keep the following points in mind:
*The MobileSupport functional alias must point to the same Pool Definition values in all the nodes of the cluster.
*Configuration of all mobile sync components must be identical across all nodes of the cluster. As part of this configuration, all packages containing the business document types and download and upload services specified in each mobile sync component must exist on each node of the cluster. You can use webMethods Deployer to help automate this process.
*Mobile Support uses the locking and unlocking functionality of Terracotta Ehcache to achieve synchronization. In a clustered environment, Mobile Support also uses a system cache, maintained on the Terracotta Server Array, to enable all Integration Servers in the cluster to process data synchronization requests received from mobile applications. Software AG recommends that you not edit the configuration parameters related to this system cache.
For more information about the various tasks involved with configuring and using Mobile Support in a clustered environment, see the following resources.
For more information about...
See...
Configuring Integration Server clusters
webMethods Integration Server Clustering Guide
Configuring functional aliases
Installing Software AG Products
Replicating Integration Server packages
webMethods Integration Server Administrator’s Guide
Using webMethods Deployer to automate mobile sync component configuration
How Mobile Support uses Terracotta and the Mobile Support system cache in a clustered environment
Using BigMemory with webMethods Products