Release notes - i2 Analyze 4.4.1

A high level overview of the release, listing new features, the system requirements and any known issues.

Release highlights

This release of i2 Analyze makes a range of new and updated features available.

All clients

Version 4.4.1 of i2 Analyze enables new functionality for all client software:

Desktop client

Version 4.4.1 of i2 Analyze enables new functionality in the i2 Analyst's Notebook Premium desktop client:

Web client

Version 4.4.1 of i2 Analyze enables new functionality in the i2 Notebook web client:

  • Users can apply styling to entities and links
  • Users can get quick access to the 360 view for a record through a new right-click option
  • Users can invert the current selection of records on the chart
Server

Version 4.4.1 of i2 Analyze brings the following changes for administrators and developers:

Other changes

In addition, the following defects have been resolved:

  • Visual queries with loops return non-matching results. [DT00098]
  • Spur-shaped visual query returns incorrect data with directed links. [DT00099]
  • Highlight Query Facet for segment does not allow multi-select. [DT00107]
  • Custom Task Scheduler error. [DT00109]
  • Visual Query time query failure. [DT00111]
  • The configureHttpServer script installs the wrong version of plug-in mod_was_ap24_http.so library. [DT00121]
  • SOLR stopped indexing. [DT00124]
  • VQ with Record Identifier incorrectly changes this term to uppercase. [DT00095]
  • Clicking on Eye icon in the VQ results opens a page with no data if Include Context is enabled. [DT00093]
  • "Get Matches" and import auto matching fails for user with "basic" security permissions. [DT00086]
  • Toolkit gets bad output from liberty securityUtility when JAVA_TOOL_OPTIONS env is set. [DT00067]

Updated documentation:

System requirements

The following system requirements should be used to ensure that the setup you are running is fully supported. Ensure that existing deployments are upgraded to currently supported versions of all the software required.

Operating systems

To run i2 products, you must ensure that you are using a supported operating system.

This release of i2 Analyze 4.4.1 is the last version to support Windows Server 2012 R2.

The supported operating systems for i2 Analyze:
  • Red Hat Enterprise Linux (RHEL) 8
  • Red Hat Enterprise Linux (RHEL) 7
  • Windows 10 Enterprise
  • Windows 10 Professional
  • Windows Server 2019 Datacenter Edition
  • Windows Server 2019 Essentials Edition
  • Windows Server 2019 Standard Edition
  • Windows Server 2016 Datacenter Edition
  • Windows Server 2016 Essentials Edition
  • Windows Server 2016 Standard Edition
  • Windows Server 2012 R2 Datacenter Edition
  • Windows Server 2012 R2 Essentials Edition
  • Windows Server 2012 R2 Standard Edition
Note: i2 products are supported on hardware virtualization environments that run any of the operating systems that are listed in the detailed system requirements. When you run in a virtual environment, any issues that can be replicated by i2 in a supported operating system are addressed by using the standard support policy.

Software

To run i2 products, you must ensure that your environment includes the listed prerequisite software. In addition you may need to install companion software to enhance your work flow.

Co-packaged software

i2 Analyze 4.4.1 is included as a part of the following i2 solutions:
  • i2 Enterprise Insight Analysis 2.5.1
  • i2 Analyst's Notebook Premium 9.4.1

Compatible companion products

Analyst's Notebook Premium 9.4.0 or later can be used to connect to this version of i2 Analyze.

Prerequisites

Application Servers
Open Liberty 22.0.0.12
Development Tools
Temurin 11
Web Browsers
  • Google Chrome (latest version)
  • Microsoft Edge (latest version)
  • Mozilla Firefox (latest version)
  • Mozilla Firefox ESR (latest version)

Supported software

Databases
  • Postgres 15
  • IBM Db2 Advanced Workgroup Server Edition (minimum version 11.1.3.3)
  • IBM Db2 Enterprise Server Edition (minimum version 11.1.3.3)
  • IBM Db2 Workgroup Server Edition (minimum version 11.1.3.3)
  • IBM Db2 Advanced Enterprise Server Edition (minimum version 11.1.3.3)
  • IBM Db2 Advanced Edition VPC option (minimum version 11.5.0.0)
  • IBM Db2 Standard Edition VPC Option (minimum version 11.5.0.0)
  • Microsoft SQL Server Enterprise Edition 2019
  • Microsoft SQL Server Standard Edition 2019
  • Microsoft SQL Server Enterprise Edition 2017
  • Microsoft SQL Server Standard Edition 2017

Hardware

Ensure that the hardware you are installing onto meets the minimal system requirements. Depending on your environment you may wish to increase these values to improve system performance.

i2 Analyze server

Disk space
A minimum of 4 GB total disk space is recommended for installation based on following minimum requirements:
  • 1 GB free disk space for installation for i2 Analyze
  • 2 GB free disk space for installation for Open Liberty
  • 1 GB free disk space for installation for the database
In addition to these minimum requirements additional disk space will be required for data storage.
Note: An additional 20 GB free disk space is temporarily required to download and unpack the installation media.
Memory RAM

In a production environment, a minimum of 16 GB of RAM is required for the application server and 8 GB of RAM is required for the i2 Analyze JVM. The recommended amount of memory is 32 GB for the application server and 16 GB for the i2 Analyze JVM.

Processor
  • Minimum: 2 GHz x86-64 dual-core processor
Network
Transport Layer Security (TLS)1.2 or later is required. TLS 1.0 and 1.1 are not supported.

Language support

i2 products are tested on a number of various regional variations of operating systems. In addition they are translated into a number of different languages.

Operating system support

i2 supports this product on the following regional versions of the supported operating systems:
Language Group/Language Language Collection Support Status
Western Europe and USA Basic Supported
Central Europe Basic Supported
Baltic Basic Supported
Cyrillic Basic Supported
Turkic Basic Supported
Arabic Complex Script Supported
Japanese East Asian Supported
Korean East Asian Supported
Traditional Chinese East Asian Supported
Simplified Chinese East Asian Supported
Thai Complex Script Unsupported
Vietnamese Complex Script Unsupported
Greek Basic Unsupported
Hebrew Complex Script Unsupported
Indic Complex Script Unsupported
Georgian Complex Script Unsupported
Armenian Complex Script Unsupported
Dhivehi Complex Script Unsupported
Galician Complex Script Unsupported
Gujararti Complex Script Unsupported
Kannada Complex Script Unsupported
Krgyz Complex Script Unsupported
Mongolian (Cyrillic) Complex Script Unsupported
Punjabi Complex Script Unsupported
Syriac Complex Script Unsupported
Telagu Complex Script Unsupported

Data support

i2 products support unicode data.

Translations

The following components are translated:
Analyze (Server messages, web clients, and UI hosted in the desktop clients) Analyst's Notebook Premium (Desktop client including Schema Designer)
Arabic
Czech
French
German
Hebrew
Hungarian
Italian
Japanese
Korean
Polish
Portuguese (Brazilian)
Russian
Simplified Chinese
Slovak
Spanish
Traditional Chinese
Turkish

Known issues

The following issues are currently reported:

Web clients
Table 1. Table 1. Web clients
Problem Description
Importing entity types that do not have source reference schema fragments set up can cause the import to fail If you have made use of source reference schema fragments to have different schemas for individual items types or groups of item types, it is not advisable to add source references to imported records.
Only 500,000 records can be added to a i2 Notebook chart in a single operation Charting more than 500,000 records results in the first 500,000 records being added to the i2 Notebook chart, and no notification is provided that some of the items were not charted.
Keyboard navigation does not work within visualizations Attempting to navigate around records that contain visualizations, the visualization cannot be accessed using the tab key. If the tab key is pressed when an item in the visualization is selected, focus is removed from the visualization.
Blocks of text are clipped when printing in Firefox If large amounts of text (more than will fit on a printed page) are entered into a record property, note, or source reference, the text will be clipped if the record is printed.
Using reserved terms in the highlight-queries-configuration.xml file can cause issues when results are expanded in the Show More view Reserved terms should not be used as the id value in the highlight-queries-configuration.xml for example:
<highlightQuery title="Suspects">
  <path>
    <segments>
      <segment>
        <Listed_In-I />
        <Person-I>
        <exportFields>
          <propertyField propertyType="last_name-P" aggregatingFunction="MAX" id="term" />
        </exportFields>
        </Person-I>
      </segment>
    </segments>
  </path>
  <sortBy>
    <field id="term" order="ASC" />
  </sortBy>
</highlightQuery>
If reserved terms are added to the id value, the system will try and interpret them as system specific commands causing unexpected behavior. The following list of reserved terms should not be used as values for id in the highlight-queries-configuration.xml file:

version, id, full_text, full_text_reversed, item_type_id, link_from_id, link_to_id, is_link, link_direction, merged_record_info, record_version, data_source_created, data_source_modified, data_source_seen, data_source_name, data_store_created, data_store_modified, data_store_seen, record_first_uploaded_by, record_last_uploaded_by, record_id, text_facet, source_references_id, source_references_ref_type, source_references_source_name, source_references_location,source_references_image, source_references_description, source_references_is_modifiable

Information Store
Table 2. Table 2. Information Store
Problem Description
Some non-English characters are replaced in the Information Store table and column names This replacement of characters can change the names that you expect to see, when you are completing operations such as ingesting data. For example, the German language esszett character (written 'ß') is replaced by an underscore in Information Store table and column names.
Information Store does not support Read Cloaked The security classification Read Cloaked is not supported in the Information Store.
i2 Analyze services
Table 3. Table 3. i2 Analyze - services
Problem Description
Visual Query timeout for Geospatial searches of large datasets Depending on the scale and geographic distribution of geospatial data in the system, Visual Query searches can return results slowly, or even timeout. To improve the performance of Visual Queries that use geospatial information, you can create geospatial indexes manually.
The message Enter fewer characters is displayed in the Record Inspector when a user enters data into a single-line string The number of characters is less than the limit set in the i2 Analyze schema but contains special characters (for example 'ä'). When data is used in the client, some special characters use more bytes than standard characters. This can cause a validation error because the size of the string is too long.
Messages when Solr starts or stops If you are using third-party tools that contain a find executable, you might see messages that indicate files cannot be found:
find: unable to access "TCP ":
   The system cannot find the file specified.
   find: unable to access ":0 ":
   The system cannot find the file specified.
   find: unable to access ":8983 ":
   The system cannot find the file specified.
These messages might indicate that the system variable that defines the environment path has the path to the third-party tool before the system files. Verify that the Path= system variable contains paths that point to the third-party command line tools added after the paths that point to the system folders.
Searches can stop running after i2 Analyze is restarted If the WebSphere® Liberty Application Server is restarted while searches are running, the search might time out. To prevent this issue, ensure that the HTTP server is restarted when you restart the Application Server.