A local master configuration file can either be located in the Eclipse root folder with the name MasterConfig.xml or MasterConfig.txt depending on its format. See Master configuration syntax for more information. Alternatively, a master configuration file can be returned by a local operating system command. See Master Configuration for more information. In this case, a local system reference can be created in the Application Explorer view:
This opens the Add System(s) dialog box.
Expand the local system reference to view all the applications defined in the local master configuration file.
The master configuration can be specified in one of two supported formats, flat format and XML. Both formats use the same keywords. The table below lists all available keywords and their descriptions.
The flat format master configuration consists of lines with keywords, together with their respective values. The keywords are separated from the values by a colon and at least one space.
For example, a row in the master configuration file might look like this:
System: System_nameLines beginning with an asterisk (*) are interpreted as comments.
| Flat format | XML format | Description |
|---|---|---|
| System | <System> | Name and identifier of the remote system as it is displayed in the tree view. It is used as a unique identifier for caching application data, therefore, Micro Focus strongly recommends that you do not change the name in a production system. |
| Appl | <Appl> | Name and identifier of the modeled application as it is displayed in the tree view. |
| Conf | <Appl conf="…"/> | Platform, path, and name of the model file. |
| Version | <Appl version="…"/> | Version of the model file. |
| INFO | <Appl info="…"/> | Optional. Information about the data that is deleted for consistency in the Eclipse workspace when loading a new version of the model. |
| Property: <Property ID>=<Value> | <Property propertyID="…" value="…"/> | Static property values for an application. |
| EndAppl | </Appl> | End of an application description. |
Any number of modeled applications can be listed for a system. The master configuration file must have at least one application defined.
The Conf entry consists of the specification of the platform together with the platform-dependent fully-qualified or absolute file name. The only supported value for the platform is local..
local:c:\config\config.xml (Windows)
local:/etc/AWM/config/masterconfig.xml (UNIX)
The INFO entry determines which persistent information held in the Eclipse workspace have to be deleted in the case of a version change of the modeled application. Permitted information are filters and elements. The information can be combined in any way.
| INFO entry | Deleted files | Content of the files |
|---|---|---|
| filters | ft_filters.xml | All filters in the application. |
| elements | et_elements.xml
eb_elementsinlists.xml li_<listid> lm_Element_Lists.xml |
All cached elements that are assigned to the application and all element lists in the application. |
A local master configuration can be returned dynamically by an operating system command. The command which could, for example, execute a script file to return the configuration must be specified with the teamdeveloper.masterconfig Java system variable. See Setting Java System Variables for more information.
When setting the Java system variable in the eclipse.ini file, you must ensure that the Eclipse instance is stopped and restarted before the change can take effect. [2]
The value of the variable must contain an operating system command, which returns a complete master configuration file, in XML format, to standard out when executed. If the script is a Windows .bat file, it should start with @echo off so that only the master configuration file lines are written to standard out. [2]
For example (Windows):