Creating catalog service domains in WebSphere Application Server
Catalog service domains define a group of catalog servers that manage the placement of shards and monitor the health of container servers in your data grid.
Before you begin
- Install WebSphere® eXtreme Scale on WebSphere Application Server. See Installing WebSphere eXtreme Scale or WebSphere eXtreme Scale Client with WebSphere Application Server
About this task
By creating a catalog service domain, you are defining a highly available collection of catalog servers.
These catalog servers can run in WebSphere Application Server within a single cell and core group. The catalog service domain can also define a remote group of servers that run in different Java™ SE processes or other WebSphere Application Server cells.
For catalog servers that run on existing application servers within the cell: When you define a catalog service domain that places catalog servers on the application servers within the cell, the core group mechanisms of WebSphere Application Server are used. The catalog service automatically starts on the application servers in the cell. As a result, the members of a single catalog service domain cannot span the boundaries of a core group, and a catalog service domain therefore cannot span cells. However, WebSphere eXtreme Scale container servers and clients can span cells by connecting to a catalog server across cell boundaries, such as a stand-alone catalog service domain or a catalog service domain embedded in another cell.
For remote catalog servers: You can connect WebSphere eXtreme Scale containers and clients to a catalog service domain that is running in another WebSphere Application Server cell or that are running as stand-alone processes. Because remotely configured catalog servers do not automatically start in the cell, you must manually start any remotely configured catalog servers. When you configure a remote catalog service domain, the domain name should match the domain name that you specified when you start the remote catalog servers. The default catalog service domain name for stand-alone catalog servers is DefaultDomain. Specify a catalog service domain name with the startOgServer or startXsServer command -domain parameter, a server properties file, or with the embedded server API. You must start each remote catalog server process in the remote domain with the same domain name. See Starting a stand-alone catalog service that uses the ORB transport for more information about starting catalog servers.