Migrating the EnterWorks Data Model
In order to migrate the EnterWorks Data Model from one EnterWorks server to another, for example, from Development to QA or QA to Production, the following procedure must be performed.
The types of migrations and when they need to be performed are described in the table below:
Migration |
When Performed |
EnterWorks Data Model Migration |
|
Repository Migration |
|
Update Snapshot Table Views |
|
Restart of EnterWorks Services |
|
The EnterWorks Data Model Migration function is performed in the Enable Classic UI. Perform the following steps to migrate the EnterWorks data model from one EnterWorks server to another.
NOTE: Before performing these steps, be sure there is a backup of the target Enable database in case migration failures necessitate restoring the database from the backup.
- Log in to the source Enable (e.g., QA) Classic UI as a system administrator.
- Click on the Migration option on the feature bar and select Migrate Out function. The Migrate Objects Out page appears.
- Enter the name for the Migration file in the Zip and Specification file name fields. The actual file name will include a time-based number to ensure uniqueness.
- Optionally select an existing Migration Specification file. This will pre-select the objects to be migrated.
- Click Next. The Select Objects to Migrate page appears.
- Click the checkbox next to any Profile in the Profiles section that has changes to be migrated. For example, if the character length of an attribute in the SKU Group repository has been increased, check the checkbox next to SKU Group.
- If any Association groups (including order) have been changed, click the Check link at the top of the Association Groups section.
- If any code set has been added or modified, click the checkbox next to that code set (or alternatively click the Check link at the top of the Code Set section).
- If any changes have been made to the hierarchies or taxonomies, check its checkbox in the Hierarchies or Taxonomy section.
- If any changes have been made to any transmission options, check its checkbox in the Transmission Options section.
- If any changes or additions have been made to any Attribute Security Filters, check its checkbox in the Attribute Security Filters section.
- If any changes or additions have been made to any Record Security Filters, check its checkbox in the Record Security Filters section.
- If any changes or additions have been made to any repositories, check its checkbox in the Repositories section.
- If any changes have been made to an Export/Publication/Syndication templates, check its checkbox in the Templates section.
- If any changes or additions have been made to any Template Folders, check its checkbox in the Template Folders section. If the sequence has been changed on the folders, click the Check link to check all repository folders.
- If any changes have been made to a Style Map, check its checkbox in the Style Maps section.
- If any changes have been made to Style Map Folders, check its checkbox in the Style Map Folders section.
- If any changes have been made to any import templates, check its checkbox in the Import Templates section.
- Click Migrate.
- Open the Job Monitor. The new migration job appears at the top of the list.
- Repeatedly click Refresh to monitor the progress of the migration, until the Status shows “Completed”.
- Copy the .zip and .msf files from the \Enterworks\shared\migration folder on the source system (e.g., QA) to the same location on the target system (e.g., PROD).
- Log into the target Enable (e.g., PROD) Classic UI as user system.
- Click on the Migration option on the feature bar and select Migrate In function. The Migrate Objects In page appears.
- Select the .zip and .msf files that were just copied to the migration folder and click Next. The Select Objects to Migrate page appears.
- Click the Overwrite All Check link. The checkboxes for all objects in the migration are checked.
- Click Migrate.
- Open the Job Monitor. The new migration job appears at the top of the list.
- Repeatedly click Refresh to monitor the progress of the migration, until the Status shows “Completed”.
- Click the Log File icon for the Migration Log for the Migrate In job in the Job Monitor page. A window containing the migration log file contents appears.
- Review the contents of the log to ensure the expected objects were migrated. If the errors are substantial and cannot be quickly remedied, abort the migration attempt by restoring the target Enable database from the backup.