|Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher|
Release 11g (11.1.1)
Part Number E13880-02
This appendix 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 may need to reference this information in the following scenarios:
You are upgrading from a 10g release to the 11g release
You are running a separate installation of BI Publisher and wish 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
Oracle BI Publisher must be installed on the same server with the other components of Oracle BI Enterprise Edition.
The security configuration must be either Oracle Fusion Middleware security or Oracle BI Server security.
To manually configure BI Publisher to use the Oracle BI Presentation Catalog, perform the following:
On the Server Configuration page in the Catalog region, select Catalog Type: Oracle BI EE Catalog
Enter the following:
Server Version - v6
BISystemUser is a fixed user created during installation for trusted communication between components.
Enter the password for BISystemUser.
Connection Protocol - TCP
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 will upload the contents of your 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 hostname, port, and URL suffix values. Furthermore, the username and password fields will be hidden because both products will be configured to use Oracle Fusion Middleware security.
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 will be 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
Note: If your deployment is configured for SSO, 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
Note: If you installed BI Publisher with the Oracle BI Enterprise Edition, this data source will be automatically configured.
To add the Oracle BI Enterprise Edition server as a JDBC data source, follow the guidelines in Adding a JDBC Data Source in conjunction with these specific guidelines.
You must use the BISystemUser user name and password for connection to the BI Server.
Note that if your Oracle BI Server is SSL-enabled, 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 your Oracle BI Server is SSL-enabled, you must copy the keystore to the BI Publisher server and provide it in the connection string. For more information on SSL, see the Oracle Fusion Middleware Security Guide for Business Intelligence.
The URL for the connection string requires the following format:
<URL>:= <Prefix>: [//<Host>:<Port>/][<Property Name>=<Property Value>;]*
<Prefix>: is the string jdbc:oraclebi
<Host>: is the hostname of the analytics server. It can be an IP Address or hostname. The default is localhost.
<Port> is he 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> - can be any catalog name that is available on the server. If the catalog is not specified, then it will default to the default catalog specified by the server. If the catalog name is not found in the server, it will still use the default catalog and issue a warning during connect.
<User> - specifies the username for the BI Server. The default is "Administrator".
<Password> - specifies the password for the BI Server for the username. The password will be encrypted using 3DES.
<SSL> True|False - default is False. Specifies if the JDBC driver will use SSL or not. If true, the driver will check if SSLKeyStoreFileName is readable; if not, it will issue an error message.
<SSLKeyStoreFileName> - 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> - 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 will verify 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> - specify 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 will create a new entry marked as _0, _1 if the same file name already 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 will try 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 will try 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 Proxy Authentication - (Required) select this box. Proxy authentication is required.
Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved.