Multiple Support Catalogs

Sets the current MDU catalog. Multiple copies of the MDU catalog can be created to support the use of different catalogs in a single session.

Note:
The Multiple Support Catalogs functionality is only available when all the databases, for example, MDS/CATA(DB No.7320), MDS/MDSAPPDEFAULTS(DB No.7351) and MDU/CATA(DB No.7355) are part of the selected MDB.

Select a catalog from the MDU drop-down list.

Copy MDU Catalog

Copies an existing MDU Catalog to support the use of multiple catalogs in a single session.

From

Select from the drop-down list to define the source MDU catalog to be copied.

To

Select from the drop-down list to define the target location of the created MDU catalog.

Description

Input a name for the created MDU catalog.

Messages

Describes what actions the application is carrying out.

Click Cancel to discard any changes and close the MDU Catalog Copy window.

Click Apply to copy the MDU catalog, a Confirm window displays informing you that the operation may take considerable time to complete.

Click Yes to continue with the copy process.

Note:
You are prompted to restart the session for the modifications to take effect.

Support Configuration File

By default, support configuration files are read from the default path which is the installation directory. The default path can be overwritten by setting the environment variable MDS_SUPPORT_CONFIG_LOCATION.

The standard support configuration file is named SupportConfigurationFile.xml. Multiple support configuration files are supported.

New support catalogs must follow a defined folder path:

%MDS_SUPPORT_CONFIG_LOCATION%userSupportConfiguration\Configuration-<MDU DB CODE>\plots

A folder named userSupportConfiguration must be added to the %MDS_SUPPORT_CONFIG_LOCATION% path.

All configuration information, for example, image files, the support configuration xml file and any other files specific to that support configuration must be stored in a unique configuration specific folder. This folder uses the naming convention Configuration-<MDU DB CODE>.

Plot files must be stored in the plots folder which is located in the configuration specific folder.

Specific naming conventions must be used, if the internally referenced MDU DB CODE is A, the naming convention is:

For example, if the %MDS_SUPPORT_CONFIG_LOCATION% is configured to a folder other than the installation directory, the default configuration xml file (SupportConfiguration.xml) must be located alongside the userSupportConfiguration folder. In the example, the %MDS_SUPPORT_CONFIG_LOCATION% folder is D:\localSupportConfigurations\.

The userSupportConfiguration folder contains a folder for each specific configuration.

The configuration specific folder contains the plots folder, image files and the support configuration file.

The plots folder contains the plot files.

A new support catalog that uses the key letter K may require a separate support configuration file, named SupportConfigurationFile-K.xml. The new support configuration file is stored in the configuration specific folder.

The DimensionsControlConfiguration id value, in the support configuration file, can be set to the defined key letter. For example:

<DimensionControlConfiguration id="K">

Mapping and representation for a specific support type can be defined. For example, AT510 and AT03.

For mapping name "AT510", the image id is "at510". The application searches for the image named at510.png. The image is stored in the same path as the support configuration file.

For mapping name "AT03", the image id is "at03". An image file is not found, the application uses the support standard image.

If an external image or a support standard image is not found, a blank image displays.