Changing an OLM-based CP4BA deployment to a non-OLM deployment

When you use the OpenShift Container Platform (OCP) console to install a CP4BA production deployment, the custom resource (CR) parameters are prefixed with olm_. The olm_ parameters identify the options in the Form View with the CR parameters in the YAML View. The olm_ parameters can be changed later to non-OLM CR parameters to manage your deployment better outside of the console.

If a CP4BA CR is generated from the OCP console, it has olm_ parameters. For more information, see Business Automation configuration parameters for OpenShift console.

Remember: OLM refers to the operator lifecycle manager that is used in OpenShift. OLM helps you to install, update, and manage the lifecycle of operators and services that are deployed in OCP clusters.

If at some point you decide that you do not want to use the OCP console to manage your deployment, use the CR file that you created in the Form View as a reference to change the parameters to non-OLM parameter names. The following table provides the equivalent non-OLM parameter names for the olm_ parameters.

Download the CR from the console, make the parameter name changes, and then apply the CR update from the OC CLI.

Restriction: After the change is made, you can no longer use the Form View for your CP4BA deployment.
Table 1. CP4BA deployment OLM parameters versus non-OLM parameters
OLM parameters Non-OLM parameter names
spec.olm_deployment_type spec.shared_configuration.sc_deployment_type: Production
spec.olm_ibm_license spec.ibm_license
spec.olm_production_document_processing spec.shared_configuration.sc_deployment_patterns: foundation, document_processing

spec.shared_configuration.sc_optional_components: ae_data_persistence

spec.olm_production_decisions spec.shared_configuration.sc_deployment_patterns: foundation, decisions
spec.olm_production_content spec.shared_configuration.sc_deployment_patterns: foundation, content
spec.olm_production_workflow spec.shared_configuration.sc_deployment_patterns: foundation, workflow
spec.olm_production_workflow_deploy_type="workflow_authoring" spec.shared_configuration.sc_optional_components: baw_authoring
spec.olm_production_workflow_deploy_type="workflow_runtime" spec.shared_configuration.sc_optional_components: ae_data_persistence
spec.olm_production_option spec.shared_configuration.sc_optional_components:[]

This parameter is used to list the optional components for selected capabilities.

spec.olm_production_application spec.shared_configuration.sc_deployment_patterns: foundation, application
spec.olm_production_decisions_ads spec.shared_configuration.sc_deployment_patterns: foundation, decisions_ads
spec.olm_production_workflow_process_service spec.shared_configuration.sc_deployment_patterns: foundation, workflow-process-service

spec.shared_configuration.sc_optional_components: wfps_authoring

spec.olm_dc_os_ae_datasources spec.datasource_configuration.dc_os_datasources
spec.olm_dc_os_workflow_datasources spec.datasource_configuration.dc_os_datasources
spec.olm_sc_content_verification spec.shared_configuration.sc_content_verification
spec.olm_sc_content_initialization spec.shared_configuration.sc_content_initialization
spec.olm_dc_os_adp_datasources spec.datasource_configuration.dc_os_datasources
spec.olm_dc_os_ae_datasources spec.datasource_configuration.dc_os_datasources
spec.olm_dc_os_content_datasources spec.datasource_configuration.dc_os_datasources