Begin with the workload
A sizing plan should name its inputs and assumptions. Capture representative document sizes and formats, daily volume and peak arrival rate, backfile volume, concurrent users, search patterns, rendition requests and retention rules. Measure bursts and recovery backlogs as well as average demand.
Oracle’s system requirements distinguish installation requirements from production memory planning. Check the exact product, operating system, JDK and database certifications. Minimum installation resources do not predict business throughput.
Separate the deployed roles
| Role, where deployed | Workload to measure |
|---|---|
| Web and access tier | Concurrent requests, connection behavior and identity dependencies |
| Content Server and user interface | Check-ins, metadata operations, downloads, search and authorization |
| Inbound Refinery | Conversion time by file type, queue depth and temporary working space |
| Enterprise Capture | Intake bursts, image processing and commit throughput |
| Forms Recognition | Recognition and verification demand under its separate Windows runtime |
| Database and search | Transaction volume, index size, query behavior and maintenance windows |
Some roles may share hosts; others need separation for supportability, capacity or availability. Count every process on a host before allocating memory. Check the WFR installation guide independently of the Content release.
Build the storage model
Account for originals, revisions, renditions, indexes, temporary processing files, logs, backups and recovery copies. Retention and legal holds can change the expected growth curve; the records owner must supply those requirements.
The File Store Provider documentation describes supported storage choices. A filesystem, database or configured OCI Object Storage option is an architecture decision, not a universal destination. Include latency, failure behavior, retrieval, backup and reconciliation in that decision.
State the planning horizon, measured growth, capacity headroom and the threshold that triggers expansion. An unexplained percentage or a default disk size is not a substitute for those inputs.
Size environments for their purpose
Development, test, training, performance and recovery environments need not have identical capacity. Record what each can prove. A reduced test environment may verify function but cannot establish production throughput or failover behavior.
For the proposed production topology, test peak ingestion alongside normal retrieval and processing. Include backlog recovery and the agreed failure scenario. Record queue depth, processing latency, resource use and the point at which the acceptance threshold is exceeded.
The sizing deliverable
A useful deliverable contains the workload baseline, certified product topology, resource allocation by role, storage growth model, availability assumptions, measured acceptance results and unresolved inputs. Keep forecast assumptions separate from observed results.
For an upgrade, connect this work to the isolated rehearsal. For a repository move, include the migration and reconciliation plan. ECMWorks can help define the measurements and review the resulting capacity proposal.