6.2.8 Notes on execution of service linkage objects monitoring jobs

This subsection provides notes on executing service linkage objects monitoring jobs.

• Consider the options of the information acquisition command line executed by service linkage objects monitoring jobs so that the number of objects to be obtained is 5,000 or less. In addition, adjust the configuration of the linked cloud service or the command line of the information acquisition command so that the names of the objects to be obtained each have 128 bytes or less in size. For example, if you run a command with no option specified, trying to obtain the information of all the objects on the cloud service, a command with potential unlimited results can lead to degraded performance of processing, insufficient memory, or the upper limit of the standard output size, resulting in abnormal termination.

• Update the definition for authentication information quickly. A service linkage objects monitoring job reads the definition for authentication information at monitoring intervals while running. However, monitoring continues in a condition where the connection processing to the cloud service ended abnormally or the connection failed. When jobs are running in particular, do so not to interrupt your operation.

• Execution of the information acquisition command might take time and the monitoring might not be performed at the monitoring interval, depending on the status of communication with the cloud environment or when there are numerous objects on the cloud service, etc.

• If you want to guarantee the order of information on objects to be obtained from a cloud service, see the specifications of the information acquisition command you use and specify the object monitoring definition. When a generic name (wildcard character) is used in Name of the object to be monitored, the value stored in the passing information depends on the specifications of the information acquisition command. Therefore, verify in what order the information is passed and then design your use of macro variables in succeeding jobs.

• Wildcard characters available in Name of the object to be monitored are * and \ that is used to escape *. Other characters such as ., ^, $, |, [, ], (, ), {, }, +, ?, which are used as generic names, are treated as literal characters.

• A service linkage objects monitoring job obtains the latest information on the JP1/AJS3 for Cloud Service Applications server. Therefore, if you change definitions used for the service linkage objects monitoring jobs on the JP1/AJS3 for Cloud Service Applications server, the service linkage objects monitoring job may not correctly operate.

  When changing definitions on the JP1/AJS3 for Cloud Service Applications server, make sure that the service linkage objects monitoring job operates correctly.

• Service linkage objects monitoring jobs are custom event jobs. The return codes that can be checked with JP1/AJS3 include the return codes of service linkage objects monitoring jobs and the return codes set by JP1/AJS3, which is described in Checking the return code of a job in the manual JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

• Check in advance if a command can be executed in the environment before executing a service linkage objects monitoring job.

  When the command defined on the JP1/AJS3 for Cloud Service Applications server does not exist, the command defined on the JP1/AJS3 for Cloud Service Applications server ends with a return value other than 0.

• When the execution host of the service linkage objects monitoring job is on Windows, there is a limitation on the number of characters of OS command lines. Set the number of characters of command lines (command lines after the variable replacement) defined on the JP1/AJS3 for Cloud Service Applications server to be approximately 8000. If the number of characters exceeds the limitation on OS command lines, the command defined on the JP1/AJS3 for Cloud Service Applications server ends with a value other than 0.

• The upper limit on the output size is 10,240 KB, even if settings are made to output the standard output and the standard error output for execution commands in Output settings for detailed execution results and Log output settings in the monitoring definition.

• When multiple service linkage object monitoring jobs run same time on one agent, monitoring processes are execute parallel.

  The maximum number of items that can be monitored in parallel is 20. During the monitoring process, the number of executions is exclusively occupied, and the monitoring process of the subsequent service linkage object monitoring job is in queue. Therefore, the start of the subsequent monitoring processing might be delayed. If there is a possibility that numerous monitoring processes can run at a certain point in time, consider organizing agents into groups.

To Page Top