Integration Server or Microservices Container Clustering Requirements

Complete Installation and Upgrade Information for Software AG Products : Upgrading Software AG Products : Critical Factors and Requirements for Successful Upgrade : Integration Server or Microservices Container Clustering Requirements

Note:

Steps for Microservices Container are identical to those for Integration Server.

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 Integration Server installations on different machines, server instances within an Integration Server installation, or both.

This section is intended for use with the rest of this guide. You must perform all tasks in this guide for your products, in the order they are written, with the additional tasks or exceptions noted in this section.

Use the instructions below with the instructions in Install New Products and Begin Migration.

When you install the new Integration Servers, create a cluster that matches your old cluster. You can install the new Integration Servers in parallel.

When you install the fixes on the new Integration Servers you can install the fixes in parallel.

When you shut down the old products, shut down all cluster nodes.

Use the instructions below with the instructions in Migrate Integration Server, Microservices Container, and Hosted Wm Packages.

After you migrate server instances, make sure the new server instances are processing client requests.

The tasks in Migrate Event Infrastructure and Perform Final Upgrade Tasks for All Products include a task to configure your products. For instructions on configuring Integration Server clusters, see the webMethods Integration Server Clustering Guide.

Contact Support | Community | Feedback