Upgrading to i2 Analyze 4.4.2
To upgrade a deployment of i2 Analyze, you must first upgrade the deployment toolkit that you are using. You then use this upgraded toolkit to upgrade the deployment.
The version of your current deployment determines exactly which path to follow:
If you are upgrading from i2 Analyze 4.3.2 or earlier, you must first upgrade your deployment to a supported version before upgrading to this one. The earliest supported version from which to upgrade is 4.3.3.
Note: From i2 Analyze version 4.3.3, the Analysis Repository, Intelligence Portal, and Onyx services are no longer supported. Deployments that contain an Analysis Repository must migrate data into another repository.
If you are upgrading from i2 Analyze version 4.3.3 or later, complete the instructions below.
For more information about changes to supported versions of i2 Analyze, see Configuration and database changes.
Before you begin
Before you upgrade your production deployment, use a pre-production or test environment to verify that you can complete the upgrade process successfully and that you are familiar with the procedure. After you test the upgrade process for your deployment, complete the upgrade in your production environment. If you do not have a pre-production or test environment, you can create one. For more information, see Creating a production deployment.
If you are upgrading a deployment of i2 Analyze 4.3.3 that uses SQL Server for the Information Store database, you must install a later version of the ODBC Driver for SQL Server and sqlcmd utility. For more information, see Software prerequisites.
Ensure that you back up your deployment before you complete an upgrade. For more information about backing up your deployment, see Backing up a deployment.
About this task
Depending on the scale and complexity of your data, changes of this nature can take time. You might want to plan your upgrade to take place in a period where there is usually no activity.
As part of the i2 Analyze upgrade process, Open Liberty, Solr, ZooKeeper, and Java are updated. You do not need to download and update these prerequisites before you upgrade an existing deployment.
To upgrade the deployment toolkit to version 4.4.2:
Stop i2 Analyze:
In a single-server topology, run setup -t stop.
In a multiple-server topology, see Stopping and starting i2 Analyze.
On each server where the deployment toolkit is installed, make a backup of the i2 Analyze directory, including the toolkit. For example, i2/i2analyze.
Install the i2 Analyze deployment toolkit.
On each server where the toolkit is installed, remove the toolkit, license, and swidtag directories from the existing installation.
Install the i2 Analyze version 4.4.2 deployment toolkit over your existing i2 Analyze directory. For more information, see Installing i2 Analyze.
For each deployment toolkit in your deployment, copy the configuration directory that you backed up in Step 2 to the i2analyze/toolkit directory of the upgraded deployment toolkit that you installed in Step 3.
If it is not already present, create and populate the credentials.properties file. This file must be stored in the location toolkit/configuration/environment in each deployment toolkit.
For more information about the file, see The credentials.properties file.
If you are upgrading a deployment of i2 Analyze 4.3.3 that uses SQL Server for the Information Store database, update the JDBC driver in your deployment configuration to the Java 11 version.
For more information about which driver to install, see Specifying the JDBC driver.
After you upgrade the deployment toolkit, you can use it to upgrade the deployment to version 4.4.2:
Upgrade and start i2 Analyze according to the instructions in Upgrading an i2 Analyze deployment.
If you are using the IBM HTTP Server, restart it.
What to do next
If your deployment includes the ETL toolkit, you must upgrade the ETL toolkit to version 4.4.2 after you upgrade the rest of the deployment. For more information, see Upgrading the ETL toolkit.
After you upgrade, you might need to update the configuration of your deployment for any new or modified configuration settings. For more information about new and modified configuration settings, see Configuration and database changes.
When you start the server after you upgrade, extra processing of the data in the Information Store is completed after the upgrade. During this processing, you might not be able to ingest, update, and delete data in the Information Store. For more information, see Information Store processing after you upgrade i2 Analyze.