Starting the catalog service in a stand-alone environment

You must start the catalog service manually when you are using a distributed WebSphere eXtreme Scale environment that is not running in WebSphere® Application Server.

Before you begin
If you are using WebSphere Application Server, the catalog service automatically starts within one of the existing processes. See Starting the catalog service in WebSphere Application Server for more information.
About this task
The catalog service can run in a single process or can include multiple catalog servers to form the catalog server grid. A catalog server grid is required in a production environment for high availability. For more information on how to configure a catalog server grid, see Catalog service clusteringthe information about catalog service clustering in the Product Overview. The catalog service, whether it is placed in a grid or in a single process, is started using the startOgServer script. You can also specify additional parameters to the script to bind the Object Request Broker (ORB) to a specific host and port, specify the domain, or enable security.

When you call the start command, use the startOgServer.sh script on Unix platforms or startOgServer.bat on Windows®.