Progress
DataServer
for ORACLE Guide


Overview

As of version 9.1, Progress provides a single set of executables (both client and server) that will access any supported version of ORACLE (7.3 or later). 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, please 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 LD_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.

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

  1. ORACLE (Version 7.3 or later) supports shared objects on your version of UNIX and Progress 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 PROBUILD any executables. You do not need to set the LD_LIBRARY_PATH environment variable. You may use _progres as the client executable and _orasrv as the server executable.
  2. ORACLE (Version 7.3 or later) supports shared objects on your version of UNIX, however, Progress is unable to dynamically load the ORACLE shared object when the DataServer connects to your ORACLE database. In this case you do not need to PROBUILD any executables. However, you may use _progres to access a remote DataServer only. You may use orarx as a self-service client and _orasrv as the server executable. In the environment where you want to run orarx and__orasrv you must set the LD_LIBRARY_PATH environment variable. If either orarx or _orasrv has the SETUID bit on you must also include a soft link pointing to the ORACLE shared libraries in /usr/lib.
  3. ORACLE does not provide a shared object. You must PROBUILD your server executable. You may also PROBUILD 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 may use _progres to access a remote DataServer only. Because you statically link the necessary ORACLE code when you PROBUILD your server, you do not need to set the LD_LIBRARY_PATH environment variable.

The following sections provide detailed instructions on using the Progress PROBUILD utility to build executables. These instructions apply if you are building custom executables by choice on UNIX, NT, or Windows.

Table E–1 lists the possible configurations that include UNIX and describes the process for setting up the client and server modules.

Table E–1: Building DataServer Processes 
Client
Server
Building and Configuring
UNIX
Local UNIX
Use PROBUILD to build a single executable for a UNIX client process that includes the ORACLE DataServer as a configurable element.
Build this configuration for local access or if you want the DataServer to access the remote ORACLE instance through ORACLE communications (SQL*Net or Net 8).
UNIX
Remote UNIX
On the UNIX client machine, build a client executable that includes the remote ORACLE DataServer as a configurable element using PROBUILD. Building the client is optional-by default, the UNIX client executable supports access to the remote DataServer.
On the UNIX host machine, build two executables: 1) the remote DataServer broker, and 2) the remote ORACLE DataServer.
UNIX
Remote NT
On the UNIX client machine, build a client executable that includes the remote ORACLE DataServer as a configurable element using PROBUILD. Building the client is optional-by default, the UNIX client executable supports access to the remote DataServer.
On the NT host machine, configure the default broker executable using ProControl on NT.
Windows
Remote UNIX
On Windows, use the default Progress client executable (prowin32.exe).
On the UNIX host machine, build two executables: 1) the remote DataServer broker, and 2) the remote ORACLE DataServer.

NOTE: If you are building executables to access ORACLE7 (7.2 and earlier) and ORACLE8, you must build separate executables for each version. When you build an executable, you link to ORACLE libraries that vary across versions.


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