Overview

Tasks performed during this step include configuring Audit, Quartz, and Hibernate properties. Tasks are grouped by the DI Repository database you have.

Configure PostgreSQL DI Repository Database

These instructions explain how to configure Quartz, Hibernate, Jackrabbit, and Pentaho Security for use with the PostgreSQL database. By default, the files edited in this section are configured for a PostgreSQL database that runs on port 5432. The default password is also in these files. If you have a different port, different password, or if had the system configured using a different database and now you want to change it back to PostgreSQL, complete all of the instructions in these steps.

Configure Quartz on PostgreSQL DI Repository Database

When you use Pentaho to schedule an event, such as a report to be run every Sunday at 1:00 a.m. EST, event information is stored in the Quartz JobStore. During the installation process, you must indicate where the JobStore is located. To do this, modify the quartz.properties file.

Open the pentaho/server/data-integration-server/pentaho-solutions/system/quartz/quartz.properties file in the text editor of your choice.

Make sure that in the #_replace_jobstore_properties section of the file, the org.quartz.jobStore.driverDelegateClass is set to org.quartz.impl.jdbcjobstore.PostgreSQLDelegate.

In the # Configure Datasources section of the file, set the org.quartz.dataSource.myDS.jndiURL equal to Quartz.

org.quartz.dataSource.myDS.jndiURL = Quartz

Save the file and close the text editor.

Configure Hibernate Settings for PostgreSQL DI Repository Database

Modify the hibernate settings file to specify where Pentaho will find the DI 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.

Open pentaho/server/data-integration-server/pentaho-solutions/system/hibernate/hibernate-settings.xml in a text editor.

Verify that the location of the PostgreSQL hibernate configuration file appears. Make changes if necessary.

Save the file if you had to make changes, then close it. Otherwise, just close it.

Open pentaho/server/data-integration-server/pentaho-solutions/system/hibernate/postgresql.hibernate.cfg.xml in a text editor.

Make sure that the password and port number match the ones you specified in your configuration. Make changes as necessary, then save and close the file.

Modify Jackrabbit DI Repository Information for PostgreSQL

Indicate which database houses the DI Repository as well as the port, url, username, and password. All of the information needed to configure the repository for the PostgreSQL, MySQL, and Oracle DI Repository databases appear. By default, the PostgreSQL sections are not commented out, but the MySQL and Oracle sections are. To modify this file so that it works for your DI Repository, you will need to make sure that the sections that refer to your DI Repository database are not commented out, and the sections refer to other DI Repository databases are commented out.

When code is commented out, it appears between the <!-- and --> tags. The information in between the tags is commented out, and is therefore not executed by the software. In this example, the code <! <FileSystem class=”org.apache.jackrabbit.core.fs.db.OracleFileSystem”> is commented out.

Note: If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly.

In the Persistence Manager section of the code that is near the end of the file, verify that PostgreSQL lines of code are not commented out, but the MySQL and Oracle lines are. The codes should look like this.

Note: If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly.

Close and save the file.

Configure MySQL DI Repository Database

These instructions explain how to configure Quartz, Hibernate, Jackrabbit, and Pentaho Security for a MySQL database.

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

Set Up Quartz on MySQL DI 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.

Open the pentaho/server/biserver-ee/pentaho-solutions/system/quartz/quartz.properties file in any text editor.

Locate the #_replace_jobstore_properties section and set the org.quartz.jobStore.driverDelegateClass as shown here.

Set Hibernate Settings for MySQL

Modify the hibernate settings file to specify where Pentaho should find the DI Repository’s hibernate-settings config file. The hibernate-settings config 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/data-integration/pentaho-solutions/system/hibernate directory.

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

Modify Jackrabbit Repository Information for MySQL

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

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

Following the table below, locate and change the code so that the MySQL lines are not commented out, but the PostgreSQL and Oracle lines are commented out.

If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters in each section accordingly.

Prepare Oracle DI Repository Database

These instructions explain how to configure Quartz, Hibernate, Jackrabbit, and Pentaho Security. By default, the examples in this section are for a Oracle database that runs on port 1521. The default password is also in these examples. If you have a different port, different password complete all of the instructions in these steps.

Configure Quartz on Oracle DI Repository Database

When you use Pentaho to schedule an event, such as a report to be run every Sunday at 1:00 a.m. EST, event information is stored in the Quartz JobStore. During the installation process, you must indicate where the JobStore is located. To do this, modify the quartz.properties file.

Open the pentaho/server/data-integration-server/pentaho-solutions/system/quartz/quartz.properties file in the text editor of your choice.

In the #_replace_jobstore_properties section of the file, set the org.quartz.jobStore.driverDelegateClass equal to org.quartz.impl.jdbcjobstore.oracle.OracleDelegate.

In the # Configure Datasources section of the file, set the org.quartz.dataSource.myDS.jndiURL equal to Quartz.

org.quartz.dataSource.myDS.jndiURL = Quartz

Save the file and close the text editor.

Configure Hibernate Settings for Oracle

Modify the hibernate settings file to specify where Pentaho will find the DI 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.

Open pentaho/server/data-integration-server/pentaho-solutions/system/hibernate/hibernate-settings.xml in a text editor. By default, the location of the PostgreSQL database configuration file is specified.

Open pentaho/server/data-integration-server/system/hibernate/oracle10g.hibernate.cfg.xml in a text editor.

Make sure that the password and port number match the ones you specified in your configuration. Make changes as necessary, then save and close the file.

Replace Default Version of Audit Log File with Oracle Version

The default audit_sql.xml file that is in the pentaho-solutions/system directory is configured for the PostgreSQL database. Since you are using Oracle to host the DI Repository, you need to replace the audit_sql.xml file with one that is configured for Oracle. To do this, copy the pentaho-solutions/system/dialects/oracle10g/audit_sql.xml file to the pentaho-solutions/system directory.

Modify Jackrabbit Repository Information for Oracle

You must indicate which database is used as the DI Repository as well as the port, url, username, and password. All of the information needed to configure the repository for the PostgreSQL, MySQL, and Oracle DI Repository databases appear. By default, the PostgreSQL sections are not commented out, but the MySQL and Oracle sections are. To modify this file so that it works for your DI Repository, you will need to make sure that the sections that refer to your DI Repository Database are not commented out, and the sections refer to other DI Repository databases are commented out.

When code is commented out, it appears between the <!-- and --> tags. The information in between the tags is commented out, and is therefore not executed by the software. In this example, the code <! <FileSystem class=”org.apache.jackrabbit.core.fs.db.OracleFileSystem”> is commented out.

Note:If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly. Also note that the <param name="url" value="jdbc:oracle:thin:@localhost:1521:orcl"/> parameter indicates that the database is named orcl. Modify the parameter if your database has a different name.

Note:If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly. Also note that the <param name="url" value="jdbc:oracle:thin:@localhost:1521:orcl"/> parameter indicates that the database is named orcl. Modify the parameter if your database has a different name.

Note:If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly. Also note that the <param name="url" value="jdbc:oracle:thin:@localhost:1521:orcl"/> parameter indicates that the database is named orcl. Modify the parameter if your database has a different name.

Note:If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly. Also note that the <param name="url" value="jdbc:oracle:thin:@localhost:1521:orcl"/> parameter indicates that the database is named orcl. Modify the parameter if your database has a different name.

Note:If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly. Also note that the <param name="url" value="jdbc:oracle:thin:@localhost:1521:orcl"/> parameter indicates that the database is named orcl. Modify the parameter if your database has a different name.

In the Persistence Manager section of the code that is near the end of the file, change the code so that the Oracle lines of code are not commented out, but the PostgreSQL and MySQL lines are, like this.

Note:If you changed your password when you initialized the database during the Prepare Environment step, or if your database is on a different port, edit the url and password parameters accordingly. Also note that the <param name="url" value="jdbc:oracle:thin:@localhost:1521:orcl"/> parameter indicates that the database is named orcl. Modify the parameter if your database has a different name.