Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

> ## Windows registry and the progress.ini file

> Applications running in Windows 2000, Windows 2003, or Windows XP Professional rely on the registry for startup information, such as color, font, and key bindings. OpenEdge keeps this information in the initialization file, `progress.ini`, located in your `Progress\OpenEdge\bin` directory. During the tailoring phase of the installation, the Installation Utility creates registry entries from the`progress.ini` data.

> Information from the progress.ini resides under the following registry keys:

> ``

>     HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\version10.1A

> ``

>     HEKY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\version10.1A

> Note: If you modify the `progress.ini` information, you must run the `ini2reg` utility.
> This utility updates the information in the registry.

> See OpenEdge Deployment: Managing 4GL Applications for more information on the `progress.ini` file and the `ini2reg` utility.

> ##### Environment variables

> OpenEdge supports some environment variables for graphical user interface (GUI) clients in the [Startup] section of the `progress.ini` file. OpenEdge supports environment variables for character clients, such as the AppServer and WebSpeed Agents, in the [WinChar Startup] section of the `progress.ini` file.

> Table 7–1 lists the supported environment variables.

> Table 7–1: Supported environment variables
> Variable | Progress.ini file section | Description | Example
> --- | --- | --- | ---
> `DLC` 1 | [Startup] [WinChar Startup] | The relative pathname of the directory where you installed your OpenEdge system software. By default, the installation utility sets this variable. |
>     set
>     DLC=C:\Progress\
>     OpenEdge
> `EVTLEVEL` | – | Windows 2000 only. Specifies the level of information that OpenEdge writes to the 2000 Application Event Log. You can specify one of the following cases: None — No OpenEdge events are written to the Event Log. Brief — OpenEdge Error and Warning messages are written to the Event Log. Normal — OpenEdge Error and Warning messages are written to the Event Log along with any OpenEdge messages that are normally written to the log file (`.lg`). This is the default. Full — OpenEdge Error, Warning, and Informational messages are written to the Event Log along with any messages generated by the Message Statement. |
>     set EVTLEVEL =
>     NORMAL
> `PATH` | – | A list of directory paths separated by semicolons. When you run a program or batch file, the system searches for it in the current directory. Then it searches in the directory paths defined in `PATH` in the order they are mentioned. Your`PATH` should include any directory pathname that contains a program or batch file you want to run. Also, each directory pathname should include the drive letter of the disk that contains the directory. `PATH` is a system environment variable, not an OpenEdge environment variable. Set it in a manner appropriate for the operating system instead of in the registry or in progress.ini. Different OpenEdge products require different `PATH` settings. To set up `PATH` for your OpenEdge product, follow the instructions provided in the "Reviewing the Windows platform installation directory structure" section |
>     set PATH=%PATH%;
>     %DLC%\BIN;%DLC%
> `OEBUILD` | [Startup] | The pathname of the directory that contains items referenced in link scripts produced by the `OEBUILD` utility. By default, the installation utility sets this variable. |
>     set OEBUILD=
>     C:\Progress\
>     OpenEdge\OEBUILD
> `PROCFG` | [Startup] [WinChar Startup] | The filename (or full pathname) of your product’s configuration file. The configuration file is a data file that identifies the OpenEdge products and components that you are licensed to use. Reset `PROCFG` if you have moved your configuration file from the directory where you installed OpenEdge. |
>     set PROCFG=%DLC%\
>     PROGRESS.CFG
> `PROCONV` | – | The filename (or full pathname) of the OpenEdge `convmap.cp` file. The `convmap.cp` file is a binary file that contains all of the conversion tables that are available to OpenEdge. See OpenEdge Development: Internationalizing Applications for more information on the `convmap.cp` file. |
>     set PROCONV=%DLC%\
>     CONVMAP.CP
> `PROMSGS` | [Startup] [WinChar Setup] | The full pathname of your OpenEdge error messages file. The default value is `%DLC%\promsgs`. Set the `PROMSGS` environment variable only if you want to use an error messages file different from the default `PROMSGS` file in the `%DLC%` directory. |
>     set PROMSGS=
>     C:\Progress\
>     OpenEdge\PROLANG\
>     GER\PROMSGS.GER
> `PROPATH` | [Startup] [WinChar Setup] | A list of directory paths separated by commas. By default, the installation utility sets this variable. |
>     set PROPATH=.,
>     C:\Progresss\
>     OpenEdge
> `PROSTARTUP` | – | The pathname of the OpenEdge default startup parameter file, `startup.pf`. This file is read by all OpenEdge modules at startup; it must exist for OpenEdge to execute properly. |
>     set PROSTARTUP=
>     C:%DLC%\STARTUP.PF
> `JDKHOME` | – | Establishes the top-level directory for the Java Developer’s Kit (JDK). |
>     set
>     JDKHOME=%DLC%\jdk
> `JREHOME` | – | Establishes the top-level directory for the Java Runtime Environment (JRE). |
>     set
>     JREHOME=%DLC%\jre
> `JFCHOME` | – | Establishes the top-level directory for the Java Foundation Classes (JFC). |
>     set
>     JFCHOME=%DLC%\jfc
> `JDKCP` | – | Sets the classpath for `class.zip`; Java Developer’s Kit (JDK) only. |
>     set JDKCP=
>     %variable-name%/
>     lib/class.zip
> `JRECP` | – | Sets the classpath for Java Runtime Environment (JRE); if no JRE, then it sets classpath for JDK. |
>     set JRECP=
>     %variable-name%/
>     lib/rt.jar
> `JFCCP` | – | Sets the classpath for Java Foundation Classes (JFC) only. |
>     set JFCCP=
>     %variable-name%/
>     swingall.jar
> `PROGRESSCP` | – | Contains a list of paths, jar files, and zip files for running Progress-specific products. |
>     set PROGRESSCP=
>     %variable-name%/
>     java/progress.zip
> `CLASSPATH` | – | OpenEdge correctly sets the appropriate classpath variable based on the platform in use. |
>     set CLASSPATH=
>     $JDKCP;$JFCCP;
>     $PROGRESSCP
> `JIT` | – | Sets the just-in-time compiler correctly. |
>     set JIT="-nojit"
> `JVMEXE` | – | Sets the Java virtual machine to run correctly. |
>     set JVMEXE=jre

> 1Note that the `DLC` variable is set in the various command scripts and in the registry; the variable is not set at the system level.

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