Dotsphere Migration Framework : Approach Paper
Electronic Document Migration refers to the process of migrating documents stored in one content repository to another content repository. The migration is often executed when the existing version of the content repository is upgraded to a new version or a content repository from a new vendor is installed. Often problems arise when the new repository is from a new vendor or a new hardware platform. To address this problem, AWPL has built the Dotsphere Migration Framework for the needs of an Electronic Document Migration.
The Migration Framework is a collection of pre-built code assets that allows Automated Workflow (AWPL) to conduct migrations in a much more cost effective manner for customers. By using the Migration Framework one could see substantial cost savings.
The Migration Framework consists of modules called “ERs”, so named because each module ends with the phonetic sound of ER. They are as follows:
Not all of the ERs are used in every circumstance. For example, the inflator is typically only used when migrating COLD data as it is usually compressed. The components that are used will be customized during the development phase of the engagement. They need to be adapted to work with the customer’s specific environment and circumstances.
Customization takes many forms, for example, different repositories have variable table structures, can be customized upon implementation, and certainly field names and values are unique in each and every circumstance. Metadata may also reside in many locations within the application being migrated, it can and usually has been modified, and frequently is located in completely different applications. Most repositories handle images and annotations differently. Not all content is managed the same. For these reasons, and many more, customization is always required.
The audit capability is the most important component of the Migration Framework. When you are moving many millions of items with potentially many more millions of associated attributes from one system to another there are a multitude of opportunities for failure. It is pretty safe to say that there will be some form of failure in your migration. There nearly always is. Bad media and or data structures are the leading problems. The issue isn’t that the problems exist. The issue is that they must be properly identified so that an appropriate course of action is taken. Additionally the audit capabilities provide you the information you need to insure the migration was successful.
When development and testing are completed the customer will have a software asset that is specifically built for their migration needs. They will be able to run this asset as needed in order to perform the migration. The customer has the right to utilize this customized version of the framework for themselves only. Decompiling, customizing, and or using components that were not necessary for the migration AWPL was engaged for is not allowed.
The Migration Framework is a cost effective solution to your migrations needs and is sold as a software asset in conjunction with a services agreement with AWPL.
Other Products – Dotsphere Case Manager | Dotsphere Capture | Pencil