Creating a PostgreSQL database

Create a PostgreSQL database before installing Application Engine.

About this task

Tip: If you need to know which database versions are supported for your installation, use this IBM Support page to generate a software compatibility report.

Procedure

  1. To create the Application Engine database with the default tablespace, run the following command on your local or remote database server:
    -- create a new user
    create user APP_ENGINE_DB_USER_NAME with password 'APP_ENGINE_DB_PASSWORD';
    
    -- create database APP_ENGINE_DB_NAME
    create database APP_ENGINE_DB_NAME owner APP_ENGINE_DB_USER_NAME;
    
    -- The following grant is used for databases
    grant all privileges on database APP_ENGINE_DB_NAME to APP_ENGINE_DB_USER_NAME;
    
    where:
    • APP_ENGINE_DB_USER_NAME is the username that the Application Engine uses to connect to the database.
    • APP_ENGINE_DB_PASSWORD is the password that the Application Engine uses to connect to the database.
    • APP_ENGINE_DB_NAME is the database name for the Application Engine database, for example, AAEDB. It is case-sensitive.
    Optionally, if you want to create the Application Engine database with a separate tablespace, run the following command on your local or remote database server:
    -- create a new user
    create user APP_ENGINE_DB_USER_NAME with password 'APP_ENGINE_DB_PASSWORD';
    
    -- create tablespace and modify location as per your requirement 
    create tablespace APP_ENGINE_TABLESPACE_NAME owner APP_ENGINE_DB_USER_NAME location '/pgsqldata/aedb';
    grant create on tablespace APP_ENGINE_TABLESPACE_NAME to APP_ENGINE_DB_USER_NAME;
    
    -- create database APP_ENGINE_DB_NAME
    create database APP_ENGINE_DB_NAME owner APP_ENGINE_DB_USER_NAME tablespace APP_ENGINE_TABLESPACE_NAME encoding UTF8;
    
    -- The following grant is used for databases
    grant all privileges on database APP_ENGINE_DB_NAME to APP_ENGINE_DB_USER_NAME; 
    where:
    • APP_ENGINE_DB_USER_NAME is the username that the Application Engine uses to connect to the database.
    • APP_ENGINE_DB_PASSWORD is the password that the Application Engine uses to connect to the database.
    • APP_ENGINE_DB_NAME is the database name for the Application Engine database, for example, AAEDB. It is case-sensitive.
    • APP_ENGINE_TABLESPACE_NAME is the tablespace name for the Application Engine database, for example, aedb_tbs. It is case-sensitive.
    Note: If FIPS is enabled and you use PostgreSQL database with SCRAM-SHA-256 authentication, then passwords for database connections must contain at least 16 alphanumeric characters.
  2. If Business Automation Application data persistence is enabled, it needs one object store from IBM FileNet® Content Manager. You can either reuse the existing one and specify it for the object_store_name parameter or create one named something like AEOS, which stands for application engine object store.
    • To create the databases for IBM FileNet Content Manager, create a database for the Content Platform Engine Global Configuration Database (GCD) and one database for the content stores. For more information, see Preparing the databases.
    • To create one object store for Business Automation Application data persistence but not reuse the existing one, you must create one database, such as one named AEOSDB. For more information, see Setting up a PostgreSQL database for Content Platform Engine.
  3. Optional: To use your own JDBC driver, complete the following steps.
    1. Package your JDBC files into a compressed file and use the sc_drivers_url configuration parameter to download them from an accessible web server. Follow the steps in Optional: Preparing customized versions of JDBC drivers and ICCSAP libraries.
    2. Add the customized JDBC driver information to the configuration parameters. Set application_engine_configuration.use_custom_jdbc_drivers to true in the configuration parameters. See Application Engine configuration parameters.

What to do next

To protect the configuration data you are going to enter, see Creating secrets to protect sensitive configuration data.