Preparing the database

To deploy IBM Business Automation Navigator, you must prepare a separate database in advance.

dc_icn_datasource:
      
      dc_database_type: "<Required>"
      dc_common_icn_datasource_name: "ECMClientDS"
      database_servername: "<Required>"
      database_port: "<Required>"
      database_name: "<Required>"
      database_ssl_secret_name: "<Required>"
      dc_oracle_icn_jdbc_url: "<Required>"


navigator_configuration:

  icn_production_setting:

      icn_jndids_name: ECMClientDS
      icn_schema: ICNDB
      icn_table_space: ICNDB

1. If you haven't already done so, install a database server.
   Use your vendor documentation to accomplish the server installation.

   You can find additional database planning and installation information in the FileNet Content Manager documentation:

   • Preparing Db2 for Linux, UNIX, and Windows server
   • Preparing Microsoft SQL Server
   • Preparing Oracle Server
   • Setting up a PostgreSQL database
2. Prepare the IBM Business Automation Navigator database:

   Db2

   For details about configuring a Db2 database for your IBM Business Automation Navigator deployment, see Creating a Db2® database for Navigator

   Note: The Before you begin content does not apply for container deployments in the Cloud Pak. Create a database, but do not run additional scripts for creating the tables and indexes.

   Oracle

   For details about configuring an Oracle database for your IBM Business Automation Navigator deployment, see Creating an Oracle database for Navigator.

   Note: The Before you begin content does not apply for container deployments in the Cloud Pak. Create a database, but do not run additional scripts for creating the tables and indexes.

   Microsoft SQL Server

   You create both a database and a schema for the container deployment, for example:

   create database <dbName>
   ** connect to database ** 
   create schema <schemaName>

   For details about configuring a Microsoft SQL Server database for your IBM Content Navigator deployment, see Setting up a Microsoft SQL Server database.

   Note: The Before you begin content does not apply for container deployments in the Cloud Pak. Create a database, but do not run additional scripts for creating the tables and indexes.

   PostgreSQL

   Set up your PostgreSQL database and record the database settings. For more information about PostgreSQL, see Setting up a PostgreSQL database

3. Create a table space in your database.
   The FileNet Content Manager documentation provides some information on creating table spaces, on Db2, Oracle, and Microsoft SQL Server. Note that for Navigator, the sizing requirements are less than other uses, such as object stores. When you create the table space for Navigator, use "REGULAR" as the type or size.
4. Create a database user.
   You can choose to use your dbadmin user, or create another database user for your Navigator database.

   For details about the kind of privileges this user needs, see Creating database accounts.

   This user that you create is included in the Business Automation Navigator secret as the navigatorDBUsername.

5. Optionally create a schema.
   The operator can detect whether a schema exists in the database and creates one if a schema does not exist. If you want to select a schema name in advance, specify the name of your schema in the custom resource file in the icn_production_setting.icn_schema parameter. If you plan to use Task Manager, the schema name must be ICNDB.

   If you don't specify a value for the icn_production_setting.icn_schema parameter, the operator creates the following schema name:

   • Oracle database: The schema is named the same as the navigatorDBUsername from the Business Automation Navigator secret.
   • All other databases: The schema keeps the default name, ICNDB.