Skip to main content
Pentaho Documentation

Use PostgreSQL as Your Repository Database

Overview

Explains how to configure and use PostgreSQL as your BA Repository database.

Before you prepare your Business Analytics (BA) Repository, complete the tasks in Prepare Environment.

The BA Repository resides on the database that you installed during the Prepare Environment step, and consists of four components: Jackrabbit, Quartz, Hibernate, and Pentaho Operations Mart.

  • Jackrabbit contains the solution repository, examples, security data, and content data from reports that you use Pentaho software to create.
  • Quartz holds data that is related to scheduling reports and jobs.
  • Hibernate holds data that is related to audit logging.
  • Pentaho Operations Mart reports on system usage and performance.

Initialize PostgreSQL BA Repository Database

To initialize PostgreSQL so that it serves as the BA Repository, you will need to run a few SQL scripts to create the Hibernate, Quartz, Jackrabbit (JCR), and Pentaho Operations Mart components.

Use the ASCII character set when you run these scripts. Do not use UTF-8 because there are text string length limitations that might cause the scripts to fail.

These sections take you through the steps to initialize the PostgreSQL BA repository database.

Step 1: Change Default Passwords

We recommend that you change the default passwords in the SQL script files. If you are evaluating Pentaho, you might want to skip this step.

If you do decide to make the databases more secure, go to the pentaho/server/biserver-ee/data/postgresql directory and use any text editor to change the passwords in these files:

  • create_jcr_postgresql.sql
  • create_quartz_postgresql.sql
  • create_repository_postgresql.sql
  • pentaho_mart_postgresql.sql

Step 2: Run SQL Scripts

Once you change the passwords, you will need to run these SQL scripts. You will need administrator permissions on the server in order to run these scripts. The list of  SQL scripts is shown in the table below.

If you have a different port or different password, make sure that you change the password and port number in these examples to match the ones in your configuration.

Run these scripts from the PSQL Console window in the pgAdminIII tool.

Action SQL Script
SQL Scripts
Create Quartz \i <your filepath>/data/postgresql/create_quartz_postgresql.sql
Create Hibernate repository \i <your filepath>/data/postgresql/create_repository_postgresql.sql
Create Jackrabbit \i <your filepath>/data/postgresql/create_jcr_postgresql.sql
Create Pentaho Operations Mart \i <your filepath>/data/postgresql/pentaho_mart_postgresql.sql

Step 3: Verify PostgreSQL Initialization

After you run the scripts, this list will help you verify that databases and user roles have been created.

  1. Open the pgAdminIII tool.
  2. Verify that you can log in as hibuser.
  3. Once logged in, make sure that the Quartz, Jackrabbit (JCR), Hibernate, and Pentaho Operations Mart components are present.
  4. Exit from the pgAdminIII.

Configure PostgreSQL BA Repository Database

Now that you have initialized your repository database, you will need to configure Quartz, Hibernate, Jackrabbit, and Pentaho Operations Mart for a PostgreSQL database.

PostgreSQL is configured by default; if you kept the default passwords and port, you won't need to set up Quartz, Hibernate, Jackrabbit or the Pentaho Operations Mart. You can skip ahead to the connection tasks section.

By default, the examples in this section are for a PostgreSQL database that runs on port 5432. The default password is also in these examples. If you have a different port or different password, complete all of the instructions in these steps.

If you have a different port or different password, make sure that you change the password and port number in these examples to match the ones in your configuration.

Step 1: Set Up Quartz on PostgreSQL BA Repository Database

Event information, such as scheduled reports, is stored in the Quartz JobStore. During the installation process, you must indicate where the JobStore is located. You do this by modifying the quartz.properties file.

  1. Open the pentaho/server/biserver-ee/pentaho-solutions/system/quartz/quartz.properties file in any text editor.
  2. Locate the #_replace_jobstore_properties section and set the org.quartz.jobStore.driverDelegateClass as shown here.
    org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
    
  3. Locate the # Configure Datasources section and set the org.quartz.dataSource.myDS.jndiURL equal to Quartz, like this.
    org.quartz.dataSource.myDS.jndiURL = Quartz
    
  4. Save the file and close the text editor.

Step 2: Set Hibernate Settings for PostgreSQL

Modify the hibernate settings file to specify where Pentaho should find the BA Repository’s hibernate configuration file. The hibernate configuration file specifies driver and connection information, as well as dialects and how to handle connection closes and timeouts. The files in this section are located in the pentaho/server/biserver-ee/pentaho-solutions/system/hibernate directory.

  1. Open the hibernate-settings.xml file in a text editor. Find the <config-file> tags and confirm that it is configured for PostgreSQL. 
    <config-file>system/hibernate/postgresql.hibernate.cfg.xml</config-file>
    
  2. Save the file if you made changes, and close the file.
  3. Open the postgresql.hibernate.cfg.xml file in a text editor.
  4. Make sure that the password and port number match the ones you specified in your configuration. Make changes if necessary, then save and close the file.

Step 3: Modify Jackrabbit Repository Information for PostgreSQL

There are parts of code that you will need to alter in order to change the default jackrabbit repository to PostgreSQL.

  1. Navigate to the pentaho/server/biserver-ee/pentaho-solutions/system/jackrabbit and open the repository.xml file with any text editor.
  2. Following the table below, locate and verify or change the code so that the PostgreSQL lines are not commented out, but the MySQL, Oracle, and MS SQL Server lines are commented out.

If you have a different port or different password, make sure that you change the password and port number in these examples to match the ones in your configuration.

Item: Code Section:
Repository
<FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
    <param name="driver" value="org.postgresql.Driver"/>
    <param name="url" value="jdbc:postgresql://localhost:5432/jackrabbit"/>
    ...
  </FileSystem>
DataStore
<DataStore class="org.apache.jackrabbit.core.data.db.DbDataStore">
    <param name="url" value="jdbc:postgresql://localhost:5432/jackrabbit"/>
    ...
  </DataStore>
Workspaces
<FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
      <param name="driver" value="org.postgresql.Driver"/>
      <param name="url" value="jdbc:postgresql://localhost:5432/jackrabbit"/>
     ...
    </FileSystem>

PersistenceManager

(1st part)

<PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.PostgreSQLPersistenceManager">
      <param name="url" value="jdbc:postgresql://localhost:5432/jackrabbit"/>
      ...
    </PersistenceManager>
Versioning
<FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
      <param name="driver" value="org.postgresql.Driver"/>
      <param name="url" value="jdbc:postgresql://localhost:5432/jackrabbit"/>
     ...
    </FileSystem>

PersistenceManager

(2nd part)

<PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.PostgreSQLPersistenceManager">
      <param name="url" value="jdbc:postgresql://localhost:5432/jackrabbit"/>
      ...
    </PersistenceManager>

Perform Tomcat-Specific Connection Tasks

After your repository has been configured, you must configure the web application servers to connect to the BA Repository. In this step, JDBC and JNDI connections are made to the Hibernate, Jackrabbit, and Quartz components.

By default, the BA Server software is configured to be deployed and run on the Tomcat server. As such, connections have already been specified and the Tomcat context.xml file must be modified ONLY if you have changed the default ports or passwords.

The next couple of sections guide you through the process of working with the JDBC drivers and connection information for Tomcat.

Step 1: Download Drivers and Install with the JDBC Distribution Tool

To connect to a database, including the Pentaho Repository database, you will need to download and install a JDBC driver to the appropriate places for Pentaho components as well as on the the web application server that contains the Pentaho Server(s). Fortunately, the JDBC Distribution Tool makes this process easy. 

Due to licensing restrictions, Pentaho cannot redistribute some third-party database drivers. This is why you have to download the file yourself and install it yourself.

  1. Download a JDBC driver JAR from your database vendor or a third-party driver developer.
  2. Copy the JDBC driver JAR you just downloaded to the pentaho/jdbc-distribution directory.
  3. Open a cmd prompt or shell tool, navigate to the pentaho/jdbc-distribution directory and enter one of the following:

​Windows:

distribute-files.bat <name of JDBC driver JAR>

Linux:

./distribute-files.sh <name of JDBC driver JAR>
  1. If you have run this utility as part of the installation process, you are done. Go to the next step of the installation instructions.
  2. If you have run this utility so that you can connect to a new repository, restart the BA or DI Server and Design tools, then try to connect to the new repository. If you cannot connect, verify that the drivers are installed as shown in this table. Restart your Pentaho Server(s) and Client tools.
List of Products and Corresponding Locations for JDBC Drivers
Server or Design Tool Directory
Business Analytics (BA) Server pentaho/server/biserver-ee/tomcat/lib
Data Integration (DI) Server pentaho/server/data-integration-server/tomcat/lib
Pentaho Data Integration (Spoon) pentaho/design-tools/data-integration/lib
Pentaho Report Designer (PRD) pentaho/design-tools/report-designer/lib/jdbc
Pentaho Aggregation Designer (PAD) pentaho/design-tools/aggregation-designer/drivers
Pentaho Schema Workbench (PSW) pentaho/design-tools/schema-workbench/drivers
Pentaho Metadata Editor (PME) pentaho/design-tools/metadata-editor/libext/JDBC

Step 2: Modify JDBC Connection Information in the Tomcat context.xml File

Database connection and network information, such as the username, password, driver class information, IP address or domain name, and port numbers for your BA Repository database are stored in the context.xml file. Modify this file to reflect the database connection and network information to reflect your operating environment. You also modify the values for the validationQuery parameters in this file if you have chosen to use an BA Repository database other than PostgreSQL.

If you have a different port, password, user, driver class information, or IP address, make sure that you change the password and port number in these examples to match the ones in your configuration environment.

  1. Consult your database documentation to determine the JDBC class name and connection string for your BA Repository database.
  2. Go to the biserver-ee/tomcat/webapps/pentaho/META-INF directory and open the context.xml file with any file editor.
  3. Comment out the resource references that refer to databases other than PostgreSQL, such as MySQL, MS SQL Server, and Oracle. Then, add the following code to the file if it does not already exist. Be sure to adjust the port numbers and passwords to reflect your environment, if necessary.
    <Resource name="jdbc/Hibernate" auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxTotal="20" maxIdle="5" maxWaitMillis="10000" username="hibuser" password="password" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost:5432/hibernate" validationQuery="select 1"/>
    
    <Resource name="jdbc/Audit" auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxTotal="20" maxIdle="5" maxWaitMillis="10000" username="hibuser" password="password" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost:5432/hibernate" validationQuery="select 1"/>
    
    <Resource name="jdbc/Quartz" auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxTotal="20" maxIdle="5" maxWaitMillis="10000" username="pentaho_user" password="password" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost:5432/quartz" validationQuery="select 1"/>
    
    <Resource name="jdbc/pentaho_operations_mart" auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxTotal="20" maxIdle="5" maxWaitMillis="10000" username="hibuser" password="password" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost:5432/pentaho_operations_mart" validationQuery="select 1"/>
    
    <Resource name="jdbc/PDI_Operations_Mart" auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxTotal="20" maxIdle="5" maxWaitMillis="10000" username="hibuser" password="password" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost:5432/hibernate" validationQuery="select 1"/>
    
  4. Make sure that the validationQuery variable for your database is set to this: validationQuery="select 1"
  5. Save the context.xml file, then close it.
  6. Clear the tomcat/work and tomcat/temp directories. 

Next Steps

Now it is time to start your server.