2.5.2 Monitoring the status

In Application Server, you can monitor that the operations of the system are functioning normally by monitoring the status. The status can be monitored in the following two ways:

Monitoring the status of the service unit

You can monitor the status of the service unit.
Monitoring the status of the logical server

You can monitor the status of a logical server.

Reference note

Server management commands can be used to monitor the status of the application that is running on the server and display the transaction information of the running J2EE server or batch server.

Organization of this subsection

(1) Monitoring the status of service units
(2) Monitoring the status of a logical server

(1) Monitoring the status of service units

You can use the Smart Composer functionality command (cmx_list_status command) to monitor the operational status of service units. For using the cmx_list_status commands, see cmx_list_status (Display a status of service unit) in the uCosminexus Application Server Command Reference Guide. In the case of monitoring the status of the service unit, you can output the status of a specific service unit or the status of all the service units in the Web system, to a file in CSV format.

To Page Top

(2) Monitoring the status of a logical server

In the case of monitoring the status of the logical server, you can use the management commands (mngsvrutil) to monitor the status of the logical server. The status information can be output to a standard output, or a CSV format file.

This section describes how to monitor the statistics (status) of a logical server, and the items that you can monitor.

Reference note

You can use the following methods to check the status of a Management Server and Administration Agent:

check subcommand of the management command (mngsvrutil)
adminagentcheck command

For details on the management commands and the adminagentcheck commands, see mngsvrutil (Management Server management command) and adminagentcheck (check Administration Agent activation) in the uCosminexus Application Server Command Reference Guide.

(a) How to monitor the status

You can use the management command (mngsvrutil) to monitor the status of a logical server.

To monitor the status of logical servers, specify the subcommand list in the management command (mngsvrutil). As a result, you can output the status information of the logical server in the standard output, or a CSV format or an SNMP integration format file.

You can specify a logical server for which you want to output the status by specifying the value in arguments of the list.

For details on the management commands and there subcommands, see 7.3 Details of subcommands of the mngsvrutil command in the uCosminexus Application Server Command Reference Guide.

The execution format and example of execution are described below:

When the logical server name and status information in a management domain are output
Execution format
```
mngsvrutil -m host-name-of-the-Management-Server[:port-number] -u management-user-ID -p management-password list status
```
Execution example

mngsvrutil -m mnghost -u user01 -p pw1 list status
When the J2EE application name and status information imported in a specified logical server are output
Execution format
```
mngsvrutil -m host-name-of-the-management-server[:port-number] -u management-user-ID -p Management-password -t logical-server-name list appStatus
```
Execution example

mngsvrutil -m mnghost -u user01 -p pw1 -t J2Eeserver1 list appStatus

(b) Items that you can check by monitoring the status

You can confirm the start and stop status of a logical server by monitoring the status. You can also confirm the status of all logical servers.

You can confirm the status for each of the following:

Management domain unit

You can confirm the status of all logical servers included in a management domain at the same time.
Host unit

You can confirm the status of all logical servers in a selected host.
Logical server unit

You can check the status of selected logical servers. You can check the status for each type and for individual logical server.

The following table describes types and meanings of a status that you can confirm:

Table 2‒4: Types and meaning of operational status
Operational status	Description
Stop	An initial state of a logical server or a state in which a logical server is terminated after reception of a termination request, and completing the termination process. In this state, it is confirmed that the management agent is terminated after restoring the communication failure.
Start	A state where a logical server is being started, after reception of a start request until the logical server is operational.
Run	A state where a logical server is operational, after reception of a start request and completing the start process. Alternatively, this is a state in which it is confirmed that the management agent is operational after restoring the communication failure.
Termination in-process	A state where a logical server is being terminated, after reception of a termination request until the logical server is terminated.
Forced termination in-process	A state where a logical server is being terminated forcefully, after reception of a forced termination request until the logical server is terminated.
Abnormal termination	A state where it is detected that a logical server is terminated without reception of a termination request.
Recovery in-process	A state where a logical server is being started, after reception of a start request in the abnormal termination state until the logical server is operational.
Communication failure	A state where there is a communication failure with a management agent, and the status cannot be displayed.
Automatic termination in-process	A state where a logical server is being terminated forcefully, after reception of a notification of abnormality (notification that a process exists but is not running) of the logical server from a management agent.
Automatic restart in-process	A state in which a running logical server with auto restart specifications, is being automatically restarted on reception of a notification for termination from a management agent.
Planned termination in-process	A planned termination state of a logical Web server until the actual termination, after receipt of a planned termination request. Only a logical Web server goes into this state.

To Page Top