WebSphere eXtreme Scale Administration Guide > Administer the WebSphere eXtreme Scale environment > Start stand-alone WebSphere eXtreme Scale servers
Configure ports in stand-alone mode
A Java™ virtual machine that hosts a catalog service instance requires four ports. Two ports are used for internal use, the third port is used for clients and container shards to communicate with Internet Inter-ORB Protocol (IIOP), and the fourth port is used for Java Management Extensions (JMX) communication.
Catalog service Java virtual machine (JVM) end points
eXtreme Scale uses IIOP mainly to communicate betweenJava virtual machines. The catalog service Java virtual machines are the only Java virtual machines that require the explicit configuration of ports for the IIOP services and group services ports. The internal ports are specified using the -catalogServiceEndPoints command line option:-catalogServiceEndPoints <server:host:port:port,server:host:port:port>
With the -catalogServiceEndPoints command line option, you can configure two ports per server. The IIOP ports are configured using the following command line options:-listenerHost <host_name> -listenerPort <port>
When each catalog service JVM is started, specify the complete set of catalog service end points along with a single listener port for that JVM.
Container JVM end points
The container Java virtual machines use two ports. One port is for internal use and the other port is for IIOP communication. The container Java virtual machines normally automatically find unused ports and then configure themselves to use two dynamically created ports. This automatic process minimizes configuration. However, when firewalls are being used or you want explicitly configure ports, you can use a command line option to specify the Object Request Broker (ORB) port to use:-listenerHost <host_name> -listenerPort <port>
With these command line options, you can specify the host name (important for binding to correct network card) and the port to be specified for that JVM. You can specify the internal port with the -haManagerPort command line argument. However, for the simplest configuration, you can let the run time choose the ports.
- Start the first catalog server on hostA. An example of the command follows:./startOgServer.sh cs1 -listenerHost hostA -listenerPort 2809 -catalogServiceEndPoints cs1:hostA:6601:6611,cs2:hostB:6601:6611
- Start the second catalog server on hostB. An example of the command follows:./startOgServer.sh cs2 -listenerHost hostB -listenerPort 2809 -catalogServiceEndPoints cs1:hostA:6601:6611,cs2:hostB:6601:6611
Clients need only to know the catalog service listener end points. Clients retrieve end points for container Java virtual machines, which are the Java virtual machines that hold the data, automatically from the catalog service.
To connect to the catalog service in the previous example, the client should pass the following list of host:port pairs to the connect API:hostA:2809,hostB:2809
To start a container JVM to use the example catalog service, use the following command:./startOgServer.sh c0 -catalogServiceEndPoints hostA:2809,hostB:2809
Parent topicStart stand-alone WebSphere eXtreme Scale servers