Deploying i2 Analyze with high availability
When you deploy i2 Analyze with high availability, there are a number of steps that you must complete.
- Install any prerequisite software to
prepare your servers for the pre-production
- For a deployment with high availability, use the multiple servers deployment topology with at least the minimum number of servers required for high availability of each component. For more information, see Deployment topologies.
- To deploy with high availability, you must configure your database management system after you install it:
- Copy the toolkit\configuration directory from the configuration development environment, to the toolkit directory at the root of the deployment toolkit on one of the Liberty servers.
- Update the configuration to specify your
remote database, follow the instructions in Specifying remote database storage to update
and topology.xml files.
- If you are using Db2, you can
specify any alternative database location
information in the
- If you are using an automated cluster-controller such as IBM Tivoli System Automation for Multiplatforms (TSAMP), then specify the hostname and port number of the cluster.
- If you are not using an automated
cluster-controller, in the
<database>element for your Information Store, provide the hostname and port number of any standby databases in the
The host and port number must be separated by a colon (
:), and each database server must be separated by a (
- If you are using SQL Server, specify the hostname and port number of the availability group listener.
- If you are using Db2, you can specify any alternative database location information in the topology.xml.
- Update the
configuration to configure each component for high
availability:The environment.properties, http-server.properties, and topology.xml contain hostname and file path settings that you might need to update for the servers in your pre-production environment. For more information, see Configuration files reference.
- Deploy and start i2 Analyze with one Liberty server by following the instructions in Deploying i2 Analyze on multiple servers.
- After you deploy with one Liberty
server, update the configuration on any other
- Copy the configuration directory from the deployed Liberty server to the toolkit directory on any other Liberty servers in your environment.
- On each Liberty server, in the
topology.xml file update the
port-numberattributes of the
- Deploy and start the i2 Analyze
application on each of the other Liberty
setup -t installLiberty setup -t deployLiberty setup -t startLiberty
The security configuration must be the same on each server.
- Configure Liberty
security for your environment. To do this, repeat
any changes that you made to the Liberty
configuration in the previous
environment.This might involve copying the user registry file, or updating the server.xml file.
- After you deploy i2 Analyze, configure
your database management system to replicate the
Information Store database to your standby
- If you are using Db2, configure high
availability for the Information Store database
and replicate it to any standby database
instances.For more information, see Replicate the Information Store in Db2.
- If you are using SQL Server, add the
Information Store to your availability
group.For more information, see Replicate the Information Store in SQL Server.
- If you are using Db2, configure high availability for the Information Store database and replicate it to any standby database instances.
- Complete any configuration changes in
the Information Store database on the primary
- If you created any rules or
schedules to delete records by rule, replicate the
rules and schedules that you created in the
previous environment.On SQL Server, you must update the automated job creation schedule on every database instance. For more information see, Changing the automated job creation schedule.
- If you created any merged property values definition views for your ingestion process, replicate the view definition that you created in the previous environment.
- If you created any rules or schedules to delete records by rule, replicate the rules and schedules that you created in the previous environment.