Upgrading an i2 Analyze deployment on multiple servers

To upgrade i2 Analyze in a multiple-server deployment topology, you must run the commands to upgrade and start the components of i2 Analyze on each server.

Before you begin

Complete the instructions in Upgrading i2 Analyze to install the latest version of the deployment toolkit on the Liberty, Solr, and ZooKeeper servers, and prepare the environment before you upgrade the deployment.

About this task

To upgrade i2 Analyze in a multiple server deployment topology, you must provide an upgraded configuration to each deployment toolkit. Then, you can run the commands to upgrade the components of i2 Analyze on each server.

As you follow the procedure, it is important to keep track of which server each command runs on, and whether you need to specify the hostname of that server to the command.

Run all toolkit commands from the toolkit/scripts directory in the deployment toolkit on the specified server in your environment.

Procedure

  1. Upgrade and copy the i2 Analyze configuration.

    1. Upgrade the i2 Analyze configuration:

      setup -t upgradeConfiguration
    2. Provided that all servers have the same configuration, copy the upgraded toolkit\configuration to the toolkit directory on each Solr and ZooKeeper server in your environment. Accept any file overwrites.

  2. Upgrade the ZooKeeper and Solr components of i2 Analyze.

    1. On each ZooKeeper server, run the following command:

      setup -t upgradeZookeeper --hostname zookeeper.hostname

      Where zookeeper.hostname is the hostname of the ZooKeeper server where you are running the command, and matches the value for the host-name attribute of a <zkhost> element in the topology.xml file.

    2. On each Solr server, run the following command:

      setup -t upgradeSolr --hostname solr.hostname

      Where solr.hostname is the hostname of the Solr server where you are running the command, and matches the value for the host-name attribute of a <solr-node> element in the topology.xml file.

  3. Upgrade the Information Store database.

    On the Liberty server, run the following command:

    setup -t upgradeDatabases

    If the create-databases attribute in the topology.xml file is set to false, you must run the scripts to update the database manually.

    The scripts are created in the toolkit\scripts\database\db2\InfoStore\generated\upgrade directory. Run the scripts in ascending alphanumeric order. The user that you run the scripts as must have permission to drop and create database tables and views.

  4. Start the ZooKeeper component of i2 Analyze.

    On each ZooKeeper server, start the ZooKeeper hosts:

    setup -t startZkHosts --hostname zookeeper.hostname
  5. Upload the Solr configuration to ZooKeeper.

    On the Liberty server, run:

    setup -t createAndUploadSolrConfig --hostname liberty.hostname
  6. Start the Solr component of i2 Analyze.

    On each Solr server, start Solr:

    setup -t startSolrNodes --hostname solr.hostname
  7. Upgrade Liberty.

    On the Liberty server, run the following command:

    setup -t upgradeLiberty
  8. Upgrade the Solr collections and indexes.

    1. To upgrade the Solr Collections, run the following command on the Liberty server:

      setup -t upgradeSolrCollections --hostname liberty.hostname
    2. To upgrade the Solr indexes, run the following command on the Liberty server.

      setup -t upgradeAllSolrIndexes --hostname liberty.hostname

      The command first checks whether any indexes require an upgrade. If they do, you are prompted to confirm whether to proceed: the upgrade re-creates the index, which triggers a full reindex of the main, chart, and match index types, while other index types are wiped.

      While the data is being reindexed, the system is offline. In systems where there is a lot of data, this can take some time. You can continue by pressing Y and Enter or, o reschedule the downtime, quit the command and skip this step for now. You can reindex your data at another time by following the instructions in Reindexing data after a major version Solr upgrade.

      If a standby index has been created for a collection type, it will be used to reindex the data without modifying the live index.

  9. Start Liberty.

    On the Liberty server, run the following command:

    setup -t startLiberty
  10. If you are using a deployment with an Information Store and have configured system match rules, run the following command to instruct the system to use the upgraded match index:

    setup -t switchStandbyMatchIndexToLive

What to do next

After you upgrade and start i2 Analyze, return to perform the rest of the instructions to finish upgrading the system.