Skip to content
ECMWorks

Tool

WebCenter Content estate inspector

A discovery readiness check across six dimensions of a WebCenter Content estate, and the installed component that reports on them. Early access by request.

What this tells you

Before December 2026 every WebCenter Content estate gets the same three questions from its CIO, its CFO and its Oracle account team: what is running, what changes, and which way forward. Most estates have grown over a decade while the documentation thinned, so the honest first step is discovery. The check below scores how much of the estate is already written down, across the six dimensions the installed inspector reports on, and tells you where to start.

Discovery readiness check

01Installed components. Is there a current list of every installed component, with versions, dependencies and who owns each?
02Workflow definitions. Are the workflow definitions inventoried, with unused ones identified and the approval routing understood?
03Storage and archive. Do you know storage use by file system, database and object storage, growth by content type, and which content could be retired?
04Security model. Are the custom security groups, roles and account hierarchy documented, and has the access pattern been reviewed for the last audit?
05Customisations. Are ADF customisations, custom content profiles, custom services, validation rules and search-result templates all known and written down?
06Forward-path mapping. Has each finding been mapped to a forward path (move to OCI as-is, upgrade to 14c, re-platform, hybrid) with a sequence and an owner?

Reading

Answer all six. 0 of 6 answered.

How to read the result

  1. The score is a documentation score, not a health score

    An estate can be well documented and still need a great deal of work. The reading says how much discovery stands between you and a defensible decision, nothing more.

  2. Unknown dimensions come first

    They are where the surprises live. Components and customisations are usually the two that decide the size of an upgrade; security and storage decide the audit story.

  3. Forward-path mapping is the last dimension for a reason

    It cannot be done until the other five are known. If it is the only unknown, the estate is ready for the decision guide.

The decision guide · The component inventory

The installed inspector

A native WebCenter Content component that produces a readiness report for the estate, aligned to the 12c support decision. It installs through Component Manager, the same mechanism as any other component, in a few minutes; runs read-only inside the environment, typically five to fifteen minutes depending on size; and produces a report you can hand to the CIO, the CFO and the Oracle account team. It reports on:

  • Installed components

    Catalogs every component (Oracle-shipped, third-party, custom) with versions, dependencies and last-modified dates.

  • Workflow definitions

    Inventories every workflow definition, identifies definitions with no recent activity, and surfaces approval-routing complexity that will be hard to carry forward.

  • Storage and archive

    Storage utilisation across file system, database and object storage; document growth rate by content type; retirement candidates; Managed Attachments link health.

  • Security model

    Custom security groups, roles, account hierarchy and access-pattern analysis, laid out for SOX, HIPAA and FedRAMP audit cycles as well as for upgrade planning.

  • Customisations

    Surfaces ADF customisations, custom content profiles, custom services, custom validation rules and custom search-result templates: the layers that complicate an upgrade.

  • Forward-path mapping

    Maps each finding to what it means for the four forward paths, so the report reads as a decision document, not only an inventory.

Questions

What is the installed inspector?

A native WebCenter Content component, installed through Component Manager, that reads the environment and produces a written readiness report across six dimensions: components, workflows, storage, security, customisations and forward-path mapping. It uses documented WebCenter Content services, writes to no base tables, collects read-only, and makes no outbound calls; the report stays with you.

Which WebCenter Content releases does it support?

WebCenter Content 11g, 12c and 14c. The component detects the installed release and adapts what it collects.

Why is it by request rather than a download?

Because the first installs are walked through with an engineer, who confirms the release and the environment shape before the component goes in, and because the report is more useful when its output is read with someone who knows the estate. Broader availability follows the first cohort.

Does the readiness check on this page send anything?

No. The six answers are scored in the browser (two points for documented, one for partly, none for unknown) and nothing is stored or transmitted.

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.

Talk to an engineer