Creating and reconfiguring new cluster members

When IBM® InfoSphere® Information Server is installed within a cluster, it configures the cluster with appropriate settings required for proper InfoSphere Information Server operation. When additional cluster members are added, these settings are automatically copied to the new cluster members so that they are properly enabled for use by InfoSphere Information Server. If you remove all members from your cluster, additional manual steps are required to then create new cluster members that are properly configured for use by InfoSphere Information Server.

About this task

To create new cluster members, you use the IBM_Information_Server_template to create the cluster member and, if necessary, you run the reconfigure_was_cluster script to add the required settings.

You can create a cluster by using either the server or cluster option. If you use the server option, all the data sources are propagated properly. If you use the cluster option, then all the key resources will be deleted, and the reconfigure_was_cluster script is used to recover some of the deleted resources, but not all of them. Therefore, it is recommended to use the server option.

Important: The server option is the only option that guarantees that the system is in the proper state.

Follow this task only to add cluster members when all existing cluster members have been removed subsequent to an InfoSphere Information Server installation. However, it is assumed that no other configured InfoSphere Information Server resources have been removed. If any of the following resources have been removed, you must instead reinstall InfoSphere Information Server to restore them.

  • The InfoSphere Information Server shared library:
    Environment > Shared Libraries > IBM_Information_Server_iis
  • The InfoSphere Information Server security domain:
    Security > Security Domains > IBM_Information_Server_sd
  • The actual cluster on which InfoSphere Information Server has been installed:
    Servers > Clusters > WebSphere application server clusters > <cluster_name>
  • The InfoSphere Information Server applications:
    Applications > All applications > <list_of_applications>
    (applications such as isf-launchpad, isf-server-rest2, and isf-servlets)

Procedure

  1. Log in to he IBM WebSphere® Application Server administrative console and select Servers > Clusters > WebSphere application server clusters.
    Select the cluster that currently contains no cluster members.
  2. Begin the process of creating a new cluster member by selecting one of the following options to determine how the server resources are promoted to the cluster:
    • Server - Select this option to maintain the server resources at the new cluster member level. The cluster resources remain unchanged.
    • Cluster - Select this option to move the resources of the first cluster member to the cluster level. The resources of the first cluster member replace the resources of the cluster.
    Note: You would later run the reconfigure_was_cluster script only if you choose the Cluster option.

    For more information on adding new cluster members, see Adding members to a cluster in the WebSphere Application Server documentation.

  3. If you selected the Server option, complete the following steps:
    1. Create a new cluster member by clicking New. Use the WebSphere Application Server administrator credentials.
    2. Start the cluster by navigating to Servers > Clusters > WebSphere application server clusters and clicking Start.
    3. If the web server is on a managed node, stop the server, generate a plug-in, propagate the plug-in, and then start the selected web server from Servers > Server Types > Web servers.
    4. Log in to the IBM InfoSphere Information Server Web console
      https://<hostname>:<port>/ibm/iis/console
      Note: If you are using an HTTP server as the front-end dispatcher for your cluster, regenerate and propagate the plugin-cfg.xml file. You need this for the front-end web server workload management plug-in to take into account the new cluster member. Regenerate and propagate the plugin-cfg.xml file to the front-end Web server as described in Propagating the plugin-cfg.xml file to the front-end web server.
  4. If you selected the Cluster option, complete the following steps:
    Note: When this option is selected, all the JDBC resources defined at the cluster level are gone. In this case, the reconfigure_was_cluster script can be used to recreate the minimum required data sources and JDBC sources.
    1. Create a new cluster member by clicking New. Use the WebSphere Application Server administrator credentials.
    2. Run the reconfigure_was_cluster script with the WebSphere Application Server administrator credentials.
      (The ⇒ character indicates a line continuation.)
      Linux cue graphicUNIX cue graphic
      cd IS_install_path/ASBServer/bin
      ./reconfigure_was_cluster.sh -username <was_admin_user> ⇒
      -password <was_admin_pass>
      Windows cue graphic
      cd IS_install_path\ASBServer\bin
      reconfigure_was_cluster.bat -username <was_admin_user> ⇒
      -password <was_admin_pass>
      Note: This step is mandatory to map the required InfoSphere Information Server data sources present at the server level to the cell level. Without this step, accessing the IBM InfoSphere Information Server Web console might give an exception.
    3. Start the cluster by navigating to Servers > Clusters > WebSphere application server clusters and clicking Start.
    4. If the web server is on a managed node, stop the server, generate a plug-in, propagate the plug-in, and then start the selected web server from Servers > Server Types > Web servers.
    5. Log in to the IBM InfoSphere Information Server Web console
      https://<hostname>:<port>/ibm/iis/console
      Note: If you are using an HTTP server as the front-end dispatcher for your cluster, regenerate and propagate the plugin-cfg.xml file. You need this for the front-end web server workload management plug-in to take into account the new cluster member. Regenerate and propagate the plugin-cfg.xml file to the front-end Web server as described in Propagating the plugin-cfg.xml file to the front-end web server.