Each operating unit of an Automated Operation Process. This is an action for which an agent (a name starting with "@") has not been defined for the role. This term refers to processing boxes that require human intervention.
A Systemwalker Runbook Automation application that is installed and resides on the managed Business Server, Linked Server or Relay Server and performs processing by operation instructions from the Management Server. There are two types of Agents: Agents for Business Servers and Agents for Linked Servers and Relay Servers.
A folder that Studio uses to manage items such as Automated Operation Processes and forms.
Process definitions for procedures of system operation tasks. With Systemwalker Runbook Automation Studio, Automated Operation Processes can be created easily using the Process Definition Editor.
Automated Operation Process Group
A unit of management for Automated Operation Processes on a Management Server.
The first day of the fiscal month. With Schedule Definitions, schedules can be defined based on rules such as "the beginning of the fiscal month is the first business day of the month".
A day when an Automated Operation Process is subject to starting. All days other than days defined as holidays by a holiday calendar are business days.
An institution that manages the issuance of certificates. Certificates are required to perform encryption of communication data and emails and to serve as digital signatures for Internet communications and electronic email services. Once they have been issued, the Certificate Authority also manages the certificates. The Certificate Authority adds its own electronic signature to the issued certificate, and verifies that the certificate was issued by the Certificate Authority.
The configuration information required to manage the operation of an IT system. This is the unit for configuration components managed in the CMDB.
Configuration Management Database (CMDB)
A configuration management database defined by ITIL(R). This database handles configuration information, operations process information, and other information that is relevant to managing IT system operations.
Refers to the boundary between one day's operations and the next day's operations. The day change time is the starting time for each day when Automated Operation Processes are displayed with the Process Status Chart.
A computer where developers use Systemwalker Runbook Automation Studio to develop Automated Operation Processes and operation components.
Directory Information Tree (DIT)
A data structure used in LDAP (Lightweight Directory Access Protocol) based directory services.
A service that systematically organizes (in a tree) and manages the names and associated attributes of various physical/logical resources distributed inside and outside an organization. The resources are organized and managed according to the organizational structure, geographical classifications, etc. The directory service also updates and references these names and attributes.
An entry that represents an object and whatever was defined as the RDN column of its parent entry. Each name must be unique within the Directory Information Tree (DIT).
Example:
cn=user001
o=fujitsu
dc=com
The last day of the fiscal month. This is the day before the beginning of the (next) fiscal month.
Refers to the execution times for Automated Operation Processes that are specified by Schedule Definitions.
This time is used to determine the expected finishing time for an Automated Operation Process when using the Process Status Chart to display the execution schedule for an Automated Operation Process.
The process in which the standby node inherits operations from the active node when an error occurs in a cluster system.
A protocol for communications between computers. It is available when a Systemwalker Runbook Automation Agent has been installed.
Personnel who support all the possible paths (including escalation) that may follow from accepting through resolving requests/complaints of customers, including issues in systems and operators inside organization.
A calendar that defines holidays - the days when an Automated Operation Process needs to be suppressed from starting.
If the startup day for an Automated Operation Process that is specified by a Schedule Definition coincides with a holiday, holiday calendars can be used to select whether to cancel the startup of the Automated Operation Process or shift it to the day before or after the holiday.
Computer configuration information, such as the IP address, host name, operating system, hardware information (such as CPU, memory, and disk drives), software information, and patch information.
LDAP (Lightweight Directory Access Protocol) is an Internet-standard, directory access protocol operating on TCP/IP. By using this protocol, it is possible to search and refer to a directory service directly from an LDAP client such as a web browser.
A server where a product linked to Systemwalker Runbook Automation (such as a Systemwalker Centric Manager Operation Management Server) is running.
A virtual IP address that is shared by the active node and the standby node in a cluster system.
Data and files that are used to investigate problems in Systemwalker Runbook Automation, which contain settings information, operating system information, and various logs (such as error, trace, and access logs).
A server that is operated from the Management Server. This is a generic term that includes Business Servers, Linked Servers and Relay Servers.
A server where Systemwalker Runbook Automation Manager can run and where Automated Operation Processes are executed.
In Systemwalker Runbook Automation, this term is used in the following two senses:
A generic term of the process box for process definitions created by Systemwalker Runbook Automation Studio. There are the following types of node:
Start Node, Exit Node and Activity Node
Individual devices that make up the computer network. Similar to node information such as active node, standby node, and IT resources, it is mainly used in reference to the servers.
IT resource information related to nodes, such as IP addresses, host names, operating system names and LAN information.
This term is the opposite of a cluster environment, that is, an environment where a cluster system has not been installed.
Information indicating the actual status of system in an operational environment, which is stored in CMDB.
A person who manages the entire data center. He or she issues instructions to operators to use Automated Operation Processes, and checks the results of the work done.
A Ruby or Perl script written to automatically execute operations for Business Servers and linked products, which have been previously performed manually. Operation components absorb differences between platforms, and are designed to make them easy to use even without detailed knowledge about system management tools and operating system. Also, it is possible to call existing applications to perform associated operations.
The operation period for a Schedule Definition. During the period specified by the operation period, Automated Operation Processes will be started according to the startup days and startup times specified by the Schedule Definition.
A schedule displayed in calendar format to indicate the startup days for an Automated Operation Process that have been specified in the Schedule Definition.
Operation schedules show one month's worth of startup days separated into single day units.
It is possible to look up operation schedules for up to three years.
A person who uses Automated Operation Processes according to instructions issued by administrators.
An IP address that is specific to each node. In cluster systems, physical IP addresses are contrasted with logical IP addresses.
A node that is the active node when the cluster service starts. After that, the primary node switches between the standby node and the active node every time a failover occurs.
A specification that expresses business processes and supports operation automation. Process definitions define the properties and behavior of the process instances generated, including the flow of control within the process.
Entities generated when process definitions are executed. The structure of a process instance is the same as the structure of the process definition on which it is based.
The status in which Automated Operation Processes run in production mode. Published Automated Operation Processes cannot be changed (draft Automated Operation Processes can be changed).
Relative Distinguished Name (RDN)
A name used to distinguish an entry that is directly under a parent entry. Each RDN must be unique within that sibling relationship.
Example: o=fujitsu
A server that is used to relay the collected configuration information. It is necessary to deploy Relay Servers when there are more than 300 Business Servers being managed.
The overall flow of release tasks such as planning, approval, testing, deployment, and confirmation.
The release automation template is a process definition that deploys release packages to the release targeted servers.
The following three types of release package are provided:
Template for release of Interstage Application Server Java EE Application
Template for release of Interstage Application Server J2EE Application
Template for release of other Applications
A jar format or zip format file for each of the release targeted servers. The file contains applications and definition files to be deployed respectively to each server.
release package storage server
The server where the release package is archived. Refers to Interstage Application Development Cycle Manager and ftp Servers etc.
The term 'Release package storage server' presumes a separate independent server configuration from the Management Server.
Tasks such as planning, approval, testing, deployment, and confirmation etc., related to individual releases.
A definition for automatically starting an Automated Operation Process on a prescheduled day and time.
A pattern that registers startup days for an Automated Operation Process. When specifying startup days in Schedule Definitions, Schedule Definitions can be easily set up by simply selecting a Schedule Pattern that has been registered in advance.
A node that is the standby node when the cluster service starts. After that, the secondary node switches between the active node and the standby node every time a failover occurs.
An item where the user selects from values already provided using a checkbox, radio button, list box, or combo box.
The maximum number of days that the startup of an Automated Operation Process can be shifted. If the startup day for an Automated Operation Process coincides with a holiday, the Schedule Definition enables the startup day for the Automated Operation Process to be shifted to the day before or after the holiday. If the day to which the startup of the Automated Operation Process has been shifted is also a holiday, the Automated Operation Process will be shifted further, but the number of days that the Automated Operation Process can be shifted is limited by the shift limit. If the shift limit is exceeded, the Automated Operation Process will no longer be started.
When specifying the startup days for an Automated Operation Process by specifying a Schedule Pattern or a rule such as "every week" or "every month" in a Schedule Definition, the behavior of the Automated Operation Process may need to be changed for specific days. Those days are referred to as "specific days".
For example, particular days can be defined so that the startup of an Automated Operation Process is suppressed on a particular day even though it was due to start on that day, or conversely so that an Automated Operation Process starts on a particular day even though it was not due to start on that day.
Abbreviation for Secure Shell, a protocol for communications between computers, which is supported by most operation components for Systemwalker Runbook Automation.
The day when an Automated Operation Process starts.
The startup days for Automated Operation Processes are specified by Schedule Definitions or Schedule Patterns.
The time when an Automated Operation Process starts. The startup times for Automated Operation Processes are specified by Schedule Definitions.
Abbreviation for Systemwalker Runbook Automation Studio, a development tool used to create Automated Operation Processes. It can be used to create the following elements of Automated Operation Processes:
Process definitions
Forms
Operation components
A person who changes operational settings for Systemwalker Runbook Automation, performs maintenance and manages accounts for administrators.
A person who uses Systemwalker Runbook Automation from a Web Console connected to a Management Server. This term includes administrators and operators.
The status in which the processing within a process instance has moved to an Activity node and an operation has been allocated to a person.
Customizable models for Automated Operation Processes, provided with Systemwalker Runbook Automation as standard or as needed.
User-defined attributes used by Systemwalker Runbook Automation Studio. These are global variables defined within process definitions, and their values are maintained throughout process execution. UDAs contain data that process participants need to access, change or add.
