17.8.4 Starting and stopping the system during maintenance of the 1-to-1 node switching system of Application Server

In the executing node host, stop the running J2EE application and resource adapter.

In case of a batch server, check that the batch application is not running and then stop the resource adapter.

For stopping the system, see Appendix F.4 How to terminate a system in the uCosminexus Application Server Command Reference Guide.

Use the server management commands to execute the maintenance process.

For operations of the server management commands, see 3. Basic Operations of Server Management Commands in the uCosminexus Application Server Application Setup Guide.

Start the J2EE application and resource adapter that you stopped in step 1.

In case of the J2EE server, start the J2EE application and resource adapter. In case of the batch server, start the resource adapter.

For the startup methods, see Appendix C.2 How to start a system in the uCosminexus Application Server Command Reference Guide.

As and when required, check the operation of the J2EE application and resource adapter.

From the Start menu, select Control Panel - Performance and Maintenance - Management Tools, and then select Cluster Administrator.

The Cluster Administrator starts.

In the console tree (left pane), select the resource group that contains the executing node and standby node, and then from the File menu, choose Migrate Group.

The nodes switch.

In the executing node host following switching, execute step 1. to step 6.

To return the post-switching executing node host to the executing node, in the console tree (left pane), select the resource group that contains the executing node and standby node, and then from the File menu, choose Migrate Group.

Maintenance is complete.

When you have not specified the settings for batch stop of the logical servers, stop each logical server in the executing node host.

This step is not required when you have specified the settings for batch stop with the Management Server. For stopping the logical servers, see the following manuals:

• In a system executing J2EE applications

  See 4.1.3 Procedure for stopping a system and 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.3 Procedure for stopping a system and 6.1.4 Methods of stopping a system in the uCosminexus Application Server Management Portal User Guide.

From the Start menu, select Control Panel - Performance and Maintenance - Management Tools, and then select Cluster Administrator.

The Cluster Administrator starts.

In the console tree (left pane), select the resource group that contains the executing node and standby node, and then from the File menu, choose Set to Offline.

The resource group containing the executing node and standby node goes offline.

In the console tree (left pane), select the spare node, and then from the File menu, choose Stop Cluster Service.

The cluster service of the spare node stops.

In the console tree (left pane), select the active node, and then from the File menu, choose Stop Cluster Service.

The cluster service of the active node stops.

In the active node and spare-node host, execute the maintenance operation including changing the definition file.

In the console tree (left pane), select the active node, and then from the File menu, choose Start Cluster Service.

The cluster service of the active node starts.

In the console tree (left pane), select the spare node, and then from the File menu, choose Start Cluster Service.

The cluster service of the spare node starts.

In the console tree (left pane), select the resource group that contains the active node and spare node, and then from the File menu, choose Set to Online.

The 1-to-1 node switching system restarts.

When you have not specified the settings for batch start of the logical servers, start each logical server in the executing node host.

This step is not required when you have specified the settings for batch start with Management Server. For the startup method, 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.

In the executing node host, confirm the operation related to definition changes as and when required.

Maintenance is complete.

In the spare-node host, execute the maintenance operation including changing the definition file.

From the Start menu, select Control Panel - Performance and Maintenance - Management Tools, and then select Cluster Administrator.

The Cluster Administrator starts.

In the console tree (left pane), select the resource group that contains the executing node and standby node, and then from the File menu, choose Migrate Group.

Application Server running on the executing node host stops, and Application Server starts on the node that was in standby status until now. As a result, the host for which you have already performed maintenance becomes the executing node host.

In the post-switching executing node host, confirm the operation related to definition changes as and when required.

In the post-switching standby node host, execute the maintenance operation including editing of definition files.

To return the post-switching executing node host to the executing node, in the console tree (left pane), select the resource group that contains the executing node and standby node, and then from the File menu, choose Migrate Group.

In the post-switching executing node host, confirm the operation related to definition changes.

Maintenance is complete.