skip to main content
Corticon Server: Deploying Web Services with .NET : Corticon Server for .NET files and API tools : The Corticon Server for .NET home and work directories
 

Try Corticon Now

The Corticon Server for .NET home and work directories

As a Corticon installation completes, it tailors two properties that define its global environment. These variables are used throughout the product to determine the relative location of other files.

Corticon environment

The installer establishes a common environment configuration file, \bin\corticon_env.bat, at the program installation location. That file defines the Progress Corticon runtime environment so that most scripts simply call it to set common global environment settings, such as CORTICON_HOME and CORTICON_WORK_DIR (and, in some cases, simply CORTICON_WORK.)

CORTICON_HOME

The explicit path of the installation home directory -- either the default location, C:\Program Files\Progress\Corticon 5.7, or the preferred location you specified -- is assigned to [CORTICON_HOME].

CORTICON_WORK_DIR

The explicit path of the work directory -- either the default location, C:\Users\{username}\Progress\CorticonWork 5.7, or the preferred location you specified -- is assigned to [CORTICON_WORK_DIR].
Note: The Corticon Start menu provides a Corticon Command Prompt command that calls corticon_env.bat, adds several [CORTICON_HOME] script paths to the PATH so that you can launch scripts by name from several locations -- \bin, \Server\bin, \Server\pas\bin, \Studio\bin, and, \Studio\eclipse -- and then relocates the prompt to the root of the Corticon work directory.

It is a good practice to use global environment settings

Many file paths and locations are determined by the CORTICON_HOME and CORTICON_WORK_DIR variables. Be sure to call corticon_env.bat, and then use these variables in your scripts and wrapper classes so that they are portable to deployments that might have different install paths.
Note: While you could change these locations with the assurance that well-behaved scripts will follow your renamed path or location, you might also encounter unexpected behaviors from any that do not. Also, issues might arise when running update, upgrade, and uninstall utilities.