Agree acceptance before the window
List the business functions, platform dependencies and recovery objectives the target must satisfy. Give each a test, expected result, evidence location and owner. Record which checks require a real integration and which use a controlled substitute.
Use Oracle’s WebCenter upgrade documentation for the applicable execution procedure. This checklist defines additional acceptance work; it does not replace required product checks.
Check prerequisites and configuration
Confirm the running product versions and patches, JDK, operating system, database and topology against the applicable certifications and system requirements. Verify the actual runtime rather than only installed binaries.
Review database connectivity, required schema state, character-set requirements and representative multilingual metadata. Confirm storage paths, permissions, capacity, logging and monitoring. A configuration difference needs investigation; it does not justify assuming a particular corruption symptom.
Reconcile repository content
Use the agreed manifest to verify items, revisions, files, metadata and exceptions. Test representative originals and renditions, folders, search and business-record links. Search counts alone do not prove completeness or file integrity.
Where indexing or conversion is asynchronous, define when it must complete and how a backlog is reported. Include configured records and hold controls with their owners.
Exercise extensions and access controls
Inventory source components and custom deployments, confirm the intended target configuration and test the behavior each supplies. An enabled component is not proof of a working feature. A browser list analyzer can help organize the inventory but cannot inspect the running server.
Test authentication and role mapping, then allowed and denied actions. Include direct access to protected resources; a hidden menu is not a complete authorization boundary. Verify credential and trust configuration without exposing secrets in test evidence.
Run the business and operations tests
| Area | Representative checks |
|---|---|
| Content lifecycle | Check-in, retrieval, search, metadata update and revision history |
| Integrations | Capture commits, document links, workflow handoffs and ERP results |
| Exceptions | Invalid input, denied access, timeout, retry and duplicate prevention |
| Operations | Monitoring, scheduled jobs, restart and agreed availability scenario |
| Recovery | Restore boundary, decision point and reconciliation of external effects |
For invoice workflow, first decide whether existing SOA work can finish before cutover. Include active-instance checks only if that scope is required, and reconcile open ERP invoices independently.
Record the release decision
Document results, unresolved exceptions and the authorized acceptance decision. Basic smoke tests do not replace the full business and recovery criteria. Keep the source available according to the agreed recovery and retention plan until those obligations are resolved.
The isolated rehearsal guide provides the environment boundary, and invoice process validation supplies deeper AP checks.