|
A computer is a physical machine that participates in your DTAP arrangement. In that role, it is also referred to as an environment.
Each computer is uniquely identified by the following call to the RulesEngine internal component:
select RulesEngine.GetProperty( 'ENV COMPUTERNAME' )
You can register where folders of specific types are located on each of the participating computers. Do this by choosing Define, Computers and filling out the form. The meaning of each field is explained in the table below.
You only need to do this if you use path variables in upgrade scripts. In this case, Delivery Manager needs machine-specific folder paths in order to expand path variables to the correct path on each computer.
You only normally need to specify folders for target-side computers, that is, computers that you deliver to, as opposed to computers in the Development environment. But if you want to use your Development environment to test expanded paths in upgrade scripts, you must specify folder paths also for the Development computer(s) that you test from.
Field
|
Explanation
|
Computer Name
|
The name of the computer as returned on that computer by the following call:
select RulesEngine.GetProperty( 'ENV COMPUTERNAME' )
|
Install folder
|
The folder where USoft is installed.
|
Temp folder
|
The folder where Delivery Manager stores temporary or intermediate files used only as steps in a larger operation. It is typically not necessary to inspect materials placed in this folder except for debug purposes.
Do not confuse with the USoft Temp Folder specified at USoft installation time, which is the folder path returned by the following call:
select RulesEngine.GetProperty( 'USoftTempDir' )
You may choose to set "Temp folder" to the USoft Temp Folder.
|
Stash folder
|
The folder that you can use for temporary storage of application data that is in danger of being lost when it is transferred or transformed during upgrade. Once upgrade has proven successful, the contents of this folder is no longer relevant until the next upgrade.
|
Unpack folder
|
The folder on a target machine where new deliverables are placed before they are unpacked and deployed.
|
Root folder
|
The parent folder where deliverables of the current release and all the past releases are found. The root folder identifies the release tree.
|
Release folder
|
The folder where deliverables are currently written to each time they are released.
Delivery Manager automatically sets this value to a combination of the "Root folder" attribute and the current version name (as known in the Current Release window), as follows;
root-folder\current-version
|
Previous folder
|
The folder where deliverables of the most recent previous release were written to.
Delivery Manager automatically sets this value to a combination of the "Root folder" attribute and the previous version name (as known in the Current Release window), as follows;
root-folder\previous-version
If a previous version is not known, previous-version evaluates to the current version.
|
Using folder
|
A folder where helper files are placed that are necessary for operations in the parent folder. This folder contains the following 2 types of helper files for producing deliverables in the "scripts" parent folder:
•Intermediate .XML files and .XSL transformations that Delivery Manager needs to compile the "200.upg.rdbms.sql" database upgrade script: the new-style "Create-Tables" script. •.XSL transformations that are applied by upgrade scripts in the "scripts" folder and must be distributed to each target machine. Delivery Manager automatically derives this value either from the "Release folder" or the "Unpack folder" attribute, depending on the value of the "Set using relative to unpack" flag (see next).
|
Set using relative to unpack
|
In upgrade scripts, you can use the $$using path variable to refer to the using folder. $$using is expanded either to the "\scripts\using" subfolder of the release folder, or to the "using" subfolder of the unpack folder. For each machine, you can choose between these 2 alternatives by setting or unsetting "Set using relative to unpack".
|
|
