3.2 Creating or Upgrading a Connect Database Schema

IMPORTANT: Ensure your DBA has properly setup the Connect database table spaces before proceeding.

Beginning with version 10r5.7.1, Connect uses the Liquibase tool to manage the database schema. Liquibase is a tool that manages a schema model, defined in XML, and provides tooling to compare the model with your actual Connect database schema. More information on Liquibase is available at https://docs.liquibase.com/.

4.3.1 Using the Liquibase Schema Update Tool

The Liquibase schema model is stored in the $KCHOME/initschema directory. The Liquibase schema is defined as a sequence of Change Sets. Each change set is a schema change, such as creating a table, creating an index, or adding a new column to an existing table. Liquibase records each change set that has been applied in a table named databasechangelog.

Once the liquibase.properties file is set up run:

#
runliquibase.sh clearCheckSums


Once you the clear Checksum has finished you can see the SQL changes that Liquibase will make using the following command. :


./runliquibase.sh updateSQL


If you are satisfied with the changes that liquibase will make, you can have liquibase apply the schema changes using this command:

./runliquibase.sh update


4.3.2 Using seeddb.sh

Seeddb requires the database.properties to be populated with connection information for the database. More information here

You can find seeddb in the install subdirectory $KCHOME/install If you are not familiar with the parameters used for seeddb.sh, you can type

seeddb.sh

without parameters. The command will display all of the parameter types that can be used.
When running seeddb.sh, there are three parameters commonly used:

  • Company Name: This is the name of the company entity. This is typically used in multi-tenant (i.e. multi-company) instances. In the case of multi-tenancy, each company will have their own name. The primary company is 'Default'

  • Sender Name: This is the name that will appear on outgoing messages. This name is able to be changed as well as added to if need be at a later time.

  • Sender Email Address: This is the default email address that will be used to send the outgoing messages. This email is able to be changed as well as added to if need be at a later time.

Example:

sh ./seeddb.sh Default "Customer Care" [email protected]