Cubing — Starting, stopping, or restarting cube servers

In the Administration Console, you can start, stop, or restart cube servers that are on local or remote hosts.

Before you begin

Start the Administration Console.
Ensure that the Cubing Services feature is installed.
To start, stop or restart a cube server that is on a remote host, you need to first create a cube server, and specify the correct host name, user id password, connection type, Cubing Services installation path, and JVM installation path for the remote cube server. You also need to ensure that the cube servers and the Administration Console share a common repository. If the remote host uses REXEC or RSH protocols, you need to enable them on the remote host. For more information on how to enable RSH and REXEC on Solaris 10, Linux and AIX®, refer to Enabling RSH and REXEC protocols for cube servers on Solaris 10, Linux, and AIX
To start, stop or restart a cube server that is on a local or remote host on Windows, you need to configure both the cube server host and the host where the Administration Console is installed. To learn more about the configurations, see Setting up and troubleshooting RXA for cube servers on Windows.

Procedure

To start, stop, or restart cube servers:

Select the Cubing Services tab, and click Manage Cube Servers. A list of available cube servers is displayed.

Select one or more cube servers from the list, then click one of the icons to start, stop or restart the cube servers.

Option	Description
	This command starts one or more cube servers. Starting a cube server makes the cube server's cubes available to OLAP clients. Cubes that were added to a cube server will be automatically started if the option Start cubes when cube server starts is enabled for the selected cube server. Cubes might not be immediately available to OLAP clients after the cube server starts because cube startup might take several minutes for large cubes. If the WebSphere® Application Server for the Administration Console is stopped, the cube server will continue to run. Log messages that are generated by the cube server during startup are logged in the Administration Console log file. Log messages that are generated by a cube server after startup completes are recorded in the cube server log files. For more information, refer to Creating a cube server. A cube server can also be started using a Windows service or UNIX daemon if one is configured for this cube server. For more information, refer to Running the Cubing Services Cube Server as a standalone process.
	This command stops one or more cube servers. All cubes on the selected cube server will be stopped and will no longer be available for OLAP clients. Log messages that are generated by the cube server during shutdown are logged in the Administration Console log file. A cube server can also be stopped using a Windows service or UNIX daemon if one is configured for this cube server. For more information, refer to Running the Cubing Services Cube Server as a standalone process.
	Restarts one or more cube servers

Option

Description

This command starts one or more cube servers.

Starting a cube server makes the cube server's cubes available to OLAP clients.
Cubes that were added to a cube server will be automatically started if the option Start cubes when cube server starts is enabled for the selected cube server.
Cubes might not be immediately available to OLAP clients after the cube server starts because cube startup might take several minutes for large cubes.
If the WebSphere® Application Server for the Administration Console is stopped, the cube server will continue to run.
Log messages that are generated by the cube server during startup are logged in the Administration Console log file. Log messages that are generated by a cube server after startup completes are recorded in the cube server log files. For more information, refer to Creating a cube server.

A cube server can also be started using a Windows service or UNIX daemon if one is configured for this cube server. For more information, refer to Running the Cubing Services Cube Server as a standalone process.

This command stops one or more cube servers.

All cubes on the selected cube server will be stopped and will no longer be available for OLAP clients.
Log messages that are generated by the cube server during shutdown are logged in the Administration Console log file.

A cube server can also be stopped using a Windows service or UNIX daemon if one is configured for this cube server. For more information, refer to Running the Cubing Services Cube Server as a standalone process.

Restarts one or more cube servers

If you select multiple cube servers, the servers are started, stopped, or restarted sequentially in the order that they appear in the cube server list. The operation is performed for all selected cube servers even if the task fails for one or more cube servers. For example, if you select three cube servers to start and the operation fails for the first cube server in the list, the operation continues for the other cube servers that were selected from the list.

Note: If you shut down the application server, and therefore the Administration Console, any running cube servers are not automatically shut down because the cube server is independent from the application server.