Migrating External Data to an Oracle Content Management (OCM) Documents
(Doc ID 3014599.1)
Last updated on APRIL 04, 2024
Applies to:
Oracle Content Management - Version 23.6.3 and laterInformation in this document applies to any platform.
Purpose
This document will provide a brief overview of the data migration option to OCM documents from various sources, as well as how to engage support.
NOTE: For bulk migrations to an OCM Asset Repository, please see KM Document Migrating Data to an Oracle Content Management (OCM) Asset Repository (Doc ID 2920845.1)
Scope
Limitations/Caveats
All migration options share the following characteristics:
- 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 by leveraging the features of OCM using Metadata Fields and sub-directories, etc.
- Security must also be re-implemented using the OCM features of groups and roles.
- Before 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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |