A Scheduler Configuration Reference

This appendix describes how to configure the BI Publisher scheduler for each supported database and how to configure ActiveMQ as the JMS provider.

It covers the following topics:

A.1 Introduction

The Oracle Business Intelligence Platform Installer configures the connection to the scheduler and installs the scheduler schema to your selected scheduler database. The WebLogic JMS queues are set up and the scheduler is up and running after installation is complete and the servers have been started.

This information in this appendix is provided for reference for manually configuring the scheduler and for setting up ActiveMQ as an alternative JMS provider.

For conceptual information about the scheduler, information for installing and configuring additional managed servers, and a description of the scheduler diagnostics page, see Chapter 7, "Configuring the Scheduler."

A.2 Configuring BI Publisher for ActiveMQ

The scheduler is configured by default to use WebLogic JMS. The scheduler also supports ActiveMQ as an alternative JMS provider. Use these guidelines with the ActiveMQ documentation to configure BI Publisher if you choose to use ActiveMQ as the JMS provider.

A.2.1 Install ActiveMQ

It is recommended that you install ActiveMQ version 5.2.0 or later. This can be installed in Windows, UNIX or Linux. Follow the installation steps documented at the following location:


A.2.2 Register ActiveMQ as a JNDI Service

When you start ActiveMQ, the queues can be accessed using JNDI service.

The default URL to access this service is:


To change this configuration, update the activemq.xml configuration file found in apache-activemq-x.x.x\conf for example: apache-activemq-5.2.0\conf.

A.2.3 Update the BI Publisher Scheduler Configuration Page

To update the Scheduler Configuration page:

  1. On the BI Publisher Administration page, under System Maintenance, click Scheduler Configuration.

  2. Under the JMS Configuration region, select ActiveMQ.

  3. Enter the ActiveMQ JNDI URL. For example: failover://tcp://localhost:61616

  4. Enter the threads per processor (for example: 5).

  5. Enter the path to a shared temporary directory.

  6. Click Test JMS to test the connection.

  7. Click Apply to apply the changes to this page.

The ActiveMQ URL is dynamically applied. The queues and topics are automatically created in ActiveMQ and are ready for scheduling. You can confirm the queues by checking them in the Scheduler Diagnostics page. Alternatively, you can check the status in the ActiveMQ Web console: http://localhost:8161/admin.

A.3 Manually Configuring the Quartz Scheduler

BI Publisher includes the Hyperion-branded DataDirect Connect for JDBC drivers to setup a connection to install and use the scheduler tables in your database. These drivers can be used as an alternative to the native JDBC drivers provided by your database vendor. When you choose a database for which a DataDirect driver is available, BI Publisher automatically enters the database driver class information in the setup screen for you. There is no additional setup required for the driver files.

If you choose to use a data direct driver not provided by the BI Platform Installer, then you must download, install, and configure the driver manually.

A.3.1 Recommendations for Using DataDirect Connect or Native Database Drivers

DataDirect Connect for JDBC drivers are provided for the following databases:

  • IBM DB2 v8.1, v9.1

  • Microsoft SQL Server 2000, 2005

  • Sybase Adaptive Server Enterprise

  • Oracle 9i, Oracle 10g, Oracle 11g,


Some database options listed here and in the Scheduler page might not be supported in this release. See "System Requirements and Certification" for the most up-to-date information on supported hardware and software.

Table A-1 displays the driver recommendations for the supported scheduler databases.

Table A-1 Driver Recommendations

Database Native JDBC Driver DataDirect JDBC Driver

Oracle 10g, Oracle 11g



IBM DB2 v8.1, v9.1



Microsoft SQL Server 2000, 2005



Sybase Adaptive Server Enterprise



MySQL 4.1.10a-NT, 5.0


Not Supplied

A.3.2 Set Up a User on Your Scheduler Database

To set up the connection to the scheduler database, you must ensure that you have created a user on the selected database. BI Publisher uses this user to connect to the database. Depending on the database type, this user might require specific privileges. These are detailed in the database-specific sections later in this appendix.

A.3.3 Connecting to Your Scheduler Database and Installing the Schema

Following are the general steps for setting up the Scheduler database. Also refer to the subsequent section that is specific to your database.

To set up the Scheduler database:

  1. Log in to BI Publisher with Administrator credentials and select the Administration tab.

  2. Under System Maintenance, click Scheduler Configuration.

  3. In the Scheduler Selection region, select Quartz.


    The option "Enterprise Scheduler Services" is reserved for Oracle Fusion Applications.

  4. Enter the following fields for the Database Connection:

    • Database Type — Select the database from the list. After you make a selection, the Database Driver Class field automatically updates with the recommended driver class.

    • Connection String — Enter the connection string for your selected database. Sample strings are provided in the database-specific sections that follow.

    • Username and Password — Enter the scheduler user you set up for your database. The user must have permissions to connect to the database and create tables. Other permissions might be required depending on the database type. See the appropriate database-specific section later in this chapter.

    • Database Driver Class — When you select the database type this field is automatically updated with the recommended driver. If you want to use another driver, then specify it in this field.


      Note: The Oracle database drivers and the DataDirect drivers are installed with BI Publisher and no further setup is required. Note that for other databases, even though the recommended native drivers are automatically populated in this field, additional setup is required to make the drivers available to BI Publisher.

  5. Click Test Connection to ensure that BI Publisher can connect to the database. If the connection fails, ensure that you have entered the fields as shown and set up your database appropriately.

  6. Click Install Schema to install the BI Publisher scheduler schema to your database.

A.3.4 Connecting to Oracle Database

Prerequisite: Ensure that the database user you enter has "connect" or "create session" and "create table" privileges and that the user has been assigned a quota (otherwise the quota is 0).

For example, the following sample creates the user "bipuser":

   2  IDENTIFIED BY welcome
User created. 


 Grant succeeded. 

 SQL> grant create table to bipuser; 
 Grant succeeded.

Table A-2 describes the fields for the Oracle native driver to connect to the Oracle Database.

Table A-2 Oracle Native Driver Fields

Field Description

Database Type:

Select Oracle 11g or Oracle 10g from the list.

Connection String:

Enter the following connection string parameters: jdbc:oracle:thin:@<hostname>:<port>:<oracle SID> For example: jdbc:oracle:thin:@mydatabaseserver.com:1521:bipscheduler

Database Driver Class:


A.3.5 Connecting to IBM DB2

Prerequisite: Ensure that the user that you enter to configure the scheduler has been set up with a 32 K page size tablespace. If not, create the table and assign it to the user. The user must also have "Connect to database" and "Create tables" privileges.

Table A-3 describes the fields for the DataDirect driver to connect to an IBM DB2 v8 or IBM DB2 v9 database.

Table A-3 DataDirect Driver Fields for IBM Databases

Field Entry

Database Type:

Select IBM DB2 v9 or IBM DB2 v8 from the list.

Connection String:

Enter the following connection string parameters:jdbc:hyperion:db2://<hostname>:<port>;DatabaseName=<DATABASENAME> For example: jdbc:hyperion:db2:// mydatabaseserver.com:1433;DatabaseName=bipscheduler

Database Driver Class:


A.3.6 Connecting to Microsoft SQL Server

Prerequisite: Ensure that the Microsoft SQL Server is set up with mixed mode authentication. Also ensure that the user that you enter to configure the scheduler has the "db_owner" role.

Table A-4 describes the fields for the DataDirect driver to connect to a Microsoft SQL Server 2000 or 2005 database.

Table A-4 DataDirect Driver Fields for SQL Server Databases

Field Entry

Database Type:

Select Microsoft SQL Server 2000 or Microsoft SQL Server 2005 from the list.

Connection String:

Enter the following connection string parameters: jdbc:hyperion:sqlserver://<hostname>:<port>;DatabaseName=<DATABASENAME> For example: jdbc:hyperion:sqlserver:// mydatabaseserver.com:1433;DatabaseName=bipscheduler

Database Driver Class:


A.3.7 Connecting to Sybase Adaptive Server Enterprise Database

Prerequisite: Ensure that you set the "ddl in tran" mode to true in the database. Consult the Sybase documentation or contact your database administrator for instruction how to enable this option.

Table A-5 describes the fields for the DataDirect driver to connect to a Sybase Adaptive Server Enterprise database.

Table A-5 DataDirect Driver Fields for Sybase Database

Field Entry

Database Type:

Select Sybase Adaptive Server Enterprise from the list.

Connection String:

Enter the following connection string parameters: jdbc:hyperion:sybase://<hostname>:<port>;DatabaseName=<DATABASENAME> For example: jdbc:hyperion:sybase://mydatabaseserver.com:4100;DatabaseName=bipscheduler

Database Driver Class: