The DSL uses the concept of a configuration to organize different local NX settings. This allows a site to have different customizations for different areas, such as product design and tool design. A configuration also can be used to isolate local changes for testing before being placed in the "production" configuration.
A configuration collects and organizes the following types of files that are locally created or modified by the site:
Configuration directories are organized into NX version directory structures. Each major version of the DSL will look for the configuration settings within the NX version directory that DSL version supports. For example, DSL X.y.z supports NX X.y and looks in the nxX.y directory for the local configuration. A configuration may contain several NX version directories depending on how many NX versions you are supporting. NX versions that are no longer being used can then safely delete its NX version directory in the configuration.
NOTE: In the documentation you will see symbolds like DSL X.y.z and NX X.y instead of typing in the current version that will be osbolete soon I instead use general lettering, such that DSL X.y.z could mean DSL 9.0.1 and NX X.y could mean NX 9.0. So keep that in mind as you read this documentation.
The ugsite directory is where all the site's configuration directories are located. More information on this directory can be found here.
The DSL Menu program includes an Options menu that allows the user to control the visibility of configuration types. The default is to only have Production configurations visible. The Options menu is hidden from the user unless the DSL Menu program is started with the commandline argument: --showOptions. The command on Windows would be:
$DSL_BASE_DIR/start_dsl.vbs --showOptions
The configuration directories are created and managed by the DSL configuration program. To invoke the program, type the following command in a terminal window:
$DSL_BASE_DIR/dsl_configure.vbs
Where DSL_BASE_DIR is the the directory where the DSL is installed by the build center which should be something like C:\Program Files\nxdslX.y.
The DSL's primary purpose is to setup the environment to configure NX the way the Customer desires. The local site can also add to this environment. The areas of control the DSL are has are:
The order that these areas are evaluated is:
Settings in later areas can override settings defined in earlier areas with some exceptions.
Applications can be defined with the Disable Customizations flag set. The modifies the evaluations that take place when the application is launched. The evaluations are: