Pattern configuration

You can install software of the Cloud Pak for evaluation and production purposes by using Digital Business Automation (DBA) patterns. A pattern includes all the components that are needed to accomplish a specific set of cross-component functional tasks. The scripts and custom resource templates that are provided for the patterns reduce the number of steps you need to do to prepare your environment.

Table 1. Shared configuration parameters for patterns, optional components, and dynamic storage: spec.shared_configuration
Parameter name Description Default/Example values
sc_deployment_patterns You have "starter" and "production" patterns to choose from.
  • Automation Decision Services (decisions_ads)
  • Automation Document Processing (document_processing)
  • Automation Workstream Services starter (workstreams)

    Automation Workstream Services custom (workstreams)

  • Automation Workstream Services and Business Automation Workflow (workflow-workstreams)
  • Business Automation Application (application)
  • Business Automation Workflow (workflow)
  • Foundation (foundation)
  • FileNet® Content Manager (content)
  • Operational Decision Manager (decisions)

Each pattern has two custom resource template files. One with the minimal set of parameters, and the other contains all of the configurable parameters.

content
sc_optional_components Each pattern has a list of optional components that you can install with it. A component is identified by an acronym of the component or subcomponent name. If you want to install more than one component, separate the acronyms of the components with a comma. cmis
sc_content_initialization

Enable or disable content initialization (creation of FileNet P8 domain, creation of object stores, creation of CSS servers, and initialization of Navigator (ICN)).

If sc_content_initialization is set to "false," then the operator ignores the initialize_configuration section that is defined in the CR.

If sc_content_initialization is set to "true," then the initialize_configuration section in the CR must be defined for the operator to use the parameters and configure.

If the initialize_configuration section is defined in the CR, but sc_content_initialization is not set, the operator ignores the initialize_configuration" section is defined in the CR.

 The default is false.
sc_content_verification

Enable/disable the content verification (creation of test folder, creation of test document, execution of CBR search, and creation of Navigator repository and desktop).

If sc_content_verification is set to "false," then the operator ignores the verification_configuration section that is defined in the CR.

If sc_content_verification is set to "true," then the verify_configuration section in the CR must be defined for the operator to use the parameters and configure.

If the verify_configuration section is defined in the CR, but sc_content_verification is not set, the operator ignores the verify_configuration section is defined in the CR.

 The default is false.

sc_fast_file_storage_classname

sc_medium_file_storage_classname

sc_slow_file_storage_classname

Storage for a production deployment needs 3 storage classes. If you do not have 3 storage classes, you can use the same one for "slow", "medium", and "fast".

On OpenShift® Container Platform (OCP), the deployment script sets these parameters based on the user input.

ibmc-file-gold-gid

ibmc-file-silver-gid

ibmc-file-bronze-gid