Progress
DataServer
for ORACLE Guide


DataServer Modules

The DataServer for ORACLE can run in a variety of configurations. Some configurations involve a single process running on one machine. Others involve multiple processes running on different machines across multiple platforms.

To set up a DataServer configuration, determine which modules you need on which platforms. Then, set up the appropriate executables on those platforms. Table 3–1 lists the possible combinations and describes which executables you must set up on each machine. The term local indicates that a DataServer runs on the same machine as the client. Remote indicates that a DataServer runs on a different machine than the client.

Table 3–1: Installing DataServer Modules
Client
DataServer
Installing and Configuring
NT
Local NT
Use the default Progress client executable (prowin32).
This executable also allow you to use SQL*Net or Net 8 to access ORACLE remotely.
NT or Windows
Remote NT
On the client machine, use the default Progress client executable (prowin32).
On the NT host machine, use the default broker executable (_probrkr) and configure it using ProControl. Unless you set ORASRV to point to another DataServer executable, the broker starts the default DataServer executable _orasrv.
Windows
Remote UNIX
On the client machine, use the default Progress client executable (prowin32).
On the UNIX host machine, use the default broker executable (_probrkr) and set ORASRV to point to the _orasrv DataServer executable to access ORACLE7 or ORACLE8. This executable supports Progress networking.
UNIX
Local UNIX
To access ORACLE7 or ORACLE8, use the orarx client executable.
This executable also allow you to use SQL*Net or Net 8 to access ORACLE remotely.
UNIX
Remote UNIX
On the UNIX client machine, use the default client executable (_progres).
On the UNIX host machine, use the default broker executable (_probrkr) and set ORASRV to point to the _orasrv DataServer executable to access ORACLE7 or ORACLE8. These executables support Progress networking.
UNIX
Remote NT
On the UNIX client machine, use the default client executable (_progres).
On the NT host machine, use the default broker executable (_probrkr). Unless you set ORASRV to point to another DataServer executable, the broker starts the default DataServer executable _orasrv.
These executables support Progress networking.
Windows
Local Windows
Use the default Progress Windows client executable (prowin32).
This executable also allow you to use SQL*Net or Net 8 to access ORACLE remotely.

NOTE: If you are using a DataServer on UNIX to access ORACLE on a platform where ORACLE does not support shared objects, you must build DataServer executables instead of using the default client, broker, and DataServer executables. See "Building DataServer Executables," for instructions.

For instructions on setting up your DataServer configuration, see the section or sections that apply to the platform you are considering. For example, if you are configuring a local DataServer where all the Progress modules run on the same UNIX machine, see the "Configuring UNIX Modules" section. If you are building a remote DataServer configuration with a UNIX client accessing an NT host, see the "Configuring UNIX Modules" section for instructions on setting up the client and see the "Configuring NT Modules" section for instructions on setting up the host.


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