Optional: Adding additional object stores post-deployment

You can add extra object stores post-deployment by updating the custom resource file to include the additional configuration information for the object store.

About this task

You can add additional object stores post-deployment by updating the CR file to include the additional datasource under the datasource_configuration section and updating the object store configuration under the initialize_configuration section.

Procedure

When you install by using the deployment script, follow these steps:

  1. Edit the ibm_cp4a_cr_final.yaml custom resources file from the initial installation.
    To validate you have the most recently edited version of ibm_cp4a_cr_final.yaml used for the installation, compare it to the version currently being used by the operator:
    oc get icp4acluster -o yaml
  2. For each additional/new object store that you create, make a copy of an existing object store datasource under dc_os_datasources and update the required parameters for the additional/new object store.
    Refer to Configuring FileNet Content Manager to understand how to update parameters. Also, see topic Datasource Parameters for more details.
  3. Under the initialize_configuration.ic_obj_store_creation.object_stores section in the ibm_cp4a_cr_final.yaml CR file:
    1. Make a copy of the required parameters.
      The required parameters include oc_cpe_obj_store_display_name, oc_cpe_obj_store_symb_name, oc_cpe_obj_store_conn.dc_os_datasource_name, oc_cpe_obj_store_conn.dc_os_xa_datasource_name, and oc_cpe_obj_store_admin_user_groups.
    2. If the initialization includes a FileNet Workflow system, enter a unique value for oc_cpe_obj_store_workflow_pe_conn_point_name parameter.
  4. Use the existing configuration as a guide to fill up the values for the required parameters.
  5. Modify the cp4adeploy-initialization-config configmap with:
    cpe_initialized = "False"
    cpe_os_number = x
    where, x is the total number of object stores initialized.
  6. When the edits to the CR and secret are complete, apply the updated custom resource YAML file:
    oc apply -f <ibm_cp4a_my_cr_final.yaml> --overwrite=true
  7. Update the IBM FileNet Content Manager secret ibm-fncm-secret to have the new credentials added.
    See Creating secrets to protect sensitive IBM FileNet Content Manager configuration data to prepare your ibm-fncm-secret secret. The credentials added in the secret must match with the credentials in the dc_os_label parameter.
  8. For a multi pattern deployment, restart both the ibm-cp4a-operator and the ibm-content-operator.