Harness Designs > Migration of Designs From Capital Harness Classic

Migrating a

Capital Harness Classic Design into Capital Harness Designer or Capital Harness Designer Modular

You can migrate a package of designs that have been premigrated from Capital Harness Classic.

See “Capital Harness Classic Design Migration to Capital” in the Capital Designer User Guide to create the premigrate package files.

Prerequisites

Valid Capital Harness Classic premigration package files are available for migration.
The package files must be in a folder named Caph (case insensitive). The migration process will not run if this naming convention is not used.
The user running the CapitalMigrate.exe must have: Full Capital permissions and access rights. See “User Accounts” in the Capital Access Manager - User Guide for user configuration.

Any Harness Domains that may be created during the migration, associated to their user account. See “Domains” in the Capital Access Manager - User Guide.

The target project specified in the premigrate process, into which the designs are to be migrated, exists in this Capital installation. If the project name specified does not exist, the migrate process will create it.
The release levels associated to each design to be migrated must exist in the target project. If they do not: The migrate process fails.

You must manually create the required release levels. See “Release Level” in the Capital Project Manager User Guide. Note You can configure the Capital Harness Classic Design Migration to Capital process to automatically map Capital Harness Classic (CapH) Release Status (Draft, Checking, Released, Obsolete) settings to specified release levels that exist in the target Capital database. See also the [CapHToXCMigration] section of the “Capitalh.ini file - Variable Descriptions” topic in the Capital Designer User Guide.

The CapitalMigrate_username.log file lists all release levels present in the premigration package files that must exist in the target project.

Ensure you have specified the required settings in the Bridge Options Dialog Box and that any pre-processor plugins that you have referenced there have been loaded. See Migration of Designs From Capital Harness Classic, to use Bridge Options when running the migration tool.
The premigrate process converts any Capital Harness Classic Range values assigned to the selected designs, into Capital Domain values and stores this information in the premigrate package. The target Capital installation must already contain the names of such Domains before you start the migrate process, otherwise they will not be defined against the migrated designs.

Procedure

On the machine where you want to run the Capital Migrate utility:Open a command prompt. Navigate to the capital_home/bin directory of the Capital installation. Run the CapitalMigrate.exe program using the command line flag -caph.For example: CapitalMigrate.exe –caph

(Optionally). Create a shortcut to the CapitalMigrate.exe program, (located in the capital_home/bin folder). Add the required command line flag, -caph, to the end of the Target field in the shortcut properties. Double-click the shortcut to run the program.

The Capital Migrate Login window is displayed. Enter the required username and password (see “Prerequisites”), and then click Login.
A file chooser dialog box displays. Navigate to the folder level that contains the Caph folder (see “Prerequisites”), and then click Select.
The Capital Migrate window displays, a status bar indicates the progress of the migration. The dialog box closes automatically once it has finished.

Results

All designs from the Premigrate package are migrated and can be opened in Capital Harness Designer or Capital Harness Designer Modular, as appropriate.
The CapitalMigrate_username.log file (located in your capital_temp folder) details any errors or warnings encountered during the migration and should always be checked.
Any module codes from Capital Harness Classic designs are created as functional module codes against the project and assigned as applicable functional module codes to the created designs.
Module code relationships are created at design level not project level.
The DXF image name appears in the Project browser. Double-click the name to open and view the image in the application Output Window.
The style set named during the premigrate task in Capital Harness Classic Designer is applied. If the style set name specified does not exist in the Capital installation, you are prompted to select an alternative style set when you first open the diagram in the Capital installation.
The Capital design name and part number are created from the Capital Harness Classic harness internal part number.
The Capital design revision is created from the Capital Harness Classic internal issue.
The migration process applies any “Auto Assign” Object Type Information (OTI) properties, which are configured in Capital Project Manager, to the relevant objects that have been migrated. See also “Object Type Information” in the Capital Project Manager User Guide.
The DSI data is migrated in accordance with the settings that you have defined in the Bridge Options Dialog Box.
Any “Range” attributes that you had configured against a design in the source Capital Harness Classic database are created as Domain values by the migration process. See “Prerequisites”.

Note

If you are migrating a design between Capital Harness Classic and Capital on the same database, the design name will already exist. As this has to be unique within the database, you must edit the internal part number or internal issue in the Premigrate Package.dsi file before starting the migration. The process will not migrate such designs.

Parent Topic:

Migration of Designs From Capital Harness Classic