Preface
This manual explains how to design, set up, and operate Hitachi Elastic Application Data Store, and how to develop Hitachi Elastic Application Data Store application programs.
- Organization of this preface
■ Intended readers
This manual is intended for readers who design, set up, or operate a system in which Hitachi Elastic Application Data Store is deployed, and for developers of Hitachi Elastic Application Data Store application programs.
Readers of this manual must have:
-
A basic knowledge of in-memory data grids
-
Knowledge of Linux
-
A basic knowledge of program development using the Java or C programming language (application program developers)
■ Conventions: Abbreviations for product names
This manual uses the following abbreviations for product names and Java-related terms:
Abbreviation |
Full name or meaning |
||
---|---|---|---|
EADS |
EADS server |
Hitachi Elastic Application Data Store |
|
EADS client |
EADS client (Java) |
Hitachi Elastic Application Data Store Client for Java |
|
EADS client (C) |
Hitachi Elastic Application Data Store Client for C |
||
JavaVM |
Java Virtual Machine |
||
JDK |
Java Developer's Kit |
■ Conventions: Acronyms
This manual also uses the following acronyms:
Acronym |
Full name or meaning |
---|---|
API |
Application Programming Interface |
KVS |
Key-Value store |
■ 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: KB, MB, GB, and TB
This manual uses the following conventions:
-
1 KB (kilobyte) is 1,024 bytes.
-
1 MB (megabyte) is 1,0242 bytes.
-
1 GB (gigabyte) is 1,0243 bytes.
-
1 TB (terabyte) is 1,0244 bytes.
■ 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.