2.5.1 Monitoring the system operations

You need to maintain stable operating conditions by checking that the status of a logical server and the statistics of a running system are appropriate. You also need to determine whether tuning is required based on the system performance output in the statistics.

This subsection gives an overview of operations that monitor the system operations. The following table describes the monitoring of system operation:

Table 2‒3: Monitoring system operations
Operation contents	Measure	Operation overview	Reference manual	Section
Monitoring the status of service units	Smart Composer functionality commands (`cmx_list_status` command)	You can check the status of service units in the Web system and can monitor that the system is running normally.	This manual	2.5.2(1)
Monitoring the status of a logical server	Management command (`mngsvrutil`)	You can check the status of hosts and servers that configure the system and monitor whether the system is running normally. Based on this information, you can start, stop, and restart the system, as required. You can confirm the status of a logical server in the following units: Management domain unit Host unit Logical server unit		2.5.2(2)
Monitoring system operations	Statistics collection function^{#1 #2}	The operational statuses of the monitored J2EE server or batch server can be output to statistics files. By monitoring the system performance, you can find the locations in the system where errors occur and this can help for performance tuning.		3.2
	Management command (`mngsvrutil`)	The operational statuses of the monitored J2EE server or batch server can be output to a CSV file or an SNMP integration format file. By monitoring the system performance, you can find the locations in the system where errors occur and this can help for performance tuning.		8.2
	Function for monitoring resource depletion^{#1 #3}	By monitoring the transition of usage rate and the number of resources, the system can output a message when the usage rate or the number of used resources exceeds the threshold value. The system can periodically output the transition of usage rate and number of used resources as the resource depletion monitoring information. When the threshold value is exceeded, you can prevent the occurrence of an error by analyzing the cause based on the output resource depletion monitoring information and take an appropriate action. Further, the resource depletion monitoring information is useful in analyzing the cause of an error.		4.2
	Management command (`mngsvrutil`)	You can check the statistics for CTM^#4 that exist in the management domain for the following units: All CTM of the management domain Specified CTM from the management domain or the CTM that exists on a specified host		Chapter 10
Checking the transaction information	Server management commands (`cjlisttrn`)	You check information, such as the transaction status on running J2EE servers or the existence of a pending transaction on the stopped J2EE servers.	Common Container Functionality Guide	3.15.9

#1: Since the file is output at a regular interval that is set when building a system, there is no need to use tools such as server management commands and the management command to output the file.
#2: The number of Full GC occurrences and the number of pending requests for each URL group are output to statistics files. When either of these numbers exceeds their thresholds, a message is output (threshold event). Using this message, you can issue a management event and automate the corresponding action as the management action. For details on the threshold event settings, see 3.4.4 Settings for the execution environment (J2EE server settings). For details on the settings for the automatic execution of processes using Management events, see 9.4 Settings for automatic execution of processes by management events.
#3: When the resource usage status exceeds the threshold, a management event can be issued. If a management event is used, the action can be automated as a management action. For details on how to set up the automatic execution of processes with Management events, see the section 9.4 Settings for automatic execution of processes by management events.
#4: You can use the CTM only in the products in which Cosminexus Component Transaction Monitor is included in the component software. For products that you can use, see 2.2.1 Relationship of products and component software in the manual uCosminexus Application Server Overview.

To Page Top