Migrating EnterWorks - EnterWorks - EnterWorks Process Exchange (EPX) - Precisely EnterWorks - 10.5

EnterWorks Classic Administration Guide

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks > EnterWorks
Precisely EnterWorks > EnterWorks Process Exchange (EPX)
Precisely EnterWorks
Version
10.5
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Classic Administration Guide
Topic type
Configuration
Administration
First publish date
2007

The EnterWorks migration feature allows for the transfer of the following data model components from one EnterWorks server to another:

  • Users and user groups.

  • Data sources.

  • Security filters. 

  • Transmission options.

  • File definitions.

  • Home configuration.

  • Server Properties.

  • Data model objects: such as Repositories, Code Sets, Profiles, etc.

For example, a common installation setup consists of three separate environments:  DEV, QA, and PROD.   The data model is developed in the DEV environment, tested in the QA environment, and put into production in the PROD environment.  The migration feature is designed to facilitate the transfer of initial data model components, plus all future changes and improvements, from DEV to QA, and ultimately to PROD.  Each data model component has an underlying unique identifier assigned to it, which ensures the correct migration of components even if their names have been changed.

For example, if we have an attribute called “User Desc” in the DEV environment that is migrated to QA and PROD as “User Desc”. Later, the attribute name is changed to “User Description” but all other qualities of the attribute remain the same. A second migration of the profile containing this attribute would successfully locate the “User Desc” attribute in the QA and PROD environments and update its name to be “User Description”.

The migration flow should always be from DEV to QA and then to PROD.  Development changes and enhancements should always be performed in DEV, migrated to QA, and then migrated to PROD.  Conforming to this protocol allows migration to properly locate the data model components to change.

Examples of reasons you may want to migrate data model components:

  • EnterWorks Data Model objects:

    • Code set definition changes.

    • Addition, modification (for example, character length, data type, etc.) or removal of attributes to any profiles.

    • Hierarchy or Taxonomy changes (for example, addition of new nodes).

    • Change to attribute order, group, or tab assignments.

  • Repository Migration:

    • Addition of attributes to the Snapshot Table.

    • Change of default values.

    • Change of assignment of Pop-Up controls and pages.

    • Change in Trigger or Promotion properties.

For a detailed description of when you should migrate data model components, which components should be migrated together, how migration of the data model fits in the EnterWorks deployment process, and how to migrate EPX, see Best Practices for EnterWorks Deployments and Migrations.