| Oracle® Business Intelligence Suite Enterprise Edition Release Notes Release 10.1.3.4.2 Part Number E10404-34 |
|
|
View PDF |
| Oracle® Business Intelligence Suite Enterprise Edition Release Notes Release 10.1.3.4.2 Part Number E10404-34 |
|
|
View PDF |
Oracle Business Intelligence Suite Enterprise Edition consists of components that were formerly available from Siebel Systems as Siebel Business Analytics Platform, with many significant enhancements.
These release notes describe known issues and workarounds for versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
For information about installing and upgrading to Oracle Business Intelligence Suite Enterprise Edition Version 10.1.3.4.2, refer to the following Oracle Business Intelligence Suite Enterprise Edition documents:
Oracle Business Intelligence Infrastructure Installation and Configuration Guide Version 10.1.3.2.1
For more information on UNIX installations, see Section 1.3, "Installing or Uninstalling Oracle BI in Silent Mode Under UNIX."
Oracle Business Intelligence Enterprise Edition Deployment Guide Version 10.1.3.2
Oracle Business Intelligence Infrastructure Upgrade Guide Version 10.1.3.2
When you upgrade the Oracle BI EE platform to a new release, continue to use
the information that is provided in the Oracle Business Intelligence Infrastructure Upgrade Guide Version 10.1.3.2. For more information on upgrading, see Section 1.2, "Upgrading to This Release."
The following list describes the sections of this chapter:
These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Business Intelligence Suite Enterprise Edition Web site.
To find the Release Notes document:
Click the following link:
In the section for the latest release, click View Library.
On the Documentation Library page, click the Getting Started tab.
On the Getting Started tab, in the Release Notes section, click PDF or HTML.
When you upgrade the Oracle BI EE platform to a new release, continue to use
the information that is provided in Oracle Business Intelligence Infrastructure Upgrade Guide Version 10.1.3.2. Before you upgrade to an Oracle BI EE Release 10.1.3.2.1 or later, review Table 1-1 for information on the steps that are required for upgrading from various releases. This information relates to upgrading the Oracle BI EE platform and not to upgrading Oracle Business Intelligence Applications.
| Upgrade From | Upgrade To | Summary Steps |
|---|---|---|
|
Siebel Analytics 7.5.x, 7.7, 7.7.1.x, and 7.8.x. |
Oracle BI EE Release 10.1.3.2.1 or later |
Follow the procedures in Oracle Business Intelligence Infrastructure Upgrade Guide Version 10.1.3.2. It is not necessary to uninstall Siebel Analytics 7.5.x, 7.7, 7.7.1.x, or 7.8.x when you upgrade to Oracle BI EE Release 10.1.3.2.1 or later. It is necessary to uninstall the Siebel Analytics Microsoft Excel add-in. |
|
Oracle BI EE 10.1.3.2, |
Oracle BI EE Release 10.1.3.2.1 or later Do not move to a release lower than the one that is currently installed. |
Perform the following upgrade steps:
|
Use the procedures in this section only to uninstall Oracle BI components for reasons not related to upgrading the software. The same procedures are used both for installation and for uninstallation of Oracle BI components; only the locations from which commands are run differ.
In the so-called silent or unattended installation, Oracle Business Intelligence platform components are installed or uninstalled across a network. The administrator performs the following general steps:
Backs up all Oracle BI folders and files.
Performs a default Oracle BI installation or uninstallation on an administrator (target) computer.
During the installation or uninstallation, all the options selected and settings created are written to a text file named response.txt.
Runs a batch or shell program that uses the response file to install or uninstall the same Oracle BI components, with all the previously selected options and settings, to other servers and client workstations.
Without being modified, the response.txt file is portable only to other installation computers having the identical directory structures (including logical drives) as the initial installation computer.
Prepare for a silent installation or uninstallation by running shell scripts to create text files, as described in Section 1.3.1, "Creating a Response Text File."
This procedure initiates an installation on an administrator computer and creates an annotated response file of all your input during the installation or uninstallation. This response file has all your responses recorded during this installation.
To create a response file on UNIX systems:
Navigate to the product CD location.
Run the following command:
./setup.sh -options-record <RESPONSE_FILE_LOCATION>/response.txt -silent
where <RESPONSE FILE LOCATION> is the full path to the response file.
When prompted, provide the oc4jadmin password.
The file response.txt is created in the directory that you specified for <RESPONSE_FILE_LOCATION>.
To install or uninstall Oracle BI silently on other computers using the response.txt file:
Back up all Oracle BI folders and files.
On the target computers, run the appropriate command from the location that is specified in the following list:
To install from the Product CD, run the following command:
./setup.sh -options <RESPONSE_FILE_LOCATION>/response.txt -silent
To uninstall, run the following command from the /OracleBI/uninstall/ directory:
./setup.bin -options <RESPONSE_FILE_LOCATION>/response.txt -silent
Proceed to Section 1.3.3, "Installing or Uninstalling Oracle BI Silently on More Than One Computer."
This procedure installs Oracle BI silently on other computers, using the responses created in the file <RESPONSE_FILE_LOCATION>/response.txt, where <RESPONSE FILE LOCATION> is the full path to the response file.
There are two porting options for distributing the silent installation to other computers, as described in the following list:
When porting from the target computer, see Section 1.3.4, "Installing or Uninstalling from a Target Computer."
When porting from a network-accessible computer, see Section 1.3.5, "Installing or Uninstalling from a Network-Accessible Computer."
The entire Oracle BI installation image must be on the target computer in order for the installWithResponseFile.bat file to perform this procedure.
To install Oracle BI silently from a target computer:
Copy the response.txt file from the master installation to the drive.
The Oracle BI installation directories and Oracle BI installation image location on the target computer might be configured exactly as on the initial installation computer.
If the target directory paths are configured exactly as on the initial installation computer, then install Oracle BI by running the installWithResponseFile file at the command line.
If the target directory paths are not configured the same, then modify the following response.txt file parameters to reflect the target directory paths:
-W TempPanelBean.Destination="<Logical Drive>:/<target path>/OracleBI"
-W TempPanelBean.TempDir="<Logical Drive>:/<target path>/OracleBIData"
The installation has completed when the command prompt returns.
The installWithResponseFile file does not force a computer restart. Restart manually at the end of the installation.
The entire Oracle BI installation image must reside on the network computer on a drive that is accessible to all computers that perform an Oracle BI installation or uninstallation.
To install Oracle BI silently from a network-accessible computer:
Copy the response.txt file created from the master installation to the drive.
On each target installation computer, map a logical drive to the network computer Oracle BI installation image root directory.
The drive letter for this map must be the same on all target installation computers.
On the network computer, change the following parameters in the response.txt file to use the Oracle BI installation directory paths common to all target installation computers:
-W TempPanelBean.Destination="<Logical Drive>:/<target path>/OracleBI"
-W TempPanelBean.TempDir="<Logical Drive>:/<target path>/OracleBIData"
On the target installation computer, change directory to the mapped logical drive that points to the Oracle BI installation image directory on the network computer.
From the command line, run the installWithResponseFile file.
The installation has completed when the command prompt returns.
The installWithResponseFile file does not force a computer restart. Restart manually at the end of the installation.
This section describes general issues and workarounds for Oracle Business Intelligence Suite Enterprise Edition products. It contains the following topics:
Section 1.4.1, "New Features in Oracle BI Enterprise Edition Version 10.1.3.3"
Section 1.4.2, "New Features in Oracle BI Enterprise Edition Version 10.1.3.3.1"
Section 1.4.3, "New Features in Oracle BI Enterprise Edition Version 10.1.3.3.2"
Section 1.4.4, "New Features in Oracle BI Enterprise Edition Version 10.1.3.3.3"
Section 1.4.5, "New Features in Oracle BI Enterprise Edition Version 10.1.3.4"
Section 1.4.6, "New Features for Oracle BI Enterprise Edition Version 10.1.3.4.1"
Section 1.4.7, "New Features for Oracle BI Enterprise Edition Version 10.1.3.4.2"
Section 1.4.14, "New Privilege Further Secures XSS Vulnerability"
Section 1.4.15, "Cannot View PDF in Internet Explorer 6 and 7 over SSL"
Section 1.4.16, "SQLEXTENDEDFETCH with Oracle Retail Predictive Application Server (RPAS)"
Section 1.4.17, "Issues with Discoverer Metadata Migration Utility"
Section 1.4.18, "Configuring Oracle BI EE Using an EAR File"
Section 1.4.19, "New Books for Oracle BI Suite Enterprise Edition Version 10.1.3.4.2"
Oracle BI Enterprise Edition Version 10.1.3.3 has the following new features:
General New Features
Oracle BI Answers-Based Metadata Dictionary
Multi-Select Dashboard Prompts
Office Integration with BI Dashboard
New Dashboard Link Types
Import Oracle Catalog
Embedded Database Functions
Drag and Drop XMLA Metadata Objects
New Features for Oracle BI Publisher
Oracle BI Publisher Template Builder Enhancements
Flash Templates for Oracle BI Publisher
Oracle BI Publisher PowerPoint Output
Oracle BI Publisher Integration with Oracle BI Discoverer
Performance Improvements for Oracle BI Publisher
Converting Reports from Oracle Reports to Oracle BI Publisher
Support for Digital Signature in PDF Documents
Support for Postscript Printers
New Features Oracle Business Intelligence for Microsoft Office
Improved version of Oracle Business Intelligence Add-in for Microsoft Office, with a new Excel and PowerPoint Add-in.
For more information about new features, refer to Oracle Business Intelligence New Features Guide.
Note:
Oracle BI Publisher has additional features that are not documented in Oracle Business Intelligence New Features Guide. For more information, see Oracle Business Intelligence Publisher New Features Guide.
Oracle BI Enterprise Edition Version 10.1.3.3.1 has the following new features:
General New Features
Oracle Business Intelligence Installer Now Deploys Oracle BI Enterprise Edition Components into One OC4J Container
DataDirect Connect ODBC Drivers for Linux and UNIX Operating Systems Bundled with Oracle BI Enterprise Edition 10.1.3.3.1
Support for Oracle BI EE Charts in Arabic, Thai, and Hebrew
New Features for Oracle BI Publisher
Time Out Value for the Web Service Data Source
Bidirectional Function for eText Data Fields
Default Repository
Oracle BI Publisher Web Services
New Features for the Oracle BI Add-in for Microsoft Office
Configure the Connection URL
Language Support
For information about the new features, refer to Oracle Business Intelligence New Features Guide.
Oracle BI Enterprise Edition Version 10.1.3.3.2 has the following new features:
General New Features
Oracle BI EE supports Hyperion Essbase as a data source.
Oracle BI EE provides a proxy plug-in that can be configured to enable the Business Intelligence EE OC4J component to run on IIS.
New Features for Oracle BI Publisher
Support for Document Cache
Support for New Output Types
Oracle BI Enterprise Edition Version 10.1.3.3.3 contains no new features.
However, Oracle BI Publisher Version 10.1.3.3.3 contains new features. For more information about the new Oracle BI Publisher features, refer to Oracle Business Intelligence New Features Guide.
Oracle BI Enterprise Edition Version 10.1.3.4 has the following new features:
General New Features
Oracle BI EE is integrated with Oracle Enterprise Performance Management Workspace and Oracle Smart Space, Fusion Edition.
You can migrate metadata from relational data sources for Oracle BI Discoverer to Oracle BI EE metadata.
A new type of line chart to plot time series data is available.
The ability to use Oracle BI EE and Oracle BI Publisher with Oracle WebLogic Server 10.x is available.
A new sample Oracle BI application and data set called "Sample Sales" has been designed to better and more fully illustrate the capabilities of Oracle BI 10.1.3.4.
For information about the new features, refer to Oracle Business Intelligence New Features Guide.
New Features for Oracle BI Publisher
BI Publisher is integrated with Oracle Enterprise Performance Management Workspace and Oracle Smart Space, Fusion Edition.
BI Publisher supports connections to the following multidimensional data sources: Oracle's Hyperion Essbase, Microsoft SQL Server 2000 Analysis Service, Microsoft SQL Server 2005 Analysis Service, and SAP Business Information Warehouse (SAP BW).
BI Publisher Web service PublicReportService has been expanded to support more operations.
BI Publisher supports "After Report" Triggers.
BI Publisher accepts Web services that return complex data types.
The new property "Disable Client Access from Analyzer for Excel" enables you to control the method used to download data to Microsoft Excel at the report level.
The Template Builder for Microsoft Word has these enhancements: page break support, support for additional chart types, more properties supported for charts, support for multiple measures in charts, and enhanced crosstab features.
The documentation set for BI Publisher has been updated for Release 10.1.3.4. See that documentation for information about the new features.
New Features for Oracle Business Intelligence for Microsoft Office
Ability to enable logging
Enhanced BI Catalog Task Pane
Ability to preserve Excel conditional formatting during refreshes
Support for gauge and funnel views
Edit prompts and levels after insert
Enhanced prompts selection interface
Support for grand totals in table views
Support for inserting BI Answers request views to Excel and PowerPoint that have been constructed using Set operations
Server independence
Transparent compression of results
Support for NT Lan Manager (NTLM) Authentication Protocol for Microsoft Windows
For information about the new features, refer to Oracle Business Intelligence New Features Guide.
Oracle BI Enterprise Edition Version 10.1.3.4.1 contains the following new features:
Configuring for connections to EPM Workspace
Validating the catalog
Oracle BI Publisher Version 10.1.3.4.1 contains new features. For more information about the new Oracle BI Publisher features, refer to Oracle Business Intelligence Publisher New Features Guide.
Oracle BI Enterprise Edition Version 10.1.3.4.2 contains the following new features:
Support for SAP/BW Variables
Enhancements for Catalog Manager:
Search and Replace
Creating Reports
Obtaining audit trail information for objects
Oracle BI Publisher Version 10.1.3.4.2 contains new features. For more information about the new Oracle BI Publisher features, refer to Oracle Business Intelligence Publisher New Features Guide.
Oracle Business Intelligence for Microsoft Office Version 10.1.3.4.2 contains new features. For more information about the new features, refer to Oracle Business Intelligence New Features Guide.
For certification information, refer to the System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition document. This document is part of the Oracle BI Suite Enterprise Edition documentation set. It is also available from the Certifications tab on My Oracle Support at the following location:
This section provides release notes on installing and upgrading Oracle Business Intelligence Suite Enterprise Edition. It contains the following topics:
Section 1.4.9.1, "Warning Messages Are Displayed Despite Successful Upgrade"
Section 1.4.9.2, "Essbase API Reference Is Not Added to nqsconfig.ini During Upgrade"
Section 1.4.9.3, "Microsoft .NET Installation Dialog Is Displayed"
Section 1.4.9.4, "Cosmetic Issues to Ignore During Installation"
Section 1.4.9.5, "Host Name Errors After Installation on UNIX Platforms"
Section 1.4.9.6, "Issue Starting Javahost Service on Solaris Platforms"
Section 1.4.9.7, "Oracle BI Presentation Services Plug-In Deployed with All Custom Installations"
Section 1.4.9.8, "Oracle BI Presentation Services Does Not Start After Windows Installation"
Section 1.4.9.10, "Issue Starting Oracle BI Scheduler After Installing Paint Repository"
Section 1.4.9.11, "Oracle 11g Not in the Picker List for Scheduler Configuration DB Type"
Section 1.4.9.13, "Install/Uninstall Log Is Encoded with ASCII"
Section 1.4.9.15, "Installer Indicates a Successful Installation Though Installation Fails"
Section 1.4.9.17, "Oracle BI Folders Remain After Uninstall on Windows Server 2008"
Section 1.4.9.18, "Preload 64-Bit Stream Library for HP-UX IA64"
Section 1.4.9.20, "Asian Languages Do Not Display Correctly with Java 5.0"
Section 1.4.9.21, "Cannot Perform an Advanced Installation If SSO Is Already Configured"
Section 1.4.9.22, "Automatic Restart of OC4J on Linux or UNIX"
Section 1.4.9.23, "Installing Oracle BI EE with Microsoft IIS 7"
Section 1.4.9.24, "Installing Oracle BI EE on IBM AIX Platform"
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
During the upgrade process, you see various messages. You might see warning messages that mention a successful upgrade. Be aware that the use of "Warning" as a message category does not necessarily imply an unsuccessful upgrade operation. This issue has no workaround.
This issue applies to Version 10.1.3.3.2 and 10.1.3.3.3. It is fixed in Version 10.1.3.4.
When an existing Oracle BI Enterprise Edition installation is upgraded, the reference for the Essbase API.dll is not added to the nqsconfig.ini (DB_DYNAMIC_LIBRARY) section. This issue causes errors when users try to use Essbase as a data source.
To work around this issue, locate the DB_DYNAMIC_LIBRARY section and add the following entry:
ESSBASE = nqsdbgatewayessbasecapi;
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When you run the Oracle Business Intelligence installer on Windows systems, you might notice that the Microsoft .NET installation dialog is displayed. If you see this dialog, then click either the Cancel or OK buttons there. In either case, the installation of Oracle Business Intelligence Suite Enterprise Edition proceeds normally.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
You can ignore the following cosmetic issues during installation:
When you run the Oracle Business Intelligence installer on Windows or Linux systems, you might notice text such as "$Lcom.siebel.analytics" displaying where the descriptions should be at the start of a full installation. This text can be displayed for approximately 30 seconds before a more meaningful description is displayed.
While this text might be construed as an error with installation, it is simply a refreshing issue that you can ignore when it disappears. Then you can continue with the installation.
On the "Installing Oracle Business Intelligence 10.1.3.2.0" progress page, the progress bar quickly shows 100%, even though the progress window indicates that files are being installed. In addition, the text for 100% is in reverse video (a pale gray), which is not very readable.
This issue has no workaround and does not hinder a successful installation.
This section addresses issues regarding host name lookup.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After installation on a UNIX platform, you might encounter errors such as the following ones:
When you click the BI Publisher tab on the Oracle BI Answers page, the page appears to "hang," giving no response.
When you click the BI Publisher tab on the Oracle BI Dashboard page, you see an error message similar to the following one:
The following error occurred: [code=DNS_HOST_NOT_FOUND] The host name was not found during the DNS lookup.
These errors occur because the installer cannot locate a valid full host name. The installer tries to obtain the full host name by using the "nslookup" command. If the "nslookup" utility is installed and working correctly, then the installer can find and use the full host name. If the "nslookup" utility is not installed or is not working correctly, then the installer cannot find the full host name. Instead, the installer tries to use the original computer name without the domain name.
To work around this issue, ensure that the "nslookup" utility is installed and working correctly on the UNIX computer so that the installer can find the full host name to use in configuration files. Otherwise, the installer uses only the original computer name, which can produce errors.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After installing Oracle Business Intelligence Suite Enterprise Edition on Solaris platforms, you might see an error message such as the following one:
Javahost service is unable to start, exiting with the following error: "...SEVERE: Unexpected Exception. Listener will be shutdown. java.io.IOException: Invalid argument..."
This error is likely caused by Solaris bug (6433853). To resolve this issue:
Upgrade to the latest Java version for Solaris., which is 1.5.0_08 or later.
Ensure that the Javahost service uses the new Java version by completing these steps:
Open the instanceconfig.xml file in the SADATADIR/web/config directory for editing.
Modify the JavaHome element to point to the 1.5.0_08 or later version.
See Oracle Business Intelligence Presentation Services Administration Guide for information on editing the instanceconfig.xml file.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you perform a custom installation on a computer on which an HTTP server has been installed and if you choose to install Oracle Business Intelligence Presentation Services, then the Oracle BI Presentation Services Plug-in is deployed even if you do not select it. To avoid the plug-in being used, manually stop it after installation or un-deploy it using Oracle Enterprise Manager.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After installing on a Windows system and after restarting the computer, you might find that Oracle BI Presentation Services does not start. This can occur due to many other large processes or services starting at the same time, which causes Oracle BI Presentation Services to time out.
To work around this issue, restart Oracle BI Presentation Services manually after the computer has restarted.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After performing an Advanced installation on a Windows system and after restarting the computer, you might encounter an error message that states that a service failed to start. The event viewer shows log information similar to the following:
Invalid repository file: Drive:\OracleBI\server\Repository\paint.rpd.
This message is generated because the Paint demo is available only for the Basic installation and not for the Advanced installation. You can ignore this error message. This issue has no workaround.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After installing the paint repository, you notice that Oracle BI Scheduler is not preconfigured. If you try to start Oracle BI Scheduler without configuring it first, then you might see an error message such as the following:
Error 1064: An exception occurred in the service when handling the control request
To avoid encountering this error message after installation, configure Oracle BI Scheduler as described in Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Oracle BI EE has been certified with Oracle Database 11g. In the configuration for Scheduler and connectivity, there is no Scheduler configuration setting for Oracle 11g. The Call Interface can be set to OCI 10g/11g within Administration Tool or Scheduler, but the Scheduler has a database type poplist that does not contain Oracle 11g.
Users can proceed successfully using the 11g database having set the Database Type value to Oracle 10g R2.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you plan to run the Oracle BI Enterprise Edition installer on a workstation running Microsoft Windows 2000, you must first download and install the Windows executable file reg.exe. This file is required to allow the installer to update the Windows registry on Windows 2000 computers, but is not installed by default with the Windows 2000 operating system. The file reg.exe is located on the Windows 2000 installation media in the Support Tools folder.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The Oracle BI installer is not localized. When installing Oracle BI with a localization such as FR on Microsoft Windows 2003, the log is encoded with ASCII instead of UTF-8; therefore, non-ASCII characters are displayed as question marks.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After upgrading from Oracle BI EE Release 10.1.3.2.1 to 10.1.3.3 or later, the OC4J process might not start, even after a manual restart. This issue occurs because DLL files are being locked by a background monitoring process. The locked DLL files cause the OC4J process to fail, because the DLL files cannot be deleted and replaced with the newer files from the later release.
To work around this issue on Windows:
Stop or kill the running background process that is locking the files OracleBI/server/Bin/perfcoll_OracleBIServer.dll and OracleBI/web/bin/perfcoll_OracleBIPresentationServer.dll.
Delete the files OracleBI/server/Bin/perfcoll_OracleBIServer.dll and OracleBI/web/bin/perfcoll_OracleBIPresentationServer.dll.
Run the following commands at a command prompt:
sawserver -installperf
NQSServer -installperf
To work around this issue on Linux:
Stop or kill the running background process that is locking the files OracleBI/server/Bin/libperfcoll_OracleBIPresentationServer.so OracleBI/web/bin/libperfcoll_OracleBIServer.so.
Delete the files OracleBI/server/Bin/libperfcoll_OracleBIPresentationServer.so OracleBI/web/bin/libperfcoll_OracleBIServer.so.
Run the following commands at a command prompt:
OracleBI/setup/installperfsas.sh
OracleBI/setup/installperfsaw.sh
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
In some instances during installation, the user might encounter an error "An error occurred and product installation failed. Look at the log file...." where the installer does not stop and the Next button is available. If the user clicks Next, then the message "The installation of Oracle Enterprise Edition 10g(10.1.3.3) was successful" is displayed. The second message is incorrect and the user should look at the log file to correct the issues and have a successful installation.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When installing Oracle BI Enterprise Edition using the Advanced installation type, you must install Oracle Application Server before running the Oracle BI Installer. By default, Oracle Application Server creates an OC4J container called "home." This container is the location where all the Oracle BI Applications are deployed. The Oracle BI Installer requires the OC4J container called "home" to be present and enabled.
If a container called "home" does not exist, then follow the instructions located in Oracle Application Server Administration Guide to re-create the container.
If the OC4J instance named "home" is disabled, then the Oracle BI Installer does not proceed. You must enable the OC4J "home" instance for Oracle BI Installer to proceed. The Oracle BI Installer checks the existence of OC4J "home" instance and if it is enabled. If it is not, the Installer displays the following error message: "Please specify a valid Oracle Application Server 10g installation location. A valid Oracle Application Server 10g installation must have the default OC4J instance named 'home' and that 'home' OC4J instance must be enabled."
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After you uninstall the basic installation of Oracle BI EE Release 10.1.3.4 on Windows Server 2008, you might see the following error message:
Uninstall failed.
Please see the attached uninstall.log.
Windows Server 2008 is supported for Oracle BI EE Release 10.1.3.4, and this uninstallation issue is specific to Windows Server 2008. This error likely occurs when some Oracle BI EE DLL files are locked during the uninstallation, which prevents the files and Oracle BI EE folders from being deleted.
To complete the uninstall process manually, restart the computer and delete the Oracle BI folders that were not deleted.
This issue applies to Versions 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After you install Oracle BI EE on HP-UX IA64, you must modify the user.sh file to preload the 64-bit stream library. Make this change by adding the following lines to the user.sh file in the setup directory:
LD_PRELOAD=/usr/lib/hpux64/libstream.so.1 export LD_PRELOAD
Ensure that the correct path to libstream.so.1 is used. Depending on the HP-UX installation, this library might be in a different path. Modify it for your installation of HP-UX IA64.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When you install Oracle Business Intelligence within a ja_JP locale on SUSE Linux, the titles of the Installer windows, including Help windows, include garbled fonts (for example,'%9%H$'). However, the fonts displayed in the Installer windows' body text are displayed correctly.
According to the release notes for Java Developer Kit (JDK) 1.4.2 posted on the Sun Microsystems Java Web site (http://java.sun.com), JDK 1.4.2 does not provide support on SUSE Linux for east Asian languages.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Asian language characters including Japanese, Korean, Traditional Chinese, and Simplified Chinese do not display on the SUSE platform due to lack of JDK support.
To resolve this issue, you can modify the font properties/config files. Refer to the following Sun Microsystems Java Web site URL for details:
http://java.sun.com/j2se/1.5.0/docs/guide/intl/fontconfig.html
However, Oracle does not support these modifications and if you need support, you must reproduce the product functional errors with an unaltered JDK.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
You cannot perform an advanced installation of Oracle BI EE if Single Sign-On has been configured. This is not supported.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
OC4J does not restart automatically after restarting a computer running the Linux or UNIX operating system. OC4J installed with Oracle BI EE is not a managed process. Use the following command with an Oracle BI EE basic installation to start OC4J on Linux or UNIX as a background process:
./oc4j -start &
After OC4J starts as a background process you can exit the session while it is running.
This issue applies to Version 10.1.3.4.2.
When you install Oracle BI EE Version 10.1.3.4.2 on a Windows platform on which Microsoft IIS 7 is configured, you expect to see a screen that allows you to select IIS 7 or Oracle Containers for J2EE (OC4J) as the application server. If IIS 7 is not displayed as an option, then IIS 7 is not configured properly on the computer.
To see IIS 7 as an available option on this screen, you must ensure that the IIS 6 Management Compatibility options for IIS 7 have been installed on the computer. You can consult the pages that are available from the following links for information on IIS 7:
Installing IIS 7:
http://learn.iis.net/page.aspx/28/installing-iis-on-windows-vista-and-windows-7/
Start or Stop the Web Server on IIS 7
http://technet.microsoft.com/en-us/library/cc732317%28WS.10%29.aspx
Start or Stop the Management Service on IIS 7
http://technet.microsoft.com/en-us/library/cc732778%28WS.10%29.aspx
This issue applies to Version 10.1.3.4.2.
To install Oracle BI EE Version 10.1.3.4.2 on the IBM AIX platform, you must use JDK 1.5 for installation.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When you use a Firefox browser on the Solaris platform, you might encounter a known issue with popup descriptions. When you hover the mouse pointer over an item to pop up its description, you might notice that the description is truncated to a single line, even if it should display multiple lines. This issue does not occur on browsers such as Internet Explorer on Windows platforms. Windows browsers display the entire description.
This issue has no workaround.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, and 10.1.3.4.1, and 10.1.3.4.2.
See Oracle Business Intelligence New Features Guide for information on enhancements to Catalog Manager.
This section provides information on documentation corrections for Oracle Business Intelligence Suite Enterprise Edition. These issues apply to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, and 10.1.3.4.1, and 10.1.3.4.2.
This section contains the following topics:
Section 1.4.12.3, "Corrections for Oracle Business Intelligence Infrastructure Upgrade Guide"
Section 1.4.12.5, "Corrections for Oracle Business Intelligence Administration Tool Help"
Section 1.4.12.6, "Corrections for Oracle Business Intelligence Server Administration Guide"
Section 1.4.12.7, "Corrections for Oracle Business Intelligence Delivers Help"
Section 1.4.12.8, "Corrections for Oracle Business Intelligence Scheduler Guide"
Section 1.4.12.9, "Corrections for Oracle Business Intelligence Enterprise Edition Deployment Guide"
Section 1.4.12.11, "Corrections for Oracle Business Intelligence Publisher User's Guide"
Section 1.4.12.12, "Corrections for Oracle Business Intelligence Publisher Help"
Section 1.4.12.13, "Corrections for Oracle Business Intelligence Disconnected Administration Guide"
This section contains corrections to Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
Throughout Oracle Business Intelligence Installation and Configuration Guide, there are references to the file install.pdf on page 94, 182, and 183. The PDF file, titled "Deploying Oracle Business Intelligence Publisher in J2EE Application Servers" is now part of the Oracle BI EE documentation library. The documentation library is available on the product DVD and on Oracle Technology Network.
The section "Deploying Oracle BI on Oracle Application Server" requires the following correction:
If you plan to perform an Advanced Installation, then a supported version of Oracle Application Server (as specified in Oracle Business Intelligence Enterprise Edition System Requirements and Supported Platforms) must be installed before you run the Oracle BI EE Installer.
In Chapter 4:
This issue is documented in version 10.1.3.2.1 of Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
To the section "Process of Planning the Installation", the following text should be added to the end:
To install Oracle BI EE and Oracle client software on the same computer, you must install the Oracle client software first. If you install the Oracle client software after installing Oracle BI EE, then you might change the Java SDK version for Oracle BI EE, which might result in run-time errors.
The section "Process of Planning the Installation" contains a Step 3, which states that if you have an earlier version of Siebel Analytics platform installed, then you must first uninstall it. That statement is incorrect and should be disregarded.
A similar paragraph exists in the "Installation Requirements for All UNIX Platforms" section and should also be disregarded.
The following information must be added to Oracle Business Intelligence Infrastructure Installation and Configuration Guide, Versions 10.1.3, 10.1.3.2, and 10.1.3.2.1.
On page 39, in the subsection "Making the Java Platform Installation Writable," add the following text as a third bullet under the task "To make the Java platform writable under UNIX":
Run the following scripts.
Note:
These scripts must be run by the user who owns the JDK home folder.
To set the permissions:
oraclebi_enable_jdk_home_permissions.sh
To revert the permissions:
oraclebi_restore_jdk_home_permissions.sh
The section "Oracle BI Server Environment Variables for IBM AIX" includes the subsection "Deploying 32-bit Oracle BI Under IBM AIX." In that subsection, the following sentence is incorrect:
Run the following commands to set your 32-bit Oracle BI deployment under AIX:
This sentence should read as follows:
The following 32-bit environment variables for AIX are set automatically by .variant.sh:
In two subsections, there are incorrect values for LDR_CNTRL = IGNOREUNLOAD@LOADPUBLIC@PREREAD_SHLIB@MAXDATA. These subsections and the correct values for each are as follows:
Subsection: "Deploying 32-bit Oracle BI Under IBM AIX"
export LDR_CNTRL = IGNOREUNLOAD@LOADPUBLIC@PREREAD_SHLIB@MAXDATA=0X80000000
Subsection: "Deploying 64-bit Oracle BI Under IBM AIX"
export LDR_CNTRL=IGNOREUNLOAD@LOADPUBLIC@PREREAD_SHLIB@MAXDATA=0x200000000
In Chapter 5, Table 7 contains information for interacting with the Oracle Application Server Location screen. The Administrator user name that must be assigned to the role oc4j_administrators is the user name of the Oracle Application Server Administrator, and not the username of the Oracle BI Administrator.
In the section "Installing Oracle BI Office Plug-In," in the first paragraph, the following sentence is incorrect:
The Plug-In provides a way to browse the Analytics catalog, select a report, and then drop that report into Microsoft Word or Excel.
This sentence should read as follows:
The Plug-In provides a way to browse the Analytics catalog, select a report, and then drop that report into Microsoft PowerPoint or Excel.
Also in this chapter, in the section "Installing Oracle BI Office Plug-In," in the second bullet, the following sentence is incorrect:
An appropriate version of Microsoft Office, containing Microsoft Word and Excel (see System Requirements and Supported Platforms)
This sentence should read as follows:
An appropriate version of Microsoft Office, containing Microsoft PowerPoint and Excel (see System Requirements and Supported Platforms)
The section "Creating a WAR File for Oracle BI Presentation Services" includes an incorrect table before the procedure. Replace that table with the following text:
This procedure uses the WAR file, located in the following directories:
Windows: OracleBI_HOME\web
UNIX: /usr/local/OracleBI/web
In the procedure in this same section, replace the procedure as follows:
To create or re-create a WAR file:
Navigate to the Oracle Business Intelligence installation directory shown in the preceding list.
To create the WAR file, run the following jar command:
jar -cf Analytics.war -C app.
Note:
You must include the period at the end of the command.
The section "Oracle BI Scheduler Server Functions" contains the following paragraph:
The Scheduler uses a single commercial back-end database to store pertinent information about a job, its instances, and its parameters. The Scheduler works with all the supported databases for Oracle Business Intelligence. For the complete list of supported databases, see System Requirements and Supported Platforms.
This paragraph should be reworded as follows:
The Scheduler uses a single commercial back-end database to store pertinent information about a job, its instances, and its parameters. The Scheduler works with the databases that are listed in Oracle Business Intelligence Enterprise Edition System Requirements and Supported Platforms.
Appendix A, "NQSConfig.INI File Reference," requires the following changes.
The following text is incorrect for the SORT_ORDER_LOCALE item in the "General Section Parameters in the Configuration File" section:
The SORT_ORDER_LOCALE entries in the Features table and in the NQSConfig.INI file match only if the database and the Oracle BI Server have matching settings in these areas. If the settings do not match, wrong answers can result when using multidatabase joins, or errors can result when using the Union, Intersect and Except operators, which all rely on consistent sorting between the back-end server and the Oracle BI Server.
The text should read:
An Inconsistent Sort Order Locale setting between a database platform's internal settings and the Database Features of an Oracle BI Enterprise Edition metadata repository Connection Pool can affect the correctness of the result set. If the settings do not match, then incorrect answers can result when using multi-database joins, or errors can result when using the Union, Intersect, and Except operators, which all rely on consistent sorting between the back-end server and the Oracle BI Server.
Inconsistent SORT_ORDER_LOCALE settings between the nQSConfig.ini and the Database Features of an Oracle BI Enterprise Edition metadata repository Connection Pool can negatively impact query performance; however, it does not affect the correctness of the result set.
The description of the parameter PROJECT_INACCESSIBLE_COLUMN_AS_NULL in the section "Security Section Parameters in the Configuration File" is incorrect. The correct description for this parameter is as follows:
Controls how security-sensitive columns are displayed to unauthorized users. If this parameter is set to YES, a NULL expression replaces the original column expression in the query and secured columns are hidden from unauthorized users in both Answers and Interactive Dashboards reports.
If this parameter is set to NO, when a user attempts to run a report that contains a secured column that the user is not authorized to see, then an unresolved column error occurs.
The default value is NO.
In Oracle Business Intelligence Infrastructure Quick Installation Guide, the section "Changing the DEP Setting" states that you should turn on the Data Execution Prevention (DEP) feature. This is incorrect; the DEP is no longer required for Version 10.1.3.3 or later versions of Oracle BI EE.
In Oracle Business Intelligence Infrastructure Upgrade Guide, Chapter 2 includes the section "Overview of the Upgrade Steps for the Different Versions of Siebel Analytics." A list in that section contains the following sentence:
Uninstall Siebel Analytics.
That sentence is incorrect and should be reworded as follows:
Uninstall the Siebel Analytics Microsoft Excel add-in.
This section contains corrections to Oracle Business Intelligence Presentation Services Administration Guide.
In Chapter 2:
In the section "Setting the Oracle BI Presentation Services Configuration File Path," replace the first sentence with this sentence: "You can override the path that Oracle BI Presentation Services searches for customer-specific configuration files upon startup."
In addition, replace <ConfigDir> with <DataConfigDir> so that the instanceconfig.xml entry looks like this: <DataConfigDir>value</DataConfigDir>.
In the section "Setting the Time to Expire for Oracle BI Presentation Services Client Sessions," remove the following sentence in the fourth paragraph: "The value must be greater than or equal to the value specified for the setting SearchIDExpireMinutes, described in the section "Setting the Time to Keep an Unsaved Oracle Business Intelligence Request".
Remove the section "Setting the Time to Keep an Unsaved Oracle Business Intelligence Request" as this configuration setting has been deleted.
In the section "Specifying the Expiration Date for Persisted Oracle BI Presentation Services Cookies," replace <CookieExpire> with <CookieLifetimeMinutes> so that the instanceconfig.xml entry looks like this: <CookieLifetimeMinutes>Tue, 31 Dec 2040 23:59:59 GMT</CookieLifetimeMinutes>.
Chapter 2 provides incorrect information on the javahost "InputStreamLimitInKB" setting. To increase the javahost "InputStreamLimitInKB" setting, the value for a new limit should be placed under the XMLP node and not under the PDF one in the javahost config.xml file.
In Chapter 3, the section "Configuring Answers Pivot Table Settings" states that you use elements within the <PivotView> element to affect pivot tables. That is incorrect. You do not include the elements that are mentioned in that section within the <PivotView> element but directly under the <ServerInstance> element.
In Chapter 4, the section "Changing the Directory in Which Delivers iBot Deliveries Are Stored" contains two errors.
First, the sections state that the <PersistentStorageDirectory> element has to be placed within the <Web> element, and that the <Web> element has to be created after the <ServerInstance> element. These instructions are incorrect. The <PersistentStorageDirectory> element has to be placed within the existing <ServerInstance> element, which is within the <WebConfig> element.
Second, the section states that the default storage location for iBot deliveries is the deliveries directory in the same location as the Presentation Catalog. This is incorrect. The default storage location is the _delivers/_deliveries folder within the user's home folder within the Presentation Catalog.
In Chapter 5, the section "Setting Up Hierarchies in the Physical Layer for a Multidimensional Data Source" contains the following information:
You can set up unbalanced hierarchies in the physical layer by changing the hierarchy type. This is incomplete. The statement should read as follows:
You can manually model an unbalanced hierarchy in the Physical layer by explicitly setting the hierarchy type, but queries against it do not work.
In Chapter 6 in the section "Archiving a Presentation Catalog," Step 5 describes the use of the Keep Timestamp option. This option is inoperable and its description should be removed from the guide.
In Chapter 7:
The section "Searching for and Replacing Presentation Catalog Text Using Catalog Manager" states in two places that you must be in offline mode to search for and replace text. This is not correct. You can be in either offline or online mode.
The section "Creating Reports to Display Presentation Catalog Data Using Catalog Manager" states that you can create reports for requests, dashboards, segments, segment trees, and list formats. This is incorrect. You can create reports for requests and dashboards but not for segments, segment trees, and list formats. In Version 10.1.3.4.2, the reports capability has been enhanced so that you can create reports for many more object types and even for the entire catalog. See Oracle Business Intelligence New Features Guide for revised instructions for creating reports.
The section "Creating Reports to Display Presentation Catalog Data Using Catalog Manager" contains the following sentence: "If you want to create a report showing the SQL that is sent to Oracle BI Presentation Services for the object, you must open the Presentation Catalog in online mode." The sentence should read: "If you want to create a report showing the SQL that is sent to Oracle BI Server for the object, you must open the Presentation Catalog in online mode."
When you create a report, a blank or empty field is exported as a tab character. If you have created a report with the default of a tab as the field separator, then two tab characters in the report file indicates a blank field.
The section "Localizing Presentation Catalog Captions" requires documentation corrections. See Section 2.2.9, "Issue Handling Captions in Presentation Services" for information.
In Chapter 8, the procedure for creating a custom message template for the proxy functionality is missing a statement in the SQL code to connect to the correct db/connection pool to extract the target users, and so on.
To work around this issue, replace the code in Step 4 in the procedure for creating a custom message template in the "Creating a Custom Message Template for Proxy Functionality" section with this code:
<XML>
<logonParam name="RUNAS">
<getValues>EXECUTE PHYSICAL CONNECTION POOL physical_dbname.conn_pool_name
select targetId from Proxies where proxyId='@{USERID}'</getValues>
<verifyValue>EXECUTE PHYSICAL CONNECTION POOL physical_dbname.conn_pool_name
select targetId from Proxies where proxyId='@{USERID}' and
targetId='@{VALUE}'</verifyValue>
<getDelegateUsers>EXECUTE PHYSICAL CONNECTION POOL physical_dbname.conn_pool_name select proxyId, proxyLevel from Proxies where
targetId='@{USERID}'</getDelegateUsers>
</logonParam>
</XML>
Also include this sample custom message template at the end of the procedure:
Sample Custom Message Template
<?xml version="1.0" encoding="utf-8" ?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem">
<WebMessageTable system="SecurityTemplates" table="Messages">
<WebMessage name="LogonParamSQLTemplate">
<XML>
<logonParam name="RUNAS">
<!-- for EXECUTE PHYSICAL CONNECTION POOL, SQL_Paint.SQL_Paint = -->
<!-- SAS Repository physical_dbname.conn_pool_name -->
<getValues>EXECUTE PHYSICAL CONNECTION POOL SQL_Paint.SQL_Paint
select targetId from Proxies where proxyId='@{USERID}'\</getValues>
<verifyValue> EXECUTE PHYSICAL CONNECTION POOL SQL_Paint.SQL_Paint
select targetId from Proxies where proxyId='@{USERID}' and targetId='@{VALUE}'\</verifyValue>
<getDelegateUsers>EXECUTE PHYSICAL CONNECTION POOL SQL_Paint.SQL_Paint
select proxyId, proxylevel from Proxies where targetId='@{USERID}'
</getDelegateUsers>
</logonParam>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
In Chapter 10:
The section "About Skins and Styles" contains incomplete information. The following information should be displayed after the section's first paragraph:
Respective Web servers require resource files such as styles to be deployed appropriately for those applications. For example, when using OC4J as is common in Oracle BI deployments, skins, styles and images must be duplicated in the following directories:
{OracleBI}\oc4j_bi\j2ee\home\applications\analytics\analytics\res
{OracleBI}\web\app\res
As a rule, customer-specific files such as custom styles should exist in the {OracleBIData} folders so these are not lost during upgrades. In this case, the custom style would then be deployed to OC4J as described above and to the following directory: {OracleBIData}\web\res
While XML message files that affect a language-specific user interface must be localized, the XML file that is used for configuring a report write back template is usually not translated, because it is language-independent. As described in the section "Customizing the Oracle BI Presentation Services User Interface Using XML Message Files" in Chapter 10, the write back template files should be stored in the base CustomMessages folder. This is primarily to persist these files during upgrades.
In the rare cases where write back template files must be language
dependent (for example, if a user logging in using the l_es (Spanish) locale would
use a different SQL then a user logging in using l_fr (French) locale), then
the write back template messages should exist in appropriate language
directories. See the section "Customizing the Oracle BI Presentation Services User
Interface Using XML Message Files" for information.
In Chapter 11:
The section "Structure of the Basic Oracle BI Presentation Services Dashboard URL" provides incorrect information for the syntax for providing the path of the URL.
The correct syntax for providing the path of the dashboard in a Dashboard URL is:
http://server_name_or_ip_address/analytics/saw.dll?Dashboard&PortalPath="path of the dashboard"
Example:
http://localhost:9704/analytics/saw.dll?Dashboard&PortalPath=/shared/Paint Demo/_portal/Paint Dashboard
The section "Optional Parameter for the Oracle BI Presentation Services Dashboard URL" is missing information about the PortalPages command and the Done parameter. The section should read as follows:
Optional Commands and Parameters for the Oracle BI Presentation Services Dashboard URL
You can add optional commands and parameters to the Dashboard URL. The below examples show and explain various uses of commands and parameters.
User ID and Password Example
You can modify the behavior of the Dashboard URL command by adding the user ID and password parameters. If the parameters are omitted, then the user is prompted for user ID and password information, unless the user chose the option to have logon information remembered when last logged on. If using a Session ID or Ticket, pass it as the NQUser parameter. In the parameter description, SB2 is the name of the request to execute.
This is the format where the user ID is uuu and the password is ppp:
&NQUser=uuu&NQPassword=ppp
Example URL:
http://localhost:9704/analytics/saw.dll?Dashboard&PortalPath=/shared/PaintDemo/_portal/PaintDashboard&NQUser=user1&NQPassword=rock
PortalPages Example
You can modify the behavior of the Dashboard URL command by adding the PortalPages command. This command opens a dashboard page without the common header. You can use this command to create a link or image with the specified dashboard page as the destination and open the dashboard page in a new browser window.
This is the format where the catalog path portal page is xxx and the dashboard page name is yyy.
PortalPages&PortalPath=xxx&Page=yyy&Done=close
Note the following command descriptions:
PortalPath – This parameter contains the dashboard's catalog path.
Page – (Optional) This parameter contains the dashboard page name.
Example URL:
http://localhost:8080/analytics/saw.dll?PortalPages&PortalPath=%2fshared%2fdashboar dfolder1%2f_portal%2fdefault&Page=page%202&Done=close
Go Example
You can modify the behavior of the Dashboard URL command by adding the Go command and specifying the catalog path to an analysis. This command opens an analysis without the common header. You can use this command to create a link or image with the specified analysis as the destination and open the analysis in a new browser window.
This is the format where the path is xxx and Done is close.
Go&Path=xxx&Done=close
Note the following parameter descriptions:
Path – This parameter contains the analysis' catalog path.
Done – This parameter is obsolete for the analysis' path.
Example URL:
http://localhost:8080/analytics/saw.dll?Go&Path=%2fusers%2fadministrator%2fdashboar d_actionlink_report&Action=Prompt&Done=close
PortalGo Example
You can modify the behavior of the Dashboard URL command by adding the PortalGo parameter and specifying the catalog path to the analysis. This parameter opens an analysis in a dashboard. You can use this parameter to create a link or image with an analysis as the destination, and open the analysis in the existing browser window.
This is the format where the portal path is xxx, the path is yyy, and Done is zzz.
PortalGo&PortalPath=xxx&Path=yyy&Done=zzz
Note the following parameter descriptions:
PortalPath – This parameter is the dashboard's catalog path. It is in this dashboard that the analysis is displayed.
Path – This parameter is the analysis' catalog path.
Done – This parameter is used by the Return link and contains the return location.
Example URL:
http://localhost:8080/analytics/saw.dll?PortalGo&PortalPath=%2fusers%2fadministrator%2f_portal&Path=%2fusers%2fadministrator%2fSalesInMarket
This section contains a correction to the Oracle Business Intelligence Administration Tool Help System.
The Administration Tool help that describes how to enter the "Import from XMLA" parameters is incorrect. To access the Help, create a new repository by selecting "Import Physical Schema from Multi-Dimensional Datasources." Next, select "Essbase" and click "Help." The following help text appears.
From your data source administrator, obtain the URL connection string and user name and password for the data source.
In the Administration Tool, select File > Import from XMLA.
In the Import From XMLA dialog box, complete the following fields:
In the URL field, type the URL for the Web service that acts as the XMLA provider. Use the URL connection string obtained from your data source administrator.
In the URL field, type the URL for the Web service that acts as the XMLA provider. Use the URL connection string obtained from your data source administrator.
In the username and password fields, type a valid username and password for the data source. Use the user name and password that you obtained from your data source administrator.
This help text should read as follows:
From your Essbase Server administrator, obtain the host name and user name and password for use.
In the Administration Tool, select File > Import from Multi-dimensional...
In the Import From this dialog box, complete the following fields:
In the "ESS Server" field, type the host name of the ESS Server that acts as the XMLA provider.
In the user name and password fields, type a valid user name and password for the data source. Use the name and password that you obtained from the data source administrator.
This section contains corrections to Oracle Business Intelligence Server Administration Guide.
The section "Opening a Repository in Online Mode" does not mention that multiple concurrent Administration Tool users are not supported in online mode. This section should also mention the following:
Guidelines for Using Online Mode
Use caution when making changes to your repository in online mode, and always perform a consistency check to ensure the repository is consistent before checking in objects.
Only one user working on repository development in the Administration Tool in online mode at a time is supported. Even when users have different objects checked out, concurrent edits and check-ins by multiple users are not supported and produce unreliable results. Additional online logins can be used only for management features that do not affect repository metadata, such as managing the cache.
If you must have multiple concurrent metadata developers, then use the multiuser development environment to merge and publish your changes. See "Setting up and Using the Oracle BI Multiuser Development Environment" for more information.
Be aware that online mode is riskier than offline mode because you are working against a running server. If you check in changes that are not consistent, then it might cause the Oracle BI Server to shut down. When you work in online mode, ensure that you have a backup of the latest repository so that you can revert to it if needed.
The following issues applies to version 10.1.3.3.2, only. In the Creating and Administering the Physical Layer in an Oracle BI Repository chapter, in the Process of Creating the Physical Layer from Multidimensional Data Sources > Importing a Physical Schema from Multidimensional Data Sources > To import a physical schema from multidimensional data sources topic, the following steps are incorrect.
From your data source administrator, obtain the URL connection string and user name and password for the data source.
In the Administration Tool, select File > Import from XMLA.
In the Import From XMLA dialog box, complete the following fields:
In the URL field, type the URL for the Web service that acts as the XMLA provider. Use the URL connection string obtained from your data source administrator.
In the URL field, type the URL for the Web service that acts as the XMLA provider. Use the URL connection string obtained from your data source administrator.
In the username and password fields, type a valid username and password for the data source.
Use the user name and password that you obtained from your data source administrator.
The steps should read as follows:
From your Essbase Server administrator, obtain the host name and user name and password for use.
In the Administration Tool, select File > Import from Multi-dimensional...
In the Import From this dialog box, complete the following fields:
In the "ESS Server" field, type the host name of the ESS Server that acts as the XMLA provider.
In the user name and password fields, type a valid user name and password for the data source. Use the name and password that you obtained from the data source administrator.
The section "About Sorting on a Logical Column" should include the following information.
For a logical column from an Essbase data source, you can specify a different sort order column on which to base a sort. This specification changes the sort order of a column when you do not want to order the values lexicographically. You can use the following steps to add a sort key or to replace the existing Rank-based sort key with Memnor.
In the Physical layer of the Administration Tool, right-click a physical cube table for an Essbase data source and select New Object, then select Physical Cube Column.
In the Physical Column dialog, type a name for the physical column.
In the Type field, select a data type of DOUBLE.
In the External Name field, type Memnor and click OK.
The new column is associated directly with the cube.
Drag and drop the column onto the root level of the appropriate dimension to make it a dimensional property that can adapt to the projected level.
Drag and drop the column onto the appropriate logical table.
Make the column the sort order column for the logical column using the following steps:
Double-click the logical column to display the Logical Column dialog.
In the Sort Order Column area, click Set, then select the new column.
Click OK twice to save your changes and dismiss the dialogs.
In the section "Setting Up the Repository to Work with Delivers," the steps to set up the SA System subject area are incomplete. The SA System subject area must be correctly set up in the Presentation layer of the Oracle BI repository for Oracle BI Delivers to function.
For the complete steps to set up the SA System subject area, refer to Analytics Server Administration Guide Version 7.8.2, Revision A. Navigate to Chapter 7, "Completing Setup and Managing Oracle BI Repository Files" and the "Setting Up the Repository to Work with Delivers" section. The following information contained in this section is applicable to the Oracle Business Intelligence 10.1.3.2 release.
The Presentation layer metadata must contain the SA System folder, User table, and columns as shown in Figure 15.
Table 26 in the guide describes the columns for the User table of the SA System subject area folder.
Analytics Server Administration Guide Version 7.8.2 Revision A is available on the Oracle BI Enterprise Edition Documentation page on Oracle Technology Network at the following location:
http://www.oracle.com/technology/documentation/bi_ee.html
and on SupportWeb on the Documentation Updates page at the following location:
In the section "Configuring Query Caching," the first two paragraphs should be replaced with the following text:
The query cache is enabled by default. After deciding on a strategy for flushing outdated entries, you should configure the cache storage parameters in the NQSConfig.INI file. This section includes information on the tasks necessary to configure the Oracle BI Server for query caching. For details about the parameters used to control query caching, see Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
The section "Selecting and Testing the Data Source and ConnectionPool" describes how to use XML as a data source. As of version 10.1.3.3, XML is no longer supported as a data source type.
Appendix A contains Table 42 that includes a row for the QUERY_TEXT column of the usage tracking table. The description of the column should be enhanced as follows:
Varchar (1024).
The SQL statement that was submitted for the query.
You can change the length of this column (using the ALTER TABLE command), but note that the text that is written into this column is always truncated to the size that is defined in the physical layer. It is the responsibility of the repository administrator not to set the length of this column to a value greater than the maximum query length that is supported by the back-end physical database.
For example, Oracle Databases enable a maximum Varchar of 4000, but Oracle Databases truncate to 4000 bytes, not 4000 characters. Hence, if you use a multibyte character set, the actual maximum string size has a varying number of characters, depending on the character set and characters used.
The description for the TIMESTAMPDIFF SQL function describes the behavior when the function is calculated in the BI Server. If this function is calculated in the data source, then the result might be different from the behavior described in this appendix. If the TIMESTAMPDIFF function result is different from the desired result, then you can disable TIMESTAMP_DIFF_SUPPORTED in the Features tab for the database object in the Administration Tool to ensure that the function is calculated in the BI Server. However, this change might adversely affect performance.
This section contains a correction to the Oracle Business Intelligence Delivers Help System.
The help text that is displayed when adding a post action of type iBot with filters is: "Filter values are generated by the conditional report. The iBot specified in this step will be executed once for each row in the conditional report, with filters generated by the values in that row."
This help text should read: "Filter values are generated by the conditional report. The iBot specified in this step will be executed once with filter values generated by the results of the conditional report. For example, if the conditional report returns values for region = North, South, then the post action iBot will execute once with a filter of region = North, South."
In the Oracle BI Delivers Advanced configuration tab you can create a Custom Java Job. The dialog for this option has a field for "Additional Class Paths". The help for this field states that paths should be separated by a semicolon, which is incorrect. You should use a comma (,) as a separator. In addition, this help should be expanded to explain that these additional class paths should refer to java .jar files, which should be in the same directory as the one referenced in the "Class Path" field immediately above.
This section contains corrections to the Oracle Business Intelligence Scheduler Guide:
The section called "About Database Support in Oracle BI Scheduler" contains the following paragraph:
Oracle BI Scheduler uses a single commercial back-end database to store pertinent information about a job, its instances, and its parameters. Oracle BI Scheduler works with all supported databases for Oracle Business Intelligence Enterprise Edition. For information about supported databases, see Oracle Business Intelligence Enterprise Edition System Requirements and Supported Platforms.
This paragraph should be reworded as follows:
Oracle BI Scheduler uses a single commercial back-end database to store pertinent information about a job, its instances, and its parameters. Oracle BI Scheduler works with the databases that are listed in Oracle Business Intelligence Enterprise Edition System Requirements and Supported Platforms.
This section contains corrections to Oracle Business Intelligence Enterprise Edition Deployment Guide:
In Oracle Business Intelligence Enterprise Edition Deployment Guide, Version 10.1.3.2, the example given in step 3 of the procedure on page 142 to change the default Oracle BI Presentation Services listener port is incorrect. References to the <RPC> node must be removed.
Step 3 should read as follows:
3. Within the <WebConfig> tags, assign the RPC Listener Port value for the Oracle BI Presentation Services instance, as shown in the following example.
<WebConfig>
<ServerInstance>
...
<Listener port="9715"/>
...
</ServerInstance>
</WebConfig>
Note: In the preceding example, the RPC Listener port for the Oracle BI Presentation Services instance has been changed to port 9715 from the default of 9710.
In Oracle Business Intelligence Enterprise Edition Deployment Guide, Version 10.1.3.2, the connection strings included in Chapter 3, "Integrating BI Publisher with Oracle BI Clustered Environment" section, step 2, page 40 and Chapter 4, "Integrating BI Publisher with Oracle BI Clustered Environment" section, step 3, page 66 are missing ending semicolons.
Currently, the connection strings appear in the document as follows:
jdbc:oraclebi://BI-CCS-01:9706/PrimaryCCS=BI-CCS-01;PrimaryCCSPort=9706;SecondaryCCS=BI-CCS-02;SecondaryCCSPort=9706
The connection strings should appear as follows (note the semicolon at the end of the string):
jdbc:oraclebi://BI-CCS-01:9706/PrimaryCCS=BI-CCS-01;PrimaryCCSPort=9706;SecondaryCCS=BI-CCS-02;SecondaryCCSPort=9706;
In the Oracle Business Intelligence Enterprise Edition Deployment Guide, Version 10.1.3.2, the XML format given in step 2 of the "Configuring BI Presentation Services for SSL Communication" procedure on page 112 is incorrect.
In the 10.1.3.2 guide, the XML reads as follows:
<Alerts>
<ScheduleServer ssl="true" credentialAlias="sawclient"
certificateVerificationDepth="1" verifyPeers="true">
<BI Scheduler Host>
</ScheduleServer>
</Alerts>
Note that <BI Scheduler Host> should not be included in the XML. When using the correct XML, customers must replace MySchedulerServerName with their environment's scheduler server name. The correct XML reads as follows:
<Alerts>
<ScheduleServer ssl="true" credentialAlias="sawclient"
certificateVerificationDepth="1" verifyPeers="true">
MySchedulerServerName
</ScheduleServer>
</Alerts>
In Oracle Business Intelligence Enterprise Edition Deployment Guide, Version 10.1.3.2, the section "LDAP Authentication over SSL" is not included. Refer to Siebel Analytics Platform Installation and Configuration Guide, Version 7.8.4, Rev. A, "Process of Configuring LDAP and ADSI for Analytics Authentication" for the steps. In the second procedure "Generating a CMS Key Database File", step 2 is missing the following information: The password should be entered in Tools > Options > Repository in the Administration Tool.
The IBM Global Security Toolkit (GSKit) v. 7.0.3.3 is located on the software installation media in the following folder: Server_Ancillary\IMB_GSK. See System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition, Version 10.1.3.3, 10.1.3.4, Rev. K, available on Oracle Technology Network at the following location:
http://www.oracle.com/technology/documentation/bi_ee.html
"Process of Configuring LDAP and ADSI for Analytics Authentication" in Siebel Analytics Platform Installation and Configuration Guide, Version 7.8.4, Rev. A is available at the following location:
In Oracle Business Intelligence Enterprise Edition Deployment Guide, Version 10.1.3.2, Ch. 8, "Implementing Single Sign-On Products With Oracle Business Intelligence" contains an error in the section "Sample Configuration Files."
The sample file in "Using an HTTP header with additional parameters" shows the value for source incorrectly as "header". The sample file reads as follows:
<Param name="IMPERSONATE"
source="httpHeader"
nameInSource="x-Foo-SSO-GUID"/>
<!--Optional, NQ_SESSION.LOCALE sets up the user's locale as determined by SSO system -->
<Param name="NQ_SESSION.LOCALE"
source="cookie"
nameInSource="FOO_SSO_LocaleID"/>
<!--Optional, NQ_SESSION.P1 sets up some other parameter from SSO system -->
<Param name="NQ_SESSION.P1"
source="header"
nameInSource="FOO_SSO_P1"/>
</ParamList>
The sample file should read as follows:
<Param name="IMPERSONATE"
source="httpHeader"
nameInSource="x-Foo-SSO-GUID"/>
<!--Optional, NQ_SESSION.LOCALE sets up the user's locale as determined by SSO system -->
<Param name="NQ_SESSION.LOCALE"
source="cookie"
nameInSource="FOO_SSO_LocaleID"/>
<!--Optional, NQ_SESSION.P1 sets up some other parameter from SSO system -->
<Param name="NQ_SESSION.P1"
source="httpHeader"
nameInSource="FOO_SSO_P1"/>
</ParamList>
This section contains a correction to Oracle Business Intelligence Publisher Administrator's and Developer's Guide. This correction was made in the 10.1.3.4 version of the guide.
The section "BI Publisher Core APIs — Prerequisites" incorrectly lists the required JAR files for working with the BI Publisher Java APIs. The correct list is as follows:
In order to use the BI Publisher APIs you need the following JAR files in your class path:
bicmn.jar — charting library
bipres.jar — charting library
collections.jar — required only if working with the delivery APIs or bursting engine
i18nAPI_v3.jar — internationalization library used for localization functions
jewt4.jar — charting support library
orai18n.jar — character set and globalization support files.
share.jar — charting support library
versioninfo.jar
xdochartstyles.jar — additional chart styles not included in BI Beans
xdocore.jar — core BI Publisher library
xdoparser.jar — scalable XML parser and XSLT 2.0 engine
xmlparserv2.jar — main XML parser and XSLT engine
This section contains a correction to Oracle Business Intelligence Publisher User's Guide. This correction was made in the 10.1.3.4 version of the guide.
In Oracle Business Intelligence Publisher User's Guide, in the chapter "Using the Admin Functions", section "Setting Up Data Sources", subsection "Adding a JDBC Data Source", the format for the JDBC connection string for an Oracle database is incorrectly shown as:
jdbc:oracle:thin@server:port:sid
The correct format includes a colon after "thin" as follows:
jdbc:oracle:thin:@server:port:sid
This section contains a correction to the Oracle Business Intelligence Publisher help. This correction affects the 10.1.3.4 version of the help.
The online help included with the Template Builder Add-in for Microsoft Word states the following:
The Template Builder can be used with a BI Publisher configuration file. The configuration file must be named xdoconfig.xml and must be stored in the
config directory (example path: C:\Program Files\Oracle\BI Publisher
Desktop\config) under the BI Publisher directory.
The path to the config directory is incorrect. The path should be noted as:
C:\Program Files\Oracle\BI Publisher Desktop\Template Builder for Word\config
This section contains a correction to Oracle Business Intelligence Disconnected Administration Guide. This correction was made in the 10.1.3.2 version of the guide.
Chapter 4 contains a section called Step 4: Creating the Local Oracle BI Presentation Catalog. That section contains a list of steps to perform after you create the local Oracle BI Presentation Catalog. These steps should be rewritten as follows:
Archive the folder version of the catalog using the ONLINE archive option in the Administration settings of Oracle BI Presentation Services. If you perform the archive offline (using the Catalog Manager), then all necessary structures are not included and synchronization fails.
Place the archive of the catalog in the disconnected application metadata directory for the appropriate disconnected application.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When attempting to read an Oracle BI RSS feed, trouble authenticating an RSS reader using Single Sign-On might result from the way Oracle SSO is intercepting requests from that particular RSS reader. In this case, Oracle cannot control the feed reader application.
There are two scenarios, however, where SSO might be supportable: Using a browser based RSS reader like Wizz RSS for Firefox and using Firefox to log in to SSO before accessing the feed, or using Windows Integrated authentication with an RSS reader that uses Internet Explorer behind the scenes. Firefox can also support Windows authentication and hence it might also be usable there. Any particular deployment strategy must be validated by a specific customer.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
To complement the HardenXSS configuration setting, the ability to save content that contains script and other potentially unsafe markup (HTML) is now controlled using the "Save Content with HTML Markup" privilege. This privilege is usually granted to administrators by default and possibly to special Dashboard builder roles. If a user does not have this privilege, then that user cannot persist potentially unsafe content through all input channels (such the user interface, direct GET/POST, or SOAP). Catalog migrations assume that all existing catalog content that contains script or markup has been previously approved. This check is then applied to the submission of any new content.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you are using Microsoft Internet Explorer 6 or 7 over SSL (that is, https://), then you cannot open PDF or other binary documents. This is an Internet Explorer issue that results when the header "Cache-Control: No Cache" is present in an HTTP response. For more information see the following Microsoft documents:
Internet Explorer file downloads over SSL do not work with the cache control headers (http://support.microsoft.com/kb/323308/en-us)
Prevent caching when you download active documents over SSL (http://support.microsoft.com/kb/815313/)
For Oracle Application Server deployments, the workaround for this issue is to modify the mod_osso.conf file as follows:
Locate the following entry in the mod_osso.conf file:
<Location /xmlpserver>
require valid-user
AuthType Basic
</Location>
Modify this entry as follows:
<Location /xmlpserver>
require valid-user
AuthType Basic
OssoSendCacheHeaders off
Header unset Pragma
Header unset Cache-Control
Header unset Vary
</Location>
For non-Oracle Application Server deployments, see the Microsoft documents noted in this section for possible resolutions that can be implemented in your environment and your application server documentation for information on turning off the "Pragma" and "Cache-Control" HTTP header properties.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The Oracle BI Server can access Oracle Retail Predictive Application Server (RPAS) data stores through the RPAS ODBC driver. Customers must configure the RPAS ODBC driver to support SQLExtendedFetch, by clicking that option in the ODBC connection setup.
When the RPAS ODBC connection is configured with this option, the BI Server can issue queries using the "Oracle RPAS" data source definition and accompanying database features that are defined in the Physical Layer of the Oracle BI Administration Tool.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Release 10.1.3.4 introduces a migration utility for Discoverer relational metadata. Note the following issues about the utility:
Complex folders based on other complex folders cannot be migrated
automatically using the migration assistant.
The documentation for the utility contains Section 3.4.10 "Item Hierarchies." That section contains the following paragraph:
"All hierarchies based on a folder will be migrated to a single Dimension
created on the folder. Item Hierarchies based on Complex Folders will not be
migrated since a Dimension in SAS must be associated with a Dimension table.
Hierarchies spanning tables will be migrated by setting the Preferred Drill
Path appropriately."
That paragraph should appear as follows:
"All hierarchies based on a folder are migrated to a single Dimension
created on the folder. Item Hierarchies based on Complex Folders are not migrated because a Dimension in Oracle BI EE must be associated with a
Dimension table. Hierarchies spanning tables are migrated by setting the
Preferred Drill Path appropriately."
The following information corrects the description of configuration options in Section 3.3.4 of the metadata conversion assistant documentation.
Settings: A comma-delimited list of JOIN_ID to be skipped during migration. Any JOIN_ID listed here is excluded during migration.
Settings: A comma-delimited list of folder_id (available in the Filename.exception.log) for which the skipped joins must be accommodated during migration. This is used with ConsiderMultiplePaths = FALSE. If ConsiderMultiplePaths = TRUE, then by default all the skipped joins are considered except those configured with ExcludeJoins property.
This issue applies to Version 10.1.3.4.1 and 10.1.3.4.2.
Configuration for the Oracle BI EE analytics J2EE application can be moved outside the web.xml file and stored in a file somewhere on disk. The location of this file must be specified in the web.xml file. A single EAR file can be installed on all nodes in any given deployment if the same file system path is accessible on all nodes.
For example, consider a web.xml file that looks like:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"> <web-app> <servlet> <servlet-name>SAWBridge</servlet-name> <servlet-class>com.siebel.analytics.web.SAWBridge</servlet-class> <init-param> <param-name>oracle.bi.presentation.sawbridge.configFilePath</param-name> <param-value>/u/applic/biapps/OracleBIData/web/config/sawbridgeconfig.txt</param-value> </init-param> </servlet> <servlet-mapping> <servlet-name>SAWBridge</servlet-name> <url-pattern>/saw.dll/*</url-pattern> </servlet-mapping> <mime-mapping> <extension>xsd</extension> <mime-type>text/xml</mime-type> </mime-mapping> <welcome-file-list> <welcome-file>default.jsp</welcome-file> </welcome-file-list> </web-app>
An EAR file that containing this web.xml file can now be installed on any node in the deployment. This requires that:
Every node be able to access a file located at /u/applic/biapps/OracleBIData/web/config/sawbridgeconfig.txt.
Java and operating system security for the application server should permit the analytics J2EE application to read this file from the file system.
Sample contents of the /u/applic/biapps/OracleBIData/web/config/sawbridgeconfig.txt file are as follows:
oracle.bi.presentation.sawserver.Host = localhost oracle.bi.presentation.sawserver.Port = 9710
This is a simple Java property file that can contain all of the configuration entries that you can populate into web.xml as documented in Oracle Business Intelligence Infrastructure Installation and Configuration Guide and Oracle Business Intelligence Enterprise Edition Deployment Guide. The previous two entries are displayed only by way of example. Another sample showing a clustered configuration follows:
oracle.bi.presentation.sawservers = server1:9710;server2:9710;server3:9710
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The documentation supplied with Oracle BI Suite Enterprise Edition Version 10.1.3.2 (and 10.1.3.2.1) accurately describes Version 10.1.3.4.2 as well. As the Version 10.1.3.2 documentation has not been updated for Version 10.1.3.4.2, the title pages continue to show 'Version 10.1.3.2'. The only new documents for Version 10.1.3.4.2 are:
Oracle Business Intelligence New Features Guide
Oracle Business Intelligence Publisher New Features Guide
System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition
Use the above mentioned documents to supplement the Version 10.1.3.2 documentation included in the documentation library.
|
 Copyright © 2009, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|