Administration commands

The "Generate element in repository" command

The "Generate element in repository" command can be run on all multi-user atomic units and is used to generated a multi-user atomic unit in the form of a file.

When the "Confirm operations" MDAC parameter has been activated, confirmation is requested before the command is launched. The confirmation dialog box that appears allows you to specify the directory where the element is to be externalized, as well as indicating whether the command should be run in hierarchical mode or not (as shown in Figure 29).

Note: It is not necessary to create the externalization directory before running the command. This directory will be automatically created by the command.

You have two possibilities:

· Generation directly in the repository. By default, the repository associated with the Objecteering is proposed.

· Generation in a directory other than the repository.

If the element is generated directly in the repository, you must make sure that you have the latest version of the element before launching the command, as other users will retrieve the version that is going to be generated in the repository.

For the Objecteering ClearCase MDAC, if the element is generated directly in the view, the file corresponding to the element must first be checked-out from the ClearCase interface and in the Objecteering project, and then a check-in run on this file before launching the "Generate element in repository" command.

For the Objecteering SCC MDAC, the file generated is not transferred to the provider, but is instead exclusively generated in the directory defined by the "Work directory" MDAC parameter. In this case, the retrieval operation should be run in the provider.

Figure 29. Running the "Generate element in repository" command

The "Unlock repository" command

The "Unlock repository" command is used to unlock the repository after a system error.

For the Objecteering Multi-user MDAC, this command deletes:

· all the files present in the "Locks" directory with the ".read", ".write" and ".cout" extensions

· the "multiuser.lock" file

For the Objecteering ClearCase MDAC, this command runs:

· an "Undo check-out" of the file associated with the project located in the "Project" directory if this file is checked-out

· an "Undo check-out" of the <username>.read file located in the "Locks" directory, if this file has been checked-out by the user who is running the command

· a "Check-in" of the "Actor", "Class", "Component", "DataType", "Item", "Locks", "Package", "Project", "Node", "Signal" and "UseCase" directories

For the Objecteering SCC MDAC, this command runs:

· an "Undo check-out" of the file associated with the project located in the "Project" directory if this file is checked-out

· a "Check-in" of the users.txt file, if this file has been checked-out by the user who is running the command and if it has been modified, or an "Undo check-out" if it has not been modified

· an "Undo check-out" of the <username>.read file located in the "Locks" directory if this file has been checked-out by the user who is running the command

Note: The "Unlock repository" command is not available in the Objecteering Dimensions Administration MDAC.

The "Synchronize element state in project" command

The "Synchronize element state in project" command synchronizes the state of a multi-user atomic unit with regard to its state in the repository. This command does not re-import elements, but simply updates their check-in/check-out state in Objecteering. This command must only be used when a standard operation cannot be carried out, when Objecteering and the repository are out of synch.

A save is made if at least one element has been resynchronized.

When the "Synchronize element state in project" command is run, its result can be seen in the Objecteering output window.

Note: The "Synchronize element state in project" command is not available in the Objecteering Dimensions Administration MDAC.

The "Modify the parameters" command

The "Modify the parameters" command is used to modify the MDAC's sensitive parameters.

For the Objecteering Multi-user MDAC, this command is used to modify:

· The name of the user. All the users connected to the same repository must have different user names. Before proceeding with the modification of this parameter, the administration MDAC checks that no elements are currently checked-out (so as to avoid consistency problems), and if any elements are indeed checked out, the name change is not carried out and an error message is displayed.

· The directory where the repository is stored. After modifying this parameter, we recommend that you run the "Import from repository" command on the project, in order to obtain the latest version of the model stored in the new repository. If this new repository is completely different from the former one, you should create a new project, install the teamwork MDAC and connect to the new repository.

· The optimization mode. For reasons of performance, we recommend that you never deactivate this parameter. If this parameter is deactivated, the version of elements will not be used to optimize "Check-in", "Check-out" and "Import from repository" operations. If this parameter is active, only those elements that have been modified will be imported into Objecteering.

Given the importance of these parameters, confirmation is systematically requested (with warnings).

Figure 30. Running the "Modify the parameters" command on the Objecteering MultiUser MDAC

For the Objecteering Dimensions MDAC, this command is used to modify:

· the Product

· the Design Part: the Design Part on which the model is associated

· the Workset: the Workset of the user in which the model is imported/exported

· the Variant

The "Modify the parameters" command is not available in the Objecteering SCC Administration MDAC.