This section explains how a server managed by Systemwalker Runbook Automation can be configured as a managed server managed by Systemwalker Software Configuration Manager in environments in which both the Systemwalker Runbook Automation admin server and the Systemwalker Software Configuration Manager admin server exist together.
Registering a server
A server managed by Systemwalker Runbook Automation can be registered as a managed server of this product by using the Server Information Management command (refer to "swcfmg_server (Server Information Management Command)" in the Reference Guide for details).
Note
This product manages information about managed servers by storing it in the CMDB as configuration items of LogicalServer.
Therefore, to configure a server managed by Systemwalker Runbook Automation as a managed server managed by this product, update the attributes below for the LogicalServer configuration items corresponding to the server to be registered. Update these items with the values specified when registering the server using the Server Information Management command.
Refer to "Configuration Item Format" in the Systemwalker Runbook Automation Reference Guide for information on the format of configuration items.
Element Name | Parent Element | Element Description | Component Name | Component Type | Component Description | Value |
|---|---|---|---|---|---|---|
LogicalServer | Server node information | nickname | Attribute | Used as a nickname or partition display name | The following string will be stored: Server name + "(" + host name + ")" | |
hostname | Attribute | Host name | Host name | |||
name | Attribute | Official name | Internal information (server ID) | |||
SystemSettings | Element | System settings | - | |||
SystemSettings | LogicalServer | System settings | OSSetting | Element | OS information | - |
OSSetting | SystemSettings | OS information | platform | Attribute | OS type | OS type |
Updating a server
Use the Server Information Management command to update server information (refer to "swcfmg_server (Server Information Management Command)" in the Reference Guide for details).
Note
The items below (LogicalServer configuration items corresponding to the server to be updated) are updated with the values you specified when updating the server using the Server Information Management command.
Refer to "Configuration Item Format" in the Systemwalker Runbook Automation Reference Guide for information on the format of configuration items.
Element Name | Parent Element | Element Description | Component Name | Component Type | Component Description | Value |
|---|---|---|---|---|---|---|
LogicalServer | Server node information | nickname | Attribute | Used as a nickname or partition display name | The following string will be stored: Server name + "(" + host name + ")" | |
hostname | Attribute | Host name | Host name |
Notes on updating server information using Systemwalker Runbook Automation
Notes on updating server information using Systemwalker Runbook Automation are shown below.
Note
Do not change the values of the following LogicalServer configuration items using Systemwalker Runbook Automation, because they are used by this product.
Element Name | Parent Element | Element Description | Component Name | Component Type | Component Description | Value |
|---|---|---|---|---|---|---|
LogicalServer | Server node information | ipAddress | Attribute | IP address | IP address | |
SystemSettings | Element | System settings | - | |||
SystemSettings | LogicalServer | System settings | OSSetting | Element | OS information | - |
OSSetting | SystemSettings | OS information | platform | Attribute | OS type | OS type |
Deleting a server
To configure a server to no longer be managed by this product, delete it using the Server Information Management command (refer to "swcfmg_server (Server Information Management Command)" in the Reference Guide for details).
Information
Deleting the following server using the Server Information Management command does not delete its LogicalServer configuration items:
During server registration, server information had already been stored as LogicalServer configuration items in the CMDB using Systemwalker Runbook Automation
