17.10.1 Starting the 1-to-1 node switching system

This subsection describes the points you must keep in mind when you start the system using the 1-to-1 node switching system and the procedure for starting the system.

Organization of this subsection

(1) Points to remember when starting the system
(2) Procedure to start the system

(1) Points to remember when starting the system

Keep the following points in mind when you start a system using the 1-to-1 node switching system:

The HA monitor deployed on the host of active node and spare node starts simultaneously as the OS.
If you are using the Management Server to start the 1-to-1 node switching system of Application Server, make sure that you start the Management Server beforehand. For starting the Management Server, see 4.1.1 Procedure for starting a system and 4.1.2 Methods of starting a system in the uCosminexus Application Server Management Portal User Guide.
When starting the 1-to-1 node switching system of the management server, start the Administration Agent of the Application Server existing in the management domain in advance, if the application server is deployed on another host. For starting the Administration Agent, see 4.1.2 Methods of starting a system in the uCosminexus Application Server Management Portal User Guide.

To Page Top

(2) Procedure to start the system

To start a system using the 1-to-1 node switching system:

Execute the monbegin command in the active node host to start the active node host as the executing node.
```
# monbegin server-identification-name
```
In the underlined part, specify the server identification name specified in the operand 'alias' of the servers file.

As a result, the processes defined in the script file to start the Administration Agent are executed and the active node host will start as the executing node.
Execute the monbegin command in the spare node host to start the spare node host as the standby node.
```
# monbegin server-identification-name
```
In the underlined part, specify the server identification name specified in the operand 'alias' of the servers file.

As a result, the spare node host becomes the standby node and prepares for the failure in the executing node.

Important note

If you have not specified settings to collectively start the logical servers exist on the management domain when the Management Server starts, you start each logical server for the active node host. Note that if you have specified settings to collectively start the logical servers present in the management domain when the Management Server starts, you need not start the logical servers manually. For the startup methods, see the following manuals:

In a system executing J2EE applications

See 4.1.1 Procedure for starting a system and 4.1.2 Methods of starting a system in the uCosminexus Application Server Management Portal User Guide.
In a system executing batch applications

See 6.1.1 Procedure for starting a system and 6.1.2 Methods of starting a system in the uCosminexus Application Server Management Portal User Guide.

Reference note: For details on the servers file definition (server environment settings in the HA monitor), see 17.7.7 Server-compliant environment settings.

To Page Top