IBM Support

Instructions for Suite install of IBM InfoSphere Information Server 11.7.1.3

How To


Summary

Instructions for setting up a new installation of Information Server 11.7.1.3.

Information Server 11.7.1.3 can be installed on any of the supported platforms.

Starting with Information Server 11.7.1.0, in addition to Information Server Enterprise Search (ISES), the master node (ISES) host contains other microservices and is called the Microservices tier.

You should install the Microservices tier if you plan to use any of the following features:
1. Information Server Enterprise Search
2. the new Information Governance Catalog and Information Analyzer console

These instructions can be used to install Information Server 11.7.1.3 with or without a Microservices tier.

Objective

Set up a new installation of Information Server 11.7.1.3 with or without a Microservices tier.

Environment

Information Server 11.7.1.3 can be installed on all supported platforms.

For the Information Server host system and the Microservices tier, ensure that your system meets the requirements listed in Information Server 11.7.1 System requirements.
Refer to the pre-installation checklist while checking your system.

Using Db2 as the repository database

You can  use the Information Server 11.7.1.3 installation program to install Db2 11.5, or preinstall Db2 11.5. Db2 11.1 is not supported.

Using WebSphere Application Server Network Deployment

You may preinstall WebSphere Application Server Network Deployment version 9.0.5.6 or later, or have it installed by the Information Server 11.7.1.3 installation program.


Microservices tier system requirements and configuration

Disk space requirements
Disk space requirements are documented in the System requirements.

Requirements related to single and multiple nodes


You can set up the Microservices tier as a single node or as multiple nodes with a master node and two worker nodes.

The Microservices tier needs to meet the following requirements:

  • Red Hat 7.3 or later
  • Single node: minimum 8 vcpu and 32 GB memory
  • Multiple nodes: minimum 8 vcpu and 32 GB memory on each node
For information on configuring the Microservices tier, see Specifying microservices tier options, 11.7.1.
You can use this pre-installation checklist while setting up the Microservices tier.


Network protocol
 
TLS 1.2 is the default protocol for Information Server 11.7.1.3 installations.
However, communication between the services tier and the repository tier will not be TLS 1.2 by default; it can be changed post-install.
 

Steps


Table of Contents
    1) General installation information
         1.1) Using a password or passwordless SSH for installing the Microservices tier
         1.2) Ports used during Microservices tier installation
         1.3) GIDs and UIDs created during Microservices tier installation
 
    2) Downloads and preinstall actions
 
    3) Installation scenarios
         3.1) Instructions for is-suite installation
                  3.1.1) Installation in GUI mode
                  3.1.2) Installation in Console (silent) mode
 
    4) Post-install actions
          4.1) Remove Governance Monitor icon from launchpad
          4.2) (Optional) Change communication between the services tier and the repository tier to TLS 1.2
          4.3) Disable the Kafka log cleaner
          4.4) Information Server Microservices tier needs an additional key


 
 
1) General installation information
1.1) Provide a password or set up passwordless SSH to install the Microservices tier
        To facilitate the install, you can set up passwordless SSH from a user on the Information Server host to the master node host, as was the case in prior releases.
        However, there are additional installation modes that do not need passwordless SSH to be set up.
        You have four options to choose from when the Microservices tier is installed:

    a. Specify that the root user must 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 must be used on the master node, and don't provide a password.
         You must 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 is used on the master node, and don't provide a password.
         The specified non-root user must have sudo privilege with NOPASSWD enabled.
         You must 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. In all four installation modes, use visudo to update the /etc/sudoers file and add an entry for root:
                       root    ALL=(ALL)       ALL

      2. 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
                    <userid> ALL=NOPASSWD: ALL

      3. In the /etc/sudoers file, there is a "requiretty" setting that can cause the following messages to appear in the Kubernetes deployment log:
              a. A "sudo: sorry, you must have a tty to run sudo" message when sudo is invoked.
              b. While "yum install zip" is running, you may get a message
                        "ERROR: With yum install of zip. You can try to install requirement manually"
                   This error can appear even if zip is installed as needed.

              You will have to disable "requiretty" globally or at a user/group/command level:
                    Replace "Defaults requiretty" with "Defaults !requiretty" in your /etc/sudoers. This will impact your global sudo configuration.
                    Alternatively, you can change this configuration at a per user, per group or per command basis. For example,
                            Defaults!/path/to/my/bin !requiretty
                            Defaults:myuser !requiretty

      4. sudo privilege is only needed for the duration of the install.

      5. 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.
1.2) Ports used during Microservices tier installation
The following ports are used during Microservices tier installation. Please ensure that they are not in use.

HTTP 80
TCP 443 - ingress-nginx-controller
TCP 5000 -- docker
TCP 6443* Kubernetes API Server
TCP 2379-2380 etcd server client API
TCP 10250 Kubelet API
TCP 10251 kube-scheduler
TCP 10248 kubelet
TCP 10249 kube-proxy
TCP 10252 kube-controller-manager
TCP 10255 Read-Only Kubelet API
TCP 30000-32767 NodePort Services
TCP 6783/6784 Weave Services
TCP 9092 Kafka
TCP 2181 zookeeper

1.3) GIDs and UIDs created during Microservices tier installation
The following GIDs and UIDs are created during the Microservices tier installation.
Please make sure that they are available for use. These IDs are created as local OS groups and users.

UG group -  gid=2000
WKC group - gid=3000
kafka_user_uid: 9092
redis_user_uid: 6379
solr_user_uid: 8983
zookeeper_user_uid: 2181
elasticsearch_user_uid: 9200
kibana_user_uid: 5601
grafana_user_uid: 9091
prometheus_user_uid: 9090
cassandra_user_uid: 9042
zookeeper_user_uid: 2181
elasticsearch_user_uid: 9200

You can change the UID and GID only while adding a Microservices tier to an existing Information Server installation. See technote for details.
 

    2) Downloads and preinstall actions

    2.1) On the Information Server host, download the Information Server is-suite image from Passport Advantage.
                 For example, IS_V11713_Linux_x86_multi.tar.gz
                 AIX
                 Linux
                 Windows

    2.2) Extract the image
             Ensure that your umask is set to 022.
                 For example, tar -xvf IS_V11713_Linux_x86_multi.tar.gz

    2.3) On the client tier, download the Information Server client image from Passport Advantage.
             For example, IS_V11.7.1.3_WINDOWS_CLIENT.zip

    2.4) On the Microservices tier host:
     
            Download the Docker image for Information Server 11.7.1.3 from Passport Advantage.
            For example, is-enterprise-search-11.7.1.3.tar.gz
            Do not extract the file.
            Note:
                    Starting in Information Server version 11.7.1.2, Ansible is no longer shipped with the product. This utility is still required for installation of version 11.7.1.2 and future maintenance actions. You can install Ansible version 2.9 in a number of different ways, which are described in the official documentation: https://docs.ansible.com/ansible/2.9/installation_guide/intro_installation.html.
    2.5) Red Hat Enterprise Linux 8 libraries
             Before installing Information Server version 11.7.1.3 on RHEL 8, ensure that your system contains all the libraries required for a successful install. If not, failures may be reported during the Installer's early requirements check.
             For example, you may need the following libraries and any dependencies:
                         libXp, libXau, libXext, libX11, libX11-common, libxcb, libXmu

             You can use yum to list available packages, and install as needed. For example,
                         yum list libXp
                         yum install libXp .x86_64

    2.6) Windows installations must enable TLS 1.2 support in Internet Explorer

             IMPORTANT - This step must be followed even if your using an alternative web browser to Internet Explorer.

    1. Open Internet Explorer.
    2. From the menu bar, click Tools >  Internet Options > Advanced tab.
    3. Scroll down to the security section at the bottom of the Settings.
    4. Enable "Use TLS 1.2".
    5. Save the changes.
    2.7) AIX installations must upgrade OpenSSL
            OpenSSL must be upgraded to version 1.0.2.2102 or later. For example, see AIX Web Download Pack Programs.

     

    3) Installation scenarios
     

    3.1) Instructions for is-suite installation

    If not already done, before installing Information Server 11.7.1.3, see  "Preparing the Information Server 11.7.1 microservices tier node"  for details of the steps needed to set up the Microservices tier. You can use this pre-installation checklist while setting up the Microservices tier.

    You should address "Known issues while installing or upgrading Information Server to version 11.7.1.0" before starting the 11.7.1.3 install.

    3.1.1) Installation in GUI mode

    3.1.1.1) Login to the Information Sever host as the root user (or a user that has all sudo access) and change directory to the folder where is-suite is extracted.
                   To start the install, run the following command

                       <is-suite downloaded path>/.setup

                This will launch the Installer in GUI mode.

                Provide information as required in each panel as shown below.

    3.1.1.2) Click Login.

    welcomepage

    3.1.1.3) Getting started – Click Next.

    image-20211004155546-1

    3.1.1.4) Click Next.

    image-20211004160052-1

    3.1.1.5) Early system requirement – Click Next if all requirements are passed.

    image-20211004160331-3

    3.1.1.6) Select the Installation directory (the installer will automatically display the default install directory). Click Next.

    image-20211004160441-4

    3.1.1.7) Select New Installation and click Next.

    image-20211004160536-5

    3.1.1.8) Select the Tiers you want to install and click Next.

    image-20211004160625-6

    3.1.1.9) Select the products you want to install and click Next.

    image-20211004160722-7

    3.1.1.10) Accept the license and click Next.

    image-20211004161748-1

    3.1.1.11) Click Next, unless you are installing a High Availability installation.

    image-20211004161932-2

    3.1.1.12) Db2 11.5 is bundled in the Information Server install image. You can choose to preinstall Db2 or the Information Server installation program can install Db2 for you.

    If you want the Installer to install DB2 that is bundled with Information Server, click the first radio button. Click Next and go to step 3.1.1.13.
    If you have preinstalled Db2 11.5, click the second radio button to use your existing Db2 instance. Click Next and go to step 3.1.1.12.1.

    image-20211004162025-3

    3.1.1.12.1) Provide the information for your Db2 11.5 instance. Click Next and move to step 3.1.1.16.

    Note: Even though Db2 11.1 is listed, it is not supported. You must point to a Db2 11.5 instance.

    Screenshot 2022-10-07 at 7 05 12 PM

    If you provide a Db2 11.1 instance, an error message will be reported:
    Screenshot 2022-10-07 at 7 06 27 PM

    3.1.1.13) Provide the DB2 installation directory and click Next.

    image-20211004162144-4

    3.1.1.14) Provide the DB2 Instance user name and click Next.

    image-20211004162232-5

    3.1.1.15) Provide the DB2 Fence user name and click Next.

    image-20211004162317-6

    3.1.1.16) Provide the XMETA user name and password. Click Next.

    image-20211004162402-7

    3.1.1.17) Provide the XMETASR user name and password and click Next.

    image-20211004162446-8

    3.1.1.18) Select the WebSphere Application Server Installation type. For WebSphere Network Deployment, you may choose to have it installed, or use an existing installation. Click Next.

    image-20211004162734-9

    3.1.1.19) Provide the WebSphere Application Server Network Deployment installation directory and click Next.

    image-20211004162818-10

    3.1.1.20) Examine the ports that will be used by WebSphere and customize as needed. Click Next.

    image-20211004162859-11

    3.1.1.21) Provide the WebSphere Application Server user name and password. Click Next.

    image-20211004162935-12

    3.1.1.22) Provide the Information Server user name and password. Click Next.

    image-20211004163031-13

    3.1.1.23) Select Next to use the default ports for Connector Access Services.
                      If any of the specified ports are in use, you may accept the currently specified range or modify the specified range. Click Next.

    image-20211004163327-14

    3.1.1.24) Specify the Agent port and click Next.

    image-20211004163412-15

    3.1.1.25) Provide the DataStage Administrator user name and password. Click Next.

    image-20211004163450-16

    3.1.1.26) Select the TCP/IP ports. Click Next.

    image-20211004163547-17

    3.1.1.27) Select the ITAG for Engine tier instance and click Next.

    image-20211004163627-18

    3.1.1.28) Select Install globalization support and click Next.

    image-20211004163701-19

    3.1.1.29) Click Next.

    image-20211004163739-20

    3.1.1.30) Click Next.

    image-20211004163815-21

    3.1.1.31) Select the default dstage1 project and click Next.

    image-20211004163853-22

    3.1.1.32) Provide the IAUSER user name and password. Click Next.

    image-20211004163955-23

    3.1.1.33) If you do not intend to use Information Server Enterprise Search or the new Information Governance Catalog and Information Analyzer console you can skip installation of the Microservices tier:
                       Select the checkbox "Skip installation of Information Server microservices tier".
                       Click Next and skip forward to step 3.1.1.35.

    no_ms

    3.1.1.34) Installation of the Microservices tier

    3.1.1.34.1) Provide the information needed to install the Microservices tier:

    a. See the "Microservices tier system requirements and configuration" section of this document for details.
    b. For details on the "Authenticate with a password" box shown below, see section 1.1.
    c. For the Persistent Storage location, specify a directory on a local file system that has at least 300 GB of free disk space; do not specify a device location.

    Click Next.
    image-20211004165134-25

    image-20211004165255-26

    3.1.1.34.2) If you specified more than one node, you can specify the hosts for the worker nodes. Click Next.

    image-20211004165420-27

    image-20211004165459-28

    3.1.1.35) Provide credentials to be used for Kafka and Solr (for example, solruser, solrpwd etc).
                   The Suite Installer will create 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.

    image-20211004165602-29

    3.1.1.36) Provide Operation Database Configuration user name and password, or skip the step and you can configure them subsequently. Click Next.

    image-20211004165650-30

    3.1.1.37) Select the DataStage Edition options as appropriate and click Next.

    image-20211004165814-31

    3.1.1.38) Ensure that all system requirements are passed and click Next.

    image-20211004170139-33

    3.1.1.39) Examine the results from system requirement checks of the Microservices tier. If all is good, click Next.

    image-20211004172229-35

    3.1.1.40) You can choose to generate a response file or proceed with the install. Click Next.

    image-20211004172402-36

    3.1.1.41) Check the Preinstallation Summary and click Install to start the install.

    image-20211004172436-37

    3.1.1.42) Click Finish to complete the install.

    image-20211004172540-38

    3.1.1.43) Click “Advanced” and "Proceed to <machine name>".

    image-20211004172632-39

    3.1.1.44) Click the link "Proceed to <machine name>".

    image-20211004172802-40
     

    3.1.1.45) If any failure occurs during installation of the Microservices tier, an Installer exception is displayed with three options to select from

    •   Retry
    •   Continue
    •   Exit

    If the error reported is the same as in the following screen capture, choose the Continue option to complete the installation.

    Screen Error


    3.1.1.46) The Launchpad is displayed.

    3.1.1.46.1) If Information Server was installed without the Microservices Tier,  the Information Sever Launchpad is displayed.
    Subsequently, you can open the Information Server Launchpad by using url <Information Server hostname>:port/ibm/iis/launchpad

    image-20211004173519-42

    3.1.1.46.2) If you installed a Microservices tier, the Information Server (Microservices) Launchpad is displayed.

    image-20211004173019-41

     
    3.1.2) Installation in Console (silent) mode

    3.1.2.1) Login to the Information Server host. Change directory to <is-suite downloaded build path>/is-suite
                   For example, cd /opt/Builds/is-suite

    3.1.2.2) Prepare the response file.
    It is a best practice to first generate a response file, and then use it while installing.
    The response file can be generated by running the Suite installer in GUI mode, and clicking the "Cancel" button in the "Preinstallation Summary" screen.
    Edit the response file, providing password values and changing any values that are specific for the computer that you are installing the software on:

    • You can edit the following sample response file to install Information Server without a Microservices tier

                   Sample response file without a Microservices tier

    • You can edit either of the following sample response files to install Information Server with a single node or multiple nodes Microservices tier

                   Sample response file for single node
                   Sample response file for multiple nodes

    3.1.2.3) Run the Installer.
                   ./setup -rsp /opt/Builds/response.txt -verbose



     

     
    4) Post-install instructions

    4.1) Remove Governance Monitor icon from launchpad
             If the Governance Monitor icon is displayed in the Microservices tier launchpad, remove it by doing the following steps.
            
    4.1.1) Unset corresponding iisAdmin keys:
           a) /opt/IBM/InformationServer/ASBServer/bin/iisAdmin.sh -unset -key com.ibm.iis.launchpad.application.govmon.name
           b) /opt/IBM/InformationServer/ASBServer/bin/iisAdmin.sh -unset -key com.ibm.iis.launchpad.application.govmon.url
           c) /opt/IBM/InformationServer/ASBServer/bin/iisAdmin.sh -unset -key com.ibm.iis.launchpad.application.govmon.icon
    4.1.2) Restart WebSphere Application Server.

    4.2) (Optional) Change communication between the services tier and the repository tier to TLS 1.2
           You can use the following technotes depending on your repository type:
           

    4.3) Disable the Kafka log cleaner
             If a Microservices tier is not installed, the Kafka log cleaner must be disabled as follows:
                    a) edit kafka/conf/server1.properties
                    b) search the log cleaner property and set it to false: log.cleaner.enable=false
                    c) restart the services
             The logs are deleted because the cleanup.policy is set to delete. Also, after 7 days, the logs are auto deleted because log.retention.hours is set to 168 hours.

    4.4) Information Server Microservices tier needs an additional key
             If you installed a Microservices tier,  run the following commands on your services tier
                 $ cd <IIS_INSTALL_LOCATION>/ASBServer/bin
                 $ ./iisAdmin.sh -set -key com.ibm.iis.ug.installed.version -value 11713


    History
    29 October 2021: Initial publish
    10 November 2021: fixed AIX link for Passport Advantage
    07 January 2022: Information Server Microservices tier needs an additional key
    12 April 2022: 11.7.1.3 suite installation supports only Db2 11.5
    10 October 2022: Only Db2 11.5 is supported even though Db2 11.1 is listed in drop down choices for preinstalled repository
    03 November 2022: Fix typographical error in step 4.3 and clarify log cleanup

    [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"InfoSphere Information Server"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"11.7.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

    Document Information

    Modified date:
    03 November 2022

    UID

    ibm16489295

    Page Feedback