Master Configuration

Master configurations are files which define AWM systems with available modeled AWM applications. A successfully parsed master configuration creates an AWM system in the Application Explorer view.

In addition, the master configuration file stores the following information about each application:

The logical name of the application.
Reference to the central storage location for the AWM model.
The version of the current AWM model.
Locally cached data that is to be deleted when the AWM model is updated.
Static property values.
Optionally, the restriction to specific USERIDs which are allowed to access a modeled application.

The version number in the master configuration is used to control model updates for all users of the configuration. As long as this version number is equal to the cached AWM model in a client’s Eclipse workspace, AWM does not update loaded applications. The master configuration is automatically checked to determine if a new model version is available. Due to performance implications, this is done once per session and master configuration, as soon as a user executes any action of a non-checked AWM application.