Vignette
Vignette revamped its Web Content Management technology with version V7 to adopt industry standards J2EE, XML and Web Services. While this move helped customers lower total cost of ownership by leveraging open standards and application server services, it posed new challenges in migrating existing sites running on earlier versions V5/V6. V7 introduced an entirely new architecture, making V6 implementations almost obsolete. Customers going for the V7 platform have to model, design and rebuild the site. Along with re-engineering the site, one of the most critical tasks in V7 migration is to rebuild the content into new V7 server from an old story server. As re-creating the whole site content is quite a tedious task, customers might wonder if there is any way out. This three-part series attempts to give insights into successful and efficient content migration by following a structured content migration process, using techniques for automation wherever possible.

Audience

The intended audience of this article includes: * Content Management Architects – those responsible for defining V7 content migration strategy in their organization. * Site development team – developers can refer to this document to understand content migration approach and provide implementation for the same. * People responsible for Vignette content management can refer to this article to understand content migration scope and activities involved, such as which data can be migrated with an automation tool, which data needs to be migrated manually, pre processing required before content migration, post processing after content migration.

Content Migration Process

Steps involved in the content migration process are: * Content Analysis * Defining Migration Approach * Content Migration using defined approach * Post-Migration Processing Content migration involves identifying and analyzing content that is to be migrated. Output from content analysis is used to define the migration approach for various types of content. This is applied to the content for actual migration from V6 to V7 system. Finally, migrated content is passed through the post processing activities to publish the content on the site. Output from each step serves as input to the next step with final goal to publish migrated content on the Website running V7.
vignette content migration process

Diagram: Content Migration Process – Steps These 4 steps describe content life cycle during migration as content traverses from one phase to the next. * Analyze Content – Content to be migrated is analyzed. Data points are created that are required for migration process. This step is part of the content migration development project and is carried out at the development site. * Define Migration Approach – Overall approach for migration is defined to migrate the content. This step is part of the content migration development project and is carried out at the development site. * Migration – After baseline migration approach, defined approach is followed for actual content migration. This step is carried out on the content at the production site. * Post-Migration Processing – Migrated content is processed for review, approval and publication. This step is necessary to check effectiveness of the content migration and take required actions for correction before migrated content goes live. This step is carried out at the production site. The first two steps, Content Analysis and Migration Approach, define and develop content migration strategy and will be discussed in detail in the next two installments of this series. The final two steps, Migration and Post-Migration Processing, are execution operations that must to be carried at the production site.

About the Author

Sandip Mane is a Sr. Technical Architect at Infosys Technologies Limited.