Defining MDAC parameters

Introduction

When a teamwork MDAC is selected, MDAC parameters are automatically initialized with optimal default values.

This section presents the different MDAC parameters, and describes their impact on the behavior of the teamwork MDACs.

The Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC, Objecteering CM Synergy and Objecteering Dimensions MDACs also provide additional MDAC-specific parameters. For details on these parameters, please refer to the corresponding chapter in this user guide.

Configuring the Objecteering teamwork MDACs

The Objecteering teamwork MDACs can be parameterized through the "Modifying configuration" dialog box as shown in Figure 20), which is launched by clicking on the "MDAC options" icon.

The "Diff-Merge" parameter set

The "Diff-Merge" parameter set represents the default values of the parameters used in the Diff-Merge wizard, launched using the "Diff-Merge models" command.

Figure 20. The "Diff-Merge" set of parameters for the Objecteering Multi-user MDAC

The ... parameter	is used to ...
Log	save all the modifications carried out during the merge in a file. Environment variables in $(OBJING_PATH) form can be used in this field to define the location of the log file.
External editor for merging texts	indicate the external editor used to merge all note types (C++, Java, documentation, etc). For example, filemerge on UNIX and winmerge on PC. Environment variables in $(OBJING_PATH) form can be used in this field to define the location of the external editor of your choice.
Options and arguments for merge editor	define the options and arguments of the editor used in the Diff-Merge of texts. According to the editor used, options and arguments can be different. Two variables must be used to represent the initial text and the text which is to be compared. $$(LEFTFILE) represents the initial text, and $$(RIGHTFILE) represents the text which is to be compared. Two $ signs must be used, in order to ensure that Objecteering interprets these parameters as $ plus the name of the variable. For example, $$(LEFTFILE) will be interpreted as $(LEFTFILE). This is important, as these parameters are used by Objecteering to create its own temporary files.
Merge result	define the file containing the result of the text merge. According to the editor used, the editor value can be different. For example, if the editor saves the result of the merge in the initial text, the $$(LEFTFILE) value must be given to this parameter.

Note: The above parameters do not exist for the Objecteering CM Synergy MDAC.

The "Search" parameter set

The parameters provided by the "Search" parameter set are used to specify the elements which are to be searched for through the "Get information" command. If the "Confirm operations" parameter is not active in the "General settings" parameter set, then these parameters are used directly to define the behavior of the "Get information" command. If the "Confirm operations" parameter is activated, then these parameters are proposed in the confirmation window of the "Get information" command.

Figure 21. The "Search" set of parameters for the Objecteering Multi-user MDAC

The ... parameter	is used to ...
Memorize search parameters	specify whether modifications made to parameters defined in the "Get information" command confirmation window should be memorized for the following search.
Elements checked-out by me	list the elements checked-out by the current user.
Elements checked-out by others	list the elements checked-out by other users.
New elements in the project	list the new elements present in the model and not yet checked-in in the repository.
Elements deleted from the repository	list the elements deleted by another user. These elements are no longer present in the repository, but are still present in the model.
New elements in the repository	list the new elements present in the repository and not yet present in the model.

Note: The parameters described exist only for the Objecteering Multi-user MDAC. By default, the "Elements deleted from the repository" and "New elements in the repository" parameters are deactivated, since a search for these elements is more lengthy.

The "General settings" parameter set

Figure 22. The "General settings" set of parameters for the Objecteering Multi-user MDAC

The ... parameter	is used to ...
Hierarchical operations	run commands on components. This parameter determine the hierarchical or non-hierarchical functioning modes of the check-out, check-in and model import operations (to know whether, for example, a package check-in automatically leads to the check-in of the classes it contains).
Confirm operations	select a mode employed by users to confirm operations. If this option is activated, certain commands run by you will be subject to interactive confirmation.
Update project at start-up	automatically run the "Import from repository" command when Objecteering is started. By doing this, the project is automatically updated with regard to the repository. Those elements which are still in check-out are not updated.
Memorize actions in the log	record in a file all actions carried out by you. By default, this file is created in the repository directory, and its name corresponds to your name followed by the ".log" suffix.
Log	define the file which will contain a record of all the actions carried out by the MDAC. This parameter is only used if the "Memorize actions in the log" parameter has been activated.
Confirm model component update	activate and deactivate the model component update prompt. If this tickbox is not checked, then Objecteering Multi-user will automatically update model components according to the information present in the "ramcList.conf" file, unless an undeclared model component is deployed.
Confirm MDA component update	activate and deactivate the MDA component update prompt. If this tickbox is not checked, then Objecteering Multi-user will automatically update MDA components according to the information present in the "modulesList.conf" file, unless an undeclared MDA component is deployed.

Note: The parameters described above exist for the Objecteering SCC, Objecteering ClearCase and Objecteering Dimensions MDACs, as well as the Objecteering Multi-user MDAC.

The "Work product options" parameter set

Figure 23. The "Work product options" set of parameters for the Objecteering Multi-user MDAC

The ... parameter	is used to ...
Update generation work products after import	update the paths of C++ generation work products (code generation and makefiles) and Java generation work products, using the values defined during C++ or Java MDAC parameterization.
Update generation work products before check-in	reverse the contents of the files generated before carrying out the check-in. This parameter is indispensable if the source code is modified outside Objecteering. If this is the case, this parameter allows modifications made to the source code to be automatically incorporated, before carrying out the check-in operation.

Note: The parameters described above exist for the Objecteering SCC, Objecteering ClearCase, Objecteering CM Synergy and Objecteering Dimensions MDACs, as well as the Objecteering Multi-user MDAC.