It covers the following topics:
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 Configuring the Scheduler.
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.
You can install Apache ActiveMQ version 5.2.0 or later in Windows, UNIX, or Linux.
Follow the installation steps documented in the ActiveMQ documentation.
Update the activemq.xml configuration file to 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:
failover://tcp://localhost:61616
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
.
Open the Scheduler Configuration page from the BI Publisher Administration page.
failover://tcp://localhost:61616
.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
.
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.
DataDirect Connect for JDBC drivers are provided for supported databases
Supported databases include:
IBM DB2 v8.1, v9.1
Microsoft SQL Server 2000, 2005
Sybase Adaptive Server Enterprise
Oracle 9i, Oracle 10g, Oracle 11g,
Note:
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.
The table below displays the driver recommendations for the supported scheduler databases.
Database | Native JDBC Driver | DataDirect JDBC Driver |
---|---|---|
Oracle 10g, Oracle 11g |
Recommended |
Supported |
IBM DB2 v8.1, v9.1 |
Supported |
Recommended |
Microsoft SQL Server 2000, 2005 |
Supported |
Recommended |
Sybase Adaptive Server Enterprise |
Supported |
Recommended |
MySQL 4.1.10a-NT, 5.0 |
Supported |
Not Supplied |
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.
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:
When connecting to an Oracle database, 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":
SQL> CREATE USER bipuser 2 IDENTIFIED BY welcome 3 DEFAULT TABLESPACE USERS 4 TEMPORARY TABLESPACE TEMP 5 QUOTA 20G ON USERS 6 QUOTA 1M ON TEMP; User created. SQL> GRANT CREATE SESSION TO bipuser; -- or "GRANT CONNECT TO bipuser;" Grant succeeded. SQL> grant create table to bipuser; Grant succeeded.
The table below describes the fields for the Oracle native driver to connect to the Oracle Database.
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: |
oracle.jdbc.driver.OracleDriver |
When connecting to an IBM DB2 v8 or IBM DB2 v9 database, 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.
The table below describes the fields for the DataDirect driver to connect to an IBM DB2 v8 or IBM DB2 v9 database.
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: |
hyperion.jdbc.db2.DB2Driver |
When connecting to a Microsoft SQL Server database, 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.
The table below describes the fields for the DataDirect driver to connect to a Microsoft SQL Server 2000 or 2005 database.
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: |
Database Driver Class: |
hyperion.jdbc.sqlserver.SQLServerDriver |
When connecting to an Sybase Adaptive Server Enterprise database, ensure that you set the "ddl in tran" mode to true in the database. Consult the Sybase documentation or contact your database administrator for instructions on how to enable this option.
The table below describes the fields for the DataDirect driver to connect to a Sybase Adaptive Server Enterprise database.
Field | Entry |
---|---|
Database Type: |
Select Sybase Adaptive Server Enterprise from the list. |
Connection String: |
Enter the following connection string parameters: |
Database Driver Class: |
hyperion.jdbc.sybase.SybaseDriver |