Administration guide > Tune and performance
Plan for network ports
WebSphere eXtreme Scale is a distributed cache that requires opening ports to communicate with the ORB and TCP stack among JVMs
Plan and control the ports, especially in an environment that has a firewall, and when you are using a catalog service and containers on multiple ports.
Catalog service domain
A catalog service domain requires the following ports to be defined:
- peerPort
- Port for the high availability (HA) manager to communicate between peer catalog servers over a TCP stack. In WAS, this setting is inherited by the high availability manager port configuration.
- clientPort
- Port for catalog servers to access catalog service data. In WAS, this port is set through the catalog service domain configuration.
- listenerPort
- ORB listener port for containers and clients to communicate with the catalog service through the ORB. In WAS, the listenerPort is inherited by the BOOTSTRAP_ADDRESS port configuration.
Container servers
The WXS container servers also require several ports to operate. By default, the WXS container server generates its HA manager port and ORB listener port automatically with dynamic ports. For an environment that has a firewall, it is advantageous for you to plan and control ports. For container servers to start with specific ports, you can use the following options in the startOgServer command.
- haManagerPort
- Peer port. (Required for WAS environments only.)
- listenerPort
- Defines the ORB listener port for containers and clients to communicate with the catalog service through the ORB.
Proper planning of port control is essential when hundreds of JVMs are started in a server. If a port conflict exists, container servers do not start.
Clients
WXS clients can receive callbacks from servers when you are using the DataGrid API or several other commands. Use the listenerPort property in the client properties file to specify the port in which the client listens for callbacks from the server.
- haManagerPort
- Peer port. (Required for WAS environments only.)
- jvmArgs (optional)
- List of JVM arguments. When security is enabled, use the following argument to configure the SSL port:
-jvmArgs Dcom.ibm.CSI.SSLPort=<sslPort>
- listenerPort
- ORB listener port for containers and clients to communicate with the catalog service through the ORB.
Ports in WAS
- The listenerPort is defined as the BOOTSTRAP_ADDRESS for each WAS application server.
- The haManagerPort and peerPort are defined as the DCS_UNICAST_ADDRESS for each WAS application server.
You can define a catalog service domain in the administrative console as described in Create catalog service domains in WAS.
You can view the ports for a particular server by clicking one of the following paths in the administrative console:
- WAS ND v6.1:
Servers | Application Servers | server_name | Ports | end_point_name
- WAS ND v7.0:
Servers | Server Types | WAS | server_name | Ports | port_name
Parent topic:
Configure ports
Parent topic:
Tune and performance
Related concepts
Servers with multiple network cards
Operating systems and network tuning
ORB properties and file descriptor settings
JVM tuning for WXS
Use WebSphere Real Time
Security integration with external providers
Related tasks
Configure ports in stand-alone mode
Configure ports in a WAS environment
Configure failover detection
Tune the dynamic cache provider
Tune the cache sizing agent for accurate memory consumption estimates
Related reference
Operational checklist
Client properties file