Try OpenEdge Now
skip to main content
DataServer for Oracle
Configuring the DataServer : Configuring UNIX modules : Configuring the DataServer on the UNIX host

Configuring the DataServer on the UNIX host

To configure the remote DataServer modules on UNIX, you set environment variables on the host machines, as described in the following table. In a remote DataServer configuration, you set all necessary variables on the host machine. Be sure to set the variables in the same environment (UNIX shell) from which you plan to run the DataServer. No configuration is required on the client machine.
The only environment variable in the following table that you set on the client is PROEXE.
Table 28. Environment variables for the remote DataServer
How to set it
The pathname to the directory where the DataServer creates the log file, dataserv.lg, to track processes and error messages. By default, the DataServer creates this file in the current directory. (Optional)
The pathname of the directory where Oracle is installed. (Required)
The identifier for the Oracle instance you are accessing. (Required)
The name of the executable (including the path) of the Oracle DataServer. Set ORASRV to point to the appropriate DataServer executable. (Required)
The pathname to the executable of the broker. (Optional)
The pathname of your default OpenEdge startup file.
To set the Message Buffer Size (-Mm) startup parameter for the broker to a value different from the 1024 default buffer size, you must set the PROSTARTUP environment variable equal to the path and name of the .pf file that contains the -Mm parameter.
This approach ensures that your value is recognized and therefore used by the broker when it starts. Only Windows clients must use this technique.
Note: If you use the command line utility and intend to set the -Mm startup parameter to a value other than 1024, you must use the .pf file with the PROSTARTUP variable set.
Once you have set up your environment, you are ready to create a schema holder. See the Creating, Maintaining, and Deploying a schema holder for instructions.