IBM Support

Instructions for installing IBM InfoSphere Information Server 11.7.1.1 Service Pack 1

Fix Readme


Abstract

This readme document contains guidance for installation of the IBM InfoSphere Information Server 11.7.1.1 Service Pack 1 upgrade package available on IBM Fix Central.

Content

Table of Contents
    1) Introduction
    2) 11.7.1.1 Service Pack 1 installation using a password and/or passwordless SSH
    3) Downloads and pre-Upgrade steps
    4) Installation of 11.7.1.1 Service Pack 1
           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


1) Introduction

The IBM InfoSphere Information Server 11.7.1.1 Service Pack 1 ispkg image is available for upgrading of Information Server version 11.7.1.1 installations. The steps for installing Information Server 11.7.1.1 Service Pack 1 depends on whether the Microservices tier is installed.

Before upgrading to version 11.7.1.1 Service Pack 1:

  • you should have Information Server version 11.7.1.1 installed
  • if you have a Microservices tier, it must be at version 11.7.1.1 and all pods must be up and running

     

2) 11.7.1 Service Pack installation using a password and/or passwordless SSH

2.1)  If you initially installed Enterprise Search in Information Server versions 11.7.0.0 through 11.7.0.2, such installations required
              a.  a user with root privileges on the master node
              b.  setting up passwordless SSH from the user running the install on the Information Server host to the master node
              c.  setting up passwordless SSH for the root user between the master node and itself

          While applying Information Server 11.7.1.1 Service Pack 1, you can continue to use your current setup. If it is as described above, no changes are needed to facilitate the install.

          However, additional installation behavior is supported that you may want to take advantage of:
              a.  You are no longer required to set up passwordless SSH for the root user between the master node and itself.
              b.  In some installation modes, you do not have to set up any passwordless ssh.
          See the next section for details.

2.2) Installation modes available while upgrading the Microservices tier
 
You can choose between four installation modes while upgrading the Microservices tier:
 
     a. Specify that the root user will be used on the master node, and provide the password and sftp port.
         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.
 
    b. Specify a non-root user to be used on the master node, and provide the password and sftp port.
         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 install 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. you must set up passwordless SSH for the specified non-root user from the master node to the worker nodes
  
    c. Specify that the root user will be used on the master node, and don't provide a password.
         You should set up passwordless SSH from the user running the install 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.
 
    d. Specify that a non-root user will be used on the master node, and don't provide a password.
         The specified non-root user must have sudo privilege with NOPASSWD enabled.
         You should set up passwordless SSH from the user running the install 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
Note:
        1. To enable NOPASSWD for the non-root user, use visudo to append " ALL=NOPASSWD: ALL" to the user's entry in the /etc/sudoers file, or add a new entry.
            The resulting line should be
                  ALL=(ALL) NOPASSWD: ALL
                     
        2. If the root user was used during the version 11.7.0.x install, then the root user should also be used while applying a  11.7.1.1 Service Pack 1.
 
        3. Sample setup of passwordless SSH connection for a root user to the Microservices Tier node.
             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 and pre-upgrade steps

3.1) Download the latest Update Installer

        Update the Update Installer to the latest (11.7.1.085 or later):

        3.1.1) On the Information Server host, download the Update Installer from
                    http://www.ibm.com/support/docview.wss?uid=swg24038034

        3.1.2) In the document, Updating IBM InfoSphere Information Server, Version 11.7, and installing additional products, under Version 11.7, click the link installing_fixes_fixpacks_updates117.html.
        3.1.3) See section “Installing a new version of the Update Installer before installing an update, fix, or patch” for the steps to extract the new Update Installer and run updateImage.sh.
                    If you used the default directory for Information Server, the Update Installer will install in /opt/IBM/InformationServer/Updates/bin.

3.2) Download the 11.7.1.1 Service Pack 1 images
        You should download the following images from IBM Fix Central depending on your installation choices.
        For details on locating the images, see the Download document

3.2.1) On the Information Server host, download and extract the Information Server 11.7.1.1 Service Pack 1 ispkg image from IBM Fix Central.
            For example, servicepack_11.7.1.1_SP1_linux64_11711.tar.gz
            Note:
                         1. Your umask should be set to 022 before extracting the image.
                         2. Unpack the file to get the ispkg and README files.

3.2.2) On the Microservices tier, download  the ISES Image for Information Server 11.7.1.1 Service Pack 1 from IBM Fix Central. Do not extract the file.
            For Service Pack 1, servicepack_11.7.1.1_SP1_microservices_11711.tar.gz

3.3) Pre-upgrade steps
3.3.1) The Metadata needed for the Information Analyzer microservice is persisted in a schema named 'ASSET_RELATION'. If you have not created the schema previously, this schema needs to be created prior to installing the Service Pack. The steps to create the schema are mentioned in the resolution section of  Technote 0887665. Absence of the schema will cause the ia-services pod to crash.

3.3.2) Ensure that your system meets all system requirements for Service Pack 1 installations. For example, the requirements for slirp4netns and fuse-overlayfs have changed.

 

4) Installation of 11.7.1.1 Service Pack 1

 

4.1) Instructions for upgrading Information Server in GUI mode of the Update Installer


4.1.1) Login 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.085 or later:
                  ./installUpdates -version

4.1.3) Initiate the Service Pack install with the following command:
                   ./installUpdates
              This will launch the Update Installer in GUI mode.

4.1.4) Provide information as required in each panel to complete the install.
               Click Login.

image 8891


 4.1.5) Review the System requirements, Release Notes and Planning information.
             Click Next.

image 8892

4.1.6) The Update Installer will display the Information Server installation directory.
              Click Next.

image 8893


4.1.7)  If you do not have a Microservices tier, skip forward to step 4.1.8.
             Note: Information on adding a Microservices tier to 11.7.1.1 Service Pack 1 can be found in Technote 6241456.

4.1.7.1)  You can choose whether to upgrade the Microservices tier while installing 11.7.1.1 Service Pack 1.
                 Note that in order to upgrade:
                         1. The Microservices tier must be at version 11.7.1.1.
                         2. All pods should be up and running.
                              You can check the status of the pods by running the following command:
                                      kubectl get pods --all-namespaces

4.1.7.2) If you do not want to upgrade the Microservices tier at this time, check the "Skip patching of Information Server microservices tier" checkbox.
                Click Next and skip forward to step 4.1.8.
                Information on subsequently upgrading your Microservices tier to 11.7.1.1 Service Pack 1 can be found in Technote 6241456.

skip1

4.1.7.3) To upgrade the Microservices tier
                  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 install of the Microservices tier.
                  d. For details 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 should be 10240.
                       Also, umask should be set to 022 in ~/.bashrc.

                 Click Next.
  
image 8894

4.1.8) In the list of "Packages to be installed", select the 11.7.1.1 Service pack 1 ispkg file you downloaded from IBM Fix Central.
Click Next.

image 8895
 

4.1.9) Provide your existing credentials for Kafka and Solr (for example, solruser, solrpwd etc). These are the credentials that you previously specified while installing or upgrading to the version 11.7.1.1 Microservices tier.
           Click Next.

image 8896


4.1.10) Provide the location of Information Server, the Administrator user name and password. Accept the certificate and click Next.

image 8897


4.1.11) On the System Requirements Check page, confirm that all system requirements passed, and then click Next.

image 8898

4.1.12) If you have a Microservices tier, examine the results from system requirement checks of the Microservices tier. If all is good, click Next.

image 8899

image 8900


4.1.13) Review the Preinstallation Summary and click the Install button to start the installation.

image 8901

4.1.14) Click the Finish button after the installation completes.

image 8902

4.1.15) Click “Advanced” followed by "Accept the Risk and Continue".

af1

af2


4.1.16) The Launchpad will be displayed.

4.1.16.1) If you do not have a Microservices tier, you will see the Information Sever Launchpad.

af4
 

4.1.16.2) If you have a Microservices tier, you will see the Information Sever (Microservices) Launchpad.

af3


4.2) Instructions for upgrading Information Server in Console mode of the Update Installer

            Note:
             1. The Microservices tier should be at version 11.7.1.1 prior to installing Service Pack 1.
             2. The validation checks performed by the Update Installer while running in Console mode are not as extensive as the checks when the Update Installer is run in GUI mode.


4.2.1) Login to the Information Server host. Change directory to <IS_HOME>/Updates/bin
              For example, cd /opt/IBM/InformationServer/Updates/bin

4.2.2) Verify that the Update Installer version is 11.7.1.085 or later:
                   ./installUpdates -version
               See step 3.1 if you need to update the Update Installer.

4.2.3) 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
                                                       For example,  servicepack_11.7.1.1_SP1_linux64_11711.tar.gz
                  <property_file_name> is the name of the property file wherein you specify values for the various properties that control the upgrade of the Microservices tier.

Sample property file

               The Update Installer will prompt you for the Information Server administrator user id and password, and the WebSphere Administrator user id and password.


5) Post upgrade actions

5.1) Docker upgrade

Due to the way in which Docker and Kubernetes services interact with each other, the Docker upgrade is not done automatically while upgrading the Microservices tier to 11.7.1.1 Service Pack 1.
You can upgrade Docker by following the instructions in Technote 6217329.
5.2)  Information Server Microservices tier launchpad and Administration console may intermittently fail
While applying the service pack in an installation with WAS version 9.0.0.7 or lower, opening of the Information Server Microservices tier launchpad or Administration console may intermittently fail with the following exception in the browser:
      
         Error 404:com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException:
               No target servlet configured for uri:/ibm/iis/launchpad
         Error 404:com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException:
               No target servlet configured for uri:/ibm/iis/console
      
 Such errors can be resolved by appending the following jars in the Ignore-Scanning-Archives  section of WAS_INSTALL_LOCATION/AppServer/properties/amm.filter.properties.
Append a comma, space  and backward slash (similar to as shown in the lines below) to the existing list and also add the following lines:
 
             jackson-annotations-2.12.1.jar,  \
             jackson-core-2.12.1.jar,  \
             jackson-databind-2.12.1.jar,  \
             log4j-api-2.11.2.jar
        
 Restart WAS after saving the file.
5.3) Information Server Microservices tier launchpad does not display icons properly

If JR62814 is applicable to your environment, do the following steps on your relevant tiers.
 
        On the Microservices tier host:
 
        1. Modify the iis-server Ingress
             a. kubectl edit Ingress iis-server
             b. Locate the following lines
                     ingress.kubernetes.io/configuration-snippet: |
                     proxy_redirect "https://$host:<IIS services tier port>/" "https://$host/";
             c. After the above lines, insert proxy-redirect directives for short host name, alias name, and IP address:
                     proxy_redirect "https://<Microservices tier short host name>:<IIS services tier port>" "https://<Microservices tier short host name>/";
                     proxy_redirect "https://<Microservices tier host name alias>:<IIS services tier port>" "https://<Microservices tier host name alias>/";
                     proxy_redirect "https://<Microservices tier IP address>:<IIS services tier port>" "https://<Microservices tier IP address>/";
                 Ensure that the newly added proxy_redirect lines are properly aligned with the prior proxy_redirect line as consumption of the file contents is very sensitive to the formatting.
             d. Save this ConfigMap.
 
        2. Modify the iis-redirect Ingress
             a. kubectl edit Ingress iis-redirect
             b. Locate the following lines
                     ingress.kubernetes.io/configuration-snippet: |
                     proxy_redirect "https://$host:<IIS services tier port>/" "https://<IIS services tier short host name>:<IIS services tier port>/";
             c. After the above lines, insert proxy-redirect directives for short host name, alias name, and IP address:
                     proxy_redirect "https://<Microservices tier short host name>:<IIS services tier port>" "https://<IIS services tier short host name>:<IIS services tier port>/";
                     proxy_redirect "https://<Microservices tier host name alias>:<IIS services tier port>" "https://<IIS services tier host name alias>:<IIS services tier port>/";
                     proxy_redirect "https://<Microservices tier IP address>:<IIS services tier port>" "https://<IIS services tier IP address>:<IIS services tier port>/";
                 Ensure that the newly added proxy_redirect lines are properly aligned with the prior proxy_redirect line as consumption of the file contents is very sensitive to the formatting.
             d. Save this ConfigMap.
 
        3. Delete nginx ingress pod using the following command:
                 kubectl delete pods -l app=ingress-nginx -n kube-system
 
        4. Ensure that nginx ingress pod is up and running using the following command:
                 kubectl get pods -l app=ingress-nginx -n kube-system
              
        On the Information Server host:

        1. Add a host alias property:
             $ cd <IIS_INSTALL_LOCATION>/ASBServer/bin
             $ ./iisAdmin.sh -set -key com.ibm.iis.ug.host.aliases -value
                  <Microservices tier long host name>,<Microservices tier short host name>,<Microservices tier alias name>,<Microservices tier IP address>
             $ ./iisAdmin.sh -d -key com.ibm.iis.ug.host.aliases
        2. Restart WAS.
               
        On the Browser host:

        You should add an entry in the hosts file
                UNIX:         /etc/hosts
                Windows: <Drive>:\Windows\System32\drivers\etc\host on Windows)
         with IP address, long host name, short host name, and alias name as follows:
               <Microservices tier IP address> <Microservices tier long host name> <Microservices tier short host name> <Microservices tier alias name>


Change History:
01 Apr 2021: Initial publication
08 Apr 2021: Added post-install steps 5.2 and 5.3 for Microservices tier launchpad and icons, and Administration console
13 Apr 2021: Added section 3.3.2; ensure that all system requirements are met before installing

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"ARM Category":[{"code":"a8m50000000L32vAAC","label":"Patch Installer-\u003ECumulative Service - Fix Packs and Service Packs"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.7.1"}]

Document Information

Modified date:
13 April 2021

UID

ibm16434773

Page Feedback