Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

> ## Overview of the building process

> OpenEdge provides a single set of executables (both client and server) that will access any supported version of ORACLE. These executables dynamically locate and load ORACLE shared libraries on those UNIX platforms where ORACLE supports shared objects. For information on whether of not your version of ORACLE supports shared objects, see your ORACLE documentation or system administrator.

> The single executable dynamically locates and loads the ORACLE shared libraries. This means there is no need to set the system dynamic library path environment variable. However, you must set the environment variable `ORACLE_HOME` by specifying the pathname of the directory on your system where ORACLE is installed. On some 64-bit systems, `ORASOPATHNAME` must also be set to the complete file specification of the ORACLE client shared library.

> Whether or not you can use the single executable depends on your version of UNIX and your version of ORACLE. There are two possible scenarios:

> 1. ORACLE supports shared objects on your version of UNIX and OpenEdge is able to dynamically load the ORACLE shared object when the DataServer connects to your ORACLE database. In this case you do not need to build any executables. You do not need to set the system dynamic library path environment variable. You can use `_progres` as the client executable and `_orasrv` as the server executable.

> 2. ORACLE does not provide a shared object. You must build your server executable. You can also build a self-service client executable (`orarx`). Refer to the following sections of this appendix for instructions. Once you have built your server executable (`_orasrv`), you can use `_progres` to access a remote DataServer only. Because you statically link the necessary ORACLE code when you build your server, you do not need to set the `LD_LIBRARY_PATH` environment variable.

> Table D–1 lists possible UNIX client/server configurations and describes the process for setting up the client and server modules and indicating which executables need to be built.

> Table D–1: Building DataServer processes
> Client | Server | Building and configuring
> --- | --- | ---
> UNIX | Local UNIX | Use a single executable on a UNIX client process that includes the ORACLE DataServer. Use this configuration for local access or if you want the DataServer to access the remote ORACLE instance through ORACLE Networking.
> UNIX | Remote UNIX | On the UNIX client machine, use a client executable that includes the remote ORACLE DataServer. Building the client is optional. By default, the UNIX client executable supports access to the remote DataServer. On the UNIX host machine, use two executables: 1) the remote DataServer broker, and 2) the remote ORACLE DataServer.
> UNIX | Remote Windows | On the UNIX client machine, use a client executable that includes the remote ORACLE DataServer. By default, the UNIX client executable supports access to the remote DataServer. In the Windows host machine, configure the default broker executable using Progress Explorer.
> Windows | Remote UNIX | In Windows, use the default OpenEdge client executable (`prowin32.exe`). On the UNIX host machine, use two executables: The remote DataServer broker. The remote ORACLE DataServer.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095