Cluster Upgrade Guidelines
In My webMethods Server, a cluster is defined as multiple My webMethods Server instances that point to the same MywebMethodsServer database component. A cluster can include separate My webMethods Server installations as well as server instances within a My webMethods Server installation.
This section is intended for use with the rest of this chapter. You must perform all documented tasks for your products in the order they are written in this chapter, with these additional tasks or exceptions:
Install
Universal Messaging before installing
My webMethods Server.
Note:
Starting in 10.0, My webMethods Server clusters no longer use the server database to exchange JMS events or as a JMS provider. Instead Universal Messaging is required for synchronization among the cluster nodes.
When you install the new
My webMethods Servers, create a set of installations that matches your old cluster. You can install the new
My webMethods Server installations in parallel.
When you install the fixes on the new
My webMethods Server installations, you can install the fixes in parallel.
You do not need upgrade the Software AG Infrastructure; you can ignore those instructions in this guide.
When you shut down the old products, shut down all cluster nodes.
When you migrate server instances from old
My webMethods Server installations to new
My webMethods Server installations, you can migrate the installations in parallel.
When you initialize the server instances, you can initialize them in parallel.
Configure the cluster as instructed in Administering My webMethods Server.