WDIR

Each release has a uniquely named WDIR environment variable based on the flow version root name of the release. For example, WDIR_PADSVX_2_6 or WDIR_PADSVX_2_5. The registration process defines these environment variables; each should have a unique value assigned to prevent sharing WDIR content between releases.

During runtime, PADS applications use environment wrapper scripts to create the WDIR environment variable and to assign the appropriate value based on the version of the application being executed. The scripts assign the WDIR_flow_version_root environment variable values to the WDIR environment variable. For example, suppose two releases are currently installed on your system, PADS VX.2.5 and PADS VX.2.6. If you do not modify the default values that are assigned during the registration process, the following two environment variables exist in your environment:

WDIR_PADSVX_2_5 = your WDIR value for PADS VX.2.5

WDIR_PADSVX_2_6 = your WDIR value for PADS VX.2.6

When you invoke an application from, for example, the PADS VX.2.6 release, the environment wrapper scripts detect the version and create a new runtime environment variable:

WDIR=<your_WDIR_value_for_PADSVX.2.6>

On Windows, the registration process prompts for setting the WDIR. Accepting the default value ensures that the registration process sets the variable correctly for the version of software you are installing.

The first element of the WDIR path must point to a local, writable location. At runtime, the standard location is appended to the WDIR path.

If WDIR is not set, $HOME/wdir is created and used as the writable location.

WDIR Path

The WDIR path consists of required and optional folder locations: a local path, a corporate path, a project path, and a standard path. A semicolon on Windows separates each part of the WDIR path. When parsed, the WDIR path typically is read from left to right.

The following describes each element of the WDIR path.

Local WDIR Path

A personal settings folder that stores project settings and a variety of files such as log and application configuration files. The folder must be writable and unique to the user.

Mentor recommends that you put the local WDIR on a local file system because network latency between the client system and the system hosting the folder could negatively impact performance. Also, user account control on Windows operating systems may make it difficult to write to a WDIR location on a remote drive when registering or installing software.

Corporate WDIR Path

A shared location where you can place files containing settings common to all users, such as templates, configuration files, and so on. Because this location is parsed after the local WDIR, any conflicts in application settings usually resolve to the value found in the corporate WDIR.

In the Windows environment, the corporate WDIR path should be a UNC pathname to support concurrent design.

Note:

The Remote Server Configuration Manager (RSCM) must have a WDIR path defined as a system environment variable.

Following is an example of how to configure a corporate-wide WDIR on Windows:

WDIR_PADSVX_2_6=C:\WDIR\PADSVX.2.6; \\appserver\shared\Mentor\Site_Config_VX.2.6

Where C:\WDIR\PADSVX.2.6 is the local writable WDIR location and \\appserver\shared\Mentor\Site_Config_VX.2.6 represents a shared WDIR location, such as a corporate WDIR.

Project WDIR Path

A shared location similar to the corporate WDIR path but that has files containing settings that are project-specific. Because this location is parsed after the local WDIR and corporate WDIR, any conflicts in application settings usually resolve to the value found in the project WDIR.

In the Windows environment, the project WDIR path should be a UNC pathname to support concurrent design.

Standard WDIR Path

A working directory that is always located in <flow_version_root>\SDD_HOME\standard. The folder contains application defaults and other settings that the end-user typically does not modify. At runtime, the environment wrapper scripts automatically append this location to the WDIR path. Therefore, you do not need to manually add this location to the WDIR path.