Configuring database.conf for Oracle

In this subsection, we configure the database.conf file to use the Oracle JDBC driver. Connect uses the thin version of the Oracle JDBC driver throughout the system.

To configure database.conf, execute the following steps:

1. Open the database.conf file using a text editor. Find the section of the file that looks like the following:

   type = oracle

   driver = oracle.jdbc.OracleDriver

   url = "jdbc:oracle:thin:@localhost:1521:db"

2. Edit the url: Specify the database server, port and database name.

   • Enter the details in the format server:port:dbname (e.g. @myserver:1521:ORCL).

3. Important: Ensure that no other lines are uncommented that would conflict with these property definitions.

4. Save the file.

Configuring database.conf for SQL Server

In this subsection, we configure the database.conf file to use the Microsoft SQL Server JDBC driver in preparation for installing or upgrading the database. Connect uses the thin version of the JDBC driver throughout the system and does not require a SQL Server client install.

To configure database.conf, execute the following steps.

1. Open the database.conf file using a text editor. Find the section of the file that looks like the following:

   #type = sql

   #driver = com.microsoft.sqlserver.jdbc.SQLServerDriver

   #url = "dbc:sqlserver://instance;DatabaseName=db"

2. Uncomment the lines for:

   • type

   • driver

   • url

3. Edit database.connect: Specify the database server, and database name.

   • Enter the details in the format server;DatabaseName=dnname (e.g. myserver;DatabaseName=CONNECT10).

4. Important: Ensure that no other lines are uncommented that would conflict with these property definitions.

5. Save the file.

Configuring database.conf for MySQL

In this subsection, we configure the database.conf file to use the MySQL JDBC driver in preparation for installing or upgrading the database.

To configure database.conf, execute the following steps.

1. Open the database.conf file using a text editor. Find the section of the file that looks like the following:

   #type = mysql

   #driver = com.mysql.cj.jdbc.Driver

   #url = "jdbc:mysql://localhost:3306/connect?useUnicode=yes&characterEncoding=UTF-8&autoReconnect=true"

2. Uncomment the lines for:

   • type

   • driver

   • url

3. Edit database.connect: Specify the database server, and database name.

   • Enter the details in the format server:3306/dbname (e.g. myserver:3306/CONNECT10).

   • Keep the query string arguments after the '?' character.

4. Important: Ensure that no other lines are uncommented that would conflict with these property definitions.

5. Save the file.

Software License Key

Connect requires a software license key. The license key is stored in the brickstlicense.jar file in the import directory. The Connect software distribution comes with a trial license key. You should replace this with a license key supplied by Brick Street Software.

The seeddb program copies the license key from the brickstlicense.jar file into the Connect database. At runtime, the Connect software checks the license key by fetching it from the database.
To update the license key, follow these steps:

• Copy the new brickstlicense.jar license key file to the import subdirectory of the Connect install directory.

• Run seeddb --updateLicense to copy the license key file to the database.

• Restart the inside nodes of each deployment to force a new license key check.

License Java Argument for WebSphere

An additional argument is needed for configuring WebSphere, without which the UI will display a "License is Expired" error. This argument is to be added in the WebSphere Admin Console in the following location:

Servers ➜ Server Types ➜ WebSphere Application ➜ (server name) ➜ Java and Process Management ➜ Process Definition ➜ Java Virtual Machine

On this page, add the following to the Generic JVM arguments: