Configuring Engagement Services Database

To create a database for Engagement Services, follow these steps:

1. Create a database with a name "kpnsdb" with character set as "utf8" and collate as "utf8_unicode_ci" using the following command. The database name can contain a custom name along with prefix and suffix. Prefix and suffix are optional. For example, schema name is <prefix>kpnsdb<suffix>.

   The following is a sample query for creating a database in MySQL

   
   
   CREATE DATABASE kpnsdb CHARACTER SET utf8 COLLATE utf8_unicode_ci;

   The following is a sample query for creating a database in DB2

   
   
   CREATE SCHEMA "schema_name" AUTHORIZATION dbclient;

   NOTE:  For DB2 and Oracle databases, a schema name should be in capital letters.

   NOTE: To create necessary tablespaces for Oracle and DB, and pre-requisites for MySQL and MS SQL, refer to Database Prerequisites.

   The following details are required for Flyway configuration:

   • Schema name for Engagement Services: kpnsdb
   • Placeholders for Engagement Services:

     flyway.placeholders.KMS_DBNAME

   • Tablespace Placeholders for DB2 and Oracle:

     Product Name	Tablespace Placeholders for DB2 and Oracle
     Engagement Services (KMS)	KMS_DATA_TABLESPACE, KMS_INDEX_TABLESPACE, KMS_LOB_TABLESPACE

   • SQL files paths for Engagement Services in QuantumFabric_Plugins folder:
     Click here for more details

     Path for SQL files in the QuantumFabric_Plugins folder	Database	Component
     \QuantumFabric_Plugins\scripts\mysql-kpns-migrations	MySQL	Engagement Services
     \QuantumFabric_Plugins\scripts\oracle-kpns-migrations	Oracle
     \QuantumFabric_Plugins\scripts\mssql-kpns-migrations	SQL Server

2. Execute all SQL scripts by using the steps provided at Configuring Flyway Command-line Tool.

   Click here to view the Engagement Services schema diagram