Fix Readme
Abstract
Instructions for upgrading Red Hat Enterprise Linux installations running IBM InfoSphere Information Server 11.7.1.0 or 11.7.1.1, to 11.7.1.2. This document contains guidance for installation of the 11.7.1.2 upgrade package available on Fix Central.
Installation of 11.7.1.2 requires Red Hat Enterprise Linux to be first upgraded to version 8. This document must not be used for installations on any other operating system.
Content
Table of Contents
1) Introduction
2) General installation information
2.1) Environment
2.2) Using a password or passwordless SSH for upgrading the Microservices tier
3) Downloads
4) Installation
4.1) Instructions for upgrading Information Server in GUI mode of the Update Installer
4.2) Instructions for upgrading Information Server in Console mode of the Update Installer
5) Post upgrade actions
5.1) Information Analyzer microservice
5.2) Data Flow Designer
5.3) Usage of Information Server Administration (web) console
5.4) Synchronize assets
5.5) Upgrade Db2 version 11.1 to Db2 11.5
1) Introduction
The IBM InfoSphere Information Server 11.7.1.2 ispkg image is available for upgrading of Information Server 11.7.1.0 version 11.7.1.1 installations. The steps for upgrading to 11.7.1.2 depends on whether a Microservices tier is installed.
11.7.1.2 upgrade prerequirements:
- Information Server 11.7.1.0 or 11.7.1.1 must be installed.
- The services tier must be on Red Hat Enterprise Linux (RHEL) and the operating system must be upgraded to Red Hat Enterprise Linux version 8 (RHEL 8).
- If you have a Microservices tier, it must be at the same version as the services tier.
- See technote for issues you might need to address before the installation, and also issues that might affect you after the installation.
- If you use Db2 as the repository database, note Db2 versions before 11.1.4.6 are not supported on RHEL 8. After Information Server is upgraded to 11.7.1.2, you can upgrade Db2 to a supported version. For usage with Information Server, Db2 11.5 can be obtained from Passport Advantage.
If Watson Knowledge Catalog (WKC) is installed, then upgrade to 11.7.1.2 is not supported.
- If WKC is installed but is not in use, you can manually uninstall WKC to allow installation of 11.7.1.2. See Remove Watson Knowledge Catalog from an Information Server 11.7.1.0 installation for details.
- If WKC is installed and is in use, you cannot install 11.7.1.2.
Note:
1. If you need to add a Microservices tier, or enhance an existing Microservices tier in an Information Server 11.7.1.0 installation, you must use technote instead of this technote.
2. If you need to add a Microservices tier to an Information Server 11.7.1.1 or later installation, you must use technote.
2) General installation information
2.1 Environment
For the Information Server host system, ensure that your system meets the Information Server 11.7.1.2 System requirements. Disk space requirements are included in the System requirements.
Refer to the version 11.7.1.0 pre-installation checklist to validate your system.
In this case, you do not have to set up passwordless SSH from the Information Server host to the master node.
However, for a multiple nodes environment, you must set up passwordless SSH for the root user from the master node to the worker nodes.
The specified non-root user must have sudo privilege with NOPASSWD enabled.
In this case, you do not have to set up passwordless SSH from the user running the installation on the Information Server host to the master node.
For a multiple nodes environment:
ii. You must set up passwordless SSH for the specified non-root user from the master node to the worker nodes.
You must set up passwordless SSH from the user running the installation on the Information Server host to the master node.
For a multiple nodes environment, passwordless SSH must also be set up for the root user from the master node to the worker nodes.
The specified non-root user must have sudo privilege with NOPASSWD enabled.
You must set up passwordless SSH from the user running the installation on the Information Server host to the master node.
For a multiple nodes environment:
i. The specified non-root user must be set up in the same manner on all nodes.
ii. Passwordless SSH must also be set up for the specified non-root user from the master node to the worker nodes.
a. If the file /root/.ssh/id_rsa.pub does not exist, create the SSH Keys with the following command:
> ssh-keygen -f /root/.ssh/id_rsa -q -N ""
b. Copy the SSH public key to the Microservices tier node with the following command:
> ssh-copy-id -i /root/.ssh/id_rsa.pub root@<enterprise search="" node="">
c. Validate the root passwordless SSH connection to the Microservices tier node with the following command:
> ssh root@<enterprise search="" node=""> hostname
A non-root user with sudo privileges can be set up for passwordless SSH in the same manner.
3) Downloads
3.1) If you are upgrading the Microservices tier, verify that your system meets the requirements for usage as the Microservices tier of IBM InfoSphere Information Server 11.7.1.2.
3.2) Update the Update Installer to the latest
3.2.1) On the Information Server host, update to an appropriate version of the Update Installer
For Windows installations, download Update Installer 11.7.1.095 or 11.7.1.116 and later. Do not use 11.7.1.105.
For AIX and Linux, you can use Update Installer 11.7.1.095 or later. However, do not use 11.7.1.098.
3.2.2) Instructions to update the Update Installer.
See section “Installing a new version of the Update Installer before installing an update, fix, or patch” for information on extracting the new Update Installer and running updateImage.sh.
If you used the default directory for Information Server, the Update Installer is installed in /opt/IBM/InformationServer/Updates/bin.
3.3) You must download the following images from IBM Fix Central and Passport Advantage depending on your installation choices.
For more information on locating the images, see the Download document.
3.3.1) On the Information Server host, download, and extract the Information Server 11.7.1.2 ispkg image (is1171_fp2_server_linux64) from IBM Fix Central:
For example, fixpack_FP2_IS1171_linux64_11710-11711.tar.gz
Note: Extract the image with umask as 022.
3.3.2) On the Microservices tier, download IBM Information Server Enterprise Search v11.7.1.2 for Linux (is11712_ises_docker_services_engine_multi) from IBM Fix Central. Do not extract the file.
For example, fixpack_FP2_IS1171_microservices_11710-11711.tar.gz
4) Installation
Use the following instructions irrespective of whether you have a Microservices tier.
Note:
Before you begin the upgrade to 11.7.1.2
See Red Hat documentation "Instructions for an in-place upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8" for information about the upgrade.
2. Address "Known issues while installing or upgrading Information Server to version 11.7.1.0".
3. If you are upgrading the Microservices tier
i. Upgrade the operating system to Red Hat Enterprise Linux 8.
ii. After the operating system is upgraded to Red Hat Enterprise Linux version 8, all pods are likely to be in an error state. Either way, you must run the following command
kubectl patch ds -n kube-system weave-net --patch '{"spec":{"template":{"spec":{"containers":[{"name":"weave","command":["/bin/sh","-c","sed '"'"'/ipset destroy weave-kube-test$/ i sleep 1'"'"' /home/weave/launch.sh | /bin/sh"]}]}}}}'
iii. The Microservices tier must be at the same version as the Information Server services tier.
iv. Ensure that all pods are up and running.
v. Upgrade Ansible to version 2.8.5 or later.
Information on Ansible can be found at https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html.
4.1) Instructions for upgrading Information Server in GUI mode of the Update Installer
4.1.1) Log in to the Information Server host. Change directory to <IS_HOME>/Updates/bin
For example, cd /opt/IBM/InformationServer/Updates/bin
4.1.2) Verify that the Update Installer version is 11.7.1.079 or later (see step 3.2):
./installUpdates -version
4.1.3) Initiate the Fix Pack install with the following command:
./installUpdates
This command launches the Update Installer in GUI mode.
4.1.4) Provide information as required in each panel to complete the installation.
Click Login.
4.1.5) Review the System requirements, Release Notes, and Planning information.
Click Next.
4.1.6) The Update Installer displays the Information Server installation directory. The contents of the displayed panel depends on whether Watson Knowledge Catalog is installed.
4.1.6.1) If your installation does not include Watson Knowledge Catalog, click Next.
4.1.6.2) If Watson Knowledge Catalog is installed, select the checkbox to indicate whether you intend to apply 11.7.1 Fix Pack 2 to your version 11.7.1.0 installation. Installations with Watson Knowledge Catalog are not permitted to install 11.7.1 Fix Pack 2 until Watson Knowledge Catalog is manually uninstalled. See technote for steps to manually uninstall Watson Knowledge Catalog.
If you select the checkbox to apply Fix Pack 2 to your version 11.7.1.0 installation, and click Next, the following error is displayed.
4.1.7) In this step choose whether to upgrade the Microservices tier.
4.1.7.1) If you do not have a Microservices tier select the "Skip installation of Information Server microservices tier" checkbox.
Since addition of a Microservices tier during the Fix Pack upgrade is not supported, click Next and skip forward to step 4.1.8.
Later, if needed you can add a Microservices tier. Refer to technote for details.
4.1.7.2) If you have a Microservices tier, you might choose to skip its upgrade while your other Information Server tiers are upgraded to 11.7.1.2.
Note:
1. If you choose to skip upgrade of the Microservices tier, then before the upgraded Information Server installation is used, the Microservices tier must be upgraded. Follow technote to upgrade the Microservices tier to be at the same 11.7.1.2 version as the other Information Server tiers.
2. In case you previously installed the Microservices tier by following technote, you must skip upgrade of the Microservices tier in this step. Instead, after the other Information Server tiers are upgraded to 11.7.1.2, use the same technote to upgrade the Microservices tier in order to avoid overwriting your handcrafted inventory file.
Select the "Skip patching of Information Server microservices tier" checkbox to skip the upgrade.
Click Next.
If you are currently using version 11.7.1.1, skip forward to step 4.1.8.
If Information Server 11.7.1.0 is in use, the following panel is displayed.
Since none of these actions are supported while upgrading to 11.7.1.2, select the "Skip enhancements of the Information Server microservices tier" checkbox.
Click Next.
Skip forward to step 4.1.8.
4.1.7.3) To upgrade the Microservices tier
Note:
1. In case you previously installed the Microservices tier by following technote, you must skip upgrading the Microservices tier in this step and instead, follow the instructions in step 4.1.7.2.
2. The Microservices tier must be at the same version as the Information Server services tier.
3. You must run the following command
kubectl patch ds -n kube-system weave-net --patch '{"spec":{"template":{"spec":{"containers":[{"name":"weave","command":["/bin/sh","-c","sed '"'"'/ipset destroy weave-kube-test$/ i sleep 1'"'"' /home/weave/launch.sh | /bin/sh"]}]}}}}'
4. All pods must be up and running.
You can check the status of the pods by running the following command:
kubectl get pods --all-namespaces
5. Ansible version 2.8.5 or later must be installed.
Information on Ansible can be found at https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html.
Provide the relevant information in the panel:
a. Deselect the "Skip patching of Information Server microservices tier" checkbox.
b. Specify a fully qualified domain name for the Master Node Host.
c. Specify the same User as was used during the initial installation of the Microservices tier.
d. For more information on "Authenticate with a password", see section 2.2.
e. If you specify a non-root user, in /etc/security/limits.conf, the hard and soft setting of nofile and nproc for the specified user must be 10240.
Also, umask must be set to 022 in ~/.bashrc.
4.1.8) In the list of "Packages to be installed", select the 11.7.1.2 ispkg file you downloaded from IBM Fix Central.
The package name is similar to as shown in section 3.3.1.
Click Next.
The Installer again checks whether Watson Knowledge Catalog is installed on the system. If present, the following error is displayed.
Installations with Watson Knowledge Catalog are not permitted to install 11.7.1 Fix Pack 2 until Watson Knowledge Catalog is manually uninstalled. See technote for steps to manually uninstall Watson Knowledge Catalog.
4.1.9) Provide credentials to be used for Kafka and Solr (for example, solruser, solrpwd etc). The Update Installer creates the specified users in Kafka and Solr; they do not have to be an operating system user, Information Server user, or LDAP user.
Later, you can use the specified values for maintenance actions such as accessing the Solr Web UI.
Click Next.
4.1.10) Provide the Information Server Administrator user name and password. Accept the certificate and click Next.
4.1.11) Accept the certificate. Click Next.
4.1.12) On the System Requirements Check page, confirm that all system requirements passed, and then click Next.
4.1.13) If you have a Microservices tier, examine the results from system requirement checks of the Microservices tier. If all is good, click Next.
4.1.14) Review the Preinstallation Summary and click the Install button to start the installation.
4.1.15) Click the Finish button after the installation completes.
4.1.16) Click “Advanced” followed by "Accept the Risk and Continue".
4.1.17) The Launchpad is displayed.
4.1.17.1) If you don't have a Microservices tier, the Information Server Launchpad is displayed.
4.1.17.2) If you have a Microservices tier, the Information Server (Microservices) Launchpad is displayed.
4.2) Instructions for upgrading Information Server in Console mode of the Update Installer
4.2.1) Log in to the Information Server host. Change directory to <IS_HOME>/Updates/bin
For example, cd /opt/IBM/InformationServer/Updates/bin
4.2.2) Before running the Update Installer, check the Information Server 11.7.1.2 System requirements and make sure that your system meets the requirements.
4.2.3) Verify that the Update Installer version is 11.7.1.079 or later (see step 3.2):
./installUpdates -version
4.2.4) Run the Update Installer to upgrade Information Server.
For example, installUpdates -i /opt/IBM/InformationServer/ -p /opt/Builds/ISPKG/<ispkg_file_name>.ispkg -verbose -console -properties <property_file_name>
where
<ispkg_file_name> is the ispkg file you downloaded from IBM Fix Central
<property_file_name> is the name of the property file wherein you specify values for the various properties that control the installation on the Microservices tier. You do not have to specify "-properties" if you don't have a Microservices tier.
The Update Installer prompts you for the Information Server administrator user ID and password, and the WebSphere Administrator user ID and password.
Sample property file
5.1) Information Analyzer microservice
Migrate the rule execution results to the IA micro-service by running following command for each project containing rule execution results:
/IBM/InformationServer/ASBServer/bin/IAAdmin -user -password -migrateXmetaMetadataToMicroservice -projectName
Do not specify the project name to migrate all projects.
The migration might take a long time depending on the number of projects and rule execution results to migrate.
5.2) Data Flow Designer
If SQLServer or Oracle is used as a metadata repository, execute the script at `<IIS_PATH>/ASBServer/bin/sql/<type_of_DB>/alterGitTable.sql to add a column 'REMOTE_GIT_PUSH_PREPEND_PATH' to the table "DFD_SCM_GIT_REPOS_CONFIG".
5.3) Usage of Information Server Administration (web) console
You might not be able to log in to the Information Server Administration (web) console.
Clear the browser cache and cookies and again try to log in to the Administration console.
5.4) Synchronize assets
If you already had data in InfoSphere Information Governance Catalog before the upgrade, you need to synchronize data manually after the upgrade. Follow the instructions here.
5.5) Upgrade Db2 version 11.1 to Db2 11.5
For upgrades to Db2 version 11.5, perform the following steps:
c. Follow Db2 instructions to upgrade Db2 to version 11.5.
d. Download the Db2 11.5 license file from Passport Advantage.
e. Follow Db2 instructions to use db2licm to apply the license.
For example,
08 October 2020: Initial publish
20 January 2021: If Db2 is used as the repository database, license Db2 11.5 upgrade is needed
30 June 2021: Added information about Db2 11.5.5.1
04 October 2022: Do not use Updater 11.7.1.105 on Windows, use Updater 11.7.1.095
19 October 2022: Updater 11.7.1.116 and later can be used on Windows
Was this topic helpful?
Document Information
Modified date:
19 October 2022
UID
ibm16333101