Migrating Data to an Oracle Content Management (OCM) Asset Repository (Doc ID 2920845.1)

Last updated on AUGUST 12, 2024

Applies to:

Purpose

 This document will provide a brief overview of the data migration options to OCM Asset Repositories from various sources, as well as how to engage support.

Scope

Limitations/Caveats

All migration options share the following characteristics:

• The Customer defines target data structures.
• None of the migration tools will interpret the architecture of a source system and automatically recreate an equivalent environment in OCM.
• Customers are required to redefine their solution leveraging the features of OCM, such as Repositories, Asset Types, Taxonomies, etc.  (this includes configuring the Asset Type to accept all of the file types - based on file extension- that will be migrated).
• Security must also be re-implemented using the OCM features of groups, roles, Repository security, and granular Taxonomy security.
• Prior to any migration, the Customer must define the target environment and provide the mapping from the source data to the target OCM environment.
• It is the Customer's responsibility to move the data to Object Storage.

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.