Skip to main content
Pentaho Documentation

Use MS SQL Server as your repository database (Manual installation)

Parent article

This article includes the steps for installing MS SQL Server as the host database for the Pentaho Server in a manual installation of Pentaho.

Before you begin

Prerequisite

Before you prepare your Pentaho Repository, you must prepare either a Windows or Linux environment.

Components

The Pentaho Repository resides on the database that you installed during the Windows or Linux environment preparation step, and consists of the following components:

  • 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.

  • (Optional) Pentaho Operations Mart

    To report on system usage and performance.

Initialize MS SQL ServerPentaho Repository database

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

CautionUse 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.

The sections in this article take you through the steps to initialize the MS SQL Server Pentaho Repository database.

Step 1: Adjust MS SQL Server configuration settings

Configure the following MS SQL Server settings in Microsoft SQL Server Management Studio or other tool of your choice.

Procedure

  1. Select SQL Server and Windows Authentication Mode​ to use mixed authentication.

  2. Enable TCP/IP for MS SQL Server.

  3. Make sure that MS SQL Server is listening on an external IP, and not localhost.

Step 2: Change default passwords

For your production server, we highly recommend that you change the default passwords in the following SQL script files to make the databases more secure.
NoteIf you are evaluating Pentaho, then you might want to skip this step.

Procedure

  1. Browse to the pentaho/server/pentaho-server/data/sqlserver directory.

  2. Use any text editor to change the passwords in these SQL scripts:

    • create_jcr_sqlServer.sql
    • create_quartz_sqlServer.sql
    • create_repository_sqlServer.sql
    • pentaho_mart_sqlServer.sql

Step 3: Run SQL scripts

You will need to run the SQL scripts in the table below.

NoteThese scripts require administrator permissions on the server in order to run them.
CautionIf you have a different port or different password, make sure that you change the password and port numbers in these examples to match the ones in your configuration.

Run these scripts from the sqlcmd utility window or from Microsoft SQL Server Management Studio.

ActionSQL Script
Create Quartz-i <filepath to DDL>/create_quartz_sqlServer.sql
Create Hibernate repository-i <filepath to DDL>/create_repository_sqlServer.sql
Create Jackrabbit-i <filepath to DDL>/create_jcr_sqlServer.sql
Create Pentaho Operations mart-i <filepath to DDL>/pentaho_mart_sqlserver.sql

Step 4: Verify MS SQL Server initialization

After you run the scripts, perform the following steps to verify that databases and user roles have been created:

Procedure

  1. Open MS SQL Server Management Studio.

  2. In the Object Explorer section of the window, make sure that the Quartz, Jackrabbit (JCR), Hibernate, and Pentaho Operations Mart databases are present.

  3. Navigate to Security Logins and make sure that the appropriate users have been created.

  4. Exit from the MS SQL Server Management Studio tool.

Configure MS SQL Server Pentaho RepositoryDatabase

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

By default, the examples in this section are for a PostgreSQL database that runs on port 1433. The default password is also in these examples.

CautionIf 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 MS SQL Server

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

  1. Open the pentaho/server/pentaho-server/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:

    org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.MSSQLDelegate
  3. Locate the # Configure Datasources section and set the org.quartz.dataSource.myDS.jndiURL equal to Quartz, as shown:

    org.quartz.dataSource.myDS.jndiURL = Quartz
  4. Save the file and close the text editor.

Step 2: Set Hibernate settings for MS SQL Server

Modify the Hibernate settings file to specify where Pentaho should find the Pentaho 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.
NoteThe Hibernate database is also where the Pentaho Server stores the audit logs that act as source data for the Pentaho Operations Mart.

The files in this section are located in the pentaho/server/pentaho-server/pentaho-solutions/system/hibernate directory.

Perform the following steps to specify where Pentaho can find the Hibernate configuration file.

Procedure

  1. Open the hibernate-settings.xml file in a text editor. Find the <config-file> tags and change postgresql.hibernate.cfg.xml to sqlserver.hibernate.cfg.xml as shown.

    From:

    <config-file>system/hibernate/postgresql.hibernate.cfg.xml</config-file>

    To:

    <config-file>system/hibernate/sqlserver.hibernate.cfg.xml</config-file>
  2. Save and close the file.

  3. Open the sqlserver.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: Replace default version of audit log file with MS SQL Server version

Since you are using MS SQL to host the Pentaho Repository, you need to replace the audit_sql.xml file with one that is configured for MS SQL Server.

Procedure

  1. Locate the pentaho-solutions/system/dialects/sqlserver/audit_sql.xml file.

  2. Copy it into the pentaho-solutions/system directory.

Step 4: Modify Jackrabbit repository information for MS SQL Server

Edit the following code to change the default Jackrabbit repository to MS SQL Server.

Procedure

  1. Navigate to the pentaho/server/pentaho-server/pentaho-solutions/system/jackrabbit and open the repository.xml file with any text editor.

  2. As shown in the table below, locate and verify or change the code so that the MS SQL Server lines are not commented out, but the MySQL, Oracle, and PostgreSQL lines are commented out.

    CautionIf 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.
    ItemCode Section
    Repository
    <FileSystem class="org.apache.jackrabbit.core.fs.db.MSSqlFileSystem">
         <param name="driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
         <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
    …
         <param name="schema" value="mssql"/>
    </FileSystem>
    DataStore
    <DataStore class="org.apache.jackrabbit.core.data.db.DbDataStore">
        <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
    …
        <param name="schema" value="mssql"/>
    </DataStore>
    Workspaces
    <FileSystem class="org.apache.jackrabbit.core.fs.db.MSSqlFileSystem">
          <param name="driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
          <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
    …
          <param name="schema" value="mssql"/>
    PersistenceManager (1st part)
    <PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.MSSqlPersistenceManager">
          <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
    …
          <param name="schema" value="mssql"/>
          <param name="schemaObjectPrefix" value="${wsp.name}_pm_ws_"/>
    </PersistenceManager>
    Versioning
    <FileSystem class="org.apache.jackrabbit.core.fs.db.MSSqlFileSystem">
          <param name="driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
          <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
    …
          <param name="schema" value="mssql"/>
    </FileSystem>
    PersistenceManager (2nd part)
    <PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.MSSqlPersistenceManager">
          <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
    …
          <param name="schema" value="mssql"/>
          <param name="schemaObjectPrefix" value="pm_ver_"/>
    </PersistenceManager>
    DatabaseJournal
    <Journal class="org.apache.jackrabbit.core.journal.MSSqlDatabaseJournal">
        <param name="revision" value="${rep.home}/revision.log"/>
        <param name="url" value="jdbc:sqlserver://localhost:1433;DatabaseName=jackrabbit"/>
        <param name="driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
        <param name="user" value="jcr_user"/>
        <param name="password" value="password"/>
        <param name="schema" value="mssql"/>
        <param name="schemaObjectPrefix" value="cl_j_"/>
        <param name="janitorEnabled" value="true"/>
        <param name="janitorSleep" value="86400"/>
        <param name="janitorFirstRunHourOfDay" value="3"/>
    </Journal>

Using JBoss

If you are installing your own JBoss web application server, skip the Tomcat section, and move on to Prepare JBOSS connections and web app servers.

Perform Tomcat-specific connection tasks

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

NoteBy default, the Pentaho 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 driver and apply to the Pentaho Server

To connect to a database, including the Pentaho Repository database, you will need to download and copy a JDBC driver to the appropriate places for the Pentaho Server as well as on the web application server.

Before you begin

NoteDue to licensing restrictions, Pentaho cannot redistribute some third-party database drivers. You must download and install the file yourself.

Procedure

  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/server/pentaho-server/tomcat/lib folder.

  3. Copy the hsqldb-2.3.2.jar file to pentaho-server/tomcat/lib if you want to retain the sample provided by Pentaho.

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 Pentaho Repository database are stored in the context.xml file. Modify this file to reflect the database connection and network information for your operating environment.

If you have chosen to use an Pentaho Repository database other than MS SQL, you also need to modify the values for the validationQuery parameters in this file.

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

Procedure

  1. Consult your database documentation to determine the JDBC class name and connection string for yourPentaho Repository database.

  2. Navigate to the pentaho-server/tomcat/webapps folder and use a ZIP extraction utility (such as 7-Zip, Winzip, or Archive) to view the contents of the pentaho.war file.

  3. Open the context.xml file with any text editor.

  4. Add the following code to the file if it does not already exist.

    <Resource validationQuery="select 1" url="jdbc:sqlserver://localhost:1433;DatabaseName=hibernate" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" password="password" username="hibuser" initialSize="0" maxActive="20" maxIdle="10" maxWait="10000" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" type="javax.sql.DataSource" auth="Container" name="jdbc/Hibernate"/>
    <Resource validationQuery="select 1" url="jdbc:sqlserver://localhost:1433;DatabaseName=hibernate" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" password="password" username="hibuser" initialSize="0" maxActive="20" maxIdle="10" maxWait="10000" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" type="javax.sql.DataSource" auth="Container" name="jdbc/Audit"/>
    <Resource validationQuery="select 1" url="jdbc:sqlserver://localhost:1433;DatabaseName=quartz" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" password="password" username="pentaho_user" testOnBorrow="true" initialSize="0" maxActive="20" maxIdle="10" maxWait="10000" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" type="javax.sql.DataSource" auth="Container" name="jdbc/Quartz"/>
    <Resource validationQuery="select 1" url="jdbc:sqlserver://localhost:1433;DatabaseName=pentaho_operations_mart" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" password="password" username="pentaho_operations_mart" initialSize="0" maxActive="20" maxIdle="10" maxWait="10000" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" type="javax.sql.DataSource" auth="Container" name="jdbc/pentaho_operations_mart"/>
    <Resource validationQuery="select 1" url="jdbc:sqlserver://localhost:1433;DatabaseName=pentaho_operations_mart" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" password="password" username="pentaho_operations_mart" initialSize="0" maxActive="20" maxIdle="10" maxWait="10000" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" type="javax.sql.DataSource" auth="Container" name="jdbc/PDI_Operations_Mart"/>
    <Resource name="jdbc/live_logging_info" auth="Container" type="javax.sql.DataSource" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" initialSize="0" maxActive="20" maxIdle="10" maxWait="10000" username="dilogs_user" password="password" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" url="jdbc:sqlserver://localhost:1433;DatabaseName=pentaho_dilogs" validationQuery="select 1"/>
  5. Modify the username, password, driver class information, IP address (or domain name), and port numbers so they reflect the correct values for your environment.

  6. Make sure that the validationQuery variable for your database is set to this: validationQuery="select 1"

  7. Save the context.xml file, then close it.

  8. The ZIP extraction utility that you used might show a prompt which asks whether you would like to update the file in the pentaho.war archive.

    1. Confirm that you would like to update the file.

  9. Clear the tomcat/work and tomcat/temp directories.

Next steps

After installing the database that will host the Pentaho Repository, the next step depends on which type of web application server you are using, either JBoss or Tomcat.