IBM Support

IBM i2 Analyze 4.3.4 Fix Pack 3 readme

Fix Readme


Abstract

Readme file for: IBM i2 Analyze 4.3.4 Fix Pack 3
Fix IDs:
IBM i2 Enterprise Insight Analysis: 2.4.0.3-SEC-i2EIA-WinLinux-FP0003
IBM i2 Analyst's Notebook Premium: 9.3.0.3-SEC-I2ANBP-Win-FP0003
i2 Connect: 1.1.0.3-SEC-I2CONNECT-WinLinux-FP0003
Publication date: December 2021
Last modified date: December 2021
Important: The most current version of the readme file can always be found online.

Content

Download location

IBM i2 Analyze 4.3.4 Fix Pack 3 can be downloaded from Fix Central. For more information, see the download document:

Download IBM i2 Analyze 4.3.4 Fix Pack 3

Prerequisites

This fix pack requires a deployment of IBM i2 Analyze 4.3.4.

Note: This fix pack includes the fixes applied in earlier fix packs. There is no need to apply fix pack 1 or 2 in addition to fix pack 3.

For more information, see:
IBM i2 Connect 1.1.0 Fix Pack 1 Readme
IBM i2 Enterprise Insight Analysis 2.4.0 Fix Pack 1 Readme

Installation information

IBM i2 Analyze 4.3.4 Fix Pack 3 contains the following files:

  • IBM_i2_Analyze_4.3.4_Fix_Pack_3_Windows_Archive.zip
  • IBM_i2_Analyze_4.3.4_Fix_Pack_3_Linux_Archive.tar.gz

Updating the toolkit

To upgrade the i2 Analyze installation, complete the following steps.

  1. Ensure that you are logged on with Administrator privileges.

  2. Extract the contents of the fix pack into the appropriate directory as follows:

    • On Windows, extract the file IBM_i2_Analyze_4.3.4_Fix_Pack_3_Windows_Archive.zip into the directory C:\IBM\i2analyze\.

    • On Linux, extract the file IBM_i2_Analyze_4.3.4_Fix_Pack_3_Linux_Archive.tar.gz or into the directory /opt/IBM/i2analyze/.

    The following files and directories are then present in the IBM\i2analyze\toolkit directory:

    • application\shared\lib\
      • log4j-1.2-api-2.17.0.jar
      • log4j-api-2.17.0.jar
      • log4j-core-2.17.0.jar
      • log4j-slf4j-impl-2.17.0.jar

    Note: If the listed files cannot be found in application\shared\lib, the patch will not be correctly applied. 

  3. Remove the older versions of the files included in the patch:

    • application\shared\lib\
      • log4j-1.2-api-2.14.0.jar or log4j-1.2-api-2.16.0.jar
      • log4j-api-2.14.0.jar or log4j-api-2.16.0.jar
      • log4j-core-2.14.0.jar or log4j-core-2.16.0.jar
      • log4j-slf4j-impl-2.14.0.jar or log4j-slf4j-impl-2.16.0.jar

Updating the deployment

Depending on your starting point, you can either update your deployment to use the patched version of log4j or upgrade your i2 Analyze deployment to include the fixes rolled up from fix pack 1. 

Applying the rolled up fixes and patching log4j

If you have not already applied fix pack 1, your deployment uses IBM Db2 as the database for the Information Store or Chart Store, and you are upgrading from an earlier version, you must apply this fix pack before running the upgrade commands, for example  setup -t upgrade.  With the files in place in your toolkit, you can continue with the upgrade process.

Updating your deployment to use the patched log4j

If you have already applied fix pack 1, or you do not use IBM Db2 as the database for the Information Store or Chart Store, you only need to apply the patched version of log4j.
To upgrade the i2 Analyze deployment to use the patched version of log4j:

  1. Stop your i2 Analyze Liberty server:

    setup -t stopLiberty

  2. Update your i2 Analyze Liberty server:

    setup -t deployLiberty

  3. Restart your i2 Analyze Liberty server:

    setup -t startLiberty

Note: If you have multiple Liberty servers in your environment, you must follow these steps on each Liberty server.

To upgrade a Solr instance in your deployment to use the patched version of log4j:

  1. Stop your Solr server:

    setup -t stopSolr

  2. Update your Solr server:

    setup -t installSolr

    During the install task, you will see a message in your console log:

    'Installing Apache Solr to C:/IBM/i2analyze/deploy/solr.<Version (new): 8.8.2-log4j-patch2, (old): 8.8.2>'

    Note: The 'log4j-patch2' indicates that the newer version has been applied.

  3. Restart your i2 Analyze Liberty server:

    setup -t startSolr

Note: If you have multiple Solr servers in your environment, you must follow these steps on each Solr server.

Updating the ETL toolkit

If your deployment of i2 Analyze uses the ETL toolkit, you must update the ETL toolkit after you apply the fix pack. To update the ETL toolkit, you must remove the existing version and replace it with the one that is created with the i2® Analyze toolkit that contains the fix pack.

  1. If you modified the connection properties of your ETL toolkit to connect to a remote instance of DB2®, make a backup of the properties file. Navigate to the etltoolkit\classes directory of your ETL toolkit, and copy the Connection.properties file to a location outside of the etltoolkit directory.
  2. You can now remove the previous ETL toolkit.
  3. After you update your deployment with the fix pack, deploy the ETL toolkit.  For more information about deploying the ETL toolkit, see Deploying the ETL toolkit.
  4. Update the Connection.properties file in the new ETL toolkit with the db.installation.dir property and value from the backed up Connection.properties file from your previous ETL toolkit.

List of fixes

This fix pack includes the following fixes.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228 
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105

In addition this fix pack rolls in the earlier fix: 

In i2 Analyze 4.3.4, Visual Query supports the querying of MULTIPLE_LINE_STRING properties, notes and source references. When upgrading to 4.3.4, the columns used for those types, in deployments that use IBM Db2 databases, are converted from CLOBs to VARCHARs. This might cause data tables to be unavailable and the subsequent recovery of the database to a backup taken prior to upgrading. This fix pack allows the newly supported types to be used in visual queries without column conversion taking place.

Known Issues

This fix pack is specific to the version of i2 Analyze specified. If your system is upgraded to i2 Analyze version 4.3.5, you must apply the related fix pack specific to that version after completing the upgrade process. 

Copyright and trademark information

IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available:  https://www.ibm.com/legal/copytrade.

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSXVXZ","label":"IBM i2 Enterprise Insight Analysis"},"ARM Category":[{"code":"a8m0z000000cwkBAAQ","label":"i2 Enterprise Insight Analysis-\u003EDeployment"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0"},{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSXVMQ","label":"i2 Analyst\u0027s Notebook Premium"},"ARM Category":[{"code":"a8m0z000000bq8pAAA","label":"i2 Analyst\u0027s Notebook-\u003EInstall\/Configure\/Upgrade"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3.0"},{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUJWJ","label":"i2 Connect"},"ARM Category":[{"code":"a8m0z0000001f9MAAQ","label":"i2 Connect"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.1.0"}]

Document Information

Modified date:
22 December 2021

UID

ibm16529042

Page Feedback