Xir2 Bip Install Unix en

BusinessObjects Enterprise™ XI
Release 2 Installation Guide
BusinessObjects Enterprise XI Release 2 Productivity Pack

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

Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
UNIX permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting up server communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Choosing a server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Choosing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Using MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Using a supported database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Choosing a deployment environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Choosing a development environment . . . . . . . . . . . . . . . . . . . . . . . . 20
Choosing a web application server . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Choosing a Web Component Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 22
Choosing optional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
OLAP Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Desktop Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Crystal Reports Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Web Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Business Process BI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Choosing an install type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
BusinessObjects XI Release 2 Installation Guide 3

Contents
New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Setting up your UNIX system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Meeting the host name and network requirements . . . . . . . . . . . . . . . . 28
Creating an account, a home directory, and a login environment . . . . . 28
Checking for required commands and utilities . . . . . . . . . . . . . . . . . . . 29
Setting the locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Setting up an empty database for the CMS . . . . . . . . . . . . . . . . . . . . . 30
Database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
DB2 database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Sybase database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Oracle database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 34
MySQL database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Preparing your existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Providing and verifying connectivity to the CMS database . . . . . . . . . . 36
Testing DB2 environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Testing Sybase environment variables . . . . . . . . . . . . . . . . . . . . . . . . . 39
Testing Oracle environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Installing the Java SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 3 Installing BusinessObjects Enterprise on UNIX 47

Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Setting up product distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Running the product distribution directly from a CD . . . . . . . . . . . . . . . 49
Copying the product distribution to your machine . . . . . . . . . . . . . . . . . 49
Beginning your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Difference between user and system installation . . . . . . . . . . . . . . . . . 50
Beginning your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Performing a new installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4 BusinessObjects XI Release 2 Installation Guide

Contents
Finishing a system installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Performing an expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Performing a custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Performing a client tool installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Performing a scripted installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Using ccm.sh to start the BusinessObjects Enterprise servers . . . . . . . 71
Installing a Java application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installing the Java application tier components . . . . . . . . . . . . . . . . . . . . . . 72
Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Verifying your performance management installation . . . . . . . . . . . . . . 77
Post installation setup for performance management . . . . . . . . . . . . . . 78
Troubleshooting starting performance management . . . . . . . . . . . . . . 78
Chapter 4 Installing the Productivity Pack 81

Productivity Pack upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
What is included in the productivity pack? . . . . . . . . . . . . . . . . . . . . . . 82
Business Process BI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
BusinessObjects Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Content Search in InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Distributed installs of BusinessObjects Voyager . . . . . . . . . . . . . . . . . . 84
Feature selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Silent install parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
New or updated WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Uninstalling the Productivity Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 5 Deploying on Tomcat 95

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Deploying with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Preparing the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Chapter 6 Deploying on Tomcat with the JDK 1.5 103

Modifying Tomcat to use JDK 1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Contents
Using a version of Tomcat already running BusinessObjects Enterprise .

104
Copying the required Jar file to Tomcat . . . . . . . . . . . . . . . . . . . . . . . 106
Adding the Java Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Preparing the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Verifying the Tomcat deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Chapter 7 Deploying on WebSphere 113

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 114
Deploying on IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating an application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Starting the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Modifying the startup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Making configuration changes for distributed performance management
120
Changing the classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Setting the heap size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Modifying the PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Checking or changing the assigned port number on WebSphere 5.1 . 125
Checking or changing the assigned port number on WebSphere 6.0 . 125
Creating a new virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Assigning an alias to the virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Verifying the WebSphere Configuration . . . . . . . . . . . . . . . . . . . . . . . 128
Chapter 8 Deploying on WebLogic 131

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Deploying on BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Copying your performance management InitConfig.properties file . . . 138
Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 139

Contents
Creating the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Changing the CLASSPATH in WebLogic . . . . . . . . . . . . . . . . . . . . . . 141
Modifying the WebLogic environment script . . . . . . . . . . . . . . . . . . . . 142
Setting the Java Virtual Machine options for OLAP Intelligence and
performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Setting up the JAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 145
Chapter 9 Deploying on WebLogic 9.2 with the JDK 1.5 147

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Deploying on BEA WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Creating a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deploying performance management . . . . . . . . . . . . . . . . . . . . . . . . . 154
Setting the Java Virtual Machine options for OLAP Intelligence and
performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Setting required variables in startup script . . . . . . . . . . . . . . . . . . . . . 156
Modifying the WebLogic environment script . . . . . . . . . . . . . . . . . . . . 158
Changing the default parser and transformer . . . . . . . . . . . . . . . . . . . 158
Adjusting the size of the JVM permanent generation . . . . . . . . . . . . . 159
Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 161
Chapter 10 Deploying on Oracle Application Server 163

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Deploying with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuring the Class Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Changing Memory Allocation Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Copying your performance management InitConfig. properties file . . 169
Setting the PATH environment variable . . . . . . . . . . . . . . . . . . . . . . . 169

Contents
Changing the command line options for OLAP Intelligence or performance

management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Setting up the JAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 172
Verifying the Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Chapter 11 Deploying on Sun Java Application Server 177

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Deploying with Sun Java Application Server . . . . . . . . . . . . . . . . . . . . . . . 181
Configuring the Class Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Editing the security.policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Updating the JVM settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Verifying the Sun Java Application Server configuration . . . . . . . . . . 186
Chapter 12 Importing Objects to BusinessObjects Enterprise 187

Importing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Importing information from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . . 189
Importing objects from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . . 190
Importing information from BusinessObjects 5.x or 6.x . . . . . . . . . . . . . . . 193
Importing Application Foundation objects . . . . . . . . . . . . . . . . . . . . . . 193
Limitations on importing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Before importing from Application Foundation . . . . . . . . . . . . . . . . . . 195
Before importing from BusinessObjects 5.x/6.x . . . . . . . . . . . . . . . . . 196
Importing objects from BusinessObjects 5.x/6.x . . . . . . . . . . . . . . . . . 199
Using the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Specifying the source environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Specifying the destination environment . . . . . . . . . . . . . . . . . . . . . . . 220
Selecting the type of objects to import . . . . . . . . . . . . . . . . . . . . . . . . 222
Choosing an import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Updating previously imported objects . . . . . . . . . . . . . . . . . . . . . . . . . 228
Selecting specific objects to import . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Contents
Finalizing the import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Using text files with the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Text file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Importing from text files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Chapter 13 Custom SDK Deployments 245

Software Development Kit overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Java Server Pages environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Chapter 14 Upgrading and Migrating 249

What does this section cover? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
What this section does not cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Upgrading from Crystal Enterprise or from BusinessObjects Enterprise . 250
Preparing for upgrading or migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Disabling and stopping servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Migrating the CMS or APS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Importing content from BusinessObjects Enterprise, Crystal Enterprise, or
Crystal Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Upgrading other components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Migrating to performance management XI Release 2 . . . . . . . . . . . . . . . 267
About the Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Migrating the performance management repository . . . . . . . . . . . . . . . . 268
Migrating schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Migrating rules and named events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Migrating security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Managing rights at the object level in performance management XI . 270
Chapter 15 Uninstalling 271

Uninstalling BusinessObjects Enterprise from UNIX . . . . . . . . . . . . . . . . 272
Appendix A Business Objects Information Resources 273

Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . 274
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Contents
What’s in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Where is the documentation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Send us your feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . 275
How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Looking for the best deployment solution for your company? . . . . . . . 276
Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Index 279

Introduction to
BusinessObjects Enterprise
XI Release 2
chapter
1 Introduction to BusinessObjects Enterprise XI Release 2
What is BusinessObjects Enterprise?
What is BusinessObjects Enterprise?

BusinessObjects Enterprise is a flexible, scalable, and reliable solution for
delivering powerful, interactive reports to end users via any web application—
intranet, extranet, Internet or corporate portal. Whether it is used for
distributing weekly sales reports, providing customers with personalized
service offerings, or integrating critical information into corporate portals,
BusinessObjects Enterprise delivers tangible benefits that extend across and
beyond the organization. As an integrated suite for reporting, analysis, and
information delivery, BusinessObjects Enterprise provides a solution for
increasing end-user productivity and reducing administrative efforts.
About this guide

This guide provides you with information and procedures for installing
BusinessObjects Enterprise. This guide also includes detailed instructions for
the different installation modes available.
Who should read this guide

This guide is intended for the system administrator or IT professional who
needs to install BusinessObjects Enterprise. Familiarity with your overall
network environment, port usage, your database environment, and your web
server software is especially beneficial. If you are installing BusinessObjects
Enterprise on UNIX, you will require root privileges to perform some of the
setup procedures.
For more information about the product, consult the BusinessObjects
Enterprise Administrator’s Guide, the BusinessObjects Enterprise Getting
Started Guide, and the BusinessObjects Enterprise User’s Guide. Online
versions of these guides are included in the docs directory of your product
distribution. Once you install BusinessObjects Enterprise, they are also
accessible from InfoView, BusinessObjects Enterprise’s web-based interface.
Business Objects information resources

For more information and assistance, see Appendix A: Business Objects
Information Resources. This appendix describes the Business Objects
documentation, customer support, training, and consulting services, with links
to online resources.

Planning Your Installation
chapter
2 Planning Your Installation
Installation overview
BusinessObjects Enterprise provides an open and flexible architecture that
supports a multitude of deployment and configuration scenarios. Before you
install BusinessObjects Enterprise you should:
• Review your system to ensure that it meets the basic requirements for a
BusinessObjects Enterprise installation.
• Ensure that all machines that will be part of your BusinessObjects
Enterprise deployment can communicate properly with one another.
• Decide which BusinessObjects Enterprise components to install and
which of your own components to integrate.
• Determine where the components should be installed.
• Choose an installation method.
Part of this section focuses on how you should prepare your infrastructure
and details considerations you should consider when you set up your
environment. Preparations should include:
• Setting up server communication
• Choosing a server location
The other parts of this section list the core software requirements, the choices
available to you within the core requirements, and the install methods that you
can use when you install BusinessObjects Enterprise.
There are some decisions that should be made before you install. These
decisions include:
• Choosing a deployment environment
• Choosing a development environment
• Choosing a web application server
• Choosing a database server
At the end of this chapter, you will find an installation checklist. You can use
this checklist to help ensure you are prepared before you begin your install of
BusinessObjects Enterprise.
System requirements
Generally, the following components must be installed and configured
correctly before you install BusinessObjects Enterprise:
• Web application server (unless you install Tomcat with your installation of
BusinessObjects Enterprise)

System requirements 2
• Database software that is compatible with the CMS and the Audit
database (unless you install MySQL during the BusinessObjects
Enterprise installation)
• For information about hardware requirements, consult the
Platforms.txt file included with your product distribution, or see the
Support Platforms PDF available from the Business Objects support site.
For a detailed list of supported environments, consult the Platforms.txt file
included with your product distribution. This file includes specific version and
patch-level requirements for web application servers, web browsers, and
operating systems. For additional important information that may pertain to
your deployment, it is also strongly recommended that you consult the
Release Notes included with your product distribution (release.pdf).
Note:
• BusinessObjects Enterprise requires a database to store information
about the system and its users. For details, see “Database requirements”
on page 32 and “Preparing your existing database server” on page 34.
• If you are installing on VMWare, ensure your machine name does not
include any of the following characters: an underscore, a period, or a
slash.
UNIX permissions
To perform either a user or system installation on UNIX, the user account
under which the install is run must have read, write, and execute permissions
to the directory where BusinessObjects Enterprise will be installed. Root
privileges are not required to perform either a user or system install of
BusinessObjects Enterprise. In fact, if you attempt an installation with root
privileges, you will be unsuccessful.
However, if you run a system installation, you do require root authority to run
the system-level initiation script. This script, which is called setupinit.sh, is run
after the installation completes. This script creates entries into the run control
scripts for the Operating System that start up the BusinessObjects Enterprise
servers when the UNIX server is brought up and stops the BusinessObjects
Enterprise servers when a machine is shut down. A system application on
UNIX is analogous to running your Windows application as a service.

Setting up server communication
Setting up server communication

BusinessObjects Enterprise requires a database server and web application
server software to be installed and configured. You can either choose to
install this software during your installation, or use other supported third-party
software. If you choose to use supported third-party database or web
application server software, it should be installed before you install
BusinessObjects Enterprise. After you complete your install, you will also
need to configure the software so it integrates with BusinessObjects
Enterprise.
In addition, ensure that all BusinessObjects Enterprise machines can
communicate properly with one another:
• Each BusinessObjects Enterprise machine must be able to communicate
over TCP/IP with the machine that runs your Central Management Server
(CMS).
The CMS is responsible for maintaining a database of information about
your BusinessObjects Enterprise system, which other components can
access as required. The data stored by the CMS includes information
about users and groups, security levels, BusinessObjects Enterprise
content, and servers. For more information about the CMS, see
BusinessObjects Enterprise Administrator’s Guide.
• UNIX servers that run BusinessObjects Enterprise must have a fixed host
name. You must have root privileges to set or modify a fixed host name
on your system. However, you do not require root privileges to perform a
user install of BusinessObjects Enterprise. If you are unfamiliar with
these procedures, consult your UNIX system documentation.
Note: Please ensure your hosts use none of the following characters in
their name: an underscore, a period, or a slash.
• Ensure that your database client and server are set up to use Unicode
character encoding (such as UTF-8). Consult your database
documentation to determine the settings required for a Unicode
configuration.
For database clients, you must set certain parameters. The DB2 client,
for example, must use the DB2CODEPAGE value of 1208. The Sybase
database client typically requires the parameter LC_ALL and an
appropriate entry in the locales.dat file (located in the locales folder
of your Sybase installation directory).

Choosing a server location 2
When you install your database server, such as Oracle and Sybase, you
need to configure the server to use Unicode encoding for the character
data types. For other databases, such as DB2, you can create the CMS
database with Unicode settings on your existing database server.
• If you connect BusinessObjects Enterprise to a web application server,
the web application server must be able to communicate with all
BusinessObjects Enterprise machines.This communication is enabled by
the BusinessObjects Enterprise Software Development Kit (SDK), which
is installed when you select either the Java or .NET Web Component
Adapters (WCA).
If you plan to use a Java application server and your existing application
server does not include a version of the Java Development Kit (JDK)
supported by BusinessObjects Enterprise, you will need to install it.
Note: If you are installing BusinessObjects Enterprise in a firewall
environment, you will need additional configuration details. See the
“Working with Firewalls” section of the BusinessObjects Enterprise
Administrator’s Guide.
Choosing a server location

When planning your BusinessObjects Enterprise installation, you should also
consider where you will place your deployment’s servers:
• Your Crystal Reports Page Server, Desktop Intelligence Report Server,
Connection Server, Web Intelligence Report Server, Job Servers, and
Report Application Server communicate frequently with the database
servers containing the data in your published reports. To optimize data
retrieval and minimize network traffic, place your processing servers
close to your database servers (ideally, on the same subnet). If your
BusinessObjects Enterprise installation is distributed over a wide
geographic region, use server groups to create groups of nearby servers
to process reports.
The Central Management Server (CMS) stores data about users and
groups, security levels, published objects, and servers in the CMS
database. The CMS can also maintain a separate audit database of
information about user actions. To optimize CMS performance, place
your CMS on the same LAN as the database servers that host your CMS
database and the BusinessObjects Enterprise audit database.
The CMS can be clustered. If you are deploying more than one CMS,
ensure each machine that runs a CMS process experiences the same
latency to the system database.

Choosing a server location
Note: This guide does not cover how to cluster a CMS. For details on
how to configure a CMS cluster after your initial installation, see these
sections in the BusinessObjects Enterprise Deployment and
Configuration Guide:
• “Clustering Central Management Servers”
• “Adding clustered CMSs to the web.xml file” in the BusinessObjects
Enterprise Deployment and Configuration Guide.
Consult the following topics in the ”Managing and Configuring Servers”
section of the BusinessObjects Enterprise Deployment and Configuration
Guide for information on other factors that you may want to consider in
planning your BusinessObjects Enterprise installation:
• See “Working with firewalls” for information on how to configure
BusinessObjects Enterprise to work with your secured network.
• See “Planning your Deployment” for information on deployment
configurations, tuning and performance.
• See “Creating accessible reports” for information on how to create and
distribute reports that meet the needs of people with disabilities.
Choosing a database server

BusinessObjects Enterprise requires a relational database to store
information about the system and its users. The primary database, which is
maintained by the Central Management Server (CMS), is known as the CMS
database. A second database will be required if you plan to use
BusinessObjects Enterprise Auditor. Before you install, you should choose
which supported database server to use.
Note:
• In earlier releases of Crystal Enterprise, the Central Management Server
was called the Crystal Management Server or the Automated Process
Scheduler (APS), and the system database was called the APS
database.
• In earlier releases of <BOProductName>BusinessObjects, the system
database was known as the repository. For more information, see the
BusinessObjects 5.x to XI Release 2 Migration Guide or the
BusinessObjects 6.x to XI Release 2 Migration Guide.
• For a detailed list of supported database servers, see the
platforms.txt file included with your product distribution.

Choosing a server location 2
Using MySQL
MySQL database server is an open-source database that provides local data
storage. The setup program can configure MySQL along with your
BusinessObjects Enterprise components. If you already have MySQL
installed, the installation program creates the CMS database using your
existing database. During the installation of BusinessObjects Enterprise, you
specify what database server you will use and enter the required parameters
for authentication.
Using a supported database server

The CMS supports a number of third-party database servers, so you can
connect BusinessObjects Enterprise to your existing database infrastructure.
For a detailed list of supported database servers, see the platforms.txt file
included with your product distribution. If you do not have a database installed
on your machine you can use MySQL for your CMS database.
Sourcing the script that identifies the database environment variables

If you are using an existing database, you need a method to connect to it from
within BusinessObjects Enterprise. This is done through your database client.
In this document, the terminology used for this operation is to source the
script that identifies the database environment variables.
If you are integrating BusinessObjects Enterprise with a different web
application server than the version of Tomcat that can be configured with your
installation, you may need to source the environment script. This will set up
the required variables for BusinessObjects Enterprise.
Technically, sourcing your environment script involves running a script in your
current environment. When your database client is sourced from within
BusinessObjects Enterprise, all the required environment variables for your
database are set up and exported.
Your database client or the BusinessObjects Enterprise environment script
can be sourced from the command line, entered into a profile, or entered into
another script.
• To source your database client from the command line, you would
execute the script that sets up the variables required by your database
client to access your database. For example, in the bash shell, you could
type this:
source ora10env.sh

Choosing a deployment environment
• To source the BusinessObjects Enterprise environment script, you would

execute the script that sets up the variables required. For example, you
could add this to the Tomcat setenv.sh or the WebSphere startup script:
source ”<INSTALLDIR>/bobje/setup/env.sh”
Note that the syntax used to source a script varies based on the type of shell
you are using. Some UNIX shells use source as the syntax for this operation;
some UNIX shells use the . (dot operator). Please consult the
documentation for your shell to determine the appropriate syntax.
Shell name source . (dot operator)

Bourne shell (sh) no yes
Korn shell (ksh) no yes
Bourne Again Shell yes yes
(bash)
C shell (csh) yes no
Turbo C shell (tcsh) yes no
Choosing a deployment environment

Before installing BusinessObjects Enterprise, you should determine in which
environment you want to deploy BusinessObjects Enterprise so you know
what components you will require. Before you install, you should:
• Determine whether you plan to develop custom applications and, if so,
which web development environment to use.
• Determine the type of web application server you will use.
• Determine whether to install the Java Web Component Adapter.
• Determine whether or not you want to install Tomcat.
This section list the decisions you should make before you install and lists the
options available when you install.
Choosing a development environment

Java Server Pages (JSP)can be used in conjunction with BusinessObjects
Enterprise. Support for Crystal Server Pages (CSP) was deprecated on UNIX
platforms in the Crystal Enterprise 10 release.
Note: The following section applies to Crystal Enterprise 10 users only.

Choosing a deployment environment 2
In the period since CSP was developed, the cross-platform application server
market has become dominated by the Java Platform, Enterprise Edition
(J2EE) platform. As a result, Business Objects has moved away from the
proprietary CSP language and has instead developed tools and applications
in J2EE.
What does deprecating CSP mean?
• New BusinessObjects Enterprise features will not be made available in
CSP.
• You should not develop new custom applications in CSP.
• You should plan to port existing CSP applications to J2EE.
For further information on how to port CSP applications, contact Business
Objects Global Services.
Choosing an environment for new custom applications

While it will be possible to run CSP applications after CSP has been
deprecated, you should not develop new custom CSP applications on that
platform. Instead, you may consider building new applications using J2EE.
You should port existing applications to J2EE since CSP on UNIX was
deprecated in Crystal Enterprise 10.
Java Server Pages allow you to develop cross-platform J2EE applications
that use BusinessObjects Enterprise objects in conjunction with your own
custom objects, or a wide variety of objects from third parties.
Your choice of which web development environment to use to develop your
own custom applications will depend largely on your own technology
preferences. However, in making this decision, consider the technology
directions foreseen by Business Objects.
Choosing a web application server

BusinessObjects Enterprise requires a web application server to process the
server-side scripts that make up web applications. Before selecting a web
application server to use with BusinessObjects Enterprise, assess your
current environment and determine the platform on which to deploy
BusinessObjects Enterprise. Determine whether you plan to develop custom
applications and, if so, which web development environment to use.
If you plan to develop custom applications using the BusinessObjects
Enterprise Java SDK, you can use any of the supported web servers listed in
the Platforms.txt file that is included with your product distribution.

Choosing optional components
Choosing a Web Component Adapter

BusinessObjects Enterprise provides a web application—the WebComponent
Adapter (WCA) —that allows your web application server to run legacy
Crystal Enterprise CSP applications and to host the Central Management
Console (CMC). If you want to run the CMC supplied with BusinessObjects
Enterprise or run legacy CSP applications, the WCA must be installed on the
same machine as your web application server. OLAP Intelligence also
requires the installation of the WCA.
Note: The Web Connector that resided on the web server in earlier versions
of Crystal Enterprise is no longer required. Requests are now handled by the
web application server, and are passed on to the Web Component Adapter.
This solution also replaces the Web Component Server (WCS).
For UNIX installations, a Java version of the WCA is available. The Java Web
Component Adapter must be installed on a J2EE web application server.

Provided that you own the appropriate licenses to the applicable Business
Objects products, the following may be installed with BusinessObjects
Enterprise XI: OLAP Intelligence, Desktop Intelligence (formerly known as
BusinessObjects), performance management, Crystal Reports Explorer, Web
Intelligence and BusinessObjects Enterprise Auditor. For information about
licenses, contact your Business Objects sales representative.
For a list of all available components, see the “BusinessObjects Enterprise
Architecture” section in the BusinessObjects Enterprise Administrator’s
Guide.
OLAP Intelligence
OLAP Intelligence leverages the power of multidimensional OLAP databases
to help organizations gain insight and uncover hidden trends in their complex
business data. OLAP Intelligence’s easy-to-use drag-and-drop environment
and rich visualization techniques enable users to build and modify analysis-
focused Worksheets and create customizable charts that graphically
represent the data in workbooks. Through its tight integration with
BusinessObjects Enterprise, OLAP Intelligence workbooks can be viewed
through an intranet, extranet, or corporate portal. Alternatively, they can be
published to BusinessObjects Enterprise.

Choosing optional components 2
OLAP Intelligence supports the market leading OLAP servers including:
Hyperion Essbase, SAP Business Information Warehouse (BW), and IBM
DB2 OLAP Server.
Desktop Intelligence
Desktop Intelligence is an integrated query, reporting, and analysis solution
for business professionals that allows users to access data in their corporate
databases directly from their desktops. Desktop Intelligence makes it easy to
access this data, because users work with it in the business terms that are
familiar to them; they don’t require knowledge of technical database terms
like those used in SQL.
Note: This product was previously known as
<BOProductName>BusinessObjects in release 5.x/6.x. Desktop Intelligence
is now installed as part of the client install for BusinessObjects Enterprise. It
can no longer be downloaded from InfoView.
Performance Management
Performance management can be applied to any business process where
there is a need to view and analyze all the points of measure that define
corporate performance, productivity and profitability.
Performance management products help users track and analyze key
business metrics via management dashboards, scorecards, and alerting.
These products also allow goals to be set around metrics, and assigned to
owners—aligning people with strategies. These products also support group
decision making and analysis via integrated collaboration and workflow
capabilities.
Performance management allows groups to collaborate and make goal and
metric based decisions. Once a decision is reached, users can establish and
reuse decision and analysis workflow so others can efficiently analyze and
resolve common business problems.
Performance management includes the following products:
• Dashboard Manager
• Performance Manager
• Set Analysis
• Predictive Analysis
• Process Analysis
You can specify whether or not to install performance management with your

Note:
• Performance management products are only available as Java web
applications. There are no corresponding products available for .NET.
• Performance management was previously known as Application
Foundation. Process Analysis was previously known as Statistical
Process Control (SPC).
Auditor
Auditor is a web-based product that allows you to monitor and analyze user
and system activity. This information provides valuable insight into your
BusinessObjects Enterprise deployment, enabling you to optimize your
deployment.
If you choose to use Auditor, you can choose to configure auditor during or
after the installation. For details on how to configure Auditor after the
installation completes, see the BusinessObjects Enterprise Auditor’s guide.
Crystal Reports Explorer

Crystal Reports Explorer allows users to create and modify reports, design
layouts, and perform data analysis using a zero-client interface. This
functionality reduces IT reporting backlog by enabling users to create, save,
and redistribute personalized report views in BusinessObjects Enterprise.
Web Intelligence
Web Intelligence provides business users an easy to use interactive and
flexible user interface for building and analyzing reports on corporate data
over the web, on secured intranets and extranets.
Business Process BI Service

Business Process BI Service is a high-level web service designed to help
align an organization’s BI investments with the everyday running of its
business. Business Process BI Service will help an organization effectively
streamline business intelligence delivery, automate data refreshes and
integrate Business Objects Enterprise administration directly into common IT
processes. See the Business Process BI Service Guide for more information.

Choosing an install type 2
Choosing an install type
After you have decided what to install and where to install it, you will decide
how to install BusinessObjects Enterprise. The first step is to select either a
client or a server installation. When you perform a client install, only the client
components are installed; when you perform a server install, both the client
and server components are installed.
The second step is to choose the install method. BusinessObjects Enterprise
offers these choices.
• New installation
• Expand installation
• Custom installation
• Silent installation
The first few choices use the installation program to guide you through the
installation process. The Silent Installation is a scripted installation on UNIX
installed from the command line.
New installation
Performing a new installation is the easiest way to deploy BusinessObjects
Enterprise because all of the required client, server, and optional components
are installed by default onto one machine.
Difference between user and system installation

When you perform a new installation, on UNIX, you can choose between a
user and a system installation.
• When you choose a user installation, all the required components are
installed.
• When you choose a system installation, all the required components are
installed, In addition, the installation creates a system-level initiation
script. This script creates entries into the run control scripts for the
Operating System that start up the BusinessObjects Enterprise servers
when the UNIX server is brought up and stops the BusinessObjects
Enterprise servers when a machine is shut down.
Note: To perform a System installation, you do not require root-level
authority. However, to run the system-level initiation script root-level
authority is required.
You may want to choose a new installation if:
• You have not installed BusinessObjects Enterprise before.

Choosing an install type
• You want to install all components on the same machine.

• You don’t need to select specific components to install.
• You don’t have stringent disk space limitations.
Expand installation
In large or mission-critical deployments of BusinessObjects Enterprise, you
can scale your system to handle increased usage or to add fault-tolerance. In
a horizontally-scaled system, BusinessObjects Enterprise components are
installed on multiple machines; in a vertically-scaled system, multiple
BusinessObjects Enterprise server components can run on the same
machine. Note that on a single server, vertically-scaled system improves the
ability of BusinessObjects Enterprise to handle increased usage, but does not
increase the fault tolerance of the system.
Once BusinessObjects Enterprise is running on one machine, you can run the
Expand installation option to add server components, create a CMS cluster,
increase available resources, and distribute the processing workload.
You may want to choose an expand installation if:
• You have already completed your initial install of BusinessObjects
Enterprise.
• You want to add additional BusinessObjects Enterprise servers.
• You require fault tolerance.
• You want to improve system performance.
Tip: Consult the Scaling Your System section of the BusinessObjects
Enterprise Deployment and Configuration Guide for information on planning
how to best expand your installation to meet the needs of your organization.
Custom installation
The custom installation allows you to choose which components are installed.
You may want to perform a custom installation if you plan to use
BusinessObjects Enterprise in a distributed environment. It may be that you
have an existing web application server that resides on a different machine
than the one that has your BusinessObjects Enterprise core components.
A distributed installation has two stages. The first step is completed on the
machine where all BusinessObjects Enterprise components except the Web
Component Adapter will reside (see “Installing only the server components”
on page 59 for more information). The second step is completed on the
machine where the web server is installed (see “Installing only the Web
Component Adapter” on page 61 for more information).

Setting up your UNIX system 2
Alternately, you may want to do a custom installation when you want to
exclude some components installed by default with the new installation, or
install only a limited set of components. It is recommended that you run this
type of installation only when you are familiar with specific BusinessObjects
Enterprise components and their roles. If you perform a custom install without
being familiar with specific BusinessObjects Enterprise components and their
roles, you may inadvertently fail to install a required component.
You may want to choose a custom installation if:
• You are already familiar with the BusinessObjects Enterprise installation
program.
• Your deployment of BusinessObjects Enterprise servers will be
distributed over multiple computers. Perhaps your web application server
will be on one machine but other BusinessObjects Enterprise
components are elsewhere.
• You know exactly what components you require.
• You have disk space constraints.
• You have customized some of your own applications and you don’t want
the installation to overwrite them.
• You have an existing Crystal Enterprise 10 web desktop that you want to
continue using.
Silent installation
If you need to perform multiple installations and do not want to interrupt
people who are currently working on machines in your system, or if you want
to install BusinessObjects Enterprise with your own script, you can use the
silent installation command for BusinessObjects Enterprise. A silent
installation is one that you run from the command line.
On UNIX, you can install silently using a scripted installation. The scripted
installation is not recommended for custom installations. For more information
on performing a scripted installation on UNIX, see “Performing a scripted
installation” on page 65.
Setting up your UNIX system

BusinessObjects Enterprise integrates with your existing database and web
server software components, so the installation script needs to collect certain
information about your current system. Because UNIX systems can vary
significantly from site to site, the following sections detail the key tasks that
you must perform prior to installing BusinessObjects Enterprise.

Meeting the host name and network requirements

Your UNIX server must have a fixed host name before you run the installation
script. You must have root privileges to set or modify this information on your
system. If you are unfamiliar with these procedures, consult your UNIX
system documentation.
When installing BusinessObjects Enterprise on multiple machines, ensure
that each target machine is able to communicate over TCP/IP with the
machine that is running as your Central Management Server (CMS).
Note: If you are installing BusinessObjects Enterprise in a firewall
environment, you will need additional configuration details. See the “Working
with Firewalls” section of the BusinessObjects Enterprise Deployment and
Configuration Guide.
Creating an account, a home directory, and a login

environment
Create a specific user account and group under which the BusinessObjects
Enterprise background processes can run. You will log on as this user in order
to perform the remainder of the installation procedures. Although you will
require root privileges to set up this account, the account itself does not
require root privileges. Neither the installation scripts nor BusinessObjects
Enterprise itself needs to run as root.
Use your usual administrative procedures to perform these recommended
tasks.
To set up an account for installing BusinessObjects Enterprise
1. Create a new group or use an existing group. Create a new user account,
and set this user’s primary group to the new group. Assign a secure
password to the new user account.
2. Create the directory where you want to install BusinessObjects
Enterprise.
By default, the installation will use your current directory as its base
directory for the install, that is, the directory where you run install.sh.
You can override this default, with the directory of your choice at install
time.You will see the directory that you specify for the installation
directory referred to as INSTALLDIR throughout this document.
3. Set the new user’s HOME directory to the installation directory that you
created. When you run the installation script, you can choose a “user”
installation type so that all of the installed files are confined to the
directory that you specify here.

4. Ensure that the account you created has read, write, and execute
permissions on the new HOME directory.
5. Assign the new user a default login shell, and create or modify the
appropriate login script(s) for the user account. In particular, make sure
that the login script(s) set up a default login environment that meets these
requirements:
• All of the commands and utilities required by the install setup
program must be accessible in the PATH environment variable.
For details, see “Checking for required commands and utilities” on
page 29.
• The user’s login environment must set up the database environment
such that the install setup program can access your database
client software. For more information, see “Providing and verifying
connectivity to the CMS database” on page 36.
• The user’s login environment must set up a default locale that is
supported by your UNIX system and BusinessObjects Enterprise.
See “Setting the locale” on page 30.
Checking for required commands and utilities

In order for the install setup program to run correctly, the following
commands and utilities must be installed on your UNIX system:
/bin/sh pwd read touch

uname expr hostname sed
awk chown grep tail
tar id dirname gzip
stty ulimit which
These relatively standard commands and utilities should be available on most

UNIX distributions. However, if for any reason one of them is not available on
your system, download and install a version appropriate to your UNIX system.
It is recommended that you obtain any required files from your UNIX vendor.
Additionally, these commands and utilities must be accessible in the PATH
environment variable of the user account that you use when installing
BusinessObjects Enterprise. For details, see “Creating an account, a home
directory, and a login environment” on page 28.

Setting the locale

Before you install BusinessObjects Enterprise, set your operating system to
use one of the locales that BusinessObjects Enterprise XI supports for your
type and version of UNIX. Consult the platforms.txt file included with
your product distribution for a complete list.
If you are working at the console of a UNIX machine, you can select your
locale directly from the logon screen when you log on with the account from
which you will install BusinessObjects Enterprise. However, to ensure that
your operating system uses the correct locale whenever BusinessObjects
Enterprise runs, set the LC_ALL and LANG environment variables to your
preferred locale in your login environment. (For example, if you are using a C
shell, set these environment variables in the .login file.)
Tip: Type locale to check that all of the related locale environment
variables (such as LC_MONETARY, LC_NUMERIC, etc.) were properly set by
LC_ALL.
See the section on International Deployments in the BusinessObjects
Enterprise Administrator’s Guide for information on deploying
BusinessObjects Enterprise for a multilingual, world-wide audience.
Setting up an empty database for the CMS

BusinessObjects Enterprise requires a relational database to store
information about the system and its users. You can install a MySQL
database during the installation, or you can use an existing database. If you
want to create a new MySQL database during the installation, this section
does not apply to you.
If you want to use an existing database, you or your database administrator
must create a new database on your database server before you install
BusinessObjects Enterprise. We strongly recommend that this database be
used only for BusinessObjects Enterprise, and not contain other tables.
The following database servers are supported on UNIX:
• Oracle
• DB2
• Sybase
• MySQL
Note:
• See the Platforms.txt file included with your product distribution for a
complete list of supported database software and version requirements.

If you plan on integrating your own database with BusinessObjects
Enterprise, rather than installing MySQL with your installation, consult these
section for details on database setup requirements before you create your
database:
• “DB2 database setup requirements” on page 32
• “Oracle database setup requirements” on page 34
• “Sybase database setup requirements” on page 33
• “MySQL database setup requirements” on page 34
If you plan on integrating your own database with BusinessObjects
Enterprise, you will to prepare it before your installation. For procedural
details about how to prepare your database, after it has been created, see
“DB2 database setup requirements” on page 32. Here is a summary of the
steps that will be part of your preparation:
• Creating a new database.
Tip: You may want to name the new database bobjecms, and create a
new user account named bobje, however, this naming convention is not
required.
Note: If you have a previous release of BusinessObjects Enterprise you
cannot use your database from a previous release for BusinessObjects
Enterprise XI Release 2; You must create a new database for this
release. If you use a database from a previous release, you will destroy
any existing data. Create a new database instead, and after you have
completed your installation, you can migrate your old content to the new
current version’s database. See “Upgrading and Migrating” on page 249
for details.
• Creating a new user account and password for this database that will be
used by BusinessObjects Enterprise.
• Ensuring that this new account has permission to create, modify, and
delete tables and create procedures so that BusinessObjects Enterprise
can modify the database as required.
• Recording the name of the database, the user account, and the password
when you run the BusinessObjects Enterprise installation script.
During the installation process, the install script asks you if you want to
reinitialize the database. Choosing to do so causes the install script to create
new tables in the database to store BusinessObjects Enterprise data. (In
Oracle, choosing this option causes the install script to create
BusinessObjects Enterprise tables in the default schema of the user whose
name you provided during the install.)

Database requirements
Note: During a reinstall of BusinessObjects Enterprise, choosing this option

causes the install script to reinitialize the tables containing BusinessObjects
Enterprise data, destroying any existing data. You must choose to reinitialize
the database to proceed with the install. In either case, reinitializing the
database does not affect any other tables in that database or schema.
(See “Upgrading and Migrating” on page 249 for information on performing a
BusinessObjects Enterprise upgrade without overwriting existing data.)
Note:
• Consult your database server documentation and/or your database
administrator if you are unsure of the procedure for creating a new
database.
• Ensure that your database server is set up to use Unicode character
encoding (such as UTF-8). Consult your database documentation to
determine the settings required for a Unicode configuration. For database
servers such as Oracle and Sybase, during installation you need to
configure the server to use Unicode encoding for the character data
types. For other databases, such as DB2, you can create the CMS
database with Unicode settings on your existing database server.
Database requirements
Before you create the relational database that you want to integrate with
BusinessObjects Enterprise, consider the following sections that detail what
settings are required when the relational database is created and what
settings you should test before beginning your BusinessObjects Enterprise
install. The one requirement that applies, regardless of your databases type,
is that your relational database be set up to use Unicode character encoding
(such as UTF-8).
Note: No additional setup is required for SQL Server.
DB2 database setup requirements

If you are using a DB2 relational database with your BusinessObjects
Enterprise deployment, there are specific settings you need to select when
the relational database is created. It is not sufficient to modify these settings
after the relational database has been created.
When you create the relational database you will use with BusinessObjects
Enterprise:
• Ensure the CMS database is not partitioned.

Database requirements 2
If your DB2 CMS database is partitioned, you will have problems creating
the CMS database.
Note: This requirement does not apply to the Audit database. If you
want, you can use a partitioned DB2 database for the Audit database.
• Create the relational database with the specific settings.
Collating Sequence = "Identity"
Codeset = "UTF-8"
Territory = "XX"
If your DB2 database does not have the correct collating sequence
setting, the users and usergroup objects may not sort properly in the
Central Management Console. Replace XX with the code that is
appropriate to your code set and codepage for your location. Consult
your DB2 documentation for specifics.
Note: If you are using DB2 8.1, you require a C compiler that is installed and
configured to build SQL stored procedures. DB2 8.2 does not have this
requirement. SQL stored procedures are used in BusinessObjects Enterprise
when users are added to groups in the CMS. Please consult the DB2
documentation for details on how to configure the C compiler for SQL stored
procedures, and for determining what version of the C compiler is supported
on your platform.
After you create your database you will need to prepare it for the
BusinessObjects Enterprise install. For details, see “Preparing your existing
database server” on page 34. In addition, before you begin the install of
BusinessObjects Enterprise, you must ensure the DB2 environment variables
are set up correctly. For details, see “Testing DB2 environment variables” on
page 36.
Sybase database setup requirements

If you are using Sybase, when you create your database for the CMS, ensure
the page size is set to 8 KB.
Note: The Sybase database default page size is 2KB which is too small for
CMS. For CMS to run optimally, the page size must be 8KB. The page size is
set up during the database creation and it cannot be changed after the
database is set up.
database server” on page 34. In addition, before you begin the install of
BusinessObjects Enterprise, you must ensure the Sybase environment
variables are set up correctly. See “Testing Sybase environment variables” on
page 39.

Preparing your existing database server
Oracle database setup requirements

For an Oracle database there are no specific parameters, other than the
setting of UTF-8, that are required for BusinessObjects Enterprise to work.
However, before you begin the install of BusinessObjects Enterprise, you
must ensure the Oracle environment variables are set up correctly. For more
information, see “Testing Oracle environment variables” on page 41.
MySQL database setup requirements

For a MySQL database there are no specific parameters that are crucial for
BusinessObjects Enterprise to work, other than the setting of UTF-8. If you
select the option to install and configure MySQL with your installation, the
installation creates a MySQL database with the default settings for the CMS
database and the Audit database.
database server” on page 34.

After you have created your database, and before you install BusinessObjects
Enterprise, you or your database administrator need to prepare your own
database server so the CMS can connect to it.
During your installation, you will be asked whether you want to install MySQL
or use an existing database. If you specify that you will you use an existing
database, you will be asked for details about your database.
Although you are required to provide the details about your database during
the installation, you will not be asked to provide your database name unless
you are using an existing version of MySQL. This table summarizes the
information you will be required to enter to identify your database during the
installation if your are using SQL Server, Sybase, Oracle, or DB2.
Database type Information required at

install time
Sybase Sybase Server Name
DB2 DB2 database alias
Oracle tnsnames connect identifier

Preparing your existing database server 2
Note: On UNIX, the Sybase Server Name is a combination of the server
name and the port number which is set by your database administrator in the
interfaces file. The database the installation connects to is the default
database for the user profile. This default database is to is set by the DBA in
the profile of the account from which you will install and run BusinessObjects
Enterprise.
Prerequisites to database preparation

Before you prepare your database, you must have already created it. Ensure
you have created the database with these required settings:
• “DB2 database setup requirements” on page 32
• “Sybase database setup requirements” on page 33
• “Oracle database setup requirements” on page 34
To prepare your database
1. Create a new, empty relational database on your database server.
2. Create a new user and assign it a secure password.
3. Ensure that the new account has permission to create, modify, delete
tables and create procedures so that BusinessObjects Enterprise can
modify the database as required.
Note: If you are not the owner of the database, you will need to have
permissions to perform the necessary operations.
4. If you are using Sybase, Oracle, or DB2, ensure the following are set up
before you begin your installation:
Database type Ensure this has been

configured
Sybase Sybase Server Name
Oracle tnsnames connect identifier
DB2 DB2 database alias
During the install, you will be asked for information regarding your
database.
5. Record the these details as they will be required during your install:
• The name of your database, your Sybase Server Name, your Oracle
tnsnames connect identifier, or your DB2 database alias.
• The user account and the password authorized to the database.

Tip: You may want to record the required details on the Installation
Checklist at the end of this chapter so the information is available when
you install.
For information on how to create a new relational database, consult your
database server documentation or your database administrator. For
information on how to migrate your initial CMS database to another supported
database server later, see the BusinessObjects Enterprise Deployment and
Configuration Guide.
Providing and verifying connectivity to the CMS database

To create tables and write data to your new CMS database, the installation
scripts need to establish a connection to the database server. That is, when
you log on to UNIX with the user name from which you will perform the
installation, the default shell environment must include the appropriate
database environment variables and/or initialization files. Only then can the
installation setup program access the CMS database using your database
client software.
The environment variables and/or files required by the installation scripts
depend upon the type of database server you are running:
Additional database environment variables must be set in order for the
installation script to use the database client software properly. Before running
the installation script, test the shell environment of the account from which
you will install BusinessObjects Enterprise to verify database connectivity and
privileges. See the procedure that corresponds to your database.
• “Testing Sybase environment variables” on page 39
• “Testing Oracle environment variables” on page 41
• “Testing DB2 environment variables” on page 36
Testing DB2 environment variables

If you choose to connect to DB2 through a native connection, the installation
searches the current shell for the DB2INSTANCE environment variable. This
standard DB2 environment variable must be set in order for the install
script to utilize the DB2 client software.
If you are using an existing database, you need to source your database
client. For information about this process see “Sourcing the script that
identifies the database environment variables” on page 19.
Sourcing the script that identifies the database environment variables can be
done in one of two ways:

• The user who performs a system installation can modify the
BusinessObjects Enterprise script setupint.sh to add the command to
source your database client. However, root access is required to execute
this script. This script can be found at the following location: <install dir>/
bobje/init/setupint.sh. This method will source the database for all users.
“Sourcing the script that identifies the database environment variables”
on page 19 for information.
• Each person with a user installation can modify their profile and add the
command to source their database environment. This method can be
done anytime.
For example, if an DB2 database was required, an entry would be made
in the user profile to source the environment script used by DB2
(db2profile). Consult your database documentation for the name of its
environment script.
Note: Instead of sourcing the script that identifies the database environment
variables, you can manually set the environment variables required by your
database. However, if you manually set the environment variables, you will
need to set them again if the system is restarted.
Consult your database documentation and/or your database administrator if
the account shell environment from which you will install BusinessObjects
Enterprise has not yet been set up for your database client software, or if you
are unable to connect successfully to the database.
These steps will test whether the required environment variables are set:
To verify DB2 native connectivity through a database alias
1. Log on to the UNIX server with the user account and password which you
will use to do your install.
Note: This account should already be set up. See “Creating an account,
a home directory, and a login environment” on page 28 for more
information on setting up a UNIX account to use when you install
2. Echo the following environment variables and ensure that their values
correspond to your database client software installation.
Variable Value
DB2INSTANCE This variable defines the current DB2 database
instance.
INSTHOME This variable contains the path to the root
directory of your DB2 client installation

Variable Value
DB2DIR This variable contains the path to the root
directory of your DB2 installation (one level
above the DB2 bin and lib directories).
library path The library search path (LD_LIBRARY_PATH on
Solaris and Linux, LIBPATH on AIX, and
SHLIB_PATH on HPUX) must include the lib
directory of your DB2 client installation.
PATH The search path must include the bin directory
of your DB2 client installation.
This example checks the required variables and shows sample output
values.
$ echo $DB2INSTANCE
db2inst1
$ echo $DB2DIR
/opt/IBMdb2/V7.1
$ echo $LD_LIBRARY_PATH
/export/home/db2inst1/sqllib/lib
$ echo $PATH
/usr/bin:/usr/ucb:/etc:.:/export/home/db2inst1/sqllib/
adm:/export/home/db2inst1/sqllib/misc
3. Issue the following command to run the DB2 SQL tool:
db2
4. Issue the following command to connect to the desired database alias:
connect to db_alias user accountname using password
Replace db_alias and password with the appropriate values. If the shell
environment has been configured correctly, you are connected to DB2.
5. Issue the following command to ensure that the account has permission
to create tables:
create table sampletable (col_fld char(10) not null)
to delete tables:
drop table sampletable
7. Type terminate

Testing Sybase environment variables
If you choose to connect to Sybase through a native connection, the
installation searches the current shell for the SYBASE and SYBASE_OCS
environment variables. These standard Sybase environment variables must
be set in order for the install script to utilize the Sybase client software.
If you are using an existing database, you need to source the script that
identifies the database environment variables. For information about this
process see “Sourcing the script that identifies the database environment
variables” on page 19.
Sourcing the script that identifies the database environment variables can be
done in one of two ways:
done anytime.
For example, if a Sybase database was required, an entry would be
made in the user profile to source the environment script used by Sybase
(SYBASE.sh or SYBASE.csh). Consult your database documentation for
the name of its environment script.
Note:
• Instead of sourcing the script that identifies the database environment
variables, you can manually set the environment variables required by
your database. However, if you manually set the environment variables,
you will need to set them again if the system is restarted.
• Consult your database documentation and/or your database
administrator if the account shell environment from which you will install
BusinessObjects Enterprise has not yet been set up for your database
client software, or if you are unable to connect successfully to the
database.
To verify Sybase native connectivity through a server name

Variable Value
SYBASE This variable contains the path to the root
directory of your Sybase client installation (one
level above the SYBASE_OCS version
directory).
SYBASE_OCS This variable contains the name of the Sybase
version directory (one level above the Sybase
bin and lib directories).
SHLIB_PATH on HPUX) must include the lib
directory of your Sybase client installation.
of your Sybase client installation.
This example checks the required variables, and shows sample output
values:
$ echo $SYBASE
/opt/sybase/12.0
$ echo $SYBASE_OCS
OCS-12_O
/export/home/sybase/12.0/OCS-12_0/lib
$ echo $PATH
/usr/bin:/usr/ucb:/etc:.:/export/home/sybase/12.0/OCS-
12_0/bin
3. Issue the following command to run the Sybase SQL tool and connect to
the database server:
isql -U user -P password -S servername
Replace user, password, and servername with the appropriate
values. If the shell environment has been configured correctly, you are
connected to Sybase.
to create tables:
use aps

go
create table sampletable (def_field char(10))
go
sp_help sampletable
go
to delete tables:
drop table sampletable
go
sp_help sampletable
go
6. Type quit
Testing Oracle environment variables

If you choose to connect to Oracle through a native connection, the
installation searches the current shell for the ORACLE_HOME environment
variable. This standard Oracle environment variable must be set in order for
the install script to utilize the Oracle client software.
If you are using an existing database, you need to source your database
client. For information about this process see “Sourcing the script that
identifies the database environment variables” on page 19.
Sourcing your database client can be done in one of two ways:
done anytime.
For example, if an Oracle database was required, an entry would be
made in the user profile to source the environment script used by Oracle
(oraXXenv.csh or oraXXenv.sh where XX is replaced with the
version number). Consult your database documentation for the name of
its environment script.
Note:
• Instead of sourcing the script that identifies the database environment
variables, you can manually set the environment variables required by
your database. However, if you manually set the environment variables,
you will need to set them again if the system is restarted.

• Consult your database documentation and/or your database

administrator if the account shell environment from which you will install
BusinessObjects Enterprise has not yet been set up for your database
client software, or if you are unable to connect successfully to the
database.
To verify Oracle native connectivity through a TNS
Variable Value
ORACLE_HOME This variable contains the path to the root
directory of your Oracle client installation (one
level above the Oracle bin and lib
directories).
SHLIB_PATH on HPUX) must include the
lib32 directory of your Oracle client
installation.
of your Oracle client installation.
This example checks the required variables and shows sample output
values.
$ echo $ORACLE_HOME
/home/dbclient/oracle/10.1.0.3
/home/dbclient/oracle/10.1.0.3/lib32
$ echo $PATH
/usr/local/bin:/home/dbclient/oracle/10.1.0.3/bin
3. Issue the following command to run the Oracle SQL tool and connect to
the appropriate service name:
sqlplus accountname/password@tnsname

Installing the Java SDK 2
Replace accountname,password and tnsname with the appropriate
values. If the shell environment has been configured correctly, you are
connected to Oracle.
4. Issue the following command to ensure that account has permission to
create tables:
create table sampletable (field1 char(10));
to delete tables:
drop table sampletable;
to create procedures:
CREATE PROCEDURE test_proc (foo_in VARCHAR, bar_in
VARCHAR) IS
BEGIN
INSERT INTO test_table (foo, bar) VALUES (foo_in,
bar_in);
END;
to drop procedures:
DROP PROCEDURE TEST_PROC;
8. Type exit
Testing MySQL environment variables

If you are using an existing MySQL database, ensure the following variable is
set up for the user who will install BusinessObjects Enterprise XI R2:
MYSQL_HOME
If this variable is not set up, and you have specified that you are using an
existing MySQL database, the installation will not proceed and you will
receive an error message. Consult the documentation for MySQL for
information on how to configure the MySQL.
Installing the Java SDK

If your Java web application server does not install the Java SDK as part of its
installation process, you must install the J2SE SDK first, before deploying the
BusinessObjects Enterprise Java SDK. You can download this software from
java.sun.com.
Note: If you choose to install Tomcat at the same time you install
BusinessObjects Enterprise, this is not necessary.

Installation checklist
Read the documentation on the Sun web site and select a version of the Java
SDK that is compatible both with your application server and with the
BusinessObjects Enterprise Java SDK. Consult the Platforms.txt file
included with your product distribution for more information.
Configuring the Java environment variable

After installing the Java SDK you must set the JAVA_HOME environment
variable. If your Java web application server installs the Java SDK as part of
its installation process, install the application server first, and then set the
environment variable.
You need to know the directory path containing your Java SDK bin directory.
To set the JAVA_HOME environment variable on UNIX
2. Type setenv JAVA_HOME InstallDirectory (if you are using a C shell).
Type JAVA_HOME= InstallDirectory (if you are using a Bourne shell).
InstallDirectory is the directory containing your Java SDK bin directory.
3. To confirm that you’ve set the environment variable correctly, type echo
$JAVA_HOME
4. Using a text editor such as vi, add the command to set JAVA_HOME to
the login environment for the account from which you will install
BusinessObjects Enterprise. For example, if you are using a C shell, add
the command to your .login file.
This ensures that the value of JAVA_HOME is correctly set each time you
log on to the account.
❏ Have you tested that all machines that will run BusinessObjects
Enterprise can communicate properly?
❏ Have you tested the database connection between the machine where
your CMS database will reside and where the Central Management
Server will be installed?
❏ Have you decided which database to use with BusinessObjects
Enterprise?
❏ If you are using your own database server, have you created a database
for the CMS?

Installation checklist 2
❏ If you plan to connect remotely to install, have you ensured your terminal
setting is set to VT100 before beginning the installation?
❏ If you are using your own database server and plan to use Auditor, have
you created an auditing database?
❏ If you are using your own database server, have you created a userid and
password with access to your existing database (if you are integrating
your existing database server software), so that the installation can
access your database to configure the CMS database?
❏ If you are using your own database server, have you made sure you can
log on to the database with the ID and setup tables?
❏ Have you ensured that any existing database you will connecting to has
been configured correctly?
❏ Have you verified you are using a supported locale?
❏ Have you decided whether or not you will develop custom applications?
❏ Have you decided what web application server to use?
❏ If you are not using Tomcat, have you made sure your existing web
application server has the JDK installed?
❏ If you are not using Tomcat, is your web application server already
installed and configured?
❏ Do the BusinessObjects Enterprise system requirements match your
UNIX setup?
❏ If you are installing on VMWare, have you ensured your machine name
does not include any of the following characters: an underscore, a period,
or a slash?
❏ Does the UNIX user account under which the install is run have read,
write, and execute permissions to the directory where BusinessObjects
Enterprise will be installed?
❏ If you’re using UNIX, and you are using an existing database, have you
sourced your database client so that all the required environment
variables are set up?
❏ If you are using DB2 or Sybase, have you verified that your database was
created with the correct settings? (Some settings can’t be modified after
the database has been created.)


Installing BusinessObjects
Enterprise on UNIX
chapter
3 Installing BusinessObjects Enterprise on UNIX
BusinessObjects Enterprise allows you to run all server components on a
UNIX server. Users then connect to BusinessObjects Enterprise over the
Web with a supported web browser.. The installation can place the necessary
run control scripts in the relevant directories for automated startup (requires
root privileges), or you can confine the installation to a particular directory.
After you finish the installation and setup procedures, the various core server
components run as background processes. You can then deploy the
BusinessObjects Enterprise Launchpads (including InfoView), and the Web
Component Adapter as web applications on your application server.
BusinessObjects Enterprise on UNIX uses the BusinessObjects Enterprise
Java SDK on a Java web application server to deliver reports over the web. A
Java version of InfoView and the Web Component Adapter (which supports
legacy CSP applications, and the Central Management Console) provide a
complete suite of web-based interfaces for users and administrators.
When you install the BusinessObjects Enterprise server components on a
UNIX machine, you can connect remotely to BusinessObjects Enterprise with
the Publishing Wizard and the Import Wizard. However, these client
applications must be installed on Windows. For details, see “Performing a
client tool installation” on page 63.
Note: Before you run the interactive installation setup program (install), it
is strongly recommended that you read through the details and procedures
provided in Chapter two of this guide, “Planning your Installation.”
Setting up product distribution

This section shows how to distribute BusinessObjects Enterprise so that you
can perform an installation.
You can perform this installation remotely through a telnet session, or locally
through a terminal window. If you will connect remotely to install
BusinessObjects Enterprise, be sure to set your terminal settings to VT100
before beginning the installation.
There are two ways you can set up the product distribution:
• Before you run install.sh, you can copy the installation files to a
temporary location.
• When you run install.sh, you can specify the temporary location to
place the installation distribution.

Installing BusinessObjects Enterprise on UNIX
Setting up product distribution 3
Before following this procedure, ensure that you have set up your UNIX
system appropriately. For details, see “Setting up your UNIX system” on
page 27.
Running the product distribution directly from a CD

By default, the installation will use your current directory, that is, the directory
you run install.sh from, as its base directory for the install. If you run
install.sh without copying the files to a temporary location, you will be
prompted to specify a temporary location for the install. After you specify the
temporary location, this will happen:
• The installation files will be copied to that temporary location.
• The installation program will exit.
You are then required to go to the temporary location you specified, and then
run install.sh from that location.
Copying the product distribution to your machine

By default, the installation will use your current directory, that is, the directory
you run install.sh from, as its base directory for the install. You may want
to copy the product distribution to directory on your machine and run
install.sh from there. The advantage of this option is that when you run
install.sh, you will not be prompted for a temporary location to put the
files.
To copy the product distribution to your machine
1. Log on to your UNIX system under the new account designated for
installing BusinessObjects Enterprise.
For details on how to create this account, see “Creating an account, a
home directory, and a login environment” on page 28.
2. Copy the installation files from the product distribution to a temporary
directory with this command where /mnt/cd is mapped to the CD drive
and tmp is a temporary directory where you want to store the installation
files:
/mnt/cd/install -t /tmp/
. Repeat this process for each DISK contained in the product distribution.
3. Proceed to “Beginning your installation” on page 50.
4. Run install.sh from the first CD.

Beginning your installation

The following instructions lead you through the initial steps of installing
BusinessObjects Enterprise on UNIX. In this stage you do the following:
• Choose the language for the installation.
• Agree to the licence terms.
• Enter the product key codes.
• Select where to install.
• Choose between a user and system install.
Difference between user and system installation

When you perform a new installation, on UNIX, you also can choose between
a user and a system installation.
installed.
also installed, however, in addition, the installation creates a system-level
initiation script. This script creates entries into the run levels for the
when the Unix server is brought up and stops the BusinessObjects
Note: To perform a System installation, you do not require root-level
authority. However, to run the system-level initiation script root-level authority
is required.

To begin your installation
1. Mount the device that contains the installation files.
2. Type ./install.sh
Note: If you run install.sh without copying the files to a temporary
location, you will be prompted to specify a temporary location for the
install. See “Running the product distribution directly from a CD” on
page 49 for an explanation of why this is required and how to proceed.
3. Select the language for your installation, and then press Enter.
4. Read the software license agreement. Type y to agree to the terms and
continue with the setup program.

Beginning your installation 3
5. Choose to install only BusinessObjects Enterprise or to install both
BusinessObjects Enterprise and Performance Management.
• To install only BusinessObjects Enterprise, type your
BusinessObjects Enterprise product activation keycode in the first
Product Keycode field on the screen, and press Enter.
• To install both BusinessObjects Enterprise and Performance
Management:
a. Enter your BusinessObjects Enterprise product activation
keycode in the first Product Keycode field on the screen.
b. Enter an x in the Install Performance Management field, and use
the TAB key to exit from the field.
The Product Keycode field will be cleared.
c. Enter the Dashboard Manager key for your Performance
Management product activation keycode in the second Product
Keycode field on the screen.
Note: The performance management product key you type here
only enables that one product. To enable other performance
management products, you need to enter the license keys for those
products in the Central Management Console (CMC) after the
installation is complete. To find out how to do this, see the
6. Choose where to install the product.
• To accept the default installation directory, which is your current
directory, press Enter.
• To create your own directory, use the Backspace key to remove the
current directory and replace it with your own path for the installation
directory.
7. Select the type of installation you want to perform.
Your installation options are User and System.
Note:
• For details on the difference between the two available new install
types, see “Difference between user and system installation” on
page 50.
• To perform a System installation, you do not require root-level
authority. However, to run the system-level initiation script root-level
authority is required.

Installation options
After you perform a System installation, there are a few additional steps
you must perform. For details about these additional steps, see “Finishing
a system installation” on page 56.
You will now be prompted to choose the type of installation you want to
perform. For further instructions, see one of the following sections:
• “Performing a new installation” on page 53
• “Performing an expand installation” on page 57
• “Performing a custom installation” on page 58
• “Performing a client tool installation” on page 63
• “Performing a scripted installation” on page 65
The following step applies if you select a system installation:
• “Finishing a system installation” on page 56
You can choose between five installation types: new, expand, custom, client
and silent.
New installation
Performing a new installation is the simplest way to deploy BusinessObjects
Enterprise because all the required components are installed by default onto
one machine.
When you perform a new installation, on UNIX, you also can choose between
a user and a system installation.
installed.
also installed, however, in addition, the installation creates a system-level
initiation script. This script creates entries into the run levels for the
when the Unix server is brought up and stops the BusinessObjects
Note: To perform a System installation, you require root-level authority
See “To perform a new installation” on page 53 for instructions.
Expand installation
Expand installation option to add server components, create a CMS cluster,
increase available resources, and distribute the processing workload.

Installation options 3
See “To perform an expand installation” on page 57 for instructions.
Custom installation
The custom installation allows you to choose which components are installed.
You may want to perform a custom installation if you plan to use
BusinessObjects Enterprise in a distributed environment.
See “To perform a custom installation” on page 58 for instructions.
Client installation
Choose to perform a client installation if you want to install tools on a
Windows machine.
See “To install the client tools” on page 64 for instructions.
Scripted installation
If you need to perform multiple installations and do not want to interrupt
people who are currently working on machines in your system, or if you want
to install BusinessObjects Enterprise with your own script, you can use the
installation command for BusinessObjects Enterprise. A scripted installation is
one that you run from the command line.
See “Performing a scripted installation” on page 65 for details.
Performing a new installation

Performing a new installation is the simplest way to deploy BusinessObjects
Enterprise because all the required and optional components are installed by
default onto one machine.
Note: The Installation Type screen in the following procedure appears after
you have completed the initial set up of the BusinessObjects Enterprise
installation. For more information, see “Beginning your installation” on
page 50.
To perform a new installation
1. From the list of options on the Installation Type screen, select New.
2. Choose whether to use an existing database or to install MySQL.
• If you choose to use an existing database:
a. Select Use an existing database, and then press Enter.
b. Select the database type for your CMS.
You can choose from MySQL, Oracle, DB2, or Sybase.
c. Provide information about your database in the fields provided,
and press Enter.

Database Information required

type
MySQL Host Name
User ID for CMS
Password for CMS
MySQL port number
Database name for CMS
Oracle TNS name
User ID for CMS
Password for CMS
CMS port number
DB2 Alias name
User ID for CMS
Password for CMS
CMS port number
Sybase Sybase Service name
User ID for CMS
Password for CMS
CMS port number
d. If you want to enable an auditing database, type an x in the field
provided.
e. Provide information about your new auditing database.
Database Information required

type
Auditing Database name
Database port number
User ID
Password
f. Decide if you want to reinitialize the database.
Reinitialization of the BusinessObjects Enterprise database will
erase all previous content in that particular database.
Note: If you are using an existing database, you need to source your
database environment variable so the CMS can access it after a
system reboot. This can be done one of two ways:

• Someone with root access can modify the BusinessObjects
Enterprise script BobjEnterprise115 and add the command to
source your database environment. This script can be found at
the following location: <installdir>/bobje/init/
BobjEnterprise115. This method will source the database
environment variable for all users.
• Each user can modify their own profile and add the command to
source their database environment. This method must be done
by each user.
For more information on sourcing your database, please refer to
“DB2 database setup requirements” on page 32.
• If you choose to install MySQL:
a. Select Install MySQL, and press Enter.
b. Provide information for your new MySQL database on the first
information-input screen, and then press Enter.
Database type Information required

MySQL Port number
Database administrator’s password
c. Provide information for your new MySQL database on the
second information-input screen, and then press Enter.
Database type Information required

MySQL MySQL CMS name
MySQL Audit database name
User ID for MySQL CMS database
User ID for MySQL Audit database
Password for CMS and Audit databases
d. Type the port number for the CMS, or accept the default of 6400.
3. Choose whether to use an existing Java application server or to install
Tomcat.
To install Tomcat:
a. Make sure Install Tomcat is highlighted, and then press Enter.
b. Type the HTTP, the Redirect and the Shutdown ports for Tomcat, or
press Enter to accept the defaults.

Note: The default ports are 8080 (HTTP), 8443 (Redirect), and 8005
(Shutdown).
4. Press Enter to start the installation.
When the new installation is finished, the setup program starts the servers as
daemons and then enables each server that is registered with the CMS. To
control the servers manually, use the ccm.sh script. For preliminary details,
see “Using ccm.sh to start the BusinessObjects Enterprise servers” on
page 71.
You must now deploy InfoView and the BusinessObjects Enterprise
Launchpads. If you do not install Tomcat when you install BusinessObjects
Enterprise, these components must configured and deployed before you use
them.
Consult the following sections for information how to deploy and what to
configure on your web application server:
• “Deploying on Tomcat” on page 95
• “Deploying on Sun Java Application Server” on page 177
• “Deploying on Oracle Application Server” on page 163
• “Deploying on WebSphere” on page 113
• “Deploying on WebLogic” on page 131
For more information about the system architecture of an installation of
BusinessObjects Enterprise, see the architecture chapter of the
For information on deploying the Web Component Adapter, including
information on deploying multiple WCAs, see “Installing only the Web
Component Adapter” on page 61.
Note: After you complete your new installation, you will need to configure
your Java web application server to work with BusinessObjects Enterprise.
For details, see the chapter that applies to your Web Application Server:
Finishing a system installation

If you chose to perform a system installation, the setup program script
prompts you to run the BobjEnterprise115 script after it is finished. The
BobjEnterprise115 script copies the run control scripts to your /sbin/rc#
directories. When implemented, these run control scripts start/stop the
BusinessObjects Enterprise servers on system startup/shutdown.

Note: To run the system installation, you must log on using a normal account.
After installation, however, you must have root privileges to run the
setupinit.shscript. This script copies the BobjEnterprise115 to the
/sbin/rc# directory.
Performing an expand installation

Expand installation on other machines to add server components, create a
CMS cluster, increase available resources, and distribute the processing
workload.
How you expand your system depends largely on your current configuration
and your reporting requirements. It is strongly recommended that, before you
expand your installation, you consult the BusinessObjects Enterprise
Administrator’s Guide for sample configurations, general scalability
considerations, information about CMS clustering, and so on.
Note:
• If you are adding another CMS, first set up the appropriate database
client software or ODBC Data Source Name (DSN) on the local machine.
The new CMS must connect to the CMS database in the same manner
as the existing CMS. Also ensure that you have the database user name
(Login ID) and password that the existing CMS uses to connect to the
CMS database. If you are unfamiliar with CMS clusters, see the
• The Installation Type screen in the following procedure appears after you
have completed the initial set up of the BusinessObjects Enterprise
page 50.
To perform an expand installation
1. On the Installation Type screen, choose Expand.
Note: The Installation Type screen appears after you have completed
the initial setup of the BusinessObjects Enterprise installation. For more
information, see “Beginning your installation” on page 50.
2. Provide the name and port number of the existing CMS, then press Enter.
3. From the list of servers, choose those you want to add to the existing
system.
Note: Servers marked with an x will be installed.
4. If you are adding a CMS, you are prompted to:
a. Choose the type of database for the existing system.

b. Provide the location and connection information for the database.

c. Decide if you want to install a new auditing database.
• If no, type a space, and then press Enter.
• If yes, type an x and enter the information for the new auditing
database in the fields provided.
5. When you reach the final screen expand option (which displays the
installation directory), press Enter to complete the installation.
Performing a custom installation

The custom installation option allows you to install specific features. You may
want to perform a custom installation if you plan to use BusinessObjects
Enterprise in a distributed environment. It may be that you have an existing
web application server that resides on a different machine than the one that
has your BusinessObjects Enterprise core components.
A distributed installation has two stages. The first step is done on the machine
where the BusinessObjects Enterprise components will reside, see “Installing
only the server components” on page 59. The second step is done on the
machine where the web server is installed, see “Installing only the Web
Component Adapter” on page 61 for more information. If you want a
distributed installation of performance management, see “Performing a
distributed install of performance management” on page 62 for more
information.
You customize the installation in the setup program’s Features dialog box. On
the Features screen, the markers in the feature tree indicate whether the
feature and its subfeatures will be installed or not:
• [X] means that the feature and all its subfeatures will be installed.
• [~] means that the feature and some of its subfeatures will be installed.
• If no marker appears, the feature or subfeature is either unavailable or
will not be installed.
To select the configuration and location of a feature or subfeature, click its
marker.
page 50.
To perform a custom installation
1. On the Installation Type screen, choose Custom.
2. On the Features screen, choose the features you want to install.

Note: Features marked with an x will be installed.
3. If you chose to install “server components,” you will be prompted to
choose between using an existing database as the CMS repository, or
installing MySQL as the default repository.
• To use an existing repository:
a. Select Use an existing database.
b. Choose from the listed database types.
c. Provide the connection information for the database.
• To install MySQL as the default repository:
a. Select Install MySQL.
b. Provide connection information for the new MySQL database.
c. Provide the server name and port number for the CMS
database.
4. If you are installing a Central Management Server, you will be prompted
to cluster it with an existing CMS. Unless you want to cluster this new
system with an existing system, select No, and press Enter.
5. When you reach the final screen of the custom installation (which
displays the installation directory), press Enter to complete the
installation.
Consult the BusinessObjects Enterprise Administrator’s Guide for information
about scaling your deployment across multiple machines.
The remainder of this section explains the following types of custom
installations:
• “Installing only the server components” on page 59.
• “Installing only the Web Component Adapter” on page 61.
• “Performing a distributed install of performance management” on
page 62.
Installing only the server components

Install the server component onto a machine that you have set aside for use
by BusinessObjects Enterprise.
When you perform this installation, the server components are installed, the
default user and group accounts are created, and the sample reports are
published to the system. When the installation is complete, the servers are
started

Note: When you install only the client and server components, neither
Tomcat nor the WCA is installed. See “Installing only the Web Component
Adapter” on page 61 for details on either of the following:
• If you want to install the WCA to connect with your existing web server on
a separate machine.
• If you want to install Tomcat and the WCA on the machine designated as
you web application server.
Note: The procedure which follows assumes you have already begun your
installation, if this is not the case, see “Beginning your installation” on
page 50.
To install only the server components
Note: The Installation Type screen appears after you have completed
the initial setup of the BusinessObjects Enterprise installation. For more
information, see “Beginning your installation” on page 50.
2. On the Features screen, expand Server Components.
3. Expand Servers.
Tip: Press Space to expand or collapse a product folder.
4. Scroll down until you see Web Component Adapter.
Tip: You will not see this option until you use the down arrow button to
scroll down multiple lines on this screen.
5. Type “X “ to deselect Web Component Adapter, and then press Enter.
6. Choose between using an existing database as the CMS repository, or
installing MySQL as the default repository.
• To use an existing repository:
a. Select Use an existing database.
b. Choose from the listed database types.
c. Provide the location and connection information for the
database, and then press Enter.
• To install MySQL as the default repository:
a. Select Install MySQL.
b. Provide the connection information for the new MySQL CMS
database and the MySQL Audit database.
c. Provide the server name and port number for the MySQL CMS
database the MySQL Audit database, and then press Enter.
7. On the Installation dir screen, do one of the following:

• Specify the installation directory, and then press Enter to complete
the installation.
• Accept the default directory, and then press Enter to complete the
installation.
Installing only the Web Component Adapter

Install the WCA on the machine running your web application server. Before
you install the WCA, you must have installed the server components. For
detailed steps, see “Installing only the server components” on page 59.
page 50.
To install only the Web Component Adapter
2. Type “X” to deselect everything except Server Components on the
Features screen, and then expand Server Components.
3. Expand Servers.
Tip: Press Space to expand or collapse a product folder.
4. Scroll down until you see Web Component Adapter.
Tip: You will not see this option until you use the down arrow button to
scroll down multiple lines on this screen.
5. Type “X “ to deselect Central Management Server and then press the
down arrow once.
6. Repeat the previous step until all servers except the Web Component
Adapter have been deselected, and then press Enter.
Tip: You will have to you use the down arrow button to scroll down
multiple lines on this screen to see the options not initially visible.
7. Enter the CMS name and the CMS port number.
8. Choose between installing Tomcat or using an existing Java application
server.
• To install Tomcat:
a. Select Install Tomcat, and then press Enter.
b. Type the redirection, the shutdown and the http request port
numbers, and then press Enter, or Press enter to accept the
default port numbers.

Note: Database information is not rrequired when configuring

Tomcat.
• To use an existing Java Application server, select Use an existing
Java application Server, and then press Enter.
9. On the Installation dir screen, press Enter to complete the installation.
Note: The WCA installation does not automatically install the EPM
destkop.war so you have to copy the EPM desktop.war and the file tree from
the core installation into the WCA installation and then you have to deploy the
.war file. For information on deploying the war file, see “Deploying the WAR
files” on page 99.
Performing a distributed install of performance management

If you want to have BusinessObjects Enterprise installed on one machine and
want to have performance management installed on a separate machine with
your web application server, you will have to do the following:
• Perform a new install.
• Perform an expand install.
• Create a new desktop.war file.
• Modify the Tomcat properties.
Note: The following procedure will refer to Server 1 which contains
BusinessObjects Enterprise components and Server 2 which contains web
applications. This procedure assumes you already have Tomcat and the Web
Component Adapter installed on Server 2.
To perform a distributed install of performance management
1. Perform a new installation and only enter the product keycode for
BusinessObjects Enterprise on Server 1 which contains BusinessObjects
Enterprise components.
For more information, see “Performing a new installation” on page 53.
2. When you see the option to install Tomcat or use an existing web server,
select use an existing web server.
The WAR files for BusinessObjects Enterprise can be found in the
following location on Server 1: <INSTALLDIR>bobje/enterprise115/java/
applications
3. Perform an expand install on Server 2 on your web server.
For more information, see “Performing an expand installation” on
page 57.
4. Provide the CMS Name and port number from Server 1.

5. Ensure Add additional Processing servers remains selected, and type
“X” beside each server type you want to deselect, and then press Enter.
6. Press Enter, to start the installation on Server 2.
A file called pm11.boar and a tool called mergeboar.jar will be created
during your install.
7. Deploy the WAR files. See “Deploying on Tomcat” on page 95 for more
information.
To create a new desktop.war file
1. Stop Tomcat.
2. Undeploy desktop.war.
3. Copy the desktop WAR file from Server 1 to a backup directory.
<INSTALLDIR>\backup_of_desktop.war
4. Use the mergeboar.jar tool to create the new desktop.war with the
backup of desktop.war from Server 1 and pm11.boar from Server 2. Run
the following command from Server 1:
java -jar "<INSTALLDIR_SERVER_2>/
Performance_Management_115/setup/mergeboar.jar"
"<INSTALLDIR_SERVER_1>/backup_of_desktop.war"
"<INSTALLDIR_SERVER_2>/Performance_Management_115/
pm11.boar" "<INSTALLDIR_SERVER_1>/bobje/enterprise115/
java/applications/desktop.war"
To modify the Tomcat properties

1. Open the setenv.sh for Tomcat.
2. Add the following information to the file:
JAVA_OPTS="$JAVA_OPTS -
Daf.configdir=<BO_INSTALL_DIR_SERVER_2>/
Performance_Management_115 -Xmx400m"r
3. Save and close the file.
4. Restart Tomcat.
The new desktop.war file will be deployed.
Performing a client tool installation

This section shows you how to perform an installation that installs only the
client tools on a Windows machine. These tools include:
• The Publishing Wizard
• The Import Wizard

• The Data Source Migration Wizard

• The Business View Manager
• Repository Migration Tool
• Desktop Intelligence
• Universe Designer
• Software Development Kits (SDKs)
• Report Conversion Tool
• Desktop Intelligence
• Universe builder
These client tools are not needed by users who access InfoView or the
Central Management Console (CMC) administrative web application. Rather,
these additional tools are provided for users who are responsible for
publishing or creating multiple reports or for moving objects between
systems. Some of these tools are used for migration of existing documents
from earlier product versions or creating new documents.
If you install the BusinessObjects Enterprise servers on a UNIX machine, you
can connect remotely to BusinessObjects Enterprise with the client tools.
However, the client applications must be installed on Windows.
Note: The client installation does not generally require a product activation
keycode. However, Desktop Intelligence does require that a key be entered in
the CMC after the install completes to enable the content type.
To install the client tools
1. Run setup.exe from the root directory of your product distribution unless
Autoplay is enabled for your CD-ROM drive.
When you start the installation, the Microsoft Windows Installer may need
to be installed or upgraded on the local machine. If so, the Wise
Installation Wizard performs the necessary modifications and prompts
you when finished. Click Yes to restart the machine and resume the
installation automatically.
2. Select which language to install from the list, and then click OK.
In a few moments you will see the Welcome to BusinessObjects
Enterprise Installation Wizard dialog.
3. Click Next.
4. Click the I accept the License Agreement button on the License
Agreement dialog, and then click Next.
5. Select Perform Client Installation, and then click Next.

6. Specify the location to install, in the Directory Selection dialog box, and
then click Next.
7. Click Next.
The installation of files begins immediately. When the installation program has
finished copying files, follow any additional instructions that appear.
Performing a scripted installation

A silent installation (Windows) or scripted installtion (UNIX) is one that you
run from the command line to automatically install BusinessObjects
Enterprise on any machine in your system, without the installation program
prompting for information during the installation. To install silently, run the
install.sh setup program, adding parameters that provide information for
installation settings and directory paths. By customizing the parameters of the
install command, you can automatically install BusinessObjects Enterprise
on any machine in your system.
This type of installation is particularly useful when you need to perform
multiple installations. You can also use the silent installation script in your own
scripts. For example, if your organization uses scripts to install software on
machines, you can add the silent BusinessObjects Enterprise installation
command to your scripts.
The silent installation command consists of the command install, followed
by the location of the installation executable file, and a number of parameters
that provide information about the installation. For example:
The following example would perform an english new user installation with
these options:
• BusinessObjects Enterprise
• Performance management
• Tomcat
• MySQL
• Auditor
• Database reinitialized
./install.sh -c en -INSTALLDIR /program/business/boe_115 -
BOBJELICENSEKEY 00000-1111111-2222222-0000 -
BOBJEINSTALLLOCAL user -INSTALLTYPE new -CMSPORTNUMBER
13888 -DBTYPE MySQL -SERVICENAME boe -INSTALLMYSQL yes -
DATABASEUID hkrishna -DATABASEPWD sa -REINIT yes -
MYSQLROOTPWD sa -SERVICENAME_AUDIT audit -

DATABASEUID_AUDIT hsmith -DATABASEPWD_AUDIT sa123 -

INSTALLTOMCAT yes -TOMCATCONNECTORPORT 13890 -
TOMCATREDIRECTPORT 13889 -TOMCATSHUTDOWNPORT 13891 -
AUDITINGENABLED yes -EPMENABLED yes -EPMLICENSEKEY C1111-
22222222-3333333-6678
The example uses the most common parameters. You can choose any
number of valid parameters, but it is good practice to keep the silent
installation as simple as possible.
Note that when you run a silent installation, you need to run the command
once for each CD, but you only need to provide the full list of options for the
first CD. For example, if the CDs are on different CD drives, the commands
could look like the following:
./install.sh -s /mnt/cd1 -INSTALLDIR /mymachine/BOBJ/
Enterprise115 -BOBJELICENSEKEY 00000-0000000-0000000-
0000 -INSTALLTYPE new -BOBJEINSTALLLOCAL user -
CMSPORTNUMBER 6401 -DBTYPE Oracle -SERVICENAME tnsname -
DATABASEUID userid -DATABASEPWD password -REINIT yes -
INSTALLTOMCAT yes -TOMCATCONNECTORPORT 8080 -
TOMCATREDIRECTPORT 8443
-TOMCATSHUTDOWNPORT 8005
./install.sh -s /mnt/cd2 -INSTALLDIR /mymachine/BOBJ/
Enterprise115
./install -s /mnt/cd3 -INSTALLDIR /mymachine/BOBJ/
Enterprise115
The following table lists the most common parameters used in a silent
installation. To use a parameter, place it on the command line after the
install command and the path for the installation files.
Note: Sample parameter values are case-sensitive.
Installation parameter Description

-s filepath Specifies the location of the CD you are
installing from. Replace filepath with
the full path for the CD drive or other
installation source directory. For
example,
-s /mnt/CD1/
-INSTALLDIR filepath Specifies the directory where you want to
install the new BusinessObjects
Enterprise components. Replace
filepath with the full path for the
installation directory. For example, -
INSTALLDIR /BOBJE/Enterprise115.

-x This parameter is followed by a comma-
separated values (CSV) string of
features that you do not want to install.
Note that this cannot be used in
combination with the -f option. See the
mymenu.xml file in the setup directory on
DISK_1 for a full list of features.
-f This parameter is followed by a comma-
separated values (CSV) string of
features that you want to install. Note
that this cannot be used in combination
with the -x option. See the mymenu.xml
file in the setup directory on DISK_1 for a
full list of features.
- EPMENABLED Use this parameter to install performance
management. The options are yes and
no; the default is no.
-EPMLICENSEKEY Use this parameter to enter your
Performance Management license key.
-c languagecode This option determines the language for
the installation. Replace languagecode
with a language code for one of the
supported languages (for example,
zh_CN, zh_TW, de, en, es, fr, it, jp,
ko, nl)
-INSTALLTYPE Specifies the type of installation. The
possible values are new, expand, or
custom.
-DBTYPE When installing a Central Management
Server, you need to specify the type of
database you want to use. Possible
values include Oracle, DB2, Sybase,
and MySQL.
-INSTALLMYSQL When installing a Central Management
Server, you can specify whether or not to
install and configure a new MySQL
database. The options are yes or no; no
is the default.
-MYSQLHOSTNAME With this parameter, you can specify the
host name of your MySQL server.


-SERVICENAME Specifies the service name used to
connect to the Central Management
Server database.
-SERVICEPORT Specifies the port number used to
connect to the Central Management
Server database. This is required only for
MySQL databases.
-DATABASEUID Specifies the user ID used to connect to
the Central Management Server
database. This option cannot be set to
root if the -INSTALLMYSQL option is set
to yes.
-DATABASEPWD Specifies the password used to connect
to the Central Management Server
database. If this option is not specified, it
defaults to blank.
-AUDITINGENABLED Use this parameter to configure Auditor
during your install. The two options are
yes and no. If this option is not specified,
it defaults to no.
-SERVICENAME_AUDIT Use this parameter to change the name
of the MySQL audit database, otherwise,
the default name of BOE115_Audit will
be used
-DATABASEUID_AUDIT Use this parameter to pass the user ID
for the database for Auditor.
Note: For trusted authentication this
parameter is not required, use
DATABASEAUTHENTICATION=trusted
-DATABASEPORT_AUDIT Use this parameter to specify the port for
MySQL Auditor.
Use only for MySQL.
-DATABASEPWD_AUDIT Specifies the Audit database password.
-MYSQLHOSTNAME_AUDIT Specifies the host name for the MySQL
server for your Audit database.
-MYSQLROOTPWD When the -INSTALLMYSQL option is set
to yes, you must also specify the -
MYSQLROOTPWD option. This option
specifies the password used for the root
account when setting up the database.

-CMSPORTNUMBER Specifies the port number for the Central
Management Server. If not specified, the
default is 6400.
-REINIT Specifies whether to reinitialize the
Central Management Server database.
The options are yes or no; yes is the
default.
-BOBJEINSTALLLOCAL Specifies whether to perform a user or a
system installation. The options are user
or system; user is the default.
-BOBJELICENSEKEY 00000- Specifies your product activation
0000000-0000000-0000 keycode.
-CLUSTERCMS For a custom installation, this option
specifies whether or not to cluster the
Central Management Server with an
existing CMS. The options are yes or no;
no is the default.
-CLUSTER_NAMESERVER For an expanded installation, this option
specifies the name of the Central
Management Server for the system you
are expanding.
For a custom installation, if the
-CLUSTERCMS option is set to yes, then
you need to specify the name of the CMS
you want to cluster with.
-CLUSTERPORTNUMBER For an expanded installation, this option
specifies the port number of the Central
Management Server for the system you
are expanding. The default is 6400.
For a custom installation, if the
-CLUSTERCMS option is set to yes, then
you need to specify the port number of
the CMS you want to cluster with. The
default is 6400.


-EXPANDSERVERS For an expanded installation, this option
provides a comma-separated values list
that specifies which servers you want to
add to the CMS specified by -
CLUSTER_NAMESERVER. The list can
include the following values:
• "CMS"
• "CacheServer"
• "EventServer"
• "InputFRS"
• "OutputFRS"
• "JobServer"
• "PageServer"
• "ReportAppServer"
• "Webi"
• "RAS21"
• "Servers" (specifies to install all of
the servers).
Note: Note that these values are case-
sensitive and do not contain spaces.
-INSTALLTOMCAT To install Tomcat, set this option to yes.
The default value is no.
-TOMCATCONNECTORPORT The port number that Tomcat uses to
connect. The default is 8080.
-TOMCATREDIRECTPORT The port number that Tomcat uses to
redirect. The default is 8443.
-TOMCATSHUTDOWNPORT The port number that Tomcat uses to
shut down. The default is 8005.
-REINIT Use yes to reinitialize the database and
no to not reinitialize.
Note:
• The silent installation is not recommended for custom installations. The
installation options are simplified and do not allow for the same level of
customization provided by the BusinessObjects Enterprise install script
program.

• To install the Java application server on the same machine, see
“Installing a Java application server” on page 72. If your Java application
server is installed on a different machine, see “Installing the Java
application tier components” on page 72.
Using ccm.sh to start the BusinessObjects Enterprise

servers
The ccm.sh script provides you with a command-line interface to the various
BusinessObjects Enterprise server components. For more information about
this script and others that are installed on your system, see the
In BusinessObjects Enterprise XI, the install setup program starts and
enables servers automatically. The following information is included for
reference.
To manually start and enable the servers
1. Go to the bobje directory that was created by the installation:
cd INSTALLDIR/bobje
2. Start all of the BusinessObjects Enterprise servers as daemons:
./ccm.sh -start all
3. Enable all of the BusinessObjects Enterprise servers. If you are using the
default ports, type the following command:
./ccm.sh -enable all
If you are using a different port number for the CMS, issue the following
command:
./ccm.sh -enable all -cms servername:portnumber
The daemons are now listening on the appropriate ports.
To view additional help on ccm.sh
• The ccm.sh script provides a detailed description of its command-line
options. To see the help, issue the following command:
INSTALLDIR/bobje/ccm.sh -help | more

Installing a Java application server
Installing a Java application server

Before you can use InfoView, the Central Management Console, or your
custom applications with BusinessObjects Enterprise, you must install one of
the supported Java application servers. Then you must install the
BusinessObjects Enterprise Java SDK and the Web Component Adapter on
the same machine.
Make sure that your Java application server can communicate with the
machine(s) that runs your BusinessObjects Enterprise servers over TCP/IP.
Alternatively, you can install your Java application server, BusinessObjects
Enterprise Java SDK, and all BusinessObjects Enterprise servers on the
same machine.
For a detailed list of tested Java application servers, consult the
Platforms.txt file included with your product distribution.
Note: If you have a firewall between the machine running your Java
application server and your other BusinessObjects Enterprise servers, you
must perform additional system configuration. See the section on how to
configure firewalls, in your BusinessObjects Enterprise Administrator’s Guide.
Follow the installation instructions that come with your Java web application
server. Configure your application server to run the source env.sh
command on startup. (The env.sh script is found in the root directory of your
BusinessObjects Enterprise installation.) This script sets a number of
environment variables necessary for operation of BusinessObjects
Enterprise.
Once your server is installed and running, verify that the application server is
running correctly by launching its default page, or administrative console in a
web browser:
• For Tomcat, type http://servername:8080/
• For BEA WebLogic, type http://servername:7001/console
• For IBM WebSphere 5, type http://servername:9090/admin
Installing the Java application tier

components
The BusinessObjects Enterprise Java SDK and the Web Component Adapter
must be installed on the machine that is running your Java web application
server. These Java application tier components are installed as part of the full
BusinessObjects Enterprise installation. For details, see “Performing a new

Installing the Java application tier components 3
installation” on page 53. If your Java application server is on the same
machine as your BusinessObjects Enterprise server components, then you
can now deploy InfoView and the BusinessObjects Enterprise Launchpads.
See “If you are using performance management from a client machine (that
is, a different desktop computer than where the performance manager server
is installed), you need to restart your computer.” on page 80.
However, if the Java application server is on a different machine from the
BusinessObjects Enterprise components, you must ensure that the Java
application tier components are installed on the Java web application server.
To install only the Java application tier components on a Java web application
server, perform a custom installation. For more information, see “Performing a
custom installation” on page 58.
For information on installing the Java web application server, see “Installing a
Java application server” on page 72. For information on deploying the Web
Component Adapter, see “Installing only the Web Component Adapter” on
page 61.
Post install component deployment

When you install BusinessObjects Enterprise on UNIX and install Tomcat with
your install, InfoView, the Central Management Console (CMC), the Web
Component Adapter (WCA) and the BusinessObjects Enterprise SDK are
installed, configured and deployed for you.
InfoView is a web-based interface that end users access to view, schedule,
and keep track of published reports. The CMC allows you to perform user
management tasks such as setting up authentication and adding users and
groups. The Web Component Adapter (WCA) is an application that runs on
your Java Web Application Server. The WCA hosts web components,
including a CSP plug-in that allows you to run CSP applications. The WCA is
also required for OLAP Intelligence. The BusinessObjects Enterprise SDKs
are used by many BusinessObjects Enterprise components and are also
used to simplify the development of custom BusinessObjects Enterprise
applications.
If you do not install Tomcat when you install BusinessObjects Enterprise,
these components must configured and deployed before you use them.
Consult the following sections for information how to deploy and what to
configure on your web application server:

Installing the Java application tier components

Verifying the Java web applications

The setup program automatically deploys the Java web applications to default
locations. You can test the deployments and change the default configuration
if necessary.
InfoView and the BusinessObjects Enterprise Administration
Launchpad
To test the Java deployment of the InfoView and the BusinessObjects
Enterprise Administration Launchpad
1. Open a web browser and type http://servername:portnumber/
businessobjects/enterprise115/desktoplaunch in its address
bar. For servername, substitute the name of the machine where you
installed.
The log on page for the InfoView should appear.
2. To test the BusinessObjects Enterprise Administration Launchpad, open
a web browser and type http://servername:portnumber/
businessobjects/enterprise115/adminlaunch in its address bar.
For servername, substitute the name of the machine where you
installed.
The BusinessObjects Enterprise Administration Launchpad should open.
Deploying custom CSP applications
To deploy your own custom CSP applications, place them in the Web
Content directory that contains the Central Management Console.
Changing the deployment values for the Web Component Adapter

The BusinessObjects Enterprise setup program automatically configures the
JAVA WCA with specific information:
• The name and location of your Central Management Server.
• The default display name of the WCA.

• The location of the directories where the WCA can find CSP applications.
• The location it should use for log files.
In most situations you should not need to change these default values.
You may want to change some of these values to change the location of the
WCA log files, if you want to deploy your custom CSP applications in a
location other than the default directory, or if you plan to deploy multiple
WCAs. If you want to change these values, follow the steps that apply to the
type of WCA you installed.
To change the deployment values for the Java WCA
1. Stop your Java application server, if it is running.
2. Extract web.xml from webcompadapter.war.
The webcompadapter.war archive file is stored in the location
<INSTALLDIR>/bobje/enterprise115/java/applications.
3. Open web.xml in a text editor.
To alter the values of cspApplication.dir (the directory for your CSP
applications), or log.file (the location of the log files created by the
WCA), edit the following lines to change the values between the <param-
value></param-value> tags:
<context-param>
<param-name>cspApplication.dir</param-name>
<param-value>EnterYourCSPLocationHere</param-value>
<param-name>log.file</param-name>
<param-value>EnterYourLogLocationHere</param-value>
</context-param>
4. Edit the value between the <display-name> </display-name> tags
to edit the display name of your WCA. Use the format wcaname.wca.
5. Edit the connection.cms context parameter to edit the name of your
Central Management Server. (Add the name of your CMS between the
<param-value> </param-value> tags for this context parameter.)
6. Save web.xml, then reinsert the file into the WEB-INF directory within
webcompadapter.war.
7. Restart your application server and redeploy webcompadapter.war. The
WCA should now use the new values from web.xml.
Installing multiple Web Component Adapters

You can install multiple Web Component Adapters (WCA) by deploying
multiple instances of webcompadapter.war.

If you deploy each WCA on a separate application server, installing multiple

WCAs is roughly equivalent to installing multiple Web Component Servers (in
a Windows installation of BusinessObjects Enterprise that uses the
BusinessObjects Enterprise COM SDK). If you deploy each WCA on the
same Java application server, installing multiple WCAs is equivalent to
creating multiple virtual directories for your web server (in a Windows
installation of BusinessObjects Enterprise that uses the BusinessObjects
Enterprise COM SDK).
When you install more than one WCA, each webcomponentadapter.war file
contains its own web.xml file that contains configuration parameters for that
WCA. However, you can only set the following parameters individually for
each WCA:
• cspApplication.defaultPage
• cspApplication.dir
• connection.cms
• connection.listenPort
• log.file
• log.ext
• log.isRolling
• log.size
• log.level
• log.entryPattern
The remaining parameters must be the same for all WCAs.
See “Changing the deployment values for the Web Component Adapter” on
page 74 for information on changing the values.
Deploying custom CSP applications

To deploy your own custom CSP applications, place them in the bobje_root/
webcontent directory (or other directory specified by the
cspApplication.dir parameter in web.xml. See “Changing the
deployment values for the Web Component Adapter” on page 74 for details.)
This is the same directory that contains the Central Management Console.
Alternatively, you can deploy a second WCA, with a separate CSP
deployment directory for your custom applications. See “Installing multiple
Web Component Adapters” on page 75 for details.

Verifying your performance management installation
Before you launch performance management, launch the CMC and go to the
Servers page to verify that all of the performance management servers
required for the products you installed are running.
The following table provides a description of each performance manager
server:
Server name Service Description

AADashboard Dashboard engine Renders the performance
management Corporate Tiered
Dashboards that users create
using Dashboard Manager
AAAnalytics Analytics server Renders the performance
management analytics by
querying the metrics metadata
and then generating the
desired visualization in the
format of the selected analytic.
AAMetrics Metrics engine Works like an Extract,
Transform and Load (ETL) tool
to extract each metric value,
aggregate it, and then load it
into the metadata layer on the
performance management
repository.
AAIProfiler Individual Profiler Used by Individual Profiler.
engine For more information, go to
Setup > Parameters >
Individual Profiler and then
click Help on the Services bar.
AARepomgt Repository manager Manages the performance
management repository –
including user security and
privileges, updates to the
system parameters, and
writing new metrics and rules
back to the repository.
AARules Rules engine Evaluates conditions placed
against metrics, goals, sets
and then outputs sending
events to other components

Server name Service Description

AAQueryManager Set Analysis query Performs Set Analysis queries
manager and builds and processes sets.
AASPC Process Analysis Used by Process Analysis.
engine Note: The Process Analysis
alerts are handled by AARules
PAServer Predictive Analysis Used by Predictive Analysis.
mining engine For more information, go to
Performance Management >
Predictive Analysis and then
click Help on the Services bar
Post installation setup for performance management

Before users in your organization can start working with performance
management, you need to do the following:
• Create the performance management repository – this repository stores
the metrics, goals, sets, and calendars that users leverage for their
performance management analysis.
• Define system users – this enables the performance management
application engines.
• Define connections to the metrics universes and push those universes to
the performance management repository – this makes the metadata for
measures and dimensions available to users for metric creation.
Full information on how to do this is available in the Performance
Management Setup Online Help.
To launch the online help and set up performance management:
1. Log into InfoView, then click Go to Performance Management.
The Performance Management welcome page appears.
2. Click Setup.
3. Click Help on the Services bar.
4. Follow the instructions in the online help.
Troubleshooting starting performance management

If, when you launch performance management, you receive an error message
saying that you cannot connect to performance management, this may mean
one of the following:

• Some of the performance management servers are stopped or disabled.
• The Initialization User that creates the performance management server
proxies may be defined inconsistently in the CMS, InfoView, and the
InitConfig.properties file.
To verify performance management servers

1. Log into the Central Management Console (CMC), and then click
Servers.
2. Verify that all the performance management servers are started.
3. If a server is not running, select the check box next to the server name,
and then click Start.
4. Make sure that all servers are enabled.
If a server is not enabled, select the check box next to the server name,
and then click Enable.
To verify the Initialization User
1. On your performance management server, open the
InitConfig.properties file and verify that the Initialization user name
and password match those in the CMS.
This file is at:
<InstallDir>/bobje/performance_management_115
The strings to search for are:
• initialization.User=
• initialization.Password=
2. Log into InfoView, and then click the Preferences button on the InfoView
toolbar.
3. Click the Performance Management tab, and then check the name of
the initialization logon user in the Change initialization logon user
section is the same as the user name specified in the
InitConfig.properties file.
4. Log into the Log into the Central Management Console (CMC), and then
click Users.
5. Check that the user defined in the InitConfig.properties is listed
among the users.
6. From the CMC home page, click Settings > Rights and check that the
initialization user has the appropriate rights.
Note: For security reasons, it is recommended that you do not provide a
real user ID for the initialization user. The default user ID is PMUser.

You need to restart the performance management servers.

7. Restart all servers.
./ccm.sh -stop all
./ccm.sh -start all
If you are using performance management from a client machine (that is, a
different desktop computer than where the performance manager server is
installed), you need to restart your computer.

Installing the Productivity
Pack
chapter
4 Installing the Productivity Pack
Productivity Pack upgrade overview

This section of the guide provides information on how to upgrade to
BusinessObjects Enterprise XI Release 2 Productivity Pack (PP). The
prerequisite for this upgrade is that you have BusinessObjects Enterprise XI
R2 Service Pack 2 installed.
Note: Service Pack 2 is the first service pack available for Unix.
If you have an existing installation of BusinessObjects Enterprise XI R2, but
have not yet applied SP2, you must apply this service pack before you
proceed with an upgrade. For details on how to upgrade to SP2, see http://
support.businessobjects.com/downloads/updates/service_packs/boxir2/
default.asp.
What is included in the productivity pack?

BusinessObjects Enterprise XI Release 2 Productivity Pack includes the
following features:
• Business Process BI Service
• BusinessObjects Voyager
• Content Search in InfoView
Business Process BI Service

Business Process BI Service is a high-level web service designed to help
align an organization’s BI investments with the everyday running of its
business. Business Process BI Service will help an organization effectively
streamline business intelligence delivery, automate data refreshes and
integrate Business Objects Enterprise administration directly into common IT
processes.
For more information, see the Business Process BI Service Guide.
Note: Business Process BI Service is available only for Java web application
servers.
BusinessObjects Voyager
BusinessObjects Voyager is a powerful OLAP analysis tool that can help you
gain insight into business data and make intelligent decisions that impact
corporate performance.

Installing the Productivity Pack
Productivity Pack upgrade overview 4
OLAP technology differs from traditional OLTP technology. You can perform
real-time, interactive analysis on large volumes of OLAP data in
BusinessObjects Voyager to get answers to your business questions much
more quickly than is possible using other techniques. You can identify trends
and anomalies within business performance that may otherwise go
unnoticed.
For an overview of OLAP technology and concepts, see the BusinessObjects
Voyager User's Guide.
OLAP data is displayed in the BusinessObjects Voyager analysis window with
crosstabs and charts. You create a workspace, add crosstab and chart
objects to the analysis window, connect those objects to OLAP data sources,
and then interactively define queries to explore your data.
BusinessObjects Voyager is accessed from within InfoView. All you need is a
connection to a BusinessObjects Enterprise system that has BusinessObjects
Voyager installed. You do not need to install BusinessObjects Voyager on
your local machine.
Note:
• The BusinessObjects Voyager web application and content viewer are
only available as Java web applications. There are no corresponding
BusinessObjects Voyager applications for .NET.
• In some instances, after the installation is complete, you will have to enter
a keycode to enable BusinessObjects Voyager. See the BusinessObjects
Voyager Administrator's Guide for information about how to enter the
keycodes and when the additional keycodes are required.
Content Search in InfoView

This feature is an optimized search tool that enables users to search within
the content of objects managed by BusinessObjects Enterprise. It also refines
the search results by grouping them into categories of similar object types,
and ranking them in order of their relevance to the search term.
For information related to the administration of this feature, see the
BusinessObjects Enterprise Administrator’s Guide. For information on how to
use this feature, see the BusinessObjects Enterprise InfoView User’s Guide.
Upgrading from BusinessObjects Enterprise XI R2 to Productivity Pack

To begin your installation
1. Mount the device that contains the installation files.
2. Type ./install.sh

3. Select the language for your installation, and then press Enter.
4. On the Software License Agreement screen, enter y to accept the
License agreement.
5. On the Installation Directory screen, remove the existing directory, then
enter the path where your original BusinessObjects Enterprise R2 was
installed, then press Enter.
6. Enter the following information and hen press Enter:
• Name of your CMS
• CMS user name
• Password
• Authentication Type
• Port number
Note: If you don’t enter a specific number, the port value will default to
6400.
7. On the select features screen, deselect the features you want, then press
next
8. Press Enter to begin the installation.
Note: By default, the installer automatically creates a daily recurring job
for the indexing process. After the installation of the Productivity Pack,
the administrator may review and change the indexing option for the
search system. Please refer to the BusinessObjects Enterprise Content
Search Administrator's Guide for details.
Installation logs
All the actions of the BusinessObjects Enterprise installation program are
recorded in a file. You can find this file BOBJPPInstall_0.log the following
location:
<Installdir>/bobje/logging directory
Distributed installs of BusinessObjects Voyager

Like the majority of the BusinessObjects Enterprise Servers, the Multi-
Dimensional Analysis Services Server, which processes BusinessObjects
Voyager documents, can be scaled to divide the processing load or to
distribute the load. This installation type is done in multiple steps:

Feature selection 4
• The BusinessObjects Voyager web application server components would
need to be installed on the machine where InfoView is deployed. This is
the machine that hosts your web application server and has the WCA
installed.
• The BusinessObjects Voyager CMS Add-On must be installed on the
machine where your CMS is installed.
• The Multi-Dimensional Analysis Services Server can be installed on any
machine that has the BusinessObjects Enterprise Java SDK installed.
Consult the BusinessObjects Voyager Administrator's Guide for details on
prerequisites and other information on BusinessObjects Voyager.
Feature selection
You can install all options included with the Productivity Pack or you can opt
to limit your install to specific items. The following table lists the options
available and describes what these options contain.

Feature selection
Option Description
BusinessObjects Voyager BusinessObjects Voyager contains three sub-
components:
• Multi Dimensional Analysis Services
Server.
• BusinessObjects Voyager web application
server component.
• BusinessObjects Voyager CMS Add-On.
The Multi Dimensional Analysis Services is the
name of the server that processes
BusinessObjects Voyager documents. After the
install, this server can be started or stopped
from the CCM or the CMC.
The web application server component is the
required information to integrate
BusinessObjects Voyager with InfoView.
The CMS Add-On option contains the
necessary changes for the CMS to support the
new object types created by BusinessObjects
Voyager.
Note:
• If Tomcat is detected during your
installation, and you allow the installation to
update and configure your web application
server components, this new WAR file will
be deployed for you.
• If Tomcat is not detected during your
installation, or you choose not to allow the
installation to update and configure your
web application server components on
Tomcat, you must deploy this WAR file after
the installation completes.

Feature selection 4
Option Description
Business Process BI This contains Business Process BI Service.
Service When this is installed, a new WAR file called
BusinessProccessBI.war is copied to your
machine.
Note:
• If Tomcat is detected during your
installation, and you allow the installation to
update and configure your web application
server components, this new WAR file will
be deployed for you.
• If Tomcat is not detected during your
installation, or you choose not to allow the
installation to update and configure your
web application server components on
Tomcat, you must deploy this WAR file after
the installation completes.
Content Search in InfoView This option contains two options:
• Search Server
• CMS Add-On
The Search Server is a search engine.
The CMS Add-On contains the necessary
changes for the CMS to support the new object
types created by the Content Search in
InfoView.
Silent installation
.A silent installation is one that you run from the command line to install
BusinessObjects Enterprise on any machine in your system. When you run a
silent installation, you can specify all the parameters to be used for the install
at the same time on the command line, rather than several at a time on each
of the different install screens.
The silent install is run from the command line. The command includes a
series of parameters that provide information for installation settings and
directory paths. You can also specify options that control the level of prompts
during an install.

Feature selection
Note: BusinessObjects Enterprise does not support silent installations when

the install contents are on multiple CDs. If your install is on multiple CDs, you
must first copy the contents from all the CDs to a central location, such as a
hard-drive, and then run the silent install from the location that contains the
content from all the CDs.
The silent BusinessObjects Enterprise installation is particularly useful when
you need to perform multiple installations or you do not want to interrupt
people who are working on machines in your system. You can also use the
silent installation command in your own scripts. For example, if your
organization uses scripts to install software on machines, you can add the
silent BusinessObjects Enterprise installation command to your scripts.The
silent installation command consists of the command setup.exe, followed by
the install destination, and a number of parameters that provide information
about the installation.
Following is an example that installs BusinessObjects Enterprise XI R2 PP,
allows Tomcat to deploy the required files an uses Enterprise authentication:
install.sh -c en -i /home/myname/boe -NAMESERVER "abclnx226"
-CMSPORTNUMBER "555" -f
"Complete,IA_Service,IA,IA_Client,IA_CMS,Search
_CMS,Search,Search_Service,BPBIS"
Note: The parameters are case sensitive. Since CMSPORTNUMBER is not
used, port 6400 will be assumed to be the CMS port number.
The example uses most of the available parameters. You can choose any
number of valid parameters, but it is good practice to keep the silent
installation as simple as possible.
The following table lists the parameters used in a silent installation of
BusinessObjects Enterprise XI R2 Productivity Pack. To use a parameter,
place it on the command line after the install.sh command and the path
for the installation files.

Feature selection 4
Silent install parameters
Installation parameter Explanation of parameters and valid

options.
-i <filepath> Use this to specify the location of your
installation of BusinessObjects Enterprise.
Replace filepath with the full path for
the installation directory. This must be
<BOJBDIR>, where BOBJDIR is the
location you specified for your original
install.
-c Use this to specify the Language version
code for the install.
• For English, enter en.
• For French, enter fr.
• For German, enter de.
• For Spanish, enter es.
• For Japanese enter jp.
• For Simplified Chinese, enter zh_CN
• For Traditional Chinese, enter zh_TW.
• For Korean, enter ko.
• For Dutch, enter nl.
• For Swedish, enter sv.
• For Italian, enter it.
• For Russian, enter ru.
• For Polish, enter pl.
• For Portuguese, enter pt.
Complete Use this option whenever you use install
BusinessObjects Enterprise XI R2
Productivity Pack.
This option is mandatory.
This parameter must be used with the -f
option.

Feature selection

options.
-NAMESERVER Use this option to specify the name of
your CMS server. This option must be
used whenever you install use either
IA_Service or Search_Service so that
the required changes to support these
new features can be made to the CMS.
Note: If you specify this parameter, you
must also specify these parameters:
CMSUSERNAME
CMSPASSWORD
-CMSPORTNUMBER Use this option to specify the name of the
CMS port. If this is not specified, it will
default to port 6400.
CMSAUTHENTICATION Use this option to specify the method of
“SecXXX” authentication used to log onto the CMS.
These are the available options, and
these must match how you have
configured authentication on your
deployment:
• SecEnterprise
• SecLDAP
If this parameter is not specified, and the
authenticating method is required
because, SecEnterprise authentication
will be used.
IA_Client Use this option to install web application
server component required to integrate
BusinessObjects Voyager with InfoView.
This parameter is an argument that can
be used with the -f option.
IA_Service Use this option to install the Multi-
Dimensional Analysis Service Server for
BusinessObjects Voyager.

Feature selection 4
options.
IA_CMS Use this option to install the required
changes in the CMS to install
BusinessObjects Voyager. This option is
required on the machine where your CMS
is installed if you are installing
BusinessObjects Voyager.
Search_Service Use this option to install the Content
Search in InfoView feature.
Search_CMS Use this option to install the required
changes in the CMS to install Content
Search in InfoView. This option is
required on the machine where your CMS
is installed if you are installing Content
Search in InfoView.
BPBIS Use this option to install Business
Process BI Service.
-f This parameter is followed by a comma-
separated values (CSV) string of features
that you want to install. Note that this
cannot be used in combination with the -x
option. See the mymenu.xml file in the
setup directory on DISK_1 for a full list of
features.
Note:
• The silent installation is not available from the BusinessObjects
Enterprise Setup program and is intended only for experienced
administrators of BusinessObjects Enterprise.
• The silent installation is not recommended for custom installations. The
installation options are simplified and do not allow for the same level of
customizing that the BusinessObjects Enterprise Setup program
provides.


When you install the BusinessObjects Enterprise XI R2 Productivity Pack,
BusinessObjects Voyager, Content Search in InfoView and Business Process
BI Service are deployed for you if you choose to allow the installation to
update the required components on the detected instance of Tomcat.
If you chose not to allow the installation to deploy new WAR files or redeploy
existing WAR files to Tomcat, or if you are using another supported web
application server, certain components must be updated on your web
application server before you use them. This means you must do the
following:
• Undeploy the original WAR files.
• Delete any content that remains in the directories where the original war
files were deployed.
If you originally deployed on an existing version Tomcat, this directory
would be the following BusinessObjects Enterprise directories where
TOMCATDIR is the location where you installed Tomcat:
• <TOMCATDIR>/webapps/businessobjects
• <TOMCATDIR>/webapps/dswsbobje
• <TOMCATDIR>/webapps/jsfadmin
If you did not deployed on Tomcat, replace TOMCATDIR/webapps with the
deployed location that applies to your web application server.
• Redeploy the updated WAR files.
New or updated WAR files

Following is a list of the WAR files that have been updated or are new in the
install of the Productivity pack:
WAR file Contents

desktop.war InfoView, BusinessObjects Voyager,
BusinessProcessBI.war Business Process BI Service
Consult the following sections for information how to deploy the WAR files on
your web application server:

Post install component deployment 4
Uninstalling the Productivity Pack

After you have completed your installation of the Productivity Pack, follow
these steps to remove it.
To uninstall the Productivity Pack
1. .Go the install directory for BusinessObjects Enterprise XI Release 2
Productivity Pack.
2. Type the following command to remove Productivity Pack:
./uninstallIW.sh


3333
Deploying on Tomcat
chapter
5 Deploying on Tomcat
Before you start
Before you start

Before you begin the deployment process, you should verify that the
application server is running correctly by launching its default page, or
administrative console in a web browser. For Tomcat, type http://
servername:8080/ where servername is the name of the machine where
tomcat is installed.
Deploying with Tomcat

If you have an existing version of Tomcat 5.0.27, and you want it to work with
BusinessObjects Enterprise, you must perform certain steps. These steps
are:
• “Preparing the service” on page 97
• “Setting up JAR files” on page 98
• “Deploying the WAR files” on page 99
Locations of the WAR files

The table that follows lists the locations of the WAR files. Replace
INSTALLDIR with the directory where you installed BusinessObjects
Enterprise.
WAR File Location

webcompadapter.war, <INSTALLDIR>/bobje/
jsfadmin.war, desktop.war, enterprise115/java/applications
admin.war, adhoc.war, If you plan on using Crystal Reports
Explorer, see “Integrating Crystal
Reports Explorer with InfoView” on
page 101 before you deploy this WAR
file.
styles.war, AnalysisHelp.war <INSTALLDIR>/bobje/
enterprise115/java/
applications/olap

Deploying on Tomcat
Before you start 5
WAR File Location
dswsbobje.war, <INSTALLDIR>/bobje/
enterprise115/web services/
<language_code>
afhelp.war <INSTALLDIR>/
Performance_Management_115If
performance management is not
installed, this WAR file will not be
present.
Note:
• Replace INSTALLDIR with the directory where you installed
• Replace <language_code> with the code specific to the language of
your installation, for example en or fr.
Preparing the service

If you use an existing version of Tomcat, you must prepare the service before
you can use it with BusinessObjects Enterprise. To prepare Tomcat, you must
do two things:
• Specify the location of the BusinessObjects Enterprise environment shell.
• Specify the location of the JDK shipped with BusinessObjects Enterprise.
This will ensure that the Java options are set in the way required by
BusinessObjects Enterprise and that the JDK shipped with BusinessObjects
Enterprise is used.
Whenever you see the following variables, replace them with the path where
you have installed the product.
• TOMCATDIR is the path where Tomcat is installed.
• INSTALLDIR is the path where BusinessObjects Enterprise is installed.
• JAVA_HOME is the path where Java is installed.
To prepare the service
1. Go to the directory where Tomcat is installed, and then change to the bin
directory.
2. Create the file setenv.sh.
3. Add this information to the file, where INSTALLDIR is the path where
BusinessObjects Enterprise is installed:
#!/bin/sh

Before you start
.”<INSTALLDIR>/bobje/setup/env.sh”
JAVA_HOME="<INSTALLDIR>/bobje/jdk"
export JAVA_HOME
4. Add the path environment variable that is used on your operating system
with the location of BusinessObjects Enterprise. The options are as
follows:
Operating Variable Example

System
For Solaris LD_LIBRARY_PATH LD_LIBRARY_PATH=<INSTALLDIR
>/bobje/enterprise115/
solaris_sparc:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
For AIX LIBPATH LIBPATH=<INSTALLDIR>/bobje/
enterprise115/aix_rs6000:$LIBPATH
export LIBPATH
For Linux LD_LIBRARY_PATH LD_LIBRARY_PATH=<INSTALLDIR
linux_x86:$LD_LIBRARY_PATH
For HPUX SHLIB_PATH SHLIB_PATH=<INSTALLDIR>/
bobje/enterprise115/hpux_pa-
risc:$SHLIB_PATH
export SHLIB_PATH
Setting up JAR files

Note: BusinessObjects Enterprise XI R2 requires version 2.5.2 of xalan.jar.
These are files used by the XML parser. If you are sure your version of
Tomcat has this version, you do not need to replace these files.
To set up the JAR files for BusinessObjects Enterprise
1. Copy the JAR file cewcanative.jar from <INSTALLDIR>/bobje/java/
applications/ to TOMCATDIR/shared/lib.
2. Replace the following JAR file found in TOMCATDIR/common/endorsed
with the one from <INSTALLDIR>/bobje/java/lib/external:
• xalan.jar

Deploying on Tomcat
Before you start 5
Note: BusinessObjects Enterprise XI R2 requires version 2.5.2 of xalan.jar.
These are files used by the XML parser. If you are sure your version of
Tomcat has this version, you do not need to replace these files.
Deploying the WAR files

To deploy the war files
1. Open a text editor.
2. Create the files listed in the following table and add the content specified
in the Content column to the files. This will set the context path for each
WAR file.
Note: As a general rule, WAR files must be deployed on the same
machine as they were installed. This is because the installation will
replace some text variables inside local WAR files with machine and
CMS specific values at install.
The one exception to this rule is the BusinessProcessBI.war file, which
can be copied to any web application server and deployed there. If you
plan on using Trusted Authentication on a different web application
server than all your other BusinessObjects Enterprise application, see
“Configuring Trusted Authentication on a separate web application
server” in the BusinessObjects Enterprise Deployment and Configuration
Guide before you deploy the BusinessProcessBI.war file.
Filename Content
desktopwar.xml <Context docBase="<INSTALLDIR>/
bobje/enterprise115/java/
applications/desktop.war" path="/
businessobjects/enterprise115/
desktoplaunch" crossContext="false"
debug="0" reloadable="false"
trusted="false"/>
webcompadapterwar.xml <Context docBase="<INSTALLDIR>/
applications/webcompadapter.war"
path="/businessobjects" debug="0"
reloadable="false"/>
jsfadminwar.xml <Context docBase="<INSTALLDIR>/
applications/jsfadmin.war" path="/
jsfadmin" debug="0" reloadable="false"/>

Before you start
Filename Content
adminwar.xml <Context docBase="<INSTALLDIR>/
applications/admin.war” path="/
businessobjects/enterprise115/adminlaunch"
crossContext="false" debug="0"
reloadable="false" trusted="false"/>
adhocwar.xml <Context docBase="<INSTALLDIR>/
applications/adhoc.war” path="/
businessobjects/enterprise115/adhoc"
analysishelpwar.xml <Context docBase="<INSTALLDIR>/
applications/olap/AnalysisHelp.war"
path="/AnalysisHelp" crossContext="false"
trusted="false"/>
styleswar.xml <Context docBase="<INSTALLDIR>/
applications/olap/styles.war"
path="/styles" crossContext="false"
trusted="false"/>
dswsbobjewar.xml <Context docBase="<INSTALLDIR>/
bobje/enterprise115/web services/
<language_code>/dswsbobje.war”
path="dswsbobje"
reloadable="false" trusted="false"/
>
BusinessProcessBI.xml <Context docBase="<INSTALLDIR>/
<language_code>/
BusinessProcesBI.war”
path="BusinessProcessBI"
>
Note:
• Desktop.war does not depend on any of the other war files so it can be
deployed at any time. The remaining files have dependencies on each
other so must be deployed in a specific order. First deploy the

Deploying on Tomcat
Before you start 5
webcompadapter.war, followed by jsfadmin.war and finally admin.war.
Adhoc.war, analysishelp.war, styles.war, dswsbobje.war and
BusinessProcessBI.war can now be deployed.
• Replace <language_code> with the code specific to the language of your
installation, for example en or fr.
3. Save each file to <TOMCATDIR>/Tomcat/conf/Catalina/localhost,
where TOMCATDIR is replaced with the directory where Tomcat is
installed.
4. Restart Tomcat. Go to the directory <TOMCATDIR>/Tomcat/bin and
type the following command:
./shutdown.sh
./startup.sh
Integrating Crystal Reports Explorer with InfoView

Desktop.war contains the components for InfoView; Adhoc.war contains the
components for Crystal Reports Explorer. If you want to integrate Crystal
Reports Explorer with InfoView, you must make some changes in
desktop.war before it is deployed.
To integrate Crystal Reports Explorer
1. Locate the desktop.war file. This file is found in the directory
<INSTALLDIR>/bobje/enterprise115/java/applications, where
INSTALLDIR is the path where BusinessObjects Enterprise is installed.
2. Open the WAR file and extract adhoc-config.xm from the WEB-INF
directory.
3. Modify the value between <serverpath> and </serverpath> with
http://servername:portnumber/businessobjects/enterprise115/adhoc.
4. Save the file.
5. Place it back in desktop.war.
After you deploy desktop.war and adhoc.war, you will be able to access
Crystal Reports Explorer if you enter http://servername:portnumber/
businessobjects/enterprise115/adhoc in your browser.
Verifying the Tomcat deployment

To verify the Tomcat configuration, make sure that InfoView and the Central
Management Console can be launched in a browser.
To verify the Tomcat configuration
1. Open a browser window.

Before you start
2. Enter the url for InfoView in the browser using the format http://[host
name]:[port number]/businessobjects/enterprise115/desktoplaunch. For
example:
http://localhost:8080/businessobjects/enterprise115/desktoplaunch
3. Enter the url for the administration launchpad in the browser using the
format http://[host name]:[port number]/businessobjects/enterprise115/
adminlaunch. For example:
http://localhost:8080/businessobjects/enterprise115/adminlaunch

Deploying on Tomcat with
the JDK 1.5
chapter
6 Deploying on Tomcat with the JDK 1.5
Modifying Tomcat to use JDK 1.5

BusinessObjects Enterprise ships with Apache Tomcat 5.0.27 which uses
JDK version 1.4.2_08. If you want Tomcat to use JDK 1.5 instead, you have
two choices:
• You can use the instance of Tomcat where BusinessObjects Enterprise is
already deployed. This would involve installing the new JDK 1.5, then
modifying your existing instance so it uses the new JDK 1.5.
See “Using a version of Tomcat already running BusinessObjects
Enterprise” on page 104 for details. If you opt to use this method, the
remainder of this section does not apply to you.
• You can deploy BusinessObjects Enterprise on Tomcat.
This will involve these steps which are outside the scope of this
document:
• Installing the new JDK
• Installing Tomcat
Note: During the install, you will be prompted to specify the location of
your JDK. When asked, specify the location of JDK 1.5.
This will also involve these steps which are detailed in this document:
• “Copying the required Jar file to Tomcat” on page 106
Note: In this document, we refer to the JDK 1.5. However, the official version
number for this product, from both JDK providers Sun and BEA, is JDK 5.0.
We have used JDK 1.5 to help clarify that this is the next JDK version after
1.4.
Using a version of Tomcat already running

To create a new version of Tomcat that uses the JDK 1.5
1. Install the new JDK 1.5 on your machine.
Note: This version cannot be installed from the BusinessObjects
Enterprise installer. You must download this version from your JDK
vendor.
2. Record the directory where the new files are installed.
3. If you had previously deployed on Tomcat with the JDK 1.4 shipped with
BusinessObjects Enterprise, stop the instance of Tomcat already running.
Note: This can be done with this command: ./tomcatshutdown.sh

Deploying on Tomcat with the JDK 1.5
6
4. Go to the following directory, where INSTALLDIR is the installation
location for the original version of Tomcat shipped with BusinessObjects
Enterprise:
<INSTALLDIR>/bobje/tomcat/bin
5. Open this file in a text editor:
setenv.sh
6. Modify the JAVA_HOME variable with the location of the newly installed
JDK 1.5.
8. Restart Tomcat.

Enterprise.
WAR File Location

admin.war, adhoc.war, Note: If you plan on using Crystal
Reports Explorer, see “Integrating
Crystal Reports Explorer with InfoView”
on page 110 before you deploy this WAR
file.
enterprise115/java/
applications/olap
<language_code>
Performance_Management_115
Note: If performance management is not
present.
Note:

• Replace <language_code> with the code specific to the language of

Copying the required Jar file to Tomcat

After you have installed a new version of Tomcat, you must copy the
cewcanative.jar file to Tomcat’s shared\lib directory.
Copying the JAR files
• Copy the JAR file cewcanative.jar from the following BusinessObjects
Enterprise directory to Tomcat’s shared/lib directory:
<INSTALLDIR>/bobje/java/applications/
Note: If you modified the default directory where BusinessObjects
Enterprise is installed, please modify this directory accordingly.
Adding the Java Options

If you use an existing version of Tomcat, you must prepare the service before
you can use it with BusinessObjects Enterprise. To prepare Tomcat, you must
do two things:
• Configure the paths
• Specify the location of the JDK 1.5
Whenever you see the following variables, replace them with the path where
you have installed the product.
• TOMCATDIR is the path where Tomcat is installed.
• INSTALLDIR is the path where BusinessObjects Enterprise is installed.
• JDKDIR is the directory where the JDK 1.5 is installed.
Preparing the service

To prepare the service
1. Go to the directory where you install Tomcat, and then change to the bin
directory.
2. Create the file setenv.sh.
3. Add this information to the file, where JDKDIR is the path where you
installed the JDK 1.5:
#!/bin/sh
JAVA_HOME="<JDKDIR>/java/jdk1.5.0_06"
export JAVA_HOME

6
4. Add the path environment variable that is used on your operating system
with the location of BusinessObjects Enterprise. The options are as
follows:

System

export LIBPATH
risc:$SHLIB_PATH
export SHLIB_PATH
5. If you are using performance management, add the following java
options:
-Daf.configdir=<INSTALLDIR>/Performance_Management_115
6. If you are using OLAP Intelligence and the DHTML viewer add the
following java options:
-Dbusinessobjects.olap.home=/<INSTALLDIR>/bobje/
enterprise115/<aix_rs6000>/olap -
Dbusinessobjects.olap.bin=/<INSTALLDIR>/bobje/
enterprise115/<aix_rs6000>/olap/bin -
Dbusinessobjects.olap.stylesheets=/<INSTALLDIR>/
bobje/enterprise115/<aix_rs6000>/olap/stylesheets -
Dbusinessobjects.olap.xslt.TransformerFactory=org.apa
che.xalan.processor.TransformerFactoryImpl -
Dbusinessobjects.olap.env=<LIBPATH>=/<INSTALLDIR>/
bobje/enterprise115/<aix_rs6000>/olap/bin:/
<INSTALLDIR>/bobje/enterprise115/<aix_rs6000>:/home/
dbclient_aix/essbase/7120/bin,holos_language=/

<INSTALLDIR> /bobje/enterprise115/<aix_rs6000>/olap/
bin,ARBORPATH=/home/<dbclient_aix>/essbase/
7120,HOME=/<INSTALLDIR>/bobje/enterprise115/
<aix_rs6000>/olap,BOE_REGISTRYHOME=<INSTALLDIR>/
bobje/data/.bobj/registry
Note: Replace aix_rs600, dbclient_aix and LIBPATH with the
platform name and pathname variable that applies to your installation.
The platform name options for Solaris are as follows:
solaris_sparc, dbclient_solaris and LD_LIBRARY_PATH

After you have completed all the steps involved in installing and configuring a
new version of Tomcat to work with JDK 1.5, you must deploy the WAR files.
To deploy the war files
1. Open a text editor.
2. Create the files listed in the following table and add the content specified
in the Content column to the files. This will set the context path for each
WAR file.
Note: As a general rule, WAR files must be deployed on the same
machine as they were installed. This is because the installation will
replace some text variables inside local WAR files with machine and
CMS specific values at install.
Filename Content
desktopwar.xml <Context docBase="<INSTALLDIR>/
applications/desktop.war" path="/
businessobjects/enterprise115/
desktoplaunch" crossContext="false"
trusted="false"/>
webcompadapterwar.xml <Context docBase="<INSTALLDIR>/
applications/webcompadapter.war"
path="/businessobjects" debug="0"
reloadable="false"/>

6
Filename Content
jsfadminwar.xml <Context docBase="<INSTALLDIR>/
applications/jsfadmin.war" path="/
jsfadmin" debug="0" reloadable="false"/>
adminwar.xml <Context docBase="<INSTALLDIR>/
applications/admin.war” path="/
businessobjects/enterprise115/adminlaunch"
adhocwar.xml <Context docBase="<INSTALLDIR>/
applications/adhoc.war” path="/
businessobjects/enterprise115/adhoc"
analysishelpwar.xml <Context docBase="<INSTALLDIR>/
applications/olap/AnalysisHelp.war"
path="/AnalysisHelp" crossContext="false"
trusted="false"/>
styleswar.xml <Context docBase="<INSTALLDIR>/
applications/olap/styles.war" path="/
styles" crossContext="false" debug="0"
dswsbobjewar.xml <Context docBase="<INSTALLDIR>/
<language_code>/dswsbobje.war”
path="dswsbobje"
>
Note:
Adhoc.war, analysishelp.war, styles.war and dswsbobje.war can now be
deployed.

• Replace <language_code> with the code specific to the language of your

3. Save each file to <TOMCATDIR>/Tomcat/conf/Catalina/localhost,
where TOMCATDIR is replaced with the directory where Tomcat is
installed.
4. Restart Tomcat. Go to the directory <TOMCATDIR>/Tomcat/bin and
type the following command:
./shutdown.sh
./startup.sh

1. Locate the desktop.war file. This file is found in the directory
INSTALLDIR is the path where BusinessObjects Enterprise is installed.
2. Open the WAR file and extract adhoc-config.xm from the WEB-INF
directory.
4. Save the file.
Verifying the Tomcat deployment

To verify the Tomcat configuration, make sure that InfoView and the Central
To verify the Tomcat configuration
2. Enter the url for InfoView in the browser using the format http://[host
name]:[port number]/businessobjects/enterprise115/desktoplaunch. For
example:

6


Deploying on WebSphere
chapter
7 Deploying on WebSphere
Before you start
Before you start

Next you should verify that the CMS is running. To view the status of the
CMS, go to the CMC and select Servers.
administrative console in a web browser.
• For IBM WebSphere 5.1, type this:
http://servername:9090/admin.
• For IBM WebSphere 6.0, type this:
http://http://servername:9060/ibm/console
WAR File contents and context roots

This section contains three tables related to the WAR files.
• The first table lists the contents of the WAR files.
• The second table list the context roots that you should use when you
deploy a WAR file.
• The third table lists the location of the WAR files.
Note: As a general rule, WAR files must be deployed on the same machine
as they were installed. This is because the installation will replace some text
variables inside local WAR files with machine and CMS specific values at
install.
The one exception to this rule is the BusinessProcessBI.war file, which can
be copied to any web application server and deployed there. If you plan on
using Trusted Authentication on a different web application server than all
your other BusinessObjects Enterprise application, see “Configuring Trusted
Authentication on a separate web application server” in the BusinessObjects
Enterprise Deployment and Configuration Guide before you deploy the
BusinessProcessBI.war file.
Contents of the WAR files

The table that follows lists the contents of the WAR files.

Before you start 7
WAR File Contents
desktop.war Contains InfoView and performance
management components
If you plan on using Crystal Reports
file.
webcompadapter.war* Contains older components of the
Central Management Console
jsfadmin.war* Contains newer components of the
admin.war* Contains the administrative tools from
the admin launchpad. These tools
include administrative tool console,
Schedule Manager, Instance Manager,
View Server Summary, Query Builder,
Object Repository Helper
afhelp.war Contains performance management help
files
adhoc.war* Contains Crystal Reports Explorer
components
styles.war Contains images, style sheets, and
scripts used by the DHTML and Web
Authoring components of OLAP
Intelligence
AnalysisHelp.war Contains OLAP Intelligence help files
dswsbobje.war Contains Web Services.
BusinesProcessBI.war Contains Business Process BI Service
Note:
• If you install performance management after your initial instalationl and
deployment of BusinessObjects Enterprise, you will need to undeploy
desktop.war and then redeploy it so that changes in the destop.war file
are reflected and the performance management features are visibile.
This is not required if you install BusinessObjects Enterprise at the same
time as performance management because the war file is modified by the
performance management install before you deploy it.
• If you will not be using Crystal Report Explorer, you are not required to
deploy adhoc.war.

Before you start
• If you will not be using OLAP Intelligence, you are not required to deploy
AnalysisHelp.war or styles.war.
• If you will not be using Web Services, you are not required to deploy
dswsbobje.war.
• If you will not be using Business Process BI Service, you are not required
to deploy BusinessProcessBI.war.
Context roots of the WAR files

The table that follows lists the context roots that should be used when you
deploy the war files.
War File Context Root

desktop.war /businessobjects/enterprise115/desktoplaunch
webcompadapter.war /businessobjects
jsfadmin.war /jsfadmin
admin.war /businessobjects/enterprise115/adminlaunch
afhelp.war /bobje
styles.war /styles
AnalysisHelp.war /analysishelp
adhoc.war /businessobjects/enterprise115/adhoc
dswsbobje.war /dswsbobje
BusinessProcessBI.war /BusinessProcessBI
Note:
• It is not recommended that you alter the context root because many of
the war file have dependence on each other. For example, if you change
the context root of either jsfadmin.war or webcompadapter.war, calls
made between different components of the Central Management
Console will not work.
• Desktop.war can be deployed at any time. The remaining files have
dependencies so must be deployed in a specific order. First deploy the
Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war and dswsbobje.war
can now be deployed.
• Desktop.war can be deployed without webcompadapter.war. However, if
you deploy it on a web application server without webcompadapter.war,
you will not be able to not be able to use the InfoView function to add
documents from your local computer to InfoView.

Deploying on IBM WebSphere 7
Enterprise.
WAR File Location

admin.war, adhoc.war,
enterprise115/java/
applications/olap
BusinessProcessBI.war enterprise115/web services/
<language_code>
afhelp.war <INSTALLDIR>/bobje/performance
management 115If performance
management is not installed, this WAR
file will not be present.
Note: Replace <language_code> with the code specific to the language of
Deploying on IBM WebSphere

If you have WebSphere 5.1 or 6.0 and you want it to work with
BusinessObjects Enterprise, you must perform some configuration and
deploy the war files so you are able to use InfoView and the Central
Management Console. The first part of this section explains how to perform
steps such as:
• “Creating an application server” on page 118
• “Starting the application server” on page 118
• “Modifying the startup script” on page 118
• “Starting the application server” on page 118
• “Modifying the startup script” on page 118
• “Modifying the PATH” on page 123
• “Making configuration changes for distributed performance management”
on page 120
• “Checking or changing the assigned port number on WebSphere 5.1” on
page 125

• “Checking or changing the assigned port number on WebSphere 6.0” on

page 125
• “Creating a new virtual host” on page 126
• “Assigning an alias to the virtual host” on page 126
The end of this section explains how you can verify the configuration a
deployment. See “Verifying the WebSphere Configuration” on page 128, for
more information.
Creating an application server

An application server is required. If you have already created one specifically
for use with BusinessObjects Enterprise, you can skip this step.
To create an application server in WebSphere
1. Start the IBM WebSphere Administrative Console in your browser.
2. Logon to the administrative console.
3. Expand Servers and then click on Application Servers.
4. Click New.
5. Enter a name for the server in the Server Name field, and then click
Next.
6. Click Finish to create the new application server.
7. Click the hyperlink Save.
8. Click Save to save the configuration files.
Starting the application server

To start the application server on UNIX
• Start the server. Go to the directory <WSINSTALLDIR>/WebSphere/
AppServer/bin where WSINSTALLDIR is the directory where WebSphere
is installed. Issue the following command, where servername is the
name of your application server:
./startServer.sh servername
Note: You may require sudo authority on your UNIX machine to start the
server. This type of authority is granted by your UNIX administrator.
Modifying the startup script

The startup script used for WebSphere must be modified for these reasons:

• To specify the location of the BusinessObjects Enterprise
environment shell.
• To append the set path variable.
To modify the startup script
1. Locate and open startServer.sh.
2. Specify the location of the BusinessObjects Enterprise environment shell.
Add the following line to startServer.sh but replace INSTALLDIR with
your install directory:
source <INSTALLDIR>/bobje/setup/env.sh
3. Append the path environment variable that is used on your operating
system with the location of BusinessObjects Enterprise specified in the
following table. The options are as follows:

System
export LIBPATH
risc:$SHLIB_PATH
export SHLIB_PATH

4. If you are using the DHTML viewer for OLAP Intelligence, you must also
append the path variable with the location for the OLAP Intelligence
DHTML Viewer.

System
>/bobje/enterprise115/solaris_sparc/
olap/bin:$LD_LIBRARY_PATH
enterprise115/aix_rs600/olap/
bin:$LIBPATH
export LIBPATH
5. Save and close startServer.sh.
Making configuration changes for distributed

If you are deploying performance management on WebSphere in a distributed
environment some configuration changes may be required. A distributed
performance management install is one where the BusinessObjects
Enterprise components are installed on a different machine. For installation
details, see “Performing a distributed install of performance management” on
page 106, for configuration details, see “Copying your performance
management InitConfig. properties file” on page 120.
Copying your performance management InitConfig. properties file

If you are using WebSphere you must copy the InitConfig.properties file to a
different that has no spaces in the directory name.
To specify the location of your InitConfig.properties file
1. Create a directory that has no spaces in its’ name.
2. Copy the InitConfig.properties file from the location that follows to the
directory you created in the previous step.
The default location for this file is as follows:
<INSTALLDIR>\Performance_Management_115
Replace INSTALLDIR with the location where you installed

Changing the classpath
To change the classpath
1. Click on the server you created in Starting the application server or click
on the server designated for use with BusinessObjects Enterprise.
Note: If you aren’t logged on:
a. Log into the administrative console.
b. Expand Server, a click on Application Servers and then
servername.
2. Go to the JVM page.
• If you are using WebSphere 5.1, follow these steps to get to the JVM
page.
a. On the server page, scroll down until you see Process
Definition in the Additional Properties column.
b. Click on Process Definition.
c. Scroll down and click on Java Virtual Machine.
page.
a. On the server page, select Java and Process Management.
b. Select Process Definition.
c. Select Java Virtual Machine.
• Enter the absolute path, including the file name for where
cewcanative.jar is located in the classpath field.
<INSTALLDIR>/bobje/enterprise115/java/applications/
cewcanative.jar
Note: The location of this file is <INSTALLDIR>/bobje/
enterprise115/java/applications. Replace <INSTALLDIR>
with the location of your installation.
3. If you are using performance management, click Generic JVM
arguments then type the location of your InitConfig.Properties file.
-Daf.configdir=<INSTALLDIR>/Performance_Management_115
Note: If you changed the default location for the InitConfig.properties file,
specify the modified location for this file. See “Copying your performance
management InitConfig. properties file” on page 120 for further
information.

4. If you are using the DHTML viewer and OLAP Intelligence, click Generic
JVM arguments and then add the following single line to the JVM
arguments:
Note:
• Replace aix_rs600, dbclient_aix and LIBPATH with the
platform name and pathname variable that applies to your
installation. The platform name options for Solaris are as follows:
solaris_sparc, dbclient_solaris and LD_LIBRARY_PATH
• The text should be entered as a single line, with spaces separating
the arguments (denoted by the "-D").
• The following argument is not required if you are using WebSphere
5.1:
-Dbusinessobjects.olap.xslt.TransformerFactory
5. Enter the following information in the Boot Classpath field.
<INSTALLDIR>/bobje/enterprise115/solaris_sparc
Replace INSTALLDIR with the location of your installation and replace
solaris_sparc with the platform name that applies to your installation.
The platform name options are as follows:
• aix_rs6000
• linux_x86
• hpux_pa_risc
6. Click Apply, and then click Save.
7. Stop the server.
8. Restart the server.

Setting the heap size
You may be prompted to set the heap size. Follow these steps if you are
prompted to set the heap size.
To change the heap size
on the server designated for use with BusinessObjects Enterprise.
Note: If you aren’t logged on:
a. Log into the administrative console.
b. Expand Server, a click on Application Servers and then
my_server_name.
2. Go to the JVM page.
page.
a. On the server page, scroll down until you see Process
Definition in the Additional Properties column.
b. Click on Process Definition.
c. Scroll down and click on Java Virtual Machine.
page.
a. On the server page, select Java and Process Management.
b. Select Process Definition.
c. Select Java Virtual Machine.
3. Scroll down until you see Initial Heap Size.
4. Enter 512 in the Initial Heap Size field.
5. Enter 1024 in the Maximum Heap Size field.
6. Click Save.
Modifying the PATH

To set the Path environment variable
on the server designated for use with BusinessObjects Enterprise
2. Scroll down until you see Process Definition in the Additional
Properties column.
3. Click on Process Definition.

4. Scroll down until you see Environment Entries in the Additional

Properties column.
5. Click on Environment Entries.
6. Click New.
7. Type PATH in the Name field.
8. Enter the following in the Value field, and click OK:
• aix_rs6000
• linux_x86
• hpux_pa_risc
9. Click New.
10. Type the pathname variable used on your operating system in the Name
field.
Operating Variable
System
For Solaris LD_LIBRARY_PATH
For AIX LIBPATH
For Linux LD_LIBRARY_PATH
For HPUX SHLIB_PATH
11. Enter the following in the Value field, and click OK:
• aix_rs6000
• linux_x86
• hpux_pa_risc
12. Click Apply, and then click Save.
13. Click Save.

Checking or changing the assigned port number on
WebSphere 5.1
To check or change the assigned ports
1. Select your server. Expand Servers, click on Application Servers then
click on your server.
2. Click on Web Container under Additional Properties.
3. Click on HTTP transports.
4. Select a new port or note the http port assigned:
• To change the port, click on the link under host beside the port you want
to change, enter the new port and click OK.
• Note the port number used. This will be required when you create a new
virtual host.
Checking or changing the assigned port number on

WebSphere 6.0
On WebSphere 6.0, the use of HTTP transports is deprecated, therefore, you
have to configure a transport chain instead of just entering http the port
number the same way you would with 5.1.
To create a transport chain for http
1. In the administrative console, click Servers > Application servers >
servername.
2. Select Web container settings, and then click Web container transport
chains.
3. Click New.
The Create New Transport Chain wizard appears.
4. Specify a name for the new chain.
5. Select a transport chain template.
6. Select a port, if one is available to which the new transport chain is
bound.
7. Click Finish.
8. Restart the application server.

Creating a new virtual host

To create a new virtual host
1. Expand Environment, select Virtual Host and then click New.
2. Enter the host name in the Name field, and then click OK.
Assigning an alias to the virtual host

To assign an alias
1. Expand Environment variables, select Virtual Hosts and then click on
the host you created.
2. Click Host Aliases under Additional Properties.
3. Click New.
4. Enter the host name of the machine that the server is running on and the
port from Checking or changing the assigned port number on WebSphere
5.1.
5. Click OK.

To deploy the WAR files
1. Go to the administrative console.
2. Expand Applications, and then click Install New Application
3. Click Browse and then find the location of the war files.
Note: The WAR files can be found in the location <INSTALLDIR>/
bobje/enterprise115/java/applications, where INSTALLDIR is
the directory where you installed BusinessObjects Enterprise.
4. Select the WAR file you want to deploy, and then click OPEN.
5. Type the context root for the WAR file in the Context Root field, and click
Next.
6. Select these options on the next screen, then click Next:
• “Generate Default Bindings”

• “Use default virtual host name for Web modules”
Note: Ensure default_host is displayed in the host name field.
7. Accept the defaults on each page and click Next until you get to this step:
• For WebSphere 5.1 “Step:3 Map modules to application servers”.
• For WebSphere 6.0 “Step:2 Map modules to servers”.
Note: Each page may take several minutes to process.
8. Select the application server you created from the Clusters and Servers
field.
9. Select the module to apply it to, and then click Apply.
10. Click Next, and then click Finish.
You will receive message when the process is complete.
11. Repeat the process for the remaining WAR files you wish to deploy.
See “Contents of the WAR files” on page 114 for information on what
each WAR file contains. You are not required to deploy a war file if you
don’t require a component it contains.
Note: Desktop.war does not depend on any of the other war files so it
can be deployed at any time. The remaining files have dependencies on
each other so must be deployed in a specific order. First deploy the
webcompadapter.war., followed by jsfadmin.war and finally admin.war.
Ensuring War file is started

After the WAR file has been deployed, it may need to be started.
To start the WAR file
1. From the administration console, expand Applications, and select
Enterprise Applications.
2. Select the WAR file you deployed, and click Start.

If you want to integrate Crystal Reports Explorer with InfoView, you have to
modify the war file for InfoView (desktop.war) before you it.
1. Locate the desktop.war file.

This file is found in the directory <INSTALLDIR>/bobje/enterprise115/

java/applications, where INSTALLDIR is the path where
BusinessObjects Enterprise is installed.
Note: Be sure you make this change before you deploy desktop.war.
2. Open the zip file and extract adhoc-config.xml.
This file is located in the WEB-INF directory.
4. Save the file.
After you deploy adhoc.war, you will be able to access Crystal Reports
Explorer if you enter http://servername:portnumber/businessobjects/
enterprise115/ached in your browser.
Verifying the WebSphere Configuration

To verify the configuration, make sure that InfoView and the Central
To verify the WebSphere configuration
2. Enter the url for the desktop launchpad in the browser using the format
http://[servername]:[port number]/businessobjects/enterprise115/
desktoplaunch. For example:
Note: You cannot use the shortcuts in the BusinessObjects Enterprise
program group to access the BusinessObjects Enterprise Launchpads
deployed on your Java web application server. To access them, you must
include the port number of the Java web application server in your URL.
That is, to access the InfoView running on your Java web application server,
type:
http://servername:portnum/businessobjects/enterprise115/desktoplaunch/
InfoView/default.htm

To access the BusinessObjects Enterprise Administration Launchpad running
on your Java web application server, type:
http://servername:portnum/businessobjects/enterprise115/adminlaunch/
launchpad.htm
where servername is the name of the server, and portnum is the port
number of the Java web application server.


Deploying on WebLogic
chapter
8 Deploying on WebLogic
Before you start
Before you start

administrative console in a web browser. For BEA WebLogic 8, type http://
servername:7001/console.

deploy a WAR file.
install.

WAR File Contents

webcompadapter.war Contains older components of the
jsfadmin.war Contains newer components of the

Before you start 8
WAR File Contents
If you plan on using Crystal Reports
file.
admin.war Contains the administrative tools from
files
If performance management is not
installed.
adhoc.war Contains Crystal Reports Explorer
components
Intelligence
dswsbobje.war Contains Web Services
BusinessProcessBI.war Contains Business Process BI
Note:
• If you install performance management after your initial install and
desktop.war and then redeploy it. This is not required if you install
BusinessObjects Enterprise at the same time as performance
management because the war file is modified by the performance
management install before you deploy it.
deploy adhoc.war.
either AnalysisHelp.war or styles.war.

Before you start
dswsbobje.war.
• If you will not be using Business Process BI, you are not required to
deploy BusinessProcessBI.war.
• If you will not be using performance management, you are not required to
deploy afhelp.war.


afhelp.war /bobj
styles.war /styles
AnalysisHelp.war /AnalysisHelp
Note:
the war file have dependencies on each other. For example, if you
change the context root of either jsfadmin.war or webcompadapter.war,
calls made between different components of the Central Management

Deploying on BEA WebLogic 8
The table that follows lists the locations of the WAR files.
WAR File Location

jsfadmin.war, desktop.war, enterprise115/java/
admin.war, adhoc.war, applications
enterprise115/java/
applications/olap
dswsbobje.war <INSTALLDIR>/bobje/
<language_code>
Performance_Management 115If
present.
Note: Replace language_code with the code specific to the language of

Note:
• Replace language_code with the code specific to the language of your
Deploying on BEA WebLogic

If you have WebLogic 8.1 and you want it to work with BusinessObjects
Enterprise, you need to perform some configuration and deploy the war files
so you are able to use InfoView and the Central Management Console. The
first part of this section explains how to perform steps such as:
• Setting the context root
• Changing the CLASSPATH in WebLogic
• Setting up the JAR files
• Deploying the WAR files
The end of this section explains how you can verify the configuration. See
“Verifying the WebLogic Configuration” on page 145, for more information.

Setting the context root

The WAR files have no weblogic.xml deployment descriptor file inside. This
means that WebLogic will deploy each web Module under the Context Root of
the file name, (e.g. desktop.war under the Context Root of /desktop), unless
you specify otherwise. If you want to choose a context root other than the file
name, complete this step; otherwise, skip this step.
There are two ways you can do this:
• You can use WebLogic Builder to modify the context root.
Note: If you want to use WebLogic builder, you must have X Windows
installed and configured.
• You can use any UNIX editor and create a weblogic.xml file that specifies
the context root of your choice.
Note: You can't change the Context Root once the WAR file has been
deployed.
To set the context root with WebLogic Builder

1. Open an X Windows session and connect to your UNIX machine.
2. Start WebLogic Builder.
./startWLBuilder.sh
If you have WebLogic 8.1 installed, this script is located in
<INSTALLDIR>/bea/weblogic81/server/bin. If you have another version
of WebLogic installed, you will have to modify your path accordingly.
3. From the File menu in WebLogic Builder, select Open.
4. Browse and select the first WAR file you want and click Open.
The WAR files can be found in the location <INSTALLDIR>/bobje/
enterprise115/java/applications, where INSTALLDIR is the
directory where you installed BusinessObjects Enterprise.
5. Click the Context Path tab.
6. Enter the context path for the WAR file you selected from the following
table.
WAR File Context Path

desktop.war /businessobjects/
enterprise115/
desktoplaunch
admin.war /businessobjects/
enterprise115/adminlaunch

afhelp.war /bobj
adhoc.war /businessobjects/
enterprise115/adhoc
styles.war /styles
7. Click File and then Save.
8. Click File and then Exit.
9. Repeat steps 3 to 8 for any remaining WAR files.
Setting the context root with an editor

To set the context root using a Unix editor
1. Create a directory called WEB-INF.
2. Copy all the WAR files to the WEB-INF directory.
The WAR files are found in the following location: <INSTALLDIR>/
bobje/enterprise115/java/applications
3. Create a file called weblogic.xml.
<weblogic-web-app>
<context-root>/context path</context-root>
</weblogic-web-app>
5. Replace context path with the context path that applies to the WAR
file.

enterprise115/
desktoplaunch


afhelp.war /bobj
enterprise115/adhoc
styles.war /styles
7. Add weblogic.xml to the WAR file.
jar -uvf <WAR_NAME_TO_BE_UPDATED> WEB-INF/weblogic.xml
8. Modify weblogic.xml with the context root for the second WAR file.
11. Repeat the previous three steps until all the required context paths are
changed.
Tip: You do not need to specify the context path for the WAR files adhoc,
AnalysisHelp, styles or dswsbobje since WebLogic already assumes a
context root is the same as the file name.
Copying your performance management

InitConfig.properties file
If you have performance management in a distributed environment, you must
copy the InitConfig.properties file from one machine to the other so that you
can log on to performance management. If you are using UNIX, you may
need to copy the InitConfig.properties file to a different that has no spaces in
the directory name.
1. Create a new folder on the drive on which BusinessObjects Enterprise is
installed.
Note: The folder name cannot contain spaces.
2. Copy the InitConfig.properties file to the folder you created in the
previous step.

C:\Program Files\Business Objects\Performance Management
11.5

<INSTALLDIR>/Performance_Management 115
Preparing afhelp.war for deployment

If you are deploying performance management, You will need to add a
web.xml to the afhelp.war. This is the war file that contains the help for
performance management; This step must be completed before deploy the
WAR file that contains the help for performance management.
To prepare the afhelp.war file
1. Create a temporary directory and in this directory, create a new directory
called WEB-INF.
2. Create a file called web.xml.
3. Copy the following text into the web.xml file:
<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//
EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>

<display-name>afhelp</display-name>
<description>
afhelp.
</description>
</web-app>
4. From the temporary directory, update the afhelp.war file using the
following command:
jar uf /the/path/to/afhelp.war ./WEB-INF/web.xml

Creating the Domain

This step details how to create a domain on WebLogic with the Configuration
Wizard. If you already have a domain created, you can skip this step and
perform the rest of the steps on the domain you plan to use for
Note: See the BEA WebLogic documentation for alternate methods of
creating a domain.
To Create the Domain in WebLogic
2. Launch the WebLogic Configuration Wizard. Go to the directory
<INSTALLDIR>/weblogic81/common/bin, where INSTALLDIR is the
directory where you installed WebLogic, and then type the following
command:
./quickstart.sh
.
3. Select Create a new WebLogic configuration, or extend an existing
one, and then click Next.
4. Select Create a new WebLogic configuration, and then click Next
5. Select Basic WebLogic Server Domain from the list of Configuration
Templates, and click Next.
6. Select Express from the Choose Express or Custom Configuration
dialog, and click Next.
7. Enter a User Name and Password. Confirm the password, and then click
Next.
Tip: Remember this information or you will not be able to use WebLogic
later.
8. Specify the Startup Mode and optionally which SDK to use, and then click
Next.
9. Click Create on the Create WebLogic Configuration dialog.
Tip: The default name for your domain is mydomain. Modify the
Configuration Name field if you want to change the default name.
You will receive a message when the configuration completes.
10. Click Done, and then click Exit

Changing the CLASSPATH in WebLogic
WebLogic needs to know where BusinessObjects Enterprise components are
installed. This is done in the following ways:
• Setting the CLASSPATH
• Setting the PATH
• Setting either the LD_LIBRARY_PATH, the LIBPATH or the
SHLIB_PATH, depending on your operating system, in the configuration
file WebLogic uses when it starts up.
To set the CLASSPATH in WebLogic
1. Open the WebLogic loader script in a text editor. On UNIX, this file is
called StartWebLogic.sh, and can be found in the directory
[WebLogic_Home]/user_projects/domains/domainname, where
WebLogic_Home is the directory where WebLogic is installed and
domainname is the name of your domain.
2. Locate the CLASSPATH definition.
Append the CLASSPATH with the path for cewcanative.jar, including
cewcanative.jar. This JAR file can be found in the location
INSTALLDIR is the directory where you installed BusinessObjects
Enterprise.
3. Add the path definition that is used on your operating system:

System
For Solaris LD_LIBRARY_PAT LD_LIBRARY_PATH=<INSTALLDIR>
H /bobje/enterprise115/
solaris_sparc:${LD_LIBRARY_PATH}
enterprise115/
aix_rs6000:${LIBPATH}
export LIBPATH


System
For Linux LD_LIBRARY_PAT LD_LIBRARY_PATH=<INSTALLDIR>
H /bobje/enterprise115/
linux_x86:${LD_LIBRARY_PATH}
For HPUX SHLIB_PATH SHLIB_PATH=<INSTALLDIR>/bobje/
enterprise115/hpux_pa-
risc:${SHLIB_PATH}
export SHLIB_PATH
Note: Replace INSTALLDIR with your install directory.
append the pathname variable with the location for the OLAP Intelligence
DHTML Viewer.
<INSTALLDIR>/bobje/enterprise115/solaris_sparc/olap/bin
Note:
• Entries are separated with a colon.
• If you are using AIX, replace solaris_sparc with aix_rs6000.
5. Add the PATH definition:
PATH="<INSTALLDIR>/bobje/enterprise115/applications/
:${PATH}"
export PATH
Modifying the WebLogic environment script

The environment script used for WebLogic must be modified to specify the
location of the BusinessObjects Enterprise environment shell.
To modify the environment script
1. Locate and open setWLSEnv.sh.
Note:
• Replace INSTALLDIR with your install directory.
• Depending on the shell you are using, you may need to replace
source with the . (dot operator). See “Sourcing the script that
identifies the database environment variables” on page 19 for details.

3. Save and close setWLSEnv.sh.
Setting the Java Virtual Machine options for OLAP

Intelligence and performance management
If you want to use the OLAP Intelligence DHTML viewer or performance
management, you must modify the Java Virtual Machine (JVM) options in
WebLogic.
To add the JVM options in WebLogic
1. If you want to use the OLAP Intelligence DHTML viewer, open the file
startWeblogic.sh and add the following after the PATH and
CLASSPATH settings:
Note:
• solaris_sparc and dbclient_solaris and
LD_LIBRARY_PATH
2. If you want to use performance management, add the location for the
Initconfig.properties file to the Java options.
-Daf.configdir="<INSTALLDIR>/Performance_Management 115

management InitConfig.properties file” on page 138 for more information.
Setting up the JAR files

This next section explains how to prepare .JAR files to deploy Voyager on the
WebLogic application server.
To prepare the JAR files
1. Manually copy the following 5 jar files to the following directory on
directory on your web application server.
JAVA_HOME>\jre\lib\endorsed
• Xalan.jar
• xercesImpl.jar
• xml-apis.jar
• xbean.jar
• jsr173_1.0_api.jar
If the endorsed directory does not exist, you must manually create it.
2. On UNIX, copy all five jar files from the the following directory:
BOE_HOME>/bobje/java/lib/external.

1. Start the WebLogic Admin server. Go to the directory [WebLogic_Home]/
user_projects/domains/, where WebLogic_Home is the directory where
WebLogic is installed, and then execute startWebLogic.sh.
2. Launch the Admin console. Open a browser window, type http://<host
name>:7001/console and then press Enter.
3. Enter the username and password.
4. Expand Deployments on the left pane, and then select Web Application
Modules.
5. Click Deploy a New Web Application Module from the right pane.
6. Navigate to the location of the webcompadapter.war.
Note: See “Locations of the WAR files” on page 135 for information on
the war file locations.
7. Click the button beside the file, and then click Target Module.
The Review your choices and deploy window will appear.

8. Click Deploy. It may several minutes for the deployment to complete.
9. Repeat steps 4 to 8 to deploy the remaining WAR files you wish to
deploy.
don’t require a component it contains.
can be deployed at any time. The remaining files have dependencies so
must be deployed in a specific order. First deploy the
webcompadapter.war., followed by jsfadmin.war and finally admin.war.

If you want to integrate Crystal Reports Explorer with InfoView, you must first
modify the war file for InfoView (desktop.war).
2. Open the WAR file and extract adhoc-config.xml.
4. Save the file.
enterprise115/adhoc in your browser.
Verifying the WebLogic Configuration

To verify the WebLogic configuration
Enter the url for the desktop launchpad in the browser using the format
http://[host name]:[port number]/businessobjects/enterprise115/

• To access the InfoView running on your Java web application server,
type:
http://server01:portnum/businessobjects/enterprise115/
desktoplaunch
• To access the BusinessObjects Enterprise Administration Launchpad
running on your Java web application server, type:
adminlaunch
where server01 is the name of the server, and portnum is the port number
of the Java web application server.

Deploying on WebLogic 9.2
with the JDK 1.5
chapter
9 Deploying on WebLogic 9.2 with the JDK 1.5
Before you start
Before you start

administrative console in a web browser. For BEA WebLogic 9.2, type
http://servername:7001/console.

deploy a WAR file.

WAR File Contents

desktop.war Contains InfoView, performance
management, and Voyager components.
admin.war Contains the administrative tools from the
admin launchpad. These tools include
administrative tool console, Schedule
Manager, Instance Manager, View Server
Summary, Query Builder, Object
Repository Helper
components
Intelligence

Deploying on WebLogic 9.2 with the JDK 1.5
Before you start 9
WAR File Contents
files
Note: If performance management is not
installed.
Note:
deploy adhoc.war.
dswsbobje.war.
deploy afhelp.war.


afhelp.war /bobj
styles.war /styles

Before you start
Note:
Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war, dswsbobje.war, and

The table that follows lists the locations of the WAR files.
WAR File Location

enterprise115/java/
applications/olap
<language_code>
afhelp.war Note: <INSTALLDIR>/
Performance_Management_115/If
present.
Note:
• Replace language_code with the code specific to the language of your

Deploying on BEA WebLogic 9.2 9
Deploying on BEA WebLogic 9.2
If you have WebLogic and you want it to work with BusinessObjects
Enterprise, you need to perform some configuration and deploy the war files
so you are able to use InfoView and the Central Management Console. The
first part of this section explains how to perform these steps.
These are the basic steps:
• Creating a domain
• Setting the context root
• Setting required variables in startup script
If you are also deploying performance management, see the following tasks
in addition to the basic steps previously outlined:
• Copying your performance management InitConfig. properties file
• Preparing afhelp.war for deployment
• Setting the Java Virtual Machine options for OLAP Intelligence and
• If you want to use performance management, you must modify the Java
Virtual Machine (JVM) options in WebLogic.
If you are also deploying Crystal Reports Explorer, see the following task in
addition to the basic steps previously outlined:
• “Integrating Crystal Reports Explorer with InfoView” on page 161
The end of this section explains how you can verify the configuration. See
“Verifying the WebLogic Configuration” on page 161, for more information.
Creating a domain
This step details how to create a domain on WebLogic with the Configuration
Wizard. Consult the BEA WebLogic documentation for alternate methods of
creating a domain, such as using weblogic.server from the command line. If
you already have a domain created, you can skip this step and perform the
rest of the steps on the domain you plan to use for BusinessObjects
Enterprise.
Note: In order to use the Configuration Wizard on unix you must have X
Windows installed and configured.

Creating a domain with WebLogic on unix

To create a domain in WebLogic on unix with the Configuration Wizard
2. Go to the following directory, where WebLogic_Home is directory where
WebLogic is installed:
WebLogic_Home/weblogic92/common/bin
3. Enter the following command:
config.sh
4. Select Create a new WebLogic domain, and then click Next.
5. Select Generate a domain configured automatically to support the
following BEA products:, then click Next.
6. Enter a User Name and Password. Confirm the password, and then click
Next.
Tip: Record this information as it will be required later to log on.
7. On the on the Configure Server Start Mode and JDK, in the JDK
Selection area of the page, select either of these JDKs:
• Sun JDK 1.5
• JRockit JDK 1.5
Note: The Sun JDK 1.5 is the one that begins with Sun SDK 1.5. The
JRockit JDK is the one that begins with JRockit SDK 1.5
8. Click Next.
9. Select No on the Customize Environment and Services Settings
page, then click Next.
10. Enter the domain name and specify the location of the domain, if you
want to modify the defaults, then click Create.
You will receive a message when the configuration completes.
11. Click Done.
Note: To start the administration server for the domain you are creating,
select the check box beside Start Admin Server before you click Done.

Setting the context root
The WAR files have no weblogic.xml deployment descriptor file inside. This
means that WebLogic will deploy each web Module under the Context Root of
the file name, (e.g. desktop.war under the Context Root of /desktop), unless
you specify otherwise. If you want to choose a context root other than the file
name, complete this step; otherwise, skip this step.
Unlike WebLogic 8.1, WebLogic 9.2 is not shipped with WebLogic Builder so
you cannot use it to add a deployment descriptor inside the war file. Instead,
you can use an editor and create a weblogic.xml file that specifies the context
root of your choice.
Note: You cannot change the Context Root once the WAR file has been
deployed.
Setting the context root with an editor

To set the context root using an editor
called WEB-INF.
2. Create a file called weblogic.xml in the WEB-INF directory.
<weblogic-web-app>
<context-root>/context path</context-root>
</weblogic-web-app>
4. Replace context path with the context path that applies to the WAR
file.

enterprise115/
desktoplaunch
afhelp.war /bobj
enterprise115/adhoc


styles.war /styles
From the temporary directory, run this command:
jar -uvf <WAR_NAME_TO_BE_UPDATED> WEB-INF/weblogic.xml
7. Repeat the steps 3 to 6 until all the required context paths are changed.
Tip: You do not need to specify the context path for the WAR files
jsfadmin, AnalysisHelp, styles or dswsbobje since WebLogic already
assumes a context root is the same as the file name.
Deploying performance management

The following steps are necessary only if you are deploying performance
management:
• Copying your performance management InitConfig. properties file
• Setting required variables in startup script
Copying your performance management InitConfig. properties file

can log on to performance management.
To specify the location of your InitConfig.properties file on Unix
1. Create a directory.
<INSTALLDIR>/Performance_Management_115

If you are deploying performance management, you will need to add a
performance management; This step must be completed before deploy the
WAR file that contains the help for performance management.
called WEB-INF.
2. Create a file called web.xml in the WEB-INF directory.
<?xml version="1.0"?>
EN"
<web-app>
<description>
afhelp.
</description>
</web-app>
following command:
Setting the Java Virtual Machine options for OLAP

Intelligence and performance management
If you want to use performance management, you must modify the Java
Virtual Machine (JVM) options in WebLogic.
To add the JVM options in WebLogic
1. Open the WebLogic loader script in a text editor.
This file is called StartWebLogic.sh, and can be found in the directory
[WebLogic_Home]/user_projects/domains/domainname/bin, where
domainname is the name of your domain.

<INSTALLDIR>/bobje/enterprise115/<aix_rs6000>/olap/
Note:
• solaris_sparc and dbclient_solaris and
LD_LIBRARY_PATH
2. If you want to use performance management, add the location for the
Initconfig.properties file to the Java options.
-Daf.configdir="<INSTALLDIR>/Performance_Management_115
management InitConfig. properties file” on page 154 for more
information.
Setting required variables in startup script

WebLogic needs to know where BusinessObjects Enterprise components are
installed. This is done in the following ways:
• Setting the CLASSPATH
• Setting the PATH

• Setting either the LD_LIBRARY_PATH, the LIBPATH or the
SHLIB_PATH, depending on your operating system, in the configuration
file WebLogic uses when it starts up.
To set the CLASSPATH in WebLogic for unix
1. Open the WebLogic loader script in a text editor. On UNIX, this file is
called StartWebLogic.sh, and can be found in the directory
[WebLogic_Home]/user_projects/domains/base_name/bin, where
base_name is the name of your domain.
2. Locate the CLASSPATH definition.
Append the CLASSPATH with the path for cewcanative.jar, including
cewcanative.jar. This JAR file can be found in the location
INSTALLDIR is the directory where you installed BusinessObjects
Enterprise.
3. Add the path definition appropriate for your installation immediately
before the CLASSPATH definition.

System
For LD_LIBRARY_PATH LD_LIBRARY_PATH=<INSTALLDIR
Solaris >/bobje/enterprise115/
solaris_sparc:${LD_LIBRARY_PATH
}
enterprise115/
aix_rs6000:${LIBPATH}
export LIBPATH
linux_x86:${LD_LIBRARY_PATH}
risc:${SHLIB_PATH}
export SHLIB_PATH
Note: Replace INSTALLDIR with your install directory.

append the pathname variable with the location for the OLAP Intelligence
DHTML Viewer.
Note:
• Entries are separated with a colon.
• If you are using AIX, replace solaris_sparc with aix_rs6000.
5. Add the following immediately before the CLASSPATH definition:
PATH="<INSTALLDIR>/bobje/enterprise115/applications/
:${PATH}"
export PATH
Modifying the WebLogic environment script

The environment script used for WebLogic must be modified to specify the
location of the BusinessObjects Enterprise environment shell.
To modify the environment script
1. Open setWLSEnv.sh from the following location, where WebLogic_Home
is directory where WebLogic is installed:
WebLogic_Home/server/bin
Note:
• Replace INSTALLDIR with your install directory.
• If you are using a unix shell that does not support the syntax source,
use . (dot operator) instead. Consult your the documentation
specific to your Unix shell environment for details.
3. Save and close setWLSEnv.sh.
Changing the default parser and transformer

By default, Weblogic 9.2 uses the parser shipped with JDK 1.5. However,
previous version of WebLogic and BusinessObjects Enterprise XI Release 2
use a different parser. Before you deploy desktop.war, you need to modify the
default version of the parser to use this compatible parser. This version of the
parser is still shipped with Weblogic 9.2.

To change the version of the parser and transformer
1. Open the administration console.
2. Expand Services.
3. Select XML Registries.
4. Click Lock & Edit.
5. Select New.
6. In the Name field on the Create a New XML Registry page, type
BusinessObjects Enterprise Infoview.
7. Enter the following in the Document Builder Factory field:
weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl
8. Enter the following in the SAX Parser Factory field:
weblogic.apache.xerces.jaxp.SAXParserFactoryImpl
9. Enter the following in the Transformer Factory field:
weblogic.apache.xalan.processor.TransformerFactoryImpl
10. Click Next.
11. Specify the server instance you want the changes applied to, then click
Finish.
12. Click Activate Changes.
Adjusting the size of the JVM permanent generation

If you are performing memory-intensive operations such as viewing Crystal
Reports with dynamic and cascading parameters, you may receive an out of
memory error. To avoid this possible issue, you can specify the JVM
PermSize and MaxPermSize options in the WebLogic startup script.
To modify the JVM permanent generation

1. Open the WebLogic startup script in a text editor.
This file is called StartWebLogic.sh, and can be found in the directory
[WebLogic_Home]/user_projects/domains/base_domain/bin, where
WebLogic_Home is the directory where WebLogic is installed and where
base_domain is the name of the domain.
Note: If you followed the steps in “Creating a domain” on page 151,
enter the domain name you entered in this step. If you already had a
domain created for BusinessObjects Enterprise, enter this domain name
instead.
2. Append the following option to the JAVA_OPTIONS:

-XX:PermSize=48m -XX:MaxPermSize=128m
Note: The MaxPermSize can be increased to 256m if necessary.
4. Restart WebLogic.

1. Start the WebLogic Admin server. Go to the directory [WebLogic_Home]/
user_projects/base_domain/, where WebLogic_Home is the directory
where WebLogic is installed and where base_domain is the name of the
domain.
Note: If you followed the steps in “Creating a domain” on page 151,
enter the domain name you entered in this step. If you already had a
domain created for BusinessObjects Enterprise, enter this domain name
instead.
2. Execute the following command:
startWebLogic.sh.
3. Launch the Admin console. Open a browser window, type http://<host
name>:7001/console and then press Enter.
4. Enter the username and password.
5. From the Domain Structure area of the page, click domain_name.
6. Click Deployments.
7. Click Lock & Edit.
8. Click Install.
The Install Application Assistant will appear.
9. Select the location where the WAR files are.
See “Locations of the WAR files” on page 150 for information on where
the WAR files can be found.
Note: The location you choose will remain selected throughout this
procedure unless you change it.
10. Select desktop.war, then click Next.
11. Click Next, then click Finish.
Note: This process takes several minutes for small WAR files to be
deployed, and a greater amount of time for the larger WAR files.
12. Click Activate Changes.

13. Select the deployed WAR file and click Start, then select Servicing all
requests.
14. Click Yes to confirm.
15. Repeat the process from step 6 to 13, for each of these WAR files in the
order they are listed:
• webcompadapter.war
• jsfadmin.war
• admin.war
16. Repeat the process from step 6 to 13 for any other war files you wish to
deploy.
Tip: See “Contents of the WAR files” on page 148 for information on
what each WAR file contains. You are not required to deploy a war file if
you don’t require a component it contains.

If you want to integrate Crystal Reports Explorer with InfoView, you have to
modify the war file for InfoView (desktop.war) before you it.
BusinessObjects Enterprise is installed
2. Open the WAR file and extract adhoc-config.xml from the WEB-INF
directory.
4. Save the file.
enterprise115/adhoc in your browser.
Verifying the WebLogic Configuration

To verify the WebLogic configuration

Enter the url for the desktop launchpad in the browser using the format
type:
desktoplaunch
adminlaunch

Deploying on Oracle
Application Server
chapter
10 Deploying on Oracle Application Server
Before you start
Before you start

administrative console in a web browser. For Oracle 10g, type http://
servername:1810/.

deploy a WAR file.
install.

WAR File Contents


Deploying on Oracle Application Server
Before you start 10
WAR File Contents
admin.war Contains the administrative tools from
files
If performance management is not
installed.
components
Intelligence
BusinessProcessBI.war Contains Business Process BI
Note:
deploy adhoc.war.
dswsbobje.war.
deploy afhelp.war.

Before you start


styles.war /styles
afhelp.war /bobj
Note:

Enterprise.

Deploying with Oracle 10
WAR File Location
enterprise115/java/applications/
olap
BusinessProcessBI.war enterprise115/web services/
<language_code>
afhelp.war <INSTALLDIR>/bobje/performance
management 115

your installation, for example en or fr
Deploying with Oracle

If you have Oracle 10g and you want it to work with BusinessObjects
Enterprise, you must perform some configuration and deploy the war files so
you are able to use InfoView and the Central Management Console. The first
part of this section explains how to perform steps such as:
• “Configuring the Class Path” on page 167
• “Setting the PATH environment variable” on page 169
• “Changing Memory Allocation Pool” on page 168
• “Preparing afhelp.war for deployment” on page 172
• “Setting up the JAR files” on page 171.
The end of this section explains how you can verify the deployment. See
“Verifying the Oracle Configuration” on page 174, for more information.
Configuring the Class Path

1. Open a browser window and enter the following: http://<host
name>:1810. Enter ias_admin for the username, and the password that
was set during the install.
2. Click on the name of the OC4J instance whose class path you will modify.

Note: If the instance is not yet started, select the instance, and then click
Start. After you receive confirmation that the instance has been started,
click on the name of the instance to modify.
3. Click the Administration tab.
4. Click the Global Web Module link under Application Defaults.
5. Click the General link under Properties.
6. Locate the Class Path section of the page
7. Click Add Another Row under Class Paths.
8. Enter the path for cewcanative.jar, including cewcanative.jar, in the path
field.
The default location of this file is <INSTALLDIR>bobje/
enterprise115/applications/cewcanative.jar. Replace
<INSTALLDIR> with the location of your installation.
9. Click Apply.
10. Click OK after you receive confirmation that the message that the
property changes have been saved.
Changing Memory Allocation Pool

Desktop.war takes up more memory to deploy than the allocated default. For
this reason the initial and maximum size of the Memory Allocation Pool must
be changed.
To change the setting for the Memory Allocation Pool
1. Scroll down on the General Server Properties page until you see
Command Line Options.
2. Append the following in the Java Options field:
-Xms128m -Xmx512m
3. Scroll down and click Apply.
4. Click Yes when you receive the message that the application server must
be restarted before the changes take affect.
Note: If you will be deploying the WAR files for OLAP Intelligence or
performance management you can skip this step. Instead, you can
restart your application server at the end of “Changing the command line
options for OLAP Intelligence or performance management” on page 170

Copying your performance management InitConfig.
properties file
can log on to performance management. If you are using UNIX, you may
need to copy the InitConfig.properties file to a different that has no spaces in
the directory name.
<INSTALLDIR>\bobje\performance management 115
Setting the PATH environment variable

To set the PATH
1. Click on the Administration tab for the appropriate instance.
2. Click on Server Properties under Instance Properties.
3. Scroll down until you see Environment Variables.
4. Click Add Environment Variable.
5. Enter the pathname that applies to your operating system in the Name
field.
Note:
Operating Variable
System
For Solaris LD_LIBRARY_PATH
For AIX LIBPATH
For Linux LD_LIBRARY_PATH
For HPUX SHLIB_PATH

6. Enter the absolute path to the BusinessObjects Enterprise operating

system directory, starting and ending with quotes, in the Value field, and
then click Apply.
<INSTALLDIR>bobje/enterprise115/solaris_sparc
Replace solaris_sparc with the platform name that applies to your
installation. The options are as follows:
• aix_rs6000
• linux_x86
• hpux_pa_risc
Changing the command line options for OLAP

Intelligence or performance management
Note: If you are not using OLAP Intelligence or performance management,
these steps are not required.
To change the command line options
1. If you want to use the DHTML Viewer with OLAP Intelligence, append the
following value to your Java Options:
Note:
• Append these values only after you have completed “Changing
Memory Allocation Pool” on page 168. This step contains procedural
details on how to set your Java Options.

• solaris_sparc, dbclient_solaris and
LD_LIBRARY_PATH
2. If you are using performance management, add the following Java
arguments that specify the location of your InitConfig.Properties file.
-Daf.configdir=<INSTALLDIR>/bobje/performance management
115
management InitConfig. properties file” on page 169 for further
information.
3. Click Yes when you receive the message that the application server must
be restarted before the changes take affect.
Setting up the JAR files

This next section explains how to prepare .JAR files to deploy Voyager on the
WebLogic application server.
To prepare the JAR files
1. Manually copy the following 5 jar files to the following directory on
directory on your web application server.
JAVA_HOME>\jre\lib\endorsed
• Xalan.jar
• xercesImpl.jar
• xml-apis.jar
• xbean.jar
• jsr173_1.0_api.jar
If the endorsed directory does not exist, you must manually create it.
2. On UNIX, copy all five jar files from the the following directory:
BOE_HOME>/bobje/java/lib/external.


If you are deploying performance management, You will need to add a
performance management; This step must be completed before you deploy
the WAR file that contains the help for performance management.
called WEB-INF.
2. Create a file called web.xml.
EN"
<web-app>
<description>
afhelp.
</description>
</web-app>
following command:

War files can be deployed from two places:
• From the Administration console.
• From the command line.
You may wish to use the command line if you encounter problems with
the deployment of WAR files when using the Administration Console, due
to limited space in Oracle’s directory /var/tmp.
Note: This may be the case when you deploy the desktop.war that
includes performance management.
To deploy the war files from the Administration Console
1. Click on the Applications tab from the server home.
2. Click Deploy WAR file.

3. Click Browse and then find desktop.war.
Note: The default location for the WAR files is c:\Program Files\Business
objects\BusinessObjects Enterprise 11.5\java\applications. Modify your
path accordingly if you changed the installation default.
Note: The location for the WAR files is <INSTALLDIR>/bobje/
enterprise115/java/applications, where INSTALLDIR is the
directory where you installed BusinessObjects Enterprise.
4. Enter the name you want to call the application in the Application Name
field.
5. Enter the context root for the WAR file in the Map to URL field.
6. Click Deploy.
7. Repeat the process for jsfadmin.war, admin.war and desktop.war. If you
are not using OLAP Intelligence, you do not need to deploy
AnalysisHelp.war or styles.war.
can be deployed at any time. The remaining files have dependencies on
each other so must be deployed in a specific order. First deploy the
Adhocwar.war, AnalysisHelpwar.war, styleswar.war, afhelp.war and
dswsbobje.war can now be deployed.
To deploy the war files from the command line
1. Locate the directory where your instance of Oracle is installed.
2. Go to following directory, where ORACLE_HOME is the location where
Oracle Application Server is installed:
<ORACLE_HOME>/dcm/bin
3. Issue the following command for each WAR file you want to deploy.
./dcmctl deployApplication -co <OC4J_INSTANCE_NAME> -a
<APPLICATION NAME> -f <LOCATION OF THE
APPLICATION>\<WAR/EAR File Name> -rc <ROOT CONTEXT>

1. Stop your web server.


5. Save the file.
Verifying the Oracle Configuration

To verify the Oracle configuration, make sure that InfoView and the Central
To verify the Oracle configuration
http://[hostname]:[port number]/businessobjects/enterprise115/
format http://[hostname]:[port number]/businessobjects/enterprise115/
That is, to access the InfoView running on your Java web application server,
type:
http://server01:portnum/businessobjects/enterprise115/desktoplaunch/
InfoView/default.htm
To access the BusinessObjects Enterprise Administration Launchpad running
on your Java web application server, type:
http://server01:portnum/businessobjects/enterprise115/adminlaunch/
launchpad.htm



3
Deploying on Sun Java

Application Server
chapter
11 Deploying on Sun Java Application Server
Before you start
Before you start

administrative console in a web browser. For Sun Java Application Server
8.1, type http://servername:4848/.
Note: Sun Java Application Server is only supported on Solaris Unix
versions of BusinessObjects Enterprise.

deploy a WAR file.
install.

WAR File Contents

desktop.war Contains Infoview and performance

Deploying on Sun Java Application Server
Before you start 11
WAR File Contents
admin.war Contains the administrative tools from the
admin launchpad. These tools include
administrative tool console, Schedule
Manager, Instance Manager, View Server
Summary, Query Builder, Object
Repository Helper
components
Intelligence
analysishelp.war Contains OLAP Intelligence help files
dswsbobje.war Contains Web Services
Note:
deploy adhoc.war.
either analysishelp.war or styles.war.
dswsbobje.war.


jsfadmin.war. /jsfadmin

Before you start

styles.war /styles
analysishelp.war /AnalysisHelp
Note:
deployed at any time. The remaining files have dependencies so must be
deployed in a specific order. First deploy the webcomponentadapter.war.,
followed by jsfadmin.war and finally admin.war. Adhoc.war,
analysishelp.war, styles.war, afhelp.war and dswsbobje.war can now be
deployed.

Enterprise.
WAR File Location

styles.war, analysishelp.war <INSTALLDIR>/bobje/
enterprise115/java/
applications/olap
<language_code>

Deploying with Sun Java Application Server 11
Deploying with Sun Java Application Server
If you have Sun Java Application Server and you want it to work with
BusinessObjects Enterprise, you must perform some configuration and
deploy the war files so you are able to use InfoView and the Central
Management Console. The first part of this section explains how to perform
steps such as:
• “Configuring the Class Path” on page 181
• “Editing the security.policy file” on page 182
• “Editing the security.policy file” on page 182
The end of this section explains how you can verify the deployment. See
“Verifying the Sun Java Application Server configuration” on page 186, for
more information.
Configuring the Class Path

To configure Class Path of the application server
1. Open a browser window and enter the url for the administration server.
The address for the administration server is http://<host name>:4848,
where host name is the domain name or your server bane. Enter the
username, and the password that was set during the installation or when
you set up your application server domain.
2. Click the link to the instance name where you will deploy the
BusinessObjects Enterprise WAR files.
If you have not created an instance yet, click New and enter the
information for your instance.
3. Click the JVM settings tab.
4. Click the Path Settings link.
5. Enter the full path where the JAR file cewcanative.jar is located in the
Classpath Suffix field.
<INSTALLDIR>/bobje/enterprise115/java/applications/
cewcanative.jar, where INSTALLDIR is the directory where you
installed BusinessObjects Enterprise.
6. Enter the path for the BusinessObjects Enterprise and OLAP Intelligence
DLLs in the Native Lib. Path Suffix field, and then click Save.

Editing the security.policy file

To edit the security.policy file
1. Locate and open the server.policy file for your domain.
This file can be found in the application servers domains/domain1/config
directory.
2. Assign write permission to java.util.PropertyPermission.
3. Assign execute and delete permissions to java.io.FilePermission.
4. Assign listen permission to java.net.SocketPermission.
The modified portion of the file should look similar to the following
example:
// Basic set of required permissions granted to all
remaining code
grant {
permission java.lang.RuntimePermission
"loadLibrary.*";
"queuePrintJob";
permission java.net.SocketPermission "*",
"connect, listen";
permission java.io.FilePermission "<<ALL
FILES>>", "read, write, execute, delete";
// work-around for pointbase bug 4864405
permission java.io.FilePermission
"${com.sun.aas.instanceRoot}${/}lib${/
}databases${/}-", "delete";
permission java.io.FilePermission
"${java.io.tmpdir}${/}-", "delete";
permission java.util.PropertyPermission "*",
"read, write";
"modifyThreadGroup";
};
Updating the JVM settings

To configure the JVM settings and options

where host name is the domain name or your server. Enter the
2. Click the link to the instance name where you will deploy the
BusinessObjects Enterprise WAR files.
3. Click the JVM settings tab.
4. Click the JVM options link.
5. Find the option that sets the heap size setting.
6. Modify the heap size so it matches the setting in the following line, and
then click Save.
-Xms512m -Xmx256m
7. Add the first option which OLAP Intelligence requires, and then click Add.
enterprise115/solaris_sparc/olap
8. Add the second option which OLAP Intelligence requires, and then click
Add.
-Dbusinessobjects.olap.xslt.TransformerFactory=org.
apache.xalan.processor.TransformerFactoryImpl
9. Restart the server.

You can deploy the WAR file one of two ways with Sun Java Application
Server:
• You can use the administration server from a web browser.
• You can use the utility asadmin from the command line in UNIX.
Note: Some of the WAR files must be deployed in a specific order because
files have dependencies on each other. First deploy the
webcomponentadapter.war., followed by jsfadmin.war and finally
admin.war. Then you may deploy Desktop.war and any of the remaining
WAR files you wish to deploy.
To deploy War files using the adminstration server


where host name is the domain name or your server. Enter the
2. Select your application server.
3. Click the icon that expands your instance in the left navigation pane.
4. Click the icon that expands Applications in the left navigation pane
5. Select Web Apps.
6. Click Deploy.
7. Select Specify a package file or a directory path.
8. Enter the path of the WAR file to deploy, or use Browse to locate the
WAR file, and then click OK.
For a list of the WAR files, and their locations, see “Locations of the WAR
files” on page 180.
Note: On some versions of Sun Java Application Server, you may only
be able to choose a local file. You can copy your WAR files over to your
local machine first, or you can use the asadmin utility to deploy your WAR
files.
9. Enter the name you want to call the application in the Application Name
field.
10. Enter the context root specified for the WAR file in the Context Root
field, and then Click OK.
The WAR file will now be deployed.
11. Repeat the 4 previous steps for each WAR file you will deploy.
don’t require a component it contains
Note: Some of the WAR files must be deployed in a specific order
because files have dependencies on each other. First deploy the
webcomponentadapter.war., followed by jsfadmin.war and finally
admin.war. Then you may deploy Desktop.war and any of the remaining
WAR files you wish to deploy.

To deploy WAR files with the asadmin utility
1. Go to the bin directory on your UNIX machine where Sun Java
Application Server is installed. If you have Sun Application Server 7
Edition 7, go to directory /<INSTALLDIR>/SunONEApp7_2004Q/
appserver7/bin, where INSTALLDIR is the directory you specified for
your installation.
2. Use the asadmin deploy command to deploy the first WAR. For specific
information on the BusinessObjects Enterprise WAR files and their
context roots, see “WAR File contents and context roots” on page 178.
The following command would deploy webcompadapter.war:
./asadmin deploy --user YourAdminUser --password
YourAdminPassword --contextroot /businessobjects --
instance YourInstanceName <INSTALLDIR>/bobje/
enterprise115/java/applications/webcompadapter.war
Note: Be sure to deploy the WAR files in the order specified earlier in
this section.
3. Repeat the previous step for each WAR file you want to deploy.

After you have deployed adhoc.war, it needs to be integrated with InfoView.
1. Stop your web server.
The default location for this file is C:\Program Files\Business
Objects\BusinessObjects Enterprise
11.5\java\applications.
BusinessObjects Enterprise is installed
5. Save the file.
You can now access Crystal Reports Explorer if you enter http://
servername:portnumber/businessobjects/enterprise115/adhoc in your
browser.

Verifying the Sun Java Application Server configuration

To verify the Sun Java Application Server configuration, make sure that
InfoView and the Central Management Console can be launched in a
browser.
To verify the Sun Java Application Server configuration
type:
http://server01:portnum/businessobjects/enterprise115/desktoplaunch
http://server01:portnum/businessobjects/enterprise115/adminlaunch
where server01 is the name of the server, and portnum is the port
number of the Java web application server.

Importing Objects to
chapter
12 Importing Objects to BusinessObjects Enterprise
Importing information
Importing information
The Import Wizard is a locally installed Windows application that allows you to
import existing user accounts, groups, folders, and reports to your new
BusinessObjects Enterprise system. The Import Wizard runs only on
Windows, but you can use it to import information from a source environment
that is running on Windows or UNIX to a new BusinessObjects Enterprise
system that is running on Windows or on UNIX.
You can import information from any of these products:
• BusinessObjects Enterprise XI or 1.0
• Crystal Enterprise 8.5, 9, or 10
• Business Intelligence Archive Resource (BIAR) files
Note: A BIAR file is a packaged BI Application Resource. It is a portable,
deployable package of the contents of a BI Application that can be used
to easily deploy the entire set of interrelated content in a single simple
action. From a technical perspective, it is a ZIP file containing the
following:
• A Deployment Manifest (BusinessObjects.xml).
• A series of other compressed files for all of the reports, universes,
and other FRS objects contained in the BI Application.
• BusinessObjects 5.x or 6.x
Note: The Import Wizard migrates Application Foundation objects from
your 6.x deployment to performance management 1.0.
For information on migration from BusinessObjects 5.x/6.x, see the
• Text files
Text files can be used to import users, groups and profiles or data source
credentials. See “Using text files with the Import Wizard” on page 238 for
further information.
The functionality provided by the Import Wizard varies, depending upon the
product from which you are importing information. In general, the Import
Wizard imports settings that are specific to each object, rather than global
system settings. For instance, a global “minimum number of characters”
password restriction is not imported. But a user-level “must change password
at next log on” restriction is imported with the user account.
The Import Wizard also has an option that allows you to control what happens
when you import an object that already exists in the destination environment.
This feature, know as incremental import allows you to decide whether or not

Importing Objects to BusinessObjects Enterprise
Importing information from Crystal Enterprise 12
to overwrite object contents and object rights. You may want to use this
feature if the objects have changed or if passwords, profiles or group
memberships have changed since you imported them the first time. See
“Choosing an import scenario” on page 227.
For details, see the section for the product from which you are importing
information:
• “Importing information from Crystal Enterprise” on page 189
• “Importing Application Foundation objects” on page 193
• “Importing information from BusinessObjects 5.x or 6.x” on page 193
For procedural details, see “Using the Import Wizard” on page 212.
BusinessObjects documents
Desktop Intelligence (.rep,.rea,.ret) documents, previously known as
BusinessObjects “full-client” documents, are now supported in
BusinessObjects Enterprise XI R2. To migrate .rep documents you can use
the Import Wizard.
Importing information from Crystal

Enterprise
If you have upgraded from Crystal Enterprise, use the Import Wizard to import
existing user accounts, groups, folders, report objects, and report instances to
BusinessObjects Enterprise XI.
You can also use the Import Wizard to import information from an existing
version XI installation to a new version 1.0. When doing so, you have the
additional option of importing calendars, events, repository objects, and
server groups. Events and server groups can also be imported from a version
8.5 or 9 installation.
When using the Import Wizard, if any of an object’s dependencies are not
imported, the wizard makes appropriate modifications to the object (in most
cases, the dependency is removed). For example, if a user has Full Control
rights on an object, but the user is not imported, the Full Control right for that
user is discarded when the object is imported. In the case of objects brought
across without their owners, the Administrator becomes the new owner of the
objects.

Importing information from Crystal Enterprise
As another, more involved example, User A owns an object and has Full
Control rights while User C has View rights on the same object. If User D runs
the Import Wizard and brings the object across along with User C, but not
User A, the object becomes owned by the Administrator: User A loses Full
Control rights, but User C still has View rights on the object.
Note: Always import users if you want to bring across the associated rights
for an object, even if the user already exists in the destination system. If the
user already exists, the Import Wizard maps all rights for the user on the
source system to the existing user on the destination system. If the user is not
brought across, all rights information for that user is discarded.
Importing objects from Crystal Enterprise

The following sections describe what happens to the objects that are
imported to 1.0. Generally, if the object will not overwrite an object that is
already in the BusinessObjects Enterprise system, then the Import Wizard
imports the object.
Users and groups

The Import Wizard imports users and groups and their hierarchical
relationships. A user or group is imported only if it does not exist already by
name.
If you import a group that already exists in the destination environment, the
list of group members is updated with any additional users who were
members of the group in the source environment. These additional users are
added to BusinessObjects Enterprise if their accounts do not exist already.
User licensing can affect the behavior of the Import Wizard. If the source
environment uses Concurrent licensing, the wizard imports all users as
Concurrent Users. However, if the source environment uses Named User
licensing, the wizard first checks the number of Named User license keys in
the destination environment. If there are enough Named User licenses in the
destination environment, the wizard imports all users as Named Users. If
there are not enough Named User licenses in the destination environment,
the wizard imports all users as Concurrent Users. For more information about
licensing, see the BusinessObjects Enterprise Administrator’s Guide.
Note: BusinessObjects Enterprise XI does not include a New Sign-Up
feature. However, if your Crystal Enterprise source environment includes
users that belong to the New Sign-Up group, the group is migrated to the
destination BusinessObjects Enterprise XI environment.

Importing information from Crystal Enterprise 12
Aliases
If a user in the destination system has an alias that is identical to a user who
is being imported, the destination user keeps all aliases, and the imported
user loses that particular alias.
Windows AD
When importing users that employ Windows Active Directory authentication,
ensure that the administrative credentials are the same on both the source
and destination systems. Active Directory authentication must also be
enabled on the destination system.
LDAP
When importing users that employ LDAP authentication, the Host list and
Base LDAP name need to be the same on both the source and destination
systems. LDAP authentication must also be enabled on the destination
system.
Folders
Folders are imported, whether or not they exist already in the destination
environment. To ensure that existing folders are not overwritten, make sure
you choose the “Automatically rename top-level folders that match top-level
folders on the destination system.” option in the “Please choose an import
scenario” dialog box. When this option is selected, the Import Wizard
appends a number to the end of any duplicated folder names to indicate the
number of copies. For example, if you import a folder called Sales Reports
when a folder called Sales Reports already exists, then the imported folder is
added to BusinessObjects Enterprise with the name Sales Reports(2).
Report objects
The Import Wizard can import Crystal report objects only if they are based on
native drivers, ODBC data sources, OLAP data sources, Crystal Info Views,
or Business Views. You can import the report instances for each report object,
and the scheduling patterns that you have set up in the source environment
are imported automatically.
Supported reports are always imported with their parent folders, whether or
not they exist already in the destination environment. However, so as not to
overwrite existing folders, the Import Wizard appends a number to the end of
any duplicated folder names to indicate the number of copies.
When you import content from one deployment to another, you can ensure
that a particular user account retains ownership of its objects and scheduled
instances by importing the user along with the content. If you don’t import the

Importing information from Crystal Enterprise
user account, the ownership properties of its objects and instances are reset
to your current administrative account. In the SDK, ownership is reflected by
an object’s SI_OWNERID property and by a scheduled instances’s
SI_SUBMITTERID properties.
Rights
When you import folders and reports from one BusinessObjects Enterprise
system to another, the associated object rights are imported for every user or
group who is imported at the same time. If the user or group is not imported at
the same time, the object rights are discarded. For instance, suppose that you
import a report that explicitly grants View On Demand rights to the Everyone
group in the source environment—but you do not import the Everyone group.
In this case, the newly imported report in the destination environment will not
grant the same explicit rights to the Everyone group. Instead, the report
inherits any rights that have been set on its parent folder.
If you do import the appropriate user or group, and it already exists by name
in the destination environment, then the corresponding object rights are
imported and applied to the existing user or group. For instance, modifying
the example above, suppose that you import the report and the Everyone
group. In this case, the Import Wizard imports the object rights along with the
report. So the newly imported report in the destination environment will
explicitly grant the View On Demand right to the Everyone group.
Events and server groups

When you use the Import Wizard to import information from a Crystal
Enterprise 8.5 or later system, you have the additional option to import events
and server groups from the source environment.
When importing server groups, the wizard does not bring across the servers
that belong to that group. You need to manually add servers to the imported
group in the Central Management Console (CMC). For more information
about how to do this, see the BusinessObjects Enterprise Administrator’s
Guide.
Note:
• When importing report objects associated with a server group, if the
server group exists on the destination system, the report objects are
added to the existing group and the source system’s server group is not
imported.
• If you have jobs scheduled or pending on a server or server group that
you are importing, you might notice odd behavior on the destination
system with the individual jobs involved until they run or time out.

Importing information from BusinessObjects 5.x or 6.x 12
Objects that have server group restrictions lose the restrictions if the objects
are imported and the server group is not. For example, if a report is scheduled
to run only under server group A and that server group is not imported, the
report loses that restriction and will run under any server group. You need to
import the server group at the same time as the objects that use it to keep the
relationship between them.
The same logic applies for events: if an object is set up to wait for an event or
to trigger an event, you need to import the event at the same time as the
object. Otherwise, the object is imported without the dependency and no
longer waits for, or triggers, the event.
Note:
• If Event A is being imported from the source system but there is already
an Event A on the destination system, and it is a different type (for
example, a File event instead of a Custom event), the wizard removes
the dependency on Event A from the object when it is imported.
• Events are based on Event Servers and, since servers are not imported,
you need to manually reset the event server and file name information on
the event in the destination system. Once this is set, the event should
work as expected.
Importing information from

BusinessObjects 5.x or 6.x
For information on importing information from BusinessObjects 5.x/6.x, see
the BusinessObjects 5.x to XI Release 2 Migration Guide or the
If you have upgraded from BusinessObjects 5.x/ 6.x, you can use the Import
Wizard to import existing user accounts, groups, categories, Desktop
Intelligence, Web Intelligence documents, universes, connection objects,
universe restriction sets, and third-party documents to BusinessObjects
Enterprise XI Release 2.
Importing Application Foundation objects

The Import Wizard migrates Application Foundation objects from your 6.x
deployment to performance management 1.0. One of two things happen to
objects stored in the Application Foundation repository and locally on the
Application Foundation server:
• The objects are migrated to the performance management 1.0 repository.

Importing information from BusinessObjects 5.x or 6.x
The Import Wizard writes new tables and columns to the Application
Foundation repository during the upgrade. Business Objects strongly
recommends that you copy the source repository before migrating, and
that you run the Import Wizard on the copy of the source. This enables
you to keep your source environment intact during and after migration.
See the BusinessObjects 5.x to XI Release 2 Migration Guide or the
BusinessObjects 6.x to XI Release 2 Migration Guide for more
information on migrating the application foundation repository.
• The objects are imported and published by the Import Wizard to the 1.0
Central Management Server (CMS).
As in previous versions, performance management relies on its own
dedicated repository as well as the Business Objects repository previously,
now the CMS. When you migrate Application Foundation 6.1 or 6.5 to
BusinessObjects Enterprise XI, you must run the Import Wizard to import
certain objects to the CMS. You must also upgrade the performance
management repository in the Import Wizard if you are migrating from version
6.x.
The Import Wizard publishes the following objects from Application
Foundation 6.1 and 6.5 as InfoObjects to the BusinessObjects Enterprise XI
CMS:
• Applications, menus and submenus.
• Corporate and personal dashboards.
• Corporate and personal analytics.
• Certain agnostic documents, including *.gif, *.bmp, *.png, *.jpg files used
in dashboards, Strategy Maps or Metric Trees, as well as SVG, *.xml and
*.swf, and *.csv used in custom calendar definitions.
• Schedules and events.
• Links in dashboards to analytics or corporate documents.
• Universes used in metric definitions or referenced by migrated
documents (and the corresponding connections).
For details on migrating Application Foundation, refer to the section called
“Understanding Application Foundation object migration” in the
BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects
6.x to XI Release 2 Migration Guide.
Limitations on importing objects

Legacy Web Connect documents can be opened in 1.0, but not edited or
refreshed.

When VBA macros from BusinessObjects 5.x/6.x are updated in 1.0, they can
no longer be used in previous versions.
1.0 can open and use LOV (list of values), UDO (user-defined objects), and
.rea files from BusinessObjects 5.x/6.x. The Import Wizard does not import
UDOs because UDOs are not usually stored in a repository.
Before importing from Application Foundation

Before running the Import Wizard, check the integrity of the source
environment. Business Objects recommends that you do the following:
• Copy the source Application Foundation repository before migrating, and
run the Import Wizard on the copy of the source.
• Run the Scan and Repair utility on the BusinessObjects repository.
• Check the integrity of universes referenced by Application Foundation
objects (in Setup > System Setup > Tools).
• Check the version and integrity of the source Application Foundation
repository.
• Check the location of the Application Foundation storage folder.
• Check the location of the inbox and personal folders.
• Ensure that your database connections are valid.
• Ensure that the appropriate middleware is installed.
The Import Wizard assumes that the source environment is clean. The Import
Wizard cannot resolve problems present in the source environment during
migration.
For example, if there are inconsistencies between universe IDs in the
Application Foundation repository (in the ci_source table) and the
BusinessObjects repository, the source ID will not be correctly mapped to the
CUID (the cluster unique ID that is assigned to the universe) assigned by the
Import Wizard during import. Double-check that universes referenced in the
ci_source table have the same id in the BusinessObjects repository before
running the Import Wizard. For information on checking the integrity of the
source environment, see Best Practices for Migrating to BusinessObjects
Performance Management XI R2.
For details on migrating Application Foundation, refer to the section called
“Understanding Application Foundation object migration” in the

Before importing from BusinessObjects 5.x/6.x

Before you use the Import Wizard to import data into the new 1.0 system, you
need to check that certain prerequisites are met.
• “Appropriate rights” on page 196
• “Data sources” on page 196
• “Folder mapping” on page 196
• “UNIX servers” on page 197
• “Locally stored objects” on page 197
• “Updating platforms and versions if required” on page 197
Appropriate rights
To use the Import Wizard, you must have the following rights:
• In BusinessObjects 5.x/6.x, you must have a General Supervisor profile
in the repository.
• In 1.0, you must belong to the Administrator group in the CMS.
• To import any resource into the CMS, you must have the rights needed to
add objects to the destination folder to which the resource is assigned.
Data sources
Create data sources on each destination server machine for every repository
domain in the source deployment. The name and configuration details for the
data sources must match the data sources in the source deployment.
Certain databases that can host a version 6.x repository are not supported for
an 1.0 repository. For the latest information, see the list of supported
platforms at:
http://support.businessobjects.com/supported_platforms_xi_release2/
Folder mapping
On the Import Wizard machine, map the drives to the source environment
directories containing the deployment’s .key files, personal documents and
categories, and users’ Inboxes:
• $INSTALLDIR\locData for access to 5.1.x .key files
• $WISTORAGEDIR\user if you are importing personal documents and
categories
• $WISTORAGEDIR\mail if you are importing the read content of users’
Inbox folders

• $INSTALLDIR\nodes\<nodename>\<clustername>\locdata for access to
6.x .key files
• $INSTALLDIR\nodes\<nodename>\<clustername>\storage\user if you
are importing 6.x personal documents and categories
• $INSTALLDIR\nodes\<nodename>\<clustername>\storage\mail if you
are importing the read content of 6.x users’ Inbox folders
UNIX servers
If your 1.0 server runs on UNIX, you need to install the Import Wizard on a
separate Windows machine. You will also need to use a third-party utility,
such as SAMBA or FTP, to map UNIX drives to Windows.
For example, see the Microsoft documentation on “Interoperability with UNIX/
Planning and Installing Services for UNIX on Windows 2000 Professional.” As
of this writing, the URL is:
http://www.microsoft.com/resources/documentation/Windows/2000/server/
reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/
server/reskit/en-us/prork/prci_unx_houn.asp
Import ing Inbox and personal files from one UNIX environment to
another
To import Inbox and personal files from one UNIX environment to another,
you must have network access rights and copy the files to the network. On
the Import Wizard machine, map drives to the local folders containing the
unzipped source environment directories.
Locally stored objects

Objects that you are planning to import to the destination environment using
the Import Wizard must reside in the BusinessObjects 5.x/6.x repository.
If objects are stored locally on users’ computers, you must make sure the
users export the objects to the repository before you begin the import.
Tip: Create a specific category to store local content.
Updating platforms and versions if required

For performance or support reasons, you may be required to update various
components (operating system, web server, application server, web
browsers, databases, etc.) in your Business Intelligence environment either to
more recent versions, or to different platforms altogether.
Business Objects recommends reading the official list of supported platforms
carefully for the most up-to-date support information. You can find it at:

http://support.businessobjects.com/supported_platforms_xi_release2/
Migrating to a different repository database

The databases supported as repository databases in BusinessObjects 5.x/6.x
may not be supported as CMS databases in version 1.0.
Nonetheless, the Import Wizard can import objects from any supported type
of source repository database seamlessly into any supported CMS repository
database.
Migrating query databases

All data access is kept from BusinessObjects 5.x/6.x. Connection Server is an
integral part of BusinessObjects Enterprise 1.0, and all the databases it
supported in BusinessObjects 5.x/6.x continue to be supported in the new
environment. Check the list of supported platforms at http://
support.businessobjects.com/supported_platforms_xi_release2/, however,
for the specifically supported driver versions.
All connectivities supported for BusinessObjects 5.x/6.x are not necessarily
supported for version 1.0. Check the list of supported platforms at http://
support.businessobjects.com/supported_platforms_xi_release2/ for detailed
information.
If you do not migrate data in unsupported database platforms to a supported
platform, universes based on them will not work in the destination
environment.
ONAMES on Oracle
The Import Wizard does not support Oracle systems that use ONAMES
naming servers. You must use TNSNAMES instead.
Stopping and starting servers

• Stop all servers in the source deployment.
• Start the following servers in the 1.0 deployment:
• Central Management Server
• Input File Repository Server and Output File Repository Server
What kinds of objects can be imported?

The table below summarizes the types of objects the Import Wizard can
migrate, as well as those it cannot.

Import Wizard can migrate: Import Wizard cannot migrate:
Users and user groups Individual LDAP users (inbox and
personal)
Inbox, personal, and corporate BusinessQuery
documents
Third party documents (such as .pdf, Web Intelligence OLAP
.ppt, .doc)
Universes Custom applications and interfaces
created using the SDK
Connections InfoView personal settings
Stored procedures BusinessObjects Auditor
Broadcast Agent Scheduler tasks Broadcast Agent Scheduler tasks
that are supported in XI R2 that are not supported in XI R2
Personal and corporate categories Broadcast Agent Publisher tasks
Application Foundation 6.x objects BusinessObjects Services
Administrator settings
Third party documents used by Administration Console settings and
Application Foundation objects (such some user settings (such as
as .svg, .xml, .gif) timestamps
Note: The Import Wizard can import objects only if they are located in the
repository or in personal and inbox folders.
Importing objects from BusinessObjects 5.x/6.x

The following sections describe what happens to objects that are imported
from BusinessObjects 5.x/6.x into 1.0.
By default, the Import Wizard does not overwrite objects with the same name
that are already stored in the 1.0 database.
In general, the Wizard imports settings that are specific to each object, rather
than global system settings.
The Import Wizard can migrate most document types from BusinessObjects
5.x and 6.x to XI R2. This section provides information on the following
document-migration related topics:
• “Inbox, personal and corporate documents” on page 200
• “BusinessObjects documents” on page 201
• “Web Intelligence documents” on page 202
• “Third-party documents” on page 203

• “When documents contain no locale” on page 204

For details, see the BusinessObjects 5.x to XI Release 2 Migration Guide or
the BusinessObjects 6.x to XI Release 2 Migration Guide.
Inbox, personal and corporate documents
You can import these types of documents:
• “Inbox documents” on page 200
• “Personal documents” on page 200
• “Corporate documents” on page 201
Inbox documents
In BusinessObjects 5.x/6.x, Inbox documents are stored in the repository until
recipients have read them. When a document has been read by a given user,
it is copied to the user’s Inbox folder . See “Folder mapping” on page 196 for
information on the location of these documents in each version. After all
recipients have read them, the documents are removed from the repository.
The Import Wizard will import both read and unread Inbox documents to 1.0;
therefore, you will have to specify the location of the mail folder.
The documents are migrated to 1.0 users’ Inbox folders in the CMS.
Documents inherit the rights of the 5.x/6.x Inbox folder.
If the Inbox contains duplicate documents, they are also migrated to the FRS.
To import 5.x/6.x Inbox documents that reside on a UNIX machine, you need
to map a drive from the Windows server running the Import Wizard to the
directories on the UNIX machine containing the documents.
Personal documents
In BusinessObjects5.x/6.x personal documents are imported to the user’s
Favorites folder in the destination CMS. Documents inherit the rights of this
folder. See “Folder mapping” on page 196 for information on the location of
these documents in each version. The document owner and the Business
Objects Administrator have access to these documents. Personal or
Corporate categories that referred to these documents in 5.x/6.x continue to
refer to them in 1.0.
To import 5.x/6.x personal documents that reside on a UNIX machine, you
need to map a drive from the Windows server running the Import Wizard to
the directories on the UNIX machine containing the documents.

Corporate documents
In BusinessObjects 5.x/6.x corporate storage is mapped to the Public Folders
folder in the 1.0 CMS repository. Corporate documents are saved in this
folder after the import.
Each domain is migrated as a folder in the Public folder of the CMS
repository.
If your 5.x/6.x repository was a distributed one, all the domains are imported
into a single place.
BusinessObjects documents
When you import a 5.x/6.x BusinessObjects (.rep) document to 1.0, the
following occur:
• The universe ID pointer is updated so that it references a universe in the
CMS.
• An InfoObject is created in the CMS for this document and for the saving
of this document.
• Properties are updated and displayed in the CMC.
BusinessObjects template (.ret) documents do not contain cubes or a
connection to a universe; therefore, all that occurs is:
• The locale of the document is updated.
• An InfoObject is created in the CMS.
Converting BusinessObjects documents

To convert 5.x/6.x .rep documents to .wid format, you can use the Report
Conversion Tool, delivered with the 1.0 suite.
Note: .wid documents for which there is no universe (so-called orphan
documents) can be imported into 1.0.
BusinessObjects document rights

If you migrate security during the import of BusinessObjects documents,
BusinessObjects 5.x/6.x security commands are converted to 1.0 application-
level and document-level rights. Some commands have been eliminated and
others renamed.
Note: In XI R2, the Administrators group has Full-Control access to
documents and the Everyone group has View access.
For a detailed summary of how BusinessObjects security commands are
migrated, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the

Limitations
Keep in mind the following limitations when you import BusinessObjects
documents:
• 1.0 can read BusinessObjects 5.x/6.x .rep documents, but after you save
these documents in 1.0, they can’t be read by BusinessObjects 5.x/6.x of
the software.
• BusinessObjects 5.x/6.x cannot open 1.0 Desktop Intelligence
documents.
• OLAP data providers are not supported in 1.0.
BusinessObjects 5.x/6.x documents based on an OLAP data provider are
view-only in 1.0.
• In XI R2, there is no document password protection on the server side.
• 1.0 Desktop Intelligence cannot access a BusinessObjects 5.x/6.x
repository.
BusinessObjects SDK
The platform-related portion of the BusinessObjects SDK has evolved, which
means that code developed for 5.1/6.x will require updates for platform
interactions (authentication, send document, receive document).
Send to Users and Send to Broadcast Agent Server are not available in 1.0.
Instead, you need to use the Platform COM SDK.
The server-side report engine is not multi-document. This means that add-ins
will not be loaded on the server. For example, for a document based on a
custom data provider (DPVBAInterface) implemented in an add-in, refresh will
fail.
Calculator changes
1.0 uses a different report engine than BusinessObjects 5.x/6.x; therefore,
there are differences in the way the calculator is handled and there may be
issues with BusinessObjects documents after they are imported to 1.0.
See the BusinessObjects 5.x to XI Release 2 Migration Guide or the
BusinessObjects 6.x to XI Release 2 Migration Guide for more information.
Web Intelligence documents

The Import Wizard can import Web Intelligence documents. It can convert
.wqy (Web Intelligence 2.x) documents to .wid format before importing them.
The .wid documents can then be used in 1.0.
When you import a Web Intelligence document, the following occur:
• Universe ID is updated so that it references a universe in the CMS.

• IDs in the Web Intelligence documents, universes, and connections are
converted to cluster unique identifiers (CUIDs), which will distinguish
these objects from objects subsequently imported from the source
environment.
• An InfoObject is created in the CMS for this document and for the saving
of this document.
• Properties are updated.
• If a .wqy and .wid document have the same name, they are both
imported, but the .wqy document is renamed to <name of
document>_WQY.wid.
Web Intelligence rights

If you choose to migrate security, all security commands in BusinessObjects
5.x/6.x Web Intelligence documents are migrated to 1.0.
A number of rights are new in Web Intelligence 1.0. For example:
• Edit SQL
• Allow user to merge dimension for synchronization
• Interactive Editing rights
The BusinessObjects 5.x/6.x security command Allow use of the
WebIntelligence HTML Report Panel has been renamed to Enable Query -
HTML. After it is migrated, set it to Denied.
Limitations
There may be an issue with the migration of the following .wqy features to
.wid:
• Autofit/Column width/Wrap text
There may be a difference in the column widths.
• Locale
In some Web Intelligence 2.x versions, locale was not stored in the .wqy file. If
no locale is found in the .wqy file, the Import Wizard prompts you for a locale.
Third-party documents
BusinessObjects 6.x supports third-party (also known as “agnostic”)
documents. The Import Wizard imports these documents into 1.0 if the format
is supported. Formats supported in 1.0 include Adobe Acrobat PDF; Microsoft
Power Point, Word, RTF, and Excel; and *.txt documents.
For the most up-to-date list of supported formats for third-party documents,
see the list of supported platforms.

When documents contain no locale

In the 5.x/6.x repository, it is possible that some .wqy and .rep (as well as
associated .rea and .ret files) documents do not store their locale. To set the
locales in these documents when they are saved in the CMS after their
conversion into 1.0 format, the Import Wizard asks for the following default
locales:
• The document’s locale
• The locale of the machine used to create the document
Once you select these locales, they are stored in the document itself when it
is imported to the CMS. The default locales apply to all documents in the
current import without locales. Applying wrong locales to a document may
cause difficulties; for example, the date or currency may be incorrectly
displayed.
If the repository contains documents with different locales, it is best practice to
run the import step by step (one step for each document language) in order to
avoid, for example, setting a default English locale for a Japanese document.
Importing Broadcast Agent jobs

This section provides information on migrating Broadcast Agent jobs. It
covers the following topics:
• “About migrating Broadcast Agent jobs” on page 204
• “Task scheduling options” on page 205
• “Associated universes” on page 205
About migrating Broadcast Agent jobs

A Broadcast Agent job can be migrated from BusinessObjects 5.x/6.x to 1.0
only if the job is supported in 1.0. If a job contains non-supported elements or
features, you must drop the feature or recreate it in the 5.x/6.x system so that
it is consistent with the 1.0 platform. You can also recreate non-migrated jobs
in 1.0 using the CMC’s scheduling features.
In 1.0, the first action for scheduled documents is always a refresh. Therefore,
a job can be imported from 5.x/6.x only if its first action is a refresh.
A job cannot be imported if it has any of the following attributes:
• Multiple outputs
• Conditional processing
• Custom macros
Note: You can have embedded VBA macros (those that include calls to
the platform, such as Login or Logout, will need to be updated).

• Report bursting (“refresh with the profile of each recipient”)
• Saved in RTF, HTML, or TXT format
Task scheduling options

The following 5.x/6.x task scheduling options (in either BusinessObjects or
Web Intelligence) are not supported in 1.0:
Daily
• Week periodicity
Weekly
• Week periodicity
Monthly interval
• Business day
• Weekend day
• Month periodicity
User-defined
• Weekday
• Business day
• Weekend day
Note: The migrated document may be assigned a different periodicity in 1.0.
File Watcher
Although the Import Wizard will transfer File Watcher details to the Event
Server, deletes set in Broadcast Agent 6.x may not function in XI R2. You can
set these deletes in Broadcast Agent 6.x:
• Delete the file each time the task starts.
• Delete the file only if the task succeeded.
• Delete the file after execution of the task.
Associated universes
When you import scheduled documents from 5.x/6.x, you must also import
the universes used by these documents. As the universes are not selected
automatically during the import, you must manually select the ones you need
for Broadcast Agent jobs if you are not importing all your universes.
How scheduled documents are migrated

The way scheduled documents are migrated varies, based on whether the job
schedules a document in Corporate or Inbox.

Corporate
If the document is not already imported in the domain or is not imported at the
same time to the CMS, then the job is not migrated. Verification is performed
by comparing the CUIDs.
Otherwise, the Import Wizard creates an instance of this document using the
schedule parameters of the original job.
• No ACL is set at this instance level. The instance inherits the ACL set at
the document level.
• If the document has been scheduled several times in Corporate, then the
same number of instances are created.
Inbox
If the sender of the original schedule already exists in the CMS or if the
sender is migrated at the same time, then the following occurs:
• The Import Wizard imports the scheduled document into the Favorites
folder of this user in the CMS. A folder named Scheduled migrated
documents/<BCA Name> is created under Favorites.
• The document is renamed to <doc_name>_<docID>.<ext> .
• An instance is created for the document using the schedule parameters
of the original job.
the folder level.
• The recipients (user or group) of the schedules are the recipients of the
original schedule, if they already exist in the CMS or if they are migrated
at the same time (name is verified).
If the sender of the original schedule does not exist in the CMS, the following
occurs:
• The Import Wizard imports the scheduled document into Public Folders/
Scheduled migrated documents/<BCA name>.
• The document is renamed to <doc_name>_<docID>.<ext> .
• An instance is created for this document using the schedule parameters
of the original job.
the folder level.
• The recipients (user or group) of the schedules are the recipients of the
original schedule, if they already exist in the CMS or if they are migrated
at the same time (name is verified).

Migrating documents with identical names
Sometimes, when a document with an associated job is migrated, a
document with the same name already exists in the destination folder. The
system manages these documents differently, depending on whether you are
migrating in Merge mode or Update mode.
Merge mode
If a document with the same name as the 6.x document exists in the
destination folder, a new folder is created. For example, for the 5.x/6.x
document Annual.rep being migrated into the folder named Agent, a new
folder named Agent(2) is created, and Annual.rep is reposted within Agent(2).
The document name and instance name do not change.
Update mode
The document ID is checked in the CMS. If an older document exists, it is
updated with the properties of the newly migrated document. The instances
are also replaced by the newly migrated schedules. The schedules and the
instances are identified by the ID received in the Scheduled Jobs table of the
repository.
Universes and universe connections

This section contains information on using the Import Wizard to import
universes and universe connections. It covers the following topics:
• “Importing universes and connections” on page 207
• “Options for importing universes and connections” on page 208
• “Configuring connections” on page 209
Importing universes and connections

The Import Wizard will import universes from a 5.x/6.x deployment into a 1.0
deployment. During this process, the relationship between universes,
connections, and Web Intelligence documents is maintained. The IDs in the
web intelligence documents, universes, and connections will be converted to
cluster unique identifier (CUIDS) and the relationship preserved.
When you import BusinessObjects Enterprise 5.x/6.x universes, the
associated connections are imported automatically. They are converted into
connection objects.
• The Import Wizard imports any associated connection objects.
• The connection is saved in the FRS and an InfoObject is created in the
CMS.
• The universe and its linked documents are copied into the FRS.

• Universe overloads defined in 5.1/6.x, if migrated, are mapped to access

restrictions in 1.0.
• ACEs are created to migrate universe-related security commands.
• The locale is preserved.This is the process when a universe is imported.
Options for importing universes and connections

The Import Wizard has three modes for importing universes:
• Import all universes and all connection objects
Note: This option does not permit you to select individual universes or
connections.
• Import all universes and only connection objects used by these universes
• Import the universes and connections that the selected Web Intelligence
and BusinessObjects documents use directly
Note: This option enables you to select additional universes to import,
even if they are not used by any document.
When you select a Web Intelligence or BusinessObjects document to import,
the Import Wizard automatically selects the associated universes for import. It
does not do this, however, for universes used by scheduled documents
(Broadcast Agent jobs). This means that if you are not importing all your
universes, you must manually select the ones you need for Broadcast Agent
jobs.
Note: The Import Wizard also imports any universes with the same name
that exist in other domains.
BusinessObjects documents may have been created outside the repository,
using a “short name”; that is, a reference to a universe stored on a local
machine. If the universe has a short name, its linked documents may not be
imported if more than one universe is found in the CMS with the same short
name.
Universe domains are converted into subfolders under the Universe folder.
Each universe folder is named after the corresponding BusinessObjects 5.x/
6.x universe domain. When you import a universe from a domain, it is placed
in the corresponding domain folder.
If the universe is a derived universe, then all relevant core universes and their
connections are also imported.
Note: Designer 5.x/6.x cannot open universes created with Designer 1.0,
due to a file format change.

Configuring connections
When you import BusinessObjects 5.x/6.x universes, the associated
connections are imported automatically. They are converted into connection
objects.
Make sure that the Import Wizard can access the 5.x/6.x database the same
way that BusinessObjects 5.x/6.x accesses it. You may need to install
database drivers or configure connection settings on the machine.
For example, if you import SQL Server connection objects from a 5.x/6.x
source environment, you must configure the connections on the destination
machine via the ODBC Data Source Administrator settings in the Windows
Start Menu Control Panel before you import the connection objects. You must
use the same name and settings as the connection used on the source
machine when you created the domain key.
BOUSER/BOPASS
In BusinessObjects 5.x/6.x, users could use @Variable('BOUSER') and
@Variable('BOPASS') in the connection information for the universe. The
variables were replaced at runtime with the user’s enterprise username and
password, and used to log on to the database.
For security reasons, 1.0 does not permit the retrieval of users’ passwords.
Therefore, universe connections that previously used the BOUSER and
BOPASS variables associated with the BusinessObjects user name and
password must now use database credentials (DBUSER and DBPASS).
Those database credentials can be populated by the Import Wizard and later
edited in the CMC, on the Properties tab for each user account.
When migrating, Import Wizard automatically does the following:
• Replaces BOUSER and BOPASS with DBUSER and DBPASS in
universes.
• Proposes automatically populating these variables for users to migrate.
You can, however, re-synchronize if users change their passwords.
Synchronizing enterprise and database credentials
There are three ways to synchronize enterprise and database credentials in
the 1.0 system:
• Choose the Import Wizard option that batch imports user names and
passwords from BusinessObjects 5.x/6.x to auto-populate database
credentials in 1.0.
• Run a batch upload of a user’s file.

User names and passwords are loaded from a file, stored and used as
database credentials.
• Create a custom application using Enterprise SDK to set DBUSER and
DBPASS information.
Importing access restrictions

In a BusinessObjects5.x/6.x system, access restrictions (that is, object
restrictions, table mapping, and row restrictions) are defined with the
Supervisor application and associated with users and groups. A user who
belongs to multiple groups is said to have multiple user instances (one
instance per group).
Note: Universe overloads in BusinessObjects 5.x/6.x are called access
restrictions in 1.0. They are managed in Designer.
The Import Wizard enables you to import all access restrictions that are
associated with the imported universes for any of the selected users and
groups being imported. If no principal users or groups are selected for import,
no access restrictions are imported and none are created.
The imported access restrictions are converted into objects. They remain
connected to the universes to which they were connected in the source
environment. The Import Wizard may create additional access restrictions in
the destination environment in order to preserve the restrictions for all
imported users.
Connections for access restrictions are not migrated automatically. You must
manually migrate these connections.
Access restrictions are migrated using both object names and object IDs to
identify universe components.
Access restriction aggregation

In both BusinessObjects 5.x/6.x and 1.0, there are two types of access
restrictions: exclusive and non-exclusive. Row restrictions are combined
using the AND operator, while object restrictions and compatible table
mappings are aggregated.
Exclusive access restrictions require a different mechanism. The Import
Wizard deduces a global ordering of groups for each universe, based on the
access restrictions prior to migration. For a given user, the Wizard considers
the set of parent groups of that user and, in that set, the group with the
highest priority determines which restriction set gets applied to that particular
user.

Access restriction collapsing
Sometimes the global group ordering that is deduced during migration cannot
account for all of the individual user priority settings in BusinessObjects 5.x/
6.x. In this case, access restrictions will be collapsed, meaning that the
effective BusinessObjects 5.x/6.x access restriction will be copied onto the
user, which always has highest priority. This means that there might be more
access restrictions in the destination than in the source environment
Importing stored procedures

In BusinessObjects 5.x/6.x, you can allocate stored procedures to users; in
1.0, Use Connection for Stored Procedures is introduced as a new right for
the connection object. During the import, for all stored procedures accessible
to a user, an ACE (Access Control Entry) is created for the user, with a
corresponding connection. Stored Procedures Access is enabled and the
ACE is set to Granted.
Importing folders, domains, and categories

You select the domains and documents you want to import into 1.0. When you
select a document, the document's domain is also imported. Documents and
universes cannot be imported without importing the domain.
BusinessObjects 5.x/6.x document and universe domains are saved as sub-
folders in the Public Folder of the CMS of 1.0. Objects corresponding to the
universes and documents contained in the domains are imported to these
folders.
If you have chosen to import security, access rights are preserved. User and
group access to the folders are equivalent to the rights they had on the
BusinessObjects 5.x/6.x domains.
1.0 preserves the hierarchy of subcategories. Corporate (or administrative)
categories are imported as categories under the Categories folder. For each
imported user, selected personal categories are imported to a new subfolder
(named after the user) under the Personal Categories folder.
You can select individual Corporate categories and import Web Intelligence
documents grouped by Corporate category. Personal categories, however,
can be imported only as part of the batch import.

Using the Import Wizard
Users and groups

All existing BusinessObjects 5.x/6.x users and groups can be migrated to
BusinessObjects Enterprise XI. Users are imported into the BusinessObjects
Enterprise repository. For each BusinessObjects 5.x/6.x user,
BusinessObjects Enterprise XI creates a user folder, a personal category, and
an Inbox folder.
User profiles from BusinessObjects 6.x are mapped to default groups in
BusinessObjects Enterprise XI as follows:
BusinessObjects 5.x/6.x user BusinessObjects Enterprise XI

profile default group
All user profiles Added to the Everyone group.
General Supervisor Added to the Administrators group.
Supervisor Granted appropriate rights on all
imported objects, but not added to
the Administrators group.
User/Versatile Added to the Everyone group.
Whenever possible, BusinessObjects 6.x security settings are preserved in
BusinessObjects Enterprise XI. If a BusinessObjects 6.x right does not map
exactly to a BusinessObjects Enterprise XI right, the right will not be granted
to the user.
Note:
• The Import Wizard migrates external user groups (LDAP or Windows AD
user groups, for example).

The Import Wizard provides a series of screens that guide you through the
process of importing user accounts, groups, folders, and reports. The screens
that appear depend on the source environment and the types of information
that you choose to import.
When you import information, you first connect to the Central Management
Server (CMS) of your existing installation (the source environment) and
specify the CMS of your new BusinessObjects Enterprise system (the
destination environment). You then select the information that you want to
import, and the Import Wizard copies the requested information from the
source to the destination.

Using the Import Wizard 12
You can choose to merge the contents of the source repository into the
destination repository, or you can update the destination with the contents of
the source CMS.
Before starting this procedure, ensure that you have the Administrator
account credentials for both the source and the destination environment.
The overall process is divided into the following procedures:
• “Specifying the source environment” on page 213
• “Specifying the destination environment” on page 220
• “Selecting the type of objects to import” on page 222
• “Selecting specific objects to import” on page 229
• “Finalizing the import” on page 237
Note:
• If you are migrating from BusinessObjects 5.x or 6.x, see the
BusinessObjects 6.x to XI Release 2 Migration Guide for detailed Import
Wizard instructions.
• The process of importing users, groups and profiles from a text files is a
less complex task. Both the format for the text file and the procedure are
outlined in “Using text files with the Import Wizard” on page 238.
Specifying the source environment

These procedures show how to specify a source environment on the initial
screen of the Import Wizard.
• “Specifying a BusinessObjects 5.x source environment” on page 214
• “Specifying a BusinessObjects 6.x source environment” on page 214
Note: This includes Application Foundation.
• “Specifying a Crystal Enterprise 8.5 source environment” on page 217
• “Specifying a Crystal Enterprise 9 source environment” on page 217
• “Specifying a Crystal Enterprise 10 source environment” on page 218
• “Specifying a BusinessObjects Enterprise XI or XI R2 source
environment” on page 218
• “Specifying a BIAR file or Text file as your source environment” on
page 219

Specifying a BusinessObjects 5.x source environment

To specify a BusinessObjects 5.x source environment
1. Start the Import Wizard. From the Start menu, select Programs >
BusinessObjects > BusinessObjects Enterprise > Import Wizard.
The Import Wizard dialog box appears.
2. Click Next.
The Source Environment dialog box appears.
3. Choose BusinessObjects 5.x from the Source list.
Note: If your source environment is on UNIX server, you should map the
UNIX server to your local machine before you start the Import Wizard.
4. Type the User Name and Password that provides you with
administrative rights to the source environment.
Note: You must have a General Supervisor profile in the repository.
5. In the Domain Key File field, type or browse for the path to the .key file
you created for the repository in your source environment.
6. Click Next.
The Destination Environment dialog box appears. Proceed to “Specifying
the destination environment” on page 220.
Specifying a BusinessObjects 6.x source environment

To specify a BusinessObjects 6.x source environment
2. Click Next.
3. Choose BusinessObjects 6.x from the Source list.
4. Type the name of the BusinessObjects repository security domain and
the User Name and Password that provides you with administrative
rights to the source environment.
Note: You must have a General Supervisor profile in the repository.
5. If you want to import Application Foundation objects proceed to
“Specifying the Application Foundation source information” on page 215.
6. If you do not want to import Application Foundation objects, make sure
the Import Application Foundation Contents check box is not
selected, and then click Next.

7. The Destination Environment dialog box appears. Proceed to “Specifying
Specifying the Application Foundation source information
This procedure assumes you have completed the step “Specifying a
BusinessObjects 6.x source environment” on page 214.
To specifying the Application Foundation source information
1. Select the Import Application Foundation contents check box on the
Source Environment dialog box, and then click Next.
Note: You can import Application Foundation objects only if you selected
BusinessObjects 6.x (or XI) in the Source list. If you import Application
Foundation objects, the Import Wizard displays additional screens and
options.
The Import Wizard verifies the following:
• The connection to the repository.
• The credential.
• The validity of the General Supervisor login.
• The repository version.
2. In the Dashboard files section of the Application Foundation source
screen, browse to the location of the Application Foundation storage
folder.
By default, it is $INSTALLDIR/Application Foundation/server/conf.

3. In the Application Foundation source repository section, indicate the

repository’s details using one of the following methods:
• Check the Use conf file option.
This option allows you to specify the location of the AF config file that
contains the repository database information rather than entering it
manually.
Note: If you check this option, the option to upgrade the AF
repository in this Import Wizard session will be grayed out. You can
only use this option to point to the source repository connection if you
are not planning to upgrade the repository using this connection. It is
highly recommended that you upgrade a copy of the source
repository, and that you point the connection to the copy when you
upgrade the repository.
• Manually enter the following information:
• The name of the source repository.
• The database engine.
• The network layer of the source repository.
• The user name and password to access the database.
Note: The user name and password you type must belong to an
Administrator profile. It is highly recommended that you upgrade a
copy of the source repository, and that you point the connection to
the copy when you upgrade the repository.
4. Click Next.
The Application Foundation Repository Update dialog box appears.
5. Select one of the following options:
• Yes to update the repository in the Import Wizard
• No to skip the repository update and migrate the repository later
Note: If you want to perform the migration in several steps, the
Application Foundation repository must be updated at the end of the
migration process. You can only update the repository once. If you
are migrating rules and schedules, you must migrate them in the
same Import Wizard session as the repository update. If you choose
not to upgrade the repository, you cannot import rules and
schedules. In addition, if you choose not to upgrade the repository,
your repository connections will not be active on the migrated
environment.
6. Click Next.

• If you chose not to upgrade the repository, a dialog box listing the
objects you can import appears. Click Next to continue.
• If you chose to upgrade the repository, an informational page
appears. You must acknowledge that you have read the information
by checking the “I understand. I want to continue.” box to proceed
with the repository upgrade.
7. Click Next.
Specifying a Crystal Enterprise 8.5 source environment

To specify a Crystal Enterprise 8.5 source environment
2. Click Next.
3. Choose Crystal Enterprise 8.5 from the Source list.
4. Enter either the name of the source CMS in the CMS Name field or the
name of the source APS in the APS Name field.
5. Type the User Name and Password that provide you with administrative
6. Click Next.
Specifying a Crystal Enterprise 9 source environment

To specify a Crystal Enterprise 9 source environment
2. Click Next.
The Source environment dialog box appears.
3. Choose Crystal Enterprise 9 from the Source list.

6. Click Next.
The Destination environment dialog box appears. Proceed to “Specifying
Specifying a Crystal Enterprise 10 source environment

To specify a Crystal Enterprise 10 source environment
2. Click Next.
3. Choose Crystal Enterprise 10 from the Source list.
6. Click Next.
Specifying a BusinessObjects Enterprise XI or XI R2 source environment

To set the source environment
2. Click Next.
3. Choose BusinessObjects Enterprise XI or BusinessObjects Enterprise XI
R2 from the Source list.

6. Click Next.
Specifying a BIAR file or Text file as your source environment

This section explains how to import from a Text or BIAR file. For details, on
how to structure your text files so the Import Wizard can import them, see
“Using text files with the Import Wizard” on page 238.
To specifying a BIAR file or Text file as your source
2. Click Next.
3. Choose either Business Intellignece Archive Resource (BIAR) File or
Text file from the Source list.

4. Enter the location of the file in the BIAR file or Import file field, and then
click Next.

Specifying the destination environment

This procedure shows how to specify a destination environment.
To set the destination environment
1. Choose the destination environment in which to export.
• If you want to export to a CMS
a. Type the name of the destination environment’s Central
Management Server in the CMS Name field.
b. Type the User Name and Password of an Enterprise account
that provides you with administrative rights to the
BusinessObjects Enterprise system.

• If you want to export to a BIAR file, specify the name and location
where you want the BIAR file to be stored.
Note: This option only applies if your source environment is 1.0.
2. Click Next.
The Select Objects to import dialog box appears.

Selecting the type of objects to import

In this stage of the import process, you select the types of objects you want to
import and select options related to their import. At a later stage, you will
select the objects themselves. You may select BusinessObjects Enterprise XI
InfoObjects, including the following performance management InfoObjects:
• universes and documents referenced by analytics you are importing
• analytics (*.afd)
• rules and schedules (rules remain in the performance management
repository. Only schedules and named events that trigger rules are
imported here)
• named events
• dashboards (corporate and personal)
The options available on the Choose object to import dialog box depend on
the version of the source environment. By default, all available objects are
checked for import. Events and server groups can be imported from Crystal
Enterprise 8.5 or later. Repository objects and calendars can be imported
from Crystal Enterprise 10. Universes, categories, Desktop Intelligence and
Web Intelligence documents can be imported from BusinessObjects 6.x. All
objects except Desktop Intelligence documents can be imported from
BusinessObjects Enterprise XI and 1.0.
If you have not already started the Import Wizard, see “Specifying the source
environment” on page 213 and “Specifying the destination environment” on
page 220.
To select the types of objects to import
1. Choose the types of object to import.
Note: The options that appear depend on the source environment and
its version, and on whether you selected the “Import Application
Foundation contents” check box.
By default, all object types are selected, so you must do one of the
following:
• Clear the check boxes for the items you don’t want to import, and
then click Next.

Note: The Import Broadcast Agent Schedules check box is dimmed
and cannot be selected if there are no Broadcast Agents and no jobs
to import in the repository.
• Accept the defaults, which is to import all documents, and then click
Next.
2. In the Import Scenario dialog box, select the type of import you want.
• To merge the source and destination environments, select I want to

merge the source system into the destination system.

• If you want to automatically rename top-level folders that match

top-level folders on the destination system, select the check box
beneath the merge option.
• To update the destination environment without merging, select I want
to update the destination system by using the source system as
a reference.
• If you want to automatically rename objects when an object with
the same title already exists in the destination folder, select the
check box beneath the update option.
For more details on the different scenarios, see “Choosing an import
scenario” on page 227.
3. If you see the Incremental Import dialog box, select the type of objects
whose content you want to overwrite.
These are your choices:

• Documents (including dashboards and analytics)
• Universes
• Connections
Note: The Incremental Import dialog box appears if you selected the
Update option a previous step.

4. If you want to overwrite object rights, select the Overwrite object rights
check box, and then click Next; If you don’t want to overwrite objects
rights, click Next.
5. If you are prompted to select specific objects for import, see “Selecting
specific objects to import” on page 229 for details on your specific object
type.
Note: The specific dialog box that appears will vary based on what you
are importing. However, the reason you will see one is because you
selected the Merge option a previous step.
6. If you opted to import users or groups, select one of the security
migration options, and then click Next.
These are three security migration options:

• Yes, migrate security on imported objects and secure the destination
system.
This is the most secure option.
• Yes, migrate security on imported objects
Users in the destination system may receive more rights than in the
source system.
• No, don’t migrate security
Note:
• The Security Migration Options dialog box appear if you selected
Import users and user groups.

• Universe overloads are not included in the Security migration.

You select overload migration on the Import Options for
Universes and Connections dialog box . For more information,
see “Universe and connection objects” on page 236.
For a full discussion of these options, see the BusinessObjects 5.x to
XI Release 2 Migration Guide.
7. If you selected the import of objects stored either in inbox or personal
folders, type or browse for the path of your Personal and/or Inbox
documents in the source environment.
Note:
• If the files are located on a remote server, you must have mapped
the remote server to your local machine.
• If the files are located on a UNIX server, you must have mapped the
UNIX server to a local drive.
• You do not need to provide a path for corporate documents because
they are stored in the repository.
• Import Wizard imports both read and unread Inbox documents to XI
R2.
.
8. If you want to limit the import of Inbox documents to those received after
a certain date:
• Select the Import Inbox documents received after check box
• Set the date
9. If you want to limit the import of Personal documents to those created or
modified after a certain date:
• Select the Import Personal documents that have been modified
or created since check box
• Set the date
10. Click Next.
11. If you chose to import universes in the Select Objects to Import dialog
box, select one of these import options:
This imports all universes from the source environment in one batch.
You cannot select individual universes or connections.
• Import all universes, and only connection objects used by those
universes

• Import universes and connections that the selected Web Intelligence
In a later dialog box, you will be able to select additional universes to
import.
12. If you want to migrate universe overloads, select the Keep universe
overloads for imported users and groups check box.
If you do not select this, then no universe overloads will be migrated.

13. Click Next.
14. If the Ready to Import dialog box appears, go to “Finalizing the import” on
page 237.
Proceed to “Selecting specific objects to import” on page 229.
For more information about merging and updating systems, see Crystal
Repository chapter in the BusinessObjects Enterprise Administration guide.
Choosing an import scenario

When you choose an import scenario, you can merge the source and
destination environments, or you can update the destination environment
without merging.
• When you merge the environments, the Import Wizard adds all objects
from the source to the destination CMS without overwriting objects in the
destination environment. This is the safest import option. All of the
objects in the destination environment are preserved.

• When you update the destination environment, all objects in the source
are added to the destination CMS, but if a source object has the same
unique identifier as an object in the destination environment, the
destination object is overwritten.
Note: When CUIDs are changed, links between documents, rules, and
other objects that refer to each other using CUIDs may be impacted. If
you import objects with links to other objects, the safest option for
migration is the second option (Updating the destination environment).
This procedure assumes you have already specified the source and
destination environment and selected the type of objects to import. If you
have not already started the Import Wizard, see “Specifying the source
environment” on page 213, “Specifying the destination environment” on
page 220 and “Selecting the type of objects to import” on page 222.
Updating previously imported objects

You may need to import some objects more than once from the source
repository to the destination repository.
In this situation, you have the following update options:
• Overwrite object contents
You must select the types of objects for which the content overwrite
applies:
• Documents (including dashboards and analytics)
• Universes
• Connections
When you reimport an object, it will completely overwrite and replace the
object (and its associated files) that you imported earlier.
• Overwrite object rights
When you reimport an object, its associated security rights will overwrite
the rights of the object you imported earlier.
If you decided not to import security in the Security Migration Options
dialog box, then the Overwrite object rights option is not relevant, and is
therefore not available.
Note: If you don’t select any overwrite options, the object in the destination
repository will not change when you try to import it again.

Selecting specific objects to import
This procedure assumes you have already specified the source and
destination environment and selected the type of objects to import. It also
assumes you have chosen an import scenario. If you have not already started
the Import Wizard, see “Specifying the source environment” on page 213,
“Specifying the destination environment” on page 220 and “Selecting the type
of objects to import” on page 222. For further information about import
scenarios, see “Choosing an import scenario” on page 227.
After you choose an import scenario, you are prompted to choose the specific
objects you want to import. You can import all of the objects or select
individual objects.
You may be prompted to select any of the following to import:
• “Users and groups” on page 229
• “Populating database credentials” on page 230
• “Dashboards” on page 231
• “Broadcast Agent” on page 231
• “Categories” on page 232
• “Document domains and documents” on page 233
• “Universes” on page 234
• “Universe and connection objects” on page 236
Users and groups

If you chose to import users and groups, the “Users and Groups” dialog box
appears. It may take some time before the users and groups are displayed,
because the Import Wizard is retrieving them from the repository.
Note: For detailed information on the import of users and groups, see the

To select users and groups

1. In the Groups list, select the groups that you want to import.
2. In the Users list, select specific members of any group.

3. Click Next.
Note: Only the General Supervisor type is added to the Administrators
Users group:
4. If the Import Groups Option dialog box appears, select if you want group
mappings from LDAP and Active Directory to be migrated to 1.0.
Note:
• If the Import Groups Option dialog box appears, the 6.x source and
the 1.0 destination environments are configured for LDAP or Active
Directory. You need to have the same LDAP or Active Directory
configuration on the source and destination.
• For information about setting alias creation and assignment for LDAP
and Active Directory users, see the BusinessObjects Enterprise
Administrator’s Guide.
5. 5. Click Next.
Populating database credentials

After users and groups are imported, the Populate Database Credentials
dialog box appears.

This dialog box enables you to automatically set the DBUSER and DBPASS
attributes, for all imported users, with their login and password. These can be
used as default database credentials for connections.
1. Decide if you want the Import wizard to import database credentials for
users.
• If you want to populate the database credentials of imported users
with their BusinessObjects user name and password, select Yes.
• If you do not want to do this, select No.
2. Click Next.
Broadcast Agent
If you are importing Broadcast Agents, the Broadcast Agent dialog box
appears.This dialog box enables you to select the Broadcast Agents you want
to import.
Note: A Broadcast Agent job can be migrated from BusinessObjects 5.x/6.x
to 1.0 only if the job is supported in 1.0. (For details, see the BusinessObjects
5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release
2 Migration Guide.)
To select Broadcast Agents for import
1. In the Broadcast Agent dialog box, select the Broadcast Agents whose
jobs you want to import.
Note that all the jobs, for each Broadcast Agent, are selected by default.
2. Click Next.
Dashboards
If you are importing dashboards, the Dashboards dialog box appears.
To select dashboards
1. Select the dashboards you want to import.
When you select an application, its submenus are also selected.
2. Click Next.
The Import Wizard checks whether any dashboards in the source
repository include security. If the Import Wizard detects security on any
dashboards, the Import Dashboard Option dialog box appears. If none of
the dashboards selected for import includes security, skip to step 4.
3. If dashboards selected for import include security, select one of the
following options:

• Import and apply page security on all page elements

The Import Wizard migrates the dashboard and any sub-menus and
applies standard page-level security, which is translated as an ACL
in the CMS. With this option, the least restrictive set of rights is
applied.
• Don’t import such dashboards
The Import Wizard imports all dashboards, including dashboards
with analytic-level security restrictions, but empties all content from
pages containing secured elements. Dashboard menu structures are
preserved.
• Import but move to administrator’s Favorites folder for revision
The Import Wizard imports all dashboards, including secured
dashboards, but empties the content of all secured dashboards.
When you choose this option, dashboard menu structures are
preserved and a copy of each secured dashboard, including its
contents, is moved to the administrator’s favorite folder. A prefix is
added to the secured dashboard’s name so that the administrator
can easily identify it after migration, then modify it manually before
publishing it to a wider audience.
Categories
If you are importing categories, the Categories dialog box appears.
To select categories
1. Select the check boxes for the categories that you want to import.

For large document domains, you can import incrementally, and import
documents one category at a time.
2. If you want to import all the objects associated with the category, select
the Import all objects that belong to the selected categories check box.
3. Click Next.
Document domains and documents

The Domains and Documents dialog box appears if you choose to import any
of the following document types:
• Web Intelligence
• Desktop Intelligence (BusinessObjects)
• performance management (Application Foundation)
• Analytics (Performance Management) (6.x only)
• Third-party
The list contains a separate branch for each domain. Domains that cannot be
opened are greyed out. If you previously chose to import all the documents of
a given category, they are preselected and cannot be cleared.
To select domains and documents
1. Select the check boxes for domains or individual documents that you
want to import.
2. Click Next.

The Locales and Platform Options dialog box appears.
In a BusinessObjects 5.x/6.x repository, some WebIntelligence 2.x (.wqy)

documents and BusinessObjects documents may not store their locales.
In order to set locales in these documents when they are saved in the
CMS (after conversion to .wid), the default locales provided by the user
are added to the documents.
3. Select the locale of the source from the top list.
4. Select the local of the destination from the bottom list.
5. Click Next.
Universes
To select universes or universe folders
1. Select the check boxes for the universes that you want to import.
The universes that are linked to specific documents cannot be cleared
from the list.You can select additional universes that are not used by any
imported document.

2. Click Next.
If no universe is found, the associated documents will not be imported

and a warning message appears. If this occurs, link the documents to a
universe, republish them to the repository, and retry the import.
Note: When you import a universe, its connection objects are imported
automatically. Before you can import connection objects from
BusinessObjects 5.x/6.x, ensure that the Import Wizard can access the
database the same way that the source environment accesses it. This
may involve installing database drivers or configuring connection settings
on the machine. For example, if you import SQL Server connection
objects from a BusinessObjects 6.x source environment, you must
configure the connections on the destination machine via the ODBC Data
Source Administrator settings in the Windows Start Menu Control Panel
before you import the connection objects. You must use the exact same
name and settings as the connection used on the source machine when
you created the domain key.
To select folders and objects
• If you chose to import folders and objects, the “Select Folders and
Objects” dialog box appears. Select the check boxes for the folders and
reports that you want to import. Then click Next.
Tip: You can also choose to “Import all instances of each selected report
and object package.”
This example imports the Report Samples folder and a subset of its
contents.

To select repository objects

• If you chose to import repository objects, the “Import repository objects
options” dialog box appears. Choose an importing option for repository
objects, then click Next.
Universe and connection objects

If you chose to import universes in the Select Objects to Import dialog box,
the Import Options for Universes and Connections dialog box appears.

When you import scheduled documents from 6.x, you must also import the
universes used by these documents. The universes are not selected
automatically during the import. This means that if you are not importing all
your universes, you must manually select the ones you need for Broadcast
Agent jobs.
To import universe and connection objects
1. Select an import option:
This imports all universes from the source environment in one batch.
You cannot select individual universes or connections.
• Import all universes, and only connection objects used by those
universes
• Import universes and connections that the selected Web Intelligence
In a later dialog box, you will be able to select additional universes to
import.
2. If you want to migrate universe overloads, select the Keep universe
overloads for imported users and groups check box.
If you do not select this, then no universe overloads will be migrated.
3. Click Next. If you chose to import a subset of the universes from the
source environment, the “Select Universe Folder and Universes” dialog
box appears.
If no universe is found, the associated documents will not be imported
and a warning message appears. If this occurs, link the documents to a
universe, republish them to the repository, and retry the import.
Finalizing the import

To finalize the import
1. When the Ready to Import dialog box appears, click Import to begin
importing the information.

Using text files with the Import Wizard
The Import Progress dialog box appears. It shows the progress of the
import and a summary of the events taking place.
2. If the import summary shows that some information was not imported
successfully, click View Detail Log for a description of the problem. If the
import summary shows no failures, click Done.
Note: The information that appears in the Detail Log is also written to a
text file called ImportWiz.log, which you will find in the directory from
which the Import Wizard was run. By default, this directory is:
C:\Program Files\Business Objects\BusinessObjects
Enterprise 11\win32_x86\
The log file includes a system-generated ID number, a title that describes
the imported information, and a field that describes the action and the
reason why it was taken.

The Import Wizard can import any of the following from text files:
• Users
• Groups
• Profiles
• Data source credentials
A combination of users, groups and profiles can be in one file, but data source
credential must be in a separate text file.

Using text files with the Import Wizard 12
Text file format
All text import file data must be in the comma-separated value (CSV) file
format. For specific details on what each field represents, see “Importing
users, groups and profiles” on page 239 and “Importing data source
credentials” on page 241. The CSV format stipulates the following:
• The comma (,) is the default separator.
• The default delimiter is double quotes (").
• The fields that contain a separator must begin and end with a delimiter.
For example, if you wanted the value Smith, John in a field, you would
enter “Smith, John”.
• The fields that contain a delimiter, must begin and end with a delimiter
and use two delimiters where one is required.
For example, if you wanted the value “quotes”, you would enter
"""quotes""", if your delimiter was double quotes. If your delimiter was a
single quote ('), and you wanted the value dog’s, you would enter 'dog''s'.
Note: The default delimiter and the default separator can be changed on the
“Select options for file import” dialog box.
Importing users, groups and profiles

The Import Wizard can import users, groups and profiles from text files. Files
used to import users, groups or profiles must be structured as follows:
• Each row in the text file defines 1 record.
• Each record consists of 6 fields.
• Each field must have separator between it and the next field.
• Each field, can potentially be blank except for field 1.
One single record can define either a group or a user or a group, a user and a
profile. Text files must be saved in UTF-8 format.
Note:
• The default separator is a comma but this can be changed on the Select
options for file import dialog box.
• If a character in the any field of the record is the same as the character
used for a separator it must be delimit. The default delimiter character is
a double quote.

User record Format
Field Number Contents of field

Field 1 Group name
Field 2 User Name
Field 3 Full name of user
Field 4 Email address of user
Field 5 Profile name for user.
Field 6 Profile value for user.
Note: Profile values must be enclosed in quotes. See “Text file format” on
page 239 for information on using delimiter.
Example user record
Sales,Psanders,Paula Sanderson,psanders@Acme.com,
Manager,West Region
The previous record would create an account name or username of
“psanders” in BusinessObjects Enterprise. The name Paula Sanderson, and
the e-mail address of psanders@Acme.com would be associated with this
account name. The username “psanders” would be member of the group
“Sales”. The username psanders and would be assigned the profile
“Manager” with the profile value of “West Region”.
Group Record Format

Field 1 Group name
Field 2 Null
Field 3 Description of group.
Field 4 Field is ignored.
Field 5 Profile name for group.
Field 6 Profile value for group.
Note: Profile values must be enclosed in quotes. See “Text file format” on
page 239 for information on using delimiter.
Example Group record
Best,,Group for sales people,,Sales,General

The previous record would create the “Best” group, with description of “Group
for sales”. The profile Sales would be assigned the profile value “General”.
Importing data source credentials

The Import Wizard can import data source credentials from text files. These
are the database credentials used for Business Object Universes. Files used
to import secondary database credentials must be structured as follows:
• Each row in the text file defines 1 record.
• Each record consists of 3 fields.
• Each field must have separator between it and the next field.
• Each database username must be associated with a Enterprise
username that already exists.

Field 1 Existing username
Field 2 Database Username
Field 3 Database password
Example database credential

Psanders,dbuser,Dbpasw0rd
The previous example create the account name “dbuser” and the password
“Dbpasw0rd” associated with Enterprise user Psanders. The option “Enable
Data Source Credentials for Business Object Universes” would also be
selected for username Psanders.
Importing from text files

This section explains how to import any of the following from text file:
• Users
• Groups
• Profiles
• Data source credentials
For details about the format of these files, see “Text file format” on page 239.
To import from text files
BusinessObjects XI R2 > BusinessObjects Enterprise > Import
Wizard.


2. Click Next.
3. Select Text file from the Source list.
4. Click the browse icon.
5. Locate the file to import, and then click Next.
6. Enter the name and credentials for the CMS, and then click Next.
The Select options for file import appears.
7. Decide what you want to import.

• To import profiles, users and groups
a. Make sure the select type of file to import list is set to Profiles,
Users and Groups.
b. If you want your text file to only create profiles, users or groups,
but not update the data already entered, clear the update
options.
c. If you want your text file to only update profiles, users or groups,
but not create new profiles, users or groups, clear the create
options.

d. To remove all existing users from a group specified in the import
file, whose membership in the group is not specified in the file,
select Remove users from a group if not included and clear
Add users to a group if not a member.
e. To add existing users or users in the import file to a group if they
are not a member, make sure Add users to a group if not a
member is selected.
f. Click Next.
• To import data source credentials
a. Select Data Source Credentials from the list.
b. Click Next.
c. Click Finish.
The file will be imported.
Note: If you are importing data source credentials, none of the
remaining steps in this procedure apply.
The select application folders and objects dialog box appears.
8. Click Next.
9. The Preview results from file import dialog box appear.
10. Review that the results are what you expect, and then click Next.
The results on this screen show the how the first user or group will be
created, after all the records in the import file have been parsed.

If your record includes both a user and a group, the user preview will be
displayed by default. To see how the what group may be created, click
Group.
11. Click Finish to begin the import.
12. Click Import to exit the Import Wizard.

Custom SDK Deployments
chapter
13 Custom SDK Deployments
Software Development Kit overview
Software Development Kit overview

By default, if you have a version of BusinessObjects Enterprise that includes
developer components, the BusinessObjects Enterprise Software
Development Kits (SDKs) are installed and configured when you install
The BusinessObjects Enterprise Java SDK uses the Java Development Kit
(JDK). If you are using a J2EE web application server and the setup program
does not detect the JDK on the machine, it installs the JDK automatically.
After you install BusinessObjects Enterprise, all of the BusinessObjects
Enterprise servers are enabled and running by default. You can implement
custom web applications using Java Server Pages (JSP).
The following Application Programming Interfaces (APIs), along with
developer documentation, are included with BusinessObjects Enterprise:
• BusinessObjects Enterprise COM and Java interfaces
• Report Application Server COM and Java interfaces
• Report Viewer COM and Java interfaces
• JavaServer Faces (JSF) tag library
Note:
• Report Application Server supports COM and Java viewer SDKs. In
addition, however, the Report Application Server includes its own
Software Development Kit (SDK) for report-creation and modification,
thereby providing you with tools for building your own web-based
reporting and query tools. Your BusinessObjects Enterprise license key
determines whether or not the report-creation SDK and InfoView
integration features are available to you.
• Refer to the Release Notes and the Platforms.txt on your product
distribution for information on limitations, system requirements, and so
on.
• For developer-specific information, see the developer documentation
available on your product CD.
Java Server Pages environment

BusinessObjects Enterprise supports web applications that are implemented
using Java Server Pages (JSP).

Custom SDK Deployments
Java Server Pages environment 13
On UNIX, BusinessObjects Enterprise uses the BusinessObjects Enterprise
Java SDK and includes a version of InfoView written in JSP. It uses a Java
web application called the Web Component Adapter to run legacy Crystal
Server Pages (CSP) applications. Before you run any of your applications
that are implemented using JSP, ensure that you have deployed them to the
appropriate folder for the web application server you are using. For more
information on deploying WAR and JAR files see the documentation that is
specific to your web application server in the following sections:

13 Custom SDK Deployments
Java Server Pages environment

Upgrading and Migrating
chapter
14 Upgrading and Migrating
What does this section cover?
What does this section cover?

This section describes how to migrate to BusinessObjects XI Release 2 from
any of the following versions:
• Crystal Enterprise 8.5
• Crystal Enterprise 9
• Crystal Enterprise10
• BusinessObjects Enterprise XI
What this section does not cover

This guide does not cover how to migrate from the following versions.
• BusinessObjects version 5.x
• BusinessObjects version 6.x
• WebIntelligence 2.x through 6.5.x
For further information on these topics, see the following documents:
• BusinessObjects 5.x to XI Release 2 Migration Guide
• BusinessObjects 6.x to XI Release 2 Migration Guide.
Upgrading from Crystal Enterprise or from

The process of moving from an earlier release of Crystal Enterprise or
BusinessObjects Enterprise involves several steps which can be divided into
three categories: upgrading, migrating, and importing.
• Upgrading consists of replacing existing components and files with the
latest BusinessObjects Enterprise versions.
Note: The term upgrading in this section refers to when you uninstall the
previous version first and then install the new version.
• Migrating consists of copying data from your old CMS database to a
BusinessObjects Enterprise XI Release 2 CMS.
This includes moving a Crystal Management Server database, or a
BusinessObjects Enterprise XI Release 1 Central Management Server to
a new BusinessObjects Enterprise XI Release 2 CMS database, while at
the same time updating the database schema to the latest version.

Upgrading from Crystal Enterprise or from BusinessObjects Enterprise 14
• Importing consists of copying objects (reports, users, groups, and so on)
and instances from one system to another.
The focus of this section is upgrading and migrating. For information on
importing, see “Importing Objects to BusinessObjects Enterprise” on
page 187.
Note:
• If you’re upgrading from Crystal Enterprise 9, you will also need to
migrate your Crystal Enterprise Repository and/or your Crystal Reports
repository. If your migrating performance management InfoObjects from
BusinessObjects Enterprise XI, you will also need to migrate the
performance management repository.
• Repository objects used by Business Views are always imported in
Update mode, even when the Merge option is selected.
If you are upgrading or migrating from Crystal Enterprise 9 or 10 or
BusinessObjects Enterprise XI, read the following topics:
• “Preparing for upgrading or migrating” on page 252
• “Migration options” on page 253
• “Disabling and stopping servers” on page 253
• “Upgrading other components” on page 264
• “Migrating the CMS or APS data” on page 254
This is done from the Central Configuration Manager
• “Copying data from a Crystal Enterprise 9 repository database” on
page 257 and “Copying data from a Crystal Reports 9 repository
database” on page 261
This is done from the Repository Migration Wizard.
Note: This step only applies if your migrating from Crystal Enterprise 9.
• “Upgrading other components” on page 264
• “Completing a CMS database migration” on page 265
If you are upgrading from BusinessObjects Enterprise 5.x/6.x see the

Preparing for upgrading or migrating

It is expected that you will follow your usual administrative practices before
upgrading to BusinessObjects Enterprise or migrating system data from
earlier product releases. However, you should also consider the following
common tasks and guidelines:
• Consult the Release Notes included with your product distribution for
further information that may pertain to your reporting environment
(release.pdf).
• Disable and subsequently stop all BusinessObjects Enterprise or Crystal
Enterprise components before upgrading.
• Stop the web servers and/or web application servers that are configured
for use with BusinessObjects Enterprise or Crystal Enterprise.
• Ensure that you have details about the database server and accounts
that are used for the existing system database and that will be used by
the new system database.
• Back up your existing repository or repositories, including the system
database. For Crystal Enterprise, also back up the root directories used
by the Input and Output File Repository Servers.
• Back up any custom web applications, HTML pages, or scripts that you
have added to your existing deployment.
• Make sure you log onto the machine as an administrator first when you
install BusinessObjects Enterprise components.
• Close any other programs that are running locally before you start the
BusinessObjects Enterprise setup program.
• If you are upgrading from Crystal Enterprise, you must migrate your
existing Crystal Management Server or Automated Process Scheduler
(APS) to the latest format. Ensure that you first install the new
components on a machine with one of these components, so you can
immediately create a new CMS database and then migrate system data
from the old database. (If you’re upgrading from BusinessObjects
Enterprise 5.x or 6.x, the migration to BusinessObjects Enterprise 6.5
occurs automatically.)
• If you’re upgrading a UNIX installation, it is important to note that the
UNIX version of BusinessObjects Enterprise XI R2 uses your existing
Java web application server. A Java web application server must be
installed and configured before you can use BusinessObjects Enterprise
on UNIX. For more information about configuring BusinessObjects
Enterprise components to work with your Java web application server,
see “Installing BusinessObjects Enterprise on UNIX” on page 47.

Preparing for upgrading or migrating 14
Migration options
Several options are available to you, depending upon your current system
and your preferred method of upgrading:
• Set up a new BusinessObjects Enterprise system alongside your original
system, and then migrate old system data into the new CMS database.
In this scenario, you need additional hardware for the new
BusinessObjects Enterprise system. When the new system is ready, you
migrate your original Crystal Management Server, APS database, or
BusinessObjects Enterprise XI Release 1 CMS so it becomes the CMS
database for the new system, and you ensure that the new Input and
Output File Repository Servers can access the root directories that were
used by the older system. For details, see “Configuring your CSP
applications for the Web Component Adapter” on page 264.
• Set up a new BusinessObjects Enterprise system, and then import
content from an existing Crystal Enterprise or Crystal Info system.
Again, this scenario requires additional hardware for the new
BusinessObjects Enterprise system. Instead of migrating an existing
database, you selectively import content (user accounts, groups, folders,
reports, and so on) into the new system. For details, see “Importing
content from BusinessObjects Enterprise, Crystal Enterprise, or Crystal
Info” on page 264.
Note: Before proceeding with any upgrade or migration, see “Preparing for
upgrading or migrating” on page 252.
If you require further assistance in upgrading particularly large-scale and/or
mission-critical deployments, or in migrating customized reporting
applications, it is recommended that you contact a Business Objects Services
consultant, who can then assess your reporting environment and assist in the
upgrade and migration process.
Disabling and stopping servers

Before you begin your upgrade you must stop and disable any servers from
previous versions.
To disable and stop Crystal Enterprise and BusinessObjects Enterprise
XI servers on Unix
1. Go to the directory <INSTALLDIR>/bobje, where INSTALLDIR is
the directory where you installed BusinessObjects Enterprise.
2. Type the following two commands:
./ccm.sh -disable all

./ccm.sh -stop all
Migrating the CMS or APS data

If you install a new BusinessObjects Enterprise system alongside your
original installation, you can use the latest version of the Central
Configuration Manager to migrate system data from the old Crystal
Management Server, APS database or CMS database into the new
BusinessObjects Enterprise XI Release 2 CMS database. In addition, you will
need to provide the newly installed File Repository Servers with access to the
root directories used by the File Repository Servers in the old Crystal
Enterprise system.
Copying data from a CMS installed on UNIX

Use this procedure if your CMS is installed on UNIX and you are copying data
from versions 8.5, 9, or 10 of Crystal Enterprise or from version XI of
BusinessObjects Enterprise. After you have completed this procedure, you
must completed your CMS migration. For more information, see “Completing
a CMS database migration” on page 265.
Note:
• Prior to BusinessObjects Enterprise XI, the CMS was known as Crystal
Management Server, and also as the Automated Process Scheduler
(APS).
• On UNIX you can not migrate directly from a source environment that
uses an ODBC connection to the CMS database. If your source CMS
database uses ODBC, you must first migrate that system to a supported
native driver.
To copy data from a CMS installed on UNIX
1. Stop the Central Management Server. Type the following command:
./ccm.sh -stop cms
2. Run cmsdbsetup.sh.
./cmsdbsetup.sh
3. Accept the default CMS name or enter your CMS name to override the
default.
Tip: Do not use Backspace or any of the arrow keys to override the
default name. Instead, to override the default, type your CMS name
beside the default CMS name and press Enter.
4. Type copy to begin the database migration.

A warning will be displayed that indicates that all data in the destination
database will deleted.
5. Type yes, and then press Enter to proceed.
6. Specify the version you want to migrate from.
You have these choices:
• For Crystal Enterprise 8.5, enter 7.
• For Crystal Enterprise 9, enter 6.
• For Crystal Enterprise 10, enter 5.
• For BusinessObjects Enterprise XI (11), enter 4.
• For BusinessObjects Enterprise XI R2 (11.5), enter 3.
• For autodetect, enter 2.
7. Decide if you want to use the current CMS Data Source database as the
destination database.
• If you want to use the current CMS Data Source as the destination
database, type yes.
• If you do not want to use the current CMS Data Source as the
destination database, type no.
8. Specify one of these database types for your database.
• Oracle
• DB2
• Sybase
• MySQL
Note: If you entered no in the previous step, specify your destination
database type. If you entered yes in the previous step, specify your
source database type.

9. Complete the required information, based on your database type, and

then press Enter.
For Oracle
Enter the TNS name.
Enter the user name and
password for the database.
For DB2
Enter the alias name.
password for the database
For Sybase
Enter the service name.
password for the database.
For MySQL
Enter the host name.
Enter the port number.
Enter the database name.
password for the database
The copy will begin. A message will be displayed when copy is complete.
If errors occurred during the migration, the location of a log file that
explains the migration results will be displayed.
Note:
• Migration of a large source database could take several hours.
• At the end of the database migration, you may be prompted to
update certain report objects. You cannot complete this step until the
File Repository Servers have been upgraded and BusinessObjects
Enterprise is back online. Therefore, you must postpone this step
until you have finished upgrading components.

Copying data from a Crystal Enterprise 9 repository database
In Crystal Enterprise 9, the Crystal Repository database was hosted on a
separate database server that you could connect to through ODBC. The tool
you use to migrate this information is called the Repository Migration Wizard
and is available on Windows as part of the client tool installation. For
information on client tools, see “Performing a client tool installation” on
page 63.
In a BusinessObjects Enterprise environment, begin by making a backup
copy of the source repository database. Then replace the repository by
importing its contents into the CMS database using the Repository Migration
Wizard.
When you use the Repository Migration Wizard, neither the source nor the
destination database is overwritten. Objects from the source repository will be
added to the destination repository database. If the Wizard finds identical
objects (that is, objects with the same unique identifier) in the source and
destination repositories, the source objects will not be copied.
When you copy repository objects into BusinessObjects Enterprise XI, only
the most recent version of each object is copied.
Note: Reports configured to use the source repository will now refer to the
destination data source.
To copy repository data from Crystal Enterprise 9
1. From the BusinessObjects Enterprise program group, click Repository
Migration Wizard. You must run the wizard on the machine containing
your source repository.
2. From the Source list in the Select Source Repository dialog, click the
name of the repository that you want to import.
3. Type the UserID and Password of a user with administrative rights to the
repository database. Click Next.
4. The Select Destination Data Source dialog appears. In the CMS field,
type the name of the destination data source’s Central Management
Server.
5. Type the User Name and Password of an Enterprise account that
provides you with administrative rights to the CMS; then click Next.

6. From the “Source Repository Objects” list, select the items that you want
to copy to your BusinessObjects Enterprise repository database. Click
Next.
BusinessObjects Enterprise exports the selected repository objects from

your BusinessObjects Enterprise Repository, reporting success or failure
for each object.
7. Select the folder in your destination repository where objects from your
source directory will be placed.

• To add objects to a new folder, select “Insert a new folder”, and then
type the name of the folder.
• To delete an existing folder from your repository, select it, and then
click “Delete the item/folder”.
8. Click Next, and then Finish to complete the transfer and close the
Repository Migration Wizard.
objects in the source and destination repositories, the source objects will not
be copied.
To copy repository data from Crystal Enterprise 9

3. Type the UserID and Password of a user with administrative rights to the
repository database. Click Next.
4. The Select Destination Data Source dialog appears. In the CMS field,
type the name of the destination data source’s Central Management
Server.
5. Type the User Name and Password of an Enterprise account that
provides you with administrative rights to the CMS; then click Next.
Next.

your BusinessObjects Enterprise Repository, reporting success or failure
for each object.

be copied.
Copying data from a Crystal Reports 9 repository database

The Crystal Repository shipped with Crystal Reports 9 was an Access
database (Repository.mdb). By default, it was located in the following
directory of your Crystal Reports installation:
C:\Program Files\Common Files\Crystal Decisions\2.0\bin\

Begin by making a backup copy of this default database. Then replace the
default repository by importing its contents into the CMS database using the
be copied.
To copy repository data from Crystal Reports 9
If you created security for your repository database, type a User id and
Password valid for the repository database.
3. Click Next.
4. Log on to the CMS using a user name with administrative rights to
Next.

7. Click Next.
your Crystal Reports repository, reporting success or failure for each
object.
Migrating from the Web Component Server to the Web Component Adapter
In BusinessObjects Enterprise XI, the Web Component Server (WCS) was
deprecated. All BusinessObjects Enterprise applications that used the WCS
have been migrated to use the Web Component Adapter (WCA).
The WCS was a Crystal Enterprise application server that provided two main
services: an engine for processing Crystal Server Pages (CSP), and an
application engine for CSP web applications.

Upgrading other components
Configuring your CSP applications for the Web Component Adapter

CSP-based application hosting is now handled by your Java application
server. If you want to use existing CSP-based applications with
BusinessObjects Enterprise XI, you need to configure them to work with the
Web Component Adapter (WCA).
Importing content from BusinessObjects Enterprise,

Crystal Enterprise, or Crystal Info
The Import Wizard allows you to selectively import objects and instances from
an existing BusinessObjects Enterprise, Crystal Enterprise, or Crystal Info
system to a newly installed BusinessObjects Enterprise system. Run the
Import Wizard from the BusinessObjects Enterprise XI R2 program group.
Tip: Because the BusinessObjects Enterprise setup program cannot directly
upgrade BusinessObjects Enterprise 6.x systems to BusinessObjects
Enterprise, the Import Wizard is the tool to use if you are copying
BusinessObjects Enterprise 6.x user accounts, groups, folders, and reports
into a new BusinessObjects Enterprise system.
For more information, see “Importing Objects to BusinessObjects Enterprise”
on page 187.

This section also explains what you need to do to complete a CMS migration
after the new software is installed.
Upgrading the Report Application Server

If you are running the unmanaged version of RAS that is included with Crystal
Reports 9 or 10, you must uninstall the previous version or RAS before you
install the new version of BusinessObjects Enterprise. Then you can migrate
your applications to the managed version of the RAS that is installed with this
latest release of BusinessObjects Enterprise.
Note: To create and modify reports over the Web through the Report
Application Server, be sure to enter your additional license key(s) in the
Authorization management area of the Central Management Console.
Upgrading Crystal Reports

This release of BusinessObjects Enterprise includes an updated version of
Crystal Reports. You have two choices:

Upgrading other components 14
• You can uninstall the existing version of Crystal Reports, and then run the
setup program to upgrade the existing versions of Crystal Reports to
replace the old software with Crystal Reports XI.
• You can have both the new and the old versions on the same machine.
Migrating from Crystal Analysis to OLAP Intelligence

Versions 8.5 and earlier of Crystal Analysis are not supported for use with this
release of BusinessObjects Enterprise. If you want to upgrade to the new
version of OLAP Intelligence, you must uninstall the old version before you
install the new.
Completing a CMS database migration

When you finish copying data from the source database to the destination
database, complete these steps before allowing users to access the system.
When migrating from an older version of Crystal Enterprise, servers that
existed in the source installation do not appear in the migrated install. This
occurs because there cannot be a mix of old and new servers in a
Server groups from the old installation appear in the new system, but they will
be empty. New servers are automatically detected and added to the servers
list (outside of any group) in a disabled state. You must enable these servers
before they can be used. You may add the new servers to the imported
groups as appropriate.
Reports that depend on a particular server group for scheduled processing
will not execute until a job server is added to that group. Reports that depend
on a particular server group for processing are not available until servers are
added to that group.
To complete a CMS database migration on UNIX
1. If errors occurred during migration, a db_migration log file was created
in the logging directory on the machine where you ran cmsdbsetup.sh
to carry out the migration. The script will notify you if you need to check
the log file.
The default logging directory is:
BusinessObjects_root/logging
where BusinessObjects_root is the absolute path to the root Business
Objects directory of your BusinessObjects Enterprise installation.

2. If you migrated CMS data from a different CMS database into your
current CMS database, you need to make your old input and output
directories available to the new Input and Output File Repository Servers.
You can do this in several ways:
• Copy the contents of the original input root directory into the root
directory that the new Input File Repository Server is already
configured to use. Then copy the contents of the original output
directory into the root directory that the new Output File Repository is
already configured to use.
• Reconfigure the new Input and Output File Repository Servers to use
the old input and output root directories.
• If the old Input and Output File Repository Servers are running on a
dedicated machine, you can run the BusinessObjects Enterprise
setup program to upgrade the servers directly. Then you need not
move the input and output directories. Instead, modify the -ns option
in both servers’ command lines to have them register with your new
CMS.
3. Use the ccm.sh script to start the CMS on the local machine.
4. Ensure that the Java web application server that hosts your Web
Component Adapter is running.
5. Log on to the Central Management Console with the default
Administrator account, using Enterprise authentication.
Tip: If you just replaced your CMS database with data from an older
system, keep in mind that you now need to provide the Administrator
password that was valid in the older system.
6. Go to the Authorization management area and check that your
BusinessObjects Enterprise license keys are entered correctly.
7. Use the ccm.sh script to start and enable the Input File Repository
Server and the Output File Repository Server.
8. Go to the Servers management area of the Central Management
Console and verify that the Input File Repository Server and the Output
File Repository Server are started and enabled.
9. Click the link to each File Repository Server and, on the Properties tab,
check that the Root Directory points to the correct location.
10. Run the ccm.sh script again. If you migrated a source database from an
earlier version of BusinessObjects Enterprise, enter the following
command:
./ccm.sh -updateobjects authentication info

Migrating to performance management XI Release 2 14
See “Unix tools” in the BusinessObjects Enterprise Administrators Guide
for information on the authentication information required by ccm.sh.
Objects typically require updating because their internal representation
has changed in the new version of BusinessObjects Enterprise, or
because the objects require new properties to support the additional
features offered by BusinessObjects Enterprise XI.
11. Use ccm.sh to start and enable the remaining BusinessObjects
Enterprise servers.
12. Verify that BusinessObjects Enterprise requests are handled correctly,
and check that you can view and schedule reports successfully.
Migrating to performance management XI

Release 2
The Import Wizard copies performance management InfoObjects from
BusinessObjects Enterprise XI to BusinessObjects Enterprise XI Release 2.
As in previous versions, performance management products rely on a
dedicated repository that stores performance management data as well as
the CMS.
To migrate BusinessObjects Enterprise XI to BusinessObjects Enterprise XI
Release 2, follow these steps:
• Install BusinessObjects Enterprise XI Release 2 and configure the CMS.
• Run the Import Wizard to copy InfoObjects from the previous version and
to import connections to the connection server (refer to “Importing
Objects to BusinessObjects Enterprise” on page 187).
• Migrate the performance management repository (refer to Migrating the
performance management repository).
About the Connection Server

Connections to the performance management repository are imported by the
Import Wizard. In BusinessObjects Enterprise XI, connections are managed
by the Connection Server. Refer to the Designer online help for more
information on the Connection Server.
You may choose to import all universes and connections, or only those
universes and connections referenced by the performance management
objects (such as dashboards and analytics) that you have selected for import.

Migrating the performance management repository
Each connection you import is stored as an InfoObject in the CMS.

Performance management XI makes use of the BusinessObjects Enterprise
XI standard connection layer. Performance management XI uses the
Connection Server to run the SQL generated by the following performance
management engines:
• Sets
• Process Analysis
• Metrics
• Predictive
Connections are configured in Designer and stored in the CMS. Refer to the
Universe Designer's Guide for more information. The ci_connection table that
stored connection details in previous versions is obsolete in BusinessObjects
Enterprise XI.
Migrating the performance management

repository
After you migrate InfoObjects from the CMS, you migrate the performance
management repository in the Repository Management section of the System
Setup page in performance management setup. Refer to the Performance
Management Setup and Administration online help.
The performance management XI R2 repository includes new columns in the
repository tables to support new features and the new architecture. All
universes are stored as InfoObjects in the CMS.
Changes to the performance management repository include new fields in the
metric table (ci_probe) that store the new metric attributes supported in XI:
• metric description
• metric owner
• last refresh date
New tables are also added to the ci_target table to support goal import.
During the migration process, the Import Wizard verifies that all
BusinessObjects universes on which performance management data relies
are also selected for import.

Migrating schedules 14
Migrating schedules
For performance management in BusinessObjects Enterprise XI R2, all
scheduled tasks are managed by the CMS scheduler. Schedules related to
performance management objects are stored in a dedicated performance
management folder in the Schedule Manager of the CMS.
Migrating rules and named events

For performance management in BusinessObjects Enterprise XI R2, rule
definitions are stored in the performance management repository but are
managed in various locations depending on the event type:
• Scheduled tasks are managed by the CMS scheduler (refer to Migrating
schedules).
• Named events are executed by the Event server and managed in the
Central Management Console. During migration, named events are
mapped to custom events in the CMS. Named events can be referenced
in a rule defined in performance management.
• Events based on the refresh of metrics and other performance
management objects continue to be managed in the performance
management repository.
During migration with the Import Wizard, schedules and named events are
migrated to the destination CMS. Links to these schedules and named events
in rule definitions are updated during migration.
Note: Rules that contain actions requiring the pre-rendering of HTML by the
Broadcast Agent scheduler are migrated, but these types of actions are no
longer supported for performance management XI R2.
Migrating security commands

User rights in BusinessObjects Enterprise XI are managed with Access
Levels (ACLs) in the CMS. Objects must be published in the CMS in order to
be secured individually with ACLs.
To manage ACL rights for performance management users
1. Launch the BusinessObjects Central Management Console.
2. In the Manage menu, select BusinessObjects Applications.
3. Select Performance Management from the list of applications.

Migrating security commands
4. In the Rights tab, click Check User Rights... to display a detailed list of
rights per user or user group, or click Add/Remove to change the rights
currently granted to users or groups.
Managing rights at the object level in performance

management XI
In performance management XI, you can grant rights to specific analytics,
application menus, documents and folders in the Central Management
Console.
Refer to the BusinessObjects Enterprise Administrator’s Guide for more
details on managing object-level security.

Uninstalling
chapter
15 Uninstalling
Uninstalling BusinessObjects Enterprise from UNIX
Uninstalling BusinessObjects Enterprise

from UNIX
To uninstall BusinessObjects Enterprise, run the uninstallBOBJE.sh script.
The uninstallBOBJE.sh script is installed to the bobje directory of your
installation.
This script stops all BusinessObjects Enterprise servers and processes, and
then deletes the files copied from the product CD during your original
installation of BusinessObjects Enterprise.
Installing BusinessObjects Enterprise creates a number of additional files on
your system. The uninstallBOBJE.sh script will not remove the files
created during the installation process, or files created by the system or by
users after installation. The files that remain include log files created by
BusinessObjects Enterprise. These log files can be useful in diagnosing
problems with previous installations.
To remove all BusinessObjects Enterprise files, perform an rm -rf command
on the bobje directory.
If you performed the “system” installation type, you will also need to delete the
run control scripts from the appropriate /etc/rc# directories.

Business Objects
Information Resources
appendix
A Business Objects Information Resources
Documentation and information services
Documentation and information services

Business Objects offers a full documentation set covering its products and
their deployment. Additional support and 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.
What’s in the documentation set?

View or download the Business Objects Documentation Roadmap, available
with the product documentation at http://www.businessobjects.com/support/.
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 from the products

Online help and guides in Adobe PDF format are available from the product
Help menus. Where only online help is provided, the online help file contains
the entire contents of the PDF version of the guide.
Documentation on the web

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

Look in the docs directory of your product CD for versions of guides in Adobe
PDF format.
274BusinessObjects XI Release 2 Installation Guide

Business Objects Information Resources
Customer support, consulting and training A
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://www.businessobjects.com/
support/.
Customer support, consulting and training

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://www.businessobjects.com/support/

Useful addresses at a glance
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
Address Content
Business Objects product Information about the full range of
information Business Objects products.
http://www.businessobjects.com
Product documentation Business Objects product
http://www.businessobjects.com/ documentation, including the
support Business Objects Documentation
Roadmap.
Business Objects Documentation Send us feedback or questions
mailbox about documentation.
documentation@businessobjects.com
Online Customer Support Information on Customer Support
http://www.businessobjects.com/ programs, as well as links to
support/ technical articles, downloads, and
online forums.

Business Objects Information Resources
Useful addresses at a glance A
Address Content
Business Objects Consulting Information on how Business
Services Objects can help maximize your
http://www.businessobjects.com/ business intelligence investment.
services/consulting/
Business Objects Education Information on Business Objects
Services training options and modules.
http://www.businessobjects.com/
services/training


Index
Symbols BusinessObjects documents
@Variable('BOPASS') 209 import limitations 202
@Variable('BOUSER') 209 importing 201
migrating OLAP data providers 202
migration of rights 201
A BusinessObjects Enterprise 5.x/6.x 193
ACEs BusinessObjects SDK
on import of stored procedures 211 Send to BCA 202
on import of universe-related security Send to Inbox 202
commands 208 BusinessObjects, migration of document rights 201
AD authentication, importing from Crystal
Enterprise 191
add-ins, migration 202 C
agnostic documents, importing 203 Categories folder 211
aliases 191 categories,selecting for import 232
Allow user to merge dimension for synchronization ccm.sh 71
right 203 CD
Application Foundation copying to your machine 49
checking universe integrity 195 running the install from 49
migration 188, 193 changing the assigned port number
Application Foundation repository, modification WebSphere 5.1 125
during import 194 WebSphere 6.0 125
associated documents 235 checklist for installation 44
Auditor 24 client tools, installing 63
authentication CMS database
LDAP 191 copying data 254
Windows AD 191 migrate information 254
Automated Process Scheduler 18 on UNIX 36
automated startup on UNIX 56 setting up on UNIX 30
CMS, and Application Foundation objects 194
codepage
B DB2 16
BEA WebLogic 135, 151 UTF-8 16
beginning your installation 50 commands required on UNIX 29
BobjEnterprise115 56 connections
Business Objects BOUSER/BOPASS variables 209
consulting services 276, 277 stored procedures 211
support services 275 connectivities, recreating in XI R2 198
training services 276, 277, 277 consultants, Business Objects 276

Index
context root and access restrictions in XI R2 210

editor 137, 153 Desktop Intelligence 23
WebLogic Builder 136 destination environment, and importing 220
converting destination environments 213
.rep files to .wid 201 development environments 20
copying the product distribution to your machine 49 distributed install
corporate documents, storage after import 201 BusinessObjects Enterprise 58
Crystal Reports Explorer 24 performance management 62
Crystal Reports Explorer,WebSphere 127 document passwords 202
Crystal Server Pages 20 documentation
CSP. See Crystal Server Pages feedback on 275
CSP deprecation 21 on product CD 274
CSV format 239 on the web 274
CUIDs 203 roadmap 274
custom installation 26, 58 documents, importing without locales 204
customer support 275 Domain Key file 214
domains
D importing 211
importing universe domains 208
data sources,creating on destination server
machines 196
database E
permissions 35 Edit SQL right 203
preparing your existing 34 education. See training
database server options 18 enabling servers, with ccm.sh 71
MySQL 19 environement variables
tested database servers 19 DB2 36
database server preparations 34, 54 Sybase 39
database, CMS 30 environment 197
databases commands and utilities 29
supported in XI R2 198 database 30, 36
synchronizing enterprise and database login 28
credentials 209 environment variables
using the DBUSER/DBPASS variables 209 MySQL 43
DB2 30, 36 Oracle 41, 43
DB2 codepages 16 events 192
deploying Expand installation
Oracle 167 on UNIX 57
Sun Java Application Server 178 exporting objects 197
Tomcat 96
WebLogic 135, 151 F
WebSphere 117
Favorites folder 200
deployment environment 20
feedback, on documentation 275
derived universe 208
firewalls 28
Designer
folders, Universe 208
5/6 and XI R2 compatibility 208

Index
FRS, connection storage 207 importing content during an upgrade 264

importing groups from Crystal Enterprise 190
G importing object rights from Crystal Enterprise 192
importing users 212
General Supervisor login 215
importing users, from BusinessObjects Enterprise
groups, importing 229
5.x/6.x 212
importing, Application Foundation 215
I importing, BusinessObjects 5.x source
IBM WebSphere 117 environment 214
Import Groups Option dialog box 230, 230 importing, BusinessObjects 6.x source
Import Progress dialog box 238 environment 214
Import Universe and Connection Objects Options Inbox documents
dialog box 226, 236 storage after import 200
Import Wizard 63 inbox documents
Application Foundation 188, 193 importing 226
how it imports domains 211 mapping Import Wizard to 196
how it imports universe connections 209 information resources 274
mapping to Inbox and personal files 196 install types 25
migrating Application Foundation 194 client tools 63
selecting information 222 custom installation 26
specifying source 213 expand installation 26
specifying source and destination 213, 220 new installation 25
third-party documents 203 silent installation 27
importing installation checklist 44
categories 222, 232 installation logs 84
database credentials 238 installation overview 14
domains 211 installing
folders from Crystal Enterprise 191 client tools 63
from BusinessObjects Enterprise 5.x/6.x 193 on UNIX 48, 50
from Crystal Enterprise 189 SDKs 246
groups 238 install.sh 48, 50
Import Wizard 188 Interactive Editing right 203
instances from Crystal Enterprise 191
mapping Import Wizard to Inbox and personal
J
documents 196
Java application server, installing 72
named events 222
Java components, installing on UNIX 72
profiles 238
java_app_install.sh 72
rights 192
selecting information 222
specifying source and destination 213, 213, L
220 locale
text files 238 and .wqy files 203
users and groups 229 importing documents without locales 204
users with aliases 191 migration of universe 208
users with LDAP authentication 191 locale, setting on UNIX 30

Index
login environment 28 orphan documents, defined 201

logs
installation 84 P
LOVs, access from XI R2 195
passwords, DBUSER/DBPASS variables 209
Perfomance management, distributed install 62
M Performance Manager 23
migrating Personal Categories folder 211
Application Foundation 188, 193 personal documents
BusinessObjects documents 201 importing 226
connections 209 mapping Import Wizard to 196
domains 211 storage after import 200
from BusinessObjects Enterprise 6.x 250 Platform COM SDK 202
from Crystal Enterprise 189, 253 platforms, updating 197
from the Web Component Server 263 Populate Database Credentials for Users dialog
selecting information 222 box 230
specifying source 213 post install deployments 73, 92
specifying source and destination 213, 220 preparing for installation 44
third-party documents 203 preparing your database server 34
migration of document rights 201 Public folder 201
migration, locales 204 Publishing Wizard 48, 63
MySQL 19
R
N .rea files, access from XI R2 195
named events 222 .rep files, migrating 201
new installation 25 reports, importing
from Crystal Enterprise 191
O repositories 196
Repository Migration Wizard 257, 261
object IDs 210
resources 274
objects
.ret files, migration 201
exporting 197
rights
restrictions 210
importing from BusinessObject 5.x or 6.x 196
objects, importing
importing from Crystal Enterprise 192
migration of BusinessObjects document
OLAP Intelligence 22
rights 201
ONAMES 198
row restrictions 210
Online Customer Support 275
optional components 22
Oracle 30, 36 S
configuring classpath 167, 181 scheduled documents, migration 205
deploying 167, 181 scheduling, importing from Crystal Enterprise 191
deploying war files 172, 183 SDK
ONAMES 198 Java 246
setting path environment variable 169 overview 246
TNSNAMES 198 security commands

Index
and WebIntelligence document migration 203 training, on Business Objects products 276
migration of universe-related 208
security, synchronizing credentials 209 U
selecting for import, categories 232
Unicode 30, 32
server communication 16
uninstalling from UNIX 272
server groups, importing from Crystal Enterprise
universe connections see connections
192
universes
server locations 17
checking integrity of those used by Application
servers starting with ccm.sh 71
Foundation objects 195
servers, starting with ccm.sh 71
exclusive overloads 210
setting up server communication 16
importing associated universes 208
firewalls 17
modes of import 208
Sybase 16
overload aggregation 210
Unicode 16
overload collapsing 211
silent install parameters 89
short name 208
silent installation on UNIX 65
the BOUSER/BOPASS variables 209
silent installation on Windows 87
using the DBUSER/DBPASS variables 209
source environment, specifying 213, 213, 220
UNIX
SQL Server, importing connection objects from 5.x/
creating login environment 28
6.x 209
host name requirements 28
Stored Procedures Access right 211
importing Inbox and personal documents 197,
Supervisor, universe access restrictions 210
197
support
network requirements 28
customer 275
required commands and utilities 29
locations 275
setting the locale 30
technical 275
setting up your system 27
web site 275
updating, platforms and versions 197
supported database servers 18
upgrading
Sybase 30, 36
considerations 252
synchronizing, enterprise and database
Crystal Analysis 265
credentials 209
Crystal Reports 264
system installation on UNIX 56
from BusinessObjects Enterprise 6.x 193
system requirements 14
Import Wizard 188
T importing content 264
table mapping 210 overview 250
technical support 275 Report Application Server 264
Testing MySQL database environment variables upgrading from BusinessObjects 5.x 250
43 upgrading from BusinessObjects 6.x 250
text file delimiter 239 User vs. system installation 25
text file format 239 users, importing 229
text file separator 239 users, importing from Crystal Enterprise 190
third-party documents, importing 203 UTF-8 16
TNSNAMES 198
Tomcat 96

Index
V .wqy files, locale 203

VBA macros migration 195
verifying Java web applications 74
version 5.x/6.x, inbox and personal storage 196
version XI R2
access restrictions 210
supported connectivities 198
W
was 21
WCA
deploying on Windows 172, 183
installing multiple 75
installing on UNIX 72
WCS, migrating from 263
web
customer support 275
getting documentation via 274
useful addresses 276
web application servers 21
Web Component Adapter 22
web development environments 20
Web Intelligence
Allow user to merge dimension for
synchronization right 203
Edit SQL right 203
Interactive Editing right 203
web servers 21, 21
web sites
support 275
training 276
WebConnect documents, access from XI R2 194
WebIntelligence documents
migration limitations 203
rights migration 203
WebIntelligence, migrating orphan documents 201
WebSphere deployment 114, 114
.wid files, migrating orphan documents 201
Windows
client tools installation 63
Import Wizard 63
Publishing Wizard 63
silent installation 87

Xir2 Bip Install Unix en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Xir2 Bip Install Unix en

Uploaded by

Copyright:

Available Formats

BusinessObjects Enterprise™ XI

Release 2 Installation Guide

BusinessObjects Enterprise XI Release 2 Productivity Pack

Copyright Copyright © 2006 Business Objects. All rights reserved.

Chapter 2 Planning Your Installation 13

BusinessObjects XI Release 2 Installation Guide 3

Chapter 3 Installing BusinessObjects Enterprise on UNIX 47

4 BusinessObjects XI Release 2 Installation Guide

Finishing a system installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 4 Installing the Productivity Pack 81

Chapter 5 Deploying on Tomcat 95

Chapter 6 Deploying on Tomcat with the JDK 1.5 103

5 BusinessObjects XI Release 2 Installation Guide

Using a version of Tomcat already running BusinessObjects Enterprise .

Chapter 7 Deploying on WebSphere 113

Chapter 8 Deploying on WebLogic 131

6 BusinessObjects XI Release 2 Installation Guide

Creating the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Chapter 9 Deploying on WebLogic 9.2 with the JDK 1.5 147

Chapter 10 Deploying on Oracle Application Server 163

7 BusinessObjects XI Release 2 Installation Guide

Changing the command line options for OLAP Intelligence or performance

Chapter 11 Deploying on Sun Java Application Server 177

Chapter 12 Importing Objects to BusinessObjects Enterprise 187

8 BusinessObjects XI Release 2 Installation Guide

Finalizing the import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Chapter 13 Custom SDK Deployments 245

Chapter 14 Upgrading and Migrating 249

Chapter 15 Uninstalling 271

Appendix A Business Objects Information Resources 273

BusinessObjects XI Release 2 Installation Guide 9

What’s in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

10 BusinessObjects XI Release 2 Installation Guide

What is BusinessObjects Enterprise?

About this guide

Who should read this guide

Business Objects information resources

12 BusinessObjects XI Release 2 Installation Guide

14 BusinessObjects XI Release 2 Installation Guide

BusinessObjects XI Release 2 Installation Guide 15

Setting up server communication

16 BusinessObjects XI Release 2 Installation Guide

Choosing a server location

BusinessObjects XI Release 2 Installation Guide 17

Choosing a database server

18 BusinessObjects XI Release 2 Installation Guide

Using a supported database server

Sourcing the script that identifies the database environment variables

BusinessObjects XI Release 2 Installation Guide 19

• To source the BusinessObjects Enterprise environment script, you would

Shell name source . (dot operator)

Choosing a deployment environment

Choosing a development environment

20 BusinessObjects XI Release 2 Installation Guide

Choosing an environment for new custom applications

Choosing a web application server

BusinessObjects XI Release 2 Installation Guide 21

Choosing a Web Component Adapter

Choosing optional components

22 BusinessObjects XI Release 2 Installation Guide

BusinessObjects XI Release 2 Installation Guide 23

Crystal Reports Explorer