localdomain The domain name xx.xx.xx.

xx The unique IP address for the computer longhostname shorthostname The long and short names for the computer 3. Ensure that you install the metadata repository and engine tiers in the same network segment. 4. Open and make TCP ports available through firewalls for InfoSphere Information Server and the application server. The following tables identify the TCP ports that must be available for each tier: v Port numbers for the metadata repository tier v Port numbers for the services tier v Port numbers for the engine tier
Table 57. Port numbers for the metadata repository tier Component Default port numbers Tiers that use the port Services Services, engine, client Services Services, engine, client Services Services, engine, client

IBM DB2 database for the metadata 50000 repository (default database) IBM DB2 database for the analysis database (default database) Oracle database for the metadata repository (if used) Oracle database for the analysis database (if used) Microsoft SQL Server database for the metadata repository (if used) Microsoft SQL Server database for the analysis database (if used) 50000 1521 1521 1433 1433

Table 58. Port numbers for the services tier Component DHTML reports server Default port numbers for stand-alone configuration 16581 Default port numbers for cluster configuration (DHTML reports server functionality is not supported in clustered configurations.) Tiers that use the port Client

InfoSphere Information Server Web-based clients

WC_defaulthost (9080)

Firewall between the client Services, engine, client and dispatcher (if any): usually 80. This value varies depending on the configuration of the front-end dispatcher. Firewall between dispatcher and cluster members (if any): WC_defaulthost of all cluster members (for example, 9080, 9081, and so on).

134

Planning, Installation, and Configuration Guide

Table 58. Port numbers for the services tier (continued) Component InfoSphere Information Server Web-based clients (HTTPS) Default port numbers for stand-alone configuration WC_defaulthost_secure (9443) Default port numbers for cluster configuration Firewall between the client and dispatcher (if any): usually 443. This value varies depending on the configuration of the front-end dispatcher. Firewall between the dispatcher and cluster members (if any): WC_defaulthost_secure of all cluster members (for example, 9443, 9444, and so on) IBM WebSphere Application Server administrative console (redirects to HTTPS) IBM WebSphere Application Server administrative console (HTTPS) InfoSphere Information Server services (RMI/IIOP) WC_adminhost (9060) WC_adminhost (9060) Client Tiers that use the port Client If HTTPS is configured, the services tier and engine tier also use this port.

WC_adminhost_secure (9043)

WC_adminhost_secure (9043)

Client

BOOTSTRAP_ADDRESS (2809) ORB_LISTENER_ADDRESS (9100) SAS_SSL_SERVERAUTH_ LISTENER_ADDRESS (9401)

BOOTSTRAP_ADDRESS of all cluster members (9810, 9811, and so on) ORB_LISTENER_ADDRESS of all node agents (9100, 9101, and so on)

Services, engine, client

SAS_SSL_SERVERAUTH_ LISTENER_ADDRESS, CSIV2_SSL_SERVERAUTH_ CSIV2_SSL_ LISTENER_ADDRESS, MUTUALAUTH_ CSIV2_SSL_ LISTENER_ADDRESS MUTUALAUTH_ (9402) LISTENER_ADDRESS CSIV2_SSL_SERVERAUTH_ of all cluster members: (9410, 9411, 9412), LISTENER_ADDRESS (9411, 9414, 9415), (9403) and so on

Chapter 7. Preparation steps for all tier computers

135

Table 58. Port numbers for the services tier (continued) Component Default port numbers for stand-alone configuration Default port numbers for cluster configuration SIB_ENDPOINT_ADDRESS of all cluster members (7277, 7278, and so on) SIB_ENDPOINT_SECURE_ ADDRESS of all cluster members (7287, 7288, and so on) Tiers that use the port Client

IBM InfoSphere SIB_ENDPOINT_ADDRESS Information Services (7276) Director services with JMS bindings SIB_ENDPOINT_SECURE_ ADDRESS (7286) SIB_MQ_ENDPOINT_ ADDRESS (5558)

SIB_MQ_ENDPOINT_ SIB_MQ_ENDPOINT_ SECURE_ADDRESS (5578) ADDRESS of all cluster members (5559, 5560, and so on) SIB_MQ_ENDPOINT_ SECURE_ADDRESS of all cluster members (5579, 5580, and so on)

Important: IBM WebSphere Application Server Network Deployment does not support deployment of firewalls between components within a cell (for example, between the dmgr and nodes).
Table 59. Port numbers for the engine tier Component InfoSphere Information Server ASB agent Default port numbers 31531, and a random port number greater than 1024 Instead of using a random port number, you can fix this to a specific port by specifying agent.objectport=# in the C:\IBM\InformationServer\ ASBNode\conf\agent.properties file after you complete the installation. After designating a specific port, restart the logging agent and the ASB agent so that the change takes effect. InfoSphere Information Server logging agent IBM InfoSphere DataStage and QualityStage Administrator services Parallel job monitors 31533 DSRPC (31538) 13400 (port 1) and 13401 (port 2) Access to port 1 is required only from the conductor node. Access to port 2 is required from the conductor node and the node where the InfoSphere DataStage and QualityStage Administrator engine is installed, if that node is different from the conductor node. Engine Engine, client Engine Tiers that use the port Services

136

Planning, Installation, and Configuration Guide

Table 59. Port numbers for the engine tier (continued) Component Parallel engine Default port numbers APT_PM_STARTUP_PORT (multiple ports, uses a port number of 10240 or greater) 22514 APT_PLAYER_CONNECTION_ PORT (multiple ports, uses a port number of 11000 or greater) Tiers that use the port Engine

Parallel engine remote process startup (rsh/ssh, multiple nodes only) Parallel engine (multiple nodes only)

Engine Engine

5. For connectivity to data sources, see the vendor-supplied documentation for additional port assignments.

Modifying kernel parameters and user limits (Linux, UNIX)

For Linux and UNIX installations, modify the kernel parameters and user limits and restart the computer before you start the installation program. The kernel parameter and user limit requirements are minimum requirements for IBM InfoSphere Information Server. The optimal value for each parameter might be higher depending on the topology of your installation and the operational data load. Additional kernel parameter and user limit changes might be required. When more than one value is provided for your configuration, use the largest minimum value. All changes must be made by a trained system administrator. Make a backup copy of the kernel parameters and user limits before you modify them. After you modify the kernel parameters and user limits with the suggested values, restart the computer, and then install InfoSphere Information Server.

Minimum kernel parameters

The following sections describe the minimum kernel parameter requirements for each tier: Metadata repository tier Minimum kernel parameters for DB2 Database for Linux, UNIX, and Windows (metadata repository tier) on page 138 Engine and services tiers v v v v
AIX Minimum AIX kernel parameters (engine and services tiers) on page 139 HP-UX Minimum HP-UX kernel parameters (engine and services tiers) on page 139 Linux Minimum Linux kernel parameters (engine and services tiers) on page 140 Solaris Minimum Solaris kernel parameters (engine and services tiers) on page 140

You can find additional system tuning information in the IBM WebSphere Application Server documentation:

Chapter 7. Preparation steps for all tier computers

137