You can execute the update processing of multiple HiRDB single server configurations as a single transaction by linking OLTP (OpenTP1) to the HiRDB single server configurations. If you partition a database by key ranges, the OLTP system (OpenTP1) running on each server machine can distribute processing to the linked HiRDB single server configurations. This enables transaction processing to be performed at high speed. When integrating multiple HiRDB single server configurations, consider linking your system to an OLTP system. The following figure shows linkage of a HiRDB single server configuration with an OLTP system (OpenTP1).

Figure 7-2 Linking a HiRDB single server configuration with an OLTP system (OpenTP1)

When a HiRDB parallel server configuration is linked with an OLTP system (OpenTP1), transaction processing can be achieved at high performance and high workload. The following figure shows linkage of a HiRDB parallel server configuration with an OLTP system (OpenTP1).

Figure 7-3 Linking a HiRDB parallel server configuration with an OLTP system (OpenTP1)

In this type of linking, multiple OLTPs (OpenTP1) and one HiRDB communicate using the client/server method. Different OLTPs (OpenTP1) can connect to one HiRDB at the same time. To do this, you must set a unique OLTP identifier (client environment definition PDTMID) for each OLTP (OpenTP1). The following figure shows linkage between multiple OLTPs (OpenTP1) and a single HiRDB.

Figure 7-4 Linking between multiple OLTPs (OpenTP1) and a single HiRDB

In this type of linking, one OLTP (OpenTP1) is linked to multiple HiRDBs. SQL statements can be executed by connecting to HiRDBs on different server machines at the same time. In such a case, you need to use the multi-connection facility. The following figure shows linkage between one OLTP (OpenTP1) and multiple HiRDBs.

Figure 7-5 Linking between one OLTP (OpenTP1) and multiple HiRDBs

For details about the multi-connection facility, see the HiRDB Version 9 UAP Development Guide.