Tool
WebCenter Content component inventory
Paste a WebCenter Content component listing and get it sorted into Oracle-shipped, Oracle-family, custom and unrecognised, with the notes that matter for 14c.
What this tells you
The component layer is where a WebCenter Content estate keeps its customisations, 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-recognised, 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 its path and enabled/disabled. A Components ResultSet from the registry .hda files also works.
How to read the result
Custom and not-recognised 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. Oracle-shipped components move with the product.“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. The installed edition below reads the dependencies, configuration deltas and custom code directly.
The installed edition
A native WebCenter Content component, installed through Component Manager like any other, that reads the environment and produces a written report. It runs inside the environment with read-only data collection and makes no outbound calls; the report stays with you. It covers six dimensions:
Complete catalog
Every installed component with name, version, install path and install date, whether Oracle-shipped, third-party or built in-house.
Dependency map
Which components depend on which, so a change to one shows its cascading effect on upgrade sequencing and retirement decisions.
Last-modified analysis
When each component was last touched, to surface dormant customisations and components untouched through several patch cycles.
Configuration deltas
Per component, the configuration that differs from Oracle defaults: the customisation surface an upgrade has to carry.
Custom code detection
Custom Java services, custom iDoc Script, custom resources and custom database objects, mapped to the business function each implements.
14c impact rating
Per-component rating of how cleanly it moves to the 14c release, and which ones need deliberate handling.
For the wider six-dimension view of the estate (workflows, storage, security, customisations), see the estate inspector. For the upgrade itself, see the out-of-place 12c to 14c upgrade and the validation checklist.
Questions
What can I paste?
Component names one per line, as shown in Component Manager; a line with the name followed by its 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 recognised” 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 button to take the sorted inventory into a spreadsheet.
Is there a version that reads the environment directly?
Yes. The installed edition is a native WebCenter Content component, installed through Component Manager, that reads the environment and produces a report: catalog, dependencies, last-modified dates, configuration deltas from Oracle defaults, custom code and a 14c impact rating per component. It runs inside the environment with read-only collection and makes no outbound calls. It is available by request; use the contact form and mention the inventory.
Put the estate in front of an engineer.
Tell us the versions, the components and the integrations. You get a straight answer on what the estate needs, what it does not, and what order to do it in.