Configuration and database changes

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

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.

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.

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 features except the export to CSV file feature.

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.

Version 4.1.5

The following changes are introduced at i2 Analyze version 4.1.5:
Default security values

In a deployment with Opal services, when users create Information Store records in Analyst's Notebook Premium, i2 Analyze applies a default set of security dimension values to the record.

You must change the default dimension values that are applied to records to suit your requirements.

By default, the value for this property uses dimension values from the example security schema.

For more information about configuring the default security dimension values, see Setting default dimension values for Opal.

Results filtering
In a deployment with Opal services, you can configure the types of items and properties, and metadata criteria, that appear in the filter list by creating and configuring facets.

By default, the value of the property is blank, which means that no results configuration is specified in your upgraded system.

For more information about configuring the search results filtering, see Setting up search results filtering.


© Copyright IBM Corporation 2012, 2020.