Configuration and database changes

Version 4.4.2

The following changes are introduced at i2 Analyze version 4.4.2:

Minimum supported version for upgrade

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

PostgreSQL Collation_Locale

If your deployment uses PostgreSQL, and you are upgrading from version 4.4.1.0, be aware that the default Collation_Locale setting was incorrect. This issue can only be resolved by dropping the database, changing the setting, re-creating the database, and re-ingesting the data.

If your deployment was initially created with the 4.4.1.1 fix pack, or you have already applied the fix pack and re-created your database, then you do not need to take any action.

Information Store schema validation

In i2 Analyze deployments that include the Information Store, the server performs additional validation on deployment and upgrade of the schema. Specifically, it checks for the case where two property types in the same item type have been assigned the same semantic property type.

At this version, this invalid state generates a warning in the output from the deploy, upgrade, and updateSchema toolkit tasks. In the future, the warning will become an error. For information about fixing the problem, see Resolving deployment errors.

Note: Previous versions of i2 Analyze included example schemas that suffered from the problem described above. For deployments that use those schemas - or schemas that were originally based upon them - the server repairs the schema dynamically, at runtime.

Information Store security schema changes

i2 Analyze supports a greater range of changes to the security schema after deployment, and there are new extension points that allow dynamic modification of the security schema.

NONE access level warning

In a security schema, specifying the NONE access level in a permission has no effect, because "no access" is the default state.

At this version, specifying NONE is invalid. Using it generates a warning in the output from the deploy, upgrade, and updateSchema toolkit tasks, and from the server. In the future, the warning will become an error. For information about fixing the problem, see Resolving deployment errors.

Removal of dimension values allowed

Dimension values can now be removed from security dimensions without requiring data to be re-ingested or re-indexed. For more details of permitted changes, see Configuring the security schema.

Extension points added

SPI extension points have been added that enable dimension values and permission assignments to be configured in code, as well as in the security schema XML file. For more details and an example of how to implement these SPIs in Java, see the dynamic security example in i2 Analyze Developer Essentials.

Support for Microsoft SQL Server 2022 and recent operating systems

i2 Analyze now supports Information Store deployments on Microsoft SQL Server 2022 as well as 2019 and 2017.

Note: For Windows installations only, the default data directory is version-specific. For SQL Server 2022, it is C:/Program Files/Microsoft SQL Server/MSSQL16.MSSQLSERVER/MSSQL/DATA; earlier versions use MSSQL15 and MSSQL14 in the same path. In a new deployment, ensure that the db.database.location.dir property in environment.properties is set correctly for the version of SQL Server you're targeting.

i2 Analyze also adds support for being deployed on Windows Server 2022 and Red Hat Enterprise Linux (RHEL) v9.

Support for record sharing

This release of i2 Analyze introduces the ability for users to share groups of selected records with their peers. On the server, this feature requires the creation of a new Solr collection named recordshare_index, and introduces new Command Access Control permissions.

The deployment toolkit automatically configures the Solr collection with default settings as part of upgrade.

By default, users are not able to share records with each other. Instead, they must be granted permission to do so. For details of how to grant permission, see The command access control file.

Apache Solr

The version of Apache Solr included in the release is still 8.11.2, but it has been patched to update the versions of Apache Commons Text and Apache Commons Configuration to address CVE-2022-42889 and CVE-2022-33980.

Note: The CVEs were not exploitable in Solr, but still caused vulnerability scan warnings. The toolkit identifies the version of Solr as 8.11.2-patch-1 and installs it as part of upgrading. You can also install it manually by running setup -t installSolr.

Highlight query categories

This release of i2 Analyze adds optional categories to the definitions of highlight queries. You can use these categories to restrict the visibility of highlight queries to specific groups of users. For more details, see Highlight queries.

No changes are necessary to continue to allow all users to see all highlight queries.

Information Store Visual Query configuration

This release of i2 Analyze allows you to control the contents of the Visual Query palette for Information Store searches. This aligns with palette configuration for external Visual Queries, and enables you to include or exclude specific item types from the palette.

These settings are additive, and no changes are required to existing Visual Query configurations. If you do make changes, you can reload the configuration live, through the admin reload endpoint.

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.