B. Glossary

One of the roles specified for resource groups. This role can manage resource groups, service templates, and services. It can also develop service templates and run services.

In JP1/AO, archiving means moving tasks whose processing has been completed from the list of tasks to the list of histories. The detailed information is deleted from archived tasks .

To make a Development service template available for debugging and able to be added as a service in a development environment. A built Development service template is imported to a JP1/AO server.

A user group provided by JP1/AO. The following four built-in user groups are provided: AdminGroup, DevelopGroup, ModifyGroup, and SubmitGroup.

A categorization of services (such as by usage and type). Services are classified based on this information and managed in hierarchies.

A system in which multiple servers are linked together and run as a single system, enabling applications to be run without interruption in the event of a failure. If a failure occurs on the server running applications (the active server), another server that has been on standby (a standby server) inherits the application processing. Inheriting processing in this manner is called failover. In general, this type of system is also called a node switching system because application processing is switched from the active node to the standby node.

A component providing a collection of functions that can be used in all Hitachi Command Suite products. Common Component is installed as a part of JP1/AO and provides such functions as user management, log output, and various commands.

The host at a connection destination that is managed by JP1/AO as a target of a service operation. Accesses from users to connection destinations can be restricted by associating the connection destinations with resource groups.

A series of operations for detecting problems of flows and plug-ins based on the results of a debug task, in order to verify operation of a Development service template.

A function provided by JP1/AO for supporting debugging of Development service templates.

A service that is generated and run when a Development service template is debugged. Unlike ordinary services, debug services need not be added in the Add Service dialog box or run in the Submit Service dialog box.

A task that is generated when a Development service template is debugged. This task is generated whenever a debug service is run. During debugging, problems of flows and plug-ins can be pointed out from the execution results of a debug task.

One of the roles specified for resource groups. This role can manage service templates and services, can develop service templates, and can run services.

A plug-in that is being created by the user, or a plug-in that was created by duplicating an existing plug-in. Development plug-ins are used in a development environment.

A service template that is being created by the user, or a service template that was created by duplicating a Release service template. Development service templates are used in a development environment.

A URL that displays a target dialog box immediately after login. The following three dialog boxes can be displayed: Service Definition dialog box, Submit Service dialog box, and Task Details dialog box.

A function for managing users by linking with JP1/Base's authentication function or Active Directory. Linking with JP1/Base's authentication function allows JP1/AO to use the JP1 user managed by other products. Linking with Active Directory allows the user to log in to JP1/AO by using Active Directory user information and use Active Directory to manage JP1/AO passwords.

A flow of an automated procedure defined in a service template

An archived task whose processing has terminated.

Product for providing centralized management of multiple storage systems, from configuration to monitoring of the storage environment, regardless of the platforms used.

Product that provides the information needed to achieve central management of a network environment, including SAN.

A collection of commands, shell scripts, or Windows executable files.

A collection of jobs that are related by their execution order. When a jobnet is executed, the jobs in the jobnet are executed automatically in the defined execution order.

Product providing a package of multiple service templates. It provides a collection of templates that support a wide variety of types and fields of operations, including virtual server operations and cloud operations.

Product that provides functions needed to automate operation procedures and support run book automation.

Product that provides functions fundamental to JP1/AO. Its functions include transmission of JP1 events and management of JP1 users. JP1/Base is a prerequisite software product for JP1/AO.

Product for achieving integrated network management, such as network configuration management, performance management, and failure management.

Information used by JP1 to manage an event that occurs in the system. The JP1 events are managed by JP1/Base's event service. JP1/Base records the JP1 events that occur in the system in a database.

Product for centrally monitoring distributed systems. It enables the user to monitor the JP1 events that indicate job execution status and failures in distributed systems via the JP1/IM - View window.

Product for monitoring and analyzing issues related to system performance.

In JP1/Base (which is a required software product for JP1/AO), the management targets (resources), such as jobs, jobnets, and events, are classified into various groups. These groups of management targets (resources) are called JP1 resource groups.

A user managed by JP1/Base. Setting up an external authentication linkage with JP1/Base enables the JP1 users to log in to JP1/AO. The JP1 users are also the users of the task-processing engine.

A step that uses a flow plug-in. Using a layering step allows the user to create a layer of flows.

A user who logs in to Active Directory to retrieve user information from an LDAP directory server. An Active Directory user who has permissions to access target user information can be specified as an LDAP search user.

One of the roles specified for resource groups. This role can manage services and run services.

A step that uses normal plug-ins (that is, other than a flow plug-in and repeated execution plug-in). Using a normal step allows the user to perform processing defined in plug-ins.

The minimum unit of processing for automated IT operations. Plug-ins include the JP1/AO standard-package plug-ins and JP1/AO Content Set Plug-ins. Of the JP1/AO standard-package plug-ins, plug-ins for general-purpose processing, such as email notification and repeated flow processing, are called basic Plug-ins.

An image file that can be set as a plug-in icon. Plug-in icons are displayed in a list of plug-ins and in the Flow view.

A definition of a property value based on the user's environment and operation that is specified in service templates. The preset properties enable the user to specify values appropriate to the user's environment and operation when services are added and edited. The preset properties can be specified in imported service templates.

Data used for managing users, including the user IDs and addresses.

A line that connects steps. An execution order of processing can be defined by deploying the steps required for a job and connecting them by using a related line.

To make a tested service template able to be added as a service in the product environment. A Development service template that has been released is called a Release service template, which cannot be edited. A released service template is imported to a JP1/AO server.

A plug-in that was imported to JP1/AO by releasing a Development service template, or a plug-in included in the service templates provided by JP1/AO. Release plug-ins are used in the product environment.

A Development service template that has been released is called a Release service template. The service templates provided by JP1/AO are also release service templates. Release service templates are used in the product environment.

A step that uses a repeated execution plug-in. Using a repeated step allows a specified flow to be executed repeatedly.

A group of services and connection destinations.

A group of clustered services that constitute a unit of service failover.

Role that restricts operations (such as managing and running services) for a given resource group. A role is set for each resource group. The four roles are the Admin role, the Develop role, the Modify role, and the Submit role.

In JP1/AO, an imported service template into which environment-specific property values are entered becomes what is called a service. Operation procedures are automated by running services.

A template that enables various operation procedures for an IT system to be run by simply specifying property values and scheduling information from a JP1/AO window.

A property whose value is shared among the services that run in JP1/AO. For example, if you define the host name, user name, and password for a server at the connection destination as shared service properties, you can skip entering these defined server information items each time you run a service. Shared service properties that are predefined by JP1/AO are called shared built-in service properties.

An element of a flow. One step executes one plug-in.

One of the roles specified for resource groups. This role can run services.

The unit of processing that is generated by running a service. By checking the tasks, you can obtain the progress and results of automatic processing.

A function that displays the progress of a selected task or debug task in flow format.

An internal component of JP1/AO. It executes the flows contained in service templates.

A group of users who use the same resource group and have the same permissions for that resource group.

Permission needed to manipulate all user accounts. A user with the User Management permission can use the functions for managing users and user groups.