IBM Financial Crimes Insight with Watson, Private - Platform 1.1.0 Interim Fix | APAR PH38961

Content

• Download this interim fix
• System requirements
• Prerequisites
• Supersedes
• Known issues
• Installation
• List of changes

Download this interim fix

• PH38961 : IBM Financial Crimes Insight with Watson, Private 1.1.0 Interim Fix

System requirements

The official statements for hardware and software support are provided for  IBM Financial Crimes Insight with Watson, Private V1.1.0 . Make sure to review new requirements for supported software, including required base product fix packs.

Review the product license to ensure that you have the necessary authorizations to support a particular topology and that you understand the usage restrictions for all software components that are included with the product.

Prerequisites

IBM Financial Crimes Insight with Watson, Private V1.1.0 (Platform) APAR PH24734

Supersedes

None

Known issues

Known problems, restrictions, and solutions are documented in the form of individual technotes. As problems are discovered and resolved, the IBM Financial Crimes Insight team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems. To view known issues and related support information, see the  IBM Financial Crimes Insight with Watson Support Portal.

Installing IBM Financial Crimes Insight with Watson APAR PH38961

Follow these instructions to install this fix:

Sign in to the Kubernetes control plane as root user and perform the following steps:

1. Unzip the IBM FCI interim fix to a temporary directory. For example, you can unzip the fix into the /root/fci-install-kit directory:

   /root/fci-install-kit/1.1-APAR-PH38961

2. Change to the /root/fci-install-kit/1.1-APAR-PH38961 directory and set file permissions.

   cd /root/fci-install-kit/1.1-APAR-PH38961 
   chmod +x loadImages.sh

3. If you are performing a SoftLayer "FCI bare metal cloud" deployment, edit loadImages.sh and add the internal host name of the Docker registry. Make this change on the line that starts with: DOCKER_REPOSITORY=

   For example:

   DOCKER_REPOSITORY=fcidevai-ikm.wfss.ibm.com:5000

4. On the Kubernetes control plane, run the loadImages.sh script to update the investigative-ui Docker from the directory where the APAR files were copied.

   sh loadImages.sh

5. Update the deployments in the $HOME/fci-install-kit/helm/fci-values.yaml file to use the new images by navigating to investigative-ui and updating the image tag of the investigative-ui container to 1.1-APAR-PH38961.

   For example, change following code from

   investigativeUI:
       image:
         repository: ibmcom/fci-investigative-ui
         tag: 1.1-xxxxxxx-xxxx
   

   to

   investigativeUI:
       image:
         repository: ibmcom/fci-investigative-ui
         tag: 1.1-APAR-PH38961

6. Update the configuration with your changes.

   cd $HOME/fci-install-kit/helm/
   ./install.sh --update-configuration

7. Wait for about 15 - 20 mins for the update to finish. If you encounter an error, see Troubleshooting IBM FCI Installation.

List of changes

Review the updated product license to ensure that you have the necessary authorizations to support a particular topology and that you understand the usage restrictions for all software components that are included with the product.

This release of IBM FCI includes the following changes:

• Resolved issues with translation support