Configuring Workflow Process Service Authoring

Before you install, configure the custom resource YAML file for Workflow Process Service Authoring.

Before you begin

Follow the instructions in Preparing Workflow Process Service Authoring.

Procedure

  1. Open the CR file that you created in Option 1a: (Recommended) Generating the custom resource with the deployment script.
  2. Check the values to make sure that they are the values that you want to deploy.
    • Make sure that the shared_configuration section of the CR file contains values for all required parameters, such as sc_deployment_license.
    • LDAP configuration (ldap_configuration) is not required. If you want to use LDAP, you can add the related parameters into your CR file.
    • By default, EDB PostgreSQL is provisioned.
      • If you ran the cp4a-prerequisites.sh script to prepare your databases and Kubernetes secrets, and you selected Document Processing with Workflow Process Service Authoring, then you must update the database section of bastudio_configuration to use PostgreSQL. You must create the PostgreSQL database for your deployment without the help of the cp4a-prerequisites.sh script. For more information, see Creating PostgreSQL databases.
      • If you want to use your own PostgreSQL, you can add the configuration under the bastudio_configuration section. The following custom resource YAML shows the required parameters.
         database:
              type: postgresql
              ## Provide the database server hostname for BAStudio
              host: "<Required>"
              ## Provide the database name for BAStudio. For example, wfpsdb. This parameter is case sensitive.
              ## The database provided should be created by the BAStudio SQL script template.
              name: "<Required>"
              ## Provide the database server port for BAStudio
              port: "<Required>"
            #   ## If you want to enable PostgreSQL connection fail-over, you must configure alternative_host and alternative_port. Otherwise, leave them blank.
            #   alternative_host:
            #   alternative_port:
            #   # ssl_enabled: <true/false>
            #   # # After you enable the database SSL connection with true, dave the TLS certificate used by the database in a secret 
            #   # # and put the name here. The secret can be created with the command:
            #   # # kubectl create secret generic <db_certificate_secret_name> --from-file=tls.crt=<certificate_pem_file_location>
            #   # certificate_secret_name: <db_certificate_secret_name>
    For more information, see Workflow Process Service Authoring parameters.
  3. If you are using the default EDB PostgreSQL installed with IBM Workflow Process Service Authoring, you need to self-manage this database. When you installed Workflow Process Service Authoring, the IBM Cloud Pak® for Business Automation operator setup the database with default values.
    1. Optional: If you want to change the default configuration, update the custom resource Cluster/<your-cr-name>-wfps-db with your changes to the database configuration. For more information about updating the custom resource parameters and cluster resources, see PostgreSQL Configuration and Resource management.
    2. Optional: If you want to switch to an external database, update your ICP4ACluster custom resource's Business Automation Studio database section. When configuring, the database name is wpsdb and the user is wpsuser. You can find the information for all the other fields in the Cluster/<your-cr-name>-wfps-db status. For example, the database section might look similar to:
      database: 
          type: "PostgreSQL"
          name: "wpsdb"
          host: "<Your_CR_Name>-wfps-db-rw.<Your_Namespace>.svc"
          port: "5432"
          ssl_enabled: "true"
          certificate_secret_name: "<Your_CR_Name>-wfps-db-server"
          use_custom_jdbc_drivers: "false"

What to do next

Continue to configure the other capabilities that are in your CR file, and make sure that you complete the last step Validating the YAML in your custom resource file before you deploy the CR.