stopOgServer script (ORB)

[Version 8.6 and later] (Deprecated) The stopOgServer script stops catalog and container servers.

Purpose

Use the stopOgServer script to stop a server. You must provide the name of the server and its catalog service endpoints.

Deprecated: The startOgServer and stopOgServer commands start servers that use the Object Request Broker (ORB) transport mechanism. The ORB is deprecated, but you can continue using these scripts if you were using the ORB in a previous release. The IBM eXtremeIO (XIO) transport mechanism replaces the ORB. Use the startXsServer and stopXsServer scripts to start and stop servers that use the XIO transport.

Location

The stopOgServer script is in the bin directory of the root directory, for example:

cd wxs_install_root/bin

Usage

To stop a catalog or container server: [Windows]

stopOgServer.bat <server_name> -catalogServiceEndPoints
<csHost:csListenerPort,csHost:csListenerPort> [options]

stopOgServer.sh <server_name> -catalogServiceEndPoints
<csHost:csListenerPort,csHost:csListenerPort> [options]

Options

-catalogServiceEndPoints <csHost:csListenerPort, csHost:csListenerPort...>

Specifies the Object Request Broker (ORB) host and port number.

For container severs: The list of catalog service endpoints should be the same as the list that was used to start the container server. If you did not specify this option when you started the container server, use the default value of localhost:2809.

For catalog servers: If you are stopping the catalog service, use the values that you indicated for the -listenerHost and -listenerPort options when you started the catalog service. If you did not specify these options when you started the catalog server, use the default value of localhost:2809. The -catalogServiceEndPoints value you use when you stop the catalog service is different from when you start the catalog service.

-clientSecurityFile <security properties file>

Specifies the path to the client properties file that defines security properties for the client. See Client properties file for more information about the security settings in this file.

-traceSpec <trace specification>

Enables trace and the trace specification string for the container server. Trace is disabled by default. This property applies to both the container server and the catalog service. Examples:

ObjectGrid=all=enabled
ObjectGrid*=all=enabled

-traceFile <trace file>

Specifies a file name to write trace information. This property applies to both the container server and the catalog service.

-jvmArgs <JVM arguments>

Specifies a set of JVM arguments. Every option after the -jvmArgs option is used to start the server Java™ virtual machine (JVM). When the -jvmArgs parameter is used, ensure that it is the last optional script argument specified.

Example:-jvmArgs -Xms256M -Xmx1G