OpenMigrate's Newest Features

Learn about the newest features in OpenMigrate, including...

Centera Migration Target (v1.2)

EMC Centera is a high-performance content addressed storage (CAS) solution.  Documentum Content Server includes a plug-in to utilize a Centera device as a second-tier content store, including the ability to migrate from a traditional file store.  However, there have been reported stability and performance issues with the out-of-the-box Documentum to Centera migration tools, including poor performance and, in some cases, no reliable way to migrate content.

TSG is enhancing OpenMigrate to support high-performance, multi-threaded migration to move content from a standard Documentum file store to an EMC Centera device.  Like the Documentum plug-in, It leverages the Centera SDK; but the OpenMigrate Centera Target adapter's key difference is that it is optimized solely for migration.  The OpenMigrate core engine already provides the necessary auditing and tracking of migration errors; and its multi-threaded approach is a perfect fit for Centera's architecture.

JDBC Migration Source and Target Adapters (v1.2)

Historically, OpenMigrate has handled Migration Sources in two ways: by directly coding an adapter (e.g., Documentum) or by using a "2-phased" approach (export from the source system to a file system, then import using the File System Source adapter).  TSG is enhancing OpenMigrate with the ability to directly load content's metadata from any JDBC data source (via the Java Hibernate API), and loading the underlying content via configurable and pluggable "Content Readers" (e.g., file system or BLOB).  This expands its horizons considerably, adding the ability to migrate directly from legacy FileNet or Hummingbird repositories without having to first stage the data.

Documentum Direct File Store Content Reader (v1.2)

Normally, OpenMigrate's Source adapters "store" the underlying content in each Migration Node (either in-memory or, if the size exceeds a configurable threshold, in a temporary file).  This solution ensures that the core Migration Engine does not need to know the details of either the Source or the Target; nor do they need any information on each other.  But there are cases where this approach is not acceptable: first, where high performance is an absolute must; and second, where individual content files are quite large.  The Documentum Direct File Store Content Reader, instead of streaming the content via a DFC call, will instead read the actual content file directly within the underlying file system.  The target, regardless of type, will be able to load this file directly.

Bulk Load Interface (v1.1)

OpenMigrate provides a highly customizable user interface which enables the user to easily manage documents and import them into a variety of targets.  The interface is built on top of the Spring framework making it extremely easily maintainable, customizable, and configurable.

Interface Components

  • Batch Creation - A batch consists of a group of documents to be migrated.  Users can establish a unique name for the batch and add multiple documents to the batch, allowing efficient one-time migrations. Documents can be uploaded from a file system or by querying a source docbase. Additional migration sources are easily added via the extensible classes.
  • Document Setup - The document setup component allows the user to select from a configurable set of options in order to identify a certain schema. A schema defines all the source and mapping properties for the migration.  Schemas are loaded from a highly configurable schema file.  This allows administrators to tailor OpenMigrate to their particular needs.  

  • View Document Details - This component allows the user to select and enter properties for each document in a batch. Included in the schema's configurable properties are cascading properties, related groups, DQL populated selectable values, and XML populated selected values.  Additional sources, such as LDAP, can easily be added.  A workflow is the operation of relocating documents through a work process. It must be selected in addition to the performers assigned to that workflow. Administrators can program custom rules to allow users to specify workflows, create ACLs, and set target attributes.

  • Copy Document Properties - This component allows the user to copy properties previously set for one document to other documents in the same batch.  Copying document properties saves the user from setting the same properties to other documents in the batch.

 

  • Dynamic Filter - The dynamic filter allows the user to sort batches based on date and status.  Documents within a batch can be sorted based on type, verify status, import status, and workflow.  Filtering generates greater readability for the users.

Services

  • Batch Source - The batch source connects the web interface with the OpenMigrate back end code.  
  • Schema Configuration - The schema configuration provides a way to configure properties set for each batch to be imported. It controls multiple input types on the document details component.  Hierarchical configuration structure eliminates configuration redundancies with user input.
  • Configuration Validation - Configuration validation is a value added feature that validates schema configurations.  This enables the administrator to more easily create properly configured schemas and it includes a detailed description of any potential problems that may exist.
  • Document Validation - This feature of OpenMigrate validates user input based on the current configuration. Custom validation for each document can be created based on applicable business needs. For example, date formats and required values can be validated.
  • Document Property Population - Document properties can be automatically populated, thus reducing user input when required.
  • Batch Import - Batch import enables the user to import batches to a file system or Documentum. This feature is XML structurally based and associates metadata with content files. It also provides the ability to set document properties and version existing documents in the docbase.

Case Study

  • Problem: A client was in need of a solution to reduce the amount of user input for document migrations, simplify and streamline imports, and more efficiently migrate documents into a customized version of Documentum.
  • Solution: TSG developed and implemented a customized web interface and document migration solution by using OpenMigrate 1.1.  OpenMigrate 1.1 automatically populates only the fields necessary for migrations, thus reducing the amount of user interaction.  Additionally, input redundancy is eliminated with the copy document properties feature and validation ensures that user input is accurate.  Since migrations are generally an ongoing process, OpenMigrate 1.1 provided the client with an effective way to continually and consistently migrate documents from a file system to their customized version of Documentum.