See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
Catalog service JVM end points
A JVM hosting a catalog service instance requires four ports. Two for internal use and one for clients and container shards to communicate with it using IIOP and finally one for JMX communication. ObjectGrid uses IIOP principally for its communication between JVMs. The catalog service JVMs are the only JVMs that required the explicit configuration of ports for the IIOP services and group services ports. The internal ports are specified using the command line option:
This allows two ports per server to be specified. The IIOP ports are configured using:
When each catalog service JVM is started then the complete set of catalogServiceEndPoints should be specified along with a single listener port for that JVM. As an example lets look at starting a group of two catalog servers. First, we're start the first catalog server on hostA:
Next, we start the second catalog server on hostB:
Clients need only to know the catalog service JVMs listener end points. Clients retrieve endpoints for container JVMs (the JVMs holding the actual data) automatically from the catalog service. If a client wanted to connect to the above catalog service then the following list of host:port pairs should be passed to the connect API: "hostA:2809,hostB:2809"
If you want to start a container JVM to use the above catalog service then the command line to use would look like:
Notice that you specify the catalog service listener ports for the catalog service JVMs.
The JMX port defaults to 1099 and can be changed using the '-JMXServicePort' command line parameter.
Container JVM end points
The container JVMs use two ports. One for internal use and the other if for IIOP communication. The container JVMs normally automatically find unused ports and then configure themselves to use two dynamically created ports. This minimizes configuration. However, when firewalls are being used or the customer wants to do explicit port configuration then there is a command line option to specify the ORB port to use:
This allows the host name (important for binding to correct network card) and the port to be specified for that JVM. The listenerHost and listenerPort command line options were added starting in V6.1 ifix 2 onwards. If you need to do this then ensure you're on at least this level of ObjectGrid. The internal port can be specified in V6.1.0.3 onwards using the '-haManagerPort' command line argument. Normally, we recommend just letting the runtime pick the ports automatically for easier configuration.
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
