Configuring your network

IBM® InfoSphere® Information Server exchanges high volumes of data across several network ports, which requires that you carefully configure the host names and ports for your network.

Before you begin

Ensure that a TCP/IP network is used for all communications in the installation.

About this task

For performance reasons, do not install InfoSphere Information Server in a wide area network (WAN) configuration because of the data exchanges that are required. Although clients can work over a WAN if the latency is low, when the network latency increases, it has a detrimental effect on the clients.

Note: The port numbers in the following tables might vary from those that are used in your system because the installation program automatically computes the port value based on port availability. For example, for the BOOTSTRAP_ADDRESS port, the installation program starts with port 2809 and increments by 1 until it locates an open port. Ensure that you select the correct ports in your system to open and make available. The port values that are used in your system are stored in the response file that the installation program generates. Before you install the product, check the Response File Review panel in the installation program for the location, name, and contents of your response file.

Procedure

Set up the name resolution.

Verify that the computers in the installation can resolve all the other computers by both the short name and long name (fully qualified domain name), for example mycomputer and mycomputer.mydomain.com.

Ensure that each of the following tier computers can resolve the IP addresses of the computers that are listed for that tier.

Table 1. Tier computers and the computers that they connect to
Tier computer	Tier computers to connect to
Metadata repository tier	Metadata repository tier
Services tier	Services tier, engine tier, client tier
Engine tier	Services tier, engine tier, client tier

Ensure that only localhost is mapped to the loopback IP address. The IPv4 version of this address is 127.0.0.1 and the IPv6 version is ::1/128. No other entries can map localhost to the IP address of the local computer. The following example shows how these entries are configured in the following files:
Operating system File

AIX® HP-UX Solaris /etc/hosts

Linux /etc/hosts

Windows C:\Windows\system32\drivers\etc\hosts
```
127.0.0.1   | ::1/128 localhost.localdomain localhost 
xx.xx.xx.xx | xx:xx::xx:xx longhostname shorthostname 
```
localdomain

The domain name.

xx.xx.xx.xx | xx:xx::xx:xx

The unique IP address for the computer. IPv4 and IPv6 addresses are supported.

longhostname shorthostname

The long and short names for the computer.

Operating system	File
AIX® HP-UX Solaris	/etc/hosts
Linux	/etc/hosts
Windows	C:\Windows\system32\drivers\etc\hosts

For the metadata repository tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.

Table 2. Port numbers for the metadata repository tier
Component	Default port numbers	Tiers that use the port
IBM DB2® database for the metadata repository (default database)	50000	Services
IBM DB2 database for the analysis database (default database)	50000	Services, engine, client
Oracle database for the metadata repository (if used)	1521	Services
Oracle database for the analysis database (if used)	1521	Services, engine, client
Microsoft SQL Server database for the metadata repository (if used)	1433	Services
Microsoft SQL Server database for the analysis database (if used)	1433	Services, engine, client

For the services tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.

Table 3. Port numbers for the services tier (basic configuration)
Component	Default port numbers for basic configuration	Tiers that use the port
Reports server	16581	Client
InfoSphere Information Server web-based clients (HTTP)	WC_defaulthost (9080)	Services, engine, client
InfoSphere Information Server web-based clients (HTTPS)	WC_defaulthost_secure (9443)	Client If HTTPS is configured, the services tier and engine tier also use this port.
IBM WebSphere® Application Server administrative console (redirects to HTTPS)	WC_adminhost (9060)	Client
IBM WebSphere Application Server administrative console (HTTPS)	WC_adminhost_secure (9043)	Client
InfoSphere Information Server communication services (Java Remote Method Invocation [RMI] or Inter-ORB Protocol [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)	Services, engine, client
IBM InfoSphere Information Services Director services with JMS bindings	SIB_ENDPOINT_ADDRESS (7276) SIB_ENDPOINT_SECURE_ ADDRESS (7286) SIB_MQ_ENDPOINT_ ADDRESS (5558) SIB_MQ_ENDPOINT_ SECURE_ADDRESS (5578)	Client

Table 4. Port numbers for the services tier (clustered configuration)
Component	Default port numbers for clustered configuration	Tiers that use the port
Reports server	(DHTML reports server functionality is not supported in clustered configurations.)	Client
InfoSphere Information Server web-based clients (HTTP)	Firewall between the 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, 9yep080, 9081, and so on).	Services, engine, client
InfoSphere Information Server web-based clients (HTTPS)	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)	Client If HTTPS is configured, the services tier and engine tier also use this port.
IBM WebSphere Application Server administrative console (redirects to HTTPS)	WC_adminhost (9060)	Client
IBM WebSphere Application Server administrative console (HTTPS)	WC_adminhost_secure (9043)	Client
InfoSphere Information Server communication services (Java Remote Method Invocation [RMI] or Inter-ORB Protocol [IIOP])	BOOTSTRAP_ADDRESS of all cluster members (9809, 9810, 9811, and so on) ORB_LISTENER_ADDRESS of all node agents (9100, 9101, and so on) DCS_UNICAST_ADDRESS (9353) SAS_SSL_SERVERAUTH_ LISTENER_ADDRESS, CSIV2_SSL_SERVERAUTH_ LISTENER_ADDRESS, CSIV2_SSL_ MUTUALAUTH_ LISTENER_ADDRESS of all cluster members: (9410, 9411, 9412), (9411, 9414, 9415), and so on	Services, engine, client
IBM InfoSphere Information Services Director services with JMS bindings	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) SIB_MQ_ENDPOINT_ ADDRESS of all cluster members (5559, 5560, and so on) SIB_MQ_ENDPOINT_ SECURE_ADDRESS of all cluster members (5579, 5580, and so on)	Client

For the engine tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.

Table 5. Port numbers for the engine tier
Component	Default port numbers	Tiers that use the port
InfoSphere Information Server ASB agent	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.	Services
InfoSphere Information Server logging agent	31533	Engine
IBM InfoSphere DataStage® and QualityStage® Administrator services	DSRPC (31538)	Engine, client
Parallel job monitors	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 Information Server engine is installed, if that node is different from the conductor node.	Engine
Parallel engine	APT_PM_STARTUP_PORT (multiple ports, uses a port number of 10240 or greater)	Engine
Parallel engine remote process startup (Remote Shell and Secure Shell, multiple nodes only)	22514	Engine
Parallel engine (multiple nodes only)	APT_PLAYER_CONNECTION_ PORT (multiple ports, uses a port number of 11000 or greater)	Engine

For the client tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.
Table 6. Port numbers for the client tier
Component Default port numbers Tiers that use the port

IBM InfoSphere Metadata Asset Manager 19443 Services
For connecting to external data sources, see the vendor-supplied documentation for additional port assignments.