Overview of the teamwork administration MDAC

Introduction

The administration MDAC should be used in regular user databases only:

· when MDAC commands are not functioning

· when you are "blocked"

· when Objecteering has crashed and consistency must be re-established between the repository and the project

The aim of this MDAC is to allow you to unblock an Objecteering project which is in an incoherent state.

Warning! It is imperative that you have a sound knowledge of the workings of the MDAC, in order to be able to use this administration MDAC with no risk of losing valuable data.

The repository administrator should normally be the only user to have deployed the teamwork administration MDAC, since deployment of this MDAC provides special rights (for example, the right to migrate the repository).

If you deploy the teamwork administration MDAC, the teamwork MDAC you are using considers that you are the repository administator.

The administration MDAC must not be deployed by default in regular user databases, but rather ONLY if the teamwork MDAC is functioning incorrectly. When it is being used, it is preferable that no other users use the teamwork MDAC (check-in, check-out or import commands).

All commands are available on elements in both read-only mode and read-write mode.

If the "Hierarchical operations" tickbox has been checked at MDAC parameter level, then the effect of these commands is propagated on all sub-elements.

Note: The MDAC must have already been deployed in order for the administration MDAC commands to function properly.

Administration MDAC commands

The ... command	is used to …
Generate element in repository	generate a multi-user atomic unit in the form of a file in the repository.
Unlock repository	delete the locks present on the repository.
Synchronize element state in project	synchronize the state of a multi-user atomic unit with regard to its state in the repository.
Modify the parameters	modify MDAC parameters. This command should be used with caution.