Default AWM systems are automatically added to the Team Developer Tree View in newly created workspaces. They must either point to a master configuration file (see
Master Configuration) or contain a command which returns a master configuration. Optionally, default AWM systems can be defined with a remote system association (see
Local Master Configuration) and an application that is loaded by default.
Default AWM systems can be (re)added at any time by using the “Add System(s)…” function in the Team Developer Tree View.
| Element
|
Attribute
|
Explanation
|
| awmSystem
|
|
Represents one default AWM system.
|
|
|
masterConfigurationPath*
|
Path to a master configuration file. Depending on the master configuration format, the file suffix must be either xml or txt.
Must be defined only if no masterConfigurationCommand has been specified.
|
|
|
masterConfigurationCommand*
|
Operating system command string which returns a complete master configuration. Supports the XML format only.
Must be defined only if no masterConfigurationPath has been specified.
|
|
|
loadedApplication
|
Name of the AWM application to be loaded by default. The application must be contained in the referenced master configuration. Since only one AWM application can be loaded at a time, only the first referenced application will be loaded by default (others will be ignored).
|
|
|
associatedRemoteSystem
|
Name of the associated remote system, if any.
|
<awmSystem associatedRemoteSystem="zServer" loadedApplication="AWM Sample Model" masterConfigurationPath="F:\Models\SampleModel.xml" /> </awmSystem>
<awmSystem masterConfigurationCommand="cmd.exe /c type F:\Models\SampleModel.xml" />
