Tool
WebCenter Content component inventory
Paste a WebCenter Content component listing and get it sorted into Oracle-shipped, Oracle-family, custom and unrecognized, with the notes that matter for 14c.
What this tells you
The component layer is where a WebCenter Content estate keeps its customizations, and it is the layer a 14c upgrade has to account for one component at a time. Paste the component listing and this sorts it into Oracle-shipped, Oracle-family, custom and not-recognized, counts each group, flags anything disabled, and attaches the notes that matter for upgrade planning. Nothing leaves the browser.
The listing
One name per line, optionally followed by a tab-separated path and enabled/disabled. A Components ResultSet from the registry .hda files also works.
How to read the result
Custom and not-recognized components are the upgrade work
Each one needs an owner, a purpose and a decision: carry it forward, rebuild it against the 14c services, or retire it. A reference-list match does not establish target-release availability or compatibility.“Oracle-family” is a naming pattern, not proof
Names that start with Oracle, WebCenter, AppAdapter and the like are usually Oracle’s, but a custom component can be named the same way. Confirm against the component’s manifest.Disabled is a decision, not an answer
A disabled component may be dormant, or may be switched off because it broke on the last patch. Find out which before it is either dropped or carried.The listing is the catalog, not the dependency map
Which components depend on which is not visible from names. Those questions need separate evidence from manifests, configuration, source and runtime behavior.
From a list to an evidence-based inventory
The browser tool classifies names and paths. A deeper review needs the exact releases, component manifests, configuration, dependencies, source availability and observed business use. Classification is a starting point, not a compatibility verdict.
Continue with the discovery readiness check and the upgrade validation checklist.
Questions
What can I paste?
Component names one per line, as shown in Component Manager; a tab-separated name, path and enabled/disabled state; or a Components ResultSet block from the component registry .hda files under the IntradocDir. Blank lines and comment lines starting with # are ignored, and duplicate names are collapsed.
What does “not recognized” mean?
That the name is not in the reference list of Oracle-shipped components and does not match an Oracle naming pattern or a custom path. It is not a verdict. Open the component’s .hda and manifest: the vendor, description and classpath settle whether it is Oracle, third-party or built in-house.
Does anything leave the browser?
No. The listing is parsed in the page and nothing is stored or transmitted. Use the copy or download controls to export it locally.
Can an engineer inspect the environment?
An Estate Review can scope deeper inspection for your releases and access constraints. Any installed collector needs a separate review of its package, compatibility, permissions, data handling and removal procedure. This page does not supply a verified installed edition.
Turn the result into the next question.
Describe what you need to understand from the tool. Keep raw inventories, credentials and customer information out of the inquiry; any evidence collection is agreed separately.