This chapter describes how to configure the Business Intelligence (BI) Publisher for reporting with Oracle Enterprise Repository.
This chapter contains the following sections:
Section 16.1, "Deploy Oracle Enterprise Repository Pre-configured BI Publisher Content"
Section 16.3, "Configuring the Oracle Enterprise Repository JDBC Data Source"
Section 16.4, "Configuring the BI Publisher Server - Cache Expiration"
Section 16.5, "Configuring the Oracle Enterprise Repository System Settings to Enable Reporting"
Oracle Enterprise Repository is the entry point for all the reports. To host reports, you must configure BI Publisher and Oracle Enterprise Repository to interact with each other.
Note:
These instructions assume that BI Publisher 11g is installed, which is dedicated only for hosting Oracle Enterprise Repository reports.
BI Publisher uses a repository internal to BI Publisher to host the users, roles, reports, and configuration for BI Publisher. This repository is replaced by the BI Publisher content which has been specifically developed for the integration with Oracle Enterprise Repository.
Note:
Do not attempt to migrate your 10g reports to 11g.
To deploy the Oracle Enterprise Repository-BI Publisher content, perform the following steps:
Find a packaged content archive for your database. You can find the reports in the Oracle Enterprise Repository Deployment in the <ORACLE_HOME>/repositoryXXX/core/tools/solutions/reports directory.
In this directory you will find 11.1.1.7.0-OER-BIP11gReports.zip. It contains three folders corresponding to each database. Each folder contains only the OER reports.
Stop your BI Publisher application server.
Copy the OER folder from the appropriate database folder into the BI Publisher Reports directory:
domain/config/bipublisher/repository/Reports.
Restart your BI Publisher application server.
Check your BI Publisher configuration by opening the web console http://hostname:port/xmlpserver. Verify that the OER folder appears in the Shared Folders directory.
BI Publisher uses Enterprise Manager to manage users and roles rather than its own security model. For more information about the security model, see the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher .
The Administrator user and password are determined during installation. This user and password are required to setup the database connection to OER as well as configure the OER user and role, and to setup the data sources in BI Publisher.
Note:
In BI Publisher, the password is case sensitive.
Use the BI Publisher WLS console to create an OER user. Apply the BI groups to this user. Verify the user account by logging into the BI Publisher console with the OER user credentials. View the reports in the Shared Folders->OER folder.
For the correct time zone to display on report footers, set the time zone in BI Publisher for the OER User account.
Sign in as the OER User and select my account link to modify the Time Zone setting, located on the Signed In As <username> link at the upper right section of the BI Publisher console.
To update the JDBC information, perform the following steps:
Log into BI Publisher as an administrator.
Click the Admin tab.
In the Data Sources section, select OER - the JDBC Connection link.
Note:
This is case-sensitive.
In the Update Data Source screen, change the connection string to point to the database for Oracle Enterprise Repository. Use the same ConnectString as what appears in the Oracle Enterprise Repository database.properties file. Use the same database authentication as Oracle Enterprise Repository.
In a WebLogic domain, the database.properties file is found in <domain>/applications/oer_11.1.1.x.0/oer-app/WEB-INF/classes.
These sections describe the database configuration for the following databases:
Click the Test Connection button to confirm that BI Publisher can access the database.
Click Apply to save the changes.
You can select either of the following Driver types for Oracle Database depending on your Oracle database version. The JDBC library file (JAR) is installed as part of the BI Publisher Server installation therefore no extra Jar file is required.
Oracle 11g
Oracle 10g
Oracle 9i
Example for Oracle JDBC Connection:
|
Database Driver Class |
oracle.jdbc.OracleDriver |
|---|---|
|
Connect String |
jdbc:oracle:thin:@[HOST]:[PORT]:[DB_NAME] |
|
Example |
jdbc.oracle.thin:@machine.example.com:1521:oer |
You can select either of the following Driver types for SQL Server Database depending on your SQL Server database version. The JDBC library file (JAR) is installed as part of the BI Publisher Server installation therefore no extra Jar file is required.
Microsoft SQL Server 2005
Microsoft SQL Server 2000
Example for SQL Server JDBC Connection:
|
Database Driver Class |
hyperion.jdbc.sqlserver.SQLServerDriver |
|---|---|
|
Connect String |
jdbc:hyperion:sqlserver://[HOST]:[PORT];DatabaseName=[DB_NAME] |
|
Example |
jdbc:hyperion:sqlserver://machine.example.com;databaseName=oer |
You can select either of the following Driver types for IBM DB2 Universal Database depending on your DB2 database version. The JDBC library file (JAR) is installed as part of the BI Publisher Server installation therefore no extra Jar file is required.
IBM DB2 Universal Database v9
IBM DB2 Universal Database v8
Example for UDB JDBC Connection:
|
Database Driver Class |
hyperion.jdbc.db2.DB2Driver |
|---|---|
|
Connect String |
jdbc:hyperion:db2://[hostHOST]:[portPORT];DatabaseName=[dbnameDB_NAME] |
|
Example |
jdbc:hyperion:db2://machine.example.com;DatabaseName=oer |
By default, all Oracle Enterprise Repository reports uses Document Caching to reduce database roundtrips on the generation of report data. While the data is cached, the rendered report may not always show the most recent activities in Oracle Enterprise Repository. Setting the cache expiration changes depending on how frequently BI Publisher needs to refresh the data for the second and subsequent rendering of a report. The default value in BI Publisher for the cache expiration is 30. To change this value, follow the following steps:
Log into BI Publisher as an administrator.
Click the Admin tab.
In the System Maintenance section, select the Server Configuration link.
In the Caching section, specify a Cache Expiration (in minutes) and click Apply apply the changes.
Note:
When reports are rendered by BI Publisher, the result is dependent upon the data found for the report. Until data is present, the reports returned by BI Publisher may be inconsistent.
Oracle Enterprise Repository contains a report page with a series of links to a set of reports. These reports are hosted by a BI Publisher instance, which must be installed and configured to host the reports. All of the links in the Oracle Enterprise Repository Reports page are incomplete following an Oracle Enterprise Repository installation. There is a system setting that provides the protocol, hostname, port, web application name, and parent directory for all of the report links. The system setting must be configured prior to running any reports.
Log into Oracle Enterprise Repository as a user with the System Administrator or the Admin role.
In Oracle Enterprise Repository Administration page, click System Settings.
In the Search text box, enter report to filter the list of system settings.
In the Reports section, set Enable Reports (cmee.reports.enabled) to True.
Set the Report Server URL (oracle.reports.server.url) to http:/</HOSTNAME>:<PORT>/xmlpserver/OER, where hostname and port match the BI Publisher installation.
If the Report Server URL property is not properly configured, then the Reports page displays the following message:
Please set the system setting for Report Server URL. Reports cannot be run until this has been properly set.
Set the system setting Report Server Endpoint URL (oracle.reports.server.endpoint.url) to http:/<HOSTNAME>:<PORT>/xmlpserver/services/PublicReportService to enable OER users to access BI Publisher reports without needing an extra set of credentials.
OER users' access to reports is set via Basic Access Settings, as described in Section 1.6, "Access Settings."
Set the system settings Report Server Username and Report Server Password to the username and password of the OER BI Publisher account created in Section 16.2.2, "The OER User and OER_REPORTS Role."
Save the system settings.
Validate that the system settings are configured properly by navigating to the Reports section.
Run any report.
If the browser does not retain an active session to BI Publisher, then the BI Publisher's Login screen is displayed. After you have successfully logged into BI Publisher, the report is displayed.
Running the report opens a new browser window to the URL for BI Publisher. Comparing the URL generated by Oracle Enterprise Repository to the URL generated by BI Publisher should be an aid in diagnosing any configuration errors of the Report Server URL System Setting.
Repeat the steps mentioned in this section, until the report runs successfully. If the report returns with "No Search Results Found", then run some keyword searches in the Assets tab of Oracle Enterprise Repository.
Note:
If Internet Explorer returns a different report than the one requested, then change the Temporary Internet Files to check for changes on Every Visit.