System requirements

Edit online
All the containers are based on Red Hat Universal Base Images (UBI), and are Red Hat and IBM certified. To use the FileNet Content Manager images, the administrator must make sure that the target cluster has the capacity for all of the components that you plan to install.

For each stage in your operations (a minimum of three stages is expected "development, preproduction, and production"), you must allocate a cluster of nodes before you install the operator. Development, preproduction, and production are stages that are best run on different compute nodes. To achieve resource isolation, each namespace is a virtual cluster within the physical cluster and a FileNet Content Manager deployment is scoped to a single namespace. High-level resource objects are scoped within namespaces. Low-level resources, such as nodes and persistent volumes, are not in namespaces.

The Detailed system requirements page provides a cluster requirements guideline for FileNet® Content Manager.

The minimum cluster configuration and physical resources that are needed to run the deployment include the following elements:

  • Hardware architecture: Intel (amd64 or x86_64 the 64-bit edition for Linux® x86) on all platforms.
  • Node counts: Dual compute nodes for nonproduction and production clusters. A minimum of three nodes is needed for medium and large production environments and large test environments. Any cluster configuration needs to adapt to the size of the projects and the workload that is expected.
A cluster where you want to install all of the capabilities needs as a minimum:
  • Master (3 nodes): 4 vCPU and 8 Gi memory on each node.
  • Worker (8 nodes): 16 vCPU and 32 Gi memory on each node.

Based on your cluster requirement, you can pick a deployment profile (sc_deployment_profile_size) and enable it during installation. FileNet Content Manager provides small, medium, and large deployment profiles. You can set the profile during installation, in an update, and during an upgrade.

The default profile is small. Before you install, you can change the profile to medium or large. You can scale up or down a profile anytime after installation.

The following table describes each deployment profile.

Table 1. Deployment profiles and estimated workloads
Profile Description Scaling (per 8-hour day) Minimum number of worker nodes
Small (no HA) For environments that are used by 10 developers and 25 users. For environments that are used by a single department with a few users; useful for application development.
  • Ingests 10,000 documents
  • Processes 5000 transactions
  • Supports failover
 8
Medium For environments that are used by 20 developers and 125 users. For environments that are used by a single department and by limited users.
  • Ingests 100,000 documents
  • Processes 25,000 transactions
  • Supports HA and failover
  • Provides at least two replicas of most services, if configuring failover
 16
Large For environments that are used by 50 developers and 625 users. For environments that are shared by multiple departments and users.
  • Ingests 1,000,000 documents
  • Processes 125,000 transactions
  • Supports HA and failover
  • Provides at least two replicas of most services, if configuring failover
 32

You can use custom resource templates to update the hardware requirements of the services that you want to install.

Attention: The values in the hardware requirements tables were derived under specific operating and environment conditions. The information is accurate under the given conditions, but results that are obtained in your operating environments might vary significantly. Therefore, IBM cannot provide any representations, assurances, guarantees, or warranties regarding the performance of the profiles in your environment.

Small profile hardware requirements

  • Table 2 Navigator default requirements for a small profile
  • Table 3 FileNet Content Manager default requirements for a small profile
Table 2. Navigator default requirements for a small profile
Component CPU Request (m) CPU Limit (m) Memory Request (Mi) Memory Limit (Mi) Number of replicas Pods are licensed for production/nonproduction
Navigator 1000 1000 3072 3072 1 No
Table 3. FileNet Content Manager default requirements for a small profile
Component CPU Request (m) CPU Limit (m) Memory Request (Mi) Memory Limit (Mi) Number of replicas Pods are licensed for production/nonproduction
CPE 1000 1000 3072 3072 1 Yes
CSS 1000 1000 4096 4096 1 Yes
CMIS 500 1000 1536 1536 1 No
GraphQL 500 1000 1536 1536 1 No
External Share 500 1000 1536 1536 1 No
Task Manager 500 1000 1536 1536 1 No
Note: Not all containers are used in every workload. If a feature like the Content Services GraphQL API is not used, that container requires less resources or is optionally not deployed.

In high-volume indexing scenarios, where ingested docs are full-text indexed, the CSS utilization can exceed the CPE utilization. In some cases, this might be 3 - 5 times larger.

For optional processing such as thumbnail generation or text filtering, at least 1 GB of native memory is required by the CPE for each. If both types of processing are expected, add at least 2 GB to the memory requests/limits for the CPE.

With the processing of content, resources required increase with the complexity and size of the content. Increase both memory and CPU for the CPE and CSS services to reflect the type and size of documents in your system. Resource requirements might also increase over time as the amount of data in the system grows.

Medium profile hardware requirements

  • Table 4 Navigator default requirements for a medium profile
  • Table 5 FileNet Content Manager default requirements for a medium profile
Table 4. Navigator default requirements for a medium profile
Component CPU Request (m) CPU Limit (m) Memory Request (Mi) Memory Limit (Mi) Number of replicas Pods are licensed for production/nonproduction
Navigator 2000 3000 4096 4096 2 No
Table 5. FileNet Content Manager default requirements for a medium profile
Component CPU Request (m) CPU Limit (m) Memory Request (Mi) Memory Limit (Mi) Number of replicas Pods are licensed for production/nonproduction
CPE 1500 2000 3072 3072 2 Yes
CSS 1000 2000 8192 8192 2 Yes
CMIS 500 1000 1536 1536 2 No
GraphQL 500 2000 3072 3072 3 No
External Share 500 1000 1536 1536 2 No
Task Manager 500 1000 1536 1536 2 No
Note: Not all containers are used in every workload. If a feature like the Content Services GraphQL API is not used, that container requires less resources or is optionally not deployed.

In high-volume indexing scenarios, where ingested docs are full-text indexed, the CSS utilization can exceed the CPE utilization. In some cases, this might be 3 - 5 times larger.

For optional processing such as thumbnail generation or text filtering, at least 1 GB of native memory is required by the CPE for each. If both types of processing are expected, add at least 2 GB to the memory requests/limits for the Content Platform Engine (CPE).

With the processing of content, resource requirements increase with the complexity and size of the content. Increase both memory and CPU for the CPE and CSS services to reflect the type and size of documents in your system. Resource requirements might also increase over time as the amount of data in the system grows.

Large profile hardware requirements

  • Table 6 Navigator default requirements for a large profile
  • Table 7 FileNet Content Manager default requirements for a large profile
Table 6. Navigator default requirements for a large profile
Component CPU Request (m) CPU Limit (m) Memory Request (Mi) Memory Limit (Mi) Number of replicas Pods are licensed for production/nonproduction
Navigator 2000 4000 4096 4096 4 No
Table 7. FileNet Content Manager default requirements for a large profile
Component CPU Request (m) CPU Limit (m) Memory Request (Mi) Memory Limit (Mi) Number of replicas Pods are licensed for production/nonproduction
CPE 3000 4000 8192 8192 2 Yes
CSS 2000 4000 8192 8192 2 Yes
CMIS 500 1000 1536 1536 2 No
GraphQL 1000 2000 3072 3072 6 No
External Share 500 1000 1536 1536 2 No
Task Manager 500 1000 1536 1536 2 No
Note: Not all containers are used in every workload. If a feature like the Content Services GraphQL API is not used, that container requires less resources or is optionally not deployed.

In high-volume indexing scenarios, where ingested docs are full-text indexed, the CSS utilization can exceed the CPE utilization. In some cases, this might be 3 - 5 times larger.

For optional processing such as thumbnail generation or text filtering, at least 1 GB of native memory is required by the CPE for each. If both types of processing are expected, add at least 2 GB to the memory requests/limits for the CPE.

With the processing of content, resources required increase with the complexity and size of the content. Increase both memory and CPU for the CPE and CSS services to reflect the type and size of documents in your system. Resource requirements might also increase over time as the amount of data in the system grows.