Cloud Software Group, Inc. EBX®
Documentation > Administration Guide > Technical administration
Navigation mode Documentation > Administration Guide > Technical administration

# Data model administration

## Administrating publications and versions

Technical data related to data model publications and versions can be accessed in the Administration section by an administrator.

Data Modeling contains the following two tables:

- Publications. Stores the publications available in the repository.

- Versions. Stores the versions of the data models available in the repository.

These tables are read-only but it is however possible to delete manually a publication or a version.

Important: If a publication or a version is deleted, then the content of associated datasets will become unavailable. So this technical data must be deleted with caution.

It is possible to spread this technical data to other TIBCO EBX® repositories exporting an archive from an EBX® repository and importing it to another one. It may be useful for propagating the evolutions of data models to other repositories.

## Migration of previous data models in the repository

In versions before 5.2.0, published data models not depending on a module were generated in the file system directory `${ebx.repository.directory}/schemas/`, with the name of the data model (product.xsd for example if the data model is named Product). Since the 5.2.0 version, this kind of data model is now fully managed within EBX® through Publications. That is, republishing an existing data model migrates it as a Publication and redirects linked datasets to the new embedded data model. The previous XML Schema Document located in `${ebx.repository.directory}/schemas/` is renamed and suffixed with toDelete, meaning that the document is no longer used and can be safely deleted.

## Schema evolutions

It is crucial to evaluate the impact of data model changes on the administration side. The following points are to be considered:

### Impacts on data persistence

Administration tasks can be related to the database cleanup after a modification of the models. The following link describes how the evolutions of data models are managed at the persistence level: Purging master tables in the database.

### Impacts on side features

Some components rely heavily on the data models and can be impacted by their evolutions. Some examples are: the user interface, the WSDL documents, existing archives, etc.

The 'Administration' section offers the possibility to manage some of these components (such as the views), whereas other components fall out of the administrator's scope, such as archives, WSDL files, etc.

Documentation > Administration Guide > Technical administration