Running the installation program (clustered installation)

After you configure your system, run the IBM® InfoSphere® Information Server installation program.

Before you begin

  • AIX® Linux®: Ensure sure that all WebSphere® Application Server processes will start with the correct ulimit setting on the computer where you will install the deployment manager and on all computers that will host a managed node:
    Add the following line to the /etc/profile file:
    ulimit -n 10240
  • Ensure that no firewall is deployed within the IBM WebSphere Application Server Network Deployment cell.
  • Ensure that the deployment manager process is running.
    Tip: You can check whether the deployment manager is running by starting the WebSphere Application Server administrative console. If the login screen displays correctly, the deployment manager process is running. If you see an error or a blank screen, you can start the deployment manager by using the startManager command located under the <dmgrProfileName>/bin directory.
  • Ensure that the managed node and node agent that you created are both running.
    Tip: You can check whether the node agent is running by logging in to the WebSphere Application Server administrative console and clicking System administration > Node agents. You can start the node agent by using the startNode WebSphere Application Server command under the <customProfileName>/bin directory.

    If the managed nodes of the cluster are not running, the installation will fail when attempting to restart the managed nodes. If you receive such a timeout, you would manually start the node agents for the managed nodes in the cluster that are not running and click retry in the Installation error window to continue with the installation.

  • Verify that you have created one cluster with at least one member.
    Note: Install IBM InfoSphere Information Server on a single-node cluster and then, after the installation, expand your cluster by adding new managed nodes and cluster members. Refer to the post-installation administration tasks for details on how to add new custom profiles.
  • If you choose to install against a front-end web server rather than a cluster member, the front-end web server and plug-in module must be installed and configured.


  1. Disable any firewall that might be running on your computer and ensure that the firewall is disabled during the entire installation. You can reenable the firewall after the installation is finished.
  2. Run the InfoSphere Information Server installation program on the computer that hosts the deployment manager process.
    1. Use the steps in the following documentation: Installing IBM InfoSphere Information Server software.
    2. On the WebSphere Application Server Selection panel, select Configure an existing instance.
  3. Select the WebSphere Application Server deployment manager profile.
    The installation program detects that you have a clustered installation rather than a stand-alone installation.
  4. During the interview process, after you select a profile, you select the cluster, web server and virtual host. You specify to install against a select cluster member or a front-end web server.
    You have a choice to install using front end web server or install using a cluster member. It is recommended to install against a cluster member unless you are very sure of the following prerequisites:
    • The front-end web server is properly configured, and the certificates at the WebSphere Cell level are imported into the front-end web server and to the web server plug-in's keystore (if applicable).
    • The web server port numbers are specified into WebSphere Virtual Hosts aliases.
    • There are no firewall issues accessing the front-end web server from the machine installing IBM InfoSphere Information Server.

    Further, during IBM InfoSphere Information Server installation, a set of IBM InfoSphere Information Server web applications are deployed into the selected cluster. Some of these web applications are also invoked with REST APIs as part of the installation process. That means that if you select the front-end web server as an installation option, you must make sure that it is pre-configured to properly propagate HTTPS requests to the back end WebSphere Application Server so that these requests are run by the new web application. Or, you must ensure that the front-end web server is fully managed by WebSphere Application Server with the automatic update and propagation of the HTTP plug-in when new web applications are deployed. If you are not sure about the front-end web server configuration and its propagation procedure, select to install against the cluster member.

What to do next

Note: When the MetadataServer script is run in a stand-alone (non-cluster) environment, it sets the following system settings:
Operating system Setting
AIX uname setting: ulimit -n 10240
Linux uname setting: ulimit -n 10240
Windows uname setting: unset LDR_CNTRL
These settings are not set when you start a cluster. You can manually produce these settings in a cluster environment, if needed. The MetadataServer script exists in the ASBServer/bin directory of the computer hosting the deployment manager.