Application Models

In a Definer repository, you define an application. In the Teamwork part of the Definer, you compose this application in terms of business areas, business objects, and tables that are owned by a business object.

This screenshot shows a Travel Agency example:

Exactly this composition is used in USoft Repository Manager, where you can generate an application model for an exported repository version. This application model can then be used to export the application in XML format. An application model consists of:

·	All business areas, business objects, and tables of a repository version.

If a business object does not belong to a business area, the business area is set to DefaultBusinessArea. If an application table does not belong to a business object, the business object is set to DefaultBusinessObject.

·	An XML document that describes this structure. The format of this Export Model is:

<REP_NAME model="REP_VERSION|CODE" code="CODE">

...tables that are not owned by a Business Object...

</DefaultBusinessArea>

<BA1>

...tables that are owned by a business object in BA1...

</BA1>

...

</REP_NAME>

If the repository version is a production version, the model attribute contains the code of the repository version for this production version. If not, the model attribute contains the code of the repository version. For example:

</DefaultBusinessArea>

</Travel>

</TRAVEL>

Applications, or parts of it, can be exported in XML format. They are stored in the Applications folder, as specified in the Folder Locations window, for example:

C:\XML Repository Manager\applications\

NAMING CONVENTIONS:

File names for exported XML applications follow these rules:

·	Applications that are exported from the Export Application button in the Repository Versions window, or from the context menu of the catalog, have name:

<Repository Version Code>_app.xml

·	Application tables that are exported from the context menu of the catalog, have name:

<Repository Version Code>_<table name>.xml

·	Applications that are exported using the Export Application Basket dialog, have name:

<Basket Exports folder>\<Repository Version Code>_<basket name>.xml