Skip Headers
Oracle® Business Intelligence Beans Installation Guide and Release Notes
10g Release 2 (10.1.2.2) for Microsoft Windows and Solaris Operating System
Part No. B16033-02
 

 

Oracle® Business Intelligence Beans

Installation Guide and Release Notes

10g Release 2 (10.1.2.2) for Microsoft Windows and Solaris Operating System

Part No. B16033-02

November 27, 2006

This document provides installation instructions and release notes for Oracle Business Intelligence Beans (OracleBI Beans) when downloaded from Oracle Technology Network. The installation instructions explain how to install OracleBI Beans. 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 OracleBI Beans Web site:

http://www.oracle.com/technology/products/bib/index.html

The following list describes the sections of this document:

1 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.

1.1 New Feature

You can use six new graph styles that have been added to this release to create attractive presentations easily. Each new style includes a gradient plot area or a gradient background, or both. The names of the new graph styles are:


April
Comet
Confetti
Glass
Nautical
Southwest

1.2 Additional Resources

For more information about OracleBI Beans, 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 at the following location:

    http://www.oracle.com/technology/products/bi/samples/samples_readme.html

2 System Requirements

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

2.1 Software Requirements

OracleBI Beans offers an extension for Oracle JDeveloper. Before you can install OracleBI Beans, you must download Oracle JDeveloper 10g (Version 10.1.2.2, build 1929) 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 /archives.html

Important: Ensure that you download Oracle JDeveloper 10g (Version 10.1.2.2, build 1929) rather than an older or a more recent version of Oracle JDeveloper.

2.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.

2.3 Database Requirements

Release 10.1.2.2 of OracleBI Beans supports the following versions for the database that contains the data on which you want to report:

  • Oracle9i Release 2 Database (9.2.0.6 and higher)

  • Oracle Database 10g Release 1 (10.1.0.4 and higher)

  • Oracle Database 10g Release 2 (10.2.0.1 and higher)

You must use Oracle Database Enterprise Edition with the OLAP Option.

Tip: If you want to upgrade an analytic workspace from Oracle Database 10g Release 1 to Release 2, then consult the appropriate section in the Oracle OLAP 10g Release 2 Application Developer's Guide.

The latest information on supported versions is on the Certify application on:

http://metalink.oracle.com

2.3.1 Downloading the Most Recent OLAP Patch

When querying a multidimensional data source, only particular database releases and patches are supported. Use the following procedure to ensure that you have the latest OLAP patch.

To access the latest OLAP patches:

  1. Log into OracleMetalink 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.

3 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 bibeans10122.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 10g (Version 10.1.2.2, build 1929) was installed. For example, if Oracle JDeveloper 10g was installed in c:\jdev10g, then the jdev_install would be c:\jdev10g.

Ensure that you use Oracle JDeveloper 10g (Version 10.1.2.2, build 1929) rather than an older or a more recent version of Oracle JDeveloper

This section provides the following information about installing OracleBI Beans:

3.1 Installing OracleBI Beans on a Windows Platform

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

  1. Unzip the bibeans10122.zip file into the same directory in which the standalone Oracle JDeveloper 10g is installed.

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

3.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 bibeans10122.zip file into the same directory in which the standalone Oracle JDeveloper 10g is installed, using a command such as the following one:

    unzip -o bibeans10122.zip -d jdev_install

    Important: Always include the -o switch to ensure that all appropriate files from the bibeans10122.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

4 Starting OracleBI Beans (and Oracle JDeveloper)

To work with OracleBI Beans, run JDeveloper:

5 Post-Installation Tasks

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

5.1 Database Considerations

OracleBI Beans supports data stored in the Oracle9i Release 2 Database or Oracle Database 10g Enterprise Edition. However, only particular releases and patchsets are supported as described in Section 2.3, "Database Requirements".

Consult the following sections, based on the database version to which OracleBI Beans applications will connect:

5.1.1 Preparing an Oracle9i Release 2 Database for Use with OracleBI Beans

Complete the following tasks to run against Oracle9i Release 2 Database:

  1. If you have not already done so, install Oracle9i Database, Release 2.

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

  2. 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.

  3. 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). 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.

5.1.2 Preparing Oracle Database 10g Enterprise Edition for Use with OracleBI Beans

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

  1. If you have not already done so, install Oracle Database 10g Enterprise Edition.

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

  2. 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.

  3. 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.

5.2 Additional Tasks

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

  • See Section 6, "Migrating Existing OracleBI Beans Projects" for migration information.

  • 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 Help topic "Installing and Configuring the BI Beans Catalog."

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

  • 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 "Verifying a BI Beans Client Configuration" topic in the OracleBI Beans Help system.

6 Migrating Existing OracleBI Beans Projects

This section provides instructions for migrating existing OracleBI Beans projects from Oracle9i JDeveloper (9.0.4). If you must migrate projects from an earlier version of OracleBI Beans 10.1.2, then consider performing the optional task that is described in Section 6.5, "Post-Migration Task for the OracleBI Beans Catalog (Optional)". This section includes the following topics:

6.1 Migrating the Oracle OLAP Instance (Optional)

OracleBI Beans 10.1.2 applications can run against Oracle9i Release 2 or Oracle Database 10g Release 1 or 2 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 Oracle9i 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.

  • If you want to upgrade OracleBI Beans applications to run against Oracle Database 10g Release 1 or 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 complete migration information for Oracle OLAP, refer to the Oracle OLAP Application Developer's Guide for the Oracle Database 10g Release 1 or 2 Enterprise Edition.

See Section 2.3, "Database Requirements" for information on the supported database versions.

6.2 Migrating the OracleBI Beans Catalog

To migrate a remote OracleBI Beans Catalog, run the upgrade utility that is delivered with OracleBI Beans. The name and location of the utility differs slightly by platform, as described in the following list:

  • Windows: The utility is named bi_upgradecatalog.bat and is located in the JDEV_HOME\bibeans\bin directory, where JDEV_HOME is the directory into which JDeveloper is installed.

  • Sun Solaris (SPARC): The utility is named bi_upgradecatalog.csh and is located in the JDEV_HOME/bibeans/bin directory, where JDEV_HOME is the directory into which JDeveloper is installed.

Important: You can only use the utility to upgrade from OracleBI Beans version 9.0.3 or version 9.0.4 to OracleBI Beans version 10.1.2.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 Help topic that is called "OracleBI Beans Catalog Upgrade Utility" in the OracleBI Beans Help system.

6.2.1 Additional Step for Migration to Oracle Database 10g Enterprise Edition Release 2

In addition to running the upgrade utility to migrate an existing OracleBI Beans Catalog to Oracle Database 10g Enterprise Edition Release 2 (10.2.0.1 and higher), you must also update a PL/SQL package on the database server by performing the following procedure:

  1. Install the patch as follows:

    1. Locate the bidatasvr.jar in the OracleBI Beans installation directory.

    2. Extract the bibcoreb.pls file from bidatasvr.jar to a local directory. The jar has packing scope and will be extracted into the oracle\dss\persistence\storagemanager\bi\scripts directory.

  2. Apply the patch as follows:

    1. At the command prompt, enter:

      cd oracle\dss\persistence\storagemanager\bi\scripts

    2. Open a sqlplus session. For example, enter:

      sqlplus BIBCAT/BIBCAT@mydb

      where mydb is the connect string and BIBCAT/BIBCAT is the username/password of the owner of the schema that hosts the OracleBI Beans Catalog.

    3. At the sqlplus prompt, enter:

      SQL> @bibcoreb.pls

      This step displays the following output:

      Package body created. 
      Commit complete.
      
      
  3. Ensure that the package is valid as follows:

    1. Reopen the sqlplus session.

    2. Enter the following SQL commands:

      SQL> column OBJECT_NAME format a30;
      SQL> column STATUS format a10; 
      SQL> select object_name, status from user_objects where object_name='BISM_CORE';
      
      

      The following display indicates that the patch has been applied successfully:

      OBJECT_NAME                STATUS
      ------------------------------------------------ 
      BISM_CORE                  VALID
      BISM_CORE                  VALID
      

6.3 Migrating User Settings from Previous Releases

You can migrate user settings from the production release of Oracle9i JDeveloper (9.0.4) to Oracle JDeveloper 10g. When you open Oracle JDeveloper 10g for the first time, you are prompted to migrate your user settings from the previous version. By default, all settings are marked for migration. You should 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 Oracle9i JDeveloper (9.0.4) or later.

6.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 6.3, "Migrating User Settings from Previous Releases", then migrate those connections before proceeding. In Oracle JDeveloper 10g, 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 Oracle9i JDeveloper (9.0.4).

  3. Allow JDeveloper to migrate the project.

    You should migrate a workspace that was created in Oracle9i JDeveloper (9.0.4) or a project that was created in Oracle9i JDeveloper (9.0.4) that you are now adding to a workspace in Oracle JDeveloper 10g. If you start Oracle JDeveloper 10g and open an OracleBI Beans workspace from Oracle9i 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 JDeveloper 10g 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.

    You should 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 6.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. If the application contains a presentation and if you use the thin QueryBuilder to edit that presentation, then you might notice that the Start With page has no measures selected. To resolve 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.

    3. Redeploy the application from the design-time Catalog to the runtime Catalog.

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

6.4.1 Manual Migration Steps for OracleBI Beans JSP Applications

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

6.4.1.1 Updating the Namespace

Edit the namespace in the initial line of code in each page. Append "/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" %>

6.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="http://java.sun.com/jstl/core" 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.

6.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>

6.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 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;

6.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.

6.4.1.6 Updating the members Attribute of the DimensionMemberList JSP Tag

The format for the members attribute of the DimensionMemberList tag has changed. The old format was member1;member2;member3. For example:

members="WORLD;AMERICA;EUROPE"

The new format is: level1::member1;level2::member2;level3::member3. For example:

members="L1::WORLD;L2::AMERICA;L2::EUROPE"

To update the format for this attribute, complete these steps:

  1. Edit the define tag for the DimensionMemberList, either by selecting it in the Structure window or by right-clicking the list in the Visual Editor and selecting Edit Define Tag.

  2. Select the members attribute.

  3. Display the advanced editor by selecting the Ellipsis button.

    You will see a message that states that there are invalid attribute values which will be updated to the new format.

  4. Choose OK. The members editor is displayed.

  5. Verify that the correct member attributes are displayed on the right side of the editor.

  6. Choose OK to complete the wizard.

    You will see the new member attribute format in the edit tag property inspector.

  7. Choose OK in the edit tag dialog.

6.4.2 Manual Migration Steps for OracleBI Beans 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.

6.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 Oracle9i JDeveloper (9.0.4), the images are stored in the public_html\cabo\images\<app_name> directory. In Oracle JDeveloper 10g, 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 JDeveloper 10g, as specified in Step 1.

6.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 take one of the following actions:

  • If you want to use the default error page that is supplied automatically by OracleBI Beans 10.1.2.2, then remove the previously existing error page before migrating the project to OracleBI Beans 10.1.2.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.

6.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.

6.4.2.4 Adding Code for Each dialogLinkDef Element

In Oracle JDeveloper 10g, 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 Oracle9i JDeveloper (9.0.4), the code looks like this:

<button onClick="${bibeans:data().bisession1.dlgLnk1}"/>

In Oracle JDeveloper 10g, the code looks like this:

<button onClick="${bibeans:data().bisession1.dlgLnk1_data.showDialog}"/>

6.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;

6.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. You should 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.

6.4.2.7 Updating the members Attribute of the DimensionMemberList UIX Tag

The format for the members attribute of the DimensionMemberList tag has changed. The old format was member1;member2;member3. For example:

members="WORLD;AMERICA;EUROPE"

The new format is: level1::member1;level2::member2;level3::member3. For example:

members="L1::WORLD;L2::AMERICA;L2::EUROPE"

To update the format for this attribute, complete these steps:

  1. Edit the define tag for the DimensionMemberList, either by selecting it in the Structure window or by right-clicking the list in the Visual Editor and selecting Edit Define Tag.

  2. Select the members attribute.

  3. Display the advanced editor by selecting the Ellipsis button.

    You will see a message that states that there are invalid attribute values which will be updated to the new format.

  4. Choose OK. The members editor is displayed.

  5. Verify that the correct member attributes are displayed on the right side of the editor.

  6. Choose OK to complete the wizard.

    You will see the new member attribute format in the edit tag property inspector.

  7. Choose OK in the edit tag dialog.

6.4.3 Manual Migration Steps for OracleBI Beans Java-Client Class Applications

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

6.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);

6.4.4 Manual Migration Steps for OracleBI Beans 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:

6.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 Oracle9i JDeveloper (9.0.4) and Oracle JDeveloper 10g. 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.

6.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 JDeveloper 10g. For example, see the code that affects the ViewToolbar and modify your application code accordingly. The ViewToolbar is not backward compatible.

6.5 Post-Migration Task for the OracleBI Beans Catalog (Optional)

After migrating the Catalog, you might want to perform a post-migration task to improve performance.

6.5.1 Conditions when Catalog Post-Migration is Beneficial

If all of the following conditions are present, then consider performing the optional post-migration task:

  • Use of an application that was migrated to OracleBI Beans 10.1.2.2 from OracleBI Beans 9.0.3 or OracleBI Beans 10g (9.0.4).

  • Use of a migrated OracleBI Beans Catalog that is running on Oracle Database 10g.

  • Detection of the following warning message in the standard ErrorHandler log while running the application:

    BIB-9549: The query has had missing level information inserted. You may wish to resave this query and its associated calculations and saved selections. (This message is followed by a list of the objects that had missing level information.)

Note: The Catalog post-migration task might also be beneficial to an OracleBI Beans 10.1.2.2 application that was previously migrated from OracleBI Beans 10g (9.0.4).

6.5.2 Reason for Message BIB-9549

Starting with the OracleBI Beans 10.1.2 release, hierarchy and level information are stored for each dimension member reference within each query and its associated calculations and saved selections in the Catalog. Whenever an application requests the loading of an object that does not have this information stored in the Catalog, the query must search for the required information before it can complete the load operation. Message BIB-9549 indicates that the load operation was delayed while the query searched for missing information.

6.5.3 Post-Migration Task

To avoid a delay each time that an object with missing information is loaded, you can perform a one-time operation of loading and resaving each object in the Catalog using OracleBI Beans 10.1.2.2.

Complete the following steps to load and resave objects:

  1. In Oracle JDeveloper 10g, under Local Catalog, double-click each object. This action opens the object.

  2. Resave each object.

  3. Copy each object to the remote Catalog.

7 Release Notes

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

7.1 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.

7.2 executecommand Method of Connection Object

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.

7.3 Family Step Followed by KEEP on Asymmetric Saved Selection

If you have a Family step that is followed by a KEEP action on an asymmetric saved selection, then you might see duplicate results when connecting to an Oracle9i (Release 2) database, version 9.2.0.6. This issue has no workaround.

7.4 Presentations

The following issues exist for presentations in OracleBI Beans:

7.4.1 Issue with Graphs with Circular Components

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 setting the graph's graphicAntialiasing property to True.

7.4.2 Issue with Start Align Button

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.

7.5 HTML-Client Applications

The following issues exist for HTML-client applications in OracleBI Beans:

7.5.1 Custom Text for Tooltips in Thin Graphs

In HTML-client applications, an application developer can allow end users to enter custom text for tooltips in thin graphs. Developers must 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.

7.5.2 Popup Windows and Third-Party Toolbar or Popup Blockers

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 an LOVContainer popup.

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

7.5.3 Issue with Partial Page Rendering

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.

7.5.4 Circular Reference in the FolderList Tag

The targetFolderListIds attribute of the BI Beans FolderList JSP tag allows a developer to specify the identifier of another FolderList tag as a target whose contents will be updated when a folder is selected. The FolderList tag does not automatically detect when a developer incorrectly specifies targets and creates a circular reference. 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"/>

When the page is run, the following infinite loop results:

FolderList A updates FolderList B
FolderList B updates FolderList C
FolderList C updates FolderList A

The FolderList tag does not detect this circular reference before the page is run.

7.6 Issues with Turkish Regional Settings

Because of Sun JRE 1.4 bug 4688797, you might encounter issues when connecting to a database schema while your computer has Turkish regional settings. You will encounter the issue when you attempt to connect to a database schema with a user name that contains certain letters, such as the letter 'I' or 'i', for example, in "bibdemo". See the Sun JRE bug for information on the letters that are affected.

To work around this issue, either do not use Turkish regional settings or use a user name that does not contain the affected letters.

7.7 Accessibility Limitations for OracleBI Beans

The following accessibility limitations exist 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.

7.8 Known Issues with Oracle OLAP Option

This section describes some of the known issues with the Oracle OLAP option. These issues affect all products that access OLAP data, including OracleBI Beans.

  • At times, database resources are not properly released in the Oracle9i (Release 2) OLAP option. This may result in excessive memory consumption. To release the resources, close OracleBI Beans.

  • There are potential performance issues running against analytic workspaces in Oracle OLAP 10g Release 1 version 10.1.0.4. To work around these issues, always check OracleMetalink for the appropriate Oracle OLAP patches at the following location:

    http://metalink.oracle.com

8 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. Accessibility 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 more information, visit the Oracle Accessibility Program Web site at

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

Accessibility of Code Examples in Documentation

Screen readers 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, some screen readers 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.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.


Oracle Business Intelligence Beans Installation Guide and Release Notes, 10g Release 2 (10.1.2.2) for Microsoft Windows and Solaris Operating System

Part No. B16033-02

Copyright © 2006 Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.