IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerworks > My developerWorks >  Dashboard > WebSphere eXtreme Scale V6.1 User Guide > Reference > Configuring ObjectGrid TCP ports when running inside WebSphere ND application servers
developerWorks
Log In   View a printable version of the current page.
Overview Connect Spaces Forums Wikis
Configuring ObjectGrid TCP ports when running inside WebSphere ND application servers
Browse space Browse Space    
Added by bnewport, last edited by bnewport on Nov 16, 2007
Labels: 
(None)

Catalog service endpoints

The catalog service runs a single instance within the deployment manager by default. It will use the IIOP Bootstrap port for the deployment manager JVM. Web applications or EJB applications within that cell can connect to grids within the cell using the null,null connect call rather than specifying catalog service bootstrap ports.

Clients outside the cell (including J2SE clients) would connect to the catalog service using the the deployment manager host name and the IIOP bootstrap port.

Group membership and JMX ports

ObjectGrid reuses the HAManager DCS ports for group membership. JMX ports are also reused.

 
    About IBM      Privacy      Contact