Corticon Server is a set of Java classes, packaged in Java archive files. The required set of JARs needed to deploy and call Corticon Server is:

JAR Description
CcServer.jar The main Corticon Server JAR, containing the core engine logic.
CcConfig.jar Contains a set of .property files that list and set all the configuration properties needed by Corticon Server. These properties pages are not intended for user access. Instead, the file brms.properties, installed by every product at the root of [CORTICON_SERVER_WORK_DIR], enables you to add your override settings to be applied after the default settings have been loaded.
CcLicense.jar An encrypted file containing the licensing information required to activate Corticon Server. Note that you need to obtain a specific license for .NET server.
CcThirdPartyJars.jar Contains third-party software such as WSDL.
CcDrivers.jar Contains the database drivers used by Corticon Server.
CcExtensions.jar Supports Service Callouts and extended language operators.

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:

CORTICON_HOME The installation directory -- either the default location, C:\Progess\Corticon x.x, or the preferred location you specified.
CORTICON_SERVER_WORK_DIR The work directory -- either the default location, C:\Progress\Corticon_Server_Work_x.x, or the preferred location you specified.
Note:

It is a good practice to use global environment settings

Many file paths and locations are determined by the CORTICON_HOME and CORTICON_SERVER_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.

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.

Corticon Server Sandbox

When Corticon Server starts up, it checks for the existence of a sandbox directory. This Sandbox is a directory structure used by Corticon Server to manage its state and deployment code.

The location of the Sandbox is controlled by com.corticon.ccserver.sandboxDir settings in your brms.properties file. This configuration setting is defined by the CORTICON_SERVER_WORK_DIR variable, in this case:

com.corticon.ccserver.sandboxDir=%CORTICON_SERVER_WORK_DIR%/%CORTICON_SETTING%/CcServerSandbox

In a default Windows installation, the result for this is C:\Progress\Corticon_server_Work_x.x\SER\CcServerSandbox. In other words, in the SER subdirectory of the CORTICON_SERVER_WORK_DIR. This directory is created (as well as peer directories, logs and output) during the first launch of Corticon Server.

Note: If the location specified by com.corticon.ccserver.sandboxDir cannot be found or is not available, the Sandbox location defaults to the current working directory as it is typically the location that initiated the call.