Top
Systemwalker Service Quality Coordinator User's Guide
Systemwalker

5.4 Service operation watch time-out value setting

This section explains the procedure for setting a separate timeout value for each monitored object for service operation monitoring.

Point

Use this procedure if the timeout values for service operation monitoring need to be changed while service operation management is being performed.

Privileges required for execution

[Windows]

The privileges of a user belonging to the "Administrators" group are required to make these settings.

[UNIX]

System administrator (superuser) privileges are required to make these settings.


Storage location

The storage location of this file is as follows:

[Windows]

<Variable file directory>\control\template.dat

[UNIX]

/etc/opt/FJSVssqc/template.dat


The service operation monitoring function has two types of timeouts.


Approach for defining monitored objects

Performance information records are not created if collection timeouts occur. This means that definitions must be made so that collection timeouts do not occur, in order to perform successful monitoring.

If there are multiple monitored objects, the number of monitored objects and the values for monitoring timeouts and collection timeouts must satisfy the condition shown in the formula below, in order to take into account the possibility that timeouts will occur for all monitored objects.

Number of monitored objects * Monitoring timeout (10 seconds) < Collection timeout (70 seconds)

Note: The maximum number of monitored objects is set at six by default.


The following items for the service operation monitoring function can be changed using the template file.

Note

The larger the value specified for the monitoring timeout value, the less objects can be monitored, so take into account the number of monitored objects when specifying the monitoring timeout.

A warning message will be output if, as a result of the settings in "A.2 Response/Operation Information Collection Policy Creation Command", the number of monitored objects and the timeout values do not satisfy the condition shown in the formula above. However, the policy will be created even though the warning message is output.

If there are a lot of monitored objects, or if there is a problem with the settings for the monitored objects, the command may take a long time to return.


Information used

Collection timeout

template.dat PING section CMDTIMEOUT parameter Default value: 70 seconds

Monitoring timeout

template.dat PING section TIMEOUT parameter Default value: 10 seconds

Number of monitored objects

ServiceConf.xml The number of monitored objects for each monitoring type