Automation Document Processing Deployment Recommendations

Content

• Use a scripted deployment.  CP4BA deployments can be performed using patterns, operator lifecycle manager (OLM), or scripts.  Of the three, scripts provides the most guided deployment method, prompting for the values it needs to deploy the product.  It also creates scripts for the databases and secrets needed for the deployment.  Pattern and OLM deployments are only recommended for advanced users familiar with the intricacies of CP4BA.
• If only one Automation Document Processing project is needed, such as for training or testing, use a Starter deployment.  Starter deployments are easy to deploy and can quickly be disposed and rebuilt as desired.  Use a Production deployment for more permanent deployments where data needs to be retained, or multiple projects are needed.
• When running the prerequisites script and asked if you want to restrict network egress, select No when possible.  Production systems require users to configure and deploy network policies to properly secure the system, and if not done properly can break the system.  If this is an internal test system or similar system where security is not an issue, selecting No eliminates this step in the deployment.
• Maximize the logging when initially deploying.  When you first deploy a system, you need good logging to troubleshoot issues that arise during deployment.  Reduce the logging level only after you have everything working and only if there is a need to optimize performance.  To maximize the logging, set these properties in your custom resource (CR) yaml.
   

    shared_configuration:
      no log: false
      show_sensitive_log: true
  
      ...
  
    ca_configuration:
      global:
        logs:
          log_level: debug