Design the following items to match the operation.
Determine the system configuration
Consider what kind of system configuration to use, by taking into account the environment where Systemwalker Runbook Automation will be installed. Refer to "System Configuration" in the Systemwalker Runbook Automation Technical Guide for information on system configurations.
Perform the following installation tasks for each server and computer in the system configuration.
Install and set up the Manager for Management Server.
Install Systemwalker Runbook Automation Studio and a Web browser.
Install and set up the Agent for Linked Server/Relay Server.
To use file transfer infrastructure as the method of communication between the Management Server and Business Server in the following functions, install "Agent for Business Server".
Operation component (when the Business Server is specified as the operation target server)
Collection of configuration information
If the Agent is not installed, communication will be executed using SSH (it must be installed and setup prior to use).
Install a Web browser.
If it is in a cluster configuration or it uses VM environment, refer to the "Required Software" in the Systemwalker Runbook Automation Technical Guide and consider to which cluster software or VM software is used.
If the installation tasks for the cluster configuration, refer to the Systemwalker Runbook Automation Cluster Setup Guide. If the installation tasks for using VM environment, refer to the VM software manual.
Design the port numbers
The list of port numbers used in Systemwalker Runbook Automation is mentioned in "9.1 Port Numbers".
Consider the environment that Systemwalker Runbook Automation will be installed in when designing which port numbers will be used.
Estimate disk space requirements
Refer to "Disk Capacity" in the Systemwalker Runbook Automation Technical Guide for information on how to estimate the required disk capacity and reserve file systems of a sufficient size.
Consider which communication method to use
Determine which communication method to use based on the methods supported by the operation components to be used.
It is a communication method that can be used to install Systemwalker Runbook Automation agent. You do not need to setup it.
SSH is an abbreviation for Secure Shell. Almost all operation components support SSH. If the Systemwalker Runbook Automation Agent has not been installed on the operation target server or file transfer infrastructure has stopped, then communication will be executed using SSH. If the operation target server is running Windows, then it will be necessary to install and set up SSH.
This is the Windows system communication method, and is supported through the operation component "Execute arbitrary command". It can be used by specifying Windows PowerShell as the method of communication with the operation target server. Windows PowerShell 2.0 must be installed and set up in the Management Server and operation target server.
Telnet is supported through the operation components "Execute arbitrary command" and "Execute multiple commands". It can be used by specifying Telnet as the method of communication with the operation target server. Telnet must be installed and set up in the operation target server.
These are short for Remote Shell and Remote Process Execution, respectively. Both are supported through the operation component "Execute arbitrary command". They can be used by specifying RSH and REXEC as the methods of communication with the operation target server. RSH and REXEC must be installed and set up in the operation target server.
This is short for File Transfer Protocol, and is supported through the operation component Transfer files It can be used by specifying FTP as the method of communication with the operation target server. FTP must be installed and set up in the operation target server.
Consider what configuration information to collect
In Systemwalker Runbook Automation, the management target ICT device (Business Server or network device) is used by collecting IT resource information. The type of IT resource information to be collected depends on the operation component used.
Additionally, it will be necessary to configure the environment settings in the management target ICT device according to the IT resource information type that will be collected.
The IT resource information types are listed below:
Node information (IP address, host name, LAN information, name of operating system)
Logical server information (operating system details, logical CPU, logical memory, logical disk, registry)
Installed software information (product name, package information, version)
Hardware information (product name, type name, serial number, physical CPU, physical memory, physical disk)
The relationships between the types and settings for the IT resource information to be collected are shown below.
[1] Collecting only node information (without OS name and Lan information)
[2] Collecting only node information (with OS name and Lan information)
[3] Collecting IT resource information (without Hardware information)
[4] Collecting IT resource information (with Hardware information)
Information to be collected | SNMP Agent settings | Installation of Systemwalker Runbook Automation agent or setting of SSH (*2) | Installation of linked products (*3) | ||||||
|---|---|---|---|---|---|---|---|---|---|
Node information | Logical server information | Information about installed software | Hardware information | ||||||
IP address | Host name | OS name LAN information | |||||||
[1] | Y | Y (*1) | N | N | N | N | Not required | Not required | Not required |
[2] | Y | Y (*1) | Y | N | N | N | Required | Not required | Not required |
[3] | Y | Y | Y | Y | Y | N | Required | Required | Not required |
[4] | Y | Y | Y | Y | Y | Y | Required | Required | Required |
Y: Collected, N: Not collected
*1: The host name must be registered in the hosts file or DNS of the server that will execute the collection of the configuration information.
*2: To use SSH, the authentication information (user ID and password) for connecting via SSH must be registered on the Management Server.
*3: The hardware information is collected by the linked server management products installed on the Business Server. For this reason, it will be necessary to install these linked products on the Business Server.
Consider the authentication method to use
Design an authentication method that is required to operate Systemwalker Runbook Automation.
Systemwalker Runbook Automation provides the following authentication methods:
Authentication via Single Sign-On
Authentication via LDAP
This method uses a user that has been registered with a repository in a Single Sign-On environment as the login user for Systemwalker Runbook Automation, and has the following advantages:
The same user information can be shared by all products that support the Single Sign-On environment. User information can be managed centrally in the repository in the Single Sign-On environment.
The information that was used to log in to the Systemwalker Runbook Automation Management Server can be used to seamlessly start software products that use Single Sign-On, without a new login window being displayed.
Systemwalker Runbook Automation can use the following Single Sign-On functions:
Interstage Single Sign-On
Use the Interstage Directory Service to create the repository for the Interstage Single Sign-On environment. If the Interstage Directory Service has already been installed, the existing Interstage Directory Service can be used.
ServerView Operations Manager Single Sign-On
If there is a ServerView Operations Manager Single Sign-On environment that has already been created, the same authentication infrastructure can be used with Systemwalker Runbook Automation as well. For the repository for the ServerView Operations Manager Single Sign-On environment, use the OpenDS or Active Directory provided by ServerView Operations Manager.
You can create an environment for authenticating via LDAP.
Note that an LDAP directory already created for user authentication can be used. By making the user the same as the user that operates Systemwalker Runbook Automation, user information can be managed centrally, making user maintenance easier.
Systemwalker Runbook Automation can use the following types of LDAP directory:
Active Directory
Interstage Directory Service
OpenLDAP
Active Directory, the Interstage Directory Service and OpenLDAP can be used to create the LDAP authentication repository. If Active Directory, the Interstage Directory Service, or OpenLDAP has already been installed, these can be used for the LDAP authentication repository.
Add the required users
In order to install Systemwalker Runbook Automation, the following users must be added to the LDAP directory beforehand.
The users required for installation
Refer to "3.1.6 Registering Users, Groups and Organizational Units" for information on adding the users required for installation.
The users that will use Systemwalker Runbook Automation during operations
Refer to "Registering user in Directory Service" and "Registering Local Group and Adding User" in the Systemwalker Runbook Automation Operation Guide for information on how to register users with Systemwalker Runbook Automation.
Refer to "3.1.6 Registering Users, Groups and Organizational Units" for information on how to register users to use authentication via the Interstage Single Sign-On function.
