Description
This operation component registers a new configuration item for a logical node in the Configuration Management Database (CMDB). This component is used to register machine information in the CMDB after a machine environment has been created.
Options
Basic Options
The IP address of the server to be registered as the Configuration Management Database (CMDB).
An argument error occurs if the IP address is omitted.
The maximum length of the IP address is 1,024 characters. An argument error occurs if this is exceeded.
If an already registered node is specified, the existing content is overwritten by the new content.
The operating system type for the server to be registered as the Configuration Management Database (CMDB).
Specify Windows, Linux or Solaris. This option is not case sensitive.
An argument error occurs if the operating system type is omitted.
The maximum length of the OS type is 1,024 characters. An argument error occurs if this is exceeded.
Advanced Options
This is the completion timeout (seconds) for the execution of operation components.
Values between 300 and 86400 (1 day) can be specified.
Example) If the completion timeout is 10 minutes: 600
If the operation component has not finished executing even though the specified time has passed, the processing for the operation component will be interrupted with return value 201.
This is the retry count for the execution of operation components.
Specify the number of retry attempts to be used when operation components terminate with return value 161. Values between 0 and 5 can be specified.
If an operation component terminates with a return value other than "161" as a result of being re-executed from a retry, execution of the operation component will terminate even if the specified number of retries has not been reached. The return value for the operation component will be the value from the last time the operation component was executed.
Example) To retry the operation component twice: 2
This is the retry interval (seconds) for operation components.
Specify the time to wait before a retry is attempted if operation components terminate with return value 161. Values between 1 and 14400 can be specified.
Example) To retry at 300 second intervals: 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 | The logical node has been registered successfully. |
| Failure | 161 | An attempt to register the logical node failed. If a retry count has been specified, retries will be attempted. |
197 | There is an error with the content of an option. | ||
200 | Registering the logical node has terminated abnormally. | ||
- | - | 201 | Execution of the operation component timed out. |
202 | The operation component has not been executed. | ||
203 | Failed to execute the operation component. There is a problem with the Management Server environment. | ||
205 | The operation component has not been executed. There is a problem with the input information specification of the operation component. | ||
206 | The operation component has not been executed normally. There is a problem with the output information specification of the operation component. | ||
207 | The operation component has not been executed. The operation component may not have been registered on 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 logical node is registered successfully. The operation component was successful. If registering the logical node fails, the content of the error will be output as a string. |
returnCode | This variable is set to the return value. |
Notes
To use this operation component, install an RBA Agent on the server where the logical node is to be registered.
For this operation component, an RBA Agent must be set up in advance. Refer to "IT Resource Information Collection Program Settings" in the Systemwalker Runbook Automation Installation Guide for details.
For this operation component, settings for collecting IT resource information must be specified for the Management Server in advance. Refer to Setup procedure(When using the "Register logical node" operation component) in the Systemwalker Runbook Automation Installation Guide for details.
Register this operation component with the CMDB bundled with the RBA Manager.
In case of a high load on the server, this operation component may take a long time to register configuration items, in which case, the return value is an error value (161).
Use the Web console to check the return value. Refer to "Confirming the Operation Component Execution Status/Execution Results" in the Systemwalker Runbook Automation Operation Guide for details.
If a return value between 201 and 208 has been output, the Automated Operation Process will enter an aborted state or an error state, and error messages will be output to the following locations:
Event logs for the Management Server (if the Management Server is running on Windows(R))
syslogs for the Management Server (if the Management Server is running on Linux)
Custom messages for BPMN
Check for messages in these locations and take the appropriate action. Refer to the Systemwalker Runbook Automation Message Guide for details.
