localdomainThe domain name

xx.xx.xx.xxThe unique IP address for the computer

longhostname shorthostnameThe long and short names for the computer

3. Ensure that you install the metadata repository and engine tiers in the samenetwork segment.

4. Open and make TCP ports available through firewalls for InfoSphereInformation Server and the application server. The following tables identify theTCP 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

IBM DB2 database for the metadatarepository (default database)

50000 Services

IBM DB2 database for the analysisdatabase (default database)

50000 Services, engine, client

Oracle database for the metadatarepository (if used)

1521 Services

Oracle database for the analysisdatabase (if used)

1521 Services, engine, client

Microsoft SQL Server database forthe metadata repository (if used)

1433 Services

Microsoft SQL Server database forthe analysis database (if used)

1433 Services, engine, client

Table 58. Port numbers for the services tier

ComponentDefault port numbers forstand-alone configuration

Default port numbers forcluster configuration Tiers that use the port

DHTML reports server 16581 (DHTML reports serverfunctionality is notsupported in clusteredconfigurations.)

Client

InfoSphere InformationServer Web-based clients

WC_defaulthost (9080) Firewall between the clientand dispatcher (if any):usually 80. This value variesdepending on theconfiguration of thefront-end dispatcher.

Firewall between dispatcherand cluster members (ifany): WC_defaulthost of allcluster members (forexample, 9080, 9081, and soon).

Services, engine, client

134 Planning, Installation, and Configuration Guide

Table 58. Port numbers for the services tier (continued)

ComponentDefault port numbers forstand-alone configuration

Default port numbers forcluster configuration Tiers that use the port

InfoSphere InformationServer Web-based clients(HTTPS)

WC_defaulthost_secure(9443)

Firewall between the clientand dispatcher (if any):usually 443. This valuevaries depending on theconfiguration of thefront-end dispatcher.

Firewall between thedispatcher and clustermembers (if any):WC_defaulthost_secure ofall cluster members (forexample, 9443, 9444, and soon)

Client

If HTTPS is configured, theservices tier and engine tieralso use this port.

IBM WebSphereApplication Serveradministrative console(redirects to HTTPS)

WC_adminhost (9060) WC_adminhost (9060) Client

IBM WebSphereApplication Serveradministrative console(HTTPS)

WC_adminhost_secure(9043)

WC_adminhost_secure(9043)

Client

InfoSphere InformationServer services(RMI/IIOP)

BOOTSTRAP_ADDRESS(2809)

ORB_LISTENER_ADDRESS(9100)

SAS_SSL_SERVERAUTH_LISTENER_ADDRESS(9401)

CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS(9402)

CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS(9403)

BOOTSTRAP_ADDRESS ofall cluster members (9810,9811, and so on)

ORB_LISTENER_ADDRESSof all node agents (9100,9101, and so on)

SAS_SSL_SERVERAUTH_LISTENER_ADDRESS,CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS,CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESSof all cluster members:(9410, 9411, 9412),(9411, 9414, 9415),and so on

Services, engine, client

Chapter 7. Preparation steps for all tier computers 135

Table 58. Port numbers for the services tier (continued)

ComponentDefault port numbers forstand-alone configuration

Default port numbers forcluster configuration Tiers that use the port

IBM InfoSphereInformation ServicesDirector services with JMSbindings

SIB_ENDPOINT_ADDRESS(7276)

SIB_ENDPOINT_SECURE_ADDRESS (7286)

SIB_MQ_ENDPOINT_ADDRESS (5558)

SIB_MQ_ENDPOINT_SECURE_ADDRESS (5578)

SIB_ENDPOINT_ADDRESSof all cluster members(7277, 7278, and so on)

SIB_ENDPOINT_SECURE_ADDRESS of all clustermembers(7287, 7288, and so on)

SIB_MQ_ENDPOINT_ADDRESS of all clustermembers(5559, 5560, and so on)

SIB_MQ_ENDPOINT_SECURE_ADDRESS of allcluster members(5579, 5580, and so on)

Client

Important: IBM WebSphere Application Server Network Deployment does notsupport deployment of firewalls between components within a cell (forexample, between the dmgr and nodes).

Table 59. Port numbers for the engine tier

Component Default port numbers Tiers that use the port

InfoSphere Information Server ASB agent 31531, and a random portnumber greater than 1024

Instead of using a random portnumber, you can fix this to aspecific port by specifyingagent.objectport=# in theC:\IBM\InformationServer\

ASBNode\conf\agent.properties

file after you complete theinstallation. After designating aspecific port, restart the loggingagent and the ASB agent so thatthe change takes effect.

Services

InfoSphere Information Server logging agent 31533 Engine

IBM InfoSphere DataStage and QualityStageAdministrator services

DSRPC (31538) Engine, client

Parallel job monitors 13400 (port 1) and 13401 (port 2)

Access to port 1 is required onlyfrom the conductor node. Accessto port 2 is required from theconductor node and the nodewhere the InfoSphere DataStageand QualityStage Administratorengine is installed, if that node isdifferent from the conductornode.

Engine

136 Planning, Installation, and Configuration Guide

Table 59. Port numbers for the engine tier (continued)

Component Default port numbers Tiers that use the port

Parallel engine APT_PM_STARTUP_PORT(multiple ports, uses a portnumber of 10240 or greater)

Engine

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

22514 Engine

Parallel engine (multiple nodes only) APT_PLAYER_CONNECTION_PORT (multiple ports, uses aport number of 11000 orgreater)

Engine

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

Modifying kernel parameters and user limits (Linux, UNIX)

For Linux and UNIX installations, modify the kernel parameters and user limitsand restart the computer before you start the installation program.

The kernel parameter and user limit requirements are minimum requirements forIBM InfoSphere Information Server. The optimal value for each parameter might behigher depending on the topology of your installation and the operational dataload. Additional kernel parameter and user limit changes might be required. Whenmore than one value is provided for your configuration, use the largest minimumvalue.

All changes must be made by a trained system administrator. Make a backup copyof the kernel parameters and user limits before you modify them. After youmodify the kernel parameters and user limits with the suggested values, restart thecomputer, and then install InfoSphere Information Server.

Minimum kernel parameters

The following sections describe the minimum kernel parameter requirements foreach tier:

Metadata repository tier“Minimum kernel parameters for DB2 Database for Linux, UNIX, andWindows (metadata repository tier)” on page 138

Engine and services tiers

v AIX “Minimum AIX kernel parameters (engine and services tiers)”on page 139

v HP-UX “Minimum HP-UX kernel parameters (engine and servicestiers)” on page 139

v Linux “Minimum Linux kernel parameters (engine and servicestiers)” on page 140

v Solaris “Minimum Solaris kernel parameters (engine and servicestiers)” on page 140

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

Chapter 7. Preparation steps for all tier computers 137