Administration guide > Configure the deployment environment > Configuring catalog and container servers
Configure WebSphere eXtreme Scale with WAS
You can run catalog service and container server processes in WAS. The process to configure these servers is different than a stand-alone configuration.
The catalog service can automatically start in WAS servers or deployment managers. Container process start when an eXtreme Scale application is deployed and started in the WAS environment.
Attention: Do not collocate the container servers with catalog servers in a production environment. Include the catalog service in multiple node agent processes or in an application server that is not hosting an eXtreme Scale application.
- Configure the catalog service in WAS
Catalog service processes can run in WAS. The server life cycle in WAS determines when the catalog service starts and stops.
- Configure container servers in WAS
Configure container servers in WAS by using a server properties file and deployment policy XML file that is embedded into a Java EE application module. Container servers stop and start when the application is stopped and started.
Parent topic:Configure catalog and container servers
Best practice: Clustering the catalog service
Configure multi-master replication topologies
Server properties file