Using source control in Migrator
Migrator Source Control (SC) functions in the same way that the AR System SC functions, except that Migrator can generate differences reports between objects under SC. If SC is enabled AR System (Enforced mode enabled), Migrator can also enable SC. See Configuring-AR-System-servers and Setting-version-control-options.
SC is a standard that was developed for tools to interface to Source Control systems (such as Microsoft Visual SourceSafe, PVCS, CM Synergy, and so on). Migrator provides an interface to the SC system so it can "talk" to these tools. This allows you to save your work with version numbers and checkin and checkout capability. The checkin and checkout capability lets teams share an application without overwriting each other's work.
Migrator migrates an object and replaces it within the Source Control system if:
- The object is checked into SC.
- The object is checked out by the same user who is performing the migration.
If the object is checked out by a user other than the user who is performing the migration, the object is not migrated.
Because SC migration is multi-byte, all Unicode items are converted to multi-byte and back when working with SC.
Starting SC in Migrator
SC integration in Migrator is essentially the same as that in AR System. The one exception is that Migrator can compare the differences between SC objects using the Migrator differences report.
Migrator SC Options
To generate a differences report for SC, select Tools > Source Control > Show Differences. For information about working with differences reports, see Migrator-overview.
Groups, Data, DSO Maps, Fields, and Views cannot be added to SC.
To start and use SC in Migrator
- Verify that you have SC enabled AR System for a particular server by viewing the server window to see if SC columns are displayed.
- Select Tools > Source Control to display the Migrator SC options, or use the Source Control toolbar.
Using SC in Migrator
The Migrator SC menu and toolbar buttons enable you to perform standard SC functions. You can also check out objects, convert them from a .def file to a .migrator file, and generate a differences report. The SC login box requests your name and password only when you log on for the first time.
To verify that Migrator integrates to your Source Control systems application, view a window within Migrator. If SC is functioning, the following columns appear in the Migrator Server, Form Detail, and Script windows.
Source control information in Migrator windows
If you see a check mark over an object's icon, that object has been checked out. Migrator remembers column settings for the next viewing (see Rearranging window columns).
The following table lists and describes the functions available from the Migrator SC toolbar.
Source control icons in Migrator SC toolbar
Migrator SC icon | Description |
Get Latest Version | Retrieves the latest definition file for the object being checked into SC and imports it to a server. When you "get" an object, you are retrieving a copy. The file is not locked from other system administrators. |
Check In | Checks the file back into SC. If Enforced mode is enabled in AR System and you check in an object, the file is no longer locked and other system administrators can use it or modify it. If Enforced mode is disabled, more than one user can check in an object at the same time. |
Check Out | Checks a file out of SC. If Enforced mode is enabled in AR System and you check out an object, the file is locked and no other system administrator can modify it. If Enforced mode is disabled, more than one user can check out an object at the same time. |
Undo Check Out | Overrides objects that have been checked out by someone else. You must have a working folder set in your SC client for this command to work properly. The file is no longer locked and the earlier version is retained in the SC project. |
Add to Source Control | Adds the objects to the SC database. The file is archived in the SC project. |
Remove from Source Control | Removes the objects from SC. Note Removing files from SC does not remove them from the server. |
Show History | Shows the history of objects selected in the SC integration. History reports summarize information about revisions of the objects. |
Show Differences | Checks out objects, converts them to a .migrator file, and generates a differences report. See Migrator-overview. |
User Information | Displays user information about administrators of the SC database. |
Refresh Status | Refreshes the current status information of an object from the SC database. |
Run Source Control Client | Runs the SC system client. |