Components for a FileNet Content Manager production deployment

You can install FileNet® Content Manager in a production deployment. Components from the foundation pattern are also automatically installed.

You can install the following capabilities with the deployment script or the Form View in the OpenShift® Container Platform (OCP) console. The templates that are used for the installation can be found in the cert-kubernetes/descriptors/patterns folder. For more information about downloading cert-kubernetes, see Preparing a client to connect to the cluster.

Prepare all the components before you install a deployment. Preparation might include creating databases, users and groups (LDAP), secrets, and other types of storage.

FNCM pattern visual
Table 1. FileNet Content Manager components
Components Capability or pattern Installed
Content Search Services (CSS) FileNet Content Manager Optional
Content Management Interoperability (CMIS) FileNet Content Manager Optional
Content Collector for SAP (ICC4SAP) FileNet Content Manager Optional
Enterprise Records (IER) FileNet Content Manager Optional
Task Manager (TM) FileNet Content Manager Optional
Business Automation Insights (BAI) Foundation Optional
Content Platform Engine (CPE) FileNet Content Manager Always
Content Services GraphQL FileNet Content Manager Always
Navigator (BAN) Foundation Always
Resource Registry (RR) Foundation Always
Default foundational services, which include
  • Platform UI (or Zen UI)
  • Identity Management (IM)
  • Common Web UI Service
  • License Service
  • Certificate Manager (installed if RH cert-manager is not installed)
 Foundation Always
  • Flink
  • Kafka
  • OpenSearch
 Foundation If Business Automation Insights is a selected option.