Preparing Db2 for HADR

When you deploy i2 Analyze with multiple database servers, there must be a mechanism in place to route requests to the new primary server if the current primary server fails.

In Db2, you configure the Information Store database for HADR after you create it. However, there are some decisions that you must make before you create the i2 Analyze configuration.

When you configure i2 Analyze, you must specify the location of the remote database servers in your system. When you configure Db2 for HADR, you can use an automated cluster-controller such as IBM Tivoli System Automation for Multiplatforms (TSAMP) to ensure that clients can connect to the new primary database instance.

If you do not choose to use an automated cluster-controller, you can specify the connection properties for all of your database servers in the i2 Analyze configuration. When you provide the details in the configuration, i2 Analyze uses client-side Automatic Client Rerouting (ACR) to route requests to the new primary server.

Before you start to configure i2 Analyze, choose an approach to ensure that clients can connect to any standby database instances.

For more information about automatic cluster-controllers, see High availability through clustering.

Deploy i2 Analyze and the Information Store database. For more information, see Deploying i2 Analyze with high availability.