Administration guide > Configure the deployment environment > Configuring ports



Configure ports in a WebSphere Application Server environment

WebSphere eXtreme Scale catalog services, container servers and clients, when running in WAS processes, utilize ports and services already defined for the process.

The following sections explain details relating to using ports in the deployment.

  1. Catalog service endpoints

    WebSphere eXtreme Scale catalog services run in any WAS process and are configured using the administrative console or using administrative tasks. All ports are inherited by the process except for the client port, which is explicitly configured. For details on which ports are used by the catalog service, see Plan for network ports. For details on configuring a catalog service domain, see High-availability catalog service.

  2. Container server endpoints

    WebSphere eXtreme Scale container servers are hosted within Java EE modules. The container servers use the ports defined for the application server process. For details on which ports are used by the container service, see Plan for network ports. For details on starting a container within a Java EE module such as an Enterprise JavaBeans™ (EJB) or Web module, see Configure WAS applications to automatically start container servers.

  3. Client endpoints

    WebSphere eXtreme Scale clients are hosted within Java EE web or EJB modules.

    Clients programmatically connect to the catalog service domain using the ObjectGridManager.connect() API. When connecting to a catalog service domain hosted within the same cell, the client connection will automatically find the default catalog service domain by using the following API call on the ObjectGridManager:

    connect(securityProps, overRideObjectGridXML)
    

    If the default catalog service domain is hosted remotely (external to the cell), the catalog service endpoints must be specified using the following method on the ObjectGridManager API:

    connect(catalogServerAddresses, securityProps, overRideObjectGridXml)
    

    If the default catalog service domain is defined in the cell, then the CatalogServerProperties API can be used to retrieve the catalog server addresses. The XSDomainManagement administrative task can also be used to retrieve any configured catalog service domain endpoints.


Parent topic:

Configure ports


Related concepts

Plan for network ports

Servers with multiple network cards


Related tasks

Configure ports in stand-alone mode

Related reference

Interface CatalogServerProperties