xir2 bip install en

7/21/2019 Xir2 Bip Install En

1/312

BusinessObjects Enterprise XI

Release 2 Installation Guide

BusinessObjects Enterprise XI Release 2 Productivity Pack

Windows


2/312

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


3/312

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


4/312

Contents

4 BusinessObjects Enterprise XI Release 2 Installation Guide

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

Expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Custom 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installation 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Expanded 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


5/312

Contents


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

Running a custom install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Upgrade 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 109Service 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Distributed 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Deploying with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 7 Deploying on WebSphere 137

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

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


6/312

Contents


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

Creating an application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Starting the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Making configuration changes for distributed performance management143

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Assigning 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Copying 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 andperformance 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


7/312

Contents


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

Changing Memory Allocation Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Copying your performance management InitConfig. properties file . . 173

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

Changing the command line options for OLAP Intelligence or performancemanagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . 201Using the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

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

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

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


8/312

Contents


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

Updating previously imported objects . . . . . . . . . . . . . . . . . . . . . . . . . 231Selecting 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Java 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257Disabling and stopping servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Upgrading previous versions components . . . . . . . . . . . . . . . . . . . . . 258

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

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

Importing content from BusinessObjects Enterprise, Crystal Enterprise, orCrystal Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

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

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

About the Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Migrating 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


9/312

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 andperformance 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Using a version of Tomcat already running BusinessObjects Enterprise294

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

Whats in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

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

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

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


10/312

Contents


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

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

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

Index 307


11/312

c h a p t e r

Introduction to

BusinessObjects Enterprise XI

Release 2


12/312


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 applicationintranet, extranet, Internet or corporate portal. Whether it is used fordistributing weekly sales reports, providing customers with personalizedservice offerings, or integrating critical information into corporate portals,BusinessObjects Enterprise delivers tangible benefits that extend across andbeyond the organization. As an integrated suite for reporting, analysis, andinformation delivery, BusinessObjects Enterprise provides a solution forincreasing end-user productivity and reducing administrative efforts.

About this guide

This guide provides you with information and procedures for installingBusinessObjects Enterprise. This guide also includes detailed instructions forthe different installation modes available.

Who should read this guide

This guide is intended for the system administrator or IT professional whoneeds to install BusinessObjects Enterprise. Familiarity with your overallnetwork environment, port usage, your database environment, and your web

server software is especially beneficial.For more information about the product, consult the BusinessObjectsEnterprise Administrators Guide, the BusinessObjects Enterprise GettingStarted Guide, and the BusinessObjects Enterprise Users Guide. Onlineversions of these guides are included in the docsdirectory of your productdistribution. Once you install BusinessObjects Enterprise, they are alsoaccessible from InfoView, BusinessObjects Enterprises web-based interface.

Business Objects information resources

For more information and assistance, seeAppendix C: Business ObjectsInformation Resources.This appendix describes the Business Objectsdocumentation, customer support, training, and consulting services, with linksto online resources.


13/312

c h a p t e r

Planning Your Installation


14/312



Installation overview4

Installation overview

BusinessObjects Enterprise provides an open and flexible architecture that

supports a multitude of deployment and configuration scenarios. Before youinstall BusinessObjects Enterprise you should:

Review your system to ensure that it meets the basic requirements for aBusinessObjects Enterprise installation.

Ensure that all machines that will be part of your BusinessObjectsEnterprise deployment can communicate properly with one another.

Decide which BusinessObjects Enterprise components to install andwhich 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 infrastructureand details considerations you should consider when you set up yourenvironment. Preparations should include:

Setting up server communication Choosing a server location

The other parts of this section list the core software requirements, the choicesavailable to you within the core requirements, and the install methods that youcan 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 usethis checklist to help ensure you are prepared before you begin your install ofBusinessObjects Enterprise.

System requirements

Generally, the following components must be installed and configuredcorrectly before you install BusinessObjects Enterprise:

Java application server (unless you install Tomcat with your installation ofBusinessObjects Enterprise)


15/312



Setting up server communication4

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 BusinessObjectsEnterprise installation)

For a detailed list of supported environments, consult the Platforms.txtfileincluded with your product distribution. This file includes specific version andpatch-level requirements for web application servers, web browsers, andoperating systems. For additional important information that may pertain toyour deployment, it is also strongly recommended that you consult theRelease Notesincluded with your product distribution (release.pdf,release.htm, or release.rtf).

Note:

BusinessObjects Enterprise requires a database to store informationabout the system and its users. For details, see Database requirementson page 29and Preparing your existing database server on page 31.

If you are installing on VMWare, ensure your machine name does notinclude any of the following characters: an underscore, a period, or aslash.

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 toinstall this software during your installation, or use other supported third-partysoftware. If you choose to use supported third-party database or webapplication server software, it should be installed before you installBusinessObjects Enterprise. After you complete your install, you will alsoneed to configure the software so it integrates with BusinessObjectsEnterprise.


16/312



Setting up server communication4

In addition, ensure that all BusinessObjects Enterprise machines cancommunicate properly with one another:

Each BusinessObjects Enterprise machine must be able to communicateover TCP/IP with the machine that runs your Central Management Server(CMS).

The CMS is responsible for maintaining a database of information aboutyour BusinessObjects Enterprise system, which other components canaccess as required. The data stored by the CMS includes informationabout users and groups, security levels, BusinessObjects Enterprisecontent, and servers. For more information about the CMS, seeBusinessObjects Enterprise Administrators Guide.

Ensure that your database client and server are set up to use Unicodecharacter encoding (such as UTF-8). Consult your databasedocumentation 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 DB2CODEPAGEvalue of 1208. The Sybasedatabase client typically requires the parameter LC_ALLand anappropriate entry in the locale.datfile.

When you install your database server, such as Oracle and Sybase, youneed to configure the server to use Unicode encoding for the characterdata types. For other databases, such as DB2, you can create the CMSdatabase 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 allBusinessObjects Enterprise machines.This communication is enabled bythe BusinessObjects Enterprise Software Development Kit (SDK), whichis 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 theJava Development Kit (JDK) supported by BusinessObjects Enterprise,you will need to install it.

Note: If you are installing BusinessObjects Enterprise in a firewallenvironment, you will need additional configuration details. See the

Working with Firewalls section of the BusinessObjects EnterpriseAdministrators Guide.


17/312



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, andReport Application Server communicate frequently with the databaseservers containing the data in your published reports. To speed dataretrieval and minimize network traffic, place your processing serversclose to your database servers (ideally, on the same subnet). If yourBusinessObjects Enterprise installation is distributed over a widegeographic region, use server groups to create groups of nearby serversto process reports.

The Central Management Server (CMS) stores data about users andgroups, security levels, published objects, and servers in the CMSdatabase. The CMS can also maintain a separate audit database ofinformation about user actions. To optimize CMS performance, placeyour CMS on the same LAN as the database servers that host your CMSdatabase 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 samelatency to the system database.

Note: This guide does not cover how to cluster a CMS. For details onhow to configure a CMS cluster after your initial installation, see these

sections in the BusinessObjects Enterprise Deployment andConfiguration 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 Serverssection of theBusinessObjects Enterprise Deployment and ConfigurationGuidefor information on other factors that you may want to consider inplanning your BusinessObjects Enterprise installation:

See Working with firewalls for information on how to configureBusinessObjects 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 anddistribute reports that meet the needs of people with disabilities.


18/312



Choosing a server location4

See International deployments for information on how to deployBusinessObjects 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 operatingsystem files. For details, see Installing Business Objects products on anon-system drive on page 41.

Choosing a database server

BusinessObjects Enterprise requires a database (or Oracle schema) to storeinformation about the system and its users. The primary database, which ismaintained by the Central Management Server (CMS), is known as the CMSdatabase. A second database will be required if you plan to useBusinessObjects Enterprise Auditor. Before you install, you should choose

which supported database server to use.

Note:

In earlier releases of Crystal Enterprise, the Central Management Serverwas called the Crystal Management Server or the Automated ProcessScheduler (APS), and the system database was called the APSdatabase.

In earlier releases of BusinessObjects, the system database was knownas the repository. For more information, see theBusinessObjects 5.x toXI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2Migration Guide.

For a detailed list of tested database servers, see the platforms.txtfile included with your product distribution.

Using MySQL

MySQL database server is an open-source database that provides local datastorage. The setup program can install and configure MySQL along with yourBusinessObjects Enterprise components. If you already have MySQLinstalled, the installation program creates the CMS database using yourexisting database engine. During the installation of BusinessObjectsEnterprise, you specify what database server you will use and enter therequired parameters for authentication.


19/312



Choosing a deployment environment4

Using a supported database server

The CMS supports a number of third-party database servers, so you canconnect BusinessObjects Enterprise to your existing database infrastructure.For a detailed list of tested database servers, see the platforms.txtfileincluded with your product distribution. If you do not have a database engineinstalled on your machine you can use MySQL for your CMS database.

Choosing a deployment environment

Before installing BusinessObjects Enterprise, you should determine in whichenvironment you want to deploy BusinessObjects Enterprise so you knowwhat 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 theoptions available when you install.

Choosing a development environment

BusinessObjects Enterprise supports Active Server Pages (ASP), JavaServer Pages (JSP) and .NET applications (ASP.NET). Support for CrystalServer Pages (CSP) was deprecated on the Windows platform inBusinessObjects Enterprise XI. (CSP was deprecated on UNIX platforms inthe 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 servermarket has become dominated by the Java Platform, Enterprise Edition(J2EE) platform and Microsofts ASP.NET. As a result, Business Objects has

moved away from the proprietary CSP language and has instead developedtools and applications in ASP.NET and J2EE.

What does deprecating CSP mean?

Existing CSP applications will continue to run on Windows (after makingminor configuration changes).


20/312




New BusinessObjects Enterprise features will not be made available inCSP.

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 BusinessObjects Global Services.

Choosing an environment for new custom applications

While it will be possible to run CSP applications after CSP has beendeprecated, you should not develop new custom CSP applications on thatplatform. Here are some directions to consider:

Windows platform, IIS web server

Consider developing new applications using ASP.NET. (You could alsodevelop new applications in ASP; however, Microsoft is graduallydeprecating 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 ofInfoView (or another application supplied by Business Objects), you may wantto 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 applicationsthat use BusinessObjects Enterprise objects in conjunction with your owncustom 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 ServerComponents which simplify development of custom BusinessObjectsEnterprise applications in ASP.NET.

Your choice of which web development environment to use to develop yourown custom applications will depend largely on your own technology

preferences. However, in making this decision, consider the technologydirections foreseen by Business Objects.


21/312




Choosing a web application server

BusinessObjects Enterprise requires a web application server to process theserver-side scripts that make up web applications. Before selecting a webapplication server to use with BusinessObjects Enterprise, assess yourcurrent environment and determine the platform on which to deployBusinessObjects Enterprise. Determine whether you plan to develop customapplications and, if so, which web development environment to use.

Note: The term web application server refers to a web server and anapplication 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 todevelop custom applications using JSP, you can use any of thesupported web servers listed in the Platforms.txtfile that is includedwith your product distribution.If you plan to develop custom applicationsusing the BusinessObjects Enterprise Java SDK, you can use any of thesupported Windows web servers listed in the Platforms.txtfile that isincluded with your product distribution.

Note: We recommend that you use ASP, ASP.NET, or JSP for new customapplications, although development of new custom applications in CSP is stillsupported in BusinessObjects Enterprise XI. For details, see Choosing anenvironment for new custom applications on page 20.

Choosing a Web Component Adapter

BusinessObjects Enterprise provides a web applicationthe WebComponent Adapter (WCA) that allows your web application server to runBusinessObjects Enterprise applications and to host the Central ManagementConsole (CMC). If you want to run the CMC supplied with BusinessObjectsEnterprise or run legacy CSP applications, the WCA must be installed on thesame machine as your web application server. OLAP Intelligence alsorequires the installation of the WCA.


22/312



Choosing optional components4

Note: The Web Connector that resided on the web server in earlier versionsof Crystal Enterprise is no longer required. Requests are now handled by theweb 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 webapplication server.

Java

The Java Web Component Adapter must be installed on a J2EE webapplication server.

Choosing optional components

Provided that you own the appropriate licenses to the applicable BusinessObjects products, the following may be installed with BusinessObjectsEnterprise XI: OLAP Intelligence, Desktop Intelligence (formerly known asBusinessObjects), performance management, Crystal Reports Explorer, WebIntelligence and BusinessObjects Enterprise Auditor. For information aboutlicenses, contact your Business Objects sales representative.

For a list of all available components, see the BusinessObjects Enterprise

Architecture section in the BusinessObjects Enterprise AdministratorsGuide.

OLAP Intelligence

OLAP Intelligence leverages the power of multidimensional OLAP databasesto help organizations gain insight and uncover hidden trends in their complexbusiness data. OLAP Intelligences easy-to-use drag-and-drop environmentand rich visualization techniques enable users to build and modify analysis-focused Worksheets and create customizable charts that graphicallyrepresent the data in workbooks. Through its tight integration withBusinessObjects Enterprise, OLAP Intelligence workbooks can be viewedthrough an intranet, extranet, or corporate portal. Alternatively, they can bepublished to BusinessObjects Enterprise.

OLAP Intelligence supports the market leading OLAP servers including:Microsoft SQL Server Analysis Services, Hyperion Essbase, SAP BusinessInformation Warehouse (BW), and IBM DB2 OLAP Server.


23/312



Choosing optional components 4

Desktop Intelligence

Desktop Intelligence is an integrated query, reporting, and analysis solutionfor business professionals that allows users to access data in their corporatedatabases directly from their desktops. Desktop Intelligence makes it easy toaccess this data, because users work with it in the business terms that arefamiliar to them; they dont require knowledge of technical database termslike 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 forBusinessObjects Enterprise. It is no longer downloaded from InfoView.

Performance management

Performance management can be applied to any business process wherethere is a need to view and analyze all the points of measure that definecorporate performance, productivity and profitability.

Performance management products help users track and analyze keybusiness metrics via management dashboards, scorecards, and alerting.These products also allow goals to be set around metrics, and assigned toownersaligning people with strategies. These products also support groupdecision making and analysis via integrated collaboration and workflowcapabilities.

Performance management allows groups to collaborate and make goal and

metric based decisions. Once a decision is reached, users can establish andreuse decision and analysis workflow so others can efficiently analyze andresolve 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 yourBusinessObjects Enterprise installation.

Note:

Performance management products are only available as Java webapplications. There are no corresponding products available for .NET.


24/312



Choosing optional components4

Performance management was previously known as ApplicationFoundation. Process Analysis was previously known as StatisticalProcess Control (SPC).

Auditor

Auditor is a web-based product that allows you to monitor and analyze userand system activity. This information provides valuable insight into yourBusinessObjects Enterprise deployment, enabling you to optimize yourdeployment.

If you choose to use Auditor, you can choose to configure auditor during orafter the installation. For details on how to configure Auditor after theinstallation completes, see the BusinessObjects Enterprise Auditors guide.

Crystal Reports Explorer

Crystal Reports Explorer allows users to create and modify reports, designlayouts, and perform data analysis using a zero-client interface. Thisfunctionality 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 andflexible user interface for building and analyzing reports on corporate dataover the web, on secured intranets and extranets.

Business Process BI Services

Business Process BI Services is a high-level web service designed to helpalign an organizations BI investments with the everyday running of itsbusiness. Business Process BI Service will help an organization effectivelystreamline business intelligence delivery, automate data refreshes andintegrate Business Objects Enterprise administration directly into common ITprocesses. See the Business Process BI Services Guide for moreinformation.


25/312



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 aclient or a server installation. When you perform a client install, only the clientcomponents are installed; when you perform a server install, boththe clientand server components are installed.

The second step is to choose the install method. BusinessObjects Enterpriseoffers these choices.

New installation

Expand installation

Custom installation Upgrade installation Silent installation

The first few choices use the installation wizard to guide you through theinstallation process. The Silent Installation is done from the command line.

Note: Regardless of how you conduct your installation, when the option ofdifferent versions exists, you will be given the choice of installing the .NET, theJAVA or both versions of a component.

New installation

Performing a new installation is the most simple way to deployBusinessObjects Enterprise because all the required client, server, andoptional 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 dont want to choose exactly which components you want installed. You dont have stringent disk space limitations.

Expand installation

In large or mission-critical deployments of BusinessObjects Enterprise, youcan scale your system to handle increased usage or to add fault-tolerance. Ina horizontally-scaled system, BusinessObjects Enterprise components areinstalled on multiple machines; in a vertically-scaled system, multiple


26/312



Choosing an install type4

BusinessObjects Enterprise server components can run on the samemachine. Note that a single server, vertically-scaled system improves theability of BusinessObjects Enterprise to handle increased usage, but does notincrease the fault tolerance of the system.

Once BusinessObjects Enterprise is running on one machine, you can run theExpand 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 BusinessObjectsEnterprise.

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 BusinessObjectsEnterprise Administrators Guide for information on planning how to bestexpand your installation to meet the needs of your organization. See Expandinstallation on page 52for detailed instructions on how to accomplish yourexpand 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 youhave an existing web application server that resides on a different machinethan the one that has your BusinessObjects Enterprise core components.

A distributed installation has two stages. The first step is done on the machinewhere the all BusinessObjects Enterprise components except the WebComponent Adapter will reside, see Installing only the server and clientcomponents on page 67for more information.The second step is done onthe machine where the web server is installed, see Installing only the WebComponent Adapter on page 74for more information.

Alternately, you may want to do a custom installation when you want toexclude some components installed by default with the new installation, orinstall only a limited set of specific components. It is recommended that yourun this type of installation only when you are familiar with specificBusinessObjects Enterprise components and their roles. If you are not


27/312



Choosing an install type 4

familiar with specific BusinessObjects Enterprise components and their rolesand you do a custom install, you may inadvertently not install a requiredcomponent.

Note: If you have an existing Crystal Enterprise 10 web desktop that youwant to continue using with BusinessObjects Enterprise XI, you must installan 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 installationprogram.

Your deployment of BusinessObjects Enterprise servers will bedistributed over multiple computers. Perhaps your web application serverwill be on one machine but other BusinessObjects Enterprisecomponents are elsewhere.

You know exactly what components you require. You have disk space constraints.

You have customized some of your own applications and you dont wantthe installation to overwrite them.

You have an existing Crystal Enterprise 10 web desktop that you want tocontinue using.

Silent installation

If you need to perform multiple installations and do not want to interruptpeople who are currently working on machines in your system, or if you wantto install BusinessObjects Enterprise with your own script, you can use thesilent installation command for BusinessObjects Enterprise. A silentinstallation is one that you run from the command line.

The silent installation is not recommended for custom or upgradeinstallations. The installation options are simplified and do not allow for thesame level of customization that is provided in the BusinessObjectsEnterprise Setup program. Silent installations are also not recommended forupgrades. For more information on performing a silent installation on

Windows, see Silent installation on page 91.


28/312



Choosing an install type4

Upgrade installation

If you have an existing installation of Crystal Enterprise 9 or 10, orBusinessObjects Enterprise XI R1, and you performed a full standalone clientor server installation of your product, you can upgrade your system toBusinessObjects Enterprise XI R2 directly with the install program. Thisprocess will not upgrade your original CMS; This step must be completedafter you upgrade your system, see Upgrading and Migrating on page 253.If you cannot upgrade your system because you did not perform a fullstandalone client install, you will need to uninstall the old components beforeperforming an install.

A full standalone server install means during the initial install, you installed thecomplete feature set onto one machine. This includes all the clientcomponents, the server components, the SDKs and either the Java or the

.NET Web Component Adapter or Web Component Server. A full standaloneclient install means you installed all of the client components onto onemachine.

Note: If either the full client or server set is not detected, you will receive amessage informing you that you must uninstall the previous version beforeyou proceed with your install.

After you enter the product keycode for your new install, the installationprogram will detect that you have a previous version installed. You will receivea message that informs you a previous version has been detected and that anupgrade will be performed. The installation program will find the existing

versions, replace them with the new BusinessObjects Enterprise XI R2components and add components new to this release.

After you upgrade your installation, you will need to migrate your system datato the new version, and import content from an earlier version of CrystalEnterprise, Crystal Info, or BusinessObjects Enterprise.

Upgrading consists of replacing existing Crystal Enterprise programs andfiles with the latest BusinessObjects Enterprise versions.

Copying the contents of the original input root directory into the rootdirectory that the new Input File Repository Server is already configuredto 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 ManagementServer (CMS) database, while at the same time updating the databaseschema to the latest version.


29/312



Database requirements 4

Note: Do not attempt to use your BusinessObjects Enterprise XI R1CMS to host your BusinessObjects Enterprise R2 deployment. This willresult 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, orBusinessObjects Enterprise XI R1, see Upgrading and Migrating onpage 253. This guide does not cover describes how to migrate from thefollowing versions:

BusinessObjects version 5.x BusinessObjects version 6.x WebIntelligence 2.x through 6.5.x

For further information on these topics, see theBusinessObjects 5.x to XI

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

If you require further assistance in upgrading, particularly large-scale and/ormission-critical deployments, or in migrating customized reportingapplications, it is recommended that you contact a Business Objects servicesconsultant, who can then assess your reporting environment and assist in theplanning 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 BusinessObjectsEnterprise XI Release 2; You must create a new database for thisrelease. If you use a database from a previous release, you will . SeeUpgrading and Migrating on page 253 for details.

Database requirements

Before you create the database that you want to integrate withBusinessObjects Enterprise, consider the following sections that detail what

settings are required when the database is created and what settings youshould test before beginning your BusinessObjects Enterprise install.


30/312



Database requirements4

DB2 database setup requirements

If you are using a DB2 database with your BusinessObjects Enterprisedeployment, there are specific settings you need to select when the databaseis created. It is not sufficient to modify these settings after the database hasbeen 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 creatingthe CMS database.

Note: This requirement does not apply to the Audit database. If youwant, 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 sequencesetting, the users and usergroup objects may not sort properly in theCentral Management Console. Replace XX with the code that isappropriate to your code set and codepage for your location. Consultyour DB2 documentation for specifics.

Note: If you are using DB2 8.1, you require a C compiler that is installed andconfigured to build SQL stored procedures. DB2 8.2 does not have this

requirement. SQL stored procedures are used in BusinessObjects Enterprisewhen users are added to groups in the CMS. Please consult the DB2documentation for details on how to configure the C compiler for SQL storedprocedures, and for determining what version of the C compiler is supportedon your platform.

Sybase database setup requirements

If you are using Sybase, when you create your database for the CMS, ensurethe page size is set to 8 KB.

Note: The Sybase database default page size is 2KB which is too small forCMS. For CMS to run optimally, the page size must be 8KB. The page size isset up during the database creation and it cannot be changed after thedatabase is set up.


31/312



Preparing your existing database server4

Oracle database setup requirements

For an Oracle database there are no specific parameters, other than thesetting of UTF-8, that are crucial for BusinessObjects Enterprise to work.However, before you begin the install of BusinessObjects Enterprise, youmust ensure the Oracle environment variables are set up correctly.

MySQL database setup requirements

For a MySQL database there are no specific parameters that are crucial forBusinessObjects Enterprise to work, other than the setting of UTF-8. If youselect the option to install and configure MySQL with your installation, theinstallation creates a MySQL database with the default settings for the CMSdatabase and the Audit database.

Preparing your existing database server

After you have created your database, and before you install BusinessObjectsEnterprise, you or your database administrator need to prepare your owndatabase server so the CMS can connect to it.

During your installation, you will be asked whether you want to install MySQLor use an existing database. If you specify that you will you use an existingdatabase, you will be asked for details about your database.

Although you are required to provide the details about your database duringthe installation, you will not be asked to provide your database name unlessyou are using an existing version of MySQL. This table summarizes theinformation you will be required to enter to identify your database during theinstallation if your are using SQL Server, Sybase, Oracle, or DB2.I

Note: The Sybase Service name is a combination of the host name and theport number which is set by your database administrator in the file sql.ini.

Database type Information required at

install time

SQL Server Data Source Name

Sybase Sybase Service Name

DB2 DB2 alias name

Oracle tnsname


32/312



Preparing your existing database server4

Prerequisites to database preparation

Before you prepare your database, you must have already created it. Ensureyou have created the database with these required settings:

DB2 database setup requirements on page 30 Sybase database setup requirements on page 30

Oracle database setup requirements on page 31

To prepare your database

1. Create a new, empty database (or Oracle schema) on your databaseserver.

2. Create a new user and assign it a secure password.

3. Ensure that the new account has permission to create, modify, deletetables and create procedures so that BusinessObjects Enterprise can

modify the database as required.

Note: If you are using Oracle, and you dont own the schema created forfor the CMS or Audit database, you must have relative permissions to theschema.

4. If you are using Sybase, Oracle, or DB2, ensure the following are set upbefore you begin your installation:I

During the install, you will be asked for information regarding yourdatabase.

5. Record the these details as they will be required during your install:

The name of your database, your Sybase service name, your Oracletnsname, or your DB2 alias.

The user account and the password authorized to the database.

Tip: You may want to record the required details on the InstallationChecklist at the end of this chapter so the information is available whenyou install.

Database type Ensure this has been

configured

Sybase Sybase service nameOracle tnsname name

DB2 DB2 alias


33/312



Installation checklist4

For information on how to create a new database (or Oracle schema), consultyour database server documentation or your database administrator. Forinformation on how to migrate your initial CMS database to another supporteddatabase server later, see the BusinessObjects Enterprise Deployment and

Configuration Guide.

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 anexisting MySQL database, the installation will not proceed and you willreceive an error message. Consult the documentation for MySQL forinformation on how to configure the MySQL.

Installation checklisto Have you tested that all machines that will run BusinessObjects

Enterprise can communicate properly?

o Have you tested the database connection between the machine whereyour CMS database will reside and where the Central ManagementServer will be installed?

o Have you decided which database to use with BusinessObjectsEnterprise?

o If you are using your own database server, have you created a database

for the CMS?

o If you plan to connect remotely to install, have you ensured your terminalsetting is set to VT100 before beginning the installation?

o If you plan to use Auditor, have you created an auditing database?

o Have you created a userid and password, with access to your existingdatabase (if you are integrating your existing database server software),so that the installation can access your database to configure the CMSdatabase?

o Have you made sure you can log on to the database with the ID andsetup tables?

o Have you ensured that any existing database you will connecting to hasbeen configured correctly?

o Have you verified you are using a supported locale?

o Have you decided whether or not you will develop custom applications?

o Have you decided what web application server to use?


34/312



Installation checklist4

o Have you made sure your existing web application server has the JDKinstalled?

o If you are not using Tomcat, is your web application server alreadyinstalled and configured?

o Have you chosen which Web Component Adapter you want to install?

o If you are installing on VMWare, have you ensured your machine namedoes not include any of the following characters: an underscore, a period,or a slash?

o


35/312

c h a p t e r

Installing BusinessObjects

Enterprise on Windows


36/312

Installing BusinessObjects Enterprise on Windows



Installation overview

Before you install BusinessObjects Enterprise on Windows, consider which of

the following scenarios is best for you: New installation

In this scenario, you install the BusinessObjects Enterprise server, clientand Web Component Adapter on a single machine. You can installTomcat with your install, or install BusinessObjects Enterprise on amachine that is already running as a web server. This provides thequickest way to install BusinessObjects Enterprise.

Custom installation

The Custom installation option allows you to install specific featuresrather than installing everything by default. This allows you to distribute

the BusinessObjects Enterprise components across multiple machineswithout installing components you dont require on each machine. Forexample, You can install the BusinessObjects Enterprise server andclient components on one machine, and use another machine thatalready has your existing web application server and simply install theWeb Component Adapter of your choicewithout installing the coreBusinessObjects Enterprise components on the web application serveritself. For more information on using the custom install to do this, seeCustom installation on page 61.

Alternately, if you are already familiar with BusinessObjects Enterprise,and familiar with the components and their roles, you can perform acustom installation to install only the specific components you require.For further information, see Running a custom install on page 78.

Note: It is not recommended that you run a custom install unless you arealready familiar with BusinessObjects Enterprise. If you are not familiarwith specific BusinessObjects Enterprise components and their roles andyou do a custom install, you may inadvertently not install a requiredcomponent. You may instead want to follow the steps outline in,Installing only the server and client components on page 67andInstalling only the Web Component Adapter on page 74,which aremore detailed.

Expand installationAn expanded installation is done after your initial install ofBusinessObjects Enterprise. This type of install allows you to scale yourdeployment of BusinessObjects Enterprise by installing additional


37/312




BusinessObjects Enterprise servers to meet the demands of yourenterprise. How you choose to expand your system depends largelyupon your current configuration and your reporting requirements.

This section, Expand installation on page 52,provides the steps toexpand installation. However, before you expand your installation, it isstrongly recommended that you consult the BusinessObjects EnterpriseDeployment and Configuration Guidefor general scalabilityconsiderations, for sample configurations, and for information about CMSclustering.

Client tools installation overview

Although most end users interact with BusinessObjects Enterprise overthe web, client tools are also provided as stand-alone Windowsapplications:

BusinessObjects Designer Publishing Wizard Repository Migration Wizard Import Wizard Desktop Intelligence Business Views Conversion Tool Universe builder

Install these applications individually for particular users who are

responsible for managing BusinessObjects Enterprise content,developing applications, or migrating system data.

Upgrade installation

If you have an existing installation of Crystal Enterprise 9 or 10, orBusinessObjects Enterprise XI, and you performed a full standaloneclient or server installation of your product, you can upgrade your systemto BusinessObjects Enterprise XI Release 2 directly.

A full standalone server install means during the initial install, youinstalled the complete feature set onto one machine. This includes all theclient components, the server components, the SDKs and either the Java

or the .NET Web Component Adapter or Web Component Server. A fullstandalone client install means you installed all of the client componentsonto one machine.

If either the full client or server set is not detected, you will receive amessage informing you that you must uninstall the previous versionbefore you proceed with your install.


38/312




Note: This guide does not cover describes how to migrate from thefollowing versions:

BusinessObjects version 5.x

BusinessObjects version 6.x WebIntelligence 2.x through 6.5.x

For further information on these topics, see theBusinessObjects 5.x to XIRelease 2 Migration Guide or the BusinessObjects 6.x to XI Release 2Migration Guide.


39/312


System requirements 5


Silent installation

Experienced administrators can use the silent installation to install fromthe command line. It is recommended that you run this installation whenyou need to install quickly on multiple machines. You can alsoincorporate the silent installation command into your own build scripts.

Tip: If you plan to use Web Intelligence documents, you may want to publishthe following user guides to BusinessObjects Enterprise, and make themavailable to your users. They are available as PDFs in the docs directory ofyour product distribution.

Performing On-Report Analysis with Web Intelligence Building Queries Using Web Intelligence Query - HTML Building Reports using the Web Intelligence Java Report Panel Building Reports Using the Web Intelligence HTML Report Panel

Designer's Guide Data Access Guide Error Messages Explained

System requirements

For a detailed list of tested environments, consult the Platforms.txtfileincluded with your product distribution. This file includes specific version andService Pack requirements for web servers, web browsers, web application

servers, databases, and operating systems. For additional importantinformation that may pertain to your deployment, it is also stronglyrecommended that you consult the Release Notesincluded with your productdistribution (release.pdf, release.htm, or release.rtf).

Generally, however, the following components must be installed andconfigured correctly before you install BusinessObjects Enterprise:

Database server for the CMS, if you do not use MySQL installed by theinstaller.

Internet Explorer or Mozilla Firefox Web application server, if you do not use Tomcat installed by the installer.

Setting up the CMS database

The Central Management Server (CMS) requires a database to storeinformation about the system and its users. By default, the Setup programinstalls and configures its own MySQL database if necessary. MySQL is a


40/312


System requirements5


client/server data engine that provides local data storage and is compatiblewith Microsoft SQL Server. CMS clustering is automatically supported by thedefault MySQL database.

Alternatively, you can connect your CMS directly to your preferred databaseserver without installing MySQL. Then set up the appropriate database clientsoftware or ODBC Data Source Name (DSN). Consult your local databaseadministrator or database system documentation for details.

You can migrate this initial CMS database to another supported databaseserver later. For details, see Configuring the intelligence tier in theBusinessObjects Enterprise Administrators Guide.

Note:

See the Platforms.txtfile included with your product distribution for acomplete list of tested database software and version requirements.

Ensure that your database server is set up to use Unicode characterencoding (such as UTF-8). Consult your database documentation todetermine the settings required for a Unicode configuration. For databaseservers such as Oracle and Sybase, during installation you need toconfigure the server to use Unicode encoding for the character datatypes. For other databases, such as DB2, you can create the CMSdatabase with Unicode settings on your existing database server.

Before installing BusinessObjects Enterprise atop an existing installationof MySQL or Microsoft SQL Server, you need to complete severalpreparatory steps before running the BusinessObjects Enterprise setupprogram.

Setting up a database account for BusinessObjects Enterprise

To administer the CMS database, you need to set up a database account. Ifyou choose to install MySQL when you install BusinessObjects Enterprise,you will be prompted during installation to set up this account. If you plan touse your own database, please complete these steps before you installBusinessObjects Enterprise.

To set up a database account for BusinessObjects Enterprise

1. Create or select a user account that provides BusinessObjects Enterprisewith the appropriate privileges to your database server.

2. Verify that you can log on to your database and carry out administrativetasks using the account you set up for use by the CMS.


41/312


Installing Business Objects products on a non-system drive 5


Providing administrative privileges

You must log on to the local machine as an Administrator when you installBusinessObjects Enterprise XI.

Meeting network requirements

When installing BusinessObjects Enterprise on multiple machines, ensure thateach target machine is able to communicate over TCP/IP with the machinethat is running as your CMS. In particular, your web server must be able tocommunicate with the machine that is running as your Web Component

Adapter (WCA). All web desktop clients must be able to access the web server.

Note: If you are installing BusinessObjects Enterprise in a firewall environment,you will need additional configuration details. See the Working with Firewallssection of the BusinessObjects Enterprise Administrators Guide.

Installing Business Objects products on anon-system drive

You can install BusinessObjects Enterprise on any drive on your machine.The Setup program installs BusinessObjects Enterprise files to the drive thatyou specify and also installs some files in the \system32 folder.

There is one exception to this rule. If you previously installed anotherBusiness Objects product, the BusinessObjects Enterprise Setup program

automatically uses the existing common directory for any shared BusinessObjects product files that it adds. If this common directory is on the systemdrive (that is, the drive containing your operating system files),BusinessObjects Enterprise automatically installs its shared files there.

To install several Business Objects products on a non-system drive, installBusinessObjects Enterprise first. All Business Objects products that youinstall subsequently will use this same non-system drive for their shared files.

New installation

This installation scenario offers the quickest way to install BusinessObjectsEnterprise. Once you have set up your web server software, run the Newinstallation from the BusinessObjects Enterprise Setup program.

When you perform this default installation, all the client and servercomponents that your product key authorizes you to install are installed onthe local machine. The Web Component Adapter (WCA) is also installed. You


42/312


New installation5


can automatically create a MySQL database for the CMS, and you can installthe Tomcat application server. Default user and group accounts are created,and sample reports are published to the system. When the installation iscomplete, the server components are started as services on the local

machine.

Note: If you are using an existing database, please make sure it is set upbefore you install. For details, see Setting up the CMS database on page 39.

To install all components

1. Run setup.exefrom the rootdirectory of your product distribution.

If Autoplay is enabled for your CD-ROM drive, the setup program willstart automatically. Click Installto continue.

Note: When you start the installation, the Microsoft Windows Installermay need to be installed or upgraded on the local machine. If so, the

Wise Installation Wizard performs the necessary modifications andprompts you when finished. Click Yesto restart the machine andresume the installation automatically.

2. Select which language to install from the list, and then click OK.

3. Click Next.

4. Click I accept the License Agreement, and then click Next.

5. Choose Perform Server Installation, and then click Next.

6. Fill out the Full Name and Organizationfields.

7. Enter your product keycode(s)


43/312


New installation 5


If you want to install BusinessObjects Enterprise, but notperformance management:

a. Enter your product code in the first Product Keycode field.

You can cut and paste the product code if you have the code in adigital format.

b. Leave the check box beside Install Performance Managementempty, then click Next.

If you want to install BusinessObjects Enterprise andperformancemanagement, which includes Dashboard Manager, PerformanceManager, Set Analysis, Predictive Analysis and Process Analysis:

a. Enter the BusinessObjects Enterprise product keycode in thefirst Product Keycodefield.

b. Click the Install Performance Management check box.

c. Enter one of the performance management keycodes in thesecond Product Keycode field.

The performance management product key you type here onlyenables that one product. To enable other performancemanagement products, you need to enter the license keys forthose products in the Central Management Console (CMC) afterthe installation is complete. To find out how to do this, see theBusinessObjects Enterprise Administrators Guide.

d. Click Next.

8. Specify the directory where you want to install, or accept the defaultlocation, and then click Next.


44/312


New installation5


9. Choose whether you want to install MySQL or use an existing databaseserver.

If you want to install MySQL:

a. Verify Newis selected.

b. Select Install MySQL Database Server.

c. Click Next.

Note: Later in the installation you will be prompted to specify the

password for MySQL root user. You will also be prompted to enter apassword for the user account BusinessObjects that accesses theCMS database.

If you want to use an existing database server:

a. Select New.

b. Select Use an existing database server.

c. Click Next.

Note: Later in the install you will be prompted to specify the type ofdatabase you will use and the authentication details for the CMS and

Auditing database.


45/312


New installation 5


10. If you entered a keycode for performance management, decide when youwant to enter the required information to enable scheduling.

If you want the installation to provide the required information now,enter the credentials in the User Nameand Passwordfields.

Note: By default, this is the user account for the operating systemwhere performance management is installed (for example, the NTuser account).

Note: If you want to provide the required information later, check Leaveit blank. I will configure it after installation.


46/312


New installation5


11. If you chose to install MySQL, specify the configuration for MySQLDatabase Server..

a. Enter the port number.

b. Enter and confirm the password that will be used by MySQLs rootuser account.

c. Accept the default user name to access the CMS database or enter anew user name to override the default name.

d. Enter and confirm the password that will be used to access the CMSdatabase, and then click Next.

Note: The setup program will configure the CMS to connect to its systemdatabase using the account and the password you create here.

12. If you chose to use an existing database server, specify the configurationfor the CMS database and the Auditing database, if you will be using one


47/312


New installation 5


Note: This must be a new DSN or database specifically created forBusinessObjects Enterprise XI Release 2. Do not specify the name of anexisting DSN or database from a previous deployment.

For SQL Server:

a. Select SQL Server,and then click Browse.

The Select Data Source dialog box appears.

b. Click the Machine Data Sourcetab.


48/312


New installation5


c. Select the data source name you created for the CMS from theData Source Namefield, and then click OK.

The SQL Server Login window will appear..

d. Enter the user id and password for the data source, and thenclick OK.

e. If you plan on using Auditing, select Auditing databaseandrepeat the previous four steps for the Auditing database, andthen click Next; otherwise, click Next.

Note: This database should have been set up prior to install. SeeSetting up a database account for BusinessObjects Enterprise onpage 40.

For Oracle:

a. Select Oracle.

b. Enter the Oracle tnsname in the Server field.

c. Enter the credentials for the server in the Username andPassword fields.

xir2 bip install en

Documents