BO Enterprise - Installation Guide (Short)

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

contributors

Business Objects products in this release may contain redistributions of software licensed

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

BusinessObjects Enterprise XI Release 2 Installation Guide 3

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

Windows permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting up server communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Choosing a server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Choosing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using a supported database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Choosing a deployment environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Choosing a development environment . . . . . . . . . . . . . . . . . . . . . . . . 19

Choosing a web application server . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Choosing a Web Component Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 21

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 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Choosing an install type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Contents

4 BusinessObjects Enterprise XI Release 2 Installation Guide

New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Upgrade installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

DB2 database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Sybase database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Oracle database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 31

MySQL database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Preparing your existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3 Installing BusinessObjects Enterprise on Windows 35

Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Setting up the CMS database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Providing administrative privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing Business Objects products on a non-system drive . . . . . . . . . . . 41

New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Expanded installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Client tools installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Installing client tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Data Access and Output Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Sample Reports and Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Selecting or deselecting features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Distributed deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Installing only the server and client components . . . . . . . . . . . . . . . . . 67

Installing only the Web Component Adapter . . . . . . . . . . . . . . . . . . . . . 74

Contents


Adding Crystal Enterprise 10 web desktop support . . . . . . . . . . . . . . . 77

Running a custom install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Upgrade installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Silent install parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Verifying your performance management installation . . . . . . . . . . . . 103

Post installation setup for performance management . . . . . . . . . . . . 105

Troubleshooting starting performance management . . . . . . . . . . . . . 105

Chapter 4 Installing Service Pack 2 109

Service Pack 2 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Installing Service Pack 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 5 Installing the Productivity Pack 111

Productivity Pack upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

What is included in the productivity pack? . . . . . . . . . . . . . . . . . . . . . 112

Business Process BI Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Content Search in InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Distributed installs of Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Feature selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Silent install parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

New or updated WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chapter 6 Deploying on Tomcat 127

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Deploying with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 7 Deploying on WebSphere 137

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 138

Contents


Deploying on IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Creating an application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Starting the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Making configuration changes for distributed performance management

143

Changing the classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Setting the heap size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Modifying the PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Checking or changing the assigned port number on WebSphere 5.1 . 147

Checking or changing the assigned port number on WebSphere 6.0 . 147

Creating a new virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Assigning an alias to the virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Verifying the WebSphere Configuration . . . . . . . . . . . . . . . . . . . . . . . 150

Chapter 8 Deploying on WebLogic 153

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154


Deploying on BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Copying your performance management InitConfig. properties file . . 159

Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 159

Creating the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Changing the CLASSPATH in WebLogic . . . . . . . . . . . . . . . . . . . . . . 161


Setting the Java Virtual Machine options for OLAP Intelligence and

performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 164

Chapter 9 Deploying on Oracle Application Server 167

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168


Deploying with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Contents


Configuring the Class Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Changing Memory Allocation Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Copying your performance management InitConfig. properties file . . 173

Setting the PATH environment variable . . . . . . . . . . . . . . . . . . . . . . . 173

Changing the command line options for OLAP Intelligence or performance

management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 175

Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Verifying the Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 10 Deploying on SAP Web Application Server 179

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

WAR file contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 181

Deploying with SAP Web Application Server . . . . . . . . . . . . . . . . . . . . . . 183


Creating an EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Deploying the EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Verifying the Web Application Server Configuration . . . . . . . . . . . . . 187

Chapter 11 Importing Objects to BusinessObjects Enterprise 189

Importing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Importing information from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . 191

Importing objects from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . 192

Importing information from BusinessObjects 5.x or 6.x . . . . . . . . . . . . . . 195

Importing Application Foundation objects . . . . . . . . . . . . . . . . . . . . . 195

Limitations on importing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Before importing from Application Foundation . . . . . . . . . . . . . . . . . . 197

Before importing from BusinessObjects 5.x/6.x . . . . . . . . . . . . . . . . . 198

Importing objects from BusinessObjects 5.x/6.x . . . . . . . . . . . . . . . . 201

Using the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Specifying the source environment . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Specifying the destination environment . . . . . . . . . . . . . . . . . . . . . . . 223

Selecting the type of objects to import . . . . . . . . . . . . . . . . . . . . . . . . 225

Contents


Choosing an import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Updating previously imported objects . . . . . . . . . . . . . . . . . . . . . . . . . 231

Selecting specific objects to import . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Finalizing the import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Using text files with the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Text file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Importing from text files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Chapter 12 Custom SDK Deployments 249

Software Development Kit overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Active Server Pages environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Java Server Pages environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

.NET environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Chapter 13 Upgrading and Migrating 253

What does this section cover? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

What this section does not cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Upgrading from Crystal Enterprise or from BusinessObjects Enterprise . 254

Preparing for upgrading or migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Disabling and stopping servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Upgrading previous version’s components . . . . . . . . . . . . . . . . . . . . . 258

Migrating the CMS or APS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Using an existing web desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Importing content from BusinessObjects Enterprise, Crystal Enterprise, or

Crystal Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Upgrading other components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Migrating to performance management XI Release 2 . . . . . . . . . . . . . . . . 272

About the Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Migrating the performance management repository . . . . . . . . . . . . . . . . . 273

Migrating schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Migrating rules and named events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Migrating security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Managing rights at the object level in Performance Management XI . 275

Contents


Chapter 14 Uninstalling 277

Uninstalling BusinessObjects Enterprise from Windows . . . . . . . . . . . . . 278

Appendix A Deploying on WebLogic 9.2 with the JDK 1.5 279

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280


Deploying on BEA WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Creating a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Deploying performance management . . . . . . . . . . . . . . . . . . . . . . . . 285

Setting the Java Virtual Machine options for OLAP Intelligence and

performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Setting required variables in startup script . . . . . . . . . . . . . . . . . . . . . 287

Changing the default parser and transformer . . . . . . . . . . . . . . . . . . 289

Adjusting the size of the JVM permanent generation . . . . . . . . . . . . 289


Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . 292

Appendix B Deploying on Tomcat with the JDK 1.5 293

Modifying Tomcat to use JDK 1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Using a version of Tomcat already running BusinessObjects Enterprise

294

Copying the required Jar file to Tomcat . . . . . . . . . . . . . . . . . . . . . . . 296

Adding the Java Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297


Verifying the Tomcat deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Appendix C Business Objects Information Resources 301

Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . 302

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

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

Where is the documentation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Send us your feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . 303

Contents


How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Looking for the best deployment solution for your company? . . . . . . . 304

Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Index 307

chapter

Introduction to

BusinessObjects Enterprise XI

Release 2


Introduction to BusinessObjects Enterprise XI Release 2

What is BusinessObjects Enterprise?3

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.

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 C: Business Objects

Information Resources. This appendix describes the Business Objects

documentation, customer support, training, and consulting services, with links

to online resources.

chapter

Planning Your Installation



Installation overview4

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:

• Java application server (unless you install Tomcat with your installation of

BusinessObjects Enterprise)



Setting up server communication 4

• 512 MB RAM minimum, 1 GB recommended

• 3 GB free disk space

• Database software that is compatible with the CMS and the Audit

database (unless you install MySQL during the BusinessObjects

Enterprise installation)

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,

release.htm, or release.rtf).

Note:

• BusinessObjects Enterprise requires a database to store information

about the system and its users. For details, see “Database requirements”

on page 29 and “Preparing your existing database server” on page 31.

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

Windows permissions

To successfully install BusinessObjects Enterprise on Windows, the user who

runs the setup program must be a member of the local Administrators group.

The following are not supported:

• Installing on a domain controller.

• Installing on a machine where the Windows default security settings

given to the local Administrators group have been modified.

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.



Setting up server communication4

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.

• 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 locale.dat file.

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 your existing web application server does not install 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 4

Choosing a server location

When planning your BusinessObjects Enterprise installation, you should also

consider where you will place 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 speed 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.

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 server location4

• See “International deployments” for information on how to deploy

BusinessObjects Enterprise for a multilingual, worldwide audience.

• On Windows, you can choose to install all BusinessObjects Enterprise

components on a drive other than the drive that contains your operating

system files. For details, see “Installing Business Objects products on a

non-system drive” on page 41.

Choosing a database server

BusinessObjects Enterprise requires a database (or Oracle schema) 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 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 tested database servers, see the platforms.txt

file included with your product distribution.

Using MySQL

MySQL database server is an open-source database that provides local data

storage. The setup program can install and 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 engine. During the installation of BusinessObjects

Enterprise, you specify what database server you will use and enter the

required parameters for authentication.



Choosing a deployment environment 4

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 tested database servers, see the platforms.txt file

included with your product distribution. If you do not have a database engine

installed on your machine you can use MySQL for your CMS database.

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 which Web Component Adapter to use.

• 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

BusinessObjects Enterprise supports Active Server Pages (ASP), Java

Server Pages (JSP) and .NET applications (ASP.NET). Support for Crystal

Server Pages (CSP) was deprecated on the Windows platform in

BusinessObjects Enterprise XI. (CSP was deprecated on UNIX platforms in

the Crystal Enterprise 10 release.)

Note: The following section applies to Crystal Enterprise 10 users only.

In the period since CSP was developed, the cross-platform application server

market has become dominated by the Java Platform, Enterprise Edition

(J2EE) platform and Microsoft’s ASP.NET. As a result, Business Objects has

moved away from the proprietary CSP language and has instead developed

tools and applications in ASP.NET and J2EE.

What does deprecating CSP mean?

• Existing CSP applications will continue to run on Windows (after making

minor configuration changes).



Choosing a deployment environment4

• 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 or ASP.NET.

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. Here are some directions to consider:

• Windows platform, IIS web server

Consider developing new applications using ASP.NET. (You could also

develop new applications in ASP; however, Microsoft is gradually

deprecating ASP.)

• Windows platform, any supported J2EE web application server

You may want to consider developing new applications using J2EE.

If you have an existing custom application that is a slightly modified version of

InfoView (or another application supplied by Business Objects), you may want

to apply your changes to an updated version of the application. J2EE and

ASP.NET versions of InfoView are available in BusinessObjects Enterprise XI.

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.

BusinessObjects Enterprise also includes Primary Interop Assemblies (PIAs)

that enable you to use the BusinessObjects Enterprise SDK and Report

Application Server SDK with ASP.NET It also includes a set of .NET Server

Components which simplify development of custom BusinessObjects

Enterprise applications in ASP.NET.

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 deployment environment 4

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.

Note: The term web application server refers to a web server and an

application server.

Depending upon your needs, you can use one of these options:

• Microsoft Internet Information Server (IIS)

If you plan to develop custom applications using ASP or ASP.NET, you

should use IIS.

Note: This option is not available on UNIX.

• Java web application servers

If you install BusinessObjects Enterprise on Windows and plan to

develop custom applications using JSP, you can use any of the

supported web servers listed in the Platforms.txt file that is included

with your product distribution.If you plan to develop custom applications

using the BusinessObjects Enterprise Java SDK, you can use any of the

supported Windows web servers listed in the Platforms.txt file that is

included with your product distribution.

Note: We recommend that you use ASP, ASP.NET, or JSP for new custom

applications, although development of new custom applications in CSP is still

supported in BusinessObjects Enterprise XI. For details, see “Choosing an

environment for new custom applications” on page 20.

Choosing a Web Component Adapter

BusinessObjects Enterprise provides a web application—the Web

Component Adapter (WCA) —that allows your web application server to run

BusinessObjects Enterprise 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.



Choosing optional components4

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

There are two versions of the Web Component Adapter:

• .NET

The .NET Web Component Adapter must be installed on an IIS web

application server.

• Java

The Java Web Component Adapter must be installed on a J2EE web

application server.

Choosing optional components

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.

OLAP Intelligence supports the market leading OLAP servers including:

Microsoft SQL Server Analysis Services, Hyperion Essbase, SAP Business

Information Warehouse (BW), and IBM DB2 OLAP Server.



Choosing optional components 4

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 BusinessObjects in release 5.x/

6.x. Desktop Intelligence is now installed as part of the client install for

BusinessObjects Enterprise. It is no longer 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

BusinessObjects Enterprise installation.

Note:

• Performance management products are only available as Java web

applications. There are no corresponding products available for .NET.



Choosing optional components4

• 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 Services

Business Process BI Services 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 Services Guide for more

information.



Choosing an install type 4

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

• Upgrade installation

• Silent installation

The first few choices use the installation wizard to guide you through the

installation process. The Silent Installation is done from the command line.

Note: Regardless of how you conduct your installation, when the option of

different versions exists, you will be given the choice of installing the .NET, the

JAVA or both versions of a component.

New installation

Performing a new installation is the most simple way to deploy

BusinessObjects Enterprise because all the required client, server, and

optional components are installed by default onto one machine.

You may want to choose a new installation if:

• You have not installed BusinessObjects Enterprise before.

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

• You don’t want to choose exactly which components you want installed.

• 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



Choosing an install type4

BusinessObjects Enterprise server components can run on the same

machine. Note that 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 Administrator’s Guide for information on planning how to best

expand your installation to meet the needs of your organization. See “Expand

installation” on page 52 for detailed instructions on how to accomplish your

expand installation.

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 done on the machine

where the all BusinessObjects Enterprise components except the Web

Component Adapter will reside, see “Installing only the server and client

components” on page 67 for more information.The second step is done on

the machine where the web server is installed, see “Installing only the Web

Component Adapter” on page 74 for more information.

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 specific 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 are not



Choosing an install type 4

familiar with specific BusinessObjects Enterprise components and their roles

and you do a custom install, you may inadvertently not install a required

component.

Note: If you have an existing Crystal Enterprise 10 web desktop that you

want to continue using with BusinessObjects Enterprise XI, you must install

an extra feature to support the older web application. For more information,

see “Adding Crystal Enterprise 10 web desktop support” on page 77.

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.

The silent installation is not recommended for custom or upgrade

installations. The installation options are simplified and do not allow for the

same level of customization that is provided in the BusinessObjects

Enterprise Setup program. Silent installations are also not recommended for

upgrades. For more information on performing a silent installation on

Windows, see “Silent installation” on page 91.



Choosing an install type4

Upgrade installation

If you have an existing installation of Crystal Enterprise 9 or 10, or

BusinessObjects Enterprise XI R1, and you performed a full standalone client

or server installation of your product, you can upgrade your system to

BusinessObjects Enterprise XI R2 directly with the install program. This

process will not upgrade your original CMS; This step must be completed

after you upgrade your system, see “Upgrading and Migrating” on page 253.

If you cannot upgrade your system because you did not perform a full

standalone client install, you will need to uninstall the old components before

performing an install.

A full standalone server install means during the initial install, you installed the

complete feature set onto one machine. This includes all the client

components, the server components, the SDKs and either the Java or the

.NET Web Component Adapter or Web Component Server. A full standalone

client install means you installed all of the client components onto one

machine.

Note: If either the full client or server set is not detected, you will receive a

message informing you that you must uninstall the previous version before

you proceed with your install.

After you enter the product keycode for your new install, the installation

program will detect that you have a previous version installed. You will receive

a message that informs you a previous version has been detected and that an

upgrade will be performed. The installation program will find the existing

versions, replace them with the new BusinessObjects Enterprise XI R2

components and add components new to this release.

After you upgrade your installation, you will need to migrate your system data

to the new version, and import content from an earlier version of Crystal

Enterprise, Crystal Info, or BusinessObjects Enterprise.

• Upgrading consists of replacing existing Crystal Enterprise programs and

files with the latest BusinessObjects Enterprise versions.

• Copying the contents of the original input root directory into the root

directory that the new Input File Repository Server is already configured

to use, or reconfiguring the new Input and Output File Repository Servers

to use the old input and output root directories.

• Migrating consists of copying data from your old CMS or Automated

Process Scheduler (APS) database to a new Central Management

Server (CMS) database, while at the same time updating the database

schema to the latest version.



Database requirements 4

Note: Do not attempt to use your BusinessObjects Enterprise XI R1

CMS to host your BusinessObjects Enterprise R2 deployment. This will

result in the destruction of your existing content.

• Importing consists of copying selected objects (reports, users, groups,

and so on) and instances from one system to another.

For more information on migrating from Crystal Enterprise 9 or 10, or

BusinessObjects Enterprise XI R1, see “Upgrading and Migrating” on

page 253. This guide does not cover describes 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 BusinessObjects 5.x to XI

Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2

Migration Guide.

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

planning or execution of the upgrade or migration.

• “MySQL database setup requirements” on page 31

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

“Upgrading and Migrating” on page 253 for details.

•

Database requirements

Before you create the database that you want to integrate with

BusinessObjects Enterprise, consider the following sections that detail what

settings are required when the database is created and what settings you

should test before beginning your BusinessObjects Enterprise install.



Database requirements4

DB2 database setup requirements

If you are using a DB2 database with your BusinessObjects Enterprise

deployment, there are specific settings you need to select when the database

is created. It is not sufficient to modify these settings after the database has

been created.

When you create the database you will use with BusinessObjects Enterprise:

• Ensure the CMS database is not partitioned.

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

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.

Documents

BO Enterprise - Installation Guide (Short)