Administration guide > Configure the deployment environment
Configure catalog and container servers
WebSphere eXtreme Scale has two types of servers:
Catalog servers Control the placement of shards and discover and monitor the container servers. Multiple catalog servers together comprise the catalog service. Container servers JVM that stores the application data for the data grid.
Catalog and container servers can start...
- WAS processes
- Stand-alone Java SE processes
- Embedding the servers in Java SE applications
How you configure the catalog and container servers depends on the topology.
Stand-alone catalog servers Configure with a server properties file. Catalog servers that start in WAS Configure with the WAS admin console, admin tasks, and the server properties file.
The server life cycle is controlled by the process life cycle within WAS. When processes start or stop in WAS, the catalog servers that are running on these processes also start or stop.
Stand-alone container servers Configure with a server properties file and a deployment policy XML file. Container servers that start in WAS Configure with a server properties file and deployment policy XML file that is embedded into a Java EE application module.
Container servers start and stop with the application.
Configure the catalog and container servers
- Server properties file
- Configure WebSphere eXtreme Scale with WAS
- Configure quorum
- Best practice: Clustering the catalog service
- Configure multi-master replication topologies
Parent topic:Configure the deployment environment
Configure cache integration
Containers, partitions, and shards
High-availability catalog service
Program for administrative tasks
Related tasksConfigure data grids
Configure deployment policies
Configure Object Request Brokers
Configure Spring integration
Configure the REST data service