Catalog service domain settings~wxs956

Use this page to manage the settings for a specific catalog service domain. Catalog service domains define a group of catalog servers that manage the placement of shards and monitors the health of container servers in your data grid. You can define a catalog service domain that is in the same cell as your deployment manager. You can also define remote catalog service domains if your WebSphere® eXtreme Scale configuration is in a different cell or your data grid is made up of Java SE processes.~wxs957

To view this administrative console page, click ~wxs958System administration~wxs959 > ~wxs960WebSphere eXtreme Scale~wxs961 > ~wxs962Catalog service domains~wxs963 > ~wxs964catalog_service_domain_name~wxs965.~wxs966

Test connection~wxs967

When you click the ~wxs968Test connection~wxs969 button, all of the defined catalog service domain end points are queried one by one, if any one end point is available, returns a message that indicates that the connection to the catalog service domain was successful. You can use this button to test that you have configured the connection and security information correctly.~wxs970

Name~wxs971

Specifies the name of the catalog service domain. ~wxs972

Enable this catalog service domain as the default unless another catalog service domain is explicitly specified~wxs973

If you select this check box, the selected catalog service domain becomes the default catalog service domain for the cell. Each server profile in the cell that is augmented with the WebSphere eXtreme Scale profile belongs to the selected catalog service domain. ~wxs974

For WebSphere eXtreme Scale, all eXtreme Scale containers that are embedded in Java EE application modules connect to the default domain. Clients can connect to the default domain using the ~wxs975ServerFactory.getServerProperties().getCatalogServiceBootstrap()~wxs976 API to retrieve the catalog service endpoints to use when calling the ~wxs977ObjectGridManager.connect()~wxs978 API.~wxs979

If you change the default domain to point to a different set of catalog servers, then all containers and clients refer to the new domain after they are restarted.~wxs980

Catalog servers~wxs981

Specifies a list of catalog servers that belong to this catalog service domain.~wxs982

Click ~wxs983New~wxs984 to add a catalog server to the list. This catalog server must already exist in the eXtreme Scale configuration. You can also edit or delete a server from the list by selecting the endpoint and then clicking ~wxs985Edit~wxs986 or ~wxs987Delete~wxs988.  Define the following properties for each catalog server endpoint:~wxs989

Catalog server endpoint~wxs990
Specifies the name of the existing application server or remote server on which the catalog service is running. A catalog service domain cannot contain a mix of existing application servers and remote server endpoints. ~wxs991
  • Existing application server~wxs992: Specifies the path of an application server, node agent, or deployment manager in the cell. A catalog service starts automatically in the selected server. Select from the list of the existing application servers. All of the application servers that you define within the catalog service domain must be in the same core group.~wxs993
  • Remote server~wxs994: Specifies the host name of the remote catalog server.~wxs995

    For WebSphere eXtreme Scale remote endpoints~wxs996: Specifies the host name of the remote catalog server process. You must start the remote servers with the ~wxs997startOgServer~wxs998 script or the embedded server API.~wxs999

    For WebSphere DataPower® XC10 Appliance remote endpoints~wxs1000: Specifies the host name of the appliance.~wxs1001

Client Port~wxs1002
Specifies the port that is used for communication between the catalog servers in the catalog service domain. This value is required for catalog servers that are running in WebSphere Application Server processes. You can set the value to any port that is not being used by another process.~wxs1003
Listener Port~wxs1004
Specifies the port that is used for communication with clients. This value is required for remote endpoints and must match the value used when the catalog service was started. The listener port is used by clients and containers to communicate with the catalog service. ~wxs1005
For WebSphere eXtreme Scale remote endpoints~wxs1006: Defines the Object Request Broker (ORB) listener port for containers and clients to communicate with the catalog service through the ORB. For WebSphere Application Server endpoints, the listener port value is inherited from the BOOTSTRAP_ADDRESS port configuration.~wxs1007
For WebSphere DataPower XC10 Appliance remote endpoints~wxs1008: Use the value ~wxs10092809 for the appliance remote endpoints.~wxs1010
Status~wxs1011
Table 1. Catalog server endpoint status~wxs1012
Icon~wxs1013 Definition~wxs1014
Unknown~wxs1015
Unknown~wxs1016
Started~wxs1017
Started~wxs1018
Stopped~wxs1019
Stopped~wxs1020