You can configure the necessary ports for servers and clients in an eXtreme scale deployment by using command-line parameters, property files or programmatically. Most examples included in the following sections describe command-line parameters to the startOgServer script. Equivalent configuration options can also be set in properties files, using the embedded server API or the client API.
WebSphere® eXtreme Scale uses IIOP to communicate between Java™ virtual machines. The catalog service JVMs are the only processes that require the explicit configuration of ports for the IIOP services and group services ports. Other processes dynamically allocate ports.
startOgServer.bat|sh cs1 -catalogServiceEndPoints
cs1:MyServer1.company.com:6601:6602,cs2:MyServer2.company.com:6601:6602,cs3:MyServer3.company.com:6601:6602
If you start additional catalog servers, they must include the same
servers in the -catalogServiceEndPoints argument.
The order of the list can be different, but the servers contained
in the list must be the same for each catalog server. Do not put any
spaces in the list.Specifies the host name to which the Object Request Broker (ORB) transport protocol binds for communication. The value must be a fully qualified domain name or IP address. If your configuration involves multiple network cards, set the listener host and port to the IP address for which to bind. By setting the listener and host port, it allows the transport mechanism in the JVM know which IP address to use. If you do not specify which IP address to use, symptoms such as connection timeouts, unusual API failures, and clients that seem to hang can occur.
Default: localhostYou can also set the listener port and listener host with the listenerHost and listenerPort server properties.
The JMX service port is used for communication from JMX clients. To specify the JMX service port, use the following command-line option:
Default: 1099 for catalog servers
You can also set the JMX service port with the JMXServicePort server property.
The JMX connector port is used for communication from JMX clients. To specify the JMX connector port, use the following command-line option:
You can also set the JMX connector port with the JMXConnectorPort server property.
-jvmArgs -Dcom.ibm.CSI.SSLPort=<sslPort>
An example of the command follows:
./startOgServer.sh cs1 -listenerHost hostA -listenerPort 2809
-catalogServiceEndPoints cs1:hostA:6601:6611,cs2:hostB:6601:6611
./startOgServer.sh cs2 -listenerHost hostB -listenerPort 2809
-catalogServiceEndPoints cs1:hostA:6601:6611,cs2:hostB:6601:6611
./startOgServer.sh c0 -catalogServiceEndPoints hostA:2809,hostB:2809
The container server Java virtual machines use two ports. The HA manager port is used for internal communication between peer container servers and catalog servers. The listener port is used for IIOP communication between peer container servers, catalog servers, and clients. The listener host is used to bind the ORB to a specific network adapter. If you do not specify, both ports are dynamically selected. However, if you want to explicitly configure ports, such as in a firewall environment, you can use a command-line options to specify the ORB port.
Specifies the host name to which the Object Request Broker (ORB) transport protocol binds for communication. The value must be a fully qualified domain name or IP address. If your configuration involves multiple network cards, set the listener host and port to the IP address for which to bind. By setting the listener and host port, it allows the transport mechanism in the JVM know which IP address to use. If you do not specify which IP address to use, symptoms such as connection timeouts, unusual API failures, and clients that seem to hang can occur.
Default: localhostYou can also set listener port and listener host with the listenerHost and listenerPort server properties.
You can also set the HA manager port with the HAManagerPort server property.
-jvmArgs -Dcom.ibm.CSI.SSLPort=<sslPort>
Default: 1099 for catalog servers
You can also set the JMX service port with the JMXServicePort server property.
The JMX connector port is used for communication from JMX clients. To specify the JMX connector port, use the following command-line option:
You can also set the JMX connector port with the JMXConnectorPort server property.
hostA:2809,hostB:2809
The client can also receive callbacks from container servers when using the DataGrid API. These callbacks communicate using IIOP with the ORB listener port. To specify the port and network adapter to receive callbacks, set the listenerHost and listenerPort properties in the client properties file.
-jvmArgs -Dcom.ibm.CSI.SSLPort=<sslPort>