Creating the databases for Document Processing

Your Automation Document Processing environment requires multiple databases.

About this task

The environment for Document Processing incorporates multiple capabilities. As part of the preparation for the other capabilities, you also prepare databases for all of those components. For a Document Processing deployment, you must prepare the following databases:

Table 1. Databases for Automation Document Processing
Component	How to prepare the required databases
Document Processing engine	Preparing the databases for Document Processing engine
FileNet® Content Manager	Preparing a database for the Global Configuration Database (GCD) and the object store
Business Automation Navigator	Preparing a database for Business Automation Navigator
Business Automation Studio	Creating databases for Business Automation Studio
Application Engine	Creating the database for Application Engine

Important: Preparing the databases is only one part of the preparation for the other components. See the links in Preparing for other components to complete all of the preparation steps for the multiple capabilities that comprise the Document Processing environment.

For Automated Document Processing, some of the database and data source settings in the custom resource YAML have specific naming requirements depending on the environment type- Authoring/development or Runtime- you are deploying. When you supply parameter values in the YAML, keep the following requirements in mind:

## For the "document_processing" pattern, the following parameters below MUST remain unchanged and have the default value:
      ##   dc_os_label: "devos1" 
      ##   dc_common_os_datasource_name: "DEVOS1DS"
      ##   dc_common_os_xa_datasource_name: "DEVOS1DSXA"
***
## For the "document_processing" pattern, the following parameters below MUST remain unchanged and have the default value:
      ##   dc_os_label: "aeos"
      ##   dc_common_os_datasource_name: "AEOS"
      ##   dc_common_os_xa_datasource_name: "AEOSXA"

Requirements for parameter values:

Authoring/Development environment: Datasource values as specified in the example must use the prepared default values.
Runtime environment: Datasource values for the devos1 object store can be updated to any value, but the values for the aeos object store must continue to use the prepared default values.

Values for the data sources that you create are also added to the Initialization section of the CR YAML to set up the data sources with the required names for your environment:

ic_obj_store_creation:
      object_stores:
     ## Configuration for the document processing object store
      - oc_cpe_obj_store_display_name: "DEVOS1"
        oc_cpe_obj_store_symb_name: "DEVOS1"
        oc_cpe_obj_store_conn:
          name: "objectstore1_connection"
          site_name: "InitialSite"
          dc_os_datasource_name: "DEVOS1DS"
          dc_os_xa_datasource_name: "DEVOS1DSXA"
        oc_cpe_obj_store_admin_user_groups:
        - "CEAdmin"
        - "<Required>" # Specify an LDAP Admin group (CE Environment Owners) as domain admin (required for "document_processing" capability)
      ## Configuration for the application engine object store
      ## Display name for the application engine object store to create
      - oc_cpe_obj_store_display_name: "AEOS"
        ## Symbolic name for the application engine object store to create
        oc_cpe_obj_store_symb_name: "AEOS"
        oc_cpe_obj_store_conn:
          ## Object store connection name
          name: "AEOS_connection" #database connection name
          ## The name of the site
          site_name: "InitialSite"
          ## Add the name of the object store data source
          dc_os_datasource_name: "AEOS"
          ## The XA datasource
          dc_os_xa_datasource_name: "AEOSXA"
        ## Admin user group
        oc_cpe_obj_store_admin_user_groups:
        - "<Required>"

For more information, see Configuring Document Processing

What to do next

To prepare the databases manually, see Preparing the databases for Document Processing engine.