Skip Headers

Oracle® Business Intelligence Beans Installation Guide and Release Notes
10 g Release 2 (10.1.2.0.0)
Part No. B15780-01
 

 

Copyright © 2005  Oracle. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Oracle® Business Intelligence Beans

Installation Guide and Release Notes

10 g Release 2 (10.1.2.0.0)

Part No. B15780-01

January 10, 2005

This document provides installation instructions and release notes for Oracle Business Intelligence Beans ("OracleBI Beans"). The installation instructions explain how to install OracleBI Beans into an existing Oracle JDeveloper 10.1.2 directory. The release notes describe known issues and workarounds for OracleBI Beans.

The 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 Web site (http://www.oracle.com/technology/products/bi/index.html).

The following list describes the sections of this document:

1 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

                                                                          http://www.oracle.com/accessibility/                                   
                                

Accessibility of Code Examples in Documentation

 JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

 This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

2 Information about OracleBI Beans

OracleBI Beans is a set of standards-based JavaBeans™ that provides analysis-aware application building blocks designed for Oracle OLAP. Using Oracle JDeveloper and OracleBI Beans, you can build Web applications quickly and easily. These applications expose the advanced analytic features of the Oracle database both to casual information viewers and to high-end users who require complete ad-hoc query and analysis functionality. For more information, consult the following:

  • "Getting Started with BI Beans" -- a topic in the JDeveloper Help system; includes links to tutorials.

  • OracleBI Beans API Reference -- accessible from the JDeveloper Help system; look under Reference in the table of contents.

  • OracleBI Beans samples -- designed to assist you in coding common application tasks. They are published on the Oracle Business Intelligence Web site (http://www.oracle.com/technology/products/bi/index.html).

3 System Requirements

This section provides the following information about requirements for installing OracleBI Beans:

3.1 Software requirements

OracleBI Beans offers an extension for Oracle JDeveloper. Before you can install OracleBI Beans, you must download Oracle JDeveloper 10.1.2 from Oracle Technology Network and install it on your computer. For instructions, consult the Oracle JDeveloper 10g Installation Guide, which you can access with other JDeveloper documentation on Oracle Technology Network at the following address.

http://www.oracle.com/technology/software/products/jdev/index.html

Important: Ensure that you download Oracle JDeveloper 10.1.2 rather than an older or a more recent version of Oracle JDeveloper.

3.2 Hardware requirements

Your computer must meet the minimum hardware requirements that are described in the Oracle JDeveloper 10g Installation Guide. In addition, your computer must have approximately 101MB of hard drive space for installing OracleBI Beans.

4 Installation Instructions

OracleBI Beans does not require an installer. To install OracleBI Beans, you need an unzip tool. You can download a free cross-platform unzip tool that is called Info-Zip from www.info-zip.org.

The file that you download from Oracle Technology Network is called bibeans1012.zip.

Important: Do not install this OracleBI Beans release into any existing ORACLE-HOME directory. You will be unable to uninstall it using Oracle Universal Installer.

The remainder of this document uses jdev_install to represent the directory location in which Oracle JDeveloper 10.1.2 was installed. For example, if Oracle JDeveloper 10.1.2 was installed in c:\jdev10g, then the jdev_install would be c:\jdev10g.

This section provides the following information about installing OracleBI Beans:

4.1 Installing OracleBI Beans on a Windows Platform

Perform the following steps to install OracleBI Beans on a Windows platform:

  1. Unzip the bibeans1012.zip file into the same directory in which the standalone Oracle JDeveloper 10.1.2 is installed.

  2. When you are prompted to overwrite existing files, always choose Yes.

4.2 Installing OracleBI Beans on a Non-Windows Platform (Not Certified)

Perform the following steps to install OracleBI Beans on a non-Windows platform:

  1. Unzip the bibeans1012.zip file into the same directory in which the standalone Oracle JDeveloper 10.1.2 is installed, using a command such as the following one:

    unzip -o bibeans1012.zip -d jdev_install

    Important: Always include the -o switch to ensure that all appropriate files from the bibeans1012.zip file overwrite existing files and allow OracleBI Beans to function properly.

  2. When you are prompted to overwrite existing files, always choose Yes.

  3. Once the files are extracted, ensure that they all have read permission by entering the following command:

    chmod -R g+r jdev_install

  4. To ensure that you can run the OracleBI Beans Catalog scripts, give those files execute permission by entering the following command:

    chmod +x jdev_install /bibeans/bin/*.csh

  5. To ensure that you can run the OracleBI Beans check configuration utility give those files execute permission by entering the following command:

    chmod +x jdev_install /bibeans/bi_checkconfig/*.csh

5 Starting OracleBI Beans (and Oracle JDeveloper)

To work with OracleBI Beans, run JDeveloper:

  • For Windows: To start JDeveloper, run the program jdev_install \jdev\bin\jdevw.exe. If you want to run JDeveloper with the console window visible (which enables you to monitor messages), then run jdev_install \jdev\bin\jdev.exe.

  • For Linux, Solaris, and HP-UX: To start JDeveloper, run the program jdev_install /jdev/bin/jdev.

6 Post-Installation Tasks

Complete the post-installation tasks that are appropriate for your site. Note that:

  • Before you can install OracleBI Beans Catalog, you need access to a database user with DBA role privileges.

  • Before you can connect to data in JDeveloper, you must install and configure Oracle Database.

  • The preparation steps in JDeveloper affect the entire JDeveloper environment, including the embedded OC4J instance.

6.1 Database Considerations

OracleBI Beans supports data stored in Oracle9 i Enterprise Edition or Oracle Database 10 g Enterprise Edition. However, only particular releases and patchsets are supported:

  • Oracle9 i Release 2 Enterprise Edition, as follows:

    • 9.2.0.6 for all platforms.

    • 9.2.0.5 with the latest OLAP patch for Windows-only.

  • Oracle Database 10 g Release 1 Enterprise Edition with the latest OLAP patch.

6.1.1 Preparing an Oracle9 i Release 2 Database for Use with OracleBI Beans

Complete the following tasks to run against Oracle9 i Release 2 Enterprise Edition:

  1. If you have not already done so, install Oracle9 i Release 2 Enterprise Edition (9.2.0.6 for all platforms or 9.2.0.5 with the latest OLAP patch for Windows-only). For instructions, download the Oracle9 i installation guide for the appropriate platform from Oracle Technology Network ( http://www.oracle.com/technology ).

    Note: When you install the database client, be sure to install it into a separate ORACLE-HOME directory.

  2. If you have not already done so, on the same server download and install the appropriate Oracle9 i OLAP patch from Oracle MetaLink ( http://metalink.oracle.com ).

    As of this writing, the latest 9.2.0.5 Windows patch is 3952897.

    For instructions on downloading patches from Metalink, see Section 6.1.3, "Downloading the Most Recent OLAP Patch".

  3. Configure the database, following the configuration settings shown in Best Practices for Tabular Cube Aggregation and Query Operations. To access this document, download patch set 2529822. You must follow these configuration settings exactly to ensure that OracleBI Beans works correctly and performs well. Because this document is updated as needed, check for a new version whenever you download a new patch set.

  4. Define the appropriate OLAP metadata, as described in the Oracle9i OLAP Release 2 - User's Guide. This book is available on Oracle Technology Network ( http://www.oracle.com/technology ). You can also refer to the Help system for the OLAP management tool of Oracle Enterprise Manager, which is a tool that you use to create the metadata. As an alternative, you can create metadata using OracleBI Warehouse Builder. If you do not define appropriate metadata, then you will not be able to create OLAP queries.

6.1.2 Preparing Oracle Database 10 g for Use with OracleBI Beans

To run against Oracle Database 10 g, complete the following tasks:

  1. If you have not already done so, install Oracle Database 10 g Release 1 Enterprise Edition. For instructions, download the Oracle Database 10 g installation guide for the appropriate platform from Oracle Technology Network ( http://www.oracle.com/technology ).

    Note: For Linux, Linux Itanium, and Solaris x86 platforms, you can install version 10.1.0.3 after downloading it from Oracle Technology Network. For all other platforms, you must first download version 10.1.0.2, then apply the appropriate patch set for 10.1.0.3.

    When you install the database client, be sure to install it into a separate ORACLE-HOME directory.

  2. If you have not already done so, on the same server download and install the appropriate Oracle OLAP 10 g patch from Oracle MetaLink ( http://metalink.oracle.com ).

    At the time of writing, the latest patch set number for Windows is 3769360.

    For instructions on downloading patches from Metalink, see Section 6.1.3, "Downloading the Most Recent OLAP Patch".

  3. Configure the database, following the configuration settings shown in Best Practices for Tabular Cube Aggregation and Query Operations. To access this document, download patch set 3760779. You must follow these configuration settings exactly to ensure that OracleBI Beans works correctly and performs well. Because this document is updated as needed, check for a new version whenever you download a new patch set download a new patch set.

  4. Define the appropriate OLAP metadata, as described in the Oracle OLAP Application Developer's Guide. This book is available on Oracle Technology Network ( http://www.oracle.com/technology ). If you do not define appropriate metadata, then you will not be able to create OLAP queries. Use one of the following tools to define the metadata:

    • The OLAP management tool of Oracle Enterprise Manager. See the Help system for Oracle Enterprise Manager for information.

    • OracleBI Warehouse Builder. See the OracleBI Warehouse Builder User's Guide for information.

    • Analytic Workspace Manager. See the Oracle OLAP Application Developer's Guide for information.

6.1.3 Downloading the Most Recent OLAP Patch

When querying a multidimensional data source, only particular database releases and patches are supported. For more information, see Section 6.1, "Database Considerations".

To access the latest OLAP patches:

  1. Log into Oracle Metalink at http://metalink.oracle.com .

  2. Click Patches.

  3. Click Advanced Search.

  4. In the Advanced Search screen, fill in the fields as follows:

    • Product or Product Family: Click the Search icon, and from the Search In field, choose Database & Tools. Click View All. From the resulting list, click Oracle OLAP.

    • Release: Select the appropriate release number from the drop-down list.

    • Patch Type: Choose Any.

    • Platform or Language: Select the platform for your site.

    • Leave the remaining fields blank.

    Click Go to display a list of patches. You can identify the OLAP patches because they include "OLAP" in the patch name.

6.2 Additional Tasks

In addition to preparing the database, perform the following tasks, as appropriate for your site:

  • Migrate existing OracleBI Beans projects. See Section 7, "Migrating Existing OracleBI Beans Projects" for information.

  • By default, JDeveloper expects the JDK to be in the ..\..\jdk directory (Windows) or in the /usr/java/jdk1.4 directory (Linux, Solaris, and HP-UX). If your JDK is not in the default location, then you must edit jdev_install /jdev/bin/jdev.conf to change the setting of the SetJavaHome option.

  • During design with JDeveloper, your analyses are saved in your project. However, if you or your end-users want to be able to share analyses and objects with other developers and end users, then you must install and configure the OracleBI Beans Catalog, as described in the topic "Installing and Configuring the OracleBI Beans Catalog" in the OracleBI Beans Help system.

    Important: Before installing the Catalog, see Section 6.2.1, "Checking the Block Size when Installing the OracleBI Beans Catalog".

  • To test your applications, you must install your chosen deployment environment. For more information, see the topic, "Requirements for the Deployment Environment" in the OracleBI Beans Help system.

  • OracleBI Beans includes a utility that examines and reports on the configuration of your client environment. The purpose of the configuration diagnostic utility is to gather information about your configuration in order to diagnose problems. It displays information such as the release numbers for OracleBI Beans, JDeveloper, and the Oracle Database, and it runs diagnostic tests against the OLAP Catalog metadata.

    For complete information, see the topic "Verifying an OracleBI Beans Client Configuration" in the OracleBI Beans Help system.

6.2.1 Checking the Block Size when Installing the OracleBI Beans Catalog

Before installing the Catalog, you must determine what the block size of the database is. You can ask your database administrator for information about the block size.

Because an analytic workspace has a recommended 8KB block size, you will likely want to use that size. However, in some cases, this size might not be large enough. In other cases, a size of 2KB or 4KB might be large enough, depending on various requirements such as the character set in use.

Perform the following steps to install the Catalog with the appropriate block size:

  1. Set the block size by doing one of the following:

    • Rebuild the database using an appropriate database block size.

    • Create a custom tablespace for the Catalog with an appropriate block size. For example, to create a tablespace that is named BIBCATIDX with a block size of 8K, use a command such as the following one:

      CREATE TABLESPACE BIBCATIDX DATAFILE 'file_1.f' SIZE 128M BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K

  2. Install the OracleBI Beans Catalog, as described in the topic "Installing and Configuring the OracleBI Beans Catalog" in the OracleBI Beans Help system. If you chose to create a custom tablespace in Step 1, then use that tablespace name as the value for the -ti parameter when you run the bi_installcatalog script.

If the block size is not large enough, then you might see an error message such as the following one when you try to install the Catalog:

ORA-01450: maximum key length number exceeded

where number represents an integer such as 1478. This error message indicates that during the creation of the Catalog, an attempt was made to create an index using a key size that is larger than maximum allowed value. The index key size is limited by the value of the block size for the database or for the tablespace, because a key value cannot span multiple blocks.

7 Migrating Existing OracleBI Beans Projects

This section provides instructions for migrating existing OracleBI Beans projects from Oracle9 i JDeveloper (9.0.4). This section includes the following topics:

7.1 Migrating the Oracle OLAP instance (Optional)

OracleBI Beans 10.1.2 applications can run against Oracle9 i Release 2 Enterprise Edition or Oracle Database 10 g Release 1 Enterprise Edition. Before performing other migration steps, you must decide which database version to use, as described in the following list:

  • If you want to upgrade OracleBI Beans applications to run against Oracle9 i Release 2 Enterprise Edition and the applications currently run against an earlier version of the database, then you must upgrade the database before migrating the applications. For information, see Oracle9i OLAP Release 2 - Installation Guide. Ensure that you are using version 9.2.0.6 for all platforms or 9.2.0.5 with the latest OLAP patch for Windows-only.

  • If you want to upgrade OracleBI Beans applications to run against Oracle Database 10 g Release 1 Enterprise Edition, and the applications currently run against an earlier version of the database, then you must upgrade the database before migrating the applications. For complete migration information for Oracle OLAP, refer to the Oracle OLAP Application Developer's Guide for the Oracle Database 10 g release.

7.2 Migrating the OracleBI Beans Catalog

To migrate a remote Catalog, run the upgrade utility that is delivered with OracleBI Beans. The following list provides the name and location of the utility, where jdev_install is the directory into which JDeveloper is installed:

  • On MS Windows XP/2000, the utility is named bi_upgradecatalog.bat and is located in the jdev_install \bibeans\bin directory.

  • On Sun Solaris (SPARC), the utility is named bi_upgradecatalog.csh and is located in the jdev_install /bibeans/bin directory.

Important: You can use the utility to upgrade only from OracleBI Beans version 9.0.3 or version 9.0.4 to OracleBI Beans version 10.1.2. Always run the utility that is delivered with the most recent version of OracleBI Beans.

For complete information about the Catalog migration utility, see the topic "OracleBI Beans Catalog Upgrade Utility" in the OracleBI Beans Help system.

7.3 Migrating User Settings from Previous Releases

You can migrate user settings from the production release of Oracle9 i JDeveloper (9.0.4) to Oracle JDeveloper10 g. When you open Oracle JDeveloper10 g for the first time, you are prompted to migrate your user settings from the previous version. By default, all settings are marked for migration. Allow the user settings to be upgraded, especially the database connections. If those connections are not migrated, then you must re-create any connections that are referenced by BIDesigners that exist in any of the workspaces that you will migrate.

Oracle does not support direct migration from Oracle JDeveloper version 3.2.3 to Oracle9 i JDeveloper (9.0.4) or later.

7.4 Migrating the OracleBI Beans Workspaces

Perform the following steps in order to migrate the projects:

  1. Before migrating any workspaces, create backup copies of those workspaces.

  2. If you did not automatically migrate database connections as described in Section 7.3, "Migrating User Settings from Previous Releases", then migrate those connections before proceeding. In Oracle JDeveloper10 g, display the Connection Navigator, right-click Database, and choose Import Connections.

    Ensure that you complete this step before opening a BIDesigner that uses a connection from Oracle9 i JDeveloper (9.0.4).

  3. Allow JDeveloper to migrate the project.

    Migrate a workspace that was created in Oracle9 i JDeveloper (9.0.4) or a project that was created in Oracle9 i JDeveloper (9.0.4) that you are now adding to a workspace in Oracle JDeveloper10 g. If you start Oracle JDeveloper10 g and open an OracleBI Beans workspace from Oracle9 i JDeveloper (9.0.4), then you will see the Migration wizard. This wizard can perform many migration steps automatically. For example, the wizard updates the workspace to the correct Oracle JDeveloper10 g version. You can allow other options to run automatically, such as the update of the UIX Installables and the data binding syntax in HTML applications, as appropriate.

    Allow the wizard to migrate any local Catalogs automatically. In the wizard, you can also specify whether to back up the Catalogs before migrating. If you do not want to migrate certain local Catalogs, then you can deselect them in the wizard. Refer to Section 7.2, "Migrating the OracleBI Beans Catalog" for information on upgrading remote Catalogs.

  4. After the automatic upgrade completes, turn on Deprecation Warnings in the Compiler options, compile the application code to identify any deprecated classes or tags that you need to replace, and fix the errors that you see.

  5. Edit the project settings by removing the following line to ensure that this option is not set. If this option is set, then JDeveloper uses the older version of JDBC rather than the newer version.

    -Djava.ext.dirs=C:\Jdev\JDev904_2.7.5.32.1\jdev\lib\patches

  6. Perform the appropriate steps that are described in the following sections, depending on the kind of application that you have:

7.4.1 Manual Migration Steps for JSP Applications

Perform the manual migration steps that are described in the following sections for JSP applications:

7.4.1.1 Updating the Namespace

Edit the namespace in the initial line of code in each page by appending "/jsp" to the existing namespace as shown in the following example:

Before edit: <%& taglib uri="http://xmlns.oracle.com/bibeans" prefix="orabi" %>

After edit: <%& taglib uri="http://xmlns.oracle.com/bibeans/ jsp " prefix="orabi" %>

7.4.1.2 Accessing New BI JSP Tag Functions

If you want to access the JSP tag functions that are new to this release of OracleBI Beans, then you must perform the following steps:

  1. Add the following text to the top of all the JSP pages in the migrated application:

    <%@ taglib uri="#" prefix="c"%>

  2. Ensure that the JSTL tag libraries are in the project, by performing the following steps:

    1. Check the <project> \public_html\WEB-INF\lib directory to see if it contains the standard.jar file. If it does not, then perform Steps b and c.

    2. Open any JSP page in the migrated project. In the Component Palette, select JSTL Core. Drag the "out" tag to the page. Choose OK in the tag editor.

    3. In the JSP page, locate the <c:out></c:out> tag and remove it.

      Check the <project> \public_html\WEB-INF\lib directory again. The standard.jar file should be there.

7.4.1.3 Updating the <body> Tag

Update the HTML <body> tag in each page that contains a BIThinSession tag. After you edit the namespace, you must update the BIBody tag and the InitBITags tag. You can simply drag and drop the BIBody tag on the page when it is displayed in the Visual Editor. You can drag and drop the InitBITags tag as the first child of the form.

If the drag-and-drop technique is not effective, then you can edit the tags manually, as described in the following steps:

  1. Remove the <body> tag and in its place insert the following required BI tags: BIBody (before the HTML <form> tag) and InitBITags (after the HTML <form> tag).

  2. Set the action attribute of the <form> to the name of the JSP page.

  3. Set the method attribute to POST.

  4. Set the parentForm attribute of InitBITags to the name of the <form>.

The following code shows an example of these tags in a page named "biexplorerdetail1.jsp":

<orabi:BIBody><form name="BIForm" method="POST" action="biexplorerdetail1.jsp" ><orabi:InitBITags parentForm="BIForm"/>

Note: Ensure that there are no slashes in the specification for the name of the JSP page. In addition, replace the end tag </body> with </orabi:BIBody>

7.4.1.4 Updating Code that Accessed a Presentation

If your application contains a scriplet in the JSP page or has Java code that accessed the presentation through its ID and cast it to a ThinDataviewCommon, then you now must cast it to a Presentation bean and get the data view from the bean.

To accomplish this, change a line of code such as the following one:

ThinDataviewCommon dataView = (ThinDataViewCommon)pageContext.findAttribute ("biuntitled1_pres1");

to read like this:

ThinDataviewCommon tdvc = null; Presentation p = ( Presentation )pageContext.findAttribute ("biuntitled1_pres1"); if (p != null) tdvc = p.getView();

Add the following import to access the new Presentation bean: oracle.dss.thin.beans.dataView.Presentation;

7.4.1.5 Updating the SaveButton JSP Tag

The SaveButton JSP tag has been replaced by the SaveLink tag. If your application uses the SaveButton JSP tag, then you can update the application by performing the following steps:

  1. In the BIThinSession, locate a SaveButton tag that is similar to the following one:

    <orabi:SaveButton id="analyze1_SaveButton1" presentationId="analyze1_Presentation1" saveConfirmationPage="saveconf1.jsp" saveConfirmationId="saveconf1_SaveConfirmation1" />

    Modify the SaveButton tag to use the SaveLink tag, as shown in the following example:

    <orabi:SaveLink id="analyze1_SaveButton1" mode="Save" presentationId="analyze1_Presentation1" />

  2. Modify the Render tag for the SaveButton tag. For example, suppose that you have a Render tag that is similar to the following one:

    <orabi:Render targetId="analyze1_SaveButton1" parentForm="BIForm"/>

    Edit the Render tag so that it is similar to the following one:

    <orabi:Button text="Save" onClick="${analyze1_SaveButton1_data.showDialog}"/>

When users click the Save button, they will see the internal save page.

7.4.2 Manual Migration Steps for UIX Applications

Perform the manual migration steps that are described in the following sections for UIX applications. These steps assume that you used the UIX application that the BI Beans generated as the basis for your custom application.

7.4.2.1 Updating the Path of Images

If a workspace contains images, then you must copy the images and update the path of the images in the BIPageTemplate UIT file and in the login UIX file, as described in the following steps:

  1. Update the source path for all the images in the BIPageTemplate UIT file and on the login UIX pages. In Oracle9 i JDeveloper (9.0.4), the images are stored in the public_html\cabo\images\ <app_name> directory. In Oracle JDeveloper10 g, the images are stored in the public_html\ <app_name> directory

    For example, the specification for this directory is made in a tag such as the following one in the UIT file: <images source="cabo\images\< app_name >\required.gif">

    Modify this tag to read as follows: <images source="< app_name >\required.gif">

  2. If the application uses custom images, then copy the images to the appropriate directory for Oracle JDeveloper10 g, as specified in Step 1.

7.4.2.2 Updating the Error Page

While migrating, you might receive a message that describes a problem with the error page in the UIX application. To resolve this problem, you can do one of two things:

  • If you want to use the default error page that is supplied automatically by OracleBI Beans 10.1.2, then remove the previously existing error page before migrating the project to OracleBI Beans 10.1.2.

  • If you have customized the default error page and do not want to lose your modifications, then before migrating, edit the <bibeans:biPageTemplate> element and remove the renderLogoutButton attribute. For example, the element might read as follows:

    <bibeansTemplate:biPageTemplate xmlns="http://xmlns.oracle.com/uix/ui" xmlns:data="http://xmlns.oracle.com/uix/ui" xmlns:ctrl="http://xmlns.oracle.com/uix/controller" renderLogoutButton="false" renderOpenButton="false" pageTitle="BI uiXML Application Error">

    Simply edit the element to remove the text that reads renderLogoutButton="false".

    After editing the element, modify the web.xml file. The error page entry reads as follows:

    <init-param> <param-name>oracle.cabo.servlet.errorPage</param-name> <param-value>cabo/bi/uix/error</param-value> </init-param>

    Change the value cabo/bi/uix/error to point to your customized error page.

7.4.2.3 Adding an Element for Partial Page Rendering

You must edit template pages that use partial page rendering (PPR) functions. Add a <body> element to the application code, as shown in the following example:

<contents> <body> <contents> <form name="form1" method="POST"> <contents>

Ensure that you add a </body> tag at the appropriate location.

7.4.2.4 Adding Code for Each dialogLinkDef Element

In Oracle JDeveloper10 g, to bind a dialogLink to the onClick attribute of a button, a link, or an image, you must bind to the dataObject of the dialogLink through the key, "showDialog". For example, assume that the id of a dialogLink is dlgLnk1, and it is defined in the BIThinSession, bisession1.

In Oracle9 i JDeveloper (9.0.4), the code looks like this: <button onClick="${bibeans:data().bisession1.dlgLnk1}"/>

In Oracle JDeveloper10 g, the code looks like this: <button onClick="${bibeans:data().bisession1.dlgLnk1_data.showDialog}"/>

7.4.2.5 Updating Code that Accessed a Presentation

If your application contains Java code that accesses the presentation through its ID and casts it to a ThinDataviewCommon, then you now must cast it to a Presentation bean and get the data view from the bean.

To accomplish this, change a line of code such as the following one:

ThinDataviewCommon dataview = (ThinDataViewCommon) pageObjects.get("< parameter >");

to read like this:

Presentation presentation = ( Presentation ) pageObjects.get("< parameter >");ThinDataviewCommon dataview = null;if (presentation !=null) dataview=presentation.getView();

In the Java code for the previous version of the UIX application, there are two instances in which you must make this code change.

Add the following import to access the new Presentation bean: oracle.dss.thin.beans.dataView.Presentation;

7.4.2.6 Updating the SaveDef UIX Tag

In the current release, the saveConfirmation tag has been deprecated and replaced by the SaveDef UIX tag. Use the internal save dialog page, which is supplied automatically, rather than the saveConfirmation page.

For example, the original lines of code might look similar to the following ones:

<bibeans:saveDef id="saveBtn1" presentationId="pres1" saveConfirmationPage="SaveConfirm1.uix" saveConfirmationId="saveConf1" />

Rewrite the code so that it looks similar to the following line:

<bibeans:saveDef id="saveBtn1" presentationId="pres1" mode="Save" />

When users click the Save button, they will see the internal save page.

7.4.3 Manual Migration Steps for Java-Client Class Applications

Perform the manual migration steps that are described in the following sections for applications that use the Java-client class:

7.4.3.1 Graph Code Changes

If you use a graph in the application, then you must make the following code change. Change the following line of code:

((GraphLayout) layout).setGraph((UIGraph) dv);

to read like this:

((GraphLayout) layout).setGraph((Graph) dv);

7.4.4 Manual Migration Steps for Java Servlet Applications

Before migrating a servlet application, consider whether you have added many custom pages or functionality. If you have not added substantial customizations, then you can generate a JSP or UIX application and recreate any customizations there. By switching to a JSP or UIX application, you can easily take advantage of the powerful new features that are available in OracleBI Beans.

If you want to migrate a servlet application, then perform the manual migration steps that are described in the following sections:

7.4.4.1 Updating the Installables in the Cabo Directory For Servlet Applications

When you migrate a JSP or UIX application, the installables in the cabo directory are updated automatically. These installables are not updated automatically for servlet applications. The cabo directory contains the UIX and OracleBI Beans images, style sheet, and Javascript files, which have been updated between Oracle9 i JDeveloper (9.0.4) and Oracle JDeveloper10 g. Perform the following steps to update the installables in the cabo directory for servlet applications:

  1. Navigate to the public_html directory of the project to be upgraded.

  2. Rename the cabo directory to cabo.9.0.4.

  3. Create a new UIX or JSP page using the same BIDesigner as in the servlet application.

    When the page is generated, it creates a new cabo directory for the project.

  4. If your old directory ( cabo.9.0.4) contained any other files (for example, if you created a new style sheet or .xss file or application-specific image files), then you must copy those files to the new cabo directory

  5. (Optional) You can safely delete the new page that was created.

7.4.4.2 Consulting Samples for Servlet Applications

OracleBI Beans ships with a set of servlet application samples. Consult these samples for best practices in handling servlet applications in Oracle JDeveloper10 g. For example, see the code that affects the ViewToolbar and modify your application code accordingly. The ViewToolbar is not backward compatible.

8 Release Notes

This section provides release notes for OracleBI Beans. It contains the following topics:

8.1 Updating a Project to use the Thin QueryBuilder

Suppose that you have an application that was created in an earlier version of JDeveloper and that contains a presentation. If you migrate and deploy that application in JDeveloper 10.1.2 and you use the thin QueryBuilder to edit that presentation, then you might notice that the Start With page has no measures selected. To workaround this issue, complete the following steps:

  1. Edit the presentation in JDeveloper.

  2. Using the Items panel in the Presentation Editor, click OK or Apply.

    This action updates the presentation in the Local Catalog.

  3. Use the Copy Objects to Remote Catalog wizard to move the updated presentation to the production Catalog.

8.2 Naming a Project with Spaces

You might notice intermittent problems with OracleBI Beans projects that are created in JDeveloper. These problems are often caused by the fact that the project's J2EE root context contains blank spaces, which in turn is caused by the fact that the project's name contains spaces.

To work around these problems, simply avoid including spaces in the project name. If you really prefer to include spaces in a project name, then modify the default J2EE context root that JDeveloper generates for the project by accessing the Project Settings dialog.

8.3 Connections

You might encounter a problem with the executeCommand method of the Connection object if the input OLAP DML string or the output log information is too long. If this happens, then use the DBMS_AW PL/SQL package through JDBC.

8.4 QueryBuilder and Queries

This section describes issues that involve the QueryBuilder and queries:

  • OracleBI Beans does not support the interspersing of symmetric and asymmetric drill operations. That is, the AsymmetricDrilling property of a Query object should not be changed during that object's lifetime.

  • In DataDirector, if you set the SuppressionState method to either DataDirector.ZERO_SUPPRESSION or DataDirector.NA_ZERO_SUPPRESSION, then the result is the same: both zeros and nulls are suppressed in the results.

  • If you have a Family step that is followed by a keep of an asymmetric saved selection, then you might see duplicate results when connecting to Oracle9 i Release 2, version 9.2.0.5 or 9.2.0.6. This issue has no workaround.

8.5 Presentations

This section describes issues that involve presentations:

  • Because of Sun Java J2SE 1.2 bug 4151279 and Sun J2SE 1.4 regression bug 4749538, pie graphs and other graphs with circular components may not render optimally. You can help to resolve this issue by using graphic anti-aliasing on the graph.

  • When users are exporting to Excel using the Netscape browser and they choose to save the file, only the first page (the table of contents) is saved. The remaining pages are lost. To work around this problem, users should open the file in Excel first, then save it from there. (Note that when they open the file, a Netscape error will indicate that the file is not in the expected location. This error can be ignored.) An alternate workaround is for the application developer to configure Export to Excel so that users download a ZIP file, which can then be extracted and opened in Excel.

  • When you apply formatting to a presentation, a stoplight format always takes precedence, and conditional formats take precedence over formats entered by way of the toolbar. This behavior helps to avoid extraneous rules, which would have a negative impact on performance.

  • When printing a worksheet that contains large numbers in the data cells, the string ####### may be printed instead of the actual numbers.

  • In the Java-client crosstab toolbar, the Start Align button always aligns text to the left. For locales that read right-to-left, use the Right Align button.

  • For non-Windows platforms, crosstabs and graphs are not renderered correctly in the JSP Visual Editor. They are rendered correctly when the page is displayed in the browser. This issue has no workaround.

8.6 OracleBI Beans Catalog

This section describes issues that involve the OracleBI Beans Catalog:

  • If you encounter performance issues on a WAN during the copying of objects to and from the OracleBI Beans Catalog, then Oracle Corporation recommends that you use the Oracle9 i OCI drivers instead of the thin JDBC drivers.

  • In the Applications-Navigator of JDeveloper, use right-mouse menu options for file operations for objects and folders in the Local Catalog. Do not use your operating system's methods for performing such operations.

  • In the 10.1.2 version of the OracleBI Beans Catalog, you can set privileges at the object level. If an OracleBI Beans 9.0.3 or 9.0.4 application connects to an OracleBI Beans 10.1.2 Catalog that has privileges set at the object level, then some objects may not be visible.

8.7 HTML-Client Applications

This section describes issues that involve HTML-client applications:

  • In HTML-client applications, an application developer can allow end users to enter custom text for tooltips in thin graphs. Developers should be aware that this practice enables users to enter Javascript that could be used for malicious purposes. Developers are advised to prohibit end users from entering custom text for tooltips in a thin graph.

  • In HTML-client applications, popup windows (Lists of Values, or LOVs) may stop working in browsers that have third-party toolbars or popup blockers installed, such as the Google or Yahoo toolbars. The following OracleBI Beans components use LOVs:

    • In data views, paging controls launch a FindMember popup.

    • QueryBuilder and CalcBuilder launch a LOVContainer popup.

    You can work around this issue by disabling or hiding the offending toolbars.

  • Occasionally when a partial page rendering action is used to update a component that is contained in paragraph elements (<p>) or invalid HTML, the component might not update correctly and a JavaScript error is generated. To work around this issue, do not place the component in paragraph elements (<p>) or in invalid HTML.

  • When an application developer drags and drops a BI Beans JSP list tag (for example, the DimensionList tag) onto a JSP page, the JDeveloper design-time environment automatically puts the list render tags inside a table component, and the id attribute of the table is set to the name of the List. This is important for partial page rendering to work. If the application developer manually deletes the render tags and drags and drops the list render tags (ListIterator first and then the ListItem tag) directly onto the page, then the developer must manually set the id attribute of the containing element, as shown in the following example:

    <span id="<c:out value="${biuntitled2_dimMemList1_data.listName}"/>"> ... <orabi:ListIterator biList="${biuntitled2_dimMemList1_data}"> ... </span>

  • The FolderList BI Beans JSP tag will not automatically detect whether the application developer has incorrectly specified the tag as the "targetFolderLists". For example, suppose that the following three FolderList tags exist on a page:

    <orabi:FolderList id="A" targetFolderListIds="B"/> <orabi:FolderList id="B" targetFolderListIds="C"/> <orabi:FolderList id="C" targetFolderListIds="A"/>

    If the page is run, then an infinite loop results. The FolderList tag cannot detect this circular reference.

8.8 Accessibility Limitations for OracleBI Beans

This section describes accessibility limitations for OracleBI Beans:

  • The current version of the JAWS screen reader does not correctly identify and read tables in Java applications. This problem occurs in the JDeveloper Help system, which incorporates the OracleBI Beans Help system.

  • JAWS does not read the description for some of the panels in the OLAP Connection wizard.

8.9 Documentation Changes

Oracle Corporation recommends that if your application needs to support localization, then you limit the format of dates to strictly numeric forms, such as 'YYYY-MM-DD'. Text forms and forward slash character produce errors in some languages. An incorrect format was recommended in the topic "Building a BI Beans Application in JDeveloper" in the OracleBI Beans Help system.

8.10 Known Issues with Oracle9 i OLAP Option

This section describes some of the known issues with the OLAP option for Oracle9 i Release 2 Enterprise Edition. These issues affect all products that access OLAP data, including OracleBI Beans.

  • You may encounter performance problems, particularly with large dimensions, if you suppress NA or zero values.

  • If you have a complex query that involves a moving total calculation, then when you navigate the query results, you may see an ArrayIndexOutOfBounds exception.

  • At times, database resources are not properly released. This may result in excessive memory consumption. To release the resources, close the custom OracleBI Beans application.