Migrating the repository
Introduction
When migrating Objecteering from an earlier version, it is important to correctly carry out the migration of Objecteering models, which use one of the Objecteering teamwork MDACs, so as to guarantee that the teamwork repository will be compatible with the version of the MDAC delivered with Objecteering 6.1.
Two case scenarios are possible:
· migration from version 6.0 or a more recent version of Objecteering
· migration from an earlier version of Objecteering
Before carrying out any migration operations, we recommend that you save your UML models (.ofp files).
Furthermore, depending on the teamwork MDAC you are using, we recommend that you carry out the following operations:
· If you are using the Objecteering Multi-user MDAC, we recommend that you make a backup of the repository.
· If you are using the Objecteering ClearCase or Objecteering SCC MDACs, we recommend that you apply a label to the teamwork repository.
·
If you are using the Objecteering Dimensions MDAC, we
recommend that you create a new baseline.
Furthermore you have to create 2 new types of item:
o OBJING_TMP: This item type corresponds to files temporarily versioned. Changes management rules must be disabled for this item type.
o
OBJING_CFG: This item type corresponds to repository configuration files. If change
management is activated on the MDAC, it is assumed to be active on this type of
items.
Old configuration files used the OBJING_EXT item type. They will then not be
found anymore by the MDAC and must be recreated manually with the new item
type.
· If you are using the Objecteering CM Synergy MDAC, we recommend that you carry out the appropriate operations to be able to roll back the repository to its previous state.
This application of a label or creation of a baseline must only be carried out if all files have been checked-in. In this case, all users should run a "Project check-in" before applying the label. After this operation, an "Import from repository" must be run on an Objecteering model, so as to transfer the latest corrections made by other users. It is then possible to run the "Apply label" command on the root of the Objecteering model.
Migration from version 6.0 or a more recent version of Objecteering
It is strongly advised that you ensure that no developers are working on the repository during the migration procedure.
In the case of migration from version 6.0 or a more recent version of Objecteering, the repository administrator must carry out the operations detailed below.
First, open an old database with Objecteering. This will automatically migrate the database.
Next, update all selected MDACs except the teamwork MDAC, to the latest available version.
Continue by selecting the new version of the Objecteering teamwork MDAC you are using.
The following dialog box will appear, explaining that you are trying to use a newer MDAC on an earlier repository:
Figure 4. Window informing you that you are trying to use a newer version of the MDAC on an earlier repository
Next, select the corresponding Objecteering teamwork administration MDAC. A second dialog box will propose the migration of the repository.
Figure 5. Window proposing the migration of the repository
Click on the “OK” button to migrate the repository.
In case you accidentally click on “Cancel”, this dialog box will appear:
· each time you select the administration MDAC
· each time you open a project with the administration MDAC selected
· each time you run any teamwork MDAC operation
The repository is now ready to be used by developers and should no longer be used with the old teamwork MDAC.
Each developer must then:
· Open his old database with Objecteering. This will automatically migrate the database.
· Update all selected MDACs except the teamwork MDAC, to the version the repository administrator has chosen.
· Select the new version of the Objecteering teamwork MDAC you are using.
Note: MDAC parameter settings are retained when the latest version of an Objecteering teamwork MDAC is selected.
Migration from an earlier version of Objecteering
In the case of migration from a version of Objecteering earlier than the 6.0 version, the teamwork repository must be recreated from an up-to-date project.
The following steps should be carried out:
1. With the previous Objecteering installation:
o
For each project connected to the repository, run a check-in on all elements which have been checked-out, so as to guarantee that the repository contains the latest modifications.
This operation can be launched by running the "Project
check-in" command for each Objecteering model.
o From one of the projects, run the "Import from repository" command on the root package, in order to have a complete Objecteering model, and then unselect the teamwork MDAC. Only this Objecteering model will exist after site migration. You must no longer use the other Objecteering models after installation of Objecteering 6.0.
2. Update the Objecteering server and all clients to the latest version:
o Ensure that you have the correct license file for Objecteering 6.0.
o Stop the "objingsrv" and "lmgrd" services.
o Launch the update of your site.
o Restart the "objingsrv" and "lmgrd" services. The Objecteering 6.0 server is now operational.
3. Recreate the teamwork repository and user projects:
o On the Objecteering model used during phase 1, select the Teamwork MDAC, and define the name and directory in which the new teamwork repository will be created.
o A new database should then be created for each user from the database used to create the new teamwork repository. The database file can be copied or a new database created and connected to the repository.
o For each copied database, select the administration MDAC, and run the "Modify the parameters" command to define the specific teamwork MDAC parameters, before making the model available.
o For each copied database, the MDA component parameters must be checked and corrected to each user's individual needs.
Special attention should be paid to the “Root directory for generation” (GenRoot)
Modeler parameter.