Configuration and database changes

As a result of an upgrade, you might need to consider configuration or database changes that are new or different compared with previous versions of the software. Depending on the default behavior, you might want to modify the configuration to meet your requirements after you upgrade the deployment.

Version 4.3.4

The following changes are introduced at i2 Analyze version 4.3.4:

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.
Multi-line string column data type change: In a deployment that uses Db2, the data type used for multi-line string property type columns is changed from CLOB to VARCHAR.

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.

Version 4.3.2

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

Version 4.3.1 Fix Pack 1

The following changes are introduced at i2 Analyze version 4.3.1.1:

Command access control permissions

New permissions can be added to your command access control file. The new permissions grant access to upload, delete, and read charts with 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 permissions, access to the features is denied to all users. If command access control is not configured in your deployment, all authenticated users have access to the new features.

Chart storage

For the Information Store database to store charts, the Information Store schema is updated to include the chart item type. After you upgrade the Information Store database, the following tables are added for chart storage:

E_ANALYST_S_NOTEBOOK_CH - the data table, includes the chart properties
E_ANALYST_S_NOTEBOOK_CH_BIN - the binary data table, includes the binary representation of the chart
E_ANALYST_S_NOTEBOOK_CH_TXT - the text data table, includes the text from the chart that can be searched for

Version 4.3.1

The following changes are introduced at i2 Analyze version 4.3.1:

OpenJDK - Java Development Kit: The JDK that is installed by the i2 Analyze toolkit is now the OpenJDK, instead of the Oracle JDK.
When you upgrade your deployment of i2 Analyze, the Oracle JDK is uninstalled and the OpenJDK is installed.
Deletion view column changes: To incorporate record identifiers, the deletion views are updated to include a new item_id column. The content of the existing record_id column now contains the record identifier for a record. The item_id column contains the item identifier.
If your existing deletion rules use the record_id column, you might need to update them to use the item_id column. For more information, see Deleting records by rule.

Version 4.3.0

The following changes are introduced at i2 Analyze version 4.3.0:

Database transaction log size increase: The database management system now logs more tables during data movement, which causes an increase to the size of the transaction log. This is more noticeable in deployments that contain large amounts of data.
InfoStoreNames.properties file rename: The InfoStoreNames.properties file is renamed to InfoStoreNamesDb2.properties.

Version 4.2.1

The following changes are introduced at i2 Analyze version 4.2.1:

Configuration fragments

You can deploy the Information Store and i2 Connect in the same deployment of i2 Analyze. To configure a deployment with this topology, some properties files and settings are in a different location:

If your deployment contained the opal-services-daod fragment, it is renamed to opal-services. The settings in the OpalServerSettingsDaodManadatory.properties file are now in the DiscoServerSettingsCommon.properties file.
If your deployment contained the opal-services-is fragment, the opal-services fragment is added and the following files are moved to the opal-services fragment.
- DiscoClientSettings.properties
- DiscoServerSettingsCommon.properties
- Results configuration file
- visual-query-configuration.xml

By default, all of the values for the settings in the files are unchanged.

Command access control permissions

New permissions can be added to your command access control file. The new permissions grant access to the export search results to a CSV file and i2 Connect features in Analyst's Notebook Premium. For more information, see Controlling access to features.

Oracle Java Development Kit

The JDK that is installed by the i2 Analyze toolkit is now the Oracle JDK, instead of the IBM® JDK.

When you upgrade your deployment of i2 Analyze, the IBM JDK is uninstalled and the Oracle JDK is installed.