Configuration and database changes

Version 4.4.1

The following changes are introduced at i2 Analyze version 4.4.1:

Open Liberty

The Liberty application server installed by the toolkit is now the Open Liberty distribution, rather than IBM® WebSphere® Liberty.

IBM HTTP Server

Toolkit support for configuring the IBM HTTP Server is now deprecated, and might be removed in a future release. If the topology.xml file in your deployment sets http-server-host="true", then then toolkit displays a warning message.

Using an HTTP server or proxy for i2 Analyze is optional. If you do want to use one, you can use any modern HTTP server.

Version 4.4.0

No changes are introduced at i2 Analyze version 4.4.0 that affect upgrade.

Version 4.3.5

The following changes are introduced at i2 Analyze version 4.3.5:

Minimum supported version for upgrade

The minimum version of i2 Analyze that you can upgrade from is now 4.3.1.1.

Improved multiple-line string Visual Query performance on IBM Db2

If your deployment includes an Information Store that runs on IBM Db2, this version includes tooling to improve Visual Query performance with properties that contain multiple-line strings.

Version 4.3.4

The following changes are introduced at i2 Analyze version 4.3.4:

Minimum supported version for upgrade

The minimum version of i2 Analyze that you can upgrade from is now 4.3.0.0.

Java install location setting moved

The java.home.dir setting in the environment.properties file is no longer used. The value that was specified for this setting is now used for the I2A_COMPONENTS_JAVA_HOME variable in the setup.in file.

For more information about how the location of Java is specified, see Specifying the Java distribution.

Additional setting require for client certificate authentication

If your deployment uses client certificate authentication, you must update the server.xml in Liberty with a new mandatory attribute. For more information, see Configuring i2 Analyze for client certificate authentication.

Temporary ingestion table space deprecated in Db2

The IngestionTempTableSpace setting in the InfoStoreNamesDb2.properties file is superseded by the InternalStagingTableSpace setting.

Version 4.3.3

The following changes are introduced at i2 Analyze version 4.3.3:

Record matching

If your existing deployment of i2 Analyze included the i2 Connect gateway but not the Information Store, then the upgrade process modifies the contents of ApolloServerSettingsMandatory.properties to reclassify your schema as a gateway schema. The effect of this change is to modify the identifiers of the item types in the schema.

If your deployment includes match rules files on the server, the upgrade process automatically updates those files to contain the correct item type identifiers. However, if your users have developed local rules files for Find Matching Records, you must edit those files before they reconnect to the server after an upgrade.

On each workstation, follow the instructions to find the local-fmr-match-rules.xml file and use the information in Match rules syntax to update the item type identifiers in the file.

Search results filtering

If your existing deployment of i2 Analyze included the i2 Connect gateway but not the Information Store, then the upgrade process modifies the contents of ApolloServerSettingsMandatory.properties to reclassify your schema as a gateway schema. If your existing deployment also used a results configuration file, then you must update that file to reflect the reclassification.

Follow the instructions in Setting up search results filtering and Understanding the results configuration file to make the necessary changes to the item type identifiers in the file.

Command access control permissions

A new permission can be added to your command access control file. The new permission grants access to the i2 Notebook web client for the Information Store. For more information, see Controlling access to features.

If you do not update your command access control configuration file to include the new permission, or if command access control is not configured in your deployment, access to the feature is denied to all users.

Liberty log location

The Liberty log files from the i2 Analyze application are now located in the wlp\usr\servers\opal-server\logs\opal-services directory. Any logs generated from your previous release remain in their current location. Any new log messages are created in the new files in the new location.

For more information about the log files, see Deployment log files.

New Information Store table space in Db2

The IS_INTSTG_TS table space is added to the Information Store database. This table space is used to store the internal staging tables that are created as part of the ingestion process. The InfoStoreNamesDb2.properties file contains a new InternalStagingTableSpace setting.