Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

> ## Reviewing the Windows platform installation directory structure

> The OpenEdge installation `PATH` contains configuration files and several subdirectories. The installation `PATH` directory contains the OpenEdge executables, several procedure (`.p`) files, and other related files and subdirectories. The default installation `PATH` is `C:\Progress\OpenEdge`.

> The installation `PATH` that you choose is referred to as DLC; for the default OpenEdge installation `PATH`, `DLC` is `C:\Progress\OpenEdge`. During installation, the `DLC` variable (`%DLC%`) is automatically set to your OpenEdge installation `PATH`.

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

> Table 3–6 describes a directory tree of the OpenEdge subdirectories.

> Table 3–6: Progress (%DLC%) directory structure
> Directory name | Description
> --- | ---
> `auditing` | Contains object (.r), development, and environment (ADM2) files for the Audit Policy Maintenance product.
> `bin` | Contains the executable files for OpenEdge, such as PRODB. It also contains batch files and system executables.
> `certs` | Contains the public keys of the Certificate Authorities (CAs) used by OpenEdge clients to perform server-side certificate validation when communicating with secure Web servers using HTTPS.
> `dotnet` | Contains support files to develop and deploy the dotnet client.
> `esbadapter` | Contains the configuration and support code for the OpenEdge Adapter for Sonic ESB.
> `gui` | Contains object (`.r`), development, and environment (ADE) files for the OpenEdge graphical tools. These tools are compiled to run in graphical mode in Windows 2000, Windows 2003, and Windows XP Professional; they cannot run in a character environment.
> `include` | Contains C and C++ header files.
> `install` | Contains Java tailoring classes that only the Installation Utility uses.
> `java` | Includes the Java files and executables necessary for running OpenEdge products.
> `javahelp` | Contains .jar files for the OpenEdge Application Debugger.
> `jdk` | Contains the Java Development Kit files and executables necessary for running OpenEdge products.
> `jms` | Contains files to support client deployment of java messaging.
> `jre` | Contains the Java Runtime Environment files and executables necessary for running OpenEdge products.
> `keys` | Contains encrypted RSA Private Key and Certificate file information.
> `lib` | Contains shared objects necessary for running OpenEdge executables.
> `licenses` | Contains license and copyright information related to HTTP Client, Open SSL toolkit, Perl, and w3c IPR software notice.
> `netsetup` | Contains files for the Shared Network Installation Utility.
> `odbc` | Includes files to support ODBC.
> `oebuild` | Includes files that the OEBUILD utility uses when creating custom executables.
> `oeide` | Contains the Eclipse environment, the plugins that comprise the OpenEdge Architect product, and other related files.
> `ora` | Contains files to support the DataServer for ORACLE.
> `perl` | Contains files to support the use of the Perl scripting language.
> `proedit` | Contains files to support the advanced editing features.
> `prohelp` | Includes the online help and other necessary files for OpenEdge.
> `prokey32` | Contains files for international keyboard support for the 32-bit Windows Character Client.
> `prolang` | Contains the national language support directories.
> `properties` | Contains property files that manage the configuration of OpenEdge services, such as WebSpeed, the NameServer, and the AppServer.
> `scripts` | Can contain files related to the Failover Cluster component.
> `servlets` | Identifies the default location of the AIA and WSA servlet containers. These containers include web definitions. 1
> `sonic` | Contains files that support the Sonic client and container.
> `sports` | Includes the schema triggers and supplier information for each sample database.
> `sports2000trgs` | Includes the schema triggers for the Sports2000 database.
> `src` | Contains source files for OpenEdge ADE tools, such as the WebSpeed, Data Dictionary, Procedure Editor, and Sample Applications.
> `templates` | Can contain files related to the Failover Cluster component.
> `toolkit` | Includes files that help in deploying and encrypting your applications.
> `tty` | Includes mostly object (`.r`) files for character-mode OpenEdge.
> `ubqmanager` | Includes files used by the AppServer exclusively. Do not modify these files.
> `wcadd` | Contains Web Client cd images that include, among other files, the `setup.exe` to install the Web Client.
> `webinstall` | Contains several WebSpeed-related files, including samples, scripts, and help files.
> `webspeed` | Supports WebSpeed Workshop files such as samples, scripts, and help, that reside on the Web server.

> 1Refer to your OpenEdge product documentation for details about configuring was and aia.

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