Master Configuration

Master configurations are files which specify AWM systems for corresponding modeled AWM applications. A successfully parsed master configuration file creates an AWM system in the Application Explorer view.

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. If this version number is equal to the cached AWM model in a client’s Eclipse workspace, AWM does not update the loaded applications. The master configuration is automatically checked to determine if a new model version is available. This action is performed once per session and master configuration as soon as a user executes any action of an unchecked AWM application.

If you want to deploy a new version of a model, you need to change the version number in the updated model to match the reference to the model version specified in the master configuration file. This will trigger the local model to be replaced with the specified version in every user workspace the next time a user starts a new IDE session and executes the first action in the application.

When working in a production environment, Micro Focus recommends that you load an AWM model that uses a master configuration.