Inventory the connected system
Oracle documents Imaging’s connection to Content Server for storing and retrieving documents. Imaging applications define the document fields and security context; workflow connections can start downstream processes. Record the actual topology instead of inferring it from the IPM, Imaging or WebCenter product name.
Include application definitions, repository and workflow connections, document identifiers, viewer behavior, custom integrations and the business applications that open images. Recognition and capture are separate capabilities and may use different products or manual steps.
Compare the forward paths
| Path | Scope to establish |
|---|---|
| Supported product upgrade | Source release, required intermediate steps, target compatibility and application acceptance |
| Hosting or storage change | Supported infrastructure, file-store choice, data consistency, recovery and performance |
| Processing replacement with retained archive | New intake/workflow interfaces plus ongoing historical access and archive operations |
| Repository replacement | Document and metadata mapping, permissions, records controls, links and history |
Use the WebCenter upgrade guide for product planning. A hosting move does not extend the 12c lifecycle dates shown in the support table.
Make storage a separate architecture decision
Oracle’s File Store Provider guidance documents storage options, including explicit OCI Object Storage configuration. Do not assume an archive storage tier supports immediate application retrieval or that file count alone determines the right design.
Confirm supported storage rules, retrieval latency, connectivity, recovery and the migration method for existing content. Rehearse change capture and reconciliation as described in the repository migration plan.
Prove the capabilities that must remain
- Open the correct document from each required business-record context.
- Verify application fields, revisions, searches and permitted user actions.
- Test denied access, including direct repository access where applicable.
- Reconcile required historical documents and supporting evidence.
- Validate configured retention and hold behavior with its owner.
- Exercise workflow handoffs and error handling without production side effects.
First assess whether existing SOA work can finish before cutover. Handle active instances explicitly if required and reconcile unfinished ERP invoices separately.
The records migration guide covers controls beyond file storage. ECMWorks can help inventory the Imaging dependencies and define acceptance evidence before a source component is retired.