How to manage object ids cleverly during content migrations

When dealing with content migrations, broken links are often an issue. Broken links might occur during non-inplace system migrations, e.g. with fme migration-center. Very often, the content files residing in the repositories contain HTTP links which point to other documents of the same (or other) repositories. Changes of the object IDs, e.g. caused by the document migration will break those HTTP links. As a result connections between documents are broken after the migration process.

fme migration experts have developed best practice methods and various solutions which can be applied to different system architectures in order to fix broken links after Documentum migrations:

DIFFERENT SOLUTION APPROACHES

When the URL consists of the physical host name
Assign the old physical host name additionally to the new hardware (host) and define a new virtual host in the JSP container handling the requests targeted to the old host name (Figure 1 ) or handle all requests to the old host names by a dedicated server (host). This dedicated server redirects the requests to the new web server host (Figure 2).

          Fig. 2 Redirections handled inside the same host
Fig. 1 As-is state                            Fig. 2 Redirections handled in the same host

When the URL consists of a DNS alias (instead of a physical host name)
This DNS alias is switched from the old host to the new host (Figure 3). The DRL / link component inside the appropriate web application is subject to being updated. This new DRL / link component is able to identify »old« object IDs either by the repository ID portion of the object ID (the repository ID is part of the object ID) or by querying the Documentum repository for the old object ID.

Fig 3 Redirections handled by a dedicated server

Fig. 3 Redirections handled by a dedicated server

HANDLING OF COMPLEX CASES

When a single cabinet is moved from one repository into another
The redirection logic have to be handled by specific code. In case the object ID has not been found within the source repository, specific target repositories are queried for the old object ID.

A lot of complex cases and the cases are not homogenous
A centralized Oracle table could hold all information regarding old object IDs mapped to new object IDs. This Oracle table might be queried by the redirector code to obtain the new object ID. By the repository ID portion of the object IDs, the redirector might also be able to identify the repository holding the corresponding object.

fme now incorporates 17 years of project experience in the field of migrating applications, content and data. Our migration experts have developed best practice methods and various solutions which can be applied to different system  architectures in order to fix broken links. If you need further Information please contact us – we welcome any challenge!

For detailed information see our technical white paper

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk