Preparing to install IBM FileNet Content Manager

Before you use the configuration container or command line to deploy your applications, you must prepare your environment. These preparation items include creating or designating LDAP users and groups, preparing databases for the application data and managed content, and configuring storage for the applications in IBM Cloud Private.

About this task

When you run the configuration tool that is provided by the IBM Business Automation Configuration Container, you supply numerous values for the required configuration parameters that define your environment. Before you start the process of deploying your containers with the configuration tool, ensure that you take the appropriate steps to prepare your environment. These prerequisite steps provide details that help you collect your input for the configuration tool.

Keep in mind the following planning considerations:
Planning for SSO
You can deploy IBM Content Navigator to work in a single sign-on (SSO) environment. The enablement for this deployment type is included in a separate container. If you want to use SSO with Content Navigator, use the SSO image when you upload your containers, for example, navigator-sso:3.0.x.

SAML SSO is supported.

Planning for autoscaling
You can enable autoscaling for your deployment by using the autoscale settings in the configuration tool. Autoscaling can increase or reduce the number of active pods to achieve a target average of CPU usage. You can specify the following parameters:
  • Enable
  • Maximum scale
  • Minimum scale
  • CPU percentage
Planning for additional Content Search Services deployments
Some environments require multiple Content Search Services deployments. To deploy multiple Content Search Services instances, specify a unique release name and service name, and a new set of persistent volumes and persistent volume claims. You can reuse the same persistent volume for the indexstore if you want to have multiple Content Search Services deployments that access the same set of index collections. However, it is recommended that the other persistent volumes be unique.

For a full list and more information about the parameters that you provide for the configuration tool, see Content services parameters.