It covers the following topics:
The information in this chapter is for reference to highlight the integration points between BI Publisher and the Oracle BI Enterprise Edition.
You might need to reference this information in the following scenarios:
You are upgrading from a 10g release to the 11g release
You run a separate installation of BI Publisher and want to integrate it
You need to modify the installed configuration
The points of integration discussed in this chapter are:
Connecting to Oracle BI Server as a data source
Configuring BI Publisher to use the Oracle BI Presentation Catalog
Configuring integration with Oracle BI Presentation Services
To manually configure BI Publisher to use the Oracle BI Presentation Catalog:
On the Server Configuration page in the Catalog region, select Catalog Type: Oracle BI EE Catalog
Enter the following:
Server Version - v7
Leave these fields blank.
BI Publisher uses the BISystemUser and password to connect to the BI Presentation Catalog. The BISystemUser is a fixed user created during installation for trusted communication between components. Typically, these fields are configured at installation and are no longer visible from this configuration page. If you are manually configuring the integration between BI Publisher and BI Presentation Catalog and these fields are visible, you can leave them blank, as BI Publisher automatically reads the values from the security store.
Connection Protocol — TCP
If you are manually configuring BI Publisher to use the BI Presentation Catalog, you may see the fields System Username and System Password. These fields can be left blank, as these values are automatically read by BI Publisher from the security store.
Click Test Connection to ensure BI Publisher can connect to Oracle BI Presentation Services.
Enter the path of the current BI Publisher repository.
Click Upload to BI Presentation Catalog. This action uploads the contents of the BI Publisher catalog to the BI Presentation catalog.
Restart the BI Publisher application.
When you install Oracle BI Enterprise Edition the integration with BI Publisher is automatically configured. This means that the Oracle BI Platform installer sets the Presentation Services host name, port, and URL suffix values. Furthermore, the username and password fields are hidden, because both products are configured to use Oracle Fusion Middleware security.
To configure integration with Presentation Services:
From the Administration page, under Integration, click Oracle BI Presentation Services.
Enter the following information about your BI Presentation Services server:
Server Protocol — Select http or https
Server Version — Select v6
Server — Enter the server host name. For example: BIEEServer
Port for the server where the BI Presentation Services plug-in is running. For example: 9704
Administrator Username and Password — These fields are hidden when using Oracle Fusion Middleware Security. If you are manually configuring the integration, enter the BISystemUser username and password.
URL Suffix — Default value is: analytics/saw.dll
If your deployment is configured for SSO, then the suffix must be entered as "analytics-ws/saw.dll" to allow the Web services between BI Publisher and BI Presentation Services. For more information on configuring SSO for Oracle BI Enterprise Edition, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
Session time out in minutes
If you installed BI Publisher with the Oracle BI Enterprise Edition, then this data source is automatically configured.
To add the Oracle BI Enterprise Edition server as a JDBC data source, follow the guidelines in Section 9.2, "Setting Up a JDBC Connection to the Data Source" with these specific guidelines.
Note that if your Oracle BI Server is SSL-enabled, then you must copy the keystore to the BI Publisher server and provide it in the connection string.
The entries for Database Driver Class and Connection String must be as follows:
Database Driver Class — oracle.bi.jdbc.AnaJdbcDriver
Connection String — The appropriate connection string depends on your specific deployment. Clustered and SSL-enabled deployments require specific parameters to construct the URL. For example, if the Oracle BI Server is SSL-enabled, then you must copy the keystore to the BI Publisher server and provide it in the connection string. For more information on SSL, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
The URL for the connection string requires the following format:
<URL>:= <Prefix>: [//<Host>:<Port>/][<Property Name>=<Property Value>;]*
<Prefix> — The string jdbc:oraclebi
<Host> — The hostname of the analytics server. It can be an IP Address or hostname. The default is localhost.
<Port> — The port number that the server is listening on. The default is 9703.
<Property Name>:= <Catalog>|<User>|<Password>|<SSL>|<SSLKeyStoreFileName> |<SSLKeyStorePassword>|<TrustAnyServer>|<TrustStoreFileName >|<TrustStorePassword>|<LogLevel>|<LogFilePath>|<PrimaryCCS>|<PrimaryCCSPort>| <SecondaryCCS>|<SecondaryCCSPort>
Valid property values are:
<Catalog> — Any catalog name that is available on the server. If the catalog is not specified, then it defaults to the default catalog specified by the server. If the catalog name is not found in the server, then it still uses the default catalog and issues a warning during connect.
<User> — Specifies the user name for the BI Server. The default is "Administrator".
<Password> — Specifies the password for the BI Server for the user name. The password is encrypted using 3DES.
<SSL> True|False — Default is False. Specifies if the JDBC driver uses SSL or not. If true, then driver checks whether SSLKeyStoreFileName is readable; if not, it issues an error message.
<SSLKeyStoreFileName> — Specifies the name of the file that store the SSL Keys. This file must exist in the local file system and be readable by the driver.
<SSLKeyStorePassword> — Specifies the password to open the file pointed to by SSLKeyStoreFileName.
<TrustAnyServer> - True | False — The default is False. If SSL is set to "True" the property specifies whether to check the trust store for the server. If TrustAnyServer is set to "False", the driver verifies that TrustStoreFileName is readable.
<TrustStoreFileName> — If TrustAnyServer is set to false, this property is required to specify the trust store file name.
<TrustStorePassword> — If TrustAnyServer and TrustStoreFileName are specified, this property specifies the password to open up the file specified by TrustStoreFileName.
<LogLevel> — Specifies the log level. Valid values are
SEVERE | WARNING | INFO | CONFIG | FINE | FINER | FINEST
<LogFilePath> — Specifies the file path of the desired logging destination. Default is %TEMP% on windows, $TMP on UNIX. Driver needs to have write permission on the file. It creates a new entry marked as _0, _1 if the same file name exists.
<PrimaryCCS> — (For clustered configurations) specifies the primary CCS machine name instead of using the "host" to connect. If this property is specified, the "host" property value is ignored. The jdbc driver tries to connect to the CCS to obtain the load-balanced machine. Default is localhost.
<PrimaryCCSPort> — Specifies the primary CCS port number running on the PrimaryCCS machine. Default is 9706.
<SecondaryCCS> — Specifies the secondary CCS machine name instead of using the "host" to connect. If this property is specified, then the jdbc driver trues to connect to the CCS to obtain the load-balanced machine. Default is localhost.
<SecondaryCCSPort> — Specifies the secondary CCS port number running on the secondary machine. Default is 9706.
Following is an example connection string for a clustered deployment with SSL enabled:
Use System User - you must select this box to use the BISystem User. When you select this box, BI Publisher will use the BISystem Username and password to connect to the BI Server. The Username and Password fields are no longer editable.
Username - leave blank
Password- leave blank
Use Proxy Authentication — (Required) select this box. Proxy authentication is required.