Hitachi

uCosminexus Application Server Operation, Monitoring, and Linkage Guide


17.10.3 Starting and stopping a system when there is a planned node switching in the 1-to-1 node switching system

This subsection describes the planned node switching of the executing node and standby node for the issues other than the problems in the 1-to-1 node switching system. When the node is switched, the Application Server must be in standby status in the standby node host.

The following points describe how to switch the executing node and standby node in the 1-to-1 node switching system in a planned manner. Note that the active node host is presumed to be running as the executing node.

  1. If you have not specified the settings to collectively stop the logical servers exist in the management domain in the script for stopping the Administration Agent, stop each logical server of the executing node host.

    You need not execute this step if you specify settings to stop the logical server in the script for stopping the Administration Agent. For stopping the logical servers, see the following manuals:

    • In a system executing J2EE applications

      See 4.1.4 Methods of stopping a system in the uCosminexus Application Server Management Portal User Guide.

    • In a system executing batch applications

      See 6.1.4 Methods of stopping a system in the uCosminexus Application Server Management Portal User Guide.

  2. Execute the monswap command in the executing node host to switch the nodes.

    # monswap server-identification-name

    In the underlined part, specify the server identification name specified in the operand 'alias' of the servers file.

    The processes defined in the script for stopping the Administration Agent are executed and the Application Server of the executing node host stops. Thereafter, the Application Server will start in the node that was in standby status until now. Thus, the planned node switching procedure is complete.

Reference note