Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Upgrade Integration Server or Microservices Runtime and Hosted Wm Packages | Cluster Upgrade Guidelines
 
Cluster Upgrade Guidelines
In Integration Server, a cluster is defined as multiple Integration Server instances that point to the same ISInternal database component and connect to the same Cache Manager on a Terracotta Server Array. A cluster can include multiple Integration Server installations as well as multiple server instances within an Integration Server installation.
In Microservices Runtime, a cluster is defined as multiple Microservices Runtime instances that point to the same ISInternal database component and connect to the same Cache Manager on a Terracotta Server Array. In pre-10.4 installations, a cluster could include multiple Microservices Runtime installations as well as multiple server instances within a Microservices Runtime installation. Starting in 10.4, Microservices Runtime supports only one server instance, so a cluster can include multiple Microservices Runtime installations only.
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:
*When you install the new Integration Servers, create a set of installations that match your old cluster. You can install the new Integration Servers in parallel.
*When you install the new Microservices Runtimes, install a Microservices Runtime for each old server instance you want to migrate. You can install the new Microservices Runtimes in parallel.
*When you install the fixes on the new Integration Servers or Microservices Runtimes, you can install the fixes in parallel.
*When you shut down the old products, shut down all cluster nodes.
Configure the cluster as instructed in webMethods Integration Server Clustering Guide.