Crystal Reports

BusinessObjects XI Release 2
Release Notes
Windows
Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.
Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.
Copyright Copyright © 2005 Business Objects. All rights reserved.
Third-party Business Objects products in this release may contain redistributions of software licensed
contributors from third-party contributors. Some of these individual components may also be available
under alternative licenses. A partial listing of third-party contributors that have requested or
permitted acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
Contents
Chapter 1 Contents 3
Chapter 2 BusinessObjects XI Release 2 Release Notes 9

About these notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
What is BusinessObjects XI Release 2? . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Third-party contributors and applications . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 3 BusinessObjects Enterprise 11

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Upgrading and migrating issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Web and Windows applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Central Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
LiveOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Scheduling issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Developer issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Browser support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Java InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
RAS Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Viewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Application server issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Web server issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Server management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Page Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
International issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
BusinessObjects XI Release 2 Windows Release Notes 3

Contents
Chapter 4 Crystal Reports 27

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Report creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Java Reporting Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Developer issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Java Reporting Component (JRC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Crystal Reports for Visual Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 5 Desktop Intelligence 31

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Drill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Report formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Saving Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Break . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Slice and Dice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Manage Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Publication scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
International issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Saving documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Desktop Intelligence in 3-tier mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 6 Developer Library 39

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Designer SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Desktop Intelligence SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Document Viewer samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Migration sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Report Engine SDK samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4 BusinessObjects XI Release 2 Windows Release Notes

Contents
Java SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
RAS SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
JSP tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Web Services portal sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Crystal Reports developer samples . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 7 Import Wizard 45

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Universes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 8 Intelligent Question 51

Exporting to Web Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 9 OLAP Intelligence 53

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Essbase support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Application behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Data source connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
General issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Chapter 10 Performance Management 61

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Swedish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Contents
International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Sybase ASE ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Upgrading and migrating issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Interactive Metric Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Map analytic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Pareto chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Dashboard Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Performance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
My Goals page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Predictive Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Process Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2-tier products: Set Architect and Set Analyzer . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 11 Portal Integration Kit 73

SharePoint web parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Security and login issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Viewing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Firefox browser issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
JSR168 portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Viewing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 12 Semantic Layer 77

Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Business View Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Contents
Chapter 13 Report Conversion Tool 79

Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuration Management Console (CMC) . . . . . . . . . . . . . . . . . . . . . . . 82
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 14 Web Intelligence 83

Formula language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Referencing data outside a section . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
ReportFilter() function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
RunningSum() function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
International issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Cell formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Change source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
International issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Drill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Document linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Data providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Custom sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Java Report Panel and HTML Query panel . . . . . . . . . . . . . . . . . . . . . . . . 88

Contents

Release Notes
chapter
1 BusinessObjects XI Release 2 Release Notes
About these notes
About these notes

The notes contained in this document cover important information about this
product release, including: installation notes, details regarding known issues
with this release, and important information for existing customers.
Please read the entire document before installing your Business Objects
software. After the release of this document, any further issues you need to
know about will be added to these release notes in the online version
available at:
http://support.businessobjects.com/documentation/
Please be sure to consult the release notes online as well as this document to
make sure you have the most up-to-date information.
What is BusinessObjects XI Release 2?

BusinessObjects XI Release 2 brings together features from across the
Business Objects product line the meet the diverse needs of users, from
presentation-quality reporting to in-depth analysis.
Third-party contributors and applications

For acknowledgements of third-party contributors and applications, in addition
to related license information, please see http://www.businessobjects.com/
thirdparty.

BusinessObjects Enterprise
chapter
2 BusinessObjects Enterprise
Installation
Installation
• For a complete list of system requirements and supported platforms, see
the platforms.txt file included with your product distribution. For
complete installation instructions, see the installation guide
(install.pdf).
• Disable all antivirus software before installing BusinessObjects
Enterprise components. Enable your antivirus software after the
installation.
• Due to third-party applications (such as JDK, JRE, and Tomcat) that do
not support directories with non-ASCII characters, BusinessObjects
Enterprise XI R2 does not support installation to a directory that contains
non-ASCII characters.
• If BusinessObjects Enterprise XI is uninstalled and then re-installed, the
tables from the previous MySQL installation are used as the CMS
repository.
• Users with Non-ASCII usernames will fail to log on to BusinessObjects
Enterprise XI R2 using Java Windows AD authentication. This is a
limitation of the Java API.
Non-ASCII usernames are not supported by Kerberos. This is a known
Kerberos limitation. The Kerberos V protocol is not internationalized, and
currently does not provide a means of specifying the character set to be
used.
• During a custom installation, the Web Component Adapter (WCA)
screen may appear even though the option to install Tomcat has already
been selected.
• If you use Microsoft SharePoint and add a report in .NET InfoView, an
error message appears.
Workaround: Do not deploy the .NET WCA to the “Microsoft SharePoint
Administration” IIS website, which is part of the Microsoft FrontPage
Server Extensions.
• BusinessObjects Enterprise installs MySQL 4.1.9 and configures it to
start by default on port 3306. If you have another version of MySQL
installed which is already running on this default port number, the version
of MySQL that BusinessObjects Enterprise installs will not start.
Workaround: Before installing BusinessObjects Enterprise, check
whether MySQL is installed on the machine and if so, what port it is
configured to start on. If it is configured to start on port 3306, specify a
different port number for MySQL when installing BusinessObjects
Enterprise.

Installation 2
• For a UNIX installation, if you are installing MySQL server with
BusinessObjects Enterprise, then you cannot use the mysql command to
access the local MySQL server. You must source env.sh before running
MySQL clients.
• The outcome of the following workflow is by design:
1. Install BusinessObjects Enterprise XI Release 2 with performance
management on machine A.
2. Re-deploy the Desktop.war on machine B.
3. Access the application from machine B.
Outcome: You cannot modify the system field (CMS name and port) from
the logon page.
• When installing BusinessObjects Enterprise XI Release 2 on a Windows
XP machine, the option “Perform Server Installation” is the default option
on the Select Client or Server Installation step of the installation wizard.
To install Desktop Intelligencd or Designer you need to select Perform
Client Installation.
• Uninstalling BusinessObjects XI Release 2 removes the MySQL 4.13a
service but leaves all the MySQL files, including the CMS data, in the
local machine. However, it is possible to start MySQL after uninstallation
of BusinessObjects using console mode by carrying out these steps:
1. Remove all innoDB files (all of ibdata*, <localhost_name>.pid,
<localhost_name>.err) or remove them from C:\Program
Files\Business Objects\MySQL\mysql-pro-4.1.13a-win32\data, if
they are present.
2. Copy MySQL configuration file C:\Program Files\Business
Objects\MySQL\mysql-pro-4.1.13a-win32\my-medium.ini (or your
choice of one of the other included my-*ini files) to your
%SYSTEMROOT% directory.
3. Rename the file %SYSTEMROOT%\my-medium.ini (or the copied-
over my-*ini file) to my.ini.
4. Edit %SYSTEMROOT%\my-ini as follows: under sections “[client]”
and “[mysqld]“, comment out the line starting with “socket” by adding
a “#” in front of the line.
5. Start up the Standalone Console MySQL application by running this
command in the bin directory of MySQL as follows:
C:\Program Files\Business Objects\MySQL\mysql-pro-4.1.13a-
win32\bin>mysqld --console

Installation
6. You are ready to run MySQL commands. For example, to connect to

MySQL and BOE115 database, run this command in a new console
window:
C:\Program Files\Business Objects\MySQL\mysql-pro-4.1.13a-
win32\bin>mysql -h <localhost_name> -P 3306 -u BusinessObjects -
p<password> -D BOE115
7. To confirm that your connection is successful, you see the users
“root” and “BusinessObjects” displayed in the console after typing the
mysql command below:
mysql> select user, host, password from mysql.user
> ;
• Autodetection of CrystalReports_11_5_2005.msm is not supported on

Visual Studio 2005.
Workaround: To enable autodetection of
CrystalReports_11_5_2005.msm in Visual Studio 2005, rename the
CrystalReports115List.xml file to CrystalReports115Listxml123, or
copy it to another location, or delete it. If you simply rename this XML file,
autodetection does not work.
• When performing a RAS XI Standalone to RAS XI Release 2 upgrade,
the last screen of the installation wizard gives incorrect information on
how to complete the upgrade.
Workaround: When upgrading from RAS XI Standalone to RAS XI
Release 2, ignore the steps described on the last screen of the
installation wizard. In this situation there is no need to do any database
migration. After installation, you only need to manually start the CMS.
• If .NET Framework 2.0 Beta 2 is installed before installing
BusinessObjects XI Release 2, it is not possible to save OLAPI reports in
.NET InfoView.
Workaround: Install BusinessObjects XI Release 2 before installing
.NET Framework 2.0 Beta 2.
• When the FRS is stopped, the –tempDir directory specified in the
command line is deleted. To avoid having the FRS remove a system-
critical element, choose a unique temporary directory such as –tempDir
c:\FRStempDirectory.

Connection Server 2
Connection Server
A Web Intelligence query can not be run when Connection Server is operating
in server mode.
Upgrading and migrating issues

Importing data from BusinessObjects Enterprise 6.x to
BusinessObjects Enterprise XI Release 2
• When upgrading from BusinessObjects Enterprise 6.5, all personal
content information for a third-party user cannot be imported to
BusinessObjects Enterprise XI release 2 unless the user has an explicit
user object in the repository. Personal content information includes
personal documents, categories, and Inbox documents.
Workaround: Create explicit user objects in BusinessObjects Enterprise
6.5 for all third party users whose personal content you want to import to
BusinessObjects Enterprise XI release 2, and then start the import
process.
Importing data from Crystal Enterprise to

BusinessObjects Enterprise XI Release 2
• If you use Windows AD authentication and you upgrade from Crystal
Enterprise 10 to BusinessObjects Enterprise XI Release 2, your Windows
AD users may not be mapped to the correct groups automatically. If you
encounter this problem, visit our customer support site for the appropriate
patch.
• When you upgrade from Crystal Enterprise, if your current deployment
uses multiple Job Servers, Page Servers, or other servers, note that only
one of each server is upgraded automatically.
• When you upgrade from Crystal Enterprise, note that the option to Install
mySQL should not be available. Upgrading from Crystal Enterprise to
BusinessObjects Enterprise XI r2 using a mySQL databse is not
supported.

• When you upgrade from Crystal Enterprise 10 Report Application Server

standalone to BusinessObjects Enterprise XI r2, note that the two
applications are so different that the installation program actually
uninstalls the original software and then performs a normal installation of
the new software.
Import Wizard
• When you choose to import inboxes, note that inboxes will be imported
only for the users that you are importing. The user is not automatically
selected for import when you select the user’s inbox for import.
• When you choose to import repository objects from BIAR, all repository
objects in the BIAR data source will be imported.
• In some cases, users who are trying to import “users and groups” or
“folders and objects” from the BIAR source file will not be able to do so.
This happens when one of the objects in the source file is corrupt. Please
note that the Import Wizard will not report an error if it encounters a
corrupt object and fails to retrieve it and others from the BIAR file.
• A timeout may occur when a large number of users and groups are being
imported to BusinessObjects Enterprise XI Release 2.
Workaround: To avoid a timeout, ensure that third-party authentication is
disabled. Disable third-party authentication after all of the objects have
been counted, but before Finish is clicked.
• When working with Dynamic Cascading Prompts (DCPs), users need to
pick "Import all repository objects" from the "Import repository objects
options". Selecting other options will result in broken DPCs after the
import.
• When a BusinessObjects 5x universe is imported, a restriction is created
for groups and a duplicate restriction is created for the user. The user
ends up having 2 identical restrictions. This is an error.
• Connections are not migrated correctly from the 5.x repository for
Informix Connect for IDS9.4.
Documentation
• The table on page 273 of the BusinessObjects 5.1.x to XI Release 2
Migration Guide and on page 303 of the BusinessObjects 6.x to XI
Release 2 Migration Guide incorrectly refers to calculation issues related
to BusinessObjects from versions 5.1.6 through 5.1.9 in the second
row. This row in fact refers to calculation issues related to
BusinessObjects 6.0.

Web and Windows applications 2
• The sections The UniverseName() function, Unicode fonts and
Decimal precision in the BusinessObjects 5.1.x to XI Release 2
Migration Guide and the BusinessObjects 6.x to XI Release 2 Migration
Guide refer to changes introduced in Desktop Intelligence. This is not
specified at this point in the document. These sections should be
preceded by a heading, Desktop Intelligence changes.
Web and Windows applications

Central Management Console
• If you experience difficulty deploying the webcompadapter.war on
Weblogic, it may be because Weblogic cannot load the deployment
descriptors.
Workaround: If the Weblogic Builder tool is used, then the web.xml files
need to be changed before deployment. After saving the
webcompadapter.war file in the Weblogic Builder tool, the line in the
web.xml should be:
SOCKS URI convention. socks://<version
#>;[<username:password>@]<hostname:port&
gt;[&]
• When large files are published from the CMC in a supported format such
as txt or .exe, the following error message may appear:
"URL Error The Web server received an incorrect or incomplete URL
from the browser. Missing data”
This message should read:
“The CMC cannot publish supported files larger than 20 M.”
InfoView
• When you expand and collapse the Events or Server Groups options
when scheduling a document from InfoView, other previously set
options are lost.
• The error “Text-only printers are not supported. Please change your
printer” occurs when you schedule a Desktop Intelligence document
to be printed using a Custom Printer, and you supply the IP address
of the printer.

Web and Windows applications
• When you save a REP document that is viewed as HTML or PDF to

CSV format, the generated CSV file is UTF-8 compliant. The
document does not display properly in Microsoft Excel if it contains
accented letters or Japanese characters. The CSV document can be
opened and viewed with a Unicode (UTF-8) text processor. If you
want to open the document in Microsoft Excel, Business Objects
recommends that you save it as Excel from InfoView.
• In Interactive Editing mode, the connection with the document is lost
periodically, and the InfoView home page is displayed in its place.
• When a document is linked to open in the same window, then the
child document replaces the parent document, rather than being a
sub-part of it. This means it is not possible to navigate to the parent
document.
• To enable Java InfoView on Sun Java Application Server, the default
Java2 security setting, which can be found on <Sun Java Application
Server InstallDir>\domains\<domain name>\config\server.policy,
should be updated as shown in the example:
grant {
permission java.lang.RuntimePermission “loadLibrary.*”;
permission java.lang.RuntimePermission “queuePrintJob”;
permission java.net.SocketPermission
“*”,”connect,listen,accept”;
permission java.io.FilePermission “<<ALL
FILES>>”,”read,write,execute,delete”;
// workaround for pointbase bug 4864405
permission java.io.FilePermission
“${com.sun.aas.instanceRoot}${/}lib${/}databases${/}-
”, “delete”;
permission java.io.FilePermission “{java.io.tmpdir}${/}-
”, “delete
permission java.util.PropertyPermission “*”, “read,write”;
permission java.lang.RuntimePermission
“modifyThreadGroup”;
• Deploying desktop.war on SAP Web Application Server 6.40 (WinSQL)
on the default setting may give you an error. It has been confirmed by
SAP that this is an SAP Web Application Server issue. Please see SAP
Note #892789. This note explains that an upcoming SP from SAP will fix
the issue. However, at the time this text is written, this SAP Note has not
been released yet. If you cannot access SAP Note #892789, here is a
workaround, only for SAP Web Application Server 6.40 (WinSQL)
running with Microsoft SQL Server 2000 SP3. If you are using the SQL
Server 2000 SP3, do the following:

Scheduling issues 2
1. In SQL Enterprise Manger, add "-g1024" to the SQL Server's startup
parameters list.
2. In SQL Qeury Analyzer, run "exec sp_configure 'network packet size
(B)', '8196'; reconfigure with override".
3. Restart the SQL server and make sure the changes were taken into
account.
4. Deploy desktop.war.
• In InfoView, you can send a document to email by first selecting a
document and then using the "Send" button in the main toolbar and
selecting "To Email" from the list. If you clear the "Use Job Server's
defaults" option, you can then specify the settings with placeholders. You
can add the placeholder "Viewer Hyperlink" to the message textbox in
.NET InfoView. In Java InfoView, the "Viewer Hyperlink" placeholder is
missing. The workaround is to manually type %SI_VIEWER_URL% in
the textbox. The viewer hyperlink placeholder will be replaced by a URL
link for document viewing.
• In InfoView, when scheduling an object to a specific destination, the user
can then specify the settings with placeholders. The placeholder "Email"
and "User Full Name" can be added to the message textbox in Java
InfoView. In .NET InfoView, the "Email" and "User Full Name"
placeholders are missing from the list. The workaround is to manually
type %SI_EMAIL_ADDRESS% and %SI_USERFULLNAME% in the
textbox respectively.
LiveOffice
• In Microsoft Word 2003, when part of a report view is copied and pasted
to another area of a document and the view is refreshed, the copied
section of the report view disappears.
• In Microsoft Excel, when you right-click the legend of a chart, the Drill
option is active. It should not be active because you cannot drill-down on
the legend of a chart.
Scheduling issues
• You cannot re-schedule Web Intelligence documents to Excel or PDF
formats. Depending on your precache settings, these options may
incorrectly appear.
• Scheduling a Publication will fail when done by a third party who lacks
the following rights:

Documentation
• "Add objects to folder"

This right allows users to create the content objects under the
instance.
• "Modify the rights users have to objects”
This allows users to decide which recipients should be able to see
what content objects.
In order to allow another user to schedule a Publication to the "Default"
destination, the publication owner must grant these rights in addition to
the "Schedule" role.
Documentation
• The BusinessObjects Enterprise XI Administrator’s Guide description for
the command-line option “-cleanup” reads "Specify the frequency (in
minutes) with which the server cleans up listener proxies"; however, the
Event Server uses minutes/2. For example, “-cleanup 10” will run the
cleanup thread in the event server every 5 minutes.
• For information on how to install the Crystal Reports Offline Viewer,
please see chapter eight of the InfoView User’s Guide.
• The BusinessObjects Enterprise XI Administrator’s Guide description for
the command-line option “-threads” reads "Use a thread pool of the
specified size. The default is one thread per request." The actual
behaviour of the “-threads” parameter depends on the size of the pool of
worker threads the CMS initializes and draws workers from. The
maximum is 150, and the minimum is 12. The default is 50 if the
parameter is not specified.
Security
• When Java Windows Active Directory (AD) authentication is used, users
with non-ASCII user names are unable to log in. This is a limitation of the
Java API.

Developer issues 2
Developer issues
Browser support
Double-byte characters are not supported by Firefox and Netscape internet
browsers. Reports that contain double-byte characters malfunction in those
browsers.
Java InfoView
• If you're running Sun Application Server 8 upgrade 1, you cannot create,
view, or modify a Dashboard from Infoview.
Workaround:
To use InfoView, the following actions should be applied to avoid possible
XML/XSLT processor conflicts:
1. Set the class-loader delegation policy in the WEB-INF/sun-web.xml
file to "true" as shown in the following example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems,
Inc.//DTD Application Server 8.0 Servlet 2.4//EN"
"http://www.sun.com/software/appserver/dtds/sun-web-
app_2_4-0.dtd">
<sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
<context-root>businessobjects/enterprise11/
desktoplaunch</context-root>
<class-loader delegate="true"/>
</sun-web-app>

Developer issues
2. Create a JSP script in the deployed application (or add the code to
an existing web application script) with the following content:
<%
System.setProperty("javax.xml.transform.TransformerFa
ctory",
"org.apache.xalan.processor.TransformerFactoryImpl");
%>
3. Before accessing Infoview, execute the JSP script from step 2. This
will set the correct XML transformer to work with Business Objects
applications.
• Users can not log on to the BusinessObjects Enterprise Java Infoview
when using the server IP address in the system field. The workaround to
achieve a successful logon is to have the client application log on with the
hostname of the Central Management Server (CMS).
• InfoView does not deploy correctly if system properties are not set
appropriately.
Workaround: Set the following propery in a JSP file, or globally in the
SAP application server:
System.setProperty("org.xml.sax.driver",
"org.apache.xerces.parsers.SAXParser");
• To enable printing from a DHTML viewer using ActiveX print control,
ensure that gzip compression is turned off for the following MIME types:
• - application/x-epf
• - application/x-ack
• - application/x-eor
• - application/x-etf
• - application/x-emf
• You may encounter problems when viewing double-byte characters if you
are using an Oracle 10G server or an SAP application server.
Workaround: Before deploying the desktop.war and jsfadmin.war files,
modify the corresponding web.xml so that the <filter> and <filter-
mapping> elements are uncommented.
RAS Java
• Some paper sizes and paper sources exposed in the SDK are not
supported by JDK 1.4. If users select the unsupported print options, an
error message appears.

Developer issues 2
Print options are handled by
PrintOutputController.printReport(PrintReportOptions), which let users
specify different paper sizes and paper sources.
Supported paper sizes are as follows:
useDefault, paperLetter, paperTabloid, paperLedger, paperLegal,
paperExecutive, paperA3, paperA4, paperA5, paperB4, paperB5,
paperFolio, paperQuarto, paperEnvelope9, paperEnvelope10,
paperEnvelope11, paperEnvelope12, paperEnvelope14,
paperCsheet, paperDsheet, paperEsheet, paperEnvelopeItaly,
paperEnvelopeMonarch, and paperEnvelopePersonal.
Supported paper sources are as follows:
auto, upper, lower, middle, manual, envelope, and largeCapacity.
Any sizes and sources not listed here, and any added in future, will cause
an error message to appear.
• The DatabaseController.ReplaceConnection method does not take a
DBOptions class; instead, its fourth argument is an integer.
The DBOptions now have four static members, which contain these
values:
• ._useDefault = 0
• ._doNotVerifyDB = 1
• ._mapFieldByRowsetPosition = 2
• ._ignoreCurrentTableQualifiers = 4
The following is an example of how use
DatabaseController.ReplaceConnection:
databaseController.replaceConnection(oldConnection,
newConnection, parameters, DBOptions._useDefault);
If you anticipate that DatabaseSchema will change after
replaceConnection is run, call verifyDatabase() to synchronize the client
and server.
Viewers
• The viewers fail to support reports that contain formula fields or database
fields whose names contain either of these brackets: {}.
• Use the new database logon format when using the RAS server. The old
format is as follows:
user=value
password=value

Application server issues
The new format is as follows:

user-dbservername.dabasename=value
password-dbservername.databasename=value
The new format for database logon lets the Viewer display the report
without prompting the user again for database logon information.
• If you use an Oracle 10g application server and you receive an
“OutputStream already retrieved” error, change the viewer.usejspwriter
context parameter to “true” in the web.xml of the desktop.war file.
• If you use an Oracle 10g application server and you receive an
"OutputStrream already retrieved" error, change the viewer.userjspwriter
setting to true in the desktop.war file. If this does not resolve the issue,
modify the error.jsp file so that it doesn't use JSTL tags.
• Use the new database logon format when using the RAS server. The old
format is as follows:
user=value
password=value
The new format is as follows:
user-dbservername.databasename=value
password-dbservername.databasename=value
The new format for database logon lets the Viewer display the report
without prompting the user again for database logon information.
Application server issues

• After InfoView is deployed on SAP, the Infoview Encyclopedia may not
work.
Workaround: When InfoView is deployed on SAP, the context parameter
in the web.xml called "encyclopedia.disable.gzip" needs to be set to
"true". This will disable the gzip action of Java Encylopedia and allow
Infoview to operate.
Web server issues

To improve the stability and performance of Microsoft’s IIS (Internet
Information Server), modify the machine.config file in the following directory:
<WindowsDirectory>\Microsoft.NET\Framework\
<InstalledFrameworkVersion\>CONFIG\...

Server management 2
Server management
Page Server
When a report which has a number of records greater than the processing
limit specified in the CMC is viewed via Page Server, the first page of the
report generates successfully without returning an error.
Use the values shown in the table.
Configuration setting Default value (.NET Recommended

Framework 1.1) value
maxconnection 2 12 * N
maxIoThreads 20 100
maxWorkerThreads 20 100
minFreeThreads 8 88 * N
minLocalRequestFreeThreads 4 76 * N
Some of the recommendations use a formula that works with the number of
CPUs on a server. The number of CPUs in each formula is represented by the
variable N. To adjust configuration settings when you have hyperthreading
enabled, you must use the number of logical CPUs instead of the number of
physical CPUs. For example, if you have a four-processor server with
hyperthreading enabled, the value of N in a formula is 8 rather than 4.
International issues
• On the Solaris and AIX platforms, if you need to run the Central
Management Console (CMC) in Chinese, Japanese, or Korean, you must
use a Chinese, Japanese, or Korean locale on the J2EE application
server that hosts the Web Component Adapter (WCA). To set the locale,
set the environment variables LANG and LC_ALL before starting the
J2EE application server.
• If you have deployed WebSphere 5.1 or WebSphere 6.0, you may
encounter problems while viewing InfoView’s preferences page using
Asian locales.

Workaround: To enable UTF-8 support for WebSphere:

1. Edit <WebSphere>/AppServer/properties/encoding.properties so
that every line contains the following information: xx=UTF-8, and
then save.
2. Pass -Dclient.encoding.override=UTF-8 into the Java Virtual
Machine.

Crystal Reports
chapter
3 Crystal Reports
Installation
Installation
(install.pdf).
installation.
Data access
• A document containing a list of limitations for the latest version of the
native XML driver can be found on our Technical Support site.
Report creation
• To find a value for a selection or content locale, put the appropriate
special field (Selection Locale or Content Locale) in your report and view
the value from the report.
• Command objects that use a dynamic prompt, or a prompt that includes a
cascading list of values, will malfunction if added to the BusinessObjects
Enterprise Repository in this version. Such a command object will return
an error when you refresh the data of the report that you created from it.
• When you define an XML element for a string type, you can define it as
follows to remove padded spaces:
<xsd:simpleType name = "myString">
<xsd:restriction base = "xsd:string">
<xsd:maxLength value="255"/>
<xsd:whiteSpace value = "collapse"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="col1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="col1" type="myString" />
</xsd:sequence>
</xsd:complexType>

Crystal Reports
Java Reporting Component 3
• If a report uses two commands, one for the report (with parameters) and
a second for populating prompts (without parameters), you should use
two command objects: one with no parameters to populate the list of
values of prompts, and a second with no parameters to populate the
report.
Java Reporting Component

• For a report with saved data, changing a parameter value that is used in
the record selection will not cause the data to be refreshed.
Workaround: Do not use reports with saved data.
Documentation
• The option “Limit size of result set to” that is described in the Crystal
Reports Online Help is unavailable in this version.
• A new, undocumented function called
CountHierarchicalChildren(GroupingLevel) has been added to
this version. Use this function to suppress hierarchical group headers or
footers when no child levels exist.
CountHierarchicalChildren(GroupingLevel)
GroupingLevel is a function that determines the level of an existing
group.
The CountHierarchicalChildren(GroupingLevel) function returns
the number of direct child hierarchical groups for any given level of the
grouping hierarchy. Grandchild (and deeper) groups are excluded from
the count.
This number does not count the number of detail records in any group.
So, the output will be different from count({field}) when summarized
across a hierarchy. (The count({field}) function counts detail
records.)

3 Crystal Reports
Developer issues
Developer issues
JDBC Driver
• The LiquidData JDBC Driver may cause the following code to fail:
ResultSet rs;
ResultSetMetaData rsmd = rs.getMetaData();
int colType = rsmd.getColumnType(i);
Java Reporting Component (JRC)

• The JRC fails to support percentage summary reports that are created
with the Report Designer Component. To use percentage summary
reports with the JRC, resave them with Crystal Reports 9 or later.
• The JRC fails to support reports that contain relative paths to dynamic
images.
Crystal Reports for Visual Studio

• Reports that are based on a User Defined Type (UDT) table fail to load if
the first relational field in the UDT table is deleted.
• Reports that contains a command object and a dynamic parameter may
fail to load if the command object and the parameter form a circular
reference. (For example, the command object references a dynamic
parameter that references the command object.)
The workaround is to create a dynamic parameter to prompt for values
for the command object, and then create a second dynamic parameter to
read values from the command object.
• If you use the OpenDocument function to display a report that uses a
RAS server group, use interactive mode. If you are using the
OpenDocument function to display a report that uses a Page Server
group, use non-interactive mode.

Desktop Intelligence
chapter
4 Desktop Intelligence
General information
General information
• When installing Desktop Intelligence, all languages are installed with the
product. But at the first logon, Desktop Intelligence is launched in
English.
Workaround: Change the language manually as follows:
1. Click Options on the Tools menu.
2. In the dialog box that opens, go to the General tab and choose the
language from the list.
• If you change the language in Desktop Intelligence as described above, if
the document locale is not modified correspondingly the number formats
associated with the selected language are not taken into account. English
number formats are used instead.
Workaround: When changing the language, be sure to click the
Language button.
• In Desktop products (Desktop Intelligence and Designer), the list that
enables you to set the current language (Tools > Options > General tab)
always displays the language names in English.
• To start a new session in Offline mode, you must first connect to the CMS
with your login in Online mode. This action refreshes the .lsi file.
• To work in 3-tier mode, you must first install Desktop Intelligence on the
client machine, then log on to InfoView and download the .jre or .net file
by creating, modifying or editing a Desktop Intelligence document.
• When you apply a filter on a date object for a document where the user
interface locale (UIL) and the user format locale (UFL) do not match, the
display of the report is blank.
• Teradata stored procedures with OUT variables are not supported by
Business Objects as concerns data providers and the Connection Server.
• When you open a Desktop Intelligence document from the InfoView
portal, sections don't appear in the report map.
• When you schedule a Desktop Intelligence document and select the
Custom Printer option with IP Address as the input, scheduling fails.
• It is not possible to change the data source of a BusinessObjects 6.x
document from Desktop Intelligence.
• When an REP file is saved as HTML from Desktop Intelligence, breaks
with center across (horizontal) do not work.

General information 4
• When importing reports from the repository, reports that are not
associated with any category do no appear in the “uncategorized”
category.
• When you attempt to export a document while the document is not open,
and click to see HTML options for the document you have chosen, the
HTML Options dialog box does not appear.
• When defining a formula or variable with “InCurrentPage” as the context,
the corresponding calculations are not displayed in XLS, HTML, TXT or
RTF files after saving the report in these formats.
• Stored procedures with OUT parameters cannot be executed on IBM
DB2 UDB for Microsoft Windows NT or UNIX platforms.
Migration
• In a mixed deployment of BusinessObjects 6.x and BusinessObjects XI
Release 2, you cannot open a BusinessObjects 6.x document using
BusinessObjects 6.5 in 3-tier mode from within the InfoView 6.x portal.
Workaround: In this situation you can open a BusinessObjects 6.x
document using BusinessObjects in 3-tier mode only by launching
BusinessObjects in 3-tier mode from the Windows Start bar. In addition,
these conditions must be met:
• BusinessObjects 6.x must have been installed prior to
BusinessObjects XI Release 2.
• You must manually copy the .rkey file that points to your InfoView 6.x
repository to your locdata folder if this has not already been done.
• Use of Microsoft VBA (for example, a VBA application using the full client
SDK, or documents containing VBA procedures) is not supported when
Desktop Intelligence XI R2 is installed on a machine that already has
BusinessObjects 6.x installed.
Workaround: Be sure to uninstall BusinessObjects 6.x prior to installing
Desktop Intelligence XI R2.
Drill
• The arrow icon for the drop-down list on the Drill toolbar is not displayed
when a dimension name contains more than 255 characters.
• You cannot drill in a dimension placed in the body of a crosstable.
• You cannot drill down or drill by from the legend, although can drill up.
• When you perform certain actions in drill mode, the labels of the charts
may change orientation.

General information
Report formatting
• When you specify a format for a negative value in the Negative text box
on the Number tab of the Cell Format dialog box, you must include the
minus symbol (-) before the format. For example, to specify a negative
format with three decimal places, you should enter -0.000.
• With linked tables, if you select the Repeat block on every page option in
the Table Format dialog box, Business Objects recommends you apply
this option to all the tables. Otherwise the blocks may overlap.
• In reports, a block set to repeat on every page may attach to the header
of another block at the top of each subsequent page.
Workaround: When necessary, insert an empty cell between two tables
to prevent the repeating block from attaching to the header.
• When the display of a block or a cell exceeds 70% of the page layout, the
Repeat on every page option is not applied. This avoids having
overlapped blocks from the second page onwards.
Workaround: Do not use the Repeat on every page option when a block
or cell exceeds 70% of the page layout.
Saving Documents
• When you activate the Automatic Open After SaveAs option (in Tools >
Options > Save tab) and save a document as HTML, PDF, XLS, RTF or
TXT, the file is opened in the appropriate application.
• The number and format of cell borders are not kept when a document is
saved as HTML.
• Saving a document with a long file name as HTML may fail.
• When you launch Desktop Intelligence in the English version and save a
document with a long file name as HTML, an error message may appear
in French.
• When a report is saved as a PDF file, the Symbol font is not converted if
the font style is bold and/or italic.
• When defining a formula or a variable with "In CurrentPage" as the
context, the corresponding calculations won't be displayed in the XLS,
HTML, TXT, and RTF files when the report is saved in these formats.
• When a Desktop Intelligence report is saved in Microsoft Excel format,
column width and value display issues may occur:
• If a column is incorrectly sized in Desktop Intelligence, the column
width is reduced and the value displayed as ### in the Excel file.

General information 4
• If percentage values are set in Desktop Intelligence without the %
symbol, the % symbol is automatically added in the Excel file, but
without resizing the column.
• If you save a document containing a chart in Microsoft Excel format
(XLS), Excel will adjust the size of your chart for the space occupied by
the labels. The larger the labels, the more the chart may be minimized.
Workaround: Manually adjust the size of the labels and the chart in
Excel.
• When saving a document containing a chart in Microsoft Excel format
(XLS), the category axis title may not be cleaned in the Chart Options
dialog box.
Workaround: Clean it manually in Excel.
• When you define a new orientation of a chart in Desktop Intelligence and
save the document in Microsoft Excel format (XLS), the elevation or
rotation of the chart may be different in Excel.
• The position of the chart legend may not be preserved in a document
saved in Microsoft Excel format (XLS).
• Desktop Intelligence optimizes the representation of the chart.
Consequently, it may apply a different orientation of the axis label
according to the options in order to have a better rendering in Reporter.
When saving the document in Microsoft Excel format (XLS), the
orientation may be different in Excel because the options are applied
without being optimized.
• Due to a limitation of Microsoft Excel, Business Objects recommends that
you not save a document in Microsoft Excel format (XLS) if it contains a
3D chart with several groups of series, otherwise the chart won’t keep the
same display.
Workaround: Set all the measures in the same group of series in order
to have only one Y-axis or define several groups of series using 2D charts
before saving your document as Excel.
• Some hyperlinks may not be saved correctly in documents when you
save it as a Rich Text Format file (.RTF).
Printing
• Some printer drivers do not differentiate the colors used in graphics and
may print similar shades for different colors. To lessen the impact of this,
Desktop Intelligence creates differences in the color palette to print colors
or shades that are clearly distinguishable.

General information
• If you want to print several reports containing the Euro character at the
same time, you must use the same printer (and the same printer driver),
otherwise the Euro character will not be printed after the first report.
• The hyperlinks won’t be activated if you select the Print as
BusinessObjects 4.1 option in the Options dialog box (Tools > Options >
General tab).
Break
• The Center Value Across Break option has no effect on a long cell,
even if this option is activated in the Breaks dialog box.
Slice and Dice

• In the Slice and Dice window, clicking F1 on the keyboard does not
display the help file.
Workaround: Use the Help button to display the Help file associated with
the Slice and Dice window.
Manage Categories
• In the Add and Edit Categories dialog boxes (Export to Repository >
Categories > Manage > Add/Edit), clicking F1 on the keyboard does not
display the help files. There are no help files associated with these dialog
boxes.
Publication scheduling
• Publication instances scheduled to the Default destination fail if the Inbox
destination is disabled on the Desktop Intelligence job server.
Workaround: Enable the Inbox destination on the job server.
• Publication recipients do not receive their content when two conditions
are true:
• The publication is scheduled to Inbox using job server defaults.
• The Desktop intelligence job server has one or more recipients set
for the Inbox destination.
Under these circumstances all the content will go to the job server
recipients instead of the Publication recipients.
Workaround: To avoid this problem, either schedule using custom Inbox
settings, or do not set any Inbox recipients.

International issues 4
Saving documents
• The name of the Automatic Open After SaveAs option may be truncated
in some languages.
Desktop Intelligence in 3-tier mode

• On the client machine, when the language of Desktop Intelligence does
not match the current language of the Internet browser and InfoView,
Desktop Intelligence in 3-tier mode is launched in the language of
Desktop Intelligence.


Developer Library
chapter
5 Developer Library
General
General
• The Business Objects Developer Library is installed with
BusinessObjects Enterprise and can be accessed through the Start
Menu, navigating to the default install directory, or through the Business
Objects Developer Zone website.
Start Menu:
Start > Programs > BusinessObjects XI Release 2 > BusinessObjects
Enterprise > BusinessObjects Enterprise Developer Documentation
Default Install Directory:
C:\Program Files\Business Objects\BusinessObjects Enterprise
11.5\Developer_Help\en\default.htm
Website:
http://www.businessobjects.com/products/dev_zone/default.asp
Designer SDK
The "Type" property of the "Key" Object is read-only.
Desktop Intelligence SDK

• Desktop Intelligence can not be started using the C# SDK.

Developer Library
Document Viewer samples 5
• Certain application variables that were included with BusinessObjects 6.5
are not included with Desktop Intelligence in XI Release 2. Desktop
Intelligence also includes one new variable.
Availability Variable name

6.5 variables available in XI R2 BOLANGUAGE
BOSECURITYDOMAIN
BOUSER
BUSER_UPPER
6.5 variables not available in XI R2 COMPUTERNAME
CommonProgramFiles
HOMEDRIVE
HOMEPATH
ProgramFiles
SystemDrive
SystemRoot
USERDNSDOMAIN
USERDOMAIN
USERNAME
USERPROFILE
New variable in XI R2 DOCNAME
Document Viewer samples

Migration sample
• If a document stored in a public folder is associated to a personal
category, it appears in the list of favorites.
Report Engine SDK samples

• In the JSP/ASPX prompt customization samples, nested prompts are not
supported. This is a known limitation. The purpose of this sample is to
demonstrate how to customize prompts in the viewer component. See
Report Engine SDK tutorials to learn how to set prompts using this SDK.

5 Developer Library
Java SDK
Java SDK
• If you use AD Authentication with Kerberos, you cannot log on to
BusinessObjects Enterprise with a non-ASCII user name. Kerberos
supports only ASCII user names.
RAS SDK
ReplaceConnection suppresses all errors related to database connectivity.
JSP tutorials
• The XML report output for a document with multiple reports always
returns the first report.
• Desktop Intelligence returns an invalid Last Refresh Date
International
• Creating a Web Intelligence document returns a compilation error in the
Japanese version.
Web Services portal sample

• Drilling on multiple duplicate reports may trigger an error.
• When navigating between documents, draft mode is not maintained.
Crystal Reports developer samples
• Windows Start menu links for developer samples do not work in non-
English operating systems.

Developer Library
International issues 5
The English version of the developer samples can be accessed from the
following locations after Crystal Reports has been installed.
• Crystal Reports for .NET Samples:
C:\Program Files\Business Objects\Crystal Reports
11.5\Samples\en\CR.NET\CRdotNetStartup_en.htm
• RDC Developer Samples:
11.5\Samples\en\RDC\RDCStartup_en.htm
• Java Reporting Component Samples:
11.5\Samples\en\JRC\JRCStartup_en.htm

5 Developer Library

Import Wizard
chapter
6 Import Wizard
General
General
• When installing BusinessObjects Enterprise, we recommend running a
Server Installation in order for the Import Wizard to run correctly.
• Import Wizard does not test that the File Repository Server and Input
Server are running before starting to import objects.
Workaround: Make sure the File Repository Server and Input Server are
running before running the Import Wizard.
• Import Wizard does not test license validity before starting to import
objects.
Workaround: Make sure you have a valid license before running the
Import Wizard.
• The “Clear All” buttons on Universe and Document dialog boxes clear
even the greyed checkboxes.
• Selected afd cannot be unselected.
• The OLEDB connection cannot be set correctly in the Application
Foundation Repository dialog box.
Universes
• Large universe descriptions are not fully migrated and may become
truncated.
• Migrated UNV files have an incorrect cluster GUID.
• Unchecking Universe for Metrics is possible after selecting for import
“universes and connections that the selected WebIntelligence,
BusinessObjects and Application Foundation documents use directly, as
well as all the universes used for metric definition.”
• Import Wizard may display universe and document domains that don't
exist in Supervisor.
Documents
• When you migrate a REP document or publish a document from Desktop
Intelligence, and then refresh it in Infoview, the date and time in the
Status bar are not updated.
• From XI to XI R2, migrated Web Intelligence reports do not update
precaching properties to the new format.
• No warnings are displayed when orphaned documents are migrated.

Import Wizard
Performance Management 6
• Migrated REP files with a long name may be renamed with a suffixed
extension.
Web Intelligence 2.x to XI Release 2

• The default fonts appear different, especially in charts.
• HTML links may not function correctly.
• When you convert a WebIntelligence 2.x (.wqy) document with column
widths that are not set to default, the Web Intelligence XI R2 (.wid)
document may contain column width issues.
Workaround: Enable “Autofit Width” in the Properties tab for the affected
columns and column headers.
• Scope of analysis is not migrated. Some objects are present in the Result
pane but they should be present only in the Scope Of Analysis pane.
• The WQY date is incorrectly migrated.
Performance Management
To see other release notes for Performance Management see Performance
Manager.
• Even if you deactivate the Import Categories, Import Documents and
Import Universes options while migrating from Application Foundation
6.x to BO XI R2, the Select Categories, Select Document, and Select
Universe screens appear and all Application Foundation 6.x related
documents, categories, universes, and connections are imported.
• Universes with subjects based or metrics associated are not imported.
• On SQL - When you select a connection to make the repository point to
the Application Foundation repository, the Connection box displays data
that is not from that connection.
• On the Setup tab of the Connection box (pointing to the Application
Foundation repository), too much data is displayed. The correct
connection names are displayed in the middle of other information
wrongly displayed as connections.
• If you add a filter to an existing metric, the metric entry is duplicated.
• During the migration of goals (in goal name) and metric tree (in metric
tree name and description), accentuated character migration does not
occur correctly.
• Upon displaying the migrated dashboards, the AAAnalytics process used
over 200K of memory and more than 90% of CPU resources. Tomcat
also uses large amounts of CPU at random.

6 Import Wizard
• The Metric list on the dashboard is not well displayed after migration for a
non-administrator user.
• The Metric list incorrectly offers “Display Goal Analytic” from its
navigation menu when no goal exists. When the Metric list has been
navigated, the “Display Goal Analytic” option is always available from the
Navigation menu for all items listed, whether a goal exists or not.
• After migration, the user can create a very long rule; after refresh the
formula definition fully disappears.
• The metrics of some universes are set to Manual Entry and are no longer
available for refresh.
• The warning message that appears when migrating from Application
Foundation 6.1 does not contain all of the necessary information.
General
• Migration to Performance Management XI R2 is only supported from the
following versions of Application Foundation: 6.1.b, 6.1.3, 6.5.1 and
Performance Management XI.
• There is a check on repository version in Import Wizard that should block
versions prior to 6.1.b but currently allows migration from versions 6.1
and 6.1.a. Migration from these versions of Application Foundation is not
supported.
• Business Objects recommends that you migrate all of your Application
Foundation objects at one time using the Import Wizard. An incremental
migration can result in corrupt links.
• When upgrading the Application Foundation repository from version 6.x,
use the Import Wizard. The repository upgrade in the Performance
Management Setup does not upgrade the version 6.x repository to XI R2.
Business Objects strongly recommends that you back up your
Application Foundation repository before launching the Import Wizard.
Failure to do so will result in the repository being unreadable in the 6.x
environment. To maintain the source system after migration, follow these
steps after the XI R2 installation:
1. Copy your AF 6.x repository using the account under which you will
access the Performance Management repository.
2. Use the Import Wizard to migrate your Business Objects and
Application Foundation objects to the CMS and to upgrade the
Application Foundation 6.x repository.
3. In Setup, configure Performance Management to use the migrated
repository.

Import Wizard
Performance Management 6
Refer to the BusinessObjects 6.x to XI Release 2 Migration Guide for
more information.
• Before importing schedules with the Import Wizard, you must define the
local server administrator account under which schedules are executed.
Note: If you migrate from BusinessObjects 6.x to XI R2, some agnostic
files are not supported by the CMS and are therefore not migrated. Refer
to the BusinessObjects 6.x to XI Release 2 Migration Guide for more
information.
Known Issues
• The Import Wizard does not import Application Foundation 6.x schedules
to CMS on Oracle.
• Before importing Application Foundation 6.x schedules to an SQL server
CMS with the Import Wizard, manually create an AFScheduleProgram
object in the destination CMS. The Import Wizard does not correctly
import AFSchedules to SQL server unless you perform this step before
running the Import Wizard.
• Links in personal dashboards to personal documents are not migrated.
• When upgrading the performance management repository from version
XI, use the repository upgrade in System Setup. You cannot upgrade a
version XI repository to version XI R2 in the Import Wizard.
• When migrating from Application Foundation versions 6.1b, 6.1.3, or
6.5.1 to BusinessObjects Enterprise IX Release 2, access restrictions on
dashboards may not be migrated correctly. Unauthorized users may be
able to access restricted dashboards and dashboard items. Other
performance management rights imported to the CMC may not be
applied correctly in the destination environment, and some users may
lose certain access rights.

6 Import Wizard

Intelligent Question
chapter
7 Intelligent Question
Exporting to Web Intelligence
Exporting to Web Intelligence

• When you export an answer to Web Intelligence, you must save it in Web
Intelligence before editing it. If you edit it first, and then try to save it, you
will receive the following error:
An error has occurred: The object with ID 0 does not exist in the CMS or
you don’t have the right to access it.
Workaround: To prevent this error, save the answer in Web Intelligence
as soon as you export it.
Configuring SSL
In the CCM, the Protocol tab in the Properties dialog box is used to configure
SSL for all servers in the Business Objects system. However, for the Question
Engine, the Protocol tab does not appear.
You need to configure the command line parameters manually. Enable SSL
for (at a minimum) CMS, PageServer, and CacheServer.
To add the SSL command line parameters to the Question Engine:
1. In the CCM, stop the Question Engine if it is running.
2. Right-click QuestionEngine and select Properties.
3. Click in the Command text box and scroll to the end of the text.
4. Paste in the command line options as described in the CCM Help (look
for SSL). For example:
-protocol ssl -ssl_certdir "C:\ssl" -ssl_mycertificate
"servercert.der" -ssl_trustedcertificate "cacert.der"
-ssl_mykey "serverkey.pem" -ssl_mykey_passphrase
"passphrase.txt"
To find the correct command-line parameter values for your server after
SSL is configured, right-click the CMS, select Properties, click in the
Command text box, and copy the SSL-related parameters from there.
5. Make sure all the servers are running.
6. Open InfoView and click Intelligent Question.
The Question Panel should function correctly.

OLAP Intelligence
chapter
8 OLAP Intelligence
Installation
Installation
(xir2_oi_olapinstall_xx.pdf).
Essbase support
A new Essbase/DB2 OLAP driver delivers enhanced support for native
Essbase features such as multiple alias tables, Dynamic Time Series,
attribute dimensions, and user-defined attributes.
Application behavior
• Calculated members from higher hierarchical levels in a dimension
appear with members from lower levels. The problem occurs if you use
OLE DB for OLAP (MSOLAP) data sources, your Worksheet contains a
dimension with three or more levels in its hierarchy, and calculated
members are on some or all of the levels in the hierarchy.
For example, if your dimension has four levels (level 4 being the lowest
child level), and calculated members exist at all four levels, when you
invoke the Member Selector by right-clicking a level 1 member, and then
use the function Add Children to Selection > Custom to display only the
level 4 members, the calculated members at level 2 are displayed along
with the level 4 members.
You can manually deselect the calculated members to remove them from
the Worksheet.
• OLAP reports that have been saved to BusinessObjects Enterprise by
the OLAP Intelligence designer appear as reports created and saved by
the Interactive Viewer. The Worksheet and Chart buttons appear on the
toolbar, and the Worksheet and Chart in the report can be toggled on and
off.
The problem happens in the following situation:
• An OLAP report is created in the Interactive Viewer and saved to
BusinessObjects Enterprise.
• The report is closed, but the InfoView session is left open.
• The report is then opened in the OLAP Intelligence designer and re-
saved to BusinessObjects Enterprise with the same name.

OLAP Intelligence
Application behavior 8
• The report is re-opened in the Interactive Viewer in the same
InfoView session.
To correct this situation, log out and log back in to InfoView.
• In .NET InfoView, when you create a report that is based on an Essbase
or DB2 OLAP data source, the cube list page fails to load.
• The height and widths of the column heading cells are resizable, and the
text in the heading cells is set to wrap by default. The report’s text wrap
setting can be changed in the OLAP Intelligence designer.
• For OLAP Intelligence reports, action URLs are always launched in a
new browser window. Consequently, if you use the sWindow URL
parameter with an openDocument URL in an action, you may receive an
error.
Workaround: Do not use the sWindow parameter in your openDocument
URLs.
The sWindow parameter determines whether the target report opens in
the current browser window or in a new browser window.
• When OLAP Intelligence reports are viewed in the DHTML Interactive
Viewer, strange behaviors such as the following may occur, depending on
your Internet Explorer settings:
• Some buttons (for example the OK and Help buttons) may be hidden
by the status bar.
• Export to Excel fails to work.
• The Copy to Excel function in the Drill Through Viewer window fails
to work.
• An error may occur when you use the “Select All Members at Level
x” option in the Member Selector.
To ensure that the DHTML Interactive Viewer functions properly in your
version of Internet Explorer, please refer to the following guidelines:
• Add the website that hosts the InfoView application as a trusted site
in Internet Options (Windows XP Service Pack 2 and Windows
Server 2003 Service Pack 1).
• Disable Enhanced Security Configuration (All versions of Windows
Server 2003).
• Turn off the pop-up blocker (Windows XP Service Pack 2) or add the
site to the Allowed sites for pop-up windows.
• Help windows that are invoked in the Excel Add-In may not close when
the Excel workbook is closed.

8 OLAP Intelligence
• In the DHTML Interactive Viewer, the whole page is refreshed after the
Member Selector window is closed.
The cause of the problem is that some browsers, such as Firefox and
Mozilla, are capable of refreshing only the entire page, not components
on a page.
For users of the BusinessObjects XI Integration Kit for SAP
• Null suppression is on when an OLAP report is first created.
This behavior is intentional when creating OLAP reports against an SAP
BW data source, to maintain consistency with SAP default views. You
can turn off null suppression with the toolbar button.
• The Member Selector in the Set Parameters dialog box may be slow to
load large numbers of members. As a result, several minutes may pass
before the Set Parameters dialog box appears; then it takes more time for
the Member Selector to display.
• The URL syntax for opening a .car file in .NET InfoView is changed in
OLAP Intelligence XI R2.
Old URL syntax:
http://<Machine name>/styles/csp/
analysisviewer_sap.csp?id=<Report ID>&sap_client=<SAP
Client>&sap_sysid=<System ID>
New URL syntax:
http://<Machine name>/businessobjects/enterprise115/SAP/
InfoView/analysisviewer_sap.csp?id=<Report
ID>&sap_client=<SAP Client>&sap_sysid=<System ID>
• In .NET InfoView, the Calculated Members dialog box does not load
properly with some Asian languages unless the Asian language packs
are installed on both the server and client machines.
Workaround: Install Asian language packs on both the server and client
machines. To install the language packs on a machine running Microsoft
Windows, do the following:
1. Click Start > Control Panel > Regional and Language Settings.
2. On the Languages tab, select “Install files for East Asian languages”,
and then click OK.
3. Reboot.

OLAP Intelligence
Data source connectivity 8
• When using the Firefox Internet browser to access the HTML Query
Panel in Web Intelligence, OLAP reports are not uploaded correctly if the
language font used in the report name does not correspond to the
language of the Firefox version and the operating system.
Workarounds:
• Make sure the report, operating system and Firefox version are the
same language.
• Use Microsoft Internet Explorer to access Web Intelligence, since
this issue does not occur with Internet Explorer.
Data source connectivity

• Holos connectivity is no longer supported. When a user opens a Holos
report, the following message appears:
“The report cannot be opened because Holos data sources are not
supported as of BusinessObjects XI Release 2.”
• Calculated cells may be displayed as empty. If you use an OLE DB for
OLAP (MSOLAP) data source, you may encounter problems with custom
calculations that are based on other calculations.
For example, create a calculation (A) and then create a custom calculation
(B) based on the first calculation. If you change calculation A, the cells in
calculation B display as empty; you must recreate calculation B.
General issues
• Errors occur when OLAP Intelligence reports are previewed in the
Central Management Console. Note that the Preview function is
designed only for use by system administrators who want to ensure that
reports display correctly. If you try to manipulate or save reports in
preview mode, the errors occur.
• The OLAP Intelligence Navigation toolbar may not be removed when the
OLAP Intelligence Add-In for Excel is disabled. When the OLAP
Intelligence Add-In is disabled from the Add-Ins option on the Tools menu
in Microsoft Excel, the OLAP Intelligence toolbar is removed, but the
OLAP Intelligence Navigation toolbar may remain. Use the Customize
option from the Tools menu in Excel to manually remove the toolbar.
• When connected to a MSOLAP data source, OLAP Intelligence may
produce erratic behavior when the underlying data cube is refreshed.
Your report may become unstable and potentially unusable.

8 OLAP Intelligence
General issues
If you need to refresh an OLAP cube, ensure that no other user is

working with the cube when you refresh it. If you refresh the cube while a
user is working with a report that uses the cube, the report’s data may fail
to be properly updated.
• Data fails to export to Excel from OLAP Intelligence. On a machine where
OLAP Intelligence has completed its installation and Excel has not yet
been opened, if you attempt to export an OLAP report to Excel, the
export fails. Although an instance of Excel appears on the taskbar, the
instance is inactive.
To export to Excel successfully, manually open Excel and then close it.
Exporting will then work as expected.
• By default, OLAP Intelligence uses XSLTC, which is not supported on
WebSphere and WebLogic. If you use WebSphere or WebLogic, append
the following to your JVM arguments (for WebSphere) or your
java.options (for WebLogic):
-Dbusinessobjects.olap.xslt.TransformerFactory=
org.apache.xalan.processor.TransformerFactoryImpl
• By default, processes are handled within ASP.NET. Because this has
limited scalability, you may want to run processes outside of ASP.NET.
For information on running processes outside of ASP.NET, refer to the
following technical brief on the Business Objects online support site:
Improving the performance and scalability of BusinessObjects OLAP
Intelligence XI.
• Copying and pasting from the ActiveX Interactive Viewer into another
application fails to copy all the information.
This is an issue with the Windows clipboard.
• In the CMC, the navigation pane that is above the tabs may disappear
when you use the Rights tab to add, remove, or check user rights for an
OLAP Intelligence object.
Workaround: Select any item from the list at the top of the CMC screen.
The navigation pane is regenerated.
• Values in an Excel sheet show inconsistent formatting. For example, the
values in the Total Expense column are formatted as currencies, but the
values in the Net Sales column are not formatted as currencies. All the
values are displayed as currencies within the OLAP Intelligence designer
and on the server.
This issue appears when inconsistencies are found in how data is
entered into the database. For example, some numbers may have been
entered as currencies and some may have been entered as reals.

OLAP Intelligence
Documentation 8
• If you modify a calculated member with the Calculation Expert or Data
Analysis Expert, and then switch to a different expert before you've
finished your modification, Internet Explorer may crash.
Avoid using the Calculation Expert when you edit calculations with the
Data Analysis Expert that were created with the Calculation Expert.
Similarly, avoid using the Data Analysis Expert when you edit calculations
with the Calculation Expert that were created with the Data Analysis
Expert.
For more information, see the following support article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;831845
• The “Copy to clipboard” option is unavailable in the Drill Through Viewer
of the DHTML Interactive Viewer.
Documentation
• In the chapter “Enabling the DHTML Interactive Viewer in Java InfoView“,
a paragraph in the Prerequisites section should read as follows:
OLAP Intelligence components, by default, are installed to the directory
C:\Program Files\Business Objects\OLAP Intelligence
11.5\. If you choose to install to a different location, substitute your
install path for the default in the generic Java Virtual Machine (JVM)
arguments. The instructions in this chapter assume that you have
installed to the default location. You must use the shortened directory
naming convention shown (that is, C:\Progra~1\ rather than
C:\Program Files\) to ensure that no spaces are entered in the
argument line. Spaces can be misinterpreted as an additional argument
and can cause errors. If your operating system does not support
shortened directory names, use the full path surrounded by quotation
marks.

8 OLAP Intelligence
Documentation

chapter
9 Performance Management
General
General
• When the maximum number of concurrent users is reached, the last user
to log in has limited options within InfoView and no access to the
performance management repository, and users already logged in who
have not accessed the performance management repository will be
denied access.
Swedish
• Truncations and translation errors occur when you try to create
dimensions, analytics, populations, sets, and models.
Installation
• If you are installing the Performance Management products on a SQL
server, the AFdemo can be installed on the SQL server as a demo
Performance Management repository. If you do this, however, the
datasource name will be created, but the connection might not work
properly.
Workaround:
1. In the CCM, stop the servers.
2. In Designer, select Tools > Connection.
3. To the AFDEMO connection, add your SQL server password.
4. Test the connection to make sure it works.
5. In the CCM, restart all of the servers.
The AFDEMO is now available.
Note: The database does not support double bytes. If you want the
database to support them, you need to change the collation name.
To do this:
1. In the CCM, stop the servers.
2. In the SQL Server Query Analyzer, log in to your SQL server.

Configuration 9
3. In the query panel, run the following command:
USE Tempdb
GO
ALTER DATABASE AFDEMO COLLATE [collation_name]
GO
where [collation_name] = Japanese_CI_AS (for Japanese) or
Chinese_PRC_CI_AS (for Chinese).
4. Verify that the collation name is changed in the SQL Server
Enterprise Manager.
5. In the CCM, restart all of your servers.
Configuration
International
• You cannot populate ASCII data in a dimension on Sybase.
Migration
• When you migrate from Business Objects 6.1.3 on a SQL server, the
target database and user in Performance Management are not visible,
but the connection still exists and works correctly.
Connections
Sybase ASE ODBC
• An error occurs if you use the Sybase Adaptive Server 12 open client to
create the performance management repository. You need to use a
Sybase ASE ODBC driver to create the repository.
To do this:
1. Install Sybase using the correct language model.

Connections
2. In the following registry location, create a new value string called

Sybase ASE ODBC3 datasource with the value Sybase ASE
ODBC3 datasource:
HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite
11.5\default\Shared\ConnectionServer\ Network
Layers\ODBC\SQL List
3. Add the following lines to the <databases> section of the odbc.sbo
(located at [BO XI R2 Installation]\BusinessObjects
Enterprise 11.5\win32_x86\dataAccess\connectionServer\ odbc):
<DataBase Active="Yes"Name="Sybase ASE ODBC3 datasource">
<Libraries>
<Library>dbd_wodbc3</Library>
<Library>dbd_odbc3</Library>
</Libraries>
<Parameter Name="Family">Generic</Parameter>
<Parameter Name="Version">rdbms_odbc3.txt</Parameter>
<Parameter Name="SQL External File">sybase</Parameter>
<Parameter Name="SQL Parameter File">sybase</Parameter>
<Parameter Name="Driver Level">31</Parameter>
<Parameter Name="Query TimeOut Available">No</Parameter>
<Parameter Name="Array Bind Available">False</Parameter>
<Parameter Name="Binary Slice Size">32000</Parameter>
</DataBase>
4. Save your change.
5. Copy the sybase.rss and sybase.prm files from:
[BO XI R2 Installation]\win32_x86\dataAccess\connectionServer
\sybase
to:
[BO XI R2 Installation]\win32_x86\dataAccess\connectionServer
\odbc
The ODBC Drivers option now appears in the Generic Selection
panel in the Designer connection wizard.
6. For non-English versions of BO XI R2, you need to use a text editor
to modify the locales.dat file in the following location:
<Sybase install folder>\locales\
Change the default locale's charset to use utf8 (or another suitable
charset, e.g. sjis) based on your platform. For example, if you are on
a Windows server make the following change in the [NT] section:
locale = default, us_english, iso_1
to:
locale = default, us_english, utf8

Deployment 9
7. In Designer, create two Sybase connections:
• in the Generic section to use the Sybase ASE ODBC3 driver
• in the Sybase section to use the Sybase Adaptive Server driver
8. Create the performance management repository using the Sybase
ASE ODBC3 connection.
Note: You may need to restart all the servers in the CCM to activate
the connection.
9. Create the universe connection using the Sybase Adaptive Server
connection.
10. Change to the Sybase Adaptive Server connection to the repository
in the performance management System Setup to complete the
setup.
Note: The Sybase ASE ODBC3 connection is only for creating the
repository.
• The univarchar data type is not supported.
• Non-ASCII data is not supported in Performance Management for the
Object for Dimension name and Object for Dimension code objects in
dimension creation.
Deployment
• There is one additional WAR file to deploy if you installed performance
management and you are deploying on any of the following web
application servers:
• WebSphere
• WebLogic
• Oracle Application Server
• SAP NetWeaver
This WAR file, which contains the online help for performance
management, is called afhelp.war and can be found at C:\Program
Files\BusinessObjects\Performance Management 11.5. The WAR file
should be deployed with the context root /bobje.
• To deploy performance management products on a different server from
BusinessObjects Enterprise XI R2:
1. Install your web application server and Web Component Adaptor
(WCA) on Server 1.

Deployment
2. Install BusinessObjects Enterprise XI R2 and the CMS on Server 1.

3. Perform an Expand installation on Server 2 and select EPM in the
Expand Options dialog box.
The web application server on Server 1 now has the desktop.war file
deployed without the EPM components, and Server 2 has the
pm11.boar file installed. The boar file contains the EPM components
you need to deploy to the web application server on Server 1 and
needs to be merged with the desktop.war file.
4. Stop Tomcat.
5. Remove the desktoplaunch web application folder, located in the
following location:
<BO_INSTALL_DIR_SERVER_1>\Tomcat\webapps\businessobje
cts\enterprise115\desktoplaunch
6. Using the mergeboar.jar tool, rename the desktop.war file
backup_of_desktop.war and move it from the following location:
<BO_INSTALL_DIR_SERVER_1>\BusinessObjects Enterprise
11.5\java\applications\
to:
<BO_INSTALL_DIR_SERVER_1>\
7. Run the following command line on Server 1:
java -jar "<BO_INSTALL_DIR_SERVER_2>\Performance
Management 11.5\setup\mergeboar.jar"
"<BO_INSTALL_DIR_SERVER_1>\backup_of_desktop.war"
"<BO_INSTALL_DIR_SERVER_2>\Performance Management
11.5\pm11.boar"
"<BO_INSTALL_DIR_SERVER_1>\BusinessObjects
Enterprise 11.5\java\applications\desktop.war"
8. To set the Java option property of the Tomcat Configuration, go to
Start > Programs > Tomcat > Tomcat Configuration.
9. In the Java Options edit box on the Java tab add the following line:
-Daf.configdir=<BO_INSTALLDIR_SERVER_2>/Performance
Management 11.5/
10. Create an afhelp.xml file under <BO_INSTALL_DIR_SERVER_1>/
Tomcat/conf/Catalina/localhost that contains the following line:
<Context docBase=”<BO_INSTALL_DIR_SERVER_2>\Performance
Management 11.5\afhelp.war” path=”/bobj”
crossContext=”false” debug=”0” reloadable=”false”
trusted=”false”/>

Upgrading and migrating issues 9
11. Restart Tomcat.
Tomcat deploys the afhelp.war and new desktop.war file
automatically.
• If you have a cluster deployment with a secondary node dedicated to
performance management processes, for this secondary node you must
select Expand in the BO XI R2 setup wizard and click Next. In the Expand
Options panel, change the CMS name to that of the PRIMARY node, and
activate Processing Servers and EPM.

Note: You need to be sure to read the migration issues for Performance
Management in the Import Wizard chapter: Performance Management.
• Set tables are not migrated correctly. Update your set tables after
migration in Setup > System Setup > Repository.
Dashboards
• Process Tracker is not available in the Corporate Analytic folder as an
analytic or a link.
• In the InfoView preferences, when you change the options Create a
Single Dashboard or Create a Tiered Dashboard in the General tab,
you need to click OK. If you click Apply, your option change will not be
applied.
• The scroll bar does not function for the Corporate Tiered Dashboard list
in performance management.
• In SAP Netweaver, a page error occurs when you create a goal or
analytic and click on Add to my dashboards.
Analytics
• When you click Cancel from the analytic prompt, the analytics properties
page reappears with all or most settings returned to the default settings.
• When you click Save As for an analytic saved in FLASH format, the title
does not appear and the only format available to save in is SVG.
• When you use the [Red] or [Blue] option in Designer to format labels, the
option name appears in the Y axis label of the Goal analytic.

Analytics
For example: if you apply the [Red] option in Designer, it will appear as
100 [Red] on the Y axis instead of 100.
• The WebSphere application server crashes when you try to create a Map
analytic.
Workaround: Define a system environment variable:
Name: JITC_COMPILEOPT
Value: SKIP{com/corda/pcis/c/c}{a}
• When you set the following metrics to open in a separate window, they
still open in the parent window:
• Speedometer
• Interactive Metric Trend
• Metric List
• When you try to refresh an analytic after e-mailing it to someone, the
following error message appears: “The document you are trying to open
no longer exists in the system.” However, the document does still exist.
Workaround: Log out and back in again to see the document.
• When you open a Metric Forecaster document in Predictive Analytics,
two error messages appear, but if you click OK for both of them, the
document appears as normal.
• An error occurs when you link to an analytic from within another analytic,
if you specify the repository type as 'M' or 'P' when creating the
openAnalytic URL.
Interactive Metric Trend

• Interactive Metric Trend analytics migrated from a Application
Foundation 6.5.1 repository and that contain no data should display the
error message "No metric to display." However, they actually display
"Interactive Metric Trends".
• The slice/unslice link does not work from a browser launched inside
VMWare.
Documentation
• The Dashboard Manager online help incorrectly states that you can
create a metric or goal type using a Change variation to detect lag.
Lag can be detected once the analytic is created:
1. Click the analytic to select the beginning point.

Dashboard Manager 9
2. Drag the mouse pointer to a prior period.
The Change and % Change calculations in the measure section
change to show the lag between the start and end points. The time
slider also changes to navigate between the start and end points.
• The Dashboard Manager online help does not discuss the following
graph options in the Trend Analysis analytics topic:
• Cumulative Sum: the running sum of a set of periods.
Generic formula: Metric value Current Period + Metric value Prior
period
• Month to Date: the running sum for each month.
period
• Quarter to Date: the running sum for each quarter.
period
• Year to Date: the running sum for each year.
period
Map analytic
• If you select the GL (Groenland) option in the Map analytic, the following
error appears: "Couldn't Create Image".
Pareto chart
• A Pareto Chart created in Application Foundation 6.5.1 and migrated to
BusinessObjects Enterprise XI Release 2 does not appear in snapshot
format.
Dashboard Manager
• Use of values larger than 1.0E27 may cause performance management
to freeze. When you try to display some analytics (like the goal analytic)
that contains such values, an error occurs.

Performance Manager
• If you select the 'Top Slices' document in the Metrics Analytics tab, it
appears to load, but then the following error message appears:
This document is not available on MS SQL Server Database.
• In the Metrics page, the refresh of groups of metrics does not always
work.
Workaround: In this case, refresh each of the metrics belonging to the
group individually.
• The Destination section in the Scheduler Analytic Refresh dialog box
shows a list column that contains the following item:
??schedule.destination.defaultmanaged???
• If you are using SAP Netweaver, a script error occurs when you try to
schedule a refresh.
• When you create metrics, a metric name is generated automatically that
may not make sense in some languages. You should type your own
metric name instead of using the system default name.
Performance Manager
• An error may occur when you publish a goal or metric, or if you try to
activate a goal or metric manually or using in Strategy Builder.
Workaround:
1. Open your CMC.
2. Restart the AA Alert & Notification Server.
• If you create a bipolar goal based on a universe query with only one
upper tolerance that is designated as the first upper tolerance, this
tolerance is not displayed.
• If you are using SAP Netweaver, a script error occurs when you try to
create in Strategy Builder a new strategy or role, or publish a goal or
metric.
My Goals page
• Not all of the action hyperlinks work on the My Goals page.
• After migrating from 6.5 to BusinessObjects XI or XI R2, the publications
may not be visible in the My Goals tab and you may not be able to publish
a goal or metric to certain users.

Predictive Analysis 9
Workaround:
1. Migrate the Business Objects repository.
2. Start your server.
3. In Strategy Builder, click the Organization tab.
4. Select the Everyone role and click Edit.
5. Click Next to go to the role definition page.
The group is defined as Dynamic (Business Objects query) on the
root folder name of your migrated 6.5 repository.
6. In the Groups list, select Everyone.
7. Click Next, then Update Role.
8. Click Refresh Membership.
9. Verify that all other roles are part of the "Everyone" group.
Predictive Analysis
• You cannot use range limits with the binning variable.
• An error occurs when you try to refresh a new model-based metric based
on a set metric.
Workaround: You need to manually set the packed_result value in the
ci_param table. Insert the following into the ci_param table:
(param_id, param_type, item_name, item_value) values
(0, 1, 'packed_result size', [packed_result
value])
where [packed_result value] is the size of your set metric. The
internal server maximum is 30000 when packed_result size is not set.
• If the default value for the packed_result size in the ci_param table is not
compliant with your database configuration, the following error message
appears when you create a model-based metric:
(Load Model error error during the uudecode - size
problem )- 147

Process Analysis
To resolve this issue:

1. Verify that the ci_param table contains the following values:
(param_id, param_type, item_name, item_value)
where item_name is ‘packed_result size’, and item_value is
an integer that corresponds to the maximum size of the
ci_context_output.packed_result.
Example: insert into ci_param (param_id, param_type, item_name,
item_value) values (0, 1, 'packed_result size', 20000)
2. Restart the performance management servers.
3. Refresh the models.
Process Analysis
• After you have migrated the Rules Engine, the formulas of new, long
rules vanish after a refresh.
2-tier products: Set Architect and Set

Analyzer
BusinessObjects XI Release 2 supports Set Architect, but not Set Analyzer in
2-tier mode.
For more information refer to the supported platforms documents, available
at:
http://support.businessobjects.com/supported_platforms_xi_release2/

Portal Integration Kit
chapter
10 Portal Integration Kit
SharePoint web parts
SharePoint web parts

Installation
complete installation instructions, see the installation guide.
installation.
Security and login issues

• If you use concurrent licenses, one license is used each time you view a
document in the Sharepoint web part. To avoid overuse of concurrent
licenses, use the named user license.
• The CMS name specified by the "BusinessObjects Central Managerment
Server" property in the web.config file must be fully qualified and all
uppercase.
Viewing issues
• In the Microsoft Sharepoint portal, you may need to adjust the layout
options to view a report in the Document View web part:
• From the Modify Shared Web Part tool pane, expand the
Appearance section, and set the width and height for the display
area.
Use Pixels as the unit of measure.
Firefox browser issues

If you use the Firefox browser to view the Microsoft Sharepoint web parts, you
may experience these issues:
• You cannot make a connection between the web parts, because the
"connections" option is on a drop-down menu. Firefox does not support
drop-down editing.
• Objects such as Word, Excel, PowerPoint, and RTF files may not display
in the web parts unless the necessary plug-ins are installed.
• In edit mode, some options may be hidden due to layout issues.

Portal Integration Kit
JSR168 portlets 10
JSR168 portlets
Installation
complete installation instructions, see the installation guide.
installation.
• The following versions of the portal platforms are supported for the Portal
Integration Kit in BusinessObjects Enterprise XI Release 2:
• IBM WebSphere Portal 5.1
• BEA WebLogic Portal 8.1 SP4
• Oracle 10g Portal Release 2
Viewing issues
• The help files may not display correctly in the browser for some Asian
languages. The workaround is as follows:
• From the View menu, select Encoding, and then click “Unicode
(UTF-8)”.
Documentation
• For the latest version of the documentation, see “Product Documentation
on the Web” at the following site: http://support.businessobjects.com/
documentation/.
• The System Requirements section in the Portal Server installation guide
states that Microsoft Windows Server 2000 or 2003 is required; however,
the Microsoft Windows Server is not required when you install the Portal
Integration Kit on a UNIX system.
• For this release, the documentation is unavailable in Swedish or
Portuguese.

10 Portal Integration Kit
JSR168 portlets

Semantic Layer
chapter
11 Semantic Layer
Designer
Designer
• The SQL syntax for Derived tables is not supported by Informix
databases.
• Although Oracle 8.x is not supported, it is available in the list of database
middleware in the Create a Connection wizard.
• You cannot create a connection with IBM DB2 if the IBM DB2 client is
installed after installing BusinessObjects.
Workaround: Install your IBMDB2 client before installing
BusinessObjects.
• The creation of universes from Metadata Exchange (File > Metadata
Exchange) is not supported on database schemas containing tables and
columns whose names contain special characters (such as: \ / @ * ,
space character).
• A universe object for which the property "can be used in result" is not
selected causes an error to occur when Web Intelligence queries
involving that object are run.
• You must install the BusinessObjects XI Release 2 Integration Kit for SAP
before you can create and use SAP OLAP universes.
• Sample universes and reports are installed in the
<INSTALLDIR>\Samples folder, where <INSTALLDIR> is the Business
Objects installation directory.
If you get a connection error when importing a sample universe to
Designer, or a "Universe can not be found" error message when
refreshing a sample report, refer to the online version of the release
notes for further information on how to solve this problem.
Business View Manager

When you create a DataFoundation using an SQL expression that contains a
concatenate (x+y) operator, the Business View Manager closes unexpectedly.
Connection Server
A Web Intelligence query can not be run when Connection Server is operating
in server mode.

Report Conversion Tool
chapter
12 Report Conversion Tool
Conversion
Conversion
• In Web Intelligence, the crosstab has horizontal and vertical lines
missing. This happens with crosstab that include functions such as
percentage.
• A cell with only wrap text and long text shrinks both in height and in width.
• After conversion, the Date format and Boolean format in a cell are
mapped to custom format, but not with a similar format.
• In the log file, entries for dangling references appear instead of missing
references.
• A custom sort on formula/Variable is not converted. In addition, internal
error occurs when view Result is selected.
• LastExecutionDate differs after migration.
• Custom sorts are not converted in MDP documents on merged
dimensions.
• Some formulas show a #DATATYPE error after migration.
• It is impossible to switch to page mode in the Java Query Panel when
Margin has been decreased in Desktop Intelligence.
• When a multi-tab REP file is converted to WID, it does not keep the
original selected tab.
• A cell containing a call to external functions is replaced by blank cells.
• Multiple Query Filters using prompt with same text and different operand
type.
• A query that has prompts with the same question (text) but a different
MONO or MULTI setting and a different response type among string,
numeric and date returns an error message.
• After conversion, 2D charts on refresh have axis lines missing.
• Measure values are not placed properly in scatter charts.
• Chart axes are displayed in Web Intelligence even though they are not
displayed in Desktop Intelligence.
• The number format for chart axis values is not converted in Web
Intelligence.
• A Publish Failed error occurs when you attempt to convert two
documents with same name in the Conversion Status window.
• The conversion status of REP documents converted to Web Intelligence
format by the Report Conversion Tool is not applied consistently.
• Migration of break properties, filter, ranking and 2cube documents may
be incorrect.

Report Conversion Tool
User interface 12
• A free cell attached to a block is lost after conversion.
• The following Break options may not be correctly converted: Remove
duplicate, Center value across break, Repeat the header on the new
page, and Repeat break values on new page are not selected.
• In the Java Report Panel, the ranking in reopened and refreshed
converted Web Intelligence documents that are reopened and refreshed
may be in a different order than in the source document.
• 2cube documents are not converted. They return an unhandled error.
• Some filters may not be converted. They will have a “Failed” status and
no log.
• When a converted Web Intelligence document is opened in Infoview, drill
hyperlinks are not available before or after refresh. When a Web
Intelligence document is opened in the Java Report Panel, drill hyperlinks
are not available before refresh but are available after refresh.
• Free-Hand SQL documents are not identified during conversion.
• Long document properties are not converted correctly.
• The category of source REP documents is not shown under the Target
categories column header in the Publish reports screen.
User interface
• Clicking the Close button in of the Report Conversion Tool caption bar
does not close the tool.
• The Start Conversion Button is not enabled when documents are
selected using the shortcut menu command “Select categories and
subcategories".
Log files
• Log files are not generated correctly in the French version.
• The "Focus" field in the log file for page setup and VBA macros is empty.
• The “Focus” field in the log file for conversion to WID format of REP files
containing the Fill option for columns is empty.
• The error message text in the log file for chart legends has the chart title
entry.

12 Report Conversion Tool
Configuration Management Console (CMC)
• When no audit connection has been defined for the Report Conversion
Tool, an irrelevant error message (MIGTOOL_UNKNOWN_ERROR)
appears in addition to the correct error message when you try to write to
the audit log.
Workaround: Before using the Report Conversion Tool, define an audit
connection for it using the Central Configuration Manager (CCM).
Configuration Management Console (CMC)

• The FCtoWebI.unv file is not shown in the “Report Conversion Tool
Universes” folder.
• The “Migration Audit Statistics Template.wid” document is not shown in
the “Report Conversion Tool Audit Documents” folder.
Documentation
The Report Conversion Tool Guide says that reports from which breaks have
been removed have converted status. In fact, they have partly converted
status.

Web Intelligence
chapter
13 Web Intelligence
Formula language
Formula language
Referencing data outside a section
Web Intelligence now references data outside the current section in a formula
that uses the In or ForAll operators.
Example: The In and ForAll Operators in a section
Here is a sample report based on the Insland Resorts Marketing universe,
with the values now returned by Web Intelligence.
France
Year Revenue [Revenue] In [Revenue] ForAll

[Year] [Country]
FY1998 295,040 1,063,554 1,063,554
Previously, Web Intelligence returned 295,040 in the last two columns

because it considered the data in the France section only. Now it considers all
data.
ReportFilter() function
The documentation states that the ReportFilter() function returns all
report filters when passed an empty string as a parameter. In fact the function
returns an empty string in this case.
RunningSum() function
The RunningSum() function returns incorrect values when used with the
Block keyword as an input or output context.
The functions appear in English in the interface when the interface language
is Japanase, Korean, Chinese (Simplified) or Chinese (Traditional).

Web Intelligence
Cell formatting 13
Cell formatting
Web Intelligence does not apply a corresponding cell format by default to a
cell containing a function. (By default, Web Intelligence uses the cell format
specified in the document locale.) For example, a cell containing the Rank()
function, which outputs an integer, might not be formatted by default to
display an integer.
Workaround: If necessary, change the cell formatting to correspond to the
function output.
Note: You should be aware of the difference between changing the cell
formatting and using the FormatNumber() function. If you format a number
using FormatNumber(), the function outputs a string with the specified
format. This means that, for example, you cannot carry out further
arithmetical operations, like multiplication or division, on the function output.
Security
If you do not have the rights to view a universe, you do not see it in the list of
universes, but you can open a report that is based on a universe to which you
do not have access in the Java Report Panel.
Limits
The Web Intelligence software itself does not impose limits on documents (for
example, there is no limit on the number of columns that a table can contain).
However, limits are imposed by the following factors:
• Parameters set in the Central Configuration Manager (for example, the
maximum size of a list of values).
• The software/hardware environment in which Web Intelligence runs.
The limitations of the software/hardware environment mean that restrictions
such as the maximum number of columns in a table, the maximum number of
tables in a report or the maximum number of prompts in a document vary
from case to case; Business Objects cannot provide precise figures.

13 Web Intelligence
Error messages
Error messages
• The help file for error message WIS 00020 is not available. The text of
the help is as follows:
Message:
The SQL generated by the query is invalid.
Cause:
The syntax of the SQL of your query is not valid.
Action:
If you have edited the SQL manually, verify its syntax. If the SQL is
generated directly by Web Intelligence, make a copy of it and see your
BusinessObjects administrator.
Message:
Invalid identifier [identifier] at position [position].
Cause:
A formula contains an element that is not in the report.
Action:
Correct the formula.
Message:
Incompatible object data types in the subquery filter.
Cause:
The subquery attemps to compare objects of different data types (for
example a measure with a dimension.)
Action:
Edit the subquery to use compatible object types.
Change source
After you change the source of a report, hidden dimensions become visible.

Web Intelligence
Charts 13
Charts
The X-axis label is not visible on a Vertical 2D chart with a thick border.
The data series is not displayed correctly on a Vertical Stacked bar chart
when there are two measures on the Y-axis.
When the traditional Chinese font MingLiU is used in charts in Web
Intelligence, the X-Axis label, Y-Axis label and legend title are not displayed
properly.
Workaround: Use the Arial Unicode font to display traditional Chinese text in
Web Intelligence charts.
1. Install the Arial Unicode font.
2. Stop the Web Intelligence Report Server
3. Modify the following entry in fontalias.xml, located in
<InstallDir>\BusinessObjects Enterprise 11.5\win32_x86\fonts.
<FONTATTRIBUTE BOLD=”false” ITALIC=”false”
LOGICAL=”MingLiU”
PHYSICAL=”mingliu.ttc,1:ARIALUNI.TTF” />
to
<FONTATTRIBUTE BOLD=”false” ITALIC=”false”
LOGICAL=”MingLiU” PHYSICAL=ARIALUNI.TTF” />
4. Start the Web Intelligence Report Server.
Drill
An error occurs when you attempt to run a query in HTML mode after drilling
out of scope then attempting to activate query drill mode.
Sometimes it is not possible to modify a table in Interactive HTML when
working in query drill mode.
Document linking
When a call to OpenDocument contains a invalid value for the sType
argument, Web Intelligence gives an HTTP 500 error.

13 Web Intelligence
Data providers
Data providers
Web Intelligence throws an error when you click Undo after you run a
duplicated or newly-inserted data provider, then try to edit the data provider.
Custom sorts
When you merge dimensions on which custom sorts are defined, the custom
sorts are lost.
Java Report Panel and HTML Query panel

• When you navigate away from the Java Report Panel or the HTML Query
Panel, the navigation message does not appear and you can lose any
changes you have made in your document.
• In the HTML Query Panel, double-clicking on the cross-hair icon in the
top left corner of a table or chart does not open the Format Table/Format
Chart window.
• In the HTML Query Panel, a blank cell cannot be edited, and you cannot
enter any text or numerical strings into it.
• In the HTML Query Panel, you cannot use edit in place for cells by
double-clicking on them.

Crystal Reports

Uploaded by

Copyright:

Available Formats

Crystal Reports

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Crystal Reports

Uploaded by

Copyright:

Available Formats

BusinessObjects XI Release 2

Copyright Copyright © 2005 Business Objects. All rights reserved.

Chapter 2 BusinessObjects XI Release 2 Release Notes 9

Chapter 3 BusinessObjects Enterprise 11

BusinessObjects XI Release 2 Windows Release Notes 3

Chapter 4 Crystal Reports 27

Chapter 5 Desktop Intelligence 31

Chapter 6 Developer Library 39

4 BusinessObjects XI Release 2 Windows Release Notes

Chapter 7 Import Wizard 45

Chapter 8 Intelligent Question 51

Chapter 9 OLAP Intelligence 53

Chapter 10 Performance Management 61

BusinessObjects XI Release 2 Windows Release Notes 5

Chapter 11 Portal Integration Kit 73

Chapter 12 Semantic Layer 77

6 BusinessObjects XI Release 2 Windows Release Notes

Chapter 13 Report Conversion Tool 79

Chapter 14 Web Intelligence 83

BusinessObjects XI Release 2 Windows Release Notes 7

8 BusinessObjects XI Release 2 Windows Release Notes

About these notes

What is BusinessObjects XI Release 2?

Third-party contributors and applications

10 BusinessObjects XI Release 2 Windows Release Notes

12 BusinessObjects XI Release 2 Windows Release Notes

BusinessObjects XI Release 2 Windows Release Notes 13

6. You are ready to run MySQL commands. For example, to connect to

• Autodetection of CrystalReports_11_5_2005.msm is not supported on

14 BusinessObjects XI Release 2 Windows Release Notes

Upgrading and migrating issues

Importing data from Crystal Enterprise to

BusinessObjects XI Release 2 Windows Release Notes 15

• When you upgrade from Crystal Enterprise 10 Report Application Server

16 BusinessObjects XI Release 2 Windows Release Notes

Web and Windows applications

BusinessObjects XI Release 2 Windows Release Notes 17

• When you save a REP document that is viewed as HTML or PDF to

18 BusinessObjects XI Release 2 Windows Release Notes

BusinessObjects XI Release 2 Windows Release Notes 19

• "Add objects to folder"

20 BusinessObjects XI Release 2 Windows Release Notes

BusinessObjects XI Release 2 Windows Release Notes 21

22 BusinessObjects XI Release 2 Windows Release Notes

BusinessObjects XI Release 2 Windows Release Notes 23

The new format is as follows:

Application server issues

Web server issues

24 BusinessObjects XI Release 2 Windows Release Notes

Use the values shown in the table.

Configuration setting Default value (.NET Recommended

BusinessObjects XI Release 2 Windows Release Notes 25

Workaround: To enable UTF-8 support for WebSphere:

26 BusinessObjects XI Release 2 Windows Release Notes

28 BusinessObjects XI Release 2 Windows Release Notes

Java Reporting Component

BusinessObjects XI Release 2 Windows Release Notes 29

Java Reporting Component (JRC)

Crystal Reports for Visual Studio

30 BusinessObjects XI Release 2 Windows Release Notes