Preface
- Organization of this preface
■ What you can do with Client Process Automation
Among the many business operations carried out by computers, some are performed regularly such as daily backups or month-end closing, while some are performed irregularly by events such as receiving orders.
Moreover, computer systems can be even more complicated with cloud services or data centers, where services and data are stored in virtual locations, as well as when different computers relate to one another to perform a set of operations. This, as a result, can impose a burden on services and system users who access the data.
Client Process Automation (simply called CPA hereafter) is designed to automate periodic or routine processing to help system users do their system operations in a more automated and simplified way.
■ What is explained in this manual
This manual explains the basic methods of configuring and operating CPA. The purpose of this manual is to help readers briefly understand the basic usage of CPA.
This manual is intended for the following users:
-
Users who will be evaluating the installation of CPA
-
Users who want to understand the concepts of CPA and to obtain in a short time an overview from configuration to operation
■ Organization of this manual
This manual is organized as follows:
- 1. Installation
-
This chapter describes how to install CPA.
- 2. Automating Applications by Using CPA
-
This chapter describes the basic methods of operating CPA.
- A. Version Revisions
-
This appendix explains the version revisions.
- B Reference Manual for This Manual
-
This appendix provides reference material for this manual, including a list of related manuals and a description of the conventions used by the writer.
■ Conventions: Fonts and symbols
The following table explains the text formatting conventions used in this manual:
Text formatting |
Convention |
---|---|
Bold |
Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:
|
Italic |
Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:
Italic characters are also used for emphasis. For example:
|
Monospace |
Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:
|
The following table explains the symbols used in this manual:
Symbol |
Convention |
---|---|
| |
In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example: A|B|C means A, or B, or C. |
{ } |
In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example: {A|B|C} means only one of A, or B, or C. |
[ ] |
In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example: [A] means that you can specify A or nothing. [B|C] means that you can specify B, or C, or nothing. |
... |
In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted. In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example: A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary. |
■ Conventions: 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.