Scalable Database Server, HiRDB Version 8 Description

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

2.4.4 System configuration

This section uses OpenTP1 as an example for explaining the configuration of a system that uses OLTP.

Organization of this subsection
(1) Linkage to HiRDB/Single Server
(2) Linkage to HiRDB/Parallel Server
(3) Linkage to multiple OpenTP1

(1) Linkage to HiRDB/Single Server

By linking HiRDB/Single Servers to OpenTP1, processing at multiple HiRDB/Single Servers can be executed centrally. In such a case, the database is partitioned and allocated using a method such as key range partitioning, and OpenTP1 running on each server machine allocates processing to each HiRDB/Single Server. In this way, large-scale transaction processing can be implemented. Linkage with OpenTP1 is the recommended means of integrating multiple HiRDB/Single Servers. Figure 2-8 shows the linkage between HiRDB/Single Servers and OpenTP1.

Figure 2-8 Linkage between HiRDB/Single Servers and OpenTp1

[Figure]

Explanation
Each of the three server machines is provided with a HiRDB/Single Server and OpenTP1; transaction processing is allocated to each of the three HiRDB/Single Servers.

(2) Linkage to HiRDB/Parallel Server

By linking a HiRDB/Parallel Server to OpenTP1, high-performance, high-load transaction processing can be achieved. Figure 2-9 shows the linkage between a HiRDB/Parallel Server and OpenTP1.

Figure 2-9 Linkage between HiRDB/Parallel Server and OpenTP1

[Figure]

Explanation
OpenTP1 is provided at the server machine where the system manager and front-end server are installed in order to control transaction processing.

(3) Linkage to multiple OpenTP1

Figure 2-10 shows linkage to multiple OpenTP1.

Figure 2-10 Linkage to multiple OpenTP1

[Figure]

Note
The OLTP identifier (PDTMID in the client environment definition) of each OpenTP1 must be unique.