How-To: Migrating Content to Vignette Version 7 (Part 3)

This is the third and final article in our series on migrating content from a previous version of Vignette to Vignette V7. The first article in the series painted the broad overview and in the last article we talked in detail about the Content Analysis part of the process. Now, we continue by digging into the final planning phase: Defining the Migration Approach.

Migration Process — Define the Approach

This step in the content migration process defines an overall approach for content transformation and migration.

Diagram: Content Migration Approach (click to enlarge)

Process Flow

1. Vignette content is analyzed. Content analysis provides type of content that can be migrated by automation using data mapping between V6 - V7 and data transformation logic.
2. Depending on content analysis output, content is selected for either automated migration process or manual migration process.
3. For manual migration, administrator uses Vignette CMA to create content instances in the V7 content repository.
4. Automated migration process fetches content from V6 content repository on production stage, applies transformation logic and inserts content instances into V7 content repository on management stage.
5. Once content is committed in the V7, Vignette content creation workflow triggers.
6. Migrated content is reviewed and approved through Vignette workflow process.
7. Manual content checks for data quality and data integrity should be carried out at this stage.
8. Approved content then goes through Vignette publish workflow process and get published on the production stage.
9. Content is displayed on the Website using Vignette content delivery process.

Automated Content Migration Process

This process defines an approach for automated content migration. Content Analysis step has identified content that can be migrated by automation and also defined mapping between V7 and V6 content data. Now, same content data will be passed through this process for an automated migration. Content that can not be migrated automatically need to be carried out manually.

Automated migration can be achieved in two ways:

1. Using Vignette content management APIs
2. Using VBIS adapter process

Vignette Content Management APIs

Vignette provides content management APIs to manage content instances. Using this APIs XML code of objects can be imported and exported to and from the Vignette content suite.

Following diagram gives a broad overview of the approach for content migration using V7 Content Management APIs.

Diagram: Automated Migration Approach 1 - V7 Content Management APIs

V7 expects XML objects of content instances for import and export. To import content instance of a particular Content Type into V7, one needs to get an exact XML structure of the Content Type.

There are two ways to get XML structure of Content Type in V7:

1. Export XML object of existing Content Type from V7 using APIs.
2. Get XML object of Content Type from ‘content type definition’ in Vignette CMA console.

Pure Java programs can be written to handle the migration process. Java program connects to the V6 content database on the management stage using JDBC driver. Content analysis step has identified content to be migrated from V6 system. Identified content is fetched from V6 database.

How-To: Migrating Content to Vignette Version 7 (Part 3)

This is the third and final article in our series on migrating content from a previous version of Vignette to Vignette V7. The first article in the series painted the broad overview and in the last article we talked in detail about the Content Analysis part of the process. Now, we continue by digging into the final planning phase: Defining the Migration Approach.

Are you hiring?    Post your job today ($45 for 45 days)!