6.2.4 Passing information of service linkage objects monitoring jobs
This subsection describes passing information of service linkage objects monitoring jobs.
- Organization of this subsection
(1) Passing information of service linkage objects monitoring jobs
In JP1/AJS3 for Cloud Service Applications, you can define what values are stored in which variables so that the values can be passed to succeeding jobs.
These variables are used to define information to be passed on for OBJECT01 through OBJECT10, which are names of passing information for the custom event job.
For example, following shows the definition example when a format, used to access a target object, which is created by combining both a packet name and an object path, //packet-name/object-path, is passed.
You use a variable, ?CSAONAME?, obtained as an object name through the JMESPath query syntax from the execution result of the information acquisition command for the object.
For example, assume that an object with the name 20230915_s1_report1.txt is detected in the path with the name /ABC/DEF/ to objects under the bucket with the name mybucket. To specify //mybucket/ABC/DEF/20230915_s1_report1.txt for the passing information name OBJECT01, in Passing information settings of the service linkage objects monitoring definition, enter //mybucket/ABC/DEF/?CSAONAME? in OBJECT01 under Name of passing information to be used as the storage destination.
In JP1/AJS3 - View, enter ?AJS2URI?:OBJECT01 in Passing of the unit definition for the service linkage objects monitoring job. This allows succeeding jobs to receive the information of the format used to access the target object using ?AJS2URI?.
The following explains the details of the variables to be used for OBJECT01 through OBJECT10, which are names of passing information for the custom event job.
(a) Values to be saved in the variables
Values set as passing information are determined by the data types of extraction position information. The following table shows the details.
|
No. |
Data type |
Information to be saved in the variables |
|---|---|---|
|
1 |
Character string |
The character string value is set as it is. |
|
2 |
Number |
Specify a numerical value that is presented as a character string and can be handled as a product. |
|
3 |
Boolean |
true or false is set. |
|
4 |
Null |
null is set. |
(b) About the variables in which object names will be saved
The information extracted by the JMESPath query statement specified in the object name is saved in the variable ?CSAONAME?.
The name of the created, updated, or deleted object is saved when creation, update, or deletion is monitored. However, when deletion is monitored and detected, a null string is saved in the variable if the condition is to be established when no objects exist.
(c) About the variables in update monitoring target information
Information extracted by the JMESPath query statement specified in the three pieces of update monitoring target information is saved in the variables ?CSAOINFO1?, ?CSAOINFO2?, and ?CSAOINFO3?. However, if the JMSPath query statement is omitted in the monitoring definition, no values are set in the omitted update monitoring target information variables after the monitoring is completed.
In addition, after the monitoring for creation, update, and deletion is completed, the following values are set:
-
In the case of creation
A value extracted by the JMESPath query statement specified in individual pieces of update monitoring target information in the object of which creation can be detected.
-
In the case of an update
A value extracted by the JMESPath query statement specified in individual pieces of update monitoring target information in the object to which updates can be detected.
-
In the case of deletion
A value extracted by the JMESPath query statement specified in individual pieces of update monitoring target information acquired during the previous monitoring.
As in the case of an object name, when deletion is detected, a null character is set if the condition is to be established when there are no objects.
(d) About system-reserved variables that can be used by default
Service linkage object monitoring jobs have the following variables, in addition to the system-reserved variables that can be used by default and are explained in 4.3.2(1) Types of variables:
|
Variable name |
Description |
|---|---|
|
?CSASOBJCOND? |
Upon completion of monitoring, save one of the following monitoring conditions that have been met:
|