Database Manual Setup

From idenprotect Knowledge Base
Jump to: navigation, search

If you install idenprotect Core Platform using the RPM or via a Virtual Machine install, the database and associated user and permissions are created automatically. There is no need to follow this article further. Instead, you should see the Database Configuration article if you wish to learn about how to make changes.


If you are not using the RPM method to install the idenprotect Core Platform you will have to manually create a database for idenprotect to use. Without this database the idenprotect Core Platform will not start.

This article describes how to perform the steps to create the database, and how to configure idenprotect Core Platform to use the database that has been created.

Creating the Database

This section contains MySQL commands required to complete the task. Replace them with equivalent commands for the database technology being used.

First create the database, for example:

create database IDENPROTECT;

idenprotect Core Platform creates all the tables and preliminary data it requires during startup, so creating an empty database is enough.

In addition to the database, a user account with access permissions has to be created:

grant all on IDENPROTECT.* to 'user' identified by 'password';

If using Oracle, see CREATE USER in Oracle Database SQL Reference. In Oracle, a user and the database schema are the same thing, so creating a user also prepares the database. The user account doesn't require additional privileges.

Configuring idenprotect

During startup, idenprotect Core Platform searches for database settings in a file called /etc/idenprotect/

This file will need to be created manually and you will need to populate it with a series of properties to allow the idenprotect Core Platform to make the connection to the database you have just set up. For more information about the Database Configuration and how to make amendments, you can see Database Configuration.

JDBC Driver note

Note that up to release version 3.12.0, specifying the driver is a requirement as noted in the example configurations below. In later versions, this requirement has been removed and the driver is automatically selected based upon the Vendor selected.

Example MySQL Configuration

This is an example of the information needed in the file for MySQL database:

db.username = IDENPROTECT    
db.password = password
db.jdbc.driver = com.mysql.jdbc.Driver
db.jdbc.url = jdbc:mysql://localhost:3306/IDENPROTECT?autoReconnect=true
db.change.log = classpath:db-changelog.xml
db.vendor = MYSQL

Example Oracle Configuration

This is an example of the information needed in the file for ORACLE database:

db.username = IDENPROTECT
db.password = password
db.jdbc.driver = oracle.jdbc.OracleDriver
db.jdbc.url = jdbc:oracle:thin:@
db.change.log = classpath:db-changelog.xml
db.vendor = ORACLE