Preface
The following provides an overview of JP1/AO and this manual.
- Organization of this preface
■ What you can do with JP1/AO
System operations require many operation procedures. The number and complexity of the procedures results in large workloads on the personnel involved. To improve this situation, measures need to be taken to reduce the tasks that depend on human resources and to improve operational efficiency. By deploying JP1/AO to automate operations of consolidated systems, you can improve operational efficiency and reduce the workload of administrators.
The following figure shows the basic concept of JP1/AO. To automate typical IT operation procedures performed in data centers and office systems, JP1/AO uses "service templates".
■ What is explained in this manual
This manual provides an overview of JP1/AO products, and describes the basic usage. The goal of this manual is to enable users to use the products to automate IT operation procedures.
The basic system configuration consists of an IT operation automation server, a Web browser for operating JP1/AO, and target devices (connection destinations) to which JP1/AO is to be connected. If you want to develop service templates, we recommend that you prepare a development server separately.
For details about how to use JP1/AO by using a different system configuration such as a cluster configuration or a configuration where JP1/AO is linked to other products, see the topic "System design" in the JP1/AO Overview and System Design Guide.
■ How to read this manual
This section describes the organization of JP1/AO manuals, and how to refer to the manuals according to your purpose.
Refer to this manual according to what you want to do, as follows.
- Users who want to use the service templates provided by JP1/AO without change:
- Users who want to customize the service templates according to the tasks to be automated:
For JP1/AO, eight manuals are available including this manual. This manual describes the basic usage of JP1/AO. In addition to basic functions, JP1/AO provides various functions to enable customers to perform operations that suit their environments. To learn more about the advanced functions and operations, refer to the appropriate manual as shown below.
Purpose |
Manual to be referenced |
---|---|
Overview of JP1/AO products and basic usage |
IT Operations Automation: Getting Started |
Overview of JP1/AO |
JP1/AO Overview and System Design Guide |
JP1/AO functions |
|
Checking what needs to be evaluated during the design process, and designing the system |
|
Setting up a JP1/AO system |
JP1/AO Configuration Guide |
Linkage between JP1/AO and other products |
|
Setting up a cluster system |
|
Performing an overwrite installation of JP1/AO |
|
Performing an upgrade installation of JP1/AO |
|
Uninstalling JP1/AO |
|
Migrating the environment in JP1/AO |
|
Using JP1/AO |
JP1/AO Administration Guide |
Maintaining the system |
|
Understanding the limitations of JP1/AO |
|
Using the commands |
JP1/AO Command and API Reference |
Using the API |
|
Service templates and plug-ins provided by JP1/AO |
JP1/AO Service Template Reference |
Developing the service templates and plug-ins |
JP1/AO Service Template Developer's Guide |
When problems occur |
JP1/AO Configuration Guide |
JP1/AO Administration Guide |
|
Checking the content of messages if problems occur, and action to be taken |
JP1/AO Messages |
A reference to another manual is written as follows: For details about something, see topic-title in the manual-name. Using topic-title as a keyword, search for the relevant section in the target manual.
Operations in each window assume the following environment:
- Server on which to install JP1/AO
Environment that uses Windows Server 2022
■ Diagrams of windows in the manual
Some windows in this manual might differ from the windows of your product due to improvements, browser differences, etc without prior notice. Please keep this in mind before reading this manual.
■ Version numbers
The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen.
For example:
-
Version 1.00 (or 1.0) is written as 01-00.
-
Version 2.05 is written as 02-05.
-
Version 2.50 (or 2.5) is written as 02-50.
-
Version 12.25 is written as 12-25.
The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.