Build the component inventory
Record the exact product, release, patches, topology, database and runtime for every dependency. Include reporting, search, directory services and integrations outside the WebCenter domain. Product names alone are not enough to establish a supported upgrade path.
Use the right guide for each component
| Component | Planning distinction | Next guide |
|---|---|---|
| WebLogic and Infrastructure | A standalone application domain differs from a domain with Fusion Middleware product schemas | WebLogic planning |
| WebCenter Content and Imaging | Repository, domain and connected workflow boundaries must remain consistent | WebCenter upgrade |
| SOA and BPM | Follow the deployed topology and decide workflow closeout or required active-instance handling | SOA planning |
| Forms | The guide lists 12.2.1.4 and 12.2.1.19; Reports has separate considerations | Forms planning |
| ODI | The 14.1.2 guide lists 12.2.1.4 and different agent topologies | ODI planning |
| Identity products | OAM, OIG, OUD and OID need their own procedures; standalone OUD is not a WebLogic domain | Identity planning |
| WFR | Separate build and Windows runtime; verify Capture interoperability | WFR assessment |
Oracle’s upgrade documentation index is the starting point for execution references. The Forms, ODI and OUD guides illustrate why starting points cannot be copied between products.
Sequence from dependencies
Identify shared domains, schemas, files, identity services and external interfaces. Confirm compatibility during any intermediate state. Choose the execution order from the applicable procedures and recovery design, then rehearse it on isolated copies.
A new Oracle home does not by itself preserve old schema or domain state. An integration that passes a connection test does not prove the business process. Include application acceptance, data reconciliation and recovery in the same plan.
Give adjacent products their own decision
Analytics, search, legacy capture and third-party extensions may have different release families or replacement routes. Establish those from their exact product documentation and entitlements. An absent 14c label is not by itself proof that only a full replacement is possible.
Use the support dates tool for applicable lifecycle entries and the Fusion Middleware overview for program planning.