Dynamic Apps Platform : Administering My webMethods Server : My webMethods Server Clustering : How a My webMethods Server Cluster Works
How a My webMethods Server Cluster Works
Content Services
The Front End URL
High Availability in a My webMethods Server Cluster
Component Deployment in a My webMethods Server Cluster
Cluster Roles
Guidelines for Assigning Specific Cluster Roles
A My webMethods Server cluster is an active/active environment in which multiple server instances run at the same time, sharing the My webMethods Server database. A My webMethods Server cluster achieves high scalability by distributing the workload among multiple servers. This model is different from an active/passive environment, which makes use of a standby server. A My webMethods Server cluster achieves high availability through the use of shared resources, allowing the cluster to continue to function when a node is taken out of service.
To create a cluster, you need to install an instance of My webMethods Server on each machine in the cluster. All nodes of the cluster share the same My webMethods Server database, which contains shared configuration information and a system content service. You should install the same set of webMethods applications (such as Task Engine), My webMethods User Interfaces, and language packs on each node in the cluster. If an application is not installed on a particular node, the components of the application are not functional on that node.
The system content service stores and retrieves files published by individual users and various objects used by webMethods applications running on My webMethods Server. The system content service is installed as part of My webMethods Server and does not require any configuration before use. Once published, content is available to all nodes in the cluster.
Cluster architecture
Image of cluster architecture
The nodes in the cluster exchange information when they run. There are two methods of communication:
*Through the My webMethods Server database. Cluster bookkeeping is maintained this way.
*Through HTTP. When a server delegates another server to run a command, it does so through the HTTP port of the target server.
Copyright © 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback