![[Contents]](FIGURE/CONTENT.GIF)
Scalable Database Server, HiRDB Version 8 UAP Development Guide
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
HiRDB operates in a client/server network environment. The unit used to send a request for executing a UAP is called the client, and the unit used to receive a request is called the server. The system used as the server is the HiRDB server.
A client can operate in any combination of these eight modes:
2 Like ODBC, OLE DB is an API for accessing a wide range of data sources. Unlike ODBC, OLE DB also defines interfaces for accessing non-SQL data. For details about how to access HiRDB from an OLE DB-compatible UAP, see 14. HiRDB Access from OLE DB Application Programs.
Figures 1-4 to 1-11 show the client operation modes.
Use the same platform for the HiRDB/Developer's Kit used to create the UAP and the HiRDB/Developer's Kit used to execute the UAP.
Figure 1-4 Operating mode using a machine other than the server machine as a client
![[Figure]](FIGURE/ZU010401.GIF)
Figure 1-5 Operating mode using the same server machine as the HiRDB server as the client
![[Figure]](FIGURE/ZU010402.GIF)
Figure 1-6 Operating mode using a UAP under OLTP as a client
![[Figure]](FIGURE/ZU010403.GIF)
Figure 1-7 Operating mode using an ODBC-compatible UAP as a client
![[Figure]](FIGURE/ZU010404.GIF)
Figure 1-8 Operating mode using an OLE DB-compatible UAP as a client
![[Figure]](FIGURE/ZU010405.GIF)
Figure 1-9 Operating mode using an ADO.NET-compatible UAP as a client
![[Figure]](FIGURE/ZU010408.GIF)
Figure 1-10 Operating mode using a Java (JDBC-compatible) application program as a client
![[Figure]](FIGURE/ZU010407.GIF)
Figure 1-11 Operating mode using a VOS3 system or Linux for AP8000 UAP as a client
![[Figure]](FIGURE/ZU010406.GIF)
All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.