Skip Headers

Oracle9iAS Personalization Release Notes
Release 9.0.2 for MS Windows

Part Number A97391-01
Go To Documentation Library
Home

Oracle9iAS Personalization

Release Notes

Release 2 (v9.0.2) for MS Windows

May 2002

Part No. A97391-01

These release notes describe Oracle9iAS Personalization, a Business Intelligence option to the Oracle9i Application Server (Oracle9iAS).

These notes present late-breaking information about the product -- information not included in the Oracle9iAS documentation library on the CD-ROM or in the online documentation.

This is the second release of the product, but the first release to run on MS Windows.

This document is organized as follows:

Supported Windows Platforms

The following Windows platforms are supported:

Where to Find More Information

The documentation set for Oracle9iAS Personalization at the current release consists of the following:

Related Manuals

Oracle9iAS Personalization documentation is a component of the Oracle9i Application Server Documentation Library. See the following manuals:

Requirements

This section specifies the requirements for accessing the OP documentation, the OP Administrative UI, and the REAPI Demo.

Requirements for Accessing Documentation

Documentation is provided in PDF and HTML formats.

To view the PDF files, you will need

To view the HTML files, you will need

Accessing OP Admin UI and REAPI Demo

To access the OP Administrative UI and the REAPI Demo, you will need

Online Help

The Oracle9iAS Personalization Administrative UI includes online help, available by clicking the Help button in the upper right corner of each page of the Administrative UI.

For System Administrators

For technical support services, contact Customer Support at

   http://www.oracle.com/support/

Customer Database

Oracle9i Personalization requires a customer database in addition to the database included with Oracle9iAS. The customer database must be Oracle9i release 1.

Restart Required after OP Configuration

Before you can log in to the Administrative UI, you must restart OC4J_BI_FORMS after you run the Oracle9iAS Personalization Configuration Wizard. If you do not restart, the changes specified in the Wizard do not take effect.

Follow these steps to restart OC4J_BI_FORMS:

  1. Start Enterprise Manager by opening http://<your_system>:1810, where <your_system> is the name of your system.

  2. In the Application Server list, click on the server where OP is installed.

  3. Select OC4J_BI_FORMS by clicking the appropriate radio button.

  4. Click the Restart button.

This applies to all platforms.

Performance and Data Sizing

The table below shows the performance results on three datasets. The build time is linear in the number of customers and quadratic in the average profile size. We obtained the results shown here on a Sun Enterprise 450 (4 x UltraSPARC-II 400MHz) with 4096 megabytes of memory. Based on these numbers, it is possible to estimate the build time for any arbitrary dataset; see the subsection on Data Sizing, below. Definitions of the column headings follow the table.

Dataset # of Cust # of Items Avg. Profile Size Avg. Rating Profile Avg. Purch. Profile Avg. Nav. Profile Build Time # of Rules Agg. Model # of Rules Cross-Sell Model

1

1000

50K

  50

  8

17

25

1 min

    9152

  155

2

5000

50K

  50

  8

27

36

3 min

166588

    37

3

1000

50K

100

16

34

50

5 min

313154

2997

The column headings have the following meanings:

MOR Temp Space

Use the following formula to calculate a rough estimate for the number of bytes of MOR temp space required:

(54 * P2 * C)/2

where P is the average profile size and C is the number of customers. Each item pair generated during a build takes 54 bytes, which is the space needed to store a record with two item columns and a count column. For the model build to run, the available temp space should be more than the estimated temp space requirement for the P and C values of the dataset.

Bugs and Limitations

This section describes known bugs and limitations in Oracle9iAS Personalization release 9.0.2 as well as corrections to the documentation.

Correct Name of Product: The correct name of the product is "Oracle9iAS Personalization." In some instances the product may be incorrectly referred to as "Oracle9i Personalization."

Restrictions on Passwords: There are two restrictions on passwords:

Sorting by ID and Sorting by Type Not Enabled: For both sessionful and sessionless calls, for recommendation content, sorting by ID and sorting by Type are not enabled, whether "Ascend" or "Descend" is selected.

Advanced Button Brings Up "404 File Not Found" Message: This can happen with some versions of some browsers if user clicks Advanced button (at the bottom of the Log page) to bring up Message Viewer window if that window is still open (because user clicked Advanced button earlier and the window is still open).

Bad Proxy Object Remains: When bad input data is entered in the REProxyManager.createProxy() method, an invalid proxy object can be created and remain in the pool. This can cause errors in later operations if you use the proxy. Workaround: Create a new proxy object using a new name. The bad proxy is harmless as long as you don't use it.

Native Character Sets Limitation: OP is certified against UTF8 only.

Edit Recommendation Engine Page and Message Viewer Logger Page Print Incompletely: The Edit Recommendation Engine page and the Message Viewer Logger Print Query Options page print only the header, footnote, and the password box.

Port Numbers Must Be Four or Fewer Digits: If you specify a port number for OP with 5 or more digits, you will not be able to create an MTR connection. The Administrative Utility does not allow you to enter 5 or more digits for the port number. This restriction applies to all platforms.

Use https to Invoke OP Administrative Utility: You must use "https" in the URL when you start the Oracle9iAS Personalization Administrative Utility. The correct URL is

   https://<mysystem>:<myport>/op/Admin/

where <mysystem> is the URL for the system where OP is installed, and <myport> is the port number that was configured for OP. The setupinfo.txt file located in the %ORACLE_HOME%\Apache\Apache directory contains a list of the configured ports.

Flat Taxonomies Are Not Supported by Oracle9iAS Personalization: Oracle9iAS Personalization does not support a flat taxonomy, that is, a taxonomy where all categories derive directly from the root and none of the categories have child categories. Workaround: For a workaround, change the flat taxonomy by creating a parent category for all existing categories. Some restrictions may apply.

Default Mail Server Cannot Be Changed: You cannot change the default mail server location for email notifications in Oracle9iAS Personalization. This restriction applies to all UNIX platforms. Restart Required after OP Configuration: You must restart OC4J_BI_FORMS after you run the Oracle9iAS Personalization Configuration Wizard. If you do not restart, the changes specified in the Wizard do not take effect.

REAPI Demo Bugs

REAPI Demo: Invalid JDBC URL Is Not Detected: REAPI Demo does not throw an exception when a bogus value is entered for JDBC URL. REAPI Demo: Session ID Not Listed in Close Session Message: If, for example, you create a customer session with ID 12 and then close this session, the following message is displayed: "REAPI session of the user null closed successfully," i.e., the user ID information is omitted.

OP REAPI Demo User ID and Application Session ID Must Not Be the Same: For the Oracle9iAS Personalization REAPI Demo, the user ID and the application session ID must not be the same. If their values are equal, OP REAPI Demo may fail.

Documentation Corrections

In the Oracle9iAS Administrator's Guide, chapter 7, page 7-2, step 4 should be followed by a new step 5, as follows:

5. Run insertMTRSeedRecords.sql

and subsequent steps should be renumbered accordingly.

This correction has been made in the revised Oracle9iAS Administrator's Guide.

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

Oracle is a registered trademark, and Oracle9i is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.

Copyright © 2002 Oracle Corporation.

All Rights Reserved.


Oracle
Copyright © 20002, 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home