xir2 bip install unix en

8/8/2019 Xir2 Bip Install Unix En

1/284

BusinessObjects Enterprise XI

Release 2 Installation Guide

BusinessObjects Enterprise XI Release 2 Productivity Pack

Unix


2/284

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/284

BusinessObjects XI Release 2 Installation Guide 3

Table of Contents

Chapter 1 Introduction to BusinessObjects Enterprise XI Release 2 11

What is BusinessObjects Enterprise? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Who should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Business Objects information resources . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2 Planning Your Installation 13

Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

UNIX permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting up server communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

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

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

Using MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Using a supported database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Choosing a deployment environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Choosing a development environment . . . . . . . . . . . . . . . . . . . . . . . . 20

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

Choosing a Web Component Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 22

Choosing optional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

OLAP Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Desktop Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Crystal Reports Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Web Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Business Process BI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

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


4/284

Contents

4 BusinessObjects XI Release 2 Installation Guide

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

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

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

Setting up your UNIX system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Meeting the host name and network requirements . . . . . . . . . . . . . . . . 28

Creating an account, a home directory, and a login environment . . . . . 28

Checking for required commands and utilities . . . . . . . . . . . . . . . . . . . 29

Setting the locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Setting up an empty database for the CMS . . . . . . . . . . . . . . . . . . . . . 30

Database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32DB2 database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Sybase database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Oracle database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 34

MySQL database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Preparing your existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Providing and verifying connectivity to the CMS database . . . . . . . . . . 36

Testing DB2 environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Testing Sybase environment variables . . . . . . . . . . . . . . . . . . . . . . . . . 39

Testing Oracle environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing the Java SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 3 Installing BusinessObjects Enterprise on UNIX 47

Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting up product distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Running the product distribution directly from a CD . . . . . . . . . . . . . . .49

Copying the product distribution to your machine . . . . . . . . . . . . . . . . . 49

Beginning your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Difference between user and system installation . . . . . . . . . . . . . . . . . 50

Beginning your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Performing a new installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53


5/284

Contents


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

Performing an expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Performing a custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Performing a client tool installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Performing a scripted installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Using ccm.sh to start the BusinessObjects Enterprise servers . . . . . . . 71

Installing a Java application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Installing the Java application tier components . . . . . . . . . . . . . . . . . . . . . . 72

Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Verifying your performance management installation . . . . . . . . . . . . . . 77

Post installation setup for performance management . . . . . . . . . . . . . . 78Troubleshooting starting performance management . . . . . . . . . . . . . . 78

Chapter 4 Installing the Productivity Pack 81

Productivity Pack upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

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

Business Process BI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

BusinessObjects Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Content Search in InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Distributed installs of BusinessObjects Voyager . . . . . . . . . . . . . . . . . . 84Feature selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Silent install parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

New or updated WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Uninstalling the Productivity Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 5 Deploying on Tomcat 95

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Deploying with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Preparing the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 6 Deploying on Tomcat with the JDK 1.5 103

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


6/284

Contents


Using a version of Tomcat already running BusinessObjects Enterprise .104

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

Adding the Java Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Preparing the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Verifying the Tomcat deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 7 Deploying on WebSphere 113

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 114

Deploying on IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Creating an application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Starting the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Modifying the startup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Making configuration changes for distributed performance management120

Changing the classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Setting the heap size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Modifying the PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Checking or changing the assigned port number on WebSphere 5.1 . 125

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

Creating a new virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

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


Verifying the WebSphere Configuration . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 8 Deploying on WebLogic 131

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 132

Deploying on BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Copying your performance management InitConfig.properties file . . . 138

Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 139


7/284

Contents


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

Changing the CLASSPATH in WebLogic . . . . . . . . . . . . . . . . . . . . . . 141Modifying the WebLogic environment script . . . . . . . . . . . . . . . . . . . . 142

Setting the Java Virtual Machine options for OLAP Intelligence andperformance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Setting up the JAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144


Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 145

Chapter 9 Deploying on WebLogic 9.2 with the JDK 1.5 147

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148


Deploying on BEA WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Creating a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Deploying performance management . . . . . . . . . . . . . . . . . . . . . . . . . 154

Setting the Java Virtual Machine options for OLAP Intelligence andperformance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Setting required variables in startup script . . . . . . . . . . . . . . . . . . . . . 156

Modifying the WebLogic environment script . . . . . . . . . . . . . . . . . . . . 158Changing the default parser and transformer . . . . . . . . . . . . . . . . . . . 158

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


Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 161

Chapter 10 Deploying on Oracle Application Server 163

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164


Deploying with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Configuring the Class Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Changing Memory Allocation Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Copying your performance management InitConfig. properties file . . 169

Setting the PATH environment variable . . . . . . . . . . . . . . . . . . . . . . .169


8/284

Contents


Changing the command line options for OLAP Intelligence or performancemanagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Setting up the JAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 172


Verifying the Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Chapter 11 Deploying on Sun Java Application Server 177

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178


Deploying with Sun Java Application Server . . . . . . . . . . . . . . . . . . . . . . . 181

Configuring the Class Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Editing the security.policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Updating the JVM settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182


Verifying the Sun Java Application Server configuration . . . . . . . . . . 186

Chapter 12 Importing Objects to BusinessObjects Enterprise 187

Importing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Importing information from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . . 189

Importing objects from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . . 190

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

Importing Application Foundation objects . . . . . . . . . . . . . . . . . . . . . . 193

Limitations on importing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Before importing from Application Foundation . . . . . . . . . . . . . . . . . . 195

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

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

Using the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Specifying the source environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Specifying the destination environment . . . . . . . . . . . . . . . . . . . . . . . 220

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

Choosing an import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Updating previously imported objects . . . . . . . . . . . . . . . . . . . . . . . . . 228

Selecting specific objects to import . . . . . . . . . . . . . . . . . . . . . . . . . . . 229


9/284

Contents


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

Using text files with the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Text file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Importing from text files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Chapter 13 Custom SDK Deployments 245

Software Development Kit overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Java Server Pages environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Chapter 14 Upgrading and Migrating 249

What does this section cover? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

What this section does not cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Upgrading from Crystal Enterprise or from BusinessObjects Enterprise . 250

Preparing for upgrading or migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Disabling and stopping servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Migrating the CMS or APS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

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

Upgrading other components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Migrating to performance management XI Release 2 . . . . . . . . . . . . . . . 267

About the Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Migrating the performance management repository . . . . . . . . . . . . . . . . 268

Migrating schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Migrating rules and named events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Migrating security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Managing rights at the object level in performance management XI . 270

Chapter 15 Uninstalling 271

Uninstalling BusinessObjects Enterprise from UNIX . . . . . . . . . . . . . . . . 272

Appendix A Business Objects Information Resources 273

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

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274


10/284

Contents


Whats in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Where is the documentation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Send us your feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . 275

How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

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

Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Index 279


11/284

c h a p t e r

Introduction to

BusinessObjects Enterprise

XI Release 2


12/284

Introduction to BusinessObjects Enterprise XI Release 2

What is BusinessObjects Enterprise?1


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 webserver software is especially beneficial. If you are installing BusinessObjects

Enterprise on UNIX, you will require root privileges to perform some of thesetup procedures.

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 docs directory 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, see Appendix A: Business ObjectsInformation Resources. This appendix describes the Business Objectsdocumentation, customer support, training, and consulting services, with linksto online resources.


13/284

c h a p t e r

Planning Your Installation


14/284


Installation overview2


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 requirementsGenerally, the following components must be installed and configuredcorrectly before you install BusinessObjects Enterprise:

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


15/284


System requirements 2


Database software that is compatible with the CMS and the Auditdatabase (unless you install MySQL during the BusinessObjectsEnterprise installation)

For information about hardware requirements, consult thePlatforms.txt file included with your product distribution, or see theSupport Platforms PDF available from the Business Objects support site.

For a detailed list of supported environments, consult the Platforms.txt fileincluded 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 Notes included with your product distribution (release.pdf).

Note:

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

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

UNIX permissions

To perform either a user or system installation on UNIX, the user accountunder which the install is run must have read, write, and execute permissions

to the directory where BusinessObjects Enterprise will be installed. Rootprivileges are not required to perform either a user or system install ofBusinessObjects Enterprise. In fact, if you attempt an installation with rootprivileges, you will be unsuccessful.

However, if you run a system installation, you do require root authority to runthe system-level initiation script. This script, which is called setupinit.sh, is runafter the installation completes. This script creates entries into the run controlscripts for the Operating System that start up the BusinessObjects Enterpriseservers when the UNIX server is brought up and stops the BusinessObjectsEnterprise servers when a machine is shut down. A system application onUNIX is analogous to running your Windows application as a service.


16/284


Setting up server communication2


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.

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.

UNIX servers that run BusinessObjects Enterprise must have a fixed hostname. You must have root privileges to set or modify a fixed host nameon your system. However, you do not require root privileges to perform a

user install of BusinessObjects Enterprise. If you are unfamiliar withthese procedures, consult your UNIX system documentation.

Note: Please ensure your hosts use none of the following characters intheir name: an underscore, a period, or a slash.

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

For database clients, you must set certain parameters. The DB2 client,for example, must use the DB2CODEPAGE value of1208. The Sybase

database client typically requires the parameterLC_ALL and anappropriate entry in the locales.dat file (located in the locales folderof your Sybase installation directory).


17/284


Choosing a server location 2


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 ComponentAdapters (WCA).

If you plan to use a Java application server and your existing applicationserver does not include a version of the Java Development Kit (JDK)supported by BusinessObjects Enterprise, you will need to install it.

Note: If you are installing BusinessObjects Enterprise in a firewall

environment, you will need additional configuration details. See theWorking with Firewalls section of the BusinessObjects Enterprise

Administrators Guide.

Choosing a server location

When planning your BusinessObjects Enterprise installation, you should alsoconsider where you will place your deployments 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 optimize 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 of

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


18/284


Choosing a server location2


Note: This guide does not cover how to cluster a CMS. For details onhow to configure a CMS cluster after your initial installation, see thesesections 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 the BusinessObjects Enterprise Deployment and ConfigurationGuide for 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 deploymentconfigurations, tuning and performance.

See Creating accessible reports for information on how to create anddistribute reports that meet the needs of people with disabilities.

Choosing a database server

BusinessObjects Enterprise requires a relational database 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 use

BusinessObjects Enterprise Auditor. Before you install, you should choosewhich 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 systemdatabase was known as the repository. For more information, see theBusinessObjects 5.x to XI Release 2 Migration Guide or the

BusinessObjects 6.x to XI Release 2 Migration Guide. For a detailed list of supported database servers, see the

platforms.txt file included with your product distribution.


19/284


Choosing a server location 2


Using MySQL

MySQL database server is an open-source database that provides local datastorage. The setup program can configure MySQL along with your

BusinessObjects Enterprise components. If you already have MySQLinstalled, the installation program creates the CMS database using yourexisting database. During the installation of BusinessObjects Enterprise, youspecify what database server you will use and enter the required parametersfor authentication.

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 supported database servers, see the platforms.txt fileincluded with your product distribution. If you do not have a database installedon your machine you can use MySQL for your CMS database.

Sourcing the script that identifies the database environment variables

If you are using an existing database, you need a method to connect to it fromwithin BusinessObjects Enterprise. This is done through your database client.In this document, the terminology used for this operation is to source thescript that identifies the database environment variables.

If you are integrating BusinessObjects Enterprise with a different webapplication server than the version of Tomcat that can be configured with yourinstallation, you may need to source the environment script. This will set upthe required variables for BusinessObjects Enterprise.

Technically, sourcing your environment script involves running a script in yourcurrent environment. When your database client is sourced from withinBusinessObjects Enterprise, all the required environment variables for yourdatabase are set up and exported.

Your database client or the BusinessObjects Enterprise environment scriptcan be sourced from the command line, entered into a profile, or entered intoanother script.

To source your database client from the command line, you wouldexecute the script that sets up the variables required by your databaseclient to access your database. For example, in the bash shell, you couldtype this:

source ora10env.sh


20/284


Choosing a deployment environment2


To source the BusinessObjects Enterprise environment script, you wouldexecute the script that sets up the variables required. For example, youcould add this to the Tomcat setenv.sh or the WebSphere startup script:

source /bobje/setup/env.sh

Note that the syntax used to source a script varies based on the type of shellyou are using. Some UNIX shells use source as the syntax for this operation;some UNIX shells use the . (dot operator). Please consult thedocumentation for your shell to determine the appropriate syntax.

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 whether to install the Java Web Component Adapter. Determine whether or not you want to install Tomcat.

This section list the decisions you should make before you install and lists theoptions available when you install.

Choosing a development environment

Java Server Pages (JSP)can be used in conjunction with BusinessObjectsEnterprise. Support for Crystal Server Pages (CSP) was deprecated on UNIXplatforms in the Crystal Enterprise 10 release.

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

Shell name source . (dot operator)

Bourne shell (sh) no yes

Korn shell (ksh) no yes

Bourne Again Shell

(bash)

yes yes

C shell (csh) yes no

Turbo C shell (tcsh) yes no


21/284


Choosing a deployment environment 2


In the period since CSP was developed, the cross-platform application servermarket has become dominated by the Java Platform, Enterprise Edition(J2EE) platform. As a result, Business Objects has moved away from theproprietary CSP language and has instead developed tools and applications

in J2EE.

What does deprecating CSP mean?

New BusinessObjects Enterprise features will not be made available inCSP.

You should not develop new custom applications in CSP. You should plan to port existing CSP applications to J2EE.

For further information on how to port CSP applications, contact BusinessObjects Global Services.

Choosing an environment for new custom applicationsWhile it will be possible to run CSP applications after CSP has beendeprecated, you should not develop new custom CSP applications on thatplatform. Instead, you may consider building new applications using J2EE.You should port existing applications to J2EE since CSP on UNIX wasdeprecated in Crystal Enterprise 10.

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.

Your choice of which web development environment to use to develop your

own custom applications will depend largely on your own technologypreferences. However, in making this decision, consider the technologydirections foreseen by Business Objects.

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 custom

applications and, if so, which web development environment to use.

If you plan to develop custom applications using the BusinessObjectsEnterprise Java SDK, you can use any of the supported web servers listed inthe Platforms.txt file that is included with your product distribution.


22/284


Choosing optional components2


Choosing a Web Component Adapter

BusinessObjects Enterprise provides a web applicationthe WebComponentAdapter (WCA) that allows your web application server to run legacy

Crystal Enterprise CSP 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.

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

For UNIX installations, a Java version of the WCA is available. The Java Web

Component Adapter must be installed on a J2EE web application server.

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


23/284


Choosing optional components 2


OLAP Intelligence supports the market leading OLAP servers including:Hyperion Essbase, SAP Business Information Warehouse (BW), and IBMDB2 OLAP Server.

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 asBusinessObjects in release 5.x/6.x. Desktop Intelligence

is now installed as part of the client install for BusinessObjects Enterprise. Itcan no longer be 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 andmetric 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.


24/284


Choosing optional components2


Note:

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

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 or

after 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 IntelligenceWeb 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 Service

Business Process BI Service 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 Service Guide for more information.


25/284


Choosing an install type 2


Choosing an install type

After you have decided what to install and where to install it, you will decide

how to install BusinessObjects Enterprise. The first step is to select either aclient or a server installation. When you perform a client install, only the clientcomponents are installed; when you perform a server install, both the clientand server components are installed.

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

New installation Expand installation Custom installation Silent installation

The first few choices use the installation program to guide you through theinstallation process. The Silent Installation is a scripted installation on UNIXinstalled from the command line.

New installation

Performing a new installation is the easiest way to deploy BusinessObjectsEnterprise because all of the required client, server, and optional componentsare installed by default onto one machine.

Difference between user and system installationWhen you perform a new installation, on UNIX, you can choose between auser and a system installation.

When you choose a user installation, all the required components areinstalled.

When you choose a system installation, all the required components areinstalled, In addition, the installation creates a system-level initiationscript. This script creates entries into the run control scripts for theOperating System that start up the BusinessObjects Enterprise serverswhen the UNIX server is brought up and stops the BusinessObjects

Enterprise servers when a machine is shut down.Note: To perform a System installation, you do not require root-levelauthority. However, to run the system-level initiation script root-levelauthority is required.

You may want to choose a new installation if:

You have not installed BusinessObjects Enterprise before.


26/284


Choosing an install type2


You want to install all components on the same machine. You dont need to select specific components to install. 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, multipleBusinessObjects Enterprise server components can run on the samemachine. Note that on 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 Deployment and Configuration Guide for information on planninghow to best expand your installation to meet the needs of your organization.

Custom installation

The custom installation allows you to choose which components are installed.You may want to perform a custom installation if you plan to useBusinessObjects 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 completed on themachine where all BusinessObjects Enterprise components except the WebComponent Adapter will reside (see Installing only the server componentson page 59for more information). The second step is completed on themachine where the web server is installed (see Installing only the WebComponent Adapter on page 61 for more information).


27/284


Setting up your UNIX system 2


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 components. It is recommended that you run thistype of installation only when you are familiar with specific BusinessObjects

Enterprise components and their roles. If you perform a custom install withoutbeing familiar with specific BusinessObjects Enterprise components and theirroles, you may inadvertently fail to install a required component.

You may want to choose a custom installation if:

You are already familiar with the BusinessObjects Enterprise 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 want

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

On UNIX, you can install silently using a scripted installation. The scriptedinstallation is not recommended for custom installations. For more informationon performing a scripted installation on UNIX, see Performing a scriptedinstallation on page 65.

Setting up your UNIX systemBusinessObjects Enterprise integrates with your existing database and webserver software components, so the installation script needs to collect certaininformation about your current system. Because UNIX systems can varysignificantly from site to site, the following sections detail the key tasks thatyou must perform prior to installing BusinessObjects Enterprise.


28/284


Setting up your UNIX system2


Meeting the host name and network requirements

Your UNIX server must have a fixed host name before you run the installationscript. You must have root privileges to set or modify this information on your

system. If you are unfamiliar with these procedures, consult your UNIXsystem documentation.

When installing BusinessObjects Enterprise on multiple machines, ensurethat each target machine is able to communicate over TCP/IP with themachine that is running as your Central Management Server (CMS).

Note: If you are installing BusinessObjects Enterprise in a firewallenvironment, you will need additional configuration details. See the Workingwith Firewalls section of the BusinessObjects Enterprise Deployment andConfiguration Guide.

Creating an account, a home directory, and a loginenvironment

Create a specific user account and group under which the BusinessObjectsEnterprise background processes can run. You will log on as this user in orderto perform the remainder of the installation procedures. Although you willrequire root privileges to set up this account, the account itself does notrequire root privileges. Neither the installation scripts nor BusinessObjectsEnterprise itself needs to run as root.

Use your usual administrative procedures to perform these recommended

tasks.

To set up an account for installing BusinessObjects Enterprise

1. Create a new group or use an existing group. Create a new user account,and set this users primary group to the new group. Assign a securepassword to the new user account.

2. Create the directory where you want to install BusinessObjectsEnterprise.

By default, the installation will use your current directory as its basedirectory for the install, that is, the directory where you run install.sh.

You can override this default, with the directory of your choice at installtime.You will see the directory that you specify for the installationdirectory referred to as INSTALLDIR throughout this document.

3. Set the new users HOME directory to the installation directory that youcreated. When you run the installation script, you can choose a userinstallation type so that all of the installed files are confined to thedirectory that you specify here.


29/284




4. Ensure that the account you created has read, write, and executepermissions on the new HOME directory.

5. Assign the new user a default login shell, and create or modify theappropriate login script(s) for the user account. In particular, make surethat the login script(s) set up a default login environment that meets theserequirements:

All of the commands and utilities required by the install setupprogram must be accessible in the PATH environment variable.

For details, see Checking for required commands and utilities onpage 29.

The users login environment must set up the database environmentsuch that the install setup program can access your databaseclient software. For more information, see Providing and verifyingconnectivity to the CMS database on page 36.

The users login environment must set up a default locale that issupported by your UNIX system and BusinessObjects Enterprise.See Setting the locale on page 30.

Checking for required commands and utilities

In order for the install setup program to run correctly, the followingcommands and utilities must be installed on your UNIX system:

These relatively standard commands and utilities should be available on mostUNIX distributions. However, if for any reason one of them is not available onyour system, download and install a version appropriate to your UNIX system.It is recommended that you obtain any required files from your UNIX vendor.

Additionally, these commands and utilities must be accessible in the PATHenvironment variable of the user account that you use when installingBusinessObjects Enterprise. For details, see Creating an account, a homedirectory, and a login environment on page 28.

/bin/sh pwd read touch

uname expr hostname sed

awk chown grep tail

tar id dirname gzip

stty ulimit which


30/284


Setting up your UNIX system2


Setting the locale

Before you install BusinessObjects Enterprise, set your operating system touse one of the locales that BusinessObjects Enterprise XI supports for your

type and version of UNIX. Consult the platforms.txt file included withyour product distribution for a complete list.

If you are working at the console of a UNIX machine, you can select yourlocale directly from the logon screen when you log on with the account fromwhich you will install BusinessObjects Enterprise. However, to ensure thatyour operating system uses the correct locale whenever BusinessObjectsEnterprise runs, set the LC_ALL and LANG environment variables to yourpreferred locale in your login environment. (For example, if you are using a Cshell, set these environment variables in the .login file.)

Tip: Type locale to check that all of the related locale environment

variables (such as LC_MONETARY, LC_NUMERIC, etc.) were properly set byLC_ALL.

See the section on International Deployments in the BusinessObjectsEnterprise Administrators Guide for information on deployingBusinessObjects Enterprise for a multilingual, world-wide audience.

Setting up an empty database for the CMS

BusinessObjects Enterprise requires a relational database to storeinformation about the system and its users. You can install a MySQL

database during the installation, or you can use an existing database. If youwant to create a new MySQL database during the installation, this sectiondoes not apply to you.

If you want to use an existing database, you or your database administratormust create a new database on your database server before you installBusinessObjects Enterprise. We strongly recommend that this database beused only for BusinessObjects Enterprise, and not contain other tables.

The following database servers are supported on UNIX:

Oracle DB2

Sybase MySQL

Note:

See the Platforms.txt file included with your product distribution for acomplete list of supported database software and version requirements.


31/284




If you plan on integrating your own database with BusinessObjectsEnterprise, rather than installing MySQL with your installation, consult thesesection for details on database setup requirements before you create yourdatabase:

DB2 database setup requirements on page 32 Oracle database setup requirements on page 34 Sybase database setup requirements on page 33 MySQL database setup requirements on page 34

If you plan on integrating your own database with BusinessObjectsEnterprise, you will to prepare it before your installation. For proceduraldetails about how to prepare your database, after it has been created, seeDB2 database setup requirements on page 32. Here is a summary of thesteps that will be part of your preparation:

Creating a new database.Tip: You may want to name the new database bobjecms, and create anew user account named bobje, however, this naming convention is notrequired.

Note: If you have a previous release of BusinessObjects Enterprise youcannot 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 destroyany existing data. Create a new database instead, and after you havecompleted your installation, you can migrate your old content to the new

current versions database. See Upgrading and Migrating on page 249for details.

Creating a new user account and password for this database that will beused by BusinessObjects Enterprise.

Ensuring that this new account has permission to create, modify, anddelete tables and create procedures so that BusinessObjects Enterprisecan modify the database as required.

Recording the name of the database, the user account, and the passwordwhen you run the BusinessObjects Enterprise installation script.

During the installation process, the install script asks you if you want to

reinitialize the database. Choosing to do so causes the install script to createnew tables in the database to store BusinessObjects Enterprise data. (InOracle, choosing this option causes the install script to createBusinessObjects Enterprise tables in the default schema of the user whosename you provided during the install.)


32/284


Database requirements2


Note: During a reinstall of BusinessObjects Enterprise, choosing this optioncauses the install script to reinitialize the tables containing BusinessObjectsEnterprise data, destroying any existing data. You must choose to reinitializethe database to proceed with the install. In either case, reinitializing the

database does not affect any other tables in that database or schema.

(See Upgrading and Migrating on page 249 for information on performing aBusinessObjects Enterprise upgrade without overwriting existing data.)

Note:

Consult your database server documentation and/or your databaseadministrator if you are unsure of the procedure for creating a newdatabase.

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.

Database requirements

Before you create the relational database that you want to integrate withBusinessObjects Enterprise, consider the following sections that detail whatsettings are required when the relational database is created and whatsettings you should test before beginning your BusinessObjects Enterpriseinstall. The one requirement that applies, regardless of your databases type,is that your relational database be set up to use Unicode character encoding(such as UTF-8).

Note: No additional setup is required for SQL Server.

DB2 database setup requirements

If you are using a DB2 relational database with your BusinessObjectsEnterprise deployment, there are specific settings you need to select when

the relational database is created. It is not sufficient to modify these settingsafter the relational database has been created.

When you create the relational database you will use with BusinessObjectsEnterprise:

Ensure the CMS database is not partitioned.


33/284


Database requirements 2


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 relational 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 XXwith 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 and

configured to build SQL stored procedures. DB2 8.2 does not have thisrequirement. 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.

After you create your database you will need to prepare it for theBusinessObjects Enterprise install. For details, see Preparing your existingdatabase server on page 34. In addition, before you begin the install ofBusinessObjects Enterprise, you must ensure the DB2 environment variables

are set up correctly. For details, see Testing DB2 environment variables onpage 36.

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.

After you create your database you will need to prepare it for theBusinessObjects Enterprise install. For details, see Preparing your existingdatabase server on page 34. In addition, before you begin the install ofBusinessObjects Enterprise, you must ensure the Sybase environmentvariables are set up correctly. See Testing Sybase environment variables onpage 39.


34/284


Preparing your existing database server2


Oracle database setup requirements

For an Oracle database there are no specific parameters, other than thesetting of UTF-8, that are required for BusinessObjects Enterprise to work.

However, before you begin the install of BusinessObjects Enterprise, youmust ensure the Oracle environment variables are set up correctly. For moreinformation, see Testing Oracle environment variables on page 41.

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.

After you create your database you will need to prepare it for theBusinessObjects Enterprise install. For details, see Preparing your existingdatabase server on page 34.

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.

Database type Information required at

install time

Sybase Sybase Server Name

DB2 DB2 database alias

Oracle tnsnames connect identifier


35/284


Preparing your existing database server 2


Note: On UNIX, the Sybase Server Name is a combination of the servername and the port number which is set by your database administrator in theinterfaces file. The database the installation connects to is the defaultdatabase for the user profile. This default database is to is set by the DBA in

the profile of the account from which you will install and run BusinessObjectsEnterprise.

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 32 Sybase database setup requirements on page 33 Oracle database setup requirements on page 34

To prepare your database1. Create a new, empty relational database on your database server.

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

3. Ensure that the new account has permission to create, modify, deletetables and create procedures so that BusinessObjects Enterprise canmodify the database as required.

Note: If you are not the owner of the database, you will need to havepermissions to perform the necessary operations.

4. If you are using Sybase, Oracle, or DB2, ensure the following are set up

before you begin your installation:

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 Server Name, your Oracletnsnames connect identifier, or your DB2 database alias.

The user account and the password authorized to the database.

Database type Ensure this has been

configured

Sybase Sybase Server Name

Oracle tnsnames connect identifier

DB2 DB2 database alias


36/284




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.

For information on how to create a new relational database, consult yourdatabase 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 andConfiguration Guide.

Providing and verifying connectivity to the CMS database

To create tables and write data to your new CMS database, the installationscripts need to establish a connection to the database server. That is, whenyou log on to UNIX with the user name from which you will perform the

installation, the default shell environment must include the appropriatedatabase environment variables and/or initialization files. Only then can theinstallation setup program access the CMS database using your databaseclient software.

The environment variables and/or files required by the installationscriptsdepend upon the type of database server you are running:

Additional database environment variables must be set in order for theinstallation script to use the database client software properly. Before runningthe installation script, test the shell environment of the account from whichyou will install BusinessObjects Enterprise to verify database connectivity and

privileges. See the procedure that corresponds to your database. Testing Sybase environment variables on page 39 Testing Oracle environment variables on page 41 Testing DB2 environment variables on page 36

Testing DB2 environment variables

If you choose to connect to DB2 through a native connection, the installationsearches the current shell for the DB2INSTANCE environment variable. Thisstandard DB2 environment variable must be set in order for the install

script to utilize the DB2 client software.If you are using an existing database, you need to source your databaseclient. For information about this process see Sourcing the script thatidentifies the database environment variables on page 19.

Sourcing the script that identifies the database environment variables can bedone in one of two ways:


37/284




The user who performs a system installation can modify theBusinessObjects Enterprise script setupint.sh to add the command tosource your database client. However, root access is required to executethis script. This script can be found at the following location: /

bobje/init/setupint.sh. This method will source the database for all users.Sourcing the script that identifies the database environment variableson page 19 for information.

Each person with a user installation can modify their profile and add thecommand to source their database environment. This method can bedone anytime.

For example, if an DB2 database was required, an entry would be madein the user profile to source the environment script used by DB2(db2profile). Consult your database documentation for the name of itsenvironment script.

Note: Instead of sourcing the script that identifies the database environmentvariables, you can manually set the environment variables required by yourdatabase. However, if you manually set the environment variables, you willneed to set them again if the system is restarted.

Consult your database documentation and/or your database administrator ifthe account shell environment from which you will install BusinessObjectsEnterprise has not yet been set up for your database client software, or if youare unable to connect successfully to the database.

These steps will test whether the required environment variables are set:

To verify DB2 native connectivity through a database alias

1. Log on to the UNIX server with the user account and password which youwill use to do your install.

Note: This account should already be set up. See Creating an account,a home directory, and a login environment on page 28 for moreinformation on setting up a UNIX account to use when you installBusinessObjects Enterprise.

2. Echo the following environment variables and ensure that their valuescorrespond to your database client software installation.

Variable ValueDB2INSTANCE This variable defines the current DB2 database

instance.

INSTHOME This variable contains the path to the rootdirectory of your DB2 client installation


38/284




This example checks the required variables and shows sample outputvalues.

$ echo $DB2INSTANCE

db2inst1$ echo $DB2DIR/opt/IBMdb2/V7.1$ echo $LD_LIBRARY_PATH/export/home/db2inst1/sqllib/lib$ echo $PATH/usr/bin:/usr/ucb:/etc:.:/export/home/db2inst1/sqllib/

adm:/export/home/db2inst1/sqllib/misc

3. Issue the following command to run the DB2 SQL tool:

db2

4. Issue the following command to connect to the desired database alias:

connect to db_aliasuser accountname using passwordReplace db_aliasand passwordwith the appropriate values. If the shellenvironment has been configured correctly, you are connected to DB2.

5. Issue the following command to ensure that the account has permissionto create tables:

create table sampletable (col_fld char(10) not null)

6. Issue the following command to ensure that the account has permissionto delete tables:

drop table sampletable

7. Type terminate

DB2DIR This variable contains the path to the rootdirectory of your DB2 installation (one level

above the DB2 bin and lib directories).library path The library search path (LD_LIBRARY_PATH on

Solaris and Linux, LIBPATH on AIX, andSHLIB_PATH on HPUX) must include the libdirectory of your DB2 client installation.

PATH The search path must include the bin directoryof your DB2 client installation.

Variable Value


39/284




Testing Sybase environment variables

If you choose to connect to Sybase through a native connection, theinstallation searches the current shell for the SYBASE and SYBASE_OCS

environment variables. These standard Sybase environment variables mustbe set in order for the install script to utilize the Sybase client software.

If you are using an existing database, you need to source the script thatidentifies the database environment variables. For information about thisprocess see Sourcing the script that identifies the database environmentvariables on page 19.

Sourcing the script that identifies the database environment variables can bedone in one of two ways:

The user who performs a system installation can modify theBusinessObjects Enterprise script setupint.sh to add the command to

source your database client. However, root access is required to executethis script. This script can be found at the following location: /bobje/init/setupint.sh. This method will source the database for all users.


For example, if a Sybase database was required, an entry would bemade in the user profile to source the environment script used by Sybase(SYBASE.shorSYBASE.csh). Consult your database documentation forthe name of its environment script.

Note:

Instead of sourcing the script that identifies the database environmentvariables, you can manually set the environment variables required byyour database. However, if you manually set the environment variables,you will need to set them again if the system is restarted.

Consult your database documentation and/or your databaseadministrator if the account shell environment from which you will installBusinessObjects Enterprise has not yet been set up for your databaseclient software, or if you are unable to connect successfully to thedatabase.

These steps will test whether the required environment variables are set:

To verify Sybase native connectivity through a server name

1. Log on to the UNIX server with the user account and password which youwill use to do your install.


40/284




Note: This account should already be set up. See Creating an account,a home directory, and a login environment on page 28 for moreinformation on setting up a UNIX account to use when you installBusinessObjects Enterprise.

2. Echo the following environment variables and ensure that their valuescorrespond to your database client software installation.

This example checks the required variables, and shows sample outputvalues:

$ echo $SYBASE/opt/sybase/12.0$ echo $SYBASE_OCSOCS-12_O$ echo $LD_LIBRARY_PATH/export/home/sybase/12.0/OCS-12_0/lib$ echo $PATH/usr/bin:/usr/ucb:/etc:.:/export/home/sybase/12.0/OCS-

12_0/bin

3. Issue the following command to run the Sybase SQL tool and connect tothe database server:

isql -U user-P password-S servername

Replace user, password, and servernamewith the appropriatevalues. If the shell environment has been configured correctly, you areconnected to Sybase.

4. Issue the following command to ensure that the account has permissionto create tables:

use aps

Variable Value

SYBASE This variable contains the path to the rootdirectory of your Sybase client installation (onelevel above the SYBASE_OCS versiondirectory).

SYBASE_OCS This variable contains the name of the Sybaseversion directory (one level above the Sybase

bin and lib directories).

library path The library search path (LD_LIBRARY_PATH onSolaris and Linux, LIBPATH on AIX, andSHLIB_PATH on HPUX) must include the libdirectory of your Sybase client installation.

PATH The search path must include the bin directoryof your Sybase client installation.


41/284




gocreate table sampletable (def_field char(10))gosp_help sampletablego

5. Issue the following command to ensure that the account has permissionto delete tables:

drop table sampletablegosp_help sampletablego

6. Type quit

Testing Oracle environment variables

If you choose to connect to Oracle through a native connection, theinstallation searches the current shell for the ORACLE_HOME environmentvariable. This standard Oracle environment variable must be set in order forthe install script to utilize the Oracle client software.

If you are using an existing database, you need to source your databaseclient. For information about this process see Sourcing the script thatidentifies the database environment variables on page 19.

Sourcing your database client can be done in one of two ways:

The user who performs a system installation can modify theBusinessObjects Enterprise script setupint.sh to add the command to

source your database client. However, root access is required to executethis script. This script can be found at the following location: /bobje/init/setupint.sh. This method will source the database for all users.


For example, if an Oracle database was required, an entry would bemade in the user profile to source the environment script used by Oracle(oraXXenv.cshororaXXenv.shwhere XXis replaced with theversion number). Consult your database documentation for the name of

its environment script.Note:

Instead of sourcing the script that identifies the database environmentvariables, you can manually set the environment variables required byyour database. However, if you manually set the environment variables,you will need to set them again if the system is restarted.


42/284




Consult your database documentation and/or your databaseadministrator if the account shell environment from which you will installBusinessObje

xir2 bip install unix en

Documents