Release

BusinessObjects XI Release Notes
BusinessObjects XI
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. 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 2004 Business Objects. All rights reserved.
Trademarks
Copyright
Contents
Chapter 1 BusinessObjects XI Release Notes 5 About these notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 What is BusinessObjects XI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Business Objects information resources . . . . . . . . . . . . . . . . . . . . . . . . 6 Chapter 2 BusinessObjects Enterprise 7
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 UNIX issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Upgrading and migrating issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Importing data from Crystal Enterprise to BusinessObjects Enterprise XI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Importing data from BusinessObjects Enterprise 6.x to BusinessObjects Enterprise XI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Server management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Central Management Server (CMS) . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Processing servers (Page, Job, Cache) . . . . . . . . . . . . . . . . . . . . . . . 20 Report Application Server (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Web and Windows applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Business Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Central Management Console (CMC) . . . . . . . . . . . . . . . . . . . . . . . . . 22 Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Dashboard issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Discussions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Publishing Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 LiveOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Viewing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Contents
Viewing Crystal reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Scheduling issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 User management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 AD and NT authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 LDAP authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Data source connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Developer issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 CSP and ASP development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 .NET development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Report Application Server (RAS) SDK development . . . . . . . . . . . . . . 36 Chapter 3 Crystal Reports 37
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Deployment issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Reporting off of Microsoft Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Working with reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Business Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Dynamic Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Formatting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Universes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 URL reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Developer issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Java Viewer SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 CR.NET SDK and Viewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Language version issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Java Reporting Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Platform-specific issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2 BusinessObjects XI Release Notes
Contents
Formatting and rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Relational databases and SQL statements . . . . . . . . . . . . . . . . . . . . . 54 Report functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Chapter 4 Web Intelligence 57
Web Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Editing reports in Interactive view format . . . . . . . . . . . . . . . . . . . . . . . 63 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Web Intelligence SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Universe and connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Web Intelligence servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Web Intelligence Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Checking connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Using the Check tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Check tool syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Check tool functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Chapter 5 OLAP Intelligence 73
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 General issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Data source connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Hyperion Essbase/IBM DB2 OLAP Enhanced Driver . . . . . . . . . . . . . 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Appendix A Business Objects Information Resources 81
Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Whats in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Where is the documentation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Contents
Send us your feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . . 83 How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Looking for the best deployment solution for your company? . . . . . . . . 84 Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
chapter
BusinessObjects XI 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, and be sure to visit the Business Objects support web site for additional notes and information that may become available following the release of this document. Note: The notes contained in this document represent only some of the known issues at the time of release. For the most up to date list of release notes, go to http://support.businessobjects.com/library/docfiles/cps10/ docs_en.asp.
What is BusinessObjects XI?

BusinessObjects XI brings together features from across the Business Objects product line to meet the diverse needs of users, from presentationquality reporting to in-depth analysis.
Business Objects information resources

For more information and assistance, see Business Objects Information Resources on page 81. This appendix describes the Business Objects documentation, customer support, training, and consulting services, with links to online resources. For acknowledgements of third party contributors and applications, in addition to related license information, please see http://www.businessobjects.com/ thirdparty.
BusinessObjects Enterprise
chapter
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. To perform a minimum installation of the Repository Migration Wizard and the Data Source Migration Wizard, use the Client installation in the setup program. Do not use the Custom installation to install only the Repository Migration Wizard, because certain dependent files will not be installed properly. All developer SDKs are installed by default. If you do not want to install the developer SDKs, perform a Custom installation and clear the selection of the SDKs in the feature tree list. If you custom installed selected components and later wanted to add additional components, the setup program will prompt you for the location of the BusinessObjects Enterprise XI CD. If you performed your Custom installation from a network image, you must use the network image (or a copy of it) as the source for adding new components. You cannot install the additional components from the CD. If you are performing a full .NET installation and the IIS option is disabled, ensure that: IIS is installed and enabled.
ASP .NET is installed and enabled.
If you installed the .NET components when ASP .NET did not exist on the machine, you need to install the .NET Framework again and repair it. To repair the .NET Framework: 1. Obtain the original installation source. For example, if you installed the .NET Framework from CD or DVD, insert the disk. Or, if you downloaded the .NET Framework, download again and choose to save to disk. If you installed from a network share, reconnect.
BusinessObjects Enterprise Installation
2.
From the command prompt, type the following command:

n:\<Installation Source>\dotnetfx.exe /t:%temp% / c:"msiexec.exe /fvecms %temp%\netfx.msi"
For example:
d:\dotNetFramework\dotnetfx.exe /t:%temp% / c:"msiexec.exe /fvecms %temp%\netfx.msi
If the .NET InfoView or Central Management Console are not working after a successful installation of the .NET WCA, ensure that the following settings are configured correctly: If you are using IIS 6 on Windows 2003, make sure that the permission for ASP .NET v1.1.4322 is set to Allowed under Web Service Extensions. Ensure that .aspx, .csp, .cwr, .rpt, and .resx application extensions have been mapped to aspnet_isapi.dll for the crystalreportviewers11 and businessobjects virtual directories. If you are performing a full .NET installation on Microsoft Windows 2000 with all the Windows updates applied, when you launch the .NET InfoView you receive the error 404: File not found. This error is caused by the Windows updates. Details of this issue can be found in the following Microsoft bulletin: http://www.microsoft.com/technet/security/bulletin/MS05-004.mspx There are two workarounds to this issue: 1. 2. Go to Internet Information Services (IIS) and click businessobjects Change the local path from
C:\Program Files\Business Obects\BusinessObjects Enterprise 11\Web Content\
ASP .NET is installed and enabled.
to
C:\Program Files\usinessObects\BusinessObjects Enterprise 11\Web Content
3. OR 1. 2.
Change the local path for crystalreportviewers11 as well. Go to Control Panel > Add/Remove Programs. Uninstall the .NET framework 1.1 hot fix.
BusinessObjects Enterprise Upgrading and migrating issues
Self-registration of some DLLs fails when the BusinessObjects Enterprise installation directory includes a semicolon. If you install to c:\;\ the install will fail. BusinessObjects Enterprise XI does not support installation to a directory that contains non-ASCII characters. This is due to the fact that some third party applications such as JDK, JRE, and Tomcat that run with BusinessObjects Enterprise do not support directories with non-ASCII characters. If you install Crystal Reports or OLAP Intelligence to a directory with nonASCII characters and then install BusinessObjects Enterprise, BusinessObjects Enterprise is forced to use the same directories that Crystal Reports and OLAP Intelligence are using. This causes unexpected behavior in JDK, JRE, and Tomcat. To avoid this issue, you must remove Crystal Reports and OLAP Intelligence and install them to a directory with completely ASCII characters and then install BusinessObjects Enterprise.
UNIX issues

Only Latin1 characters can be used in the install path, $TEMPDIR, and $TMPDIR for BusinessObjects Enterprise on a UNIX platform. When you install BusinessObjects Enterprise on Unix platforms, do not include white spaces or non-ASCII characters in the directory path
Upgrading and migrating issues
When migrating from a source environment that contains Active Directory users, the Central Configuration Manager (CCM) must run under a user account that has the Act as part of the operating system right. To choose which users have this right, set it through the Local Security Policy: 1. From the Start menu, select Programs>Administrative tools>Local Security Policy. Note: An alternative method is to type 'secpol.msc' in the "Run" command box. 2. 3. 4. Double-click Local Policies. Double-click User Rights Assignment. Double-click Act as part of the operating system.
10
5.
Add the account of the user who will run the CCM.
Note: For the change to take effect, you must log out of Windows.
Depending on the number of Crystal report instances in your source deployment, it could take some time to migrate everything to your new deployment. Be selective about the information you keep, especially if you are migrating report instances from a very large deployment. You can greatly reduce the migration time by removing instances from your source environment that you no longer need. If you are migrating a large number of report instances, you may want to consider a staged migration using the Import Wizard. When you upgrade from an earlier version of Crystal Enterprise, only one Page Server is upgraded. The BusinessObjects Enterprise XI Page Server uses child processes (like the Job Server) so you no longer need more than one Page Server per machine. When upgrading from a previous release, if the install program finds a Job Server installed, it automatically installs a Destination Job Server. When migrating from an existing Crystal Enterprise deployment, you may encounter errors if the source system includes any groups that have invalid third-party aliases. To resolve this issue, update any third-party authentication on the source system before migrating to BusinessObjects XI. If you are migrating from a deployment that contains mapped Windows NT groups, you must run the Central Configuration Manager under a domain account that can access the group and user information during migration. The account must belong to a domain that has appropriate trust relationships set up with the domains of the mapped groups. If you have more than one File Repository Server (FRS), only the first one is automatically upgraded. The other FRSs must be recreated after migration. To use a Crystal Enterprise web desktop (or ePortfolio) with a new deployment of BusinessObjects Enterprise XI, you must use an application server that is supported for the version of your web desktop (or ePortfolio). When you migrate from earlier versions of BusinessObjects Enterprise, registry settings are not migrated from the source deployment. In particular, any registry settings provided as part of patch releases will need to be set manually in the destination deployment after migration.
11
For all top level folders, access levels that are specified for users other than the default Administrators and the Everyone groups will not be migrated properly to BusinessObjects Enterprise XI from earlier versions of BusinessObjects Enterprise. For example, users with the "Full Control" access level on the Users or Groups folder will miss the rights to edit passwords, to modify rights securely, and to schedule on behalf of other users. To ensure the access levels in the destination deployment match the ones specified in the source deployment, update the access levels on all top level folders (e.g. Users, Groups, Servers, Server Groups, etc.) in the Central Management Console after migration. In Crystal Enterprise 10 and BusinessObjects Enterprise XI, the "Download files associated with the report" right is required to perform certain actions such as scheduling reports to destinations. This right is part of the Full Control role, but it is not part of any of the lesser roles. Because this right did not exist in Crystal Enterprise 8.5 or 9, users who had Schedule or View on Demand roles for a report object were able to schedule reports to destinations. After migrating to BusinessObjects Enterprise XI, those users will be unable to schedule reports to destinations unless they are granted the "Download files associated with the report" for the relevant report objects. This restriction may also cause recurring instances to fail if such instances were scheduled by users who without the download right.
After a database migration or an upgrade installation, the Central Configuration Manager may display a list of objects that failed to update (along with a reason for the failure). After you correct the problems that caused the failures, click the Update Objects button in the Central Configuration Manager. Due to a change in the rights aggregation model in BusinessObjects Enterprise XI, certain users may have different effective rights from those they had in their previous version of Crystal Enterprise. This situation will occur only if you have explicit rights set for a group that is a subgroup (indirectly or directly) of the Administrators or Everyone groups, and if these rights are set in one of the "top level" rights pages. If you set rights for a group in any of these locations, you may find that those groups are incorrectly denied the Delete and Edit rights for objects of the corresponding type after migration. For example, if you have a group "Managers" that is a subgroup of Administrators, and you have given them some explicit rights to all Calendar objects, you may find that Managers can no longer Delete or Edit any Calendar objects after
12
migration. To resolve this issue, set "Managers" to inherit rights from its parent groups in the Advanced rights page for the Managers groups (in the top level rights setting). At an SDK level, Default Objects are subject to this behavior, which are typically those objects with IDs less than 100. You can restore the rights to their previous values by turning on group inheritance for affected groups.
When you upgrade from Crystal Enterprise 9 to BusinessObjects Enterprise XI you may receive the error This application has failed to start because etc-1-0-12.dll was not found. Re-installing the application may fix this problem. If you receive this error or any unregistration errors during an upgrade, click Ignore and your new deployment will not be affected. This error occurs because MSI is attempting to unregister Crystal Enterprise 9 COM plug-in dlls
When you migrate from Crystal Enterprise 10 to BusinessObjects Enterprise XI, the migration may stop responding before it is complete. This occurs if the user performing the migration does not have access to verify the aliases of the NT users that are being migrated from the thirdparty authentication server. When you migrate from an existing BusinessObjects Enterprise deployment, you may encounter errors if the source system includes any groups that have invalid third-party aliases. To resolve this issue, update any third-party authentication on the source system before you migrate to BusinessObjects Enterprise XI.
Importing data from Crystal Enterprise to BusinessObjects Enterprise XI
When you import Crystal Enterprise 10 custom functions into BusinessObjects Enterprise XI, custom functions may not be imported properly if they are stored in the repository and you select the "Only import repository objects associated with the report option in the Import Wizard. To resolve the issue, select the "Import all repository objects" options when you import custom functions. After using the Import Wizard to import users, groups, and objects from Crystal Enterprise, certain security settings may be enforced differently than in the source deployment. This occurs because the rules for determining the effective rights for a user who belongs to multiple groups have changed in BusinessObjects Enterprise XI.
13
For example, if there are two groups, A and B, where B is a subgroup of A, and B has the "will inherit rights from its parent folders" security setting for a particular object, then users in group B will not inherit rights from group B, group A, or any other ancestor groups of B which are set on parent folders of the object. This differs from earlier versions where users who were members of group B would still inherit rights from group A, or any other parent groups of B that is still inheriting from parent folders.
Roles may be set differently after using the Import Wizard to import users, groups, and objects from Crystal Enterprise. In previous versions, when a role is set for a group, the group should not have inherited rights from its parent groups. In BusinessObjects Enterprise XI, you can choose (via the CMC) whether the group will inherit rights from the parent group. Because of this change, the effective rights may be different for users in a group that has been assigned a role. If you use database migration to transfer your repository from a previous version, these issues are remedied automatically by copying or otherwise manipulating the security settings where necessary to preserve fidelity.
Importing data from BusinessObjects Enterprise 6.x to BusinessObjects Enterprise XI
External BusinessObjects Enterprise 6.5 users who do not have an explicit user object in the repository will not be able to import their personal content (such as personal documents, categories, and Inbox documents) to BusinessObjects Enterprise XI. To resolve this issue, before you import data, create explicit user objects in BusinessObjects Enterprise 6.5 for all third-party users whose personal content you want to import. If you migrate from a BusinessObjects Enterprise 6.5 installation, Web Services user dictionary entries are not automatically migrated. You need to manually migrate your Web Services user dictionary entries. When importing from BusinessObjects Enterprise 6.x, universe dependency checking fails for Personal and Inbox documents. (Note: The dependency checking will work for corporate documents.) Use the "Import all universes and connection objects" option to make sure all required universes are imported.
14
When you import content from BusinessObjects Enterprise using the Import Wizard, you will be prompted to provide an explicit user name and password for all connections that are set to Use BusinessObjects username and password, and you may be prompted to enable single sign-on for these connections. If some connections are not modified, the user name and password may be set to @variable('BOUSER') and @variable('BOPASS') respectively. (Since BOPASS is no longer supported, you will encounter problems when connecting to the database servers while running Web Intelligence documents.) To modify the connection to use the correct user name and password, use the connections dialog box accessible from the Tools menu in the Designer.
When importing content from a BusinessObjects Enterprise 6.x system, you must run the Import Wizard on a machine with the same code page as the universes that you are importing. If an imported universe uses a different code page than the current system codepage, the internal universe data (such as object names and query strings, for example) may become corrupted. If you have universes that use different code pages, you can run the Import Wizard multiple times for each code page, importing a particular subset of universes during each import. When you import users from prior versions of BusinessObjects Enterprise using the Import Wizard, those users will become members in the Everyone group. In certain cases, the Everyone group may be granted (or denied) rights that the user was not granted (or denied) in the source deployment. When those rights are set on a parent group (rather than directly on a user) in the source, the user will gain all of the rights applied to the Everyone group after import, which may cause a change in the effective rights for that user. For example, Paul is a member of the "Associates" group in the source, and this group is denied access to the "Accounting" domain. After import to BusinessObjects Enterprise XI, the Associates group is still denied access to the Accounting domain (which is now represented as a top level folder). However, the Accounting folder will also inherit the default rights for users and groups which are set via Settings>Rights in the CMC. If these rights include "View" for everyone, Paul will be able to view the Accounting domain, since he is a member of the Everyone group, even though he was not able to view this domain in the source deployment. If Paul were specifically denied access to the domain in the source (rather than simply having his group denied access), he would not be able to see the domain after import because rights inheritance from Paul's groups will be disabled in this case.
15
When you import a user, if the user has both personal and Inbox content, then the users Inbox documents will be imported into the Favorites folder instead of the Inbox folder. (Personal content is still imported properly into the Favorites folder.). Users who encounter this problem can move documents from the Favorites folder into the Inbox. To prevent this scenario, you can run two separate imports, selecting to import personal content in one import, and Inbox documents in the other. During the first import, you can also select personal content and all of the other objects types that you want to import (such as universes, and categories). During the second import, select only Inbox content, and the users and groups again. To prevent duplicate objects from being created, you can run the imports in "Update" mode.
When you import delegated administrators (users that have been assigned the Supervisor role) from BusinessObjects Enterprise 6.x, the Import Wizard does not set the "Change password for users that the user owns" right for the object principals on the top level user folder and the top level user group folder. To resolve this issue after you have imported the delegated administrators from BusinessObjects Enterprise 6.x, grant them the "Change password for users that the user owns" right explicitly on the top level user folder and top level user group folder in the Central Management Console. When you import Web Intelligence documents that are based on universes with prompts from Enterprise 6.5 to BusinessObjects Enterprise XI , the imported documents do not have prompt information. That is, when the report is scheduled in BusinessObjects Enterprise XI, the prompt is not given and the instance fails. To work around this issue, after importing the document, you must open the document, refresh it, and save it.
Uninstalling
If you have previously installed BusinessObjects Enterprise XI Java components and you uninstall them and then reinstall, if Tomcat does not start, go to Control Panel>Add/Remove Programs and uninstall JDK 1.4.2_04 (or higher version) and then reinstall the Java components.
16
If you install multiple BusinessObjects XI features in the web tier, and then uninstall one of the products, you may not be able to view the contents of certain folders. For example, if you install InfoView with OLAP Intelligence, and then uninstall OLAP Intelligence, you may not be able to view the contents of the folders that contain your OLAP Intelligence documents. If this occurs, ask your system administrator to remove the documents.
Coexistence
Coexistence of BusinessObjects XI products
You can install more than one product from the BusinessObjects XI product suite simultaneously on the same machine. However, only the following installation orders are supported: BusinessObjects Enterprise first, followed by any one of the other version XI products. BusinessObjects Enterprise, Crystal Reports, and OLAP Intelligence can be installed in any order. For the complete suite: install BusinessObjects Enterprise, Crystal Reports, and OLAP Intelligence first; then install Enterprise Performance Management and LiveOffice.
BusinessObjects Enterprise XI and BusinessObjects Enterprise 6.5
For non-production use, you can install BusinessObjects Enterprise XI and Enterprise 6.5 on the same machine. However, you must install Enterprise 6.5 first. If you install the Tomcat application server with BusinessObjects Enterprise XI, you must also carefully select the port numbers used by Tomcat. Do not use the default Tomcat ports for BusinessObjects Enterprise XI, or the same port numbers than are used by Enterprise 6.5. For example, you may wish to choose the following values: Connection port: 9080
Shutdown port: 9005 Redirect port: 9443
Select these values either in the BusinessObjects Enterprise XI installer, or by editing the values in Tomcat's server.xml file.
17
BusinessObjects Enterprise Server management
Server management

A Java SDK application and the components that it needs to access cannot be separated by a firewall if the SOCKS protocol is the only means of traversing the firewall. If you want to be able to start or stop a server through the .NET Central Management Console on Windows 2000 Professional/Server, you must edit your configuration files: 1. Open the web.config file in a text editor. It is stored by default in: C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Web Content\. 2. 3. 4. Add the line:
<identity impersonate=true/>
Save the web.config file. Open the machine.config file in a text editor. It is stored by default in C:\WINDOWS\Microsoft.NET\Framework\ versionnumber\CONFIG\.
5.
In the processModel Attributes section of the file, change the value of the userName attribute to SYSTEM:
userName=SYSTEM
and change the value of the password attribute to AutoGenerate:

password=AutoGenerate
6.
Save the machine.config file.
In the Central Management Console, if you attempt to update a large third-party group or a large number of objects, you may encounter a timeout issue. To resolve this issue, you need to edit your configuration settings: 1. Open the web.config file in a text editor. It is stored under <installdir>\BusinessObjects Enterprise 11\Web Content.
18
BusinessObjects Enterprise Server management
2.
Change the following line

<httpRuntime maxRequestLength="20000"/>
to
<httpRuntime maxRequestLength="20000" executionTimeout="90"/>
This version provides a 90-second timeout; choose an appropriate number to allow sufficient time for processing. 3. If you need to update a large third-party group, change the scripttimeout value for the CSP in the registry, under
HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.0\Web Component Adapter\Components\csp.
4. 5.
Save the web.config file. Restart IIS.
If you start a WebLogic application server and encounter a Failed to preload jsfadmin message on startup message, ignore the message. The deployment will start normally. To use the Tomcat Web Server Administration Tools for the Tomcat server, perform the following steps: 1. 2. Open <installdir>\Business
Objects\tomcat\conf\tomcat-users.xml.
Add the following line:

<user username="admin" password="password" roles="admin,manager"/>
This gives you an administrator called admin which you can use to log onto the administration utility.
On Microsoft Windows 2003, Tomcat will fail to start if it is not running under an Administrator account or as a user with full control rights.
Central Management Server (CMS)
On Windows 2000, the Central Management Server may stop working if you try to configure the auditing database before you configure the database client.
19
BusinessObjects Enterprise Web and Windows applications
Processing servers (Page, Job, Cache)
The Page Server is not supported on Windows operating systems that run with both the /3G and /PAE boot flags. You can use these flags individually, but if you run with both flags, you may encounter problems running the Page Server. Do not install more than one Page Server per machine. The BusinessObjects Enterprise XI Page Server uses child processes (like the Job Server) so you no longer need more than one Page Server per machine. If a Java program object fails to run with an error message stating that the Program Job Server was unable to locate the JVM, ensure that all registry settings under "HKLM\JavaSoft\Java Runtime Environment" are set correctly on the Program Job Server machine. Setting the JAVA_HOME system environment variable to the correct Java directory will also allow the Program Job Server to locate the JVM. If you are using Essbase, make sure that your version of the essbhapi.dll file is consistent with the version being used by BusinessObjects Enterprise. By default, BusinessObjects Enterprise installs version 7 of the essbhapi.dll file. If you have Essbase client v6.5 installed, update essbhapi.dll to be the same as essbhapi_65.dll.
Report Application Server (RAS)
If you select the Use custom database login information specified here option in the CMC, the Report Application Server requires the correct database credentials (including a valid password) to be set in the CMCs custom database settings.
Web and Windows applications

Business Views
Creating a SQL Expression field based on a command table in a Data Foundation is not supported.
20
If the Data Foundation used by a Business View contains an active filter which consists of a constant formula and a parameter, then you cannot use the Business View to create a list of values. To work around the problem, make sure the active filter is not applied. When you create a parameter for a Data Foundation, if you add Prompt Group Text and then select or create a list of values, the Prompt Group Text will be removed from the Parameter dialog box. In order for a user to publish a report that contains a dynamic prompt and cascading list of values, the user must have the Edit and Set Security rights in the Dynamic and Cascading Prompts folder as well as Full Control rights for the target InfoView folder in the Central Management Console. You cannot save changes to the dynamic prompt values displayed in the Edit Parameter dialog box. The options displayed in this dialog box are read-only. You cannot create a cascading list of values that is based on a Business View which in turn depends on another list of values (for example a dynamic prompt used in the Data Foundation or Business Element). If this list of values is used for a parameter, then the parameter prompting will not work. In the Business View Manager, if a List of Values (LOV) has dependent prompt groups, users cannot edit LOV fields because the LOV editor disables this option. Creating a List of Values based on a Business View that depends on another List of Values is not supported. For example, if a Dynamic and Cascading Prompt parameter is used in the Data Foundation or Business Element. If this List of Values is used for a parameter, then the parameter prompt will fail.
When a parameterized stored procedure or command table is used in a Crystal report, the parameter prompts may not appear when the report is refreshed. This is possible in the following cases: A stored procedure or command table with parameters and a normal table are included in a Data Foundation. A join is created from the stored procedure to the normal table. The join is enforced both ways (or enforced from). A report is then created using a Business View based on this Data Foundation using only fields from the normal table.
21
In a Data Foundation, a normal table and a stored procedure are joined. Then that stored procedure is joined to another normal table. A Crystal report is created using fields from both normal tables but not the stored procedure.
To ensure that the parameter prompts appear in Crystal Reports, either include a field from the stored procedure in the report or create a filter with a field from the stored procedure and assign the row restriction to the Everyone group. For example, StoredProc.Field is any value
When you launch the Business View Migration Wizard, the User Interface appears correctly but the wizard does not work. This occurs because the wizard gets installed to the incorrect location. It is installed to Business Objects\BusinessObjects Enterprise 11\win32_x86 but it should be installed to Common Files\Business Objects\3.0\bin. To work around this issue, copy the following files from Business Objects\BusinessObjects Enterprise 11\win32_x86 to Common Files\Business Objects\3.0\bin
BVMigrationWiz.exe BVMigrationWiz.pdf BVMigrationWiz_res_en.dll
Central Management Console (CMC)

In the Central Management Console, using the Schedule For option for thousands of users at once is not recommended. If you have been granted the right to securely modify rights that control user access to objects, note that when you set rights for other users, you will be able to select only those rights that you have been granted on a given object. When you assign access levels for other users, you can assign them only a subset of the rights that have been granted to you. In the Central Management Console, you cannot set custom database logon information for a report that is based on a universe. If you use Internet Explorer, you cannot use a mousescroll to scroll through the list of values in the Java Central Management Console. Running the Central Management Console in Internet Explorer is recommended over other browsers.
22
If you installed the Java or .NET Web Component Adapter (WCA), ensure that the Set default viewer URL setting in the Central Management Console is set to the viewer that you want. If you installed both Java and .NET versions of the WCA, the URL will be set by default to the Java version of the HTML viewer. If you custom installed Java or .NET WCA, the URL will be empty. To set the valid URL: 1. 2. 3. Log onto the Central Management Console as an Administrator. Navigate to Home>Objects>Object Settings. Change the Set default viewer URL setting. For Java:
http://machinename:port/businessobjects/enterprise11/ desktoplaunch/opendoc/openDocument.jsp? sIDType=CUID&iDocID=%SI_CUID%
For .NET:
http://machinename/businessobjects/enterprise11/ InfoView/scripts/opendocument.aspx? sIDType=CUID&iDocID=%SI_CUID%
- The account that Internet Information Services (IIS) is configured to run its worker processes under must not be a member of a mapped Windows NT or Windows Active Directory (AD) group. If this account is added to a mapped group and IIS is not configured for Single Sign-on (Windows NT and/or Windows AD), then all users will be able to log on to BusinessObjects Enterprise XI under this account using Windows NT and/or WindowsAD authentication with a blank username and password.
Netscape issues
When using the CMC in Netscape to add a new object, the object path will be displayed incorrectly if it contains globalization characters. This issue does not occur when adding folders, users, events, and so on. This is a known Netscape issue.
Import Wizard
For information about the Import Wizard, see Upgrading and migrating issues on page 10.
23
InfoView

To assign categories to OLAP Intelligence reports, use the Publishing Wizard or the Central Management Console. You cannot assign categories to OLAP Intelligence reports in InfoView. If youre using IBM Websphere Application Server 5, you need to increase the runtime JSP compilers method size maximum from 32K (the default value) to 64K. To change the default in the WebSphere Application Server 5 Administration Console: 1. 2. Go to Servers>Application Servers>yourserver>Process Definition>Java Virtual Machine>Custom Properties. Add a new property:
com.sun.tools.javac.main.largebranch
and set its value to true. 3. 4. Apply your changes to the master configuration. Restart the server.
Note: The Java SDK 1.3 prescribes handling 64K methods. Note that you do not need to change settings for the JspBatchCompiler, because it already conforms by default to the Java SDK 1.3 specification. For more information, read the IBM technote. Note that this technote provides instructions for version 4 only. To deploy InfoView on an SAP application server, you need to set the following system property in a JSP file (or set it globally on the SAP application server):
System.setProperty("org.xml.sax.driver", "org.apache.xerces.parsers.SAXParser");
If youre using Netscape7.0.2 with the Java InfoView, Microsoft documents are opened in a standalone viewer, even if you set your documents to be viewed in the workspace. If you deployed Business Objects Enterprise XI web application on WebLogic 7.0 With Sun Java SDK 1.3.1, you may encounter out of memory errors. Try one or more of the following steps: Adjust the JVM permanent generation size by specifying:
-XX:PermSize=<value> and -XX:MaxPermSize=<value>
24
Adjust the JVM heap size by specifying -Xms<size> and -Xmx<size>. Upgrade the Java SDK to version 1.4.2.
For full procedures, refer to the Java SDK User Guide and the WebLogic Web Application Server User Guide. If you are creating a Web Intelligence document in the Java InfoView deployed on WebSphere Application Server 5.0.2, the Java Applets may fail to load. This is because WebSphere Application Server creates duplicates manifest files for signed application .jar files. To resolve this issue, apply WebSphere patch PQ76313 from the IBM web site: http:// www-1.ibm.com/support/docview.wss?uid=swg24006190.
Dashboard issues
When you add a report to dashboard, if you select "last instance", ensure that the report has instances. Similarly, if you select "parts viewer", the report must have report parts. Otherwise, you will receive an error message: "An error has occurred: Sorry, you do not have the right to execute this action. If you require this right, please see your system administrator." If you are using the dashboard in Netscape 7.02, and a pane appears blank after you have defined its content, open the pane in new window or save your changes reopen the dashboard.
Discussions
When an object package is selected, the discussions panel feature will be disabled. Discussions are not permitted on object packages.
Publishing Wizard
When you publish a report that contains a subreport, the file name of the subreport must not exceed 127 characters.
25
LiveOffice
After creating a new Report View from a report that has drill-down fields, there are no menu options to allow you to drill down in the Report View. This occurs if the Report View was created using the Report Viewer or if the Report View only contains detail level fields. When you refresh a Report View that has been formatted using Microsoft Office, the formatting is lost. This occurs because the Keep user format when refreshing check box is not selected. To select this check box: 1. 2. 3. Right-click any field in the Report View. Click View and then click Options. Select the Keep user format when refreshing check box.
Clicking the Default button on the Options dialog box does not clear the Remove Context Menu on Toolbar option. This option is clear by default so should be cleared when the Default button is clicked. After Live Office has been installed and you open a Microsoft Office application, you do not see the Live Office toolbar. This occurs if you are not the one who installed Live Office on that machine. To make the toolbar visible, search for the crystal_addin_framework.dll file in the Com Add-ins option of the Microsoft Office application and add it to the installation. When a field is deleted from a disconnected Report View that is based off of a Business View, the following error message appears:
Unable to remove field from Report View. Missing parameter values.
This message appears if a filter that uses a parameter is applied to a user who is currently logged onto BusinessObjects Enterprise. This filter was not applied to the user when the Report View was created. If you refresh the Report View before you try to delete the field, you are prompted for the parameter information and the field can be deleted.
When you drill down on a Report View and then drill up, the user formatting may appear to be lost because the view has refreshed. The Report View has the option Keep user format when refreshing turned on and has been formatted using Microsoft Office.
26
BusinessObjects Enterprise Viewing issues
Field selection
When you view a Report Views data source by going to View > Data Source, the Report View Expert appears as expected. When you click the OK button to close the Report View Expert, the dialog box closes and the Report View data is refreshed. To prevent the Report View data from being refreshed, click the Cancel button instead of the OK button. When you drill down to the lowest level of a Report View, the Drill Up option is not available. Only the Back to Original option is available. This occurs because the lowest level of data is at the detail level not the group level and there is no path to drill back up to. When drilling back up to the top level of a view that was created from a report which contains a summary field and grand total field, the grand total field may also be displayed at the top level. This occurs because RAS brings back all of the fields in that level. Use the Back to Original option to remove this grand total field.
Loading from BusinessObjects Enterprise
When you click Refresh All Data to refresh a Report View in Microsoft Office, nothing happens. Nothing happens because the Report View is not connected. If you click the Refresh button to connect the View, the Refresh All Data option will work correctly. When you open a saved View from BusinessObjects Enterprise, the drilldown menu is unavailable. To activate the drill-down menu, refresh the View by clicking the Refresh button.
Parameters
When using one report connection to create multiple Report Views, if parameter values are changed for one View, the parameter values are also changed for other Views created using the same report connection. This occurs when all Views are refreshed.
Viewing issues
The Java applet viewer does not support dynamic prompts that use multiple cascading lists of values. For example, a dynamic prompt with multiple levels for country, region, and city will prompt you only for the city. Reports with multiple-level dynamic prompts can be viewed properly in the ActiveX viewer.
27
BusinessObjects Enterprise Scheduling issues
- When using Netscape and viewing a Web Intelligence document in PDF format, the error This operation is not allowed appears. If you click the OK button, you are able to view the document correctly.
Viewing Crystal reports
You can no longer install the Crystal Reports Offline Viewer from the launchpad. If you need to install the Crystal Reports Offline Viewer, or if you want to deliver the Offline Viewer to your users, the installation program is stored by default in the following location:
C:\Program Files\Common Files\Business Objects\3.0\ crystalreportviewers11\Offline\en\cvwsetup.exe
Scheduling issues
When you schedule a cascading list of values for a dynamic prompt, BusinessObjects Enterprise keeps only the latest instance. If you schedule a report based on a universe, any user with rights to view the scheduled report may be able to see the saved data. The universes user security settings are not enforced on the saved data of a scheduled report. The Enterprise administrator must ensure that scheduled reports that are based on a universe can be viewed only by users who have the necessary rights to see the saved data.
In InfoView, if you schedule a component Web Intelligence document (in an object package) to Excel or PDF format, the Java InfoView may ignore the export format that you select. It will use the format set when the document was added via the Central Management Console.
User management

If you have purchased named user licenses, you cannot log on using the Guest account. (By default, this account is set as concurrent.) If you are using Tomcat or WebLogic and you notice that concurrent license sessions are accumulating, perform the following steps:
28
BusinessObjects Enterprise User management
1.
Add the following lines to the web.xml file:

<listener> <listener-class>com.businessobjects.sdk.ceutils. SessionCleanupListener</listener-class> </listener>
This listener will explicitly log off the session objects when they are invalidated. 2. Execute System.gc(); explicitly.
You can adjust the "User/group inherits from parent group" and the "User/ group inherits from parents folders" settings for other users only if you have the corresponding settings turned on for yourself. If the administrator can modify these flags, it may be possible for other users to enhance rights on an object beyond what the delegated administrator has been granted.
Single Sign-On

Single Sign-On to the database using Windows AD authentication is not supported for the ActiveX viewer in the CMC. When viewing reports using Kerberos Single Sign-On to the database with the Crystal Reports Page Server, if you restart the Central Management Server, then users may need to log off and log on again to BusinessObjects Enterprise in order to continue viewing reports. This also applies to viewing reports using Kerberos Single Sign-On to the database with the Web Intelligence or the Report Application Server. When you map groups from externally trusted domains using the Windows NT Authentication provider, you may need to add the DNS suffixes for these domains to the Windows DNS configuration of the Central Management Server machines. If you do not add the DNS suffixes, you may encounter a timeout while attempting to map groups from these domains. To ensure Kerberos Single Sign-On is used when accessing database servers, connections must be configured to use only TCP/IP.
29
BusinessObjects Enterprise User management
When viewing Crystal Reports in InfoView using Single Sign-On to database, generic error messages will be displayed when the associated security context becomes unavailable during viewing. This issue may occur when you restart a Central Management Server. If you encounter this issue, the BusinessObjects logon session will still be valid, but the associated Kerberos security context will no longer be valid. To resolve the issue, you must log off of InfoView and log on again using the Windows AD authentication provider. To enable or disable SiteMinder single sign-on in the Central Management Console, you need to change the following registry key:
EnableSiteMinderSingleSignOn (DWORD, default value = 0x00000001) in HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.0\Enterprise\Admin Plugins\CrystalEnterprise.CMSAdmin.
To enable single sign-on set the value to a non-zero value; to disable it, set the value to zero.
AD and NT authentication
If Active Directory administration credentials are being changed from one account from one tree to an account in a different tree from the same Active Directory forest, you may be unable to log on to BusinessObjects Enterprise (with Windows AD authentication) for a brief period of time. If local users with blank passwords cannot log on to BusinessObjects Enterprise using NT authentication, you may need to change default settings in the Local Security Policy. 1. From the Start menu, select Programs>Administrative tools>Local Security Policy. Note: An alternative method is to type 'secpol.msc' in the "Run" command box. 2. 3. 4. Double-click Local Policies. Double-click Security Options. Double-click Accounts: Limit local account use of blank password to console logon only, then click Disabled.
Note: For more information about this setting, see the Microsoft Windows Help.
30
BusinessObjects Enterprise Data source connectivity
The account that IIS uses to run its worker processes must not be a member of a mapped Windows NT or Windows AD group. If you add this account to a mapped group, and if IIS is not configured for Single SignOn, then all users will be able to log on to BusinessObjects Enterprise under this account when logging on using Windows NT or AD authentication with a blank user name and password. To ensure that the Report Servers always use the expected user accounts to log onto the database, make sure that the servers do not have default access to the database. The account that the Report Server is running under should not be an authorized user of the database. Also, you should not allow logging onto the database with an empty password. If the Active Directory database on a Windows 2003 domain controller is corrupted, the SETSPN command used to set the Service Principal Name for the database server and the service account used by BusinessObjects Enterprise may fail without displaying any error messages. If the SPNs for the service accounts of the database servers are not configured properly in Active Directory, Kerberos Single Sign-On to the database will fail. System event logs will contain the error "KDC_ERR_S_PRINCIPAL_UNKNOWN" and list the SPN that could not be found. Check these logs to ensure that the SPN was successfully set in Active Directory after running the SETSPN command.
LDAP authentication
When logging on to BusinessObjects Enterprise XI using the JAVA SDKs LDAP provider (in particular, when logging on to the Java InfoView via LDAP), specified referral credentials are not used when following referrals while looking up users. For LDAP authentication to succeed, you need to enable anonymous logon for all LDAP servers specified in referrals.
Data source connectivity
SQL Server 7 is supported only for small and medium-sized deployments. If your deployment requires CMS clustering, more than 10000 objects, or more than 50 concurrent users, then we recommend upgrading to SQL Server 2000 before installing BusinessObjects Enterprise XI.
31
BusinessObjects Enterprise Documentation
Documentation

The documentation refers to all BusinessObjects XI components as version 11 components. To improve installation performance, the Web Intelligence PDF guides are no longer installed on your local machine. These guides are available with your product distribution, or you can access them online at http:// support.businessobjects.com/documentation/. The BusinessObjects Enterprise documentation incorrectly refers to sample auditing reports that are not included in this release. In the Installing BusinessObjects Enterprise on Windows chapter, in the Deploying the Java version of InfoView section, step 3 of the procedure for deploying InfoView provides an incorrect location for adding context paths. Instead of adding the new lines above

add them above the line

</Host>
near the end of the server.xml file.
Page 511 of the BusinessObjects Enterprise Administrators Guide refers to an Express version of BusinessObjects Enterprise. There is no Express version of BusinessObjects Enterprise XI. The Configuring servers for SSL section of the BusinessObjects Enterprise Administrators Guide requires some clarification: Note that the CA certificate (cacert.der) and its corresponding private key (cakey.pem) need to be generated only once per deployment. All machines in the same deployment must share the same CA certificates. All other certificates need to be signed by the private key of any of the CA certificates. You need to create certificates and keys for all machines in the deployment, including machines running thick client components such as Crystal Reports. For these client machines, use the sslconfig command line tool to do the configuration. The certificate and key files generated using step 6 and 8 are not placed in the "new_certs_dir" location specified in the ssl.cnf file. They are placed under the current working folder instead.
32
BusinessObjects Enterprise Developer issues
For the section re: configuring the J2EE web application server, note that the code uses sample file names and paths. The following table shows the descriptions that correspond to these examples: Sample
DcertDir=d:\ssl DtrustedCert=cacert.der
Description The directory to store all the certificates and keys. Trusted certificate file. If specifying more than one, separate with semicolons. Certificate used by the SDK. Private key of the SDK certificate. The file that stores the passphrase for the private key.
DsslCert=clientcert.der DsslKey=client.key Dpassphrase=passphrase.txt
The sample serial number used for creating and signing certificates should be an even number of digits. (The number should be in hexidecimal format, such as 11111111111111111111111111111111.) For maximum security, all private keys should be protected and should not be transferred through unsecured communication channels.
Developer issues
There is no supported public SDK for the dynamic prompt feature in Crystal Reports XI or BusinessObjects Enterprise XI.
Web Services

Unified Web Services does not support dynamic prompts and cascading lists of values for Crystal report objects. Also, the Unified Web Services Report Engine does not support scheduled lists of values. The server dictionary implementation has been changed in version XI. You must migrate your server dictionary from versions 6.5 and 10 to version XI. You cannot currently use the same getDocumentInformation call to update the callback script and refresh a Web Intelligence document. You must perform two separate getDocumentInformation calls.
33
Web farms are not supported for this release of the Unified Web services The WAR file assembly script shipped with BusinessObjects Enterprise Web Services can only be used on a Windows platform. In a UNIX or Linux environment, you must write your own version of the assembly script.
CSP and ASP development
To use .csp scripts with Business Objects Enterprise XI, you need to perform the following steps depending on how you use CSP (Crystal Server Pages). To deploy your custom CSP application to a virtual directory other than the <installdir>\BusinessObjects Enterprise 11\Web Content\ directory created by the installation program, complete the following steps: 1. Copy the file global.asax and web.config files from
<installdir>\BusinessObjects Enterprise 11\Web Content\ to the directory of your application.
2.
Create a subdirectory bin under your application, and copy the file <installdir>\BusinessObjects Enterprise 11\Web Content\bin\WCA_Enterprise.dll into the new bin subdirectory. Ensure that the extension mapping for your virtual directory is defined the same way as the "businessobjects" application in IIS Manager. Merge your web.config file with the web.config file stored by default in C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Web Content.
3.
If you are using your own web application, then you need to: 1.
34
2.
Modify your global.asax.cs to include:

using BusinessObjects.Enterprise.WebComponentAdapter; protected void Session_End(Object sender, EventArgs e) { HttpSessionState session = this.Session; WCAHandler.sessionEnd(session); } protected void Application_End(Object sender, EventArgs e) { WCAHandler.applicationEnd(); }
Your application is now connected to the Web Component Adapters event handler. 3. Ensure that the extension mapping for your virtual directory is defined the same way as the "businessobjects" application in IIS Manager.
For more information about configuring your existing CSP for use with BusinessObjects Enterprise XI, contact our Technical Support site.
.NET development
In the COM and Java RAS SDK, you can save a report by calling ReportClientDocument.SaveAs(RptName,InfoObject, options), where InfoObject was the folder object from a InfoStore.Query() statement. Using InfoObject as a folder object in ReportClientDocument.SaveAs is not supported in the .NET SDK. You can, however, cast the InfoObject to a PluginInterface, cast the Interface as ISInfoObject, set ISInfoObject as a System.Object object, then pass it into the SaveAs call. For example:
using PluginInterface = CrystalDecisions.Enterprise.PluginInterface; using ISInfoObject = CrystalDecisions.Enterprise.ISInfoObject; System.Object docObject = null; System.Object infoObj = null; infoObj = InfoStore.Query(myQueryStringForFolder);
35
PluginInterface pluginObj = ((IInfoObject)infoObj).PluginInterface; ISInfoObject infoObjectInterface = (ISInfoObject) pluginObj.Interface; docObject = infoObjectInterface; myReportClientDocument.SaveAs(docName, ref docObject, options);
The following two methods have misleading names. They do the opposite of what the names suggest. Therefore, it is important to note the following:
DatabaseLogonUtility.ConvertReportLogonsToTableLogonInf os(reportLogons,tableLogonInfos)
This method converts TableLogonInfos to ReportLogons.

DatabaseLogonUtility.ConvertTableLogonInfosToReportLogo ns(tableLogonInfos,reportLogons)
This method converts ReportLogons to TableLogonInfos.
Report Application Server (RAS) SDK development
When you make changes to the FieldFormat Objects through the RAS SDK, you may need to set the EnableSystemDefault property of the CommonFieldFormat Object to false for the changes to occur properly. Note: The FieldFormat Objects include BooleanFormat, CommonFormat, DateFormat, DateTimeFormat, NumericFormat, StringFormat, and TimeFormat.
36
Crystal Reports
chapter
Crystal Reports 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). On Windows 2000, you must install the .NET framework before you install the Report Application Server. While installing, if you receive a Java Update Failed message, you can install the Sun Java Runtime Environment (JRE) manually. You can install it from Suns web site, or install the version shipped with Crystal Reports in the \win32\redist\en folder. If you are using the .NET framework on Windows 2000, an embedded installation does not check to make sure that ASP.NET is configured to work with IIS. If ASP.NET is not configured properly, you cannot run VB.NET and C-Sharp.NET samples. To configure ASP.NET for IIS, run aspnet_regiis -i (located in c:\windows\microsoft.net\framework\v1.1.4322\ by default). The JRE is not uninstalled properly. You can install an updated JRE over your existing version. You may need to configure your Java Web Applications server to align to the new version.
Deployment issues
If you create a Setup and Deployment project inside a .NET 2002 Windows or Web solution and use crystal11_net_embeddedreporting.msm from the .NET dependency detection tool as a result of your Add Project Output | Add Primary output action, you may encounter these messages in the Output Window:
This setup does not contain the .NET Framework which must be installed on the target machine by running dotnetfx.exe before this setup will install. You can find dotnetfx.exe on the Visual Studio .NET Windows Components Update media. Dotnetfx.exe can be redistributed with your setup. Unable to import merge module crystal11_net_embeddedreporting
38
Crystal Reports Data access
The first message is a warning; the second is a build failure message. To successfully build the setup project, you need to delete the entire Setup project, create a new one, and then add the primary output again. Then add the Crystal11_NET_EmbeddedReporting.msm (from C:\Program Files\Common Files\Merge Modules, by default) to the setup project. After adding an appropriate keycode to this merge module, you should be able to build the project. To avoid encountering this problem when you build a setup and deployment project inside a .NET 2002 solution that involves Crystal Reports 11 components, you should exclude any auto-detected merge module from Crystal Reports 11 and add it manually from the local drive location indicated above.
Due to an issue in the initial release of Crystal Reports 9, when Crystal Reports 9 and 11 are installed on the same computer, you cannot use Crystal Reports 9 to connect to a Crystal Enterprise (CE) 9 server. You will receive an error message saying that you cannot connect to an older version of the CMS. For Hot Fixes or Service Packs that address this issue, please refer to Knowledge Base Article ID: c2014523 on our Technical Support site.
Data access
The Lotus Notes data driver is no longer supported. It is recommended that you use the ODBC driver in its place; the Lotus Notes ODBC driver is supported. Note that the Lotus Notes data driver is still included with the product distribution of Crystal Reports 11, but will removed in a future release. If you change your data source and you have dynamic prompts, you must use Set Location to configure the data sources for use with the prompts lists of values. To report off of a universe from Crystal Reports successfully, when designing the universe in the Designer, make sure the Tables are added with fully qualified names. This will enforce SQL generation with fully qualified table names. If you are using a native Oracle connection to create a report based on a universe, and you want to use a constant date in the command, you need to edit the Oracle.prm file (located by default in C:\\Program
Files\Business Objects\BusinessObjects Enterprise 11\win32_x86\dataAccess\ConnectionServer\ oracle). Change the USER_INPUT_DATE_FORMAT parameter to:
39
<Parameter Name="USER_INPUT_DATE_FORMAT">'YYYY/MM/DD HH:MM:SS'</Parameter>
Change the DATABASE_DATE_FORMAT parameter to:

<Parameter Name="DATABASE_DATE_FORMAT">YYYY/MM/DD HH24:MI:SS</Parameter>
If you connect to an Essbase OLAP Server, you need to have the proper version of the active Essbhapi.dll file. From an installation of Crystal Reports 11, Essbhapi.dll can use the Essbase 7.0 client to connect to an Essbase 7.0 server. If you want to connect to an Essbase 6.5.4 Server and you have the Essbase 6.5.4 client on your machine, you must change the name of the Essbhapi_65.dll file to Essbhapi.dll. If you connect to an IBM DB2 OLAP Server, you need to have the proper version of the active db2hapi.dll file. From an installation of Crystal Reports 11, db2hapi.dll can use the DB2 - 8.1 client to connect to a DB2 - 8.1 Server. If you want to connect to a DB2 - 7.1.7 Server and you have the DB2 7.1.7 client on your machine, you must change the name of db2hapi_71.dll to db2hapi.dll. The following generic database drivers are thread-safe:
crdb_odbc.dll (ODBC) crdb_jdbc.dll (JDBC) crdb_ado.dll (OLE DB)
Note that ODBC connections to the following database types assume that the ODBC database driver is also thread-safe and, therefore, operate in a multi-threaded manner:
Microsoft SQL Server Oracle DB2 Teradata Sybase
Also note that it is assumed that the database drivers used with JDBC and OLE DB are always thread-safe and, therefore, always operate in a multi-threaded manner. The following native database drivers are thread-safe:
crdb_ado_plus.dll (ADO.NET data provider) crdb_com.dll (COM data provider crdb_db2cli.dll (DB2 Unicode) crdb_javabean (Javabean data provider)
40
crdb_xml (XML) crdb_olap.dll (OLAP) crdb_oracle.dll (Oracle) crdb_p2ssby10.dll (Sybase)
The Crystal Reports Online Help states that the DB2 Unicode Driver is available for download. However, this driver is included with the current version of Crystal Reportsdownload is not necessary. If your report contains a list of values based on a native DB2 connection, Crystal Reports may stop responding. Upgrading your DB2 client to version 8.2 will fix this problem. Single-Sign-On (SSO) is not supported in DB2 due to limitations in the client as noted by IBM. IBM expects to make a new client available in the future; at that time Crystal Reports will be patched to support SSO in DB2, and the required patches will be made available. When, in the Field Explorer, you select an ODBC data source through the DataDirect Oracle ODBC driver, Crystal Reports cannot expand a table whose name includes non-English characters. You can solve this problem by setting you database language to a unicode character set, such as UTF-8, in the Oracle clients NLS_LANG setting. The sample database installed with Crystal Reports (xtreme.mdb) is installed to appropriately named directories for all languages, regardless of the language you chose during install. An ODBC DSN is created to point to this database, but it is created only for the language that you chose during the install process. You must manually create DSNs for other languages, if you want to use all the languages versions of the sample database. For multiple Universe commands to work in the same report (be it a cross-data source join, or a subreport), you must name your queries differently for the parameters to work. Names are specified in the Query Panel when you design your Query. For a report with parameters that is created in the Query Panel (and, therefore, is based on a Universe), if you change the definition of the underlining object that the prompt is based, the existing report may not work. For example, if you create a prompt filter based on a Universe object with a numeric type, and then you use this parameter in a formula, changing the prompt filter to be based on string type may make the formula fail. Also, if the Universe changes in a way that results in the order of the prompts being changed, the report may not run. In this version of Crystal Reports, UFLs that return character strings are not supported on UNIX.
41
Reporting off of Microsoft Exchange

If you use Microsoft Exchange Admin, reporting off an unpatched Microsoft Office 2002 is not supported. This is a known Microsoft issue that can be resolved by installing Microsoft Office 2002 SP-1 or later. If you want to create reports based on the Exchange server in Microsoft Outlook 2003, ensure that Cached Exchange Mode is not selected in the Mail setup. If you want to create a report based on an Exchange connection, you must log in as the same user running the Exchange processes. Multiple user profiles are not supported. Because Attendees fields are returned to Crystal Reports as strings, you cant expand them. To expand Attendees fields in reports based on calendars, open the meeting in Microsoft Outlook, expand the distribution list to replace the distribution list with its members, and then save the meeting. The distribution list will be expanded in your report. You cannot create a report based on a distribution list in the Contacts folder of a Personal mailbox. MAPI treats the Mailbox Contacts folder as a single database table; so if you report on it, an individual record is returned for each contact/distribution list. Whereas the Address Book Contacts folder is treated as a folder containing distribution lists. Note: If you choose the Address Book Contacts folder to report on, it is expanded like a distribution list.
Instances that you delete from recurring appointments will still appear in your report. MAPI does not expose information that allows Crystal Reports to exclude deleted instances of a recurring appointment. You cannot view a report in Visual Studio .NET 2003 if that report has been created from Microsoft Exchange data under these circumstances: The remember password option in Outlook is unchecked The user is logged onto a machine with a user account from a domain that is different from the domain in which the MS Exchange Server resides. The Group Membership, Direct Report To, and Manager fields from an Outlook Address Book do not appear in the Field Explorer. The information for these fields is stored in a separate table for each record and, therefore, cannot be accessed by Crystal Reports as part of the selected table.
42
Crystal Reports Working with reports
If you disable the Reminder Minutes Before Start for a meeting in Outlook, Outlook still stores the information. Therefore, when you use this value in a report, it always shows a value. When reporting off Outlook, and the report is based on Tasks, the field Actual Work may not show the correct value. The reason that the Actual Work and Total Work fields may show a different value than expected is because of how Outlook calculates the time worked. It stores time in minutes, but it calculates it using 8 hours a day and 5 days a week. If you enter a task into Outlook that takes one week, Outlook stores it in Total Work as 2400 minutes based on the equation 60 (minutes/hour) * 8 (hours/day) * 5 (days/week).
Working with reports
Any Crystal Reports hyperlink that contains a URI other than http:, https:, mailto:, ftp:, or news: is removed by Crystal Reports. This is done so that malicious scripts cannot be added to a hyperlink. If you want to override this feature and allow scripts to be run through hyperlinks, you can create this registry subkey:
\HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11.0\Crystal Reports\FormatOptions
Then, make this entry as a new String Value:

DisableScriptsInHyperlinks
Finally, set its value to Yes or No.
If you create a report from a Business View, you must ensure that the Business Element does not have a space in its name. If a space exists, any filter that was defined in the Business Element will produce an error when you try to use it in the Record Selection Formula Editor dialog box in Crystal Reports. When you create a report based on a note with an Outlook or an Exchange data source connection, more fields appear in the Field Explorer than you would expect (such as: BCC, CC, CC To Me). If a record selection formula filters out all of the records in a hierarchical group, the group and its related hierarchies are unknown to the program, and your hierarchical sort will be incorrect (as will be the results from the Hierarchy functions that are available in the Formula Workshop). The hierarchical ordering of the group footer is preserved only in the page-based export formats.
43
When you select the option to use a formula as your group sort order (that is, when you specify a conditional group sort order), you cannot select options from the The section will be printed list (the option is grayed out). To work around this, clear the Use a Formula as Group Sort Order option, select a section printing option, and then reselect the conditional option. (If you have already specified the conditional formula that you want to use, you will not lose it while carrying out this work around.)
Business Views

When working with a report based on a Business View, OLEDB commands in the repository that contain duplicate columns names may return incorrect data. The parameters of a stored procedure or a command table will not be prompted when refreshing a report in the following situations: In a Data Foundation, include a stored procedure or command table with parameters and a normal table and create a join from the stored procedure to the normal table. Enforce the join both ways. Create a report using the Business View based on this Data Foundation but include only fields from the normal table. In a Data Foundation, join a normal table with a stored procedure, and then join the stored procedure to another normal table. Include the fields from both normal tables but do not include the stored procedure table in the report. To resolve this issue, include a field of the stored procedure in the report, or create a filter with a field from the stored procedure and assign the row restriction to the Everyone group. An example of the filter text is: StoredProc.Field is any value.
Dynamic Prompts
To migrate a report that contains unmanaged dynamic prompts to BusinessObjects Enterprise, you need a Report Application Server to be configured and active on that BusinessObjects Enterprise system. An unmanaged dynamic prompt is a dynamic prompt that is based off report fields or command objects, and not a list of values that is stored in BusinessObjects Enterprise. This does not affect reports that contain static prompts.
44
Dynamic prompts that are created in the Business View Manager from stored procedures do not support the NULL value option. A dynamic prompt that requires a user to select more than one value on one level may display duplicate values on the next level below if the two levels have a one-to-many relationship in the data. Crystal Reports cannot accept certain characters in a group path for a dynamic prompt, because these characters are reserved as delimiters in the Crystal Reports syntax. The reserved characters are the forward slash (/), the left square bracket ([), and the right square bracket (]). For performance reasons, the maximum number of values that are returned for each level of a list of values is set to 1000. This number is controlled by a registry key. See our Technical Support site for information about this registry key. Note: This limitation is also true when populating a static parameters pick list from a database field.
For this version of Crystal Reports, you should not add a command that is used for a dynamic prompt to the BusinessObjects Repository. Doing so will make it impossible to disconnect the command from the repository, and the prompt itself may behave incorrectly. In a report that is based on a Business View, you cannot create a static parameter with a pick list. When Crystal Reports loads a database field to retrieve field values, an error appears. This behavior is a limitation in this version of Crystal Reports and the Business View Manager. When working with parameters in existing reports, ensure that the report can still access its data source before you try to change a static prompt to a dynamic prompt. If the program cannot find the data source, it will be impossible for you to create a new list of values. A report list of values is a list of values object based on fields in a report, or based on a command object in the report. This type of list of values will inherit the following items: All of the stored procedure or command parameters used by any of the objects in the report. The parameters that are needed by an list of values will always be prompted for before the report parameters. If a report needs a parameter with the same name as a parameter needed by a list of values, the parameter will be prompted for twice. The first prompt is used to generate the list of values data, while the second is used to generate the report data.
45
If more than one list of values has a parameter with the same name, that parameter is prompted for only once for all lists of values. The prompt will be repeated if the same parameter is used by your report. You cannot use a universe to create a list of values for a dynamic prompt. The list-of-vales record limit of 1000 can apply to the bottom-most level of your cascading prompt if the data source does not support Groupby, or if the tables used in the cascade cannot be linked in a single SQL query. This limitation means that the higher-level prompts may display far fewer values than you expect.
Formatting reports
To improve the formatting of lines and boxes, Crystal Reports now considers data position when determining the position of lines and boxes. Because of this change, existing reports may need to be revised, especially reports that use hierarchical grouping. For more information, visit our Technical Support site.
Universes
When you use a universe in Crystal Reports, you will encounter some differences in behavior from what you might expect in Web Intelligence. These differences are listed in a whitepaper that you can find on our Technical Support site. When you create a report from a universe that has security applied to it, the current version of Crystal Reports correctly discards the saved data when you reopen the report. However, the saved data is accessible (that is, it is not discarded) if you open the report in an older version of Crystal Reports. If the universe SQL contains two identical prompts, the user will be prompted once. Two prompts are considered identical if they have the same question, the same type (number, string or date), and the selection (single or multiple values). One limitation of this feature is that if two universe commands in the same report share the same prompt, the user will be prompted twice (because the prompt name will be different). To avoid this problem, link the two commands on the parameter. In the universe Designer, if a normal table is mapped to a derived table through a security restriction, elements of the normal table used to generate a universe query in Crystal Reports will be invalid.
46

Query Panel
If a universe contains multiple prompts in its Where clause, you cannot use it as a prompt for a parameter field in Crystal Reports. Multiple nested prompts are not supported in this version. It is recommended that you use multiple universes in a Link relationship and avoid using an Include relationship. When a universe is included, the reports based on this universe fail to refresh. If a universe object is renamed, any reports based on the universe will need to be fixed by verifying the database in Crystal Reports.
When you are prompted to choose a list of values to resolve a nested prompt in the Crystal Reports Query Panel, the prompt text is not shown. When you use the Query Panel to create SQL, you can give the SQL a unique name in the query name field (by default, the name is Query1). If you want to link this SQL with the SQL of another universe, name the two uniquely so that the names of the prompts will also be unique. Objects with multiple @Prompt functions in the Where clause cannot be used in filter objects in the Crystal Reports Query Panel When you refresh a report based on a Query Panel query using a date in a constant value filter or a nested prompt filter, if you receive the error Failed to retrieve data from the database with details ORA-01861: String literal does not match format string, this issue can be resolved by modifying the date format generated by the Web Intelligence server. On the Web Intelligence server machine, modify the data formats in the file <INSTALLDIR>\BusinessObjects Enterprise 11\win32_x86\ dataAccess\ConnectionServer\oracle\oracle.prm:
<Parameter Name="USER_INPUT_DATE_FORMAT">'yyyy/MM/dd HH:mm:ss'</Parameter> <Parameter Name="DATABASE_DATE_FORMAT">YYYY/MM/DD HH24:MI:SS</Parameter>
URL reporting
To enable international development, all URLs need to be properly URLencoded. For example, URLs that require accented or non-ASCII characters must be encoded.
47
Crystal Reports Developer issues
When you migrate URL reporting solutions using viewrpt.cwr from previous versions of Crystal Reports to Crystal Reports 11, you need to ensure your URLs are http://webserver/businessobjects/ viewrpt.cwr instead of <http://webserver/<anything> folder>/ viewrpt.cwr. In previous releases, viewrpt.cwr was a web server extension that applied to all requests to that web server. In Crystal Reports 11, viewrpt.cwr is an actual web application that resides in a specific virtual directory on the web application server.
Developer issues

There is no supported public SDK for the dynamic prompt feature in Crystal Reports 11 or BusinessObjects Enterprise 11. To open reports via an ASP page in IIS, the user account that you are running under must have Read and Execute permissions on the appropriate temp directory and temp file. To enable images in ASP reports viewed from the businessobjects directory, set the HKEY_LOCAL_MACHINE\SOFTWARE\
Business Objects\Suite 11.0\Report Application Server\Viewer registry subkey to the directory that contains the
images. Binding string values to the properties of the JavaServer Faces viewer is not supported. Instead, use the appropriate enum type. Passing string parameters to a viewer is not supported when the viewer is bound to a Page Server report source. If you are using IIS6, some images do not appear in reports that are called by an ASP page. To solve this problem, add anonymous access permission to the folder that your ASP page sits in. Then, add the internet anonymous user account to the permission section in IIS6. Do not use brace brackets ( { or } ) in a formula, database field, or SQL expression field. Doing so will cause the formula checker to fail.
Java Viewer SDK

Multi-byte characters entered in the parameter prompt page of the JavaServer Faces Viewer will not display correctly in the report if the JSP pages character set is not set to UTF-8. Navigating between group views and main views in the JavaServer Faces viewer may disrupt the view state for some reports.
48
Crystal Reports Developer issues
Setting the reportSource attribute to a scriptlet value is not supported by the JavaServer Faces viewer. Changes to the Initial Report Part Settings in the Java Reporting Component do not carry over to a different session. The Java Reporting Component does not support malformed HTML tags. The following locale-dependant functions are not supported in locales other than EN: Totext() -- Number, Currency, Date, Time, DateTime.
CStr() -- this function is the same as ToText() CDate(String) CTime(String) CDateTime(String) IsDate(String) IsTime(String) IsDateTime(String) DateTimeValue(String) TimeValue(String) DateValue(String)
Setting the table location to ODBC from ODBC is not supported in the Java Reporting Component. The Java Reporting Component does not support the use of relative paths for SunOne8 and Oracle 10g application servers. For the most complete description of the openDocument feature (used to create links between repository objects such as Web Intelligence documents or Crystal reports), consult the Viewers Java SDK Guide or the Viewers COM SDK Guide.
CR.NET SDK and Viewers
Exporting to Microsoft Word, Excel, or RTF formats from the .NET webForm viewer may result in an empty file on a machine with the base installations of Microsoft Office 2000. To resolve this issue, install the Microsoft Office 2000 Service Release 1. From Crystal Reports for Visual Studio .NET, OLAP reports are supported only for viewing. For applications being developed with the .NET viewers, the install-ondemand feature is not currently supported.
49
Crystal Reports Language version issues
When working with the Microsoft Visual Studio .NET Object Browser, certain classes from the Report Application Server .NET API may not be visible. However, the appropriate classes will appear through the Intellisense tool when you write code in Microsoft Visual Studio .NET. When you view a report with a selection formula from Crystal Reports for Visual Studio .NET (for both winform and webform), if you set the selection formula on the viewer to an empty string, it should override the formula in the report. For Crystal Reports for Visual Studio .NET, the return type of ReportDocument. ReportClientDocument.get_Subreport has been changed from ISCRSubreport to ISCRSubreportClientDocument. Dynamic localization will not work with unsupported languages for unmanaged dlls from Crystal Reports for Visual Studio .NET applications. When using InfoObject as the report source type for CrystalReportViewer.ReportSource, it is necessary to set InfoObject on each request.
Language version issues
The SQL Server JDBC driver from Microsoft does not correctly return table names that contain Japanese characters. The IBM DB2 Type 2 JDBC driver from IBM does not correctly return field names for tables if the field name contains Japanese characters.
Documentation

The documentation refers to all BusinessObjects XI components as version 11 components. If you are running the installation from a network location, you cannot open the installation guide (install.pdf) and release notes (release.pdf) from the Autorun. You can view the documents when you run the Autorun from the CD.
50
Crystal Reports Java Reporting Component
Java Reporting Component

Restrictions
The reporting component that processes reports, provided with Crystal Reports Java Reporting Component, is restricted by keycode to provide adequate performance for development, testing and deployment of limited reporting within applications. The following other restrictions apply to this version of Crystal Reports Java Reporting Component:
The Java Reporting Component will process only reports created using Crystal Reports 9 or later. Reports from earlier versions of Crystal Reports should be converted using the Report Conversion tool available for download from the Business Objects web site. The Report Creation and Modification API for the Java Reporting Component are not exposed in this release. Reports cannot be used that access the following data sources:
OLAP
Reports may only be exported to PDF, RPT, and RTF. The following capabilities are not supported in this release:
RTF interpretation Report templates Geographic mapping Gantt, Gauge, Funnel, and Numeric Axis charts Crystal Reports Repository Report alerts
Dynamic prompts are not supported. Reports containing groups with the group sort option set to original order cannot be opened. To export a report with the Java Reporting Component, java.io.tmpdir must be set to an absolute path.
51
Platform-specific issues
On an AIX platform running IBM JDK 1.3.1 or 1.4, a bug in the JDK can cause reports to crash. As a work around, set the environment JITC_COMPILEOPT to SKIP{com/crystaldecisions/reports/common/ encryption/Processing}{processing}. The BEA JRockit JVM has a parallel garbage collection option that causes out of memory exceptions when dealing with contiguous blocks of memory greater than 2 MB. As a work around, increase the maximum heap size or switch to the generational copying garbage collector. To set the maximum heap size, use the "-XmxNNNm" option, where NNN is the size of the heap in MB. To use the generational copying garbage collector, use the "-Xgc:gencopy" option. Exporting a report to PDF (either programmatically or through the viewers) is not supported on WebSphere Studio 6. This limitation does not apply to other application servers. It is recommended that you use ActiveX printing if your web application is deployed on WebSphere Studio 6. Alternatively, you can use the JSF version of the DHTML report page viewer, which does not have this limitation.
Formatting and rendering

The currency symbol in a report floats even if the fixed position option is selected. The time and date format displayed in a report is based only on the default locale settings of the server. When viewing a report in the viewer, text objects without spaces do not display if the width is too small. Increasing the width of the text object causes the report to be correctly displayed. The character spacing feature is not supported in this release. Character spacing applied to a text object is ignored. When viewing a report in the viewer, column headings of a cross-tab may overlap or truncate. When viewing a report with a cross-tab in the viewer, if the cross-tab has a total row at the top of the cross-tab, part of the fields in the cells are clipped. If the cross-tab has a total row at the bottom of the cross-tab, the cells are not clipped (it behaves as expected). When viewing a report in the viewer, extra lines in the text field can appear. This occurs due to rounding up the conversion from twips to pixels. As a work around, resize the section slightly.
52
When exporting a report to PDF, you may get an error message that says, The font contains a bad/BBox when you open the PDF. This error can be safely ignored as it does not affect the viewing of the PDF file. Reports that contain surface charts with null data are not rendered correctly when processed by the Java Reporting Component. The following table describes how the JRC behaves when opening and saving reports with the following unsupported features: JRC behavior when opening report with this feature Raw RTF text is shown, but not interpreted Alerts are not be triggered. JRC behavior when saving report with this feature The fact that a field has RTF interpretation flag on will be preserved. Alerting information in the report definition is preserved. However, alerting views are not preserved.
Feature
RTF interpretation
Report alerts
Geographic maps Gantt, gauge, funnel, and numeric axis charts Crystal Reports 9 report charts with textures and pictures
Appear as blank objects. Preserved in the report definition. Appear as blank objects Preserved in the report definition. Preserved in the report definition. Preserved in the report definition.
Not shown.
Font, line, or fill options Not shown. in a chart legend Chart label placement
If labels are moved, they Preserved in the report are reset to their default definition. positions.
53
Feature
JRC behavior when opening report with this feature
JRC behavior when saving report with this feature
Special fields with Crystal Enterprise context: Current CE User ID, Current CE User Name, and CurrentCEUserTime Zone Dynamic images Hierarchical group sorting Formula function additions
Mapped to Vertical Page Special fields are Number, preserved. ReportAuthorName, and ReportAuthorName respectively.
Not supported. Supported.
Full support. Full support. Full support.
Parameterized sorting Supported.
Supports URL encoding/ Full support. decoding, time zones (but not Crystal Enterprise time zone), shift time zones, mround, ceiling, floor, and roundup. Not supported. Supports flattening column headings for crosstabs. Not preserved. Flattened column headings are preserved. Drill-through view is not preserved.
Dynamic prompts Grid enhancements
Relational databases and SQL statements
When refreshing a BIT stored procedure report from a SQL Server or Sybase database, parameter fields become pull down menus with no default values. You cannot view the report if the report relies on parameter values. The Oracle JDBC driver does not support reports with BFILE data. The Oracle JDBC driver does not support interval data types. The Oracle JDBC driver does not support reports with UROWID data.
54
The Sybase JDBC driver only allows up to 255 characters to be entered for fields of type char, varchar, and nvarchar. If you need to enter more than 255 characters in a field, use the text type instead. Earlier versions of the Sybase JDBC driver do not support reports with UNICHAR or UNIVARCHAR data. Use jConnect for JDBC version 5.5 ESD #9 or above. The Informix ODBC driver returns the CLOB field as an object rather than a CLOB. Reports with cyclic joins are not supported in this release. In addition, joins that require execution of independent queries, which are then later linked by some other set of tables, are not supported in this release. BLOB fields that are set to 'can grow' do not grow. For example, different sized images placed in BLOB fields with the 'can grow' property are rendered as the same size. When refreshing a stored procedure report from a SQL Server database, timestamp parameters should be in hexadecimal format. Java Reporting Component does not respect enforced join of tables.
Report functionality

The Java Reporting Component uses a high resolution time and date format. Date and time functions can return a non-integer number of seconds. When using the ASC and CHR functions, a runtime error occurs if characters with a value outside 0-127 are used. The ASC and CHR functions have been deprecated and will not be supported in future versions. We recommend using ASCW and CHRW functions in their place to avoid the runtime error with values outside 0-127. Only English-locale datetime strings are supported in the formula language for this release.
55
56
Web Intelligence
chapter
Web Intelligence Web Intelligence
Web Intelligence
This section lists general information and known issues when accessing Web Intelligence.
General Information
General
The following Web Intelligence components are not 508 compliant:
Creating and viewing Web Intelligence documents with Java Report Panel Creating Web Intelligence documents with Query HTML Viewing Web Intelligence documents in Interactive view format Viewing Web Intelligence documents in HTML view format Creating Web Intelligence documents with HTML Report Panel
However, the following Web Intelligence components are 508 compliant:
The HTML Interactive viewing option and On-Report Analysis features are not available for Web Intelligence when deployed in .NET mode. You cannot refresh a document based on a universe for which your security profile does not allow you to view specific objects. When downloading Web Intelligence documents to MS Excel, the way table columns are rendered can restrict how you apply sorts and calculations. To save Web Intelligence documents from the application, you must disable popup blocking on your web browser. A Web Intelligence document name can be a maximum of 100 characters. In this release, the DayNumberOfWeek function in Web Intelligence calculates the number for day the same as BusinessObjects: Monday is day 1. (In previous versions of Web Intelligence, Sunday is day 1.) This change can affect some results on reports created using previous versions of Web Intelligence that include the DayNumberOfWeek function. When creating Web Intelligence documents in the .NET or Java InfoView, the Select Universe page does not support paging and returns only the first 1000 universes.
58
When viewing Web Intelligence documents in the Interactive viewer, if you take a snapshot and then rename a report, an additional report will appear to be displayed. Close and reopen the document.
Java Report Panel
There are limited multiple selection features in the Java Report Panel. With the Java Report Panel, if you create a table including a measure, then save it as PDF, and then open it with Acrobat Reader, the numeric values may be poorly aligned. The display depends on the number of digits. HTML-specific features (such as the "Visited color format" option for hyperlinks and the "Read contents as HTML" cell format option) do not appear to be applied in the Java Report Panel, because the report panel is not a web browser. When you view Web Intelligence reports via InfoView in HTML format, these options are applied correctly. Setting section properties: If any of the report elements checked in the "Consider section empty when the following are empty" list on the Section properties tab are empty, the entire section is hidden. When you add blocks or free-standing cells to a section, they are checked in the "Consider section empty when the following are empty" list on the Section properties tab, by default. This means that when you add a block or free-standing cell to a section and those blocks or freestanding cells are empty, the entire section is hidden.
HTML Report Panel
The HTML Report Panel can edit most documents that had been created with the Java Report Panel, with the exception of .wid documents that include multiple blocks.
Row count value
The row count value set for tables in a universe is not supported in InfoView. The row count value for a table is manually set from the Table row count dialog box in Designer. This setting allows you to optimize the order of tables in the FROM clause.
Queries, Filters, Prompts, and Lists of Values
When you create prompts and apply the "Keep last value selected" option, you need to save the document so that the last value selected for the prompt will be retained the next time the report(s) are refreshed.
59
Known Issues
General
On Windows under heavy load, a potential stability issue has been found when transferring large binary buffers between the server component and the application server (such as PDF files, bitmaps and so on). This issue occurs on a JSP implementation using Apache/Tomcat and results in a saturation of available connectors between the web server and the application server. When the server component reaches its inactivity timeout setting, all the resources are freed and the system recovers. You cannot create a Web Intelligence document on universes when the name of the universe includes the special character "\". Workaround: Modify the name of the universe using Designer and ensure that the name of the universe does not include the "\" character.
In the Netscape web browser, when you view a Web Intelligence document in PDF format with Adobe 6, an error message appears. Ignore the error message and click OK. The document will appear in PDF format.
Downloading Web Intelligence documents as Microsoft Excel files
The default number format in Web Intelligence does not correspond with the default number format in Microsoft Excel. When you save a Web Intelligence document as an Excel spreadsheet, the rendering on the spreadsheet may differ from the format on Web Intelligence report(s). Workaround: Use Web Intelligence to apply a custom number format to report cells with numerical values, before saving the document as an Excel spreadsheet.
When you are using Web Intelligence from a Macintosh computer, a MacOffice limitation means that if a document name contains more than 31 characters, when you download the document to MS Excel, the document name is shortened and is followed by a "#" character and other special characters. When you save Web Intelligence documents that include reports with multiple aligned charts to Microsoft Excel, the reports may be incorrectly rendered.
60
Drilling Web Intelligence reports
The Drill up icon does not appear on legends. You can right-click to view the menu choice for drilling up. You cannot drill on the Drill up icon on charts. Drill up on the chart values instead of the icon. When using a Netscape web browser to interact with charts on Web Intelligence reports, in HTML or Interactive format, clicking the text on the Drill menu or the Interactive Reporting menu does not work. To display the Drill and/or Interactive Reporting menu, right-click the chart. On the menu, click either the icon or the empty space in front of the text for the option you want to select.
Queries, Filters, Prompts, and Lists of Values

Charts
No warning appears when a query returns a Cartesian Product in Web Intelligence and InfoView. This is a bug that occurs when the Warn option is selected for Cartesian Products in the SQL page of the Universe Parameters dialog box in Designer. A query in Web Intelligence can return incorrect data when the data type in the database is not compatible with the data type defined in the universe. The Both and Except operators do not work with Microsoft SQL Server databases. This is a limitation of those databases.
Some axis legends with many values or long axis labels do not display correctly. Workaround: Report Creators can try one or more of the following: resize the charts from the default size, change the point size of the axis labels, or use formulas/variables to shorten the length of object names used for axis labels. Alternatively, report creators can reduce the number of objects in a given chart, or divide one chart into many showing different parts of the same series (for example, three charts for different products/time-frames, rather than all products in same year).
When creating a Pie chart, the Show Axis Labels setting may truncate the label depending on the number of objects used to build the chart.
61
Java Report Panel
The Java Report Panel (applet) does not support cascading prompts. To use cascading prompts, we recommend that you view reports that contain cascading prompts in either HTML or Interactive view format: Click the Preferences button on the InfoView toolbar.
Click the Web Intelligence Document Preferences tab. The Web Intelligence Document Preferences page appears. In the Select a view format section, select HTML or Interactive. Click OK.
In the Netscape web browser only, the Java Report Panel does not close when you log out of InfoView. We recommend that you save documents in any Java Report Panel browser windows that you have open, and close these windows before you log out of InfoView. If you get an error in the Java Report Panel that you cannot resolve, or if you have left Web Intelligence open on your PC without using the application and reached timeout, Business Objects recommends that you do the following: Close the Java Report Panel window. Restart Web Intelligence by logging into InfoView again and either open an existing document or create a new document. Some drag and drop actions on formulas in tables may result in an unexpected behavior in the swapped columns. Workaround: Click the Undo button, and then edit or copy and paste the formulas manually.
When you use the Turn To feature to change the format of a block while working in Results View, certain charts may seem to disappear. This is because the objects displayed on the block in the previous format cannot be displayed in the new format. Workaround: Click the Edit Structure button to view the report in Structure View, and then drag the appropriate objects (that is, dimensions and measures) onto the appropriate axes on the new chart format.
When the User Settings option Show grid is selected, the grid does not display clearly if a background color, skin, or image is applied to a section.
62
Java Report Panel: Properties options
Occasionally, when editing a document in the Java Report Panel, the Repeat footer before a new page option is not applied correctly. Workaround: In such cases, you may have to reset the footer properties.
Scheduling
In some cases, the display settings for empty blocks and sections may not work properly.
When scheduling Web Intelligence documents with context, the context saved with the Web Intelligence document is used. You cannot choose a context while scheduling. Pre-caching works if the cache is still valid and your view requests are sent to the Web Intelligence server that handles scheduling. Pre-caching will not work if the cache has timed out or if the server has been restarted.
Editing reports in Interactive view format
In the appearance tab of the format chart window for scatter charts, the Y and Z labels and values are displayed in the wrong position, however the formatting applies correctly to the respective axis as shown in the pivot tab. Report toolbar items and related features in interactive menus are not available when we have an aggregate formula in a column. In the appearance tab of the format chart window, the alignment will not work for the values and labels on charts. In the appearance tab of the format chart window for 2D charts, setting the orientation of the values on the X axis does not work. It is not possible to drill on data series of any 3D charts, except for 3D bar charts. When the border size of cells are different, there can be problems correctly applying the border colors in the format cell window. After dragging and dropping a dimension with a prompt in the query panel and then selecting the quick filter button the browser hangs. If you use Interactive viewer with Netscape, you cannot change field sizes.
63
Web Intelligence Web Intelligence SDK
The find drop down in the Interactive viewer may appear inactive (greyed out) when it should not. If this occurs, delete the value that you typed into the Find drop down and re-enter it. When using Netscape to design Web Intelligence documents in the Interactive viewer, you can change column sizes, but your changes will not be displayed in the document. If you view the document in a different browser, you will see the new column settings.
Documentation
For the most complete description of the openDocument feature (used to create links between repository objects such as Web Intelligence documents or Crystal reports), consult the Viewers Java SDK Guide or the Viewers COM SDK Guide. The Hide contents button does not work in Netscape Navigator. You must leave the table of contents open. The Index and Search sections of the online help do not work the same way in Netscape Navigator as they do in Internet Explorer. To use the Index in Netscape Navigator, click the letter that corresponds to the first letter of the keyword entry you want to find in the Index. To use the Search function in Netscape Navigator, click the letter that corresponds to the first letter of the word(s) you want to search.
Web Intelligence SDK

Known Issues
The following are the known issues in Web Intelligence SDK.
Viewing
Calling Values.WasSelected, Values.IsSelected or Values.IsDefault will return an invalid procedure call. If a Sort is applied on the second column of a List of Values, the Sort will not be taken into account when the query is run. Calling RowValue.Header raises the following exception "Object doesn't support this action".
64
Web Intelligence Designer
Calling Report.getView for Excel or PDF format now returns a result depending on the Report's PaginationMode: PaginationMode.Listing returns the entire report.
Output
PaginationMode.Page returns the current report page.
Previously Report.getView returned the entire report only.
Editing
When calling the XMLView.getReader function, the QUERIES and META_DATA filters are not available.
To customize Web Intelligence, we recommend that you use the Web Intelligence Web Services SDK for all platforms, and the Web Intelligence Java SDK (REBEAN) for Java. Customization of the ASPX pages will not be supported or migrated to future versions, as a change in this code is planned. Use the Web Services SDK for .NET customization. The set and get methods inherited from Unit may return different results due to rounding off when calculating a position.
Precision
Limitations
The following are limitations in Web Intelligence SDK.
Viewing
HTML format Drilling
It is not possible to change the drill-block synchronization. This means that a report is drilled using the option set during document creation.
Designer
Although the option still appears in the Designer, the ability to restrict long text objects is not supported in this release.
65
Web Intelligence Designer
Sybase drivers cannot be used with Designer or Web Intelligence to access a read-only Sybase database. To use a Sybase database, it must have write permissions granted to the driver. (Note that no actual writes will be performed.) In the Designer, you can set formatting information (such as font and color) for objects. In previous releases (such as BusinessObjects Enterprise 6.5), these format settings were used by reporting tools like BusinessObjects 6.5. In BusinessObjects Enterprise 11, this information is not used by the reporting tools, such as Web Intelligence. If an exported list of values for an object creates a Cartesian product, you receive a warning when importing the universe. The message box warns that the query will create a Cartesian product and asks if you want to continue. If you select Yes, the List of Values will be imported. If you select No or Cancel, the List of Values will be discarded. In any case the universe import will continue normally. If an exported list of values for an object requires a context selection, you receive a context prompt when importing the universe. The selected context is used to refresh the list of values. If you click Cancel at the prompt, the list of values is discarded.
When you export a universe that contains an object that has a @Prompt in its Where clause, and the option "Export with Universe" selected for its lists of values, you are prompted for each list of values. Typing a value or canceling the list of values does not affect the export. When you create a custom hierarchy, it will always be used in InfoView, even if the Default Hierarchies (for a dimension object) radio button is selected in the Hierarchies Editor. When you add parameters to a universe in the Designer, multiple SQL statements are not supported. The efashion and beach sample universes do not connect to the sample data sources. You need to create a new ODBC data source for efashion.mdb and club.mdb found in the <INSTALLDIR>\Samples\<lang>\Databases directory. To create connections for efashion and beach universes using the new data sources: 1. 2. 3. 4. Create ODBC data sources for club.mdb and efashion.mdb. Start Designer. Browse to <INSTALLDIR>\Samples\<lang>\Universes. Open each universe.
66
Web Intelligence Universe and connection management
5.
Save each universe to the universes folder under the BusinessObjects application folder in your profile. For example: C:\Documents and Settings\<user>\Application Data\Business Objects\Business Objects 11.0\universes. For each universe:
6.
Create a secured connection using the new ODBC data source created earlier. Set the connection to the universe. Note that efashion.unv connects to efashion.mdb and beach.unv connects to club.mdb. Save each universe with its new connection. Export each universe to the repository.
You can now use the sample universes with their data sources. A universe file (.unv) saved for all users by a Business Objects 6.5 designer can be opened by a Business Objects 11 Designer. However, if the universe is exported to the repository, the local .unv file will become inaccessible. To use the universe, delete the local .unv file from the filesystem and re-import it from the repository. When you export a universe, groups that have been selected in the "Export Universe" dialog box will be assigned "Full Control" role on the universe and they will be granted the "Data Access" right on the corresponding connection. Note that the user performing the export must have rights to modify rights on the universe and connection object in order to grant the rights to the selected groups. The BusinessObjects Enterprise system variable, BOPASS, is no longer supported.
Universe and connection management
Lists of values from a core universe cannot be viewed or edited in a derived universe in the Designer. Lists of values from a core universe can be used in Web Intelligence documents based on the derived universe, but if you want to edit the lists of values in the Designer, you must edit the core universe.
67
Web Intelligence Web Intelligence servers
Web Intelligence servers

Web Intelligence Report Server
It may take several minutes to shut down the Web Intelligence Report Server if users have been refreshing documents many times in a single session. The Web Intelligence server deletes the temporary session folders on shutdown.
Checking connection configuration

You can use a command line utility called the Check tool (cscheck.exe) to verify your connection configuration. When you use the Check tool, you have the following options:
Checking available connectivities Displaying a list of installed data access drivers Displaying a list of active data access drivers Checking your middleware Testing a connection to a database server Checking a data access driver.
The Check tool is a command line utility provided with your data access driver. You can use the Check tool to check your client middleware and Business Objects data access driver installation at any time. The Check tool (cscheck.exe) is installed to the following directory:
<installdir>\win32_x86\
Using the Check tool

You can run the Check tool at any time.
Running the Check tool

1. 2. To run the cscheck utility: Open a DOS prompt. Change to the path where the utility is installed, for example:
cd $INSTALLDIR\RDBMS\connectionServer
68
3. 4.
Enter cscheck with the values you want to check. Review the returned information.
The Check tool syntax and functions that you can use are described below.
Check tool syntax

You use the Check tool in a command editor. You use the following syntax: Check tool syntax Description
cscheck (--help|-h) [(--language|l) <lg>] Displays general help message for cscheck utility. <lg>: output language name. cscheck [(--language|l) <lg>] <function name> (--help|-h) Displays the help message for the function.
cscheck [(--language|l) <lg>] [--xml|x] [- Calls the function with its options. -mute|m] <function name> <function --xml: xml output options> --mute: no output <function name> can take the following values:
(middleware|mw) (list|lt) (accessdriver|ad) (connectivity|ct) (driverssearch|ds) (find|fd) (ping|pg)
Each of these functions is described in the following section.
Check tool functions

You can run the following functions:
Drivers search
The tool returns the list of BO access drivers that are installed on your local machine.
69
Syntax
cscheck [(--language|l) <lg>] [--xml|x] [--mute|m] (driverssearch|ds)
Example
cscheck driverssearch
List
This function returns the list of network layers and database engines and allows you to get the correct network layers and database engine syntax when using other functions. This function returns the full list of supported data access drivers and middleware. You receive the full list even if you do not have all the listed data access drivers and middleware installed.
Syntax
cscheck [(--language|l) <lg>] [--xml|x] [--mute|m] (list|lt)
Example
cscheck list
Middleware
On your local machine, the tool checks the client middleware installation. Specify which couple(s) network layer / database engine you want to validate and run the command.
Syntax
cscheck [(--language|l) <lg>] [--xml|x] [--mute|m] (middleware|mw) {(-c|--clientlayer) <layername> (-d|-database) <dbname>}
Example
cscheck --xml middleware -c "Oracle Client" -d "Oracle 8.1" > c:\result.xml
Note: When using the check tool to test the middleware,an xml file c:\results.xml is generated. When opening this file with an xml editor, a missing cscheckoutput.dtd file error is seen. This dtd file is not included with the installation. However, renaming cscheckresults.dtd to cscheckoutput.dtd ensures that the check is successful.
Data access driver

On your local machine, the tool checks the Business Objects access driver(s) installation.
70
Specify which couple(s) network layer / database engine you want to validate and run the command.
Syntax
cscheck [(--language|l) <lg>] [--xml|x] [--mute|m] (accessdriver|ad) {(-c|--clientlayer) <layername> (-d|-database) <dbname>}
Example
cscheck -l English accessdriver -c "Oracle Client" -d "Oracle 8.1"
Connectivity
On your local machine, the tool checks the global connectivity (ies) (client middleware + BO access driver) installation. Specify which couple(s) network layer / database engine you want to validate and run the command.
Syntax
cscheck [(--language|l) <lg>] [--xml|x] [--mute|m] (connectivity|ct) {(-c|--clientlayer) <layername> (-d|-database) <dbname>}
Example
cscheck -l English connectivity -c "Oracle Client" -d "Oracle 8.1">c:\result.txt
Find
Returns the list of access drivers loaded by Connection Server
Syntax
cscheck (find|fd)
Example
cscheck find m local
Ping
The ping function of the Check tool (cscheck.exe) does not work.
71
72
OLAP Intelligence
chapter
OLAP Intelligence 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).
General issues
Authentication issue when creating OLAP reports from a web browser: If you are creating an OLAP report based on a Microsoft Analysis Services cube that does not use role-based security, you do not need to enter values for Username and Password. When these fields are left blank, the user will be authenticated with the credentials of the process account that runs the InfoView .NET application. Visit the Business Objects online support site for detailed information about how to configure OLAP Intelligence to support Microsoft Analysis Services security.
Errors are encountered when previewing OLAP Intelligence reports in the Central Management Console. If you preview OLAP Intelligence reports in the Central Management Console, note that the Preview function is intended only for system administrators to ensure that reports display correctly, not for interaction with the reports. If you try to manipulate or save previewed reports, errors may 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 via the Tools>Add-Ins menu in Microsoft Excel, the OLAP Intelligence toolbar is removed but the OLAP Intelligence Navigation toolbar may not be removed. You can manually remove the toolbar by using the Tools>Customize menu in Excel. Calculated members from higher hierarchical levels in a dimension are unexpectedly displayed along with members at lower levels. When you use OLE DB for OLAP (MSOLAP) data sources, then when your Worksheet contains a dimension with three or more levels in its hierarchy, and if there are calculated members at some or all of the levels in the hierarchy, the calculated members can be displayed unexpectedly. For example, if your dimension has four levels, level 4 being the lowest child level, and if calculated members exist at all four levels, then when you invoke the Member Selector by right-clicking a level 1 member, and then use the Add Children to Selection>Custom function to try to display
74
OLAP Intelligence General issues
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.
When connected to a MSOLAP data source, OLAP Intelligence can produce erratic behavior when the underlying data cube is refreshed. Your report may become unstable and potentially unusable. If you need to refresh an OLAP cube, ensure that nobody 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 reports data may not be updated properly.
An OLAP report that was saved to BusinessObjects Enterprise by the OLAP Intelligence designer, appears as a report that was 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 both be toggled on and off. This behavior occurs in the following situation: 1. 2. 3. 4. An OLAP report is created in the Interactive Viewer and saved to BusinessObjects Enterprise. The report is closed, but the InfoView session is not closed. The report is then opened in the OLAP Intelligence designer and resaved to BusinessObjects Enterprise with the same name. 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.
Users are unable to export to Excel from OLAP Intelligence. On a machine where OLAP Intelligence has just completed its installation and Excel has not yet been opened, attempting to export an OLAP report to Excel will cause an instance of Excel to appear on the taskbar, but opening this instance is not possible. 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
75
OLAP Intelligence General issues
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 Business Objects online support site. Within a Java deployment of OLAP Intelligence, saved reports performed through the DHTML viewer will force a secondary logon. Reports set with the Use WCA credentials or Use specified credentials option, when saved back into the BusinessObjects Enterprise will not keep the previous authentication method, which forces a secondary logon. To resolve this issue, change this option with the CMC for the affected OLAP Intelligence reports. The OLAP Intelligence toolbar may not contain all of the buttons described in the documentation. Some of the new toolbar functionality is available only in the DHTML version of the Interactive Viewer. The Swap Series/Groups function in the OLAP Intelligence designer does not function. When you select the Swap Series/Groups check box on the Legend tab in the Chart Options dialog box, the preview image in the dialog box displays the change but when you click OK, the chart does not update. The Swap Series/Groups feature is not supported in this release.
When you create a report in the Interactive Viewer and hide the Worksheet, some toolbar buttons that operate only on the Worksheet are still enabled. Ignore error messages resulting from the use of these toolbar buttons when the Worksheet is hidden.
Sending an email with a hyperlink to a web-authored OLAP Intelligence report that uses secondary logon, is not supported in this release. If you create an OLAP Intelligence connection and then click the Test Connection button, an error results. If you click the OK button instead, all of the fields are erased. Do not use non-standard characters in the Title field when you create a new OLAP Intelligence connection in InfoView. Some non-standard characters are: " ' @#$%^&*()!
If you press the Enter key from the Test Connection page, an error results. When you create OLAP Intelligence connections in InfoView, pressing the Enter key may not produce the desired results. Click the OK button with the mouse instead.
76
OLAP Intelligence Data source connectivity
In InfoView, %SI_VIEWER_URL% does not expand when sending an OLAP Intelligence report to SMTP. You must set the viewer URL in the Central Management Console after installing OLAP Intelligence. In the Organize area in the CMC, select Objects and then click Object Settings. Type the correct URL in the URL field, and then click Set URL.
OLAP reports that are locked with a password and then published to BusinessObjects Enterprise, open in Infoview without a password. In the OLAP Intelligence designer, you can set an option for how to remember passwords in saved files. The Never option should be used only with the designer and not with published reports.
In Java InfoView, when you save an OLAP report with a MSOLAP connection in the Interactive Viewer, you are prompted for logon credentials. When the IBM WebSphere Application Server is used, you may be prompted for logon credentials when you save reports in the Interactive Viewer.
If you set your data source logon to use WCA authentication and your data source is not MSOLAP, reports appear blank. Setting the logon for an OLAP Intelligence report to use WCA credentials is not valid for OLAP vendors other than MSOLAP.
Data source connectivity

Holos connectivity is being deprecated in the OLAP Intelligence designer. Holos data sources are not supported for web authoring. Reports appear blank when Web Component Adapter (WCA) authentication fails. If an OLAP Intelligence report fails to connect to an MSOLAP server, specify credentials other than WCA logon credentials. 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, you 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.
77
Hyperion Essbase/IBM DB2 OLAP Enhanced Driver

The following information is missing from the product documentation .
OLAP Vendor Runtime Client Pre-Requisites

The Essbase 7.0 or 7.0 or IBM DB2 OLAP 8.2 runtime client must be installed on the same machine as the OLAP Intelligence XI Windows Designer and any BusinessObjects Enterprise XI Web Component Adapter machines.
Essbase 7.0 Runtime Client: Windows

When you install with the Essbase 7.0 runtime client, you must select the following options:
Hyperion Essbase Client Runtime Client Essbase API
Essbase 7.1 or IBM DB2 OLAP 8.2 Runtime Client: Windows

When you install with the Essbase 7.1 or IBM DB2 OLAP 8.2 runtime client, you must select the following options to install:
Hyperion Essbase Client Runtime Client Essbase API
There is one file that is not installed with the Essbase 7.1 Runtime client that you must manually copy to the appropriate location. You must copy Hyperion\essbase\api\redist\libdb42.dll to Hyperion\essbase\bin\libdb42.dll and then restart the machine.
Essbase 7.1 or IBM DB2 OLAP 8.2 Runtime Client: UNIX

When you install on UNIX, you must copy the file libdb-4.2.so to the Essbase bin subdirectory. The libdb-4.2.so is part of the Essbase driver installation package.
Syntax
The Hyperion Essbase/IBM DB2 OLAP Enhanced Driver contextual syntax that is used within the actions are different than those used in the Hyperion Essbase Legacy and IBM DB2 OLAP Legacy driver. The syntax differences are outlined below.
78
Cube
Legacy Driver Example:

SERVER=server1,USER=bob,PWD=bobpassword,DATABASE=Samp part,SCHEMA=Company,CUBE=Company
Enhanced Driver Example:

SERVER=server1,USER=bob,PWD=bobpassword,APPLICATION=S amppart,CUBE=Company
Dimension

GetName({Products})

GetName({@Products})
Member

GetName({Product@*})

GetName({@@Product@*})
Known Issues
Aggregate Storage Cube with Filters
When aggregate storage cubes contain filters, whereby the user is restricted from seeing cell values for specify members, the value displayed is 0.000000000000007. The expected value is NULL, this issue is a result of the Essbase runtime client API returning the incorrect value. This is a display issue only; it does not affect data integrity or compromise security.
79
Slice Dimensions in DHTML Worksheet

When the DHTML viewer is used to view data, the worksheet will not automatically resize the lengths of the slice dimensions. Some slice dimensions with have truncated names, this does not affect functionality within OLAP Intelligence. To workaround this issue, use the tooltips by hovering above the dimension to see its full name. Another workaround it to display the slice dimensions in a Slice Navigator and disable them in the worksheet.
80
Business Objects Information Resources
appendix
Documentation and information services
Documentation and information services

Business Objects offers a full documentation set covering its products and their deployment. Additional support and services are also available to help maximize the return on your business intelligence investment. The following sections detail where to get Business Objects documentation and how to use the resources at Business Objects to meet your needs for technical support, education, and consulting.
Documentation
You can find answers to your questions on how to install, configure, deploy, and use Business Objects products from the documentation.
Whats in the documentation set?

View or download the Business Objects Documentation Roadmap, available with the product documentation at http://support.businessobjects.com/ documentation/. The Documentation Roadmap references all Business Objects guides and lets you see at a glance what information is available, from where, and in what format.
Where is the documentation?

You can access electronic documentation at any time from the product interface, the web, or from your product CD.
Documentation on the web

The full electronic documentation set is available to customers on the web from support web site at: http://support.businessobjects.com/documentation/.
Documentation on the product CD

Look in the docs directory of your product CD for versions of guides in Adobe PDF format.
Customer support, consulting and training
Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line, and we will do our best to ensure that your suggestion is included in the next release of our documentation: documentation@businessobjects.com. Note: If your issue concerns a Business Objects product and not the documentation, please contact our Customer Support experts. For information about Customer Support visit: http:// support.businessobjects.com/.

A global network of Business Objects technology experts provides customer support, education, and consulting to ensure maximum business intelligence benefit to your business.
How can we support you?

Business Objects offers customer support plans to best suit the size and requirements of your deployment. We operate customer support centers in the following countries:
USA Australia Canada United Kingdom Japan
Online Customer Support

The Business Objects Customer Support web site contains information about Customer Support programs and services. It also has links to a wide range of technical information including knowledgebase articles, downloads, and support forums. http://support.businessobjects.com/
BusinessObjects XI Release Notes 83
Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in relational and multidimensional databases, in connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: http://www.businessobjects.com/services/consulting/
Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Find more information on the Business Objects Education web site: http://www.businessobjects.com/services/training
Useful addresses at a glance

Address Business Objects product information http://www.businessobjects.com Product documentation http://support.businessobjects.com/ documentation Business Objects Documentation mailbox documentation@businessobjects.com Online Customer Support http://support.businessobjects.com/ Business Objects Consulting Services http://www.businessobjects.com/ services/consulting/ Business Objects Education Services http://www.businessobjects.com/ services/training Content Information about the full range of Business Objects products. Business Objects product documentation, including the Business Objects Documentation Roadmap. Send us feedback or questions about documentation. Information on Customer Support programs, as well as links to technical articles, downloads, and online forums. Information on how Business Objects can help maximize your business intelligence investment. Information on Business Objects training options and modules.
BusinessObjects XI Release Notes 85

Release

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Release

Încărcat de

Drepturi de autor:

Formate disponibile

BusinessObjects XI Release Notes

BusinessObjects XI Release Notes

2 BusinessObjects XI Release Notes

BusinessObjects XI Release Notes

4 BusinessObjects XI Release Notes

BusinessObjects XI Release Notes

BusinessObjects XI Release Notes About these notes

About these notes

What is BusinessObjects XI?

Business Objects information resources

BusinessObjects XI Release Notes

BusinessObjects Enterprise Installation

ASP .NET is installed and enabled.

8 BusinessObjects XI Release Notes

BusinessObjects Enterprise Installation

From the command prompt, type the following command:

ASP .NET is installed and enabled.

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

Upgrading and migrating issues

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

Importing data from Crystal Enterprise to BusinessObjects Enterprise XI

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

Importing data from BusinessObjects Enterprise 6.x to BusinessObjects Enterprise XI

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

BusinessObjects XI Release Notes

BusinessObjects Enterprise Upgrading and migrating issues

BusinessObjects Enterprise XI and BusinessObjects Enterprise 6.5

Shutdown port: 9005 Redirect port: 9443

BusinessObjects XI Release Notes

BusinessObjects Enterprise Server management

and change the value of the password attribute to AutoGenerate:

Save the machine.config file.

BusinessObjects XI Release Notes

BusinessObjects Enterprise Server management

Change the following line

Save the web.config file. Restart IIS.

Add the following line:

Central Management Server (CMS)

BusinessObjects XI Release Notes

BusinessObjects Enterprise Web and Windows applications

Processing servers (Page, Job, Cache)

Report Application Server (RAS)

Web and Windows applications

BusinessObjects XI Release Notes

BusinessObjects Enterprise Web and Windows applications

BusinessObjects XI Release Notes

BusinessObjects Enterprise Web and Windows applications

BVMigrationWiz.exe BVMigrationWiz.pdf BVMigrationWiz_res_en.dll

Central Management Console (CMC)

BusinessObjects XI Release Notes

BusinessObjects Enterprise Web and Windows applications

BusinessObjects XI Release Notes

BusinessObjects Enterprise Web and Windows applications