Installing and configuring WebSphere 9.0 Network Deployment cluster for use with IBM InfoSphere Information Server 11.7

You can deploy the IBM® InfoSphere® Information Server service application on an IBM WebSphere® Application Server Network Deployment cluster to take advantage of redundancy and high availability.

1. Install IBM WebSphere Application Server Network Deployment on each node that you plan to deploy on the IBM InfoSphere Information Server service tier.
   1. Create the download directory by running the following command:

      mkdir -p <Download directory>

   2. Download the IBM InfoSphere Information Server image IS_V11.7_LINUX_X86_64_MULTILING.tar.gz from Passport Advantage to the location <Download directory>.
      The .tar file includes the IBM WebSphere Application Server Network Deployment installer and the IBM Installation Manager that you use to install it.
   3. Download the license bundle IIS_ENTERPRISE_EDITION_V11.7_BUND.zip from Passport Advantage to the location <Download directory>
      You must use the license bundle to complete the installation of IBM InfoSphere Information Server.
   4. Extract the .tar file by running the following commands:

      cd <Download directory>
      tar -xzvf  IS_V11.7_LINUX_X86_64_MULTILING.tar.gz
      

      The content is now extracted to the directory <Download directory>/is-suite.

   5. Create a response file for the Installation Manager to use to install IBM WebSphere Application Server Network Deployment.
      The IBM WebSphere Application Server Network Deployment response file must be in the format of the following file with the values corresponding to your environment:

      <Download directory>/is-suite/payloads/Shared/WAS/payload/WAS/response.xml

   6. Run the Installation Manager client with appropriate parameters to install IBM WebSphere Application Server Network Deployment by using the response.xml file that you created on the InfoSphere Information Server services tier nodes.

      <Download directory>/is-suite/payloads/Shared/WAS/payload/WAS/agentInstaller/tools/imcl -acceptLicense -showProgress -silent -input <IBM WebSphere Application Server Network Deployment response file>  -log /tmp/WebSphereInstall.log,env=null,workingDir=<Download directory>/is-suite/payloads/Shared/WAS/payload/WAS/agentInstaller/tools

2. Install the WebSphere network deployment manager on a separate node.
   1. Create the download directory by running the following command:

      mkdir -p <Download directory>

   2. Either copy the .tar file that you downloaded in step 1.b over to the directory <Download directory> or go to Passport Advantage and download the IBM InfoSphere Information Server .tar file for your installation. The .tar file includes the IBM WebSphere Application Server Network Deployment installer and the IBM Installation Manager that you use to install it.
   3. Download the license bundle that is based on your entitlement from Passport Advantage.
      This bundle is required for IBM InfoSphere Information Server installation.
   4. Extract the .tar file by running the following commands:

      cd <Download directory>
      tar -xzvf  IS_V11.7_LINUX_X86_64_MULTILING.tar.gz
      

   5. Install the IBM WebSphere Application Server Network Deployment deployment manager on this node by running the following commands:

      <Download directory>/is-suite/payloads/Shared/WAS/payload/WAS/agentInstaller/tools/imcl install com.ibm.websphere.ND.v90_9.0.4.20170523_1327 com.ibm.java.jdk.v8_8.0.5005.20171115_0613 -repositories <Download directory>/is-suite/payloads/Shared/WAS/payload/WAS -installationDirectory <WAS installation directory>/Dmgr -sharedResourcesDirectory /opt/IBM/IMShared -acceptLicense -showProgress -prompt

3. Create the management profile for the deployment manager (dmgr).
   1. Run the following command on the node where you installed the WebSphere Network Deployment Manager.
      It might take a minute or two to finish running.

      <WAS installation directory>/Dmgr/bin/manageprofiles.sh -create -templatePath <WAS installation directory>/Dmgr/profileTemplates/dmgr/ -isDefault -profileName dmgr -adminUsername wasadmin -adminPassword <your password>

   2. Start the deployment manager by running the following command:

      <WAS installation directory>/Dmgr/profiles/dmgr/bin/startManager.sh

      The file <WAS installation directory>/Dmgr/profiles/dmgr/logs/AboutThisProfile.txt is created. The file indicates the port numbers to use for the admin console. You can find the logs in the directory <WAS installation directory>/Dmgr/profiles/dmgr/logs/dmgr.

4. Create a custom profile for IBM InfoSphere Information Server by running the following command on all the nodes where you installed IBM WebSphere Application Server Network Deployment:

   <WAS installation directory>/AppServer/bin/manageprofiles.sh -create -templatePath <WAS installation directory>/AppServer/profileTemplates/managed/ -profileName InfoServer -dmgrHost <your dmgr node> dmgrPort 8879 -adminUserName wasadmin -adminPassword your password

   The file <WAS installation directory>/AppServer/profiles/InfoServer/logs/AboutThisProfile.txt is created. The file indicates which app node the profile is created in.

5. Create a cluster and cluster members.
   1. Log in to the WebSphere administration console by using the secure port for the deployment manager and the user name<was admin UserName>. An example is https://<hostname>:9043/ibm/console/.
   2. Click Servers > Clusters > WebSphere application server clusters > New in the administrative console and specify a cluster name. Then, click Next.
   3. Specify a name in the Member name field, then select the first server in the node. Then, click Next.
   4. Specify a member name for the second node, select that node from the drop-down menu, then click Add member. When both nodes are listed in the window, click Next.
      The Create a new cluster summary window appears. Click Finish.
   5. Click Review and select Synchronize changes with nodes, then click Save. Check that you now have a new cluster in stopped status. Then, select the cluster and click Start.
   Check that the dmgr Java process is now running on the deployment manager node. On the other nodes, check that the two Java processes are running, for example, a node agent and the application sn-1 or sn-2.
6. Install IBM HTTP Server.

   IBM HTTP Server distributes the incoming request to the services tier. IBM HTTP Server must be installed on its own server. IBM HTTP Server is not provided as part of the IBM InfoSphere Information Server installer.

   The IBM InfoSphere Information Server install is-suite file is needed on the IBM HTTP Server node to be able to run imcl commands to install IBM HTTP Server and the IBM HTTP Server WebSphere plug-in.

   1. Create the download directory by running the following command:

      mkdir -p <Download directory>

   2. Either copy the .tar file that you downloaded in step 1.b over to the directory <Download directory> or go to Passport Advantage and download the IBM InfoSphere Information Server .tar file for your installation. The .tar file includes the IBM WebSphere Application Server Network Deployment installer and the IBM Installation Manager that you use to install it.
   3. Download the license bundle that is based on your entitlement from Passport Advantage. This bundle is required for IBM InfoSphere Information Server installation.
   4. Extract the .tar file by running the following commands:

      cd <Download directory>
      tar -xzvf  IS_V11.7_LINUX_X86_64_MULTILING.tar.gz
      

      The content is extracted to the directory <IBM HTTP Server download directory>/is-suite.

   5. Create the download directory by running the following command:

      mkdir -p <Download directory>

   6. Download the two compressed files for IBM HTTP Server and the IBM HTTP Server WebSphere plug-in that are for the version of IBM WebSphere Application Server Network Deployment that you installed earlier in this procedure. You download the files from Passport Advantage.
   7. Extract the files to the directory <IBM HTTP Server download directory>.
   8. Create a response file that can be used by the Installation Manager.
      The IBM HTTP Server response file must be in the format of the following example with values that correspond to your environment:

      <Download directory>/wassupp/responsefiles/samples/WASv90.ihs.install.xml

   9. Install IBM HTTP Server by running the following command:

      <Download directory>/is-suite/payloads/Shared/WAS/payload/WAS/agentInstaller/tools/imcl -acceptLicense -input <IBM HTTP Server response file> -log /tmp/HTTPServer_install_log

7. Install the IBM HTTP Server WebSphere plug-in.
   1. Create a response file that can be used by the Installation Manager.
      The IBM HTTP Server WebSphere plug-in response file must be in the format of the following example with values that correspond to your environment:

      <Download directory>/wassupp/responsefiles/samples/WASv90.plg.install.xml

   2. Install the IBM HTTP Server WebSphere plug-in by running the following command:

      <Download directory>/is-suite/payloads/Shared/WAS/payload/WAS/agentInstaller/tools/imcl -acceptLicense -showProgress input <IBM HTTP Server WebSphere plug-in response file> -log /tmp/WASPlugin_install_log

      This plug-in enables IBM HTTP Server to direct requests to the WebSphere Application Server nodes. The plug-in comes in the same supplemental package as IBM HTTP Server.

8. Configure and start the IBM HTTP Server administration server.
   1. Create the user and the group for the IBM HTTP Server administration server by running the following command:

      <Web server installation location>/bin/setupadm -create -usr ihsadmin -grp ihsgrp -cfg  <Web server installation location>/conf/httpd.conf -adm <Web server installation location>/conf/admin.conf 

   2. Set the administration password by running the following command:

      <Web server installation location>/bin/htpasswd -b -c <Web server installation location>/conf/admin.passwd ihsadmin <your password>

   3. Edit the file <Web server installation location>/conf/admin.conf and change both instances of the string @@AdminPort@@ to the port 8008.
   You can now start the HTTP Admin Server with the following command:

   <Web server installation location>/bin/adminctl start

9. Add IBM HTTP Server to the WebSphere cluster.
   1. Log in to the WebSphere administrative console.
   2. Create a node by clicking System administration > Cell > Nodes > Add node > Unmanaged node > Next.
   3. Specify a name for the new node in the Name field, then enter the fully qualified host name of the IBM HTTP Server node in the Host name field. Then, click OK
   4. Review the information on the addition of the new node, select Synchronize changes with nodes, then click Save.
   5. Click Servers > Server Types > Web servers > New.
   6. Select the node that you just created, then enter the server name <HTTP server name>, for example, httpserver1.
   7. Select IBM HTTP Server from the Type drop-down menu, then click Next.
   8. Leave the default web server template selected, then click Next.
   9. Enter the properties for the new web server.

      Port

      The default value is 80. If IBM HTTP Server is running on a different port, then specify the port number in this field.

      Web server installation location

      The default location is /opt/IBM/HTTPServer. If your location is different, then specify it in this field.

      Plug-in installation location

      The default location is <WAS installation directory>/Plugins. If your location is different, then specify it in this field.

      Administration Server Port

      The Administration Server Port field is auto-filled with the value 8008.

      Username

      The username is the HTTP Admin User that you created earlier, for example, ihsadmin.

      Password

      The password is the one that you created earlier for the HTTP Admin User.

   10. Click Next. Then, review the web server definition and click Finish.
       A confirmation window appears. Click Review.
   11. Select Synchronize changes with Nodes in the web servers window, then click Save.
       The newly added web server appears in the list of nodes.
10. Enable administration security for IBM WebSphere Application Server Network Deployment.
    By default IBM WebSphere Application Server Network Deployment administration is not secure. Global security must be enabled in IBM WebSphere Application Server Network Deployment for IBM InfoSphere Information Server to be installed.
    1. Log in to IBM WebSphere Application Server Network Deployment https://<hostname>:9043/ibm/console by using the IBM WebSphere Application Server Network Deployment administrator user name.
    2. Click Security > Global security and select Security Configuration Wizard.
    3. Select Enable application security in the Specify extent of protection window. Then, click Next.
    4. Select Federated repositories in the Select user repository window. Then, click Next.
    5. Enter the administrator user name, for example wasadmin, and password in the Configure federated repository window. Then, click Next.
    6. Review the summary, then click Finish.
       A confirmation window appears. Click Review.
    7. Select Synchronize changes with Nodes in the web servers window, then click Save.
    8. Restart the WebSphere Deployment Manager by running the following commands on the dmgr node:

       <WAS installation directory>/Dmgr/bin/stopManager.sh
       <WAS installation directory>/Dmgr/bin/startManager.sh
       

    9. Restart the node agents on both service nodes by running the following commands:

       <WAS installation directory>/AppServer/profiles/InfoServer/bin/stopNode.sh     
       <WAS installation directory>/AppServer/profiles/InfoServer/bin/startNode.sh 
       

11. Create a group that is named was_admins with all roles and assign the wasadmin user to the was_admins group by completing the following steps.

    During the installation of IBM InfoSphere Information Server, the cluster is stopped and started several times during the deployment of the apps. The wasadmin user that was created earlier in this procedure does not have that authority by default. You must either create a user that has authority to stop and start the cluster and use it during the IBM InfoSphere Information Server installation, or grant the authority to the wasadmin user and have that user stop and start the cluster.

    1. Click Users and Groups > Manage Groups, then click Create.
       The Manage Groups window appears.
    2. Enter was_admins in the Group name field, along with an optional description in the Description field, then click Create.
       The group is created.
    3. Go to Users and groups > Administrative group roles.
       The Administrative group roles window appears.
    4. Click Add, then in the next window, select all of the roles that are listed in the Roles box.
    5. Enter was* in the Search string field, then click Search. Then, select the was_admins group that appears in the results. Click the arrow icon that points to the Mapped to role box. The group is moved over. Then, click OK.

       The was_admins group with all roles that are assigned to it appears in the section Administrative group roles.

    6. Review the information and then synchronize as you did earlier in the procedure.
    7. Click Manage Groups, click the "was admins" group, click the Members tab, then click Add Users.
    8. Click Search, select the wasadmin user from the list, then click Add.
       A message confirms that the users were added successfully to the group.
    9. Click Close.
12. Generate and propagate the plug-in.
    1. Click Servers > Server Types > Web servers in the IBM WebSphere Application Server Network Deployment administrative console.
    2. Select the IBM HTTP Server that you created earlier in this procedure, for example, httpserver1, then click Generate Plug-in.
    3. Run the following commands on the IBM HTTP Server node to prepare to propagate the plug-in to the IBM HTTP administration server:

       mkdir <WAS installation directory>/Plugins/config/httpserver1
       chown -R ihsadmin:ihsgrp <IBM HTTP Server WebSphere plug-in installation directory>/config/httpserver1

       where ihsadmin is the IBM HTTP Server administration user and ihsgrp is the IBM HTTP Server administration group that you created earlier in this procedure.
    4. Select the server httpserver1 that you created earlier in the procedure in the list of web servers, then click Propagate Plug-in.
       After a few seconds, the plug-in path is shown.
    5. Set the write permissions by running the following command:

       
       chmod a+w <WAS installation directory>/config/httpserver1/plugin-cfg.xml

13. Enable SSL for the plug-in.
    1. Click Servers > Server Types > Web Servers > httpsserver1 > Plug-in properties. Then, click Copy to Web Server key store directory, then click OK. Then, review the changes, select Synchronize changes with nodes, then click Save.
       The following files are created:

       • KeyFile <WAS installation directory>/Plugins/config/httpserver1/plugin-key.kdb
       • SSLStashFile <WAS installation directory>/Plugins/config/httpserver1/plugin-key.sth

       The default password is WebAS.

14. Configure IBM HTTP Server.
    1. Add a virtual host for the default port of <HTTP server port>, or the host that you are using instead of the default, to the file <Web server installation location>/conf/httpd.conf. See the following example:

       LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
       Listen *:<HTTP server port>
       <VirtualHost *:HTTP server port>
       SSLEnable
       </VirtualHost>
       KeyFile <WAS installation directory>/Plugins/config/httpserver1/plugin-key.kdb
       SSLStashFile <WAS installation directory>/Plugins/config/httpserver1/plugin-key.sth
       SSLDisable
       

    2. Add the following two lines to the same file:

       LoadModule was_ap22_module <WAS installation directory>/Plugins/bin/64bits/mod_was_ap22_http.so
       WebSpherePluginConfig <WAS installation directory>/Plugins/config/httpserver1/plugin-cfg.xml
       

    3. Verify that the SSL certificate that is in the file <IBM HTTP Server WebSphere plug-in installation directory>/config/httpserver1/plugin-key.kdb is the default certificate by running the following command:

       <IBM HTTP Server installation location>/bin/gskcapicmd -cert -list -db <WAS installation directory>/Plugins/config/httpserver1/plugin-key.kdb -pw WebAS

       Look for a result that is similar to the following example to confirm that the step worked:

       Certificates found
       * default, - personal, ! trusted, # secret key
       ! "CN=v9was-dmgr.fyre.ibm.com, OU=Root Certificate, OU=v9was-dmgrCell01, OU=v9was-dmgrCellManager01, O=IBM, C=US"
       - default

    4. Stash the password by running the following command:

       <IBM HTTP Server installation location>/bin/gskcapicmd -keydb -stashpw -db <WAS installation directory>/Plugins/config/httpserver1/plugin-key.kdb -pw WebAS

       You can see the URL redirection by changing the log-level in the file <WAS installation directory>/Plugins/config/httpserver1/plugin-cfg.xml. Change LogLevel="Error" to either "Stats" or "Detail", then run the following commands:

       mkdir <WAS installation directory>/Plugins/logs/httpserver1
       chown -R ihsadmin:ihsgrp /<WAS installation directory>/Plugins/logs/httpserver1/
       

    5. Start the HTTP Server by running the following command:

       <IBM HTTP Server installation location>/bin/apachectl start

       During the installation of IBM InfoSphere Information Server, if the system requirements check indicates that the SDK level needs changes, edit the following file:

       /tmp/wasconfig.properties