Description
This operation component changes the status of events.
Change the status of the event in event DB on the server that monitors the event with the operation management product such as Systemwalker Centric Manager.
Options
Basic Options
Host name or IP address of the server that is performing event monitoring.
If event monitoring is used in Systemwalker Centric Manager, specify the host name or IP address of the operation management server of the Systemwalker Centric Manager.
To execute the operation component on the Management Server, specify the following:
For IPv4: 'localhost' or '127.0.0.1'
For IPv6: 'localhost' or '::1'
An argument error occurs if the host name or IP address is omitted.
The maximum length of the host name or IP address is 1,024 characters. An argument error occurs if this is exceeded.
Specify the event number whose status is to be changed.
For an event number, specify the management number in event DB.
If event monitoring is used in Systemwalker Centric Manager, specify the monitoring event number of the Systemwalker Centric Manager.
An argument error occurs if the event number is omitted.
The maximum length of the event number is 1,024 characters. An argument error occurs if this is exceeded.
Specify the new status.
The character string to be specified is different at the operation management product that is monitoring the event.
If event monitoring is used in Systemwalker Centric Manager, specify Trouble, Dealt, Deferred, or Replied. This option is not case sensitive.
An argument error occurs if the new status omitted.
The maximum length of the new status is 1,024 characters. An argument error occurs if this is exceeded.
Advanced Options
OS type of the server that performs event monitoring.
Specify Windows, Linux or Solaris. This option is not case sensitive.
If the OS type is omitted, the Configuration Management Database (CMDB) will be searched based on the specified host name or IP address, and Systemwalker Runbook Automation automatically sets the acquired OS type as the value.
The maximum length of the OS type is 1,024 characters. An argument error occurs if this is exceeded.
Name of the user connecting with SSH to the host monitoring the event.
If the connected user name and password required for connection are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired connected user name as the value.
If the operation component connects with the file transfer infrastructure, the connected user name will be fixed at either of the following names and cannot be changed. In this case, the user name is ignored even if specified.
If the Business Server is running on Windows: SYSTEM user
If the Business Server is running on Linux or Solaris: root
The maximum length of the connected user name is 1,024 characters. An argument error occurs if this is exceeded.
Password of the user connecting with SSH to the host monitoring the event.
If the connected user name and password required for connection are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired connected user password as the value.
When connecting by using the file transfer infrastructure, it becomes invalid even if the password of the user is specified.
The maximum length of the connected user password is 1,024 characters. An argument error occurs if this is exceeded.
Name of the user changing status of the event on the host monitoring the event.
If the "execusername" and "execpassword" are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired administrator user as the value.
If not to register to CMDB, it is executed by name of the user connecting.
If the host specified in "hostname" is running on Windows and it connects with file transfer infrastructure, execute the command as a SYSTEM user. In this case, the connected user name is invalid.
The maximum length of the executing user name is 1,024 characters. An argument error occurs if this is exceeded.
This operation component does not use the value of "execpassword". The value of "execpassword" is ignored even if specified.
Specify the name of the operation management product performing event monitoring which is linked to this operation component.
If event monitoring is used in Systemwalker Centric Manager, specify "CMGR". This option is not case sensitive.
Only Systemwalker Centric Manager can be specified as a linked product with this operation component.
If the operation management product name is omitted, the Configuration Management Database (CMDB) will be searched based on the specified host name or IP address, and Systemwalker Runbook Automation automatically sets the acquired operation management product name as the value.
The maximum length of the operation management product name that can be specified is 1,024 characters. An argument error occurs if this is exceeded.
Specify the command installation path for the linked product to this operation component.
If event monitoring is used in Systemwalker Centric Manager, specify the full path name of the evtutlnt command installation directory.
If Systemwalker Centric Manager is specified to mwtype as a linked product for this operation component, installation path is able to omit.
Only Systemwalker Centric Manager can be specified as a linked product with this operation component.
The maximum length of the installation path that can be specified is 1,024 characters. An argument error occurs if this is exceeded.
This is the completion timeout (seconds) for the execution of operation components.
Values between 0 and 86400 (1 day) can be specified.
For example: When timeout is to occur every 10 minutes: 600
When the execution of the operation components is not completed even if the specified time passes, the processing of the operation components is stopped in return value 201.
This is the retry count for the execution of operation components.
Specify the count that will be retried when the operation component is finished in return value 161. Values between 0 and 5 can be specified.
When the operation components is terminated in return values other than 161 as a result of the retrying, the operation components will be terminated even if it doesn't reach the specified retry counts. The return value of the operation components returns the value executed at the end.
For example: When retries are to be performed twice: 2
This is the retry interval (seconds) for operation components.
Specify the interval that will be retried when the operation component is terminated in return value 161. Values between 1 and 14400 can be specified.
For example: When retries are to be performed at 300 seconds interval: 300
If the specification of the timeout, retry and retry_interval is omitted and a value beyond the limits of the above-mentioned is input, the value specified with the operation components definition file becomes effective. Refer to "2.5 Definition File for Operation Components" for details.
Return Values
Icon | Name | Return value | Description |
|---|---|---|---|
| Success | 0 | Changing of the event status was successful. |
| Failure | 161 | Failed to change the event status. When the retry count is specified, it will be retried. |
187 | Authentication failed when an attempt was made to connect to the event monitoring server over the network (using SSH). Alternatively, an error occurred during the processing of communications with the event monitoring server (file transfer infrastructure). In this case, the error code for the file transfer infrastructure is output to the execution results. Refer to "3.21 Detailed Code of File Transfer Infrastructure" for information on error codes. | ||
188 | When the operation of the operation component are executing to the event monitoring server into which the RBA Agents have not been introduced, the network communication (SSH communication) with the event monitoring server was disconnected. | ||
189 | An attempt to connect to the event monitoring server over the network (using SSH) failed. Alternatively, an error occurred during the processing of communications with the event monitoring server (file transfer infrastructure). In this case, the error code for the file transfer infrastructure is output to the execution results. Refer to "3.21 Detailed Code of File Transfer Infrastructure" for information on error codes. | ||
197 | There is an error in the specification of the option. Or there is a problem in the registered information of the Configuration Management Database (CMDB). | ||
200 | Changing of the event status terminated abnormally. | ||
- | - | 201 | Execution of operation component timed out. |
202 | The operation component was not executed. There is a problem in the setting to execute the operation components. | ||
203 | Failed to execute the operation component. There is a problem in the Management Server environment. | ||
205 | The operation component was not executed. There is a problem with the input information specification of the operation component. | ||
206 | The operation component was not executed normally. There is a problem with the output information specification of the operation component. | ||
207 | The operation component was not executed. There is a possibility that the operation components have not been registered in the Management Server. | ||
208 | The Automated Operation Process has been canceled because the Automated Operation Process was recovered while the operation component was executing. |
Output information
Variable | Description |
|---|---|
message | This variable will be set to the following message if the status of the event monitored by the monitoring product is changed successfully. The operation component was successful. If an attempt to change the status of the event monitored by the monitoring product fails, the content of the error will be set as a string. |
returnCode | This variable is set to the return value. |
Notes
If the information except for the Management Server has been entered for 'hostname', this operation component uses the file transfer infrastructure or SSH communication to perform its operations. Set either at least to be able to communicate. Refer to "3.16 Notes of Each Communication Method" for information on communication methods.
Refer to "3.16.7 Notes When Connected User And Executing User Are Different" for information on different connected and executing users.
To check the return value, use Web console. Refer to "Confirming the Operation Component Execution Status/Execution Results" in the Systemwalker Runbook Automation Operation Guide for details.
When return values between 201 and 208 are output, the Automated Operation Process become an abort or error state,, and the error message is output to the following places.
Event log of the Management Server (When the Management Server is Windows(R))
System log of the Management Server (When the Management Server is Linux)
Custom message of BPMN
Confirm the message in any of the above-mentioned place, and execute appropriate measures. Refer to the Systemwalker Runbook Automation Message Guide for details.
