HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide

[Contents][Glossary][Index][Back][Next]

5.1.1 Organization of the Datareplicator definitions

Datareplicator definition involves creating separate definition files for source and target Datareplicators. You must create both types of definitions before you can start a data linkage system. In addition, you must specify use of Datareplicator for data linkage in the system definition for the source HiRDB.

The following figure shows the organization of the Datareplicator definitions.

Figure 5-1 Organization of the Datareplicator definitions

[Figure]

For details about how to create Datareplicator definition files, see 4.6.2 Preparation of the files used with the source Datareplicator and 4.7.2 Preparation of the files used with the target Datareplicator.

Sample definition files
Datareplicator provides templates for the definition files (sample definition files). If you copy the templates into the directory for definition files (HDSPATH) or into some other appropriate directory, and then modify a template's contents, you will not have to create the definition file from scratch. For details about Datareplicator's sample definition files, see 5.13.2 Examples of source Datareplicator definitions and 5.13.3 Examples of target Datareplicator definitions.

Table 5-1 lists the source Datareplicator definitions, and Table 5-2 lists the target Datareplicator definitions.

Table 5-1 Source Datareplicator definitions

Name of source Datareplicator definition Definition filename Required/optional Description
Extraction system definition $HDEPATH/hdeenv Required Defines information about the source Datareplicator's operating environment. The defined information includes the source and target Datareplicator identifiers.
Extraction environment definition Any name Required Defines information about the extraction processing environment. The defined information includes the names and size of the extraction information queue files.
Transmission environment definition Any name Required Defines information about a transmission processing environment. The defined information includes the service and host names for communications.
Extraction definition Any name Required Defines information about extraction and transmission processing. The defined information includes the correspondence between a table subject to extraction processing and its update information and the target identifiers for the update information.
Source HiRDB definition The following HiRDB definition files:
  • System common definition file
  • Unit control information definition file
 Required Defines information needed to use the source Datareplicator at the source HiRDB. The defined information includes the data linkage start method and the name of the directory used by the source Datareplicator.
Duplexing definition File name specified in the file_dupenv operand in the extraction system definition file Optional Defines information needed to duplex the definition files that are used at the source system. The files that can be duplexed include the extraction master status file, extraction server status file, extraction information queue file, and data linkage file.

Table 5-2 Target Datareplicator definitions

Name of target Datareplicator definition Definition filename Required/optional Description
Import system definition $HDSPATH/hdsenv Required Defines information about the target Datareplicator's operating environment. The defined information includes the communications protocol, source system's data linkage identifier, and so on.
Import environment definition Any name Required Defines information about an import processing environment. The defined information includes the import information queue filenames, import status filename, and import method.
Import definition Any name Optional Defines information about import processing. The defined information includes the correspondence between update information and the table subject to import processing, the target front-end server, key range partitioning conditions, hash partitioning conditions, and UOC routine names.
Update information definition Any name Optional Defines update information when the source database is PDM2 E2 and SAM files are used for data linkage.
Duplexing definition File name specified in the file_dupenv operand in the import system definition file Optional Defines information needed to duplex the definition files that are used at the target system. The files that can be duplexed include the extraction master status file, extraction server status file, extraction information queue file, and data linkage file.
Organization of this subsection
(1) Relationship between the source Datareplicator definitions and the data linkage system
(2) Relationship between the target Datareplicator definitions and the data linkage system

(1) Relationship between the source Datareplicator definitions and the data linkage system

The following figure shows the relationship between the source Datareplicator definitions and the data linkage system.

Figure 5-2 Relationship between the source Datareplicator definitions and the data linkage system

[Figure]

#1
If the source HiRDB is a parallel server and different information is needed in the environment variables for each server machine, you can specify the operands for the environment variables individually for each server machine.

#2
You can specify information common to all back-end servers for the source HiRDB or you can specify information only for specific back-end servers as needed.

#3
The duplexing definition is required to use the file duplexing feature.

(2) Relationship between the target Datareplicator definitions and the data linkage system

The following figure shows the relationship between the target Datareplicator definitions and the data linkage system.

Figure 5-3 Relationship between the target Datareplicator definitions and the data linkage system

[Figure]

#1
The duplexing definition is required to use the file duplexing feature.

#2
You can omit the import definition if the source and target tables have exactly the same table format, table name, and column names.

#3
The update information definition is required for PDMII E2 when the source system uses SAM files.

[Contents][Back][Next]

[Trademarks]

All rights reserved. Copyright (C) 2007, 2013, Hitachi, Ltd.