Stopping secure servers

Stopping secure catalog servers or container servers requires one security configuration file.

• Stop a secure catalog server or container server in stand-alone deployments.
  In stand-alone environments, stop WebSphere® eXtreme Scale catalog and container servers using the teardown function of the xscmd command, or using the stopXsServer or stopOgServer commands.

  Restrict access to these operations to authorized administrators only, as described in the section Authorizing access for administrative operations in stand-alone environments. When authentication or SSL is used, the stopXsServer and stopOgServer commands require that a client properties file be passed as a parameter. The content of the client properties file is described in Authenticating client requests in stand-alone environments and Securing data that flows between eXtreme Scale servers in stand-alone environments with SSL encryption.

• Use the WebSphere Application Server administrative console to stop eXtreme Scale server that run with WebSphere Application Server.
  WebSphere Application Server administrative security should be configured to restrict access for starting and stopping servers to authorized administrators, as described in Authorizing access for administrative operations in WebSphere Application Server.