This is the basic mode of operation. In it, you access a database by executing a UAP on a HiRDB client.

Note however, that the HiRDB server platforms to which you can connect are limited, depending on the version of the HiRDB client. For details, see Appendix C. HiRDB Client and HiRDB Server Connectivity. Figure 1-8 shows a mode of operation in which a database is accessed by executing UAPs running on HiRDB clients.

Figure 1-8 Accessing a database by executing UAPs from HiRDB clients

In this mode, you can access a database by executing a UAP running on the HiRDB server.

Figure 1-9 illustrates the operating mode in which a database is accessed by executing a UAP running on the HiRDB server.

Figure 1-9 Accessing a database by executing a UAP running on the HiRDB server

In this mode, a HiRDB database is accessed when a UAP running on an OLTP machine (TP monitor) issues a service request. The client must have a service-requesting UAP; the server must have a service-providing UAP. Figure 1-10 illustrates the operating mode in which a database is accessed by executing an OLTP UAP.

Figure 1-10 Accessing a database by executing an OLTP UAP

HiRDB provides an ODBC driver. When the ODBC driver is installed in a HiRDB client, ODBC-compatible applications can access the HiRDB database. ODBC-compatible applications include many commercially available programs, such as Microsoft Access and PowerBuilder. UAPs that use the ODBC function provided by HiRDB can also access the HiRDB database. Figure 1-11 shows a situation in which an ODBC-compatible application accesses a HiRDB database.

Figure 1-11 Accessing a HiRDB database from an ODBC-compatible application

For details about accessing a HiRDB database from an ODBC-compatible application, see the HiRDB Version 8 UAP Development Guide.

HiRDB provides an OLE DB provider. By selecting the OLE DB provider when you install a HiRDB client, you can enable applications that support the OLE DB to access HiRDB databases. Figure 1-12 shows a situation in which a HiRDB database is accessed from an OLE DB-compatible application.

Figure 1-12 Accessing a HiRDB database from an OLE DB-compatible application

For details about accessing a HiRDB application from an OLE DB-compatible application, see the HiRDB Version 8 UAP Development Guide.

HiRDB provides a JDBC driver. By selecting the JDBC driver when you install a HiRDB client, you can enable applications that support JDBC to access HiRDB databases. Figure 1-13 shows a situation in which a HiRDB database is being accessed from a JDBC-compatible application.

Figure 1-13 Accessing a HiRDB database from a JDBC-compatible application

For details about accessing HiRDB from a JDBC-compatible application (using Java stored procedures and Java stored functions), see the HiRDB Version 8 UAP Development Guide.

HiRDB uses ADO.NET to provide the HiRDB.NET data provider, which is needed to access HiRDB. The HiRDB.NET data provider complies with the ADO.NET specifications. By selecting the HiRDB.NET data provider when you install a HiRDB client, you can enable applications that support ADO.NET to access HiRDB databases.

HiRDB.NET data provider is bundled with a common set of basic interfaces provided by the System.Data space of Net Framework. HiRDB.NET data provider also includes its own extensions to perform array insertion and access repetition columns.

Figure 1-14 shows an example in which a HiRDB database is accessed from an ADO.NET-compatible application.

Figure 1-14 Accessing a database from an ADO.NET-compliant application

For details about accessing HiRDB from an ADO.NET-compliant application, see the HiRDB Version 8 UAP Development Guide.