Understanding Path Tokens

You use relative path tokens within a field. The software enables you to convert relative path tokens and absolute path names for those fields that accept them within the JD Edwards EnterpriseOne Product Packaging Tools. If any fields use a token, you can convert the token into an absolute path or you can convert the absolute path into a token. For example, you can convert any instance of $DEP into Z:\DepServer or you can convert Z:\DepServer into $DEP.

An absolute path name begins with the root directory and details the entire path, such as Z:\DepServer\CD Templates\Partial Update. A relative path name begins with a token, such as $DEP. The token represents at least the root directory and possible contiguous directory paths. For example, $DEP might represent Z:\DepServer. This relative path might appear within an applicable field as $DEP\CD Templates\Partial Update.

You do not need to define the tokens. The JD Edwards EnterpriseOne Product Packaging Tool automatically resolves the token values based on the installation and other information that is available to it.

These are the relative path tokens that you can use:

$DEP

Represents the root directory where JD Edwards EnterpriseOne is installed on the deployment server.

$IMAGE

Represents the image path of the software master.

$CLIENT

Represents the root directory where JD Edwards EnterpriseOne is installed on the workstation that you are currently using.

$TEMP

Represents the Microsoft Windows temporary directory of the workstation that you are currently using.