IBM InfoSphere Foundation Tools, IBM InfoSphere Information Server, Version 8.5

Installation checklist with IBM WebSphere Application Server cluster and IBM DB2 cluster

In this configuration, you install the IBM® InfoSphere® Information Server services tier in a WebSphere® Application Server cluster for high availability and scalability. The metadata repository tier is installed in a DB2® cluster. All server computers run a supported Linux or UNIX operating system.

Additionally, you install InfoSphere Information Server clients on a supported Microsoft Windows operating system.

The following diagram illustrates a sample configuration. You might choose to create a different front-end configuration than the diagram illustrates, or include more WebSphere Application Server nodes. For more information about InfoSphere Information Server clustered configurations, see High availability configurations.

Figure 1. Sample configuration with WebSphere Application Server cluster and DB2 cluster

This figure is described in the surrounding text.

The following procedures suggest various user and group names. You can use these names, or use different names in accordance with your company policies.

1. Setting up the environment

Before you install the product, plan your installation and set up network and file systems on all tiers.

Table 1. Environment setup tasks for all tiers
Task	Record your information here
1. Verify that you are installing the correct packages for your operating system. See the system requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.
2. Plan the volume groups and file systems on which you are installing InfoSphere Information Server. Verify that you have sufficient storage space in your file systems. See the system requirements, and Planning volume groups and file systems.
3. Review and verify the planning and system requirements information. See Planning for the installation of IBM InfoSphere Information Server.
4. Verify name resolution: Verify that the computers in the installation can resolve the other computers by both the short name (host name only) and long name (fully qualified host and domain name). Verify that both the short and long host names resolve to the same IP address. Verify that the computers in the installation can resolve their own names to IP addresses by both short name and long name. Ensure that the `localhost` host name resolves to IP address 127.0.0.1. Ensure that the computer host name is not mapped to the 127.0.0.1. Add the short and long names of all the computers in the installation to the /etc/hosts file of each computer in the installation. See Verifying the network and opening ports.
5. Open the TCP ports for InfoSphere Information Server and the application server across any applicable firewalls. See Verifying the network and opening ports.
6. Update the DB2 and WebSphere Application Server kernel parameters and user limits on each computer for the metadata repository tier, services tier, and engine tier. See Modifying kernel parameters and user limits (Linux, UNIX).
7. Create the temporary directories /tmp and /var/tmp, if they do not already exist. The root user must have read, write, and execute permissions to these directories. The installation program must be run as root. See Planning volume groups and file systems.
8. Prepare each computer to run the InfoSphere Information Server installation program, and back up any critical data on the computers. See Preparing to run the installation program.

2. Preparing the metadata repository tier

Install the DB2 database system and create the cluster and the database for the metadata repository.

Table 2. Metadata repository tier tasks
Task	Record your information here
1. Prepare the DB2 cluster computers, file system, network, and storage. See Preparing the servers, file system, and storage.
2. (Optional) Install and configure IBM Tivoli® System Automation for Multiplatforms (SA MP). This software monitors the state of the DB2 database system servers and manages failover. See Installing high availability software on DB2 database system servers.
3. Create the following administration accounts on each DB2 cluster computer. The accounts on each computer must be identical. Log in to each account to confirm that it functions properly: DB2 database administrator user: dasusr1 in the dasadm1 group DB2 database instance owner: db2inst1 in the db2iadm1 group DB2 fenced user: db2fenc1 in the db2fadm1 group Owner of the metadata repository: xmeta in the xmeta group (If installing InfoSphere Information Analyzer) The owner of the analysis database: iauser in the iauser group See Setting up administrator and owner accounts.
4. Install the DB2 database system, create a cluster, and create the metadata repository database on the primary node. See Installing the DB2 database system and creating the cluster and metadata repository database.

3. Installing and configuring the services tier

Install the application server, create a cluster, and then run the InfoSphere Information Server installation program.

Start with only one managed node in the cluster. Add additional nodes only after InfoSphere Information Server installation is complete. This strategy minimizes complexity and installation time.

Table 3. Services tier tasks
Task	Record your information here
1. (Linux) Make 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 to the /etc/profile file: `ulimit -n 10240` See Configuring file descriptor resources for IBM WebSphere Application Server (Linux).
2. Install IBM WebSphere Application Server Network Deployment on all the computers that will host the services tier. This installation includes the deployment manager system and all computers that will host a managed node in the cluster. Also install any required WebSphere Application Server fix packs and iFixes. See Installing IBM WebSphere Application Server Network Deployment for a cluster installation.
3. On the computer that hosts the deployment manager, create a deployment manager profile that contains the deployment manager process. Make sure that Administrative Security is disabled. See Creating a deployment manager profile.
4. On the computer that hosts the managed node, use the Profile Management Tool to create a custom profile. This profile will contain the node agent process and the managed server process that will be part of the cluster. See Creating a custom profile.
5. Use the WebSphere Application Server administrative console to create a cluster with one cluster member definition. See Creating a cluster and cluster members for the application server.
6. Install a front-end Web server and the Web server plug-in module. Run the configure`webserver_name` script to create a Web server definition in WebSphere Application Server, and do other Web server configuration. See Installing a front-end Web server.
7 Optional: Install backup Web servers, load balancers, firewalls, and other architectural components. See Installing a front-end load balancer (Optional).
8. Optional: To increase security, configure the WebSphere Application Server front-end Web server to accept secure HTTP (HTTPS) calls. See Configuring the front-end HTTP server for HTTPS.
9. Ensure that no firewall is deployed within the IBM WebSphere Application Server Network Deployment cell.
10. Make sure that you can start and stop the Web server. Then start the Web server. For IBM HTTP Server, see publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_startihs.html
11. On the computer that hosts the deployment manager, verify that you can start and stop the deployment manager process. Then start the process and verify that it is running. See Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services.
12. On the computer that hosts the managed node, verify that you can start and stop the managed node and node agent that you created. Then start the process and verify that it is running. Verify that it does not have global security on. See Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services.
13. Run the installation program on the computer where the WebSphere Application Server deployment manager is installed: From the is-suite directory on the installation media, run the following command to start the installation program: `./setup -verbose` Using a supported web browser on a Windows computer, open the URL that the ./setup command displays. In the installation program, accept all defaults, except these items: In the Tier Selection page, choose Services only. In the Application Server page, choose Use an existing WebSphere Application Server installation. In the WebSphere Application Server Profile page, choose the Deployment Manager profile. In the WebSphere Application Server Cluster Information page, specify the URL of the front-end HTTP dispatcher for the WebSphere Application Server cluster. In the HTTP Port field, type the port number of the front-end HTTP dispatcher. (Optional) Click Use Secure Sockets Layer (SSL) for HTTP communication. In the HTTP Port field, type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. In the Database Management System Selection page, choose Use existing database management system installation. In the Database Connection page, specify the metadata repository tier connection and database information. Complete the rest of the installation steps. See Starting the installation program in graphical mode.
14. After installation, configure automatic client reroute to enable WebSphere Application Server to reconnect to the DB2 standby server. See Configuring automatic client reroute.
15. To cause WebSphere Application Server to communicate with the DB2 cluster instead of a single node, run the WebSphere Application Server administrative console to specify an alternate database address and port. Then restart the cluster. See Specifying the alternate database address and port for IBM WebSphere Application Server.
16. To communicate the cluster configuration to the front-end Web server, run the WebSphere Application Server administrative console to generate the plugin-cfg.xml file, and then manually copy it to each Web server. Then restart the Web server. If you are using IBM HTTP Server, you can automatically propagate the file to your Web servers by using the WebSphere Application Server administrative console. See Propagating the plugin-cfg.xml file to the front-end Web server.

4. Installing and configuring the engine tier

Set up directories and accounts. Then install and configure the engine tier.

Table 4. Engine tier tasks
Task	Record your information here
1. Create an administrator account for the InfoSphere Information Server engine. Log in to the account to activate the password. See Setting up administrator and owner accounts.
2. For non-English locales, make sure that the locale and encoding are set correctly. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. See Setting the locale for the target computer.
3. Run the installation program: From the is-suite directory on the installation media, run the following command to start the installation program: `./setup -verbose` Using a supported web browser on a Windows computer, open the URL that the ./setup command displays. In the installation program, accept all defaults, except: In the Tier Selection page, choose Engine only. In the IBM InfoSphere Information Server Location page, specify the URL of the front-end HTTP dispatcher for the WebSphere Application Server cluster. In the Port field, type the port number of the front-end HTTP dispatcher. Enter the InfoSphere Information Server administrator account name and password. (Optional) Click Use Secure Sockets Layer (SSL) for HTTP communication. In the Port field, type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. Complete the rest of the installation steps. See Starting the installation program in graphical mode.
4. Configure the ODBC Data Source Name by using drivers in `install_home`/Server/branded_odbc as described in the documentation in that directory. Also see Configuring ODBC access (Linux, UNIX).
5. For mixed locale clients, ensure that IBM InfoSphere DataStage®, IBM InfoSphere QualityStage®, and IBM InfoSphere Information Analyzer users have the correct settings specified for globalization. See Ensuring that InfoSphere DataStage users have the correct localization settings (Linux, UNIX).
6. Review the system requirements to choose a supported C++ compiler for job development, and install it in its default location. See Installing a C++ compiler for job development.

5. Installing and configuring the client tier

On each computer where you need the client programs, run the InfoSphere Information Server installation program, and then configure ODBC drivers.

Table 5. Client tier tasks
Task	Document your information here
1. Run the installation program: Double-click the setup icon to start the installation program. The program windows display in your default Web browser. In the installation program, accept all defaults, except in the Tier Selection page, choose Client only. Note: If you are using the client-only installation media, the Tier Selection page does not display. The program installs the client tier only. Complete the rest of the installation. See Starting the installation program in graphical mode.
2. Configure the ODBC Data Source Name by using drivers in `install_home`\ODBCDrivers as described in the documentation in that directory.

6. Completing the installation

After you install the tiers, configure users, security, connectivity, and product modules.

Table 6. Postinstallation tasks for all tiers
Task	Record your information here
1. Set up firewall exceptions for client-side executable files. See Firewall exceptions for client-side executable files (Windows).
2. Optional: Configure Secure Sockets Layer (SSL): Enable SSL for inbound RMI/IIOP. When you install InfoSphere Information Server, SSL for inbound RMI/IIOP communications is disabled by default. If the installation program did not configure HTTPS for a tier computer during InfoSphere Information Server installation, manually configure HTTPS for that tier computer. To allow clients to communicate with the server by using HTTPS, you must manually configure HTTPS on each client tier computer. See Enabling Secure Sockets Layer (SSL).
3. Change InfoSphere Information Server to use a Lightweight Directory Access Protocol (LDAP) user registry. See User registry configuration.
4. Create users and groups by using the LDAP user registry utilities. See User and group creation.
5. Map credentials between the LDAP user registry and the local operating system user registry on the computer where the InfoSphere Information Server engine is installed. See Engine security configuration.
6. Assign security roles to users and groups. See Assigning user roles.
7. Assign project roles to users. See Security role overview.
8. Configure IBM InfoSphere Information Analyzer, IBM InfoSphere Business Glossary, IBM InfoSphere Metadata Workbench, and IBM InfoSphere FastTrack (if you installed any of these product modules). See Configuring product modules in the suite.
9. Add additional WebSphere Application Server cluster members and managed nodes. See WebSphere Application Server cluster administration.
10. Optional: Run the IBM Support Assistant Lite for InfoSphere Information Server tool to verify the installation. See Installation verification and troubleshooting.

This topic is also in the IBM InfoSphere Information Server Planning, Installation, and Configuration Guide.

Update timestamp

Last updated: 2012-10-8