Install and Configure Database Software

The database logs Process statistics, internal messages, and the Process control queue. Determine which software to use as the database software.

  • To use PostgreSQL, accept the default database option during the Connect:Direct® for Microsoft Windows installation.

    PostgreSQL for Connect:Direct now support certificate based authentication.Password prompted on PostgreSQL installation page is optional.

    Connect:Direct uses certificate-based authentication to authenticate to PostgreSQL and hence does not use or store the password.

    However, if you chose to provide a password during the Connect:Direct installation, the password can be used by external tools like psql, pgadmin etc to connect to PostgreSQL database.

  • To use SQL Server, install it on the local computer, a network drive, or remote computer accessible from the local Connect:Direct node.

Managing PostgresSQL Certificates

Connect:Direct for Microsoft Windows uses a self-signed certificate to authenticate with PostgreSQL. This certificate is created during the installation of Connect:Direct for Microsoft Windows and remains valid for 10 years from the installation date. If the PostgreSQL certificate expires, users can create a new self-signed certificate using the SPCli utility.

Steps to create a new self-signed certificate:

  1. Open SPCli and run the following command:

    create selfsignedcert Label=CDPostgreSQL SubjectName="CN=<USERID>" Expires=3652 CertFile="<TempDir>\server.crt" KeyFile="<TempDir>\server.key";
    

    Parameters:

    • <USERID>: The user ID for the PostgreSQL setup during the installation of Connect:Direct for Microsoft Windows. By default, this is "postgres".
    • <TempDir>: The directory where you want to create the new self-signed certificate.

Steps to Replace Existing PostgreSQL Certificates:

  1. Stop the Connect:Direct for Microsoft Windows and PostgreSQL services.
  2. Navigate to <cd_installation_dir>\PostgreSQL\certs\.
  3. Replace the existing server.crt and server.key files with the new ones created in the previous step.
  4. Restart the Connect:Direct for Microsoft Windows and PostgreSQL services.