Business Objects Enterprise XI Release 2 - Installation Guide

BusinessObjects Enterprise XI Release 2 Installation Guide
BusinessObjects Enterprise XI Release 2 Productivity Pack Windows
Patents
Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Copyright 2006 Business Objects. All rights reserved. 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
Trademarks
Copyright Third-party contributors
Contents
Chapter 1 Introduction to BusinessObjects Enterprise XI Release 2 11 What is BusinessObjects Enterprise? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Who should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Business Objects information resources . . . . . . . . . . . . . . . . . . . . . . . 12 Chapter 2 Planning Your Installation 13
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Windows permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Setting up server communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Choosing a server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Choosing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Using MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Using a supported database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Choosing a deployment environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Choosing a development environment . . . . . . . . . . . . . . . . . . . . . . . . 19 Choosing a web application server . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Choosing a Web Component Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 21 Choosing optional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 OLAP Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Desktop Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Crystal Reports Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Web Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Business Process BI Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Choosing an install type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Contents
New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Upgrade installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 DB2 database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Sybase database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Oracle database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 31 MySQL database setup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Preparing your existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Chapter 3 Installing BusinessObjects Enterprise on Windows 35
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Setting up the CMS database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Providing administrative privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Installing Business Objects products on a non-system drive . . . . . . . . . . . 41 New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Expanded installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Expand installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Client tools installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Installing client tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Data Access and Output Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Sample Reports and Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Selecting or deselecting features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Distributed deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Installing only the server and client components . . . . . . . . . . . . . . . . . 67 Installing only the Web Component Adapter . . . . . . . . . . . . . . . . . . . . . 74
Contents
Adding Crystal Enterprise 10 web desktop support . . . . . . . . . . . . . . . 77 Running a custom install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Upgrade installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Silent install parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Verifying your performance management installation . . . . . . . . . . . . 103 Post installation setup for performance management . . . . . . . . . . . . 105 Troubleshooting starting performance management . . . . . . . . . . . . . 105 Chapter 4 Installing Service Pack 2 109
Service Pack 2 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Installing Service Pack 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Chapter 5 Installing the Productivity Pack 111
Productivity Pack upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 What is included in the productivity pack? . . . . . . . . . . . . . . . . . . . . . 112 Business Process BI Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Content Search in InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Distributed installs of Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Feature selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Silent install parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Post install component deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 New or updated WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Chapter 6 Deploying on Tomcat 127
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Deploying with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Chapter 7 Deploying on WebSphere 137
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 138
Contents
Deploying on IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Creating an application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Starting the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Making configuration changes for distributed performance management 143 Changing the classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Setting the heap size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Modifying the PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Checking or changing the assigned port number on WebSphere 5.1 . 147 Checking or changing the assigned port number on WebSphere 6.0 . 147 Creating a new virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Assigning an alias to the virtual host . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Verifying the WebSphere Configuration . . . . . . . . . . . . . . . . . . . . . . . 150 Chapter 8 Deploying on WebLogic 153
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 154 Deploying on BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Copying your performance management InitConfig. properties file . . 159 Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 159 Creating the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Changing the CLASSPATH in WebLogic . . . . . . . . . . . . . . . . . . . . . . 161 Modifying the PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Setting the Java Virtual Machine options for OLAP Intelligence and performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 164 Chapter 9 Deploying on Oracle Application Server 167
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 168 Deploying with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Contents
Configuring the Class Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Changing Memory Allocation Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Copying your performance management InitConfig. properties file . . 173 Setting the PATH environment variable . . . . . . . . . . . . . . . . . . . . . . . 173 Changing the command line options for OLAP Intelligence or performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Preparing afhelp.war for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 175 Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Verifying the Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Chapter 10 Deploying on SAP Web Application Server 179
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 WAR file contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 181 Deploying with SAP Web Application Server . . . . . . . . . . . . . . . . . . . . . . 183 Modifying the PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Creating an EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Deploying the EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Verifying the Web Application Server Configuration . . . . . . . . . . . . . 187 Chapter 11 Importing Objects to BusinessObjects Enterprise 189
Importing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Importing information from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . 191 Importing objects from Crystal Enterprise . . . . . . . . . . . . . . . . . . . . . 192 Importing information from BusinessObjects 5.x or 6.x . . . . . . . . . . . . . . 195 Importing Application Foundation objects . . . . . . . . . . . . . . . . . . . . . 195 Limitations on importing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Before importing from Application Foundation . . . . . . . . . . . . . . . . . . 197 Before importing from BusinessObjects 5.x/6.x . . . . . . . . . . . . . . . . . 198 Importing objects from BusinessObjects 5.x/6.x . . . . . . . . . . . . . . . . 201 Using the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Specifying the source environment . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Specifying the destination environment . . . . . . . . . . . . . . . . . . . . . . . 223 Selecting the type of objects to import . . . . . . . . . . . . . . . . . . . . . . . . 225
Contents
Choosing an import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Updating previously imported objects . . . . . . . . . . . . . . . . . . . . . . . . . 231 Selecting specific objects to import . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Finalizing the import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Using text files with the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Text file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Importing from text files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Chapter 12 Custom SDK Deployments 249
Software Development Kit overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Active Server Pages environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Java Server Pages environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 .NET environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Chapter 13 Upgrading and Migrating 253
What does this section cover? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 What this section does not cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Upgrading from Crystal Enterprise or from BusinessObjects Enterprise . 254 Preparing for upgrading or migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Disabling and stopping servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Upgrading previous versions components . . . . . . . . . . . . . . . . . . . . . 258 Migrating the CMS or APS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Using an existing web desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Importing content from BusinessObjects Enterprise, Crystal Enterprise, or Crystal Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Upgrading other components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Migrating to performance management XI Release 2 . . . . . . . . . . . . . . . . 272 About the Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Migrating the performance management repository . . . . . . . . . . . . . . . . . 273 Migrating schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Migrating rules and named events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Migrating security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Managing rights at the object level in Performance Management XI . 275
Contents
Chapter 14
Uninstalling
277
Uninstalling BusinessObjects Enterprise from Windows . . . . . . . . . . . . . 278 Appendix A Deploying on WebLogic 9.2 with the JDK 1.5 279
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 WAR File contents and context roots . . . . . . . . . . . . . . . . . . . . . . . . . 280 Deploying on BEA WebLogic 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Creating a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Setting the context root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Deploying performance management . . . . . . . . . . . . . . . . . . . . . . . . 285 Setting the Java Virtual Machine options for OLAP Intelligence and performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Setting required variables in startup script . . . . . . . . . . . . . . . . . . . . . 287 Changing the default parser and transformer . . . . . . . . . . . . . . . . . . 289 Adjusting the size of the JVM permanent generation . . . . . . . . . . . . 289 Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Verifying the WebLogic Configuration . . . . . . . . . . . . . . . . . . . . . . . . 292 Appendix B Deploying on Tomcat with the JDK 1.5 293
Modifying Tomcat to use JDK 1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Using a version of Tomcat already running BusinessObjects Enterprise 294 Copying the required Jar file to Tomcat . . . . . . . . . . . . . . . . . . . . . . . 296 Adding the Java Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Deploying the WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 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
Contents
How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Looking for the best deployment solution for your company? . . . . . . . 304 Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Index 307
10
Introduction to BusinessObjects Enterprise XI Release 2
chapter
Introduction to BusinessObjects Enterprise XI Release 2 What is BusinessObjects Enterprise?
What is BusinessObjects Enterprise?

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

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

This guide is intended for the system administrator or IT professional who needs to install BusinessObjects Enterprise. Familiarity with your overall network environment, port usage, your database environment, and your web server software is especially beneficial. For more information about the product, consult the BusinessObjects Enterprise Administrators Guide, the BusinessObjects Enterprise Getting Started Guide, and the BusinessObjects Enterprise Users Guide. Online versions of these guides are included in the docs directory of your product distribution. Once you install BusinessObjects Enterprise, they are also accessible from InfoView, BusinessObjects Enterprises web-based interface.
Business Objects information resources

For more information and assistance, see Appendix C: Business Objects Information Resources. This appendix describes the Business Objects documentation, customer support, training, and consulting services, with links to online resources.
12
Planning Your Installation
chapter
Planning Your Installation Installation overview
Installation overview
BusinessObjects Enterprise provides an open and flexible architecture that supports a multitude of deployment and configuration scenarios. Before you install BusinessObjects Enterprise you should:
Review your system to ensure that it meets the basic requirements for a BusinessObjects Enterprise installation. Ensure that all machines that will be part of your BusinessObjects Enterprise deployment can communicate properly with one another. Decide which BusinessObjects Enterprise components to install and which of your own components to integrate. Determine where the components should be installed. Choose an installation method.
Part of this section focuses on how you should prepare your infrastructure and details considerations you should consider when you set up your environment. Preparations should include:
Setting up server communication Choosing a server location
The other parts of this section list the core software requirements, the choices available to you within the core requirements, and the install methods that you can use when you install BusinessObjects Enterprise. There are some decisions that should be made before you install. These decisions include:
Choosing a deployment environment Choosing a development environment Choosing a web application server Choosing a database server
At the end of this chapter, you will find an installation checklist. You can use this checklist to help ensure you are prepared before you begin your install of BusinessObjects Enterprise.
System requirements
Generally, the following components must be installed and configured correctly before you install BusinessObjects Enterprise:
Java application server (unless you install Tomcat with your installation of BusinessObjects Enterprise)
14
Planning Your Installation Setting up server communication
512 MB RAM minimum, 1 GB recommended 3 GB free disk space Database software that is compatible with the CMS and the Audit database (unless you install MySQL during the BusinessObjects Enterprise installation)
For a detailed list of supported environments, consult the Platforms.txt file included with your product distribution. This file includes specific version and patch-level requirements for web application servers, web browsers, and operating systems. For additional important information that may pertain to your deployment, it is also strongly recommended that you consult the Release Notes included with your product distribution (release.pdf, release.htm, or release.rtf). Note:
BusinessObjects Enterprise requires a database to store information about the system and its users. For details, see Database requirements on page 29 and Preparing your existing database server on page 31. If you are installing on VMWare, ensure your machine name does not include any of the following characters: an underscore, a period, or a slash.
Windows permissions
To successfully install BusinessObjects Enterprise on Windows, the user who runs the setup program must be a member of the local Administrators group. The following are not supported:
Installing on a domain controller. Installing on a machine where the Windows default security settings given to the local Administrators group have been modified.
Setting up server communication

BusinessObjects Enterprise requires a database server and web application server software to be installed and configured. You can either choose to install this software during your installation, or use other supported third-party software. If you choose to use supported third-party database or web application server software, it should be installed before you install BusinessObjects Enterprise. After you complete your install, you will also need to configure the software so it integrates with BusinessObjects Enterprise.
BusinessObjects Enterprise XI Release 2 Installation Guide 15
Planning Your Installation Setting up server communication
In addition, ensure that all BusinessObjects Enterprise machines can communicate properly with one another:
Each BusinessObjects Enterprise machine must be able to communicate over TCP/IP with the machine that runs your Central Management Server (CMS). The CMS is responsible for maintaining a database of information about your BusinessObjects Enterprise system, which other components can access as required. The data stored by the CMS includes information about users and groups, security levels, BusinessObjects Enterprise content, and servers. For more information about the CMS, see BusinessObjects Enterprise Administrators Guide.
Ensure that your database client and server are set up to use Unicode character encoding (such as UTF-8). Consult your database documentation to determine the settings required for a Unicode configuration. For database clients, you must set certain parameters. The DB2 client, for example, must use the DB2CODEPAGE value of 1208. The Sybase database client typically requires the parameter LC_ALL and an appropriate entry in the locale.dat file. When you install your database server, such as Oracle and Sybase, you need to configure the server to use Unicode encoding for the character data types. For other databases, such as DB2, you can create the CMS database with Unicode settings on your existing database server.
If you connect BusinessObjects Enterprise to a web application server, the web application server must be able to communicate with all BusinessObjects Enterprise machines.This communication is enabled by the BusinessObjects Enterprise Software Development Kit (SDK), which is installed when you select either the Java or .NET Web Component Adapters (WCA). If your existing web application server does not install a version of the Java Development Kit (JDK) supported by BusinessObjects Enterprise, you will need to install it. Note: If you are installing BusinessObjects Enterprise in a firewall environment, you will need additional configuration details. See the Working with Firewalls section of the BusinessObjects Enterprise Administrators Guide.
16
Planning Your Installation Choosing a server location
Choosing a server location

When planning your BusinessObjects Enterprise installation, you should also consider where you will place servers:
Your Crystal Reports Page Server, Desktop Intelligence Report Server, Connection Server, Web Intelligence Report Server, Job Servers, and Report Application Server communicate frequently with the database servers containing the data in your published reports. To speed data retrieval and minimize network traffic, place your processing servers close to your database servers (ideally, on the same subnet). If your BusinessObjects Enterprise installation is distributed over a wide geographic region, use server groups to create groups of nearby servers to process reports. The Central Management Server (CMS) stores data about users and groups, security levels, published objects, and servers in the CMS database. The CMS can also maintain a separate audit database of information about user actions. To optimize CMS performance, place your CMS on the same LAN as the database servers that host your CMS database and the BusinessObjects Enterprise audit database. The CMS can be clustered. If you are deploying more than one CMS, ensure each machine that runs a CMS process experiences the same latency to the system database. Note: This guide does not cover how to cluster a CMS. For details on how to configure a CMS cluster after your initial installation, see these sections in the BusinessObjects Enterprise Deployment and Configuration Guide:
Clustering Central Management Servers Adding clustered CMSs to the web.xml file in the BusinessObjects Enterprise Deployment and Configuration Guide.
Consult the following topics in the Managing and Configuring Servers section of the BusinessObjects Enterprise Deployment and Configuration Guide for information on other factors that you may want to consider in planning your BusinessObjects Enterprise installation:
See Working with firewalls for information on how to configure BusinessObjects Enterprise to work with your secured network. See Planning your Deployment for information on deployment configurations, tuning and performance. See Creating accessible reports for information on how to create and distribute reports that meet the needs of people with disabilities.
Planning Your Installation Choosing a server location
See International deployments for information on how to deploy BusinessObjects Enterprise for a multilingual, worldwide audience. On Windows, you can choose to install all BusinessObjects Enterprise components on a drive other than the drive that contains your operating system files. For details, see Installing Business Objects products on a non-system drive on page 41.
Choosing a database server

BusinessObjects Enterprise requires a database (or Oracle schema) to store information about the system and its users. The primary database, which is maintained by the Central Management Server (CMS), is known as the CMS database. A second database will be required if you plan to use BusinessObjects Enterprise Auditor. Before you install, you should choose which supported database server to use. Note:
In earlier releases of Crystal Enterprise, the Central Management Server was called the Crystal Management Server or the Automated Process Scheduler (APS), and the system database was called the APS database. In earlier releases of BusinessObjects, the system database was known as the repository. For more information, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide. For a detailed list of tested database servers, see the platforms.txt file included with your product distribution.
Using MySQL
MySQL database server is an open-source database that provides local data storage. The setup program can install and configure MySQL along with your BusinessObjects Enterprise components. If you already have MySQL installed, the installation program creates the CMS database using your existing database engine. During the installation of BusinessObjects Enterprise, you specify what database server you will use and enter the required parameters for authentication.
18
Planning Your Installation Choosing a deployment environment
Using a supported database server

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

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

BusinessObjects Enterprise supports Active Server Pages (ASP), Java Server Pages (JSP) and .NET applications (ASP.NET). Support for Crystal Server Pages (CSP) was deprecated on the Windows platform in BusinessObjects Enterprise XI. (CSP was deprecated on UNIX platforms in the Crystal Enterprise 10 release.) Note: The following section applies to Crystal Enterprise 10 users only. In the period since CSP was developed, the cross-platform application server market has become dominated by the Java Platform, Enterprise Edition (J2EE) platform and Microsofts ASP.NET. As a result, Business Objects has moved away from the proprietary CSP language and has instead developed tools and applications in ASP.NET and J2EE. What does deprecating CSP mean?
Existing CSP applications will continue to run on Windows (after making minor configuration changes).
New BusinessObjects Enterprise features will not be made available in CSP. You should not develop new custom applications in CSP. You should plan to port existing CSP applications to J2EE or ASP.NET.
For further information on how to port CSP applications, contact Business Objects Global Services.
Choosing an environment for new custom applications

While it will be possible to run CSP applications after CSP has been deprecated, you should not develop new custom CSP applications on that platform. Here are some directions to consider:
Windows platform, IIS web server Consider developing new applications using ASP.NET. (You could also develop new applications in ASP; however, Microsoft is gradually deprecating ASP.)
Windows platform, any supported J2EE web application server You may want to consider developing new applications using J2EE.
If you have an existing custom application that is a slightly modified version of InfoView (or another application supplied by Business Objects), you may want to apply your changes to an updated version of the application. J2EE and ASP.NET versions of InfoView are available in BusinessObjects Enterprise XI. Java Server Pages allow you to develop cross-platform J2EE applications that use BusinessObjects Enterprise objects in conjunction with your own custom objects, or a wide variety of objects from third parties. BusinessObjects Enterprise also includes Primary Interop Assemblies (PIAs) that enable you to use the BusinessObjects Enterprise SDK and Report Application Server SDK with ASP.NET It also includes a set of .NET Server Components which simplify development of custom BusinessObjects Enterprise applications in ASP.NET. Your choice of which web development environment to use to develop your own custom applications will depend largely on your own technology preferences. However, in making this decision, consider the technology directions foreseen by Business Objects.
20
Choosing a web application server

BusinessObjects Enterprise requires a web application server to process the server-side scripts that make up web applications. Before selecting a web application server to use with BusinessObjects Enterprise, assess your current environment and determine the platform on which to deploy BusinessObjects Enterprise. Determine whether you plan to develop custom applications and, if so, which web development environment to use. Note: The term web application server refers to a web server and an application server. Depending upon your needs, you can use one of these options:
Microsoft Internet Information Server (IIS) If you plan to develop custom applications using ASP or ASP.NET, you should use IIS. Note: This option is not available on UNIX.
Java web application servers If you install BusinessObjects Enterprise on Windows and plan to develop custom applications using JSP, you can use any of the supported web servers listed in the Platforms.txt file that is included with your product distribution.If you plan to develop custom applications using the BusinessObjects Enterprise Java SDK, you can use any of the supported Windows web servers listed in the Platforms.txt file that is included with your product distribution.
Note: We recommend that you use ASP, ASP.NET, or JSP for new custom applications, although development of new custom applications in CSP is still supported in BusinessObjects Enterprise XI. For details, see Choosing an environment for new custom applications on page 20.
Choosing a Web Component Adapter

BusinessObjects Enterprise provides a web applicationthe Web Component Adapter (WCA) that allows your web application server to run BusinessObjects Enterprise applications and to host the Central Management Console (CMC). If you want to run the CMC supplied with BusinessObjects Enterprise or run legacy CSP applications, the WCA must be installed on the same machine as your web application server. OLAP Intelligence also requires the installation of the WCA.
Planning Your Installation Choosing optional components
Note: The Web Connector that resided on the web server in earlier versions of Crystal Enterprise is no longer required. Requests are now handled by the web application server, and are passed on to the Web Component Adapter. This solution also replaces the Web Component Server (WCS). There are two versions of the Web Component Adapter:
.NET The .NET Web Component Adapter must be installed on an IIS web application server. Java The Java Web Component Adapter must be installed on a J2EE web application server.
Choosing optional components

Provided that you own the appropriate licenses to the applicable Business Objects products, the following may be installed with BusinessObjects Enterprise XI: OLAP Intelligence, Desktop Intelligence (formerly known as BusinessObjects), performance management, Crystal Reports Explorer, Web Intelligence and BusinessObjects Enterprise Auditor. For information about licenses, contact your Business Objects sales representative. For a list of all available components, see the BusinessObjects Enterprise Architecture section in the BusinessObjects Enterprise Administrators Guide.
OLAP Intelligence
OLAP Intelligence leverages the power of multidimensional OLAP databases to help organizations gain insight and uncover hidden trends in their complex business data. OLAP Intelligences easy-to-use drag-and-drop environment and rich visualization techniques enable users to build and modify analysisfocused Worksheets and create customizable charts that graphically represent the data in workbooks. Through its tight integration with BusinessObjects Enterprise, OLAP Intelligence workbooks can be viewed through an intranet, extranet, or corporate portal. Alternatively, they can be published to BusinessObjects Enterprise. OLAP Intelligence supports the market leading OLAP servers including: Microsoft SQL Server Analysis Services, Hyperion Essbase, SAP Business Information Warehouse (BW), and IBM DB2 OLAP Server.
22
Desktop Intelligence
Desktop Intelligence is an integrated query, reporting, and analysis solution for business professionals that allows users to access data in their corporate databases directly from their desktops. Desktop Intelligence makes it easy to access this data, because users work with it in the business terms that are familiar to them; they dont require knowledge of technical database terms like those used in SQL. Note: This product was previously known as BusinessObjects in release 5.x/ 6.x. Desktop Intelligence is now installed as part of the client install for BusinessObjects Enterprise. It is no longer downloaded from InfoView.
Performance management
Performance management can be applied to any business process where there is a need to view and analyze all the points of measure that define corporate performance, productivity and profitability. Performance management products help users track and analyze key business metrics via management dashboards, scorecards, and alerting. These products also allow goals to be set around metrics, and assigned to ownersaligning people with strategies. These products also support group decision making and analysis via integrated collaboration and workflow capabilities. Performance management allows groups to collaborate and make goal and metric based decisions. Once a decision is reached, users can establish and reuse decision and analysis workflow so others can efficiently analyze and resolve common business problems. Performance management includes the following products:
Dashboard Manager Performance Manager Set Analysis Predictive Analysis Process Analysis
You can specify whether or not to install performance management with your BusinessObjects Enterprise installation. Note:
Performance management products are only available as Java web applications. There are no corresponding products available for .NET.
Performance management was previously known as Application Foundation. Process Analysis was previously known as Statistical Process Control (SPC).
Auditor
Auditor is a web-based product that allows you to monitor and analyze user and system activity. This information provides valuable insight into your BusinessObjects Enterprise deployment, enabling you to optimize your deployment. If you choose to use Auditor, you can choose to configure auditor during or after the installation. For details on how to configure Auditor after the installation completes, see the BusinessObjects Enterprise Auditors guide.
Crystal Reports Explorer

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

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

After you have decided what to install and where to install it, you will decide how to install BusinessObjects Enterprise. The first step is to select either a client or a server installation. When you perform a client install, only the client components are installed; when you perform a server install, both the client and server components are installed. The second step is to choose the install method. BusinessObjects Enterprise offers these choices.
New installation Expand installation Custom installation Upgrade installation Silent installation
The first few choices use the installation wizard to guide you through the installation process. The Silent Installation is done from the command line. Note: Regardless of how you conduct your installation, when the option of different versions exists, you will be given the choice of installing the .NET, the JAVA or both versions of a component.
New installation
Performing a new installation is the most simple way to deploy BusinessObjects Enterprise because all the required client, server, and optional components are installed by default onto one machine. You may want to choose a new installation if:
You have not installed BusinessObjects Enterprise before. You want to install all components on the same machine. You 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, you can scale your system to handle increased usage or to add fault-tolerance. In a horizontally-scaled system, BusinessObjects Enterprise components are installed on multiple machines; in a vertically-scaled system, multiple
BusinessObjects Enterprise server components can run on the same machine. Note that a single server, vertically-scaled system improves the ability of BusinessObjects Enterprise to handle increased usage, but does not increase the fault tolerance of the system. Once BusinessObjects Enterprise is running on one machine, you can run the Expand installation option to add server components, create a CMS cluster, increase available resources, and distribute the processing workload. You may want to choose an expand installation if:
You have already completed your initial install of BusinessObjects Enterprise. You want to add additional BusinessObjects Enterprise servers. You require fault tolerance. You want to improve system performance.
Tip: Consult the Scaling Your System section of the BusinessObjects Enterprise Administrators Guide for information on planning how to best expand your installation to meet the needs of your organization. See Expand installation on page 52 for detailed instructions on how to accomplish your expand installation.
Custom installation
The custom installation allows you to choose which components are installed. You may want to perform a custom installation if you plan to use BusinessObjects Enterprise in a distributed environment. It may be that you have an existing web application server that resides on a different machine than the one that has your BusinessObjects Enterprise core components. A distributed installation has two stages. The first step is done on the machine where the all BusinessObjects Enterprise components except the Web Component Adapter will reside, see Installing only the server and client components on page 67 for more information.The second step is done on the machine where the web server is installed, see Installing only the Web Component Adapter on page 74 for more information. Alternately, you may want to do a custom installation when you want to exclude some components installed by default with the new installation, or install only a limited set of specific components. It is recommended that you run this type of installation only when you are familiar with specific BusinessObjects Enterprise components and their roles. If you are not
26
familiar with specific BusinessObjects Enterprise components and their roles and you do a custom install, you may inadvertently not install a required component. Note: If you have an existing Crystal Enterprise 10 web desktop that you want to continue using with BusinessObjects Enterprise XI, you must install an extra feature to support the older web application. For more information, see Adding Crystal Enterprise 10 web desktop support on page 77. You may want to choose a custom installation if:
You are already familiar with the BusinessObjects Enterprise installation program. Your deployment of BusinessObjects Enterprise servers will be distributed over multiple computers. Perhaps your web application server will be on one machine but other BusinessObjects Enterprise components are elsewhere. You know exactly what components you require. You have disk space constraints. You have customized some of your own applications and you dont want the installation to overwrite them. You have an existing Crystal Enterprise 10 web desktop that you want to continue using.
Silent installation
If you need to perform multiple installations and do not want to interrupt people who are currently working on machines in your system, or if you want to install BusinessObjects Enterprise with your own script, you can use the silent installation command for BusinessObjects Enterprise. A silent installation is one that you run from the command line. The silent installation is not recommended for custom or upgrade installations. The installation options are simplified and do not allow for the same level of customization that is provided in the BusinessObjects Enterprise Setup program. Silent installations are also not recommended for upgrades. For more information on performing a silent installation on Windows, see Silent installation on page 91.
Upgrade installation
If you have an existing installation of Crystal Enterprise 9 or 10, or BusinessObjects Enterprise XI R1, and you performed a full standalone client or server installation of your product, you can upgrade your system to BusinessObjects Enterprise XI R2 directly with the install program. This process will not upgrade your original CMS; This step must be completed after you upgrade your system, see Upgrading and Migrating on page 253. If you cannot upgrade your system because you did not perform a full standalone client install, you will need to uninstall the old components before performing an install. A full standalone server install means during the initial install, you installed the complete feature set onto one machine. This includes all the client components, the server components, the SDKs and either the Java or the .NET Web Component Adapter or Web Component Server. A full standalone client install means you installed all of the client components onto one machine. Note: If either the full client or server set is not detected, you will receive a message informing you that you must uninstall the previous version before you proceed with your install. After you enter the product keycode for your new install, the installation program will detect that you have a previous version installed. You will receive a message that informs you a previous version has been detected and that an upgrade will be performed. The installation program will find the existing versions, replace them with the new BusinessObjects Enterprise XI R2 components and add components new to this release. After you upgrade your installation, you will need to migrate your system data to the new version, and import content from an earlier version of Crystal Enterprise, Crystal Info, or BusinessObjects Enterprise.
Upgrading consists of replacing existing Crystal Enterprise programs and files with the latest BusinessObjects Enterprise versions. Copying the contents of the original input root directory into the root directory that the new Input File Repository Server is already configured to use, or reconfiguring the new Input and Output File Repository Servers to use the old input and output root directories. Migrating consists of copying data from your old CMS or Automated Process Scheduler (APS) database to a new Central Management Server (CMS) database, while at the same time updating the database schema to the latest version.
28
Planning Your Installation Database requirements
Note: Do not attempt to use your BusinessObjects Enterprise XI R1 CMS to host your BusinessObjects Enterprise R2 deployment. This will result in the destruction of your existing content.
Importing consists of copying selected objects (reports, users, groups, and so on) and instances from one system to another.
For more information on migrating from Crystal Enterprise 9 or 10, or BusinessObjects Enterprise XI R1, see Upgrading and Migrating on page 253. This guide does not cover describes how to migrate from the following versions:
BusinessObjects version 5.x BusinessObjects version 6.x

WebIntelligence 2.x through 6.5.x
For further information on these topics, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide. If you require further assistance in upgrading, particularly large-scale and/or mission-critical deployments, or in migrating customized reporting applications, it is recommended that you contact a Business Objects services consultant, who can then assess your reporting environment and assist in the planning or execution of the upgrade or migration.
MySQL database setup requirements on page 31 Note: If you have a previous release of BusinessObjects Enterprise you cannot use your database from a previous release for BusinessObjects Enterprise XI Release 2; You must create a new database for this release. If you use a database from a previous release, you will . See Upgrading and Migrating on page 253 for details.
Database requirements
Before you create the database that you want to integrate with BusinessObjects Enterprise, consider the following sections that detail what settings are required when the database is created and what settings you should test before beginning your BusinessObjects Enterprise install.
Planning Your Installation Database requirements
DB2 database setup requirements

If you are using a DB2 database with your BusinessObjects Enterprise deployment, there are specific settings you need to select when the database is created. It is not sufficient to modify these settings after the database has been created. When you create the database you will use with BusinessObjects Enterprise:
Ensure the CMS database is not partitioned. If your DB2 CMS database is partitioned, you will have problems creating the CMS database. Note: This requirement does not apply to the Audit database. If you want, you can use a partitioned DB2 database for the Audit database.
Create the database with the specific settings.

Collating Sequence = "Identity" Codeset = "UTF-8" Territory = "XX"
If your DB2 database does not have the correct collating sequence setting, the users and usergroup objects may not sort properly in the Central Management Console. Replace XX with the code that is appropriate to your code set and codepage for your location. Consult your DB2 documentation for specifics. Note: If you are using DB2 8.1, you require a C compiler that is installed and configured to build SQL stored procedures. DB2 8.2 does not have this requirement. SQL stored procedures are used in BusinessObjects Enterprise when users are added to groups in the CMS. Please consult the DB2 documentation for details on how to configure the C compiler for SQL stored procedures, and for determining what version of the C compiler is supported on your platform.
Sybase database setup requirements

If you are using Sybase, when you create your database for the CMS, ensure the page size is set to 8 KB. Note: The Sybase database default page size is 2KB which is too small for CMS. For CMS to run optimally, the page size must be 8KB. The page size is set up during the database creation and it cannot be changed after the database is set up.
30
Planning Your Installation Preparing your existing database server
Oracle database setup requirements

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

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

After you have created your database, and before you install BusinessObjects Enterprise, you or your database administrator need to prepare your own database server so the CMS can connect to it. During your installation, you will be asked whether you want to install MySQL or use an existing database. If you specify that you will you use an existing database, you will be asked for details about your database. Although you are required to provide the details about your database during the installation, you will not be asked to provide your database name unless you are using an existing version of MySQL. This table summarizes the information you will be required to enter to identify your database during the installation if your are using SQL Server, Sybase, Oracle, or DB2.
I
Database type SQL Server Sybase DB2 Oracle
Information required at install time Data Source Name Sybase Service Name DB2 alias name tnsname
Note: The Sybase Service name is a combination of the host name and the port number which is set by your database administrator in the file sql.ini.
Planning Your Installation Preparing your existing database server
Prerequisites to database preparation

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

1. 2. 3.
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 Create a new, empty database (or Oracle schema) on your database server. Create a new user and assign it a secure password. Ensure that the new account has permission to create, modify, delete tables and create procedures so that BusinessObjects Enterprise can modify the database as required. Note: If you are using Oracle, and you dont own the schema created for for the CMS or Audit database, you must have relative permissions to the schema.
4.
If you are using Sybase, Oracle, or DB2, ensure the following are set up before you begin your installation:
I
Database type Sybase Oracle DB2
Ensure this has been configured Sybase service name tnsname name DB2 alias
During the install, you will be asked for information regarding your database. 5. Record the these details as they will be required during your install:
The name of your database, your Sybase service name, your Oracle tnsname, 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 Installation Checklist at the end of this chapter so the information is available when you install.
32
Planning Your Installation Installation checklist
For information on how to create a new database (or Oracle schema), consult your database server documentation or your database administrator. For information on how to migrate your initial CMS database to another supported database server later, see the BusinessObjects Enterprise Deployment and Configuration Guide. If you are using an existing MySQL database, ensure the following variable is set up for the user who will install BusinessObjects Enterprise XI R2: MYSQL_HOME If this variable is not set up, and you have specified that you are using an existing MySQL database, the installation will not proceed and you will receive an error message. Consult the documentation for MySQL for information on how to configure the MySQL.
Installation checklist
o o Have you tested that all machines that will run BusinessObjects Enterprise can communicate properly? Have you tested the database connection between the machine where your CMS database will reside and where the Central Management Server will be installed? Have you decided which database to use with BusinessObjects Enterprise? If you are using your own database server, have you created a database for the CMS? If you plan to connect remotely to install, have you ensured your terminal setting is set to VT100 before beginning the installation? If you plan to use Auditor, have you created an auditing database? Have you created a userid and password, with access to your existing database (if you are integrating your existing database server software), so that the installation can access your database to configure the CMS database? Have you made sure you can log on to the database with the ID and setup tables? Have you ensured that any existing database you will connecting to has been configured correctly? Have you verified you are using a supported locale? Have you decided whether or not you will develop custom applications? Have you decided what web application server to use?
o o o o o
o o o o o
Planning Your Installation Installation checklist
o o o o
Have you made sure your existing web application server has the JDK installed? If you are not using Tomcat, is your web application server already installed and configured? Have you chosen which Web Component Adapter you want to install? If you are installing on VMWare, have you ensured your machine name does not include any of the following characters: an underscore, a period, or a slash?
34
Installing BusinessObjects Enterprise on Windows
chapter
Installing BusinessObjects Enterprise on Windows Installation overview
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, client and Web Component Adapter on a single machine. You can install Tomcat with your install, or install BusinessObjects Enterprise on a machine that is already running as a web server. This provides the quickest way to install BusinessObjects Enterprise.
Custom installation The Custom installation option allows you to install specific features rather than installing everything by default. This allows you to distribute the BusinessObjects Enterprise components across multiple machines without installing components you dont require on each machine. For example, You can install the BusinessObjects Enterprise server and client components on one machine, and use another machine that already has your existing web application server and simply install the Web Component Adapter of your choicewithout installing the core BusinessObjects Enterprise components on the web application server itself. For more information on using the custom install to do this, see Custom installation on page 61. Alternately, if you are already familiar with BusinessObjects Enterprise, and familiar with the components and their roles, you can perform a custom 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 are already familiar with BusinessObjects Enterprise. If you are not familiar with specific BusinessObjects Enterprise components and their roles and you do a custom install, you may inadvertently not install a required component. You may instead want to follow the steps outline in, Installing only the server and client components on page 67 and Installing only the Web Component Adapter on page 74, which are more detailed.
Expand installation An expanded installation is done after your initial install of BusinessObjects Enterprise. This type of install allows you to scale your deployment of BusinessObjects Enterprise by installing additional
36
BusinessObjects Enterprise servers to meet the demands of your enterprise. How you choose to expand your system depends largely upon your current configuration and your reporting requirements. This section, Expand installation on page 52, provides the steps to expand installation. However, before you expand your installation, it is strongly recommended that you consult the BusinessObjects Enterprise Deployment and Configuration Guide for general scalability considerations, for sample configurations, and for information about CMS clustering.
Client tools installation overview Although most end users interact with BusinessObjects Enterprise over the web, client tools are also provided as stand-alone Windows applications:
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, or BusinessObjects Enterprise XI, and you performed a full standalone client or server installation of your product, you can upgrade your system to BusinessObjects Enterprise XI Release 2 directly. A full standalone server install means during the initial install, you installed the complete feature set onto one machine. This includes all the client components, the server components, the SDKs and either the Java or the .NET Web Component Adapter or Web Component Server. A full standalone client install means you installed all of the client components onto one machine. If either the full client or server set is not detected, you will receive a message informing you that you must uninstall the previous version before you proceed with your install.
37
Note: This guide does not cover describes how to migrate from the following versions:
BusinessObjects version 5.x BusinessObjects version 6.x WebIntelligence 2.x through 6.5.x
For further information on these topics, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide.
38
Installing BusinessObjects Enterprise on Windows System requirements
Silent installation Experienced administrators can use the silent installation to install from the command line. It is recommended that you run this installation when you need to install quickly on multiple machines. You can also incorporate the silent installation command into your own build scripts.
Tip: If you plan to use Web Intelligence documents, you may want to publish the following user guides to BusinessObjects Enterprise, and make them available to your users. They are available as PDFs in the docs directory of your 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.txt file included with your product distribution. This file includes specific version and Service Pack requirements for web servers, web browsers, web application servers, databases, and operating systems. For additional important information that may pertain to your deployment, it is also strongly recommended that you consult the Release Notes included with your product distribution (release.pdf, release.htm, or release.rtf). Generally, however, the following components must be installed and configured correctly before you install BusinessObjects Enterprise:
Database server for the CMS, if you do not use MySQL installed by the installer. 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 store information about the system and its users. By default, the Setup program installs and configures its own MySQL database if necessary. MySQL is a
39
Installing BusinessObjects Enterprise on Windows System requirements
client/server data engine that provides local data storage and is compatible with Microsoft SQL Server. CMS clustering is automatically supported by the default MySQL database. Alternatively, you can connect your CMS directly to your preferred database server without installing MySQL. Then set up the appropriate database client software or ODBC Data Source Name (DSN). Consult your local database administrator or database system documentation for details. You can migrate this initial CMS database to another supported database server later. For details, see Configuring the intelligence tier in the BusinessObjects Enterprise Administrators Guide. Note:
See the Platforms.txt file included with your product distribution for a complete list of tested database software and version requirements. Ensure that your database server is set up to use Unicode character encoding (such as UTF-8). Consult your database documentation to determine the settings required for a Unicode configuration. For database servers such as Oracle and Sybase, during installation you need to configure the server to use Unicode encoding for the character data types. For other databases, such as DB2, you can create the CMS database with Unicode settings on your existing database server. Before installing BusinessObjects Enterprise atop an existing installation of MySQL or Microsoft SQL Server, you need to complete several preparatory steps before running the BusinessObjects Enterprise setup program.
Setting up a database account for BusinessObjects Enterprise

To administer the CMS database, you need to set up a database account. If you choose to install MySQL when you install BusinessObjects Enterprise, you will be prompted during installation to set up this account. If you plan to use your own database, please complete these steps before you install BusinessObjects Enterprise. 1. 2. To set up a database account for BusinessObjects Enterprise Create or select a user account that provides BusinessObjects Enterprise with the appropriate privileges to your database server. Verify that you can log on to your database and carry out administrative tasks using the account you set up for use by the CMS.
40
Installing BusinessObjects Enterprise on Windows Installing Business Objects products on a non-system drive
Providing administrative privileges

You must log on to the local machine as an Administrator when you install BusinessObjects Enterprise XI.
Meeting network requirements

When installing BusinessObjects Enterprise on multiple machines, ensure that each target machine is able to communicate over TCP/IP with the machine that is running as your CMS. In particular, your web server must be able to communicate 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 Firewalls section of the BusinessObjects Enterprise Administrators Guide.
Installing Business Objects products on a non-system drive

You can install BusinessObjects Enterprise on any drive on your machine. The Setup program installs BusinessObjects Enterprise files to the drive that you specify and also installs some files in the \system32 folder. There is one exception to this rule. If you previously installed another Business Objects product, the BusinessObjects Enterprise Setup program automatically uses the existing common directory for any shared Business Objects product files that it adds. If this common directory is on the system drive (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, install BusinessObjects Enterprise first. All Business Objects products that you install subsequently will use this same non-system drive for their shared files.
New installation
This installation scenario offers the quickest way to install BusinessObjects Enterprise. Once you have set up your web server software, run the New installation from the BusinessObjects Enterprise Setup program. When you perform this default installation, all the client and server components that your product key authorizes you to install are installed on the local machine. The Web Component Adapter (WCA) is also installed. You
41
Installing BusinessObjects Enterprise on Windows New installation
can automatically create a MySQL database for the CMS, and you can install the Tomcat application server. Default user and group accounts are created, and sample reports are published to the system. When the installation is complete, 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 up before you install. For details, see Setting up the CMS database on page 39. 1. To install all components Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue. Note: When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically. 2. 3. 4. 5. 6. Select which language to install from the list, and then click OK. Click Next. Click I accept the License Agreement, and then click Next. Choose Perform Server Installation, and then click Next. Fill out the Full Name and Organization fields.
7.
Enter your product keycode(s)
42
If you want to install BusinessObjects Enterprise, but not performance 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 a digital format. b. Leave the check box beside Install Performance Management empty, then click Next.
If you want to install BusinessObjects Enterprise and performance management, which includes Dashboard Manager, Performance Manager, Set Analysis, Predictive Analysis and Process Analysis: a. Enter the BusinessObjects Enterprise product keycode in the first Product Keycode field. Enter one of the performance management keycodes in the second Product Keycode field. The performance management product key you type here only enables that one product. To enable other performance management products, you need to enter the license keys for those products in the Central Management Console (CMC) after the installation is complete. To find out how to do this, see the BusinessObjects Enterprise Administrators Guide. d. Click Next.
b. Click the Install Performance Management check box. c.
8.
Specify the directory where you want to install, or accept the default location, and then click Next.
43
9.
Choose whether you want to install MySQL or use an existing database server.
If you want to install MySQL: a. c. Verify New is selected. Click Next. b. Select Install MySQL Database Server. Note: Later in the installation you will be prompted to specify the password for MySQL root user. You will also be prompted to enter a password for the user account BusinessObjects that accesses the CMS database.
If you want to use an existing database server: a. c. Select New. Click Next. b. Select Use an existing database server. Note: Later in the install you will be prompted to specify the type of database you will use and the authentication details for the CMS and Auditing database.
44
10. If you entered a keycode for performance management, decide when you want 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 Name and Password fields. Note: By default, this is the user account for the operating system where performance management is installed (for example, the NT user account).
Note: If you want to provide the required information later, check Leave it blank. I will configure it after installation.
45
11. If you chose to install MySQL, specify the configuration for MySQL Database Server.
.
a. b. c. d.
Enter the port number. Enter and confirm the password that will be used by MySQLs root user account. Accept the default user name to access the CMS database or enter a new user name to override the default name. Enter and confirm the password that will be used to access the CMS database, and then click Next.
Note: The setup program will configure the CMS to connect to its system database using the account and the password you create here. 12. If you chose to use an existing database server, specify the configuration for the CMS database and the Auditing database, if you will be using one
46
Note: This must be a new DSN or database specifically created for BusinessObjects Enterprise XI Release 2. Do not specify the name of an existing 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 Source tab.
47
c.
Select the data source name you created for the CMS from the Data Source Name field, and then click OK. The SQL Server Login window will appear.
.
d. Enter the user id and password for the data source, and then click OK. e. If you plan on using Auditing, select Auditing database and repeat the previous four steps for the Auditing database, and then click Next; otherwise, click Next.
Note: This database should have been set up prior to install. See Setting up a database account for BusinessObjects Enterprise on page 40.
For Oracle: a. c. Select Oracle. Enter the credentials for the server in the Username and Password fields. b. Enter the Oracle tnsname in the Server field.
d. If you plan on using Auditing, select Auditing database and repeat the previous four steps for the Auditing database, and then click Next; otherwise, click Next.
For DB2: a. c. Select DB2. Enter the credentials for the server in the Username and Password fields. b. Enter the DB2 alias in the Server field.
d. If you plan on using Auditing, select Auditing database and repeat the previous four steps for the Auditing database, and then click Next; otherwise, click Next.
For MySQL a. Select MySQL.
48
b. Enter the database name in the Database field for the CMS database. c. e. f. Enter the database server name in the Server field. Enter the credentials for the server in the UserName and Password fields. If you plan on using Auditing, select Auditing database and repeat the previous four steps for the Auditing database, and then click Next; otherwise, click Next. Select Sybase. Enter the credentials for the server in the UserName and Password fields. d. Enter the port being used by MySQL in the Port field.
For Sybase: a. c. b. Enter the Sybase service name in the Server field.
d. If you plan on using Auditing, select Auditing database and repeat the previous four steps for the Auditing database, and then click Next; otherwise, click Next. Tip: For Sybase, you do not enter the database name. BusinessObjects Enterprise uses the Sybase service name, which specifies which machine and port the database server is on, and the default database name associated with the users profile. 13. Choose a Web Component Adapter.
49
If you want to use a Java WCA and use your own Java application server: a. c. Select Java application server. Deselect the IIS ASP.NET check box, and then click Next. b. Click Use preinstalled Java application server.
If you want to use a Java WCA and have the installation install Tomcat: a. c. Select Java application server. Deselect IIS ASP.NET,and then click Next. Clear the Java application server check box. Accept the default or select the web site on which to deploy the WAR file. b. Click the Install Tomcat application server button.
If you want to use the IIS WCA: a. c. b. Select IIS ASP.NET,and then click Next.
Note: If you have published other web sites than the default web site with IIS, you can select it here.
If you want to use both the Java and IIS WCA: a. Make sure both Java application server and IIS ASP.NET are selected.
b. Accept the default or select the web site on which to deploy the WAR file. Note: If you have published other web sites than the default web site with IIS, you can select it here. a. Select either Use preinstalled Java application server or Install Tomcat application server, and then click Next.
50
14. Configure Tomcat if you chose to install it.; otherwise, skip this step.
Accept the defaults or change the default location for the Tomcat installation and/or the following ports, and then click Next.
The Connection port The Shutdown port The Redirect port Note: If you are installing BusinessObjects Enterprise XI on the same machine as a BusinessObjects Enterprise 6.x deployment, do not use the default port number 8080. This port may already be in use for an other deployment.
15. Click Next to begin the installation.
51
Installing BusinessObjects Enterprise on Windows Expanded installation overview
Expanded installation overview

Once BusinessObjects Enterprise is running on one machine, you can add server components, create a CMS cluster, increase available resources, and distribute the processing workload. This process is know as expanding your existing system. How you expand your system depends largely upon your current configuration and your reporting requirements. This section provides the steps to running the Expand installation. It is strongly recommended that before you expand your installation, you consult the BusinessObjects Enterprise Administrators Guide for sample configurations, general scalability considerations, information about CMS clustering, and so on. Note: If you are adding another CMS, first set up the appropriate database client software or ODBC Data Source Name (DSN) on the local machine. The new CMS must connect to the CMS database in the same manner as the existing CMS. Also ensure that you have the database user name (Login ID) and password that the existing CMS uses to connect to the CMS database. If you are unfamiliar with CMS clusters, see the BusinessObjects Enterprise Administrators Guide.
Expand installation
After you have completed your initial install of BusinessObjects Enterprise and determined what additional servers your installation requires, use the expand installation option to scale your system. You can either do an expand installation on your primary BusinessObjects Enterprise machine or on a secondary machine
A primary machine is ne that has already had the setup program run on it. A secondary machine is one that has never had the setup program run on it.
Expanding BusinessObjects Enterprise on the secondary machine

1. To expand an existing system on a secondary machine Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue.
52
Note: When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically. 2. Select which language to install from the list, and then click OK. In a few moments you will see the Welcome to BusinessObjects Enterprise Installation Wizard dialog. 3. 4. 5. 6. 7. Click Next. Click the I accept the License Agreement button on the License Agreement dialog, and then click Next. Choose Perform Server Installation on the Select Client or Server Installation dialog, and then click Next. Fill out the Full Name and Organization fields. Enter your product keycode(s)
If you only want to install BusinessObjects Enterprise: a. c. Enter its product code in the first Product Keycode field. Click Next. b. Clear the check box beside Install Performance Management.
If you are also installing performance management which includes Dashboard Manager, Performance Manager, Set Analysis, Predictive Analysis and Process Analysis: a. Enter the BusinessObjects Enterprise product keycode in the first Product Keycode field.
b. Enter one of the performance management keycodes in the second Product Keycode field. The performance management product key you type here only enables that one product. To enable other performance management products, you need to enter the license keys for those products in the Central Management Console (CMC). To find out how to do this, see the BusinessObjects Enterprise Administrators Guide. c. 8. 9. Click Next. Specify the directory where you want to install, and then click Next. Click Expand, and then click Next.
53
The Expand Options dialog box appears.
Note:
The option to add performance management servers will not be displayed on the Expand Options screen unless you entered a kedycode for performance management on the User Information screen. If you are performing a distributed install of performance management, that is, an install where performance management is not on the same machine as the core BusinessObjects Enterprise servers, there are additional configuration steps required. See Performing a distributed install of performance management on page 75 for further information. In addition, see Deploying the Performance Management Framework for further details on distributed performance management configurations.
10. Type the name of the machine that is currently running as your CMS in the Existing CMS Name field. 11. Select the check boxes that correspond to the servers that you want to add to the local machine and register with the existing CMS. Clear the remaining check boxes. Note: The options available to you include some common server combinations. For instance, you can install a new CMS and cluster it with the existing CMS by selecting only the CMS check box. Or, you can increase the report-processing capabilities of your system by selecting the Processing Servers check box, which adds both a Job Server and a Page Server to the local machine.
54
Tip: For greater control over the individual components that are installed, perform a Custom installation. For details, see Custom installation on page 61.
55
12. Select the Enable servers upon install check box. If you choose not to enable the servers immediately, use the Central Configuration Manager (CCM) to start the servers and then to enable them. 13. If you entered a keycode for performance management and selected EPM on the Expand options screen, decide when you want 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 Name and Password fields. Note: By default, this is the user account for the operating system where performance management is installed (for example, the NT user account).
If you want to provide the required information later, check Leave it blank. I will configure it after installation. If you chose to add an additional CMS, the CMS Database Information dialog box appears. If you cleared the CMS check box, skip the next step.
14. Click Next.
56
15. Specify the database connection type that the CMS must use to connect to the existing CMS database:
For SQL Server. a. Select SQL Server, and then click Browse. The Select Data Source dialog appears.
b. Click on the Machine Data Source tab.
57
c.
Select the datasource name you created for the CMS from the Data Source Name field, and then click OK. The Server Login window will appear.
.
d. Enter the userid and password for the datasource, and then click OK. e. Click Next. Select Oracle. Enter the credentials for the server in the User Name and Password fields.
For Oracle: a. c. b. Enter the Oracle tnsname in the Server field.
d. Click Next.
For DB2: a. c. Select DB2. Enter the credentials for the server in the User Name and Password fields. b. Enter the DB2 alias in the Server field.
d. Click Next.
For MySQL a. Select MySQL. b. Enter the database name in the Database field for the CMS database. c. e. f. Enter the database server name in the Server field. Enter the credentials for the server in the User Name and Password fields. Click Next. Select Sybase. d. Enter the port being used by MySQL in the Port field.
For Sybase: a.
58
b. Enter the Sybase service name in the Server field. c. Enter the credentials for the server in the User Name and Password fields.
d. Click Next. Tip: For Sybase, you do not enter the database name. BusinessObjects Enterprise uses the Sybase service name, which specifies which machine and port the database server is on, and the default database name associated with the users profile. 16. Click Next to start the installation. The installation of files begins immediately. When the installation program has finished copying files, the final setup screen appears. 17. Click Finish and, if prompted, restart the local machine.
Expanding BusinessObjects Enterprise on the primary machine

1. 2. 3. To expand BusinessObjects Enterprise on the primary machine Open the Control Panel. From the Start Menu select Settings > Control Panel. Click Add/Remove Programs. Select BusinessObjects Enterprise XI Release 2, and then click Change. The Application Maintenance screen will appear.
4. 5. 6.
Select Modify, and then click Next. Expand Server components, and then Servers. Verify the server you want installed are selected.
59
Installing BusinessObjects Enterprise on Windows Client tools installation overview
7.
Remove any servers you dont want installed. Left-click on the icons beside the server names you dont want, and select Entire feature will be unavailable. Click Next. Click Next to start the installation.
8. 9.
Client tools installation overview

This section shows you how to perform a Client installation that installs only the client tools on the local machine. These tools include:
The Publishing Wizard The Import Wizard The Migration Wizard The Business View Manager Desktop Intelligence Universe Designer Software Development Kits (SDKs) Report Conversion Tool Desktop Intelligence Universe builder
These client tools are not needed by users who access InfoView or the Central Management Console (CMC) administrative web application. Rather, these additional tools are provided for users who are responsible for publishing or creating multiple reports or for moving objects between systems. Some of these tools are used for migration of existing documents from earlier product versions or creating new documents. Note: The Client installation does not generally require a product activation keycode. However, Desktop Intelligence does require that a key entered in the CMC after the install completes to enable the content type.
Installing client tools

Follow these steps if you want to install all the client tools in one step. If you want to install only specific client tools, perform a custom install. For more information see, Running a custom install on page 78.
60
Installing BusinessObjects Enterprise on Windows Custom installation
1.
To install the client tools Run setup.exe from the root directory of your product distribution unless Autoplay is enabled for your CD-ROM drive. When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically.
2.
Select which language to install from the list, and then click OK. In a few moments you will see the Welcome to BusinessObjects Enterprise Installation Wizard dialog.
3. 4. 5. 6. 7.
Click Next. Click the I accept the License Agreement button on the License Agreement dialog, and then click Next. Select Perform Client Installation; then click Next. Specify the location to install, in the Directory Selection dialog box, and then click Next. Click Next. The installation of files begins immediately. When the installation program has finished copying files, follow any additional instructions that appear.
Custom installation
The Custom installation option allows you to install specific features and check the amount of disk space required by each feature. You may choose to use the Custom installation for various reasons:
When you want your BusinessObjects Enterprise deployment to be distributed across different servers. When you want to install support for the Crystal Enterprise 10 Desktop. When you are familiar with BusinessObjects Enterprise and know exactly which components you need to install on any particular machine.
Note: Note: See the BusinessObjects Enterprise Deployment and Configuration Guide for information about scaling your deployment across multiple machines. The top level of the Custom installation tree has four different categories:
Client Components
61
Server Components Data Access and Output Formats Sample Reports and Help
Client Components
The Client Components contain these selections:
Business Objects Data Source Migration Wizard Business View Manager Report Conversion Tool Business Objects Import Wizard Business Objects Publishing Wizard Universe Designer Developer Components Note: The Developer Components include the .NET, the COM and the Java SDKs plus BusinessObjects Enterprise Web Services. Each of these components can be individually selected or deselected.
Desktop Intelligence
Server Components
The following list details what the Server Components contain. For further explanation of what these servers do, please consult the BusinessObjects Enterprise Architecture chapter of the BusinessObjects Enterprise Administrators Guide.
Central Configuration Manager This is the configuration tool used to start, stop, add, delete and configure servers in BusinessObjects Enterprise. This tools is also used after installation to configure auditing, or to change which data source is used for either the CMS or the auditing database.
Mapping Support Installs the necessary components for building interactive geographic maps in Crystal Reports. Servers These sub selections are available:
Crystal Reports Cache Server Central Management Server
62
Note: Auditor and MySQL are available beneath the CMS.
Event Server Input File Repository Server Output File Repository Server Crystal Reports Page Server Performance Management Servers Note: The MySQL Sample Repository for performance management is available as a sub-selection. Report Application Server Job Servers Web Component Adapters
Both the .NET and Java versions of the Web Component Adapters are available. BusinessObjects Enterprise provides a web applicationthe Web Component Adapter (WCA) that allows your web application server to run BusinessObjects Enterprise applications and to host the Central Management Console (CMC). If you want to run the CMC supplied with BusinessObjects Enterprise or run legacy CSP applications, the WCA must be installed on the same machine as your web application server. OLAP Intelligence also requires the installation of the WCA.
Note: Tomcat, which is a sub selection beneath the Java Web Component Adapter, is selected by default i although you can also choose to deselect it so that it is not installed.
Web Intelligence Report Server Desktop Intelligence Servers
Data Access and Output Formats

Data access and output formats installs the necessary drivers and files to provide access to a broad range of data sources and export to a broad range of file formats. Output formats are the components required export or save Business Objects documents to these formats:
Character separated format Disk Rich Text Format XML
63
Installing BusinessObjects Enterprise on Windows Selecting or deselecting features
Adobe PDF Text Excel Word Crystal Reports
Sample Reports and Help

These components are included:
Sample Reports There reports are found in the Report Samples folder. Included are sample reports for Crystal Reports, a BIAR file that includes Web Intelligence reports as well as the universe for those sample reports.
Help This help is the html help for the product including the BusinessObjects Enterprise Administrators Guide, InfoView Users and the Business Objects Developer help library, which is available from the Start menu under BusinessObjects Enterprise. Note: The specific help related to an individual component is bundled with the component. For example, if you install the Publishing Wizard or the Import Wizard you will get the .chm help.
Selecting or deselecting features

The Select Features dialog box is the window where you select and deselect the options you want installed when you choose a custom installation.In the Select Features dialog box, the icons in the feature tree indicate whether the feature and its subfeatures will be installed or not:
64
A white icon means that the feature and all its subfeatures will be installed. A shaded icon means that the feature and some of its subfeatures will be installed. A red X means that the feature or subfeature is either unavailable or will not be installed.
To select the configuration and location of a feature or subfeature, click its icon. Use the following table to determine your installation options for each feature or subfeature: Type of feature installation Will be installed on local hard drive Description of what is installed
Installs the feature on the hard drive you specified in the Setup program. Uses typical installation settings to install some of the features subfeatures to the hard drive you specified earlier. Installs the feature and all of its subfeatures on the hard drive you specified earlier. Neither the feature nor its subfeatures are installed.
Entire feature will be installed on local hard drive Entire feature will be unavailable
Note: Subfeatures are listed below each feature. A subfeature can have a different type of installation than its parent feature.
65
Distributed deployments
If you plan to use BusinessObjects Enterprise with an existing web application server that resides on a different machine than where BusinessObjects Enterprise is installed, you will need to install the client and server components in one step, then install the WCA in another. This type of installation allows you to integrate BusinessObjects Enterprise with your existing web application serverwithout installing the core BusinessObjects Enterprise components on the web application server itself. You may deploy BusinessObjects Enterprise XI processes and performance management XI processes on separate servers in a distributed deployment. However, since the performance management setup writes to the WAR file, you must run the performance management setup on the server on which the WAR file is deployed. For information on the WAR file, refer to the section related to your chosen application server. Note: If you will be using OLAP Intelligence, the WCA must be installed.
66
This type of installation has two stages:
The first step, installing the server and client components, is done on the machine where the BusinessObjects Enterprise components will reside. This step needs to be performed first because the CMS is configured during this stage. The second step, installing the Web Component Adapter, is done on the machine where the web server is installed. During the second stage, you will be prompted to enter the name of the existing CMS that you configured during the first step.
Installing only the server and client components

Install the server and client components onto a machine that you have set aside for use by BusinessObjects Enterprise. When you perform this installation, the client and server components are installed, the default user and group accounts are created, and the sample reports are published to the system. When the installation is complete, the servers are started as services on the local machine. Note: When you install only the client and server components, neither Tomcat nor the WCA is installed. See Installing only the Web Component Adapter on page 74 for details on either of the following:
If you want to install the WCA to connect with your existing web server on a separate machine. If you want to install Tomcat and the WCA on the machine designated as you web server. To install the client and server components Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue. When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically.
1.
2.
Select which language to install from the list, and then click OK. In a few moments you will see the Welcome to BusinessObjects Enterprise Installation Wizard dialog.
3.
Click Next.
67
4. 5. 6. 7.
Click I accept the License Agreement on the License Agreement dialog, and then click Next. Choose Perform Server Installation on the Select Client or Server Installation dialog, and then click Next. Fill out the Full Name and Organization fields. Enter your product keycode(s)
If you are also installing performance management which includes Dashboard Manager, Performance Manager, Set Analysis, Predictive Analysis and Process Analysis. a. Enter the BusinessObjects Enterprise product keycode in the first Product Keycode field.
b. Enter one of the performance management keycodes in the second Product Keycode field. The performance management product key you type here only enables that one product. To enable other performance management products, you need to enter the license keys for those products in the Central Management Console (CMC). To find out how to do this, see the BusinessObjects Enterprise Administrators Guide. c. 8. 9. Click Next. Specify the directory where you want to install, and then click Next. Select Custom and then click Next.
10. Expand Server Components on the Select Features dialog, and then expand Servers. 11. Scroll down until you find Web Component Adapters. 12. Left-click on the icon beside Web Component Adapters.
68
13. Select Entire feature will be unavailable.
14. Decide if want to install MySQL.
If you want to install MySQL: a. c. Expand Central Management Server. Select Entire feature will be installed on local hard drive a b. Left-click on the icon beside MySQL4.1.9. d. Click Next.
If you do not want to install MySQL, a. c. Expand Central Management Server, Select Entire Feature will be unavailable. b. Left-click on the icon beside MySQL4.1.9. d. Click Next.
Note: The setup program checks to see whether or not MySQL or SQL Server is already installed on the local machine.
69
15. Specify whether this is the first Central Management Server cluster on the CMS Clustering dialog box.
If this is the first CMS cluster. a. c. Click Yes. Click Next. Click No, cluster it with the following CMS. b. Ensure that Enable servers upon install remains selected.
If this is not the first CMS cluster. a. b. Enter the machine name of the first CMS cluster in the Existing CMS Name field. c. Deselect Enable servers upon install. d. Click Next.
16. If you chose to MySQL, specify the configuration for MySQL Server Database.
70
a.
Enter the port number to be used.
b. c. d.
Enter and confirm the password that will be used by MySQLs root user account. Accept the default user name to access the CMS database or enter the user name you desire to override the default name. Enter and confirm the password that will be used by MySQLs CMS user account, and then click Next.
17. Specify the database connection properties.
Note: You will not see this screen if you choose to install MySQL.
71
c.
Select the datasource name you created for the CMS from the Data Source Name field, and then click OK. The Server Login window will appear.
.
d. Enter the userid and password for the datasource, and then click OK. e. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next.
Note: This database should be set up before you begin your install. See Setting up a database account for BusinessObjects Enterprise on page 40 for more information.
For Oracle: a. c. Select Oracle. Enter the credentials for the server in the User Name and Password fields. b. Enter the Oracle tnsname in the Server field.
72
d. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next.
For DB2: a. c. Select DB2. Enter the credentials for the server in the User Name and Password fields. b. Enter the DB2 alias in the Server field.
For MySQL a. Select MySQL. b. Enter the database name in the Database field for the CMS database. c. e. f. Enter the database server name in the Server field. Enter the credentials for the server in the User Name and Password fields. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next. Select Sybase. d. Enter the port being used by MySQL in the Port field.
For Sybase: a. b. Enter the database name in the Database field for the CMS database. c. Enter the database server name in the Server field d. Enter the credentials for the server in the User Name and Password fields. e. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next.
Tip: For Sybase, you do not enter the database name. BusinessObjects Enterprise uses the Sybase service name, which specifies which machine and port the database server is on, and the default database name associated with the users profile. 18. Click Next to begin the installation. After you have finished installing the server and client components, you must install the WCA. For further information, see Installing only the Web Component Adapter on page 74.
73
Installing only the Web Component Adapter

Install the appropriate WCA on the machine running your web application server. If you have a Java web application server install the Java Web Component Adapter, if you have IIS, install the .NET Web Component Adapter. Before you install the WCA, you must have installed the server and client components. For detailed steps, see Installing only the server and client components on page 67. 1. Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue. Note: When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically.automatically. 2. Select which language to install from the list, and then click OK. In a few moments you will see the Welcome to BusinessObjects Enterprise Installation Wizard dialog. 3. 4. 5. 6. 7. 8. 9. Click Next. Click the I accept the License Agreement button on the License Agreement dialog, and then click Next. Choose Perform Server Installation on the Select Client or Server Installation dialog, and then click Next. Fill out the Full Name and Organization fields. Enter your product keycode in the first Product Keycode field, and then click Next. Specify the directory where you want to install, and then click Next. Select Custom, and then click Next.
10. Left-click on the icon beside BusinessObjects Enterprise. 11. Select Entire feature will be unavailable. 12. Expand Server Components on the Select Features dialog, and then expand Servers. 13. Scroll down until you find Web Component Adapters. 14. Expand Web Component Adapters. 15. Select which WCA to install.
74
To install the.NET WCA: a. c. Left-click on the icon beside .NET Web Component Adapters. Click Next. Left-click on the icon beside Java Web Component Adapters. If you want to install Tomcat, Left-click on the icon beside Tomcat, and select Will be installed on local hard drive, otherwise, skip this step. b. Select Will be installed on local hard drive.
To install the JAVA WCA: a. c. b. Select will be installed on local hard drive.
d. Click Next. 16. Under the Sample Reports and Help, click Help Files and choose Will be installed on local hard drives. 17. Click Next. 18. Click Next in the Start Installation dialog box. The installation of files begins immediately. When the installation program has finished copying files, the final setup screen appears. 19. Click Finish and, if prompted, restart the local machine. Note: If you cannot access BusinessObjects Enterprise after the installation completes, start the Central Configuration Manager (CCM) from the BusinessObjects Enterprise program group. Ensure that all of the servers listed are both started and enabled.
Performing a distributed install of performance management

If you want to have BusinessObjects Enterprise installed on one machine and want to have performance management installed on a separate machine with your web application server, you will have to do the following:
Perform a new install. Perform an expand install. Create a new desktop.war file. Modify the Tomcat properties.
Note: The following procedure will refer to Server 1 and Server 2. This procedure assumes you already have Tomcat and the Web Component Adapter installed on Server 2. 1. Remove the desktoplaunch web application folder, located in the following location:
75
<BO_INSTALL_DIR_SERVER_1>\Tomcat\webapps\businessobjects\ent erprise115\desktoplaunch 2. Using the mergeboar.jar tool, rename the desktop.war file backup_of_desktop.war, and move it from the following location:
<BO_INSTALL_DIR_SERVER_1>\BusinessObjects Enterprise 11.5\java\applications\ to: <BO_INSTALL_DIR_SERVER_1>\
3.
Run the following command line on Server 1:

java -jar "<BO_INSTALL_DIR_SERVER_2>\Performance Management 11.5\setup\mergeboar.jar" "<BO_INSTALL_DIR_SERVER_1>\backup_of_desktop.war" "<BO_INSTALL_DIR_SERVER_2>\Performance Management 11.5\pm11.boar" "<BO_INSTALL_DIR_SERVER_1>\BusinessObjects Enterprise 11.5\java\applications\desktop.war"
Modifying Tomcat for performance Management

1. 2. 3. To add the required JVM options for performance management From the Start menu, select Programs > Tomcat > Tomcat Configuration. Click the Java tab. In the Java Options field, add the following line: -Daf.configdir=<BO_INSTALLDIR_SERVER_2>/Performance Management 11.5 Note: If you are using another web application server besides Tomcat, the previously mentioned java option must be added to your web application server. 4. Create an afhelp.xml file in the following location:
<BO_INSTALL_DIR_SERVER_1>/Tomcat/conf/Catalina/ localhost:
5.
Add the following information to the afhelp.xml file. <Context docBase=<BO_INSTALL_DIR_SERVER_2>\Performance Management 11.5\afhelp.war path=/bobj crossContext=false debug=0 reloadable=false trusted=false/>
6.
Restart Tomcat.
76
Adding Crystal Enterprise 10 web desktop support

Note: If you have an existing Crystal Enterprise 10 web desktop that you want to continue using with BusinessObjects Enterprise XI, you must install an extra feature to support the older web application. This procedure assumes you have already installed the client and server components. 1. 2. 3. To install the client and server components Open the Control Panel. From the Start Menu select Settings > Control Panel. Click Add/Remove Programs. Select BusinessObjects Enterprise XI Release 2, and then click Change. The Application Maintenance screen will appear.
4. 5. 6. 7. 8. 9.
Select Modify, and then click Next. Select Client Components. Left-click on the icon beside Client Components, and then select Entire feature will be unavailable. Expand the Client Components tree. Select v10 Crystal Enterprise Web Desktop. Left-click on the icon and select Will be installed on local hard drive.
10. Select Server Components, left-click on the icon beside it, and then select Entire feature will be unavailable. 11. Select Data Access and Output Formats, left-click on the icon beside it, and then select Entire feature will be unavailable.
77
12. Select Sample Reports and Help, left-click on the icon beside it, and then select Entire feature will be unavailable. 13. Click Next. 14. Click Next.
Running a custom install

Run a custom installation when you know precisely what components you want installed and what components you dont wish to install. Note: It is not recommended that you run a custom install unless you are already familiar with BusinessObjects Enterprise. If you are not familiar with specific BusinessObjects Enterprise components and their roles and you do a custom install, you may inadvertently not install a required component. You may instead want to follow the steps outline in, Installing only the server and client components on page 67 and Installing only the Web Component Adapter on page 74, which are more detailed. 1. To perform a custom installation Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue. Note: When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically. 2. Select which language to install from the list, and then click OK. In a few moments you will see the Welcome to BusinessObjects Enterprise Installation Wizard dialog. 3. 4. 5. Click Next. Click I accept the License Agreement on the License Agreement dialog, and then click Next. Select Perform Server Installation on the Select Client or Server Installation dialog, and then click Next. Note: If you want to select only Client tools, select Perform Client Installation on the select Client or Server Installation dialog. 6. 7. Fill out the Full Name and Organization fields. Enter your product keycode(s)
If you only want to install BusinessObjects Enterprise:
78
a. c.
Enter its product code in the first Product Keycode field. Click Next.
b. Clear the check box beside Install Performance Management.
If you are also installing performance management which includes Dashboard Manager, Performance Manager, Set Analysis, Predictive Analysis and Process Control: a. Enter the BusinessObjects Enterprise product keycode in the first Product Keycode field.
b. Enter one of the performance management keycodes in the second Product Keycode field. The performance management product key you type here only enables that one product. To enable other performance management products, you need to enter the license keys for those products in the Central Management Console (CMC). To find out how to do this, see the BusinessObjects Enterprise Administrators Guide. c. 8. 9. Click Next. Specify the directory where you want to install, and then click Next. Select Custom and then click Next. a. Expand the tree of features as required to locate the component(s) you want to install.
10. Choose the features you want to install from the Select Features dialog.

b.
To install a one specific feature, left-click on the icon beside the item you want to install and select Will be installed on local hard drive. To install all features in a tree, left-click on the icon beside the item you want to install and select Entire feature will be installed on local hard drive. To choose the components you dont want to install, left-click on the icon beside each item you do not want to install and select Entire feature will be unavailable. To reset the choices, click Reset.
Repeat these steps until you have made all your selections.
79
11. If you chose to install the Central Management Server during this custom install; otherwise, specify whether this is the first Central Management Server cluster.
If this is the first CMS cluster. a. c. Click Yes. Click Next. Click No, cluster it with the following CMS. b. Ensure that Enable servers upon install remains selected.
If this is not the first CMS cluster. a. b. Enter the machine name of the first CMS cluster in the Existing CMS Name field c. Clear Enable servers upon install. d. Click Next.
80
12. If you chose to install MySQL specify the configuration for MySQL Server Database.
a. b. c. d.
Enter the port number to be used. Enter and confirm the password that will be used by MySQLs root user account. Accept the default user name to access the CMS database or enter the user name you desire to override the default name. Enter and confirm the password that will be used by MySQLs CMS user account, and then click Next.
81
13. If you choose to use an existing database specify the CMS database connection authentication parameters.
Note: If you plan to use BusinessObjects Auditor, you can also enter the parameters for the Auditing database at this stage.
82
c.
Select the datasource name you created for the CMS from the DataSourceName field, and then click OK. The Server Login window will appear.
.
d. Enter the userid and password for the datasource, and then click OK. e. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next.
Note: This database should have been set prior to the install. See Setting up a database account for BusinessObjects Enterprise on page 40 for more information.
For Oracle: a. c. Select Oracle. Enter the credentials for the server in the UserName and Password fields. b. Enter the Oracle tnsname in the Server field.
For DB2: a. c. Select DB2. Enter the credentials for the server in the UserName and Password fields. b. Enter the DB2 alias in the Server field.
For MySQL a. Select MySQL. b. Enter the database name in the Database field for the CMS database. c. Enter the database server name in the Server field. d. Enter the port being used by MySQL in the Port field.
83
e. f.
Enter the credentials for the server in the UserName and Password fields. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next. Select Sybase.
For Sybase: a. b. Enter the database name in the Database field for the CMS database. c. Enter the database server name in the Server field d. Enter the credentials for the server in the UserName and Password fields. e. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next.
Tip: For Sybase, you do not enter the database name. BusinessObjects Enterprise uses the Sybase service name, which specifies which machine and port the database server is on, and the default database name associated with the users profile. 14. If you chose to install Tomcat during this custom installation, specify the location and ports each of the following, and then click Next.
The Tomcat installation directory The Connection port The Shutdown port The Redirect port
Note: If you are installing BusinessObjects Enterprise XI on the same machine as a BusinessObjects Enterprise 6.x deployment, do not use the default port number 8080. This port may already be in use for the existing deployment. 15. Click Next to begin the installation. Note: If you cannot access BusinessObjects Enterprise after the installation completes, start the Central Configuration Manager (CCM) from the BusinessObjects Enterprise program group. Ensure that all of the servers listed are both started and enabled.
84
Installing BusinessObjects Enterprise on Windows Upgrade installation
Upgrade installation
If you have an existing installation of Crystal Enterprise 9, or 10 or BusinessObjects Enterprise X, the installation program will upgrade your system to BusinessObjects Enterprise XI. After you have upgraded, you can migrate your system data to the new version, and import content from an earlier version of Crystal Enterprise, Crystal Info, or BusinessObjects Enterprise R2. In order to upgrade directly to BusinessObjects Enterprise XI, you must have performed a a full standalone client or server installation of your product. If either the full client or server set is not detected, you will receive a message informing you that you must uninstall the previous version before you proceed with your install. 1. 2. To upgrade your installation Disable and subsequently stop all Crystal Enterprise servers. Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue. Note: When you start the installation, the Microsoft Windows Installer may need to be installed or upgraded on the local machine. If so, the Wise Installation Wizard performs the necessary modifications and prompts you when finished. Click Yes to restart the machine and resume the installation automatically. 3. Select which language to install from the list, and then click OK. In a few moments you will see the Welcome to BusinessObjects Enterprise Installation Wizard dialog. 4. 5. 6. Click Next. Click I accept the License Agreement on the License Agreement dialog, and then click Next. Choose Perform Server Installation on the Select Client or Server Installation dialog, and then click Next.
85
7.
Fill out the Full Name and Organization fields.
8.
Enter your product keycode(s)
If you are also installing performance management, which includes Dashboard Manager, Performance Manager, Set Analysis,Predictive Analysis and Process Analysis: a. Enter the BusinessObjects Enterprise product keycode in the first Product Keycode field.
b. Enter one of the performance management keycodes in the second Product Keycode field. The performance management product key you type here only enables that one product. To enable other performance management products, you need to enter the license keys for those products in the Central Management Console (CMC). To find out how to do this, see the BusinessObjects Enterprise Administrators Guide. c. Click Next. The Upgrade Install dialog will appear.
86
9.
Decide if you want to use an existing database server or install MySQL.
If you want to use an existing database server, click Provide the DSN of the database you want to initialize for the new BusinessObjects Enterprise deployment, and then click Next. Note: This must be a new DSN specifically created for BusinessObjects Enterprise XI Release 2. Do not specify the name of an existing DSN or database from a previous deployment.
If you want to install MySQL, click Install MySQL, and then click Next.
10. If you chose to use an existing database server, provide the required information about your database on the CMS Information dialog.
87
Note: This must be a new DSN or database specifically created for BusinessObjects Enterprise XI Release 2. Do not specify the name of an existing DSN or database from a previous deployment.
88
c.
Select the datasource name you created for the CMS from the DataSourceName field, and then click OK. The Server Login window will appear.
.
d. Enter the userid and password for the datasource, and then click OK. e. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next. Select Oracle. Enter the credentials for the server in the UserName and Password fields.
For Oracle: a. c. b. Enter the Oracle tnsname in the Server field.
For DB2: a. c. Select DB2. Enter the credentials for the server in the UserName and Password fields. b. Enter the DB2 alias in the Server field.
For MySQL a. Select MySQL. b. Enter the database name in the Database field for the CMS database. c. e. Enter the database server name in the Server field. Enter the credentials for the server in the UserName and Password fields. d. Enter the port being used by MySQL in the Port field.
89
f.
Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next. Select Sybase. Enter the credentials for the server in the UserName and Password fields.
For Sybase: a. c. b. Enter the Sybase service name in the Server field.
d. Repeat these steps for the Auditing database, if you plan on using one and then click Next; otherwise, click Next. Tip: For Sybase, you do not enter the database name. BusinessObjects Enterprise uses the Sybase service name, which specifies which machine and port the database server is on, and the default database name associated with the users profile. 11. If you installed MySQL, complete the required information on the MySQL Server Database Configuration dialog.
a. b. c. d.
Enter the port number to be used. Enter and confirm the password that will be used by MySQLs root user account. Change the name of the user account that will be used to access the CMS database. The default user name for this is CMS. Enter and confirm the password that will be used by MySQLs CMS user account, and then click Next.
90
Installing BusinessObjects Enterprise on Windows Silent installation
12. Click Next to start the installation.
Silent installation
A silent installation is one that you run from the command line to install BusinessObjects Enterprise on any machine in your system. When you run a silent installation, you can:
Specify all the parameters to be used for the install at the same time on the command line, rather than several at a time on each of the different install screens. Specify other options that control the prompt level you want for the install.
The silent install is run from the command line. The command includes a series of parameters that provide information for installation settings and directory paths. You can also specify options that control the level of prompts during an install. Note: BusinessObjects Enterprise does not support silent installations when the install contents are on multiple CDs. If your install is on multiple CDs, you must first copy the contents from all the CDs to a central location, such as a hard-drive, and then run the silent install from the location that contains the content from all the CDs. The silent BusinessObjects Enterprise installation is particularly useful when you need to perform multiple installations or you do not want to interrupt people who are working on machines in your system. You can also use the silent installation command in your own scripts. For example, if your organization uses scripts to install software on machines, you can add the silent BusinessObjects Enterprise installation command to your scripts.The silent installation command consists of the command setup.exe, followed by the install destination, and a number of parameters that provide information about the installation. The following example installs BusinessObjects Enterprise with the CMS and Tomcat and MySQL onto the machine with no user interface and no prompt and the end of the installation.:
setup.exe CLIENTLANGUAGE=EN INSTALLLEVEL=6 INSTALLDIR=c:\Program Files\My Prefered_Location REBOOT=ReallySuppress PIDKEY=A1234-ABCD123-12345A6 DATABASEPWD_MYSQL =rpassword DATABASEUID=sa DATABASEPWD=mypassword /qn
The example uses the most common parameters. You can choose any number of valid parameters, but it is good practice to keep the silent installation as simple as possible.
91
The following table lists the most common parameters used in a silent installation. To use a parameter, place it on the command line after the setup.exe command and the path for the installation files.
Silent install parameters

These parameters that follow are for the silent install. Please note that these parameters are case sensitive.
92
Installation parameter
CLIENTLANGUAGE
Use Use this to specify the Language version code for the install.
For English, enter EN. For French, enter FR. For German, enter DE. For Spanish, enter ES. For Japanese enter JP. For Simplified Chinese, enter CHS For Traditional Chinese, enter CHT. For Korean, enter KO. For Dutch, enter NL. For Swedish, enter SV. For Italian, enter IT. For Portuguese, enter PT.
Note: If you dont enter this parameter, the regular language selection screen will appear at the beginning of your install, even if you specified the parameters for a no prompt installation.
INSTALLLEVEL
Determines which BusinessObjects Enterprise components are installed. 6 specifies all components will be installed. 5 specifies all components will be installed except MySQL. 4 specifies all components will be installed except MySQL, CMS and Tomcat. 3 specifies all components except MySQL, CMS, Tomcat and the SDKs will be installed. If you dont specify this parameter, the default level of 5 is used.
93
INSTALLDIR=filepath
Use Use this parameter to specify the machine and directory where you want to install the new BusinessObjects Enterprise components. Replace filepath with the full path for the installation directory. For example,
C:\Program Files\Business Objects
PIDKEY=00000-00000000000000-0000 EPMPIDKEY=00000-00000000000000-000 DATABASEUID=myusername
Specifies your product activation keycode. Specifies your product activation keycode for performance management. Use this parameter to pass the userid for the database. Note: For trusted authentication this parameter is not required, use DATABASEAUTHENTICATION=trusted. Use this parameter to specify the MySQL root password. Use this parameter to specify the administrator password for the database youll be using for BusinessObjects Enterprise. Note: For trusted authentication, this parameter is not required, use DATABASEAUTHENTICATION=trusted instead. Use this parameter to identify the type of database for the CMS. For Oracle, enter OracleDatabaseSubsystem. For DB2, enter DB2DatabaseSubsystem. For Sybase, enter SYBASEDatabaseSubsystem. For ODBC SQL, enter ODBCDatabaseSubsystem. For Remote MySQL, enter MySqlDatabaseSubsystem.
DATABASEPWD_MYSQLROOT DATABASEPWD=mypassword
DATABASEDRIVER
94
DATABASEDSN=<ODBC DSN for CMS DB> DATABASEPORT
Use Use this parameter to specify the ODBC DSN for the SQL CMS database. Use this parameter to specify the port used for MySQL Server. Defaults to port 3306 if it is not specified. Use this parameter to specify the name of the CMS database. This database name defaults to BOE115 if this parameter is not specified. Use this parameter to reset an existing database. Use this parameter to configure Auditor during your install. Use this parameter to change the name of the MySQL audit database, otherwise, the default name of BOE115_Audit will be used. Use this parameter to specify the ODBC DSN for the SQL Audit database. Use this parameter to pass the userid for the database for Auditor. Note: For trusted authentication this parameter is not required, use DATABASEAUTHENTICATION=trusted. Use this parameter to specify the administrator password for the database youll be using for BusinessObjects Enterprise. For trusted authentication, this parameter is not required, use DATABASEAUTHENTICATION=trusted instead. Use this parameter to specify the port for MySQL Auditor. Note: Use only for MySQL. Use this option to prevent the user from being prompted to reboot the machine during the install process.
DATABASEDB
REINITILIZE_CMS_DB=1 ENABLEAUDITING=1 DATABASEDB_AUDIT
DATABASEDSN_AUDIT=<ODBC DSN for AUDITDB> DATABASEUID_AUDIT
DATABSEPWD_AUDIT
DATABASEPORT_AUDIT
REBOOT=ReallySuppress
95
TOMCAT_SHUTDOWN_PORT
Use Use this option to specify a different shutdown port. If this option is not specified, port 8005 will be used. Use this option to specify a different redirect port. If this option is not specified, port 8443 will be used. Use this option to specify a different connection port. If this option is not specified, port 8080 will be used. Use this to change the default directory where Tomcat is installed. If you dont specify this parameter, Tomcat will be installed the directory TOMCAT under the default directory for BusinessObjects Enterprise 11.5. Use this option so the user is only prompted when the installation is complete. Note: You must also enter the CLIENTLANGUAGE parameter as part of your silent install string or the language selection screen will appear at the beginning of your install. Use this option so the user is not prompted during the install, or when the install is complete. Note: You must also enter the CLIENTLANGUAGE parameter as part of your silent install string or the language selection screen will appear at the beginning of your install.
TOMCAT_REDIRECT_PORT
TOMCAT_CONNECTION_PORT
TOMCATDIR
/qn+
/qn
Note:

96
The silent installation is not available from the BusinessObjects Enterprise Setup program and is intended only for experienced administrators of BusinessObjects Enterprise. The silent installation is not recommended for custom installations. The installation options are simplified and do not allow for the same level of customizing that the BusinessObjects Enterprise Setup program provides. Silent installations are not recommended for upgrades.
Installing BusinessObjects Enterprise on Windows Post install component deployment
Post install component deployment

When you install BusinessObjects Enterprise on Windows and either use IIS or install Tomcat with your install, InfoView, the Central Management Console (CMC), the Web Component Adapter (WCA) and the BusinessObjects Enterprise SDK are installed, configured and deployed for you. InfoView is a web-based interface that end users access to view, schedule, and keep track of published reports. The CMC allows you to perform user management tasks such as setting up authentication and adding users and groups. The Web Component Adapter (WCA) is an application that runs on either your Java Web Application Server or IIS. The WCA hosts web components, including a CSP plug-in that allows you to run CSP applications. The WCA is also required for OLAP Intelligence. The BusinessObjects Enterprise SDKs are used by many BusinessObjects Enterprise components and are also used to simplify the development of custom BusinessObjects Enterprise applications. If you do not either use IIS or install Tomcat when you install BusinessObjects Enterprise, these components must configured and deployed before you use them. Consult the following sections for information how to deploy and what to configure on your web application server:
Deploying on Tomcat on page 127 Deploying on SAP Web Application Server on page 179 Deploying on Oracle Application Server on page 167 Deploying on WebSphere on page 137 Deploying on WebLogic on page 153
Alternatively, you can use a tool called wdeploy to deploy BusinessObjects Enterprise web applications. This tool will be available on Business Objects technical support web site (http://support.businessobjects.com), and is supported on the following web application servers: SunOne 8 (Solaris only) Tomcat WebLogic 8 WebSphere 5.1 With wdeploy, you can deploy applications resources in two modes:
Standalone mode The WAR files that contain both static and dynamic content are deployed on the web application server.
97
Distributed mode The static content is extracted from the WAR files, and then the dynamic content is deployed to the application server. The static content is then deployed on the web server. This may enhance performance because the web server can serve up static pages without having to communicate with the web application server. Note: Documentation for wdeploy will be available on this site: http:// support.businessobjects.com/documentation.
For more information about the system architecture of an installation of BusinessObjects Enterprise, see the architecture chapter of the BusinessObjects Enterprise Administrators Guide. Note:
If you have a firewall between the machine running your Java application server and your other BusinessObjects Enterprise servers, you must perform additional system configuration. See the section on how to configure firewalls, in your BusinessObjects Enterprise Administrators Guide. If you will be scheduling documents in Adobe Acrobat format, be sure Adobe Acrobat is installed on your web application server.
Verifying the Java web applications

The setup program automatically deploys the Java web applications to default locations. You can test the deployments and change the default configuration if necessary.
InfoView and the BusinessObjects Enterprise Administration Launchpad

To test the Java deployment of the InfoView and the BusinessObjects Enterprise Administration Launchpad 1. Open a web browser and type http://servername:portnumber/ businessobjects/enterprise115/desktoplaunch in its address bar. For servername, substitute the name of the machine where you installed. The log on page for the InfoView should appear. 2. To test the BusinessObjects Enterprise Administration Launchpad, open a web browser and type http://servername:portnumber/ businessobjects/enterprise115/adminlaunch in its address bar. For servername, substitute the name of the machine where you installed. The BusinessObjects Enterprise Administration Launchpad should open.
98
The .NET Web Component Adapter

The .NET Web Component Adapter (WCA) is a web application that runs on your web application server. The WCA hosts web components, including a CSP plug-in that allows you to run CSP applications. 1. To test the deployment of the WCA on IIS Launch the Central Management Console by typing http:// servername:portnumber/businessobjects/enterprise115/ admin in the address bar of a web browser. For servername, substitute the name of the machine where you installed Tomcat. 2. Log on to the Central Management Console (CMC) as Administrator. By default, the Administrator account has no password. The Central Management Console should appear.
Verifying the .NET web applications

The setup program automatically deploys the .NET web applications to default locations. You can test the deployments and change the default configuration if necessary.
InfoView and the BusinessObjects Enterprise Administration Launchpad

To test the deployment of the InfoView and the BusinessObjects Enterprise Administration Launchpad on IIS 1. To test the InfoView, open a web browser and type http:// servername/businessobjects/enterprise115/desktoplaunch/ in its address bar. For servername, substitute the name of the machine where you installed IIS. The log on page for the InfoView should appear. 2. To test the BusinessObjects Enterprise Administration Launchpad, open a web browser and type http://servername/businessobjects/ enterprise115/adminlaunch in its address bar. For servername, substitute the name of the machine where you installed. The BusinessObjects Enterprise Administration Launchpad should open.
The .NET Web Component Adapter

The Web Component Adapter (WCA) is a web application that runs on your web application server. The WCA hosts web components, including a CSP plug-in that allows you to run CSP applications.
99
1.
To test the deployment of the WCA on IIS Launch the Central Management Console by typing http:// servername:portnumber/businessobjects/enterprise115/ admin in the address bar of a web browser. For servername, substitute the name of the machine where you installed.
2.
Log on to the Central Management Console (CMC) as Administrator. By default, the Administrator account has no password. The Central Management Console should appear.
Deploying custom CSP applications

To deploy your own custom CSP applications, place them in the Web Content directory that contains the Central Management Console.
Changing the deployment values for the Web Component Adapter

The BusinessObjects Enterprise setup program automatically configures the JAVA and/or the .NET WCA with specific information:
The name and location of your Central Management Server. The default display name of the WCA. The location of the directories where the WCA can find CSP applications. The location it should use for log files.
In most situations you should not need to change these default values. You may want to change some of these values to change the location of the WCA log files, if you want to deploy your custom CSP applications in a location other than the default directory, or if you plan to deploy multiple WCAs. If you want to change these values, follow the steps that apply to the type of WCA you installed. 1. 2. To change the deployment values for the Java WCA Stop your Java application server, if it is running. Extract web.xml from webcompadapter.war using a tool such as WinZip. The webcompadapter.war archive file is stored in the C:\Program Files\Business Objects\Enterprise 11.5\java\applications directory. 3. Open web.xml in a text editor such as Notepad.
100
To alter the values of cspApplication.dir (the directory for your CSP applications), or log.file (the location of the log files created by the WCA), edit the following lines to change the values between the <paramvalue></param-value> tags:
<context-param> <param-name>cspApplication.dir</param-name> <param-value>C:\Program Files\Business Objects\Enterprise 11.5\Web Content</param-value> </context-param> <context-param> <param-name>log.file</param-name> <param-value>C:\Program Files\Business Objects\Enterprise 11.5\Logging\wca</param-value> </context-param>
Note: The values shown here are the default locations that the BusinessObjects Enterprise setup program creates when you use the default installation directory for BusinessObjects Enterprise. 4. Edit the value between the <display-name> </display-name> tags to edit the display name of your WCA. Use the format wcaname.wca. Changing the display name of your WCA is equivalent to changing the server name of the WCS in a Windows deployment of Crystal Enterprise. Edit the connection.cms context parameter to edit the name of your Central Management Server. (Add the name of your CMS between the <param-value> </param-value> tags for this context parameter.) Save web.xml, then reinsert the file into the WEB-INF directory within webcompadapter.war. Tip: To reinsert web.xml into WEB-INF using WinZip, open WinZip. From the Options menu, select Configuration. In the Configuration dialog box, click the View tab. Ensure that the Allow all upper case file names check box is selected. Return to your files directory. Right-click the WEBINF directory that contains your edited web.xml file, and select Add to Zip File.... Adding the file in this way ensures that it is placed in the correct directory inside the archive. 7. Restart your application server and redeploy webcompadapter.war (for BEA WebLogic), or restart the application (for IBM WebSphere). The WCA should now use the new values from web.xml. To change the deployment values for the .NET WCA Stop your application server, if it is running. Open web.config in a text editor such as Notepad. Most of the default values that you may want to change are located in the
<appSettings> section of the file.
5.
6.
1. 2.
101
3.
To change the name of your WCA, change the value of the wca.Name setting. Use the format wcaname.dotnet_wca. Changing the display name of your WCA is equivalent to changing the server name of the WCS in a Windows deployment of Crystal Enterprise. To change the name of your Central Management Server, change the value of the connection.cms setting. Save web.config. Restart your application server. The WCA should now use the new values from web.config.
4. 5. 6.
Installing multiple Web Component Adapters

You can install multiple Web Component Adapters (WCA) by deploying multiple instances of webcompadapter.war. If you deploy each WCA on a separate application server, installing multiple WCAs is roughly equivalent to installing multiple Web Component Servers (in a Windows installation of BusinessObjects Enterprise that uses the BusinessObjects Enterprise COM SDK). If you deploy each WCA on the same Java application server, installing multiple WCAs is equivalent to creating multiple virtual directories for your web server (in a Windows installation of BusinessObjects Enterprise that uses the BusinessObjects Enterprise COM SDK). When you install more than one WCA, each webcomponentadapter.war file contains its own web.xml file that contains configuration parameters for that WCA. However, you can only set the following parameters individually for each WCA:
cspApplication.defaultPage cspApplication.dir connection.cms connection.listenPort log.file log.ext log.isRolling log.size log.level log.entryPattern
The remaining parameters must be the same for all WCAs. See Changing the deployment values for the Web Component Adapter on page 100 for information on changing the values.
102
Note: If you have a firewall between the machine running your Java application server and your other BusinessObjects Enterprise servers, you must perform additional system configuration. See the section on how to configure firewalls, in your BusinessObjects Enterprise Administrators Guide.
Configuring the Java environment variable

After installing the Java JDK, you must set the JAVA_HOME environment variable. If your Java web application server installs the Java JDK as part of its installation process, install the application server first, and then set the environment variable. You need to know the directory path containing your Java SDK bin directory. 1. 2. 3. 4. 5. 6. To set the JAVA_HOME environment variable on Windows Right-click My Computer, and select Properties. Click the Advanced tab. Click Environment Variables. In the System variables area, click New. In the Variable Name box, type JAVA_HOME. Enter the complete path to the directory containing your Java SDK bin directory in the Variable Value box. For example, enter C:\bea\jdk141_02 if you have completed a default installation of BEA WebLogic 8. Click OK > OK > OK.
7.
Deploying custom CSP applications

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

Before you launch performance management, launch the CMC from the Start menu and go to the Servers page to verify that all of the performance management servers required for the products you installed are running.
103
The following table provides a description of each performance manager server: Server name AADashboard Service Dashboard engine Description Renders the performance management Corporate Tiered Dashboards that users create using Dashboard Manager Renders the performance management analytics by querying the metrics metadata and then generating the desired visualization in the format of the selected analytic. Works like an Extract, Transform and Load (ETL) tool to extract each metric value, aggregate it, and then load it into the metadata layer on the performance management repository. Used by Individual Profiler. For more information, go to Setup > Parameters > Individual Profiler and then click Help on the Services bar. Manages the performance management repository including user security and privileges, updates to the system parameters, and writing new metrics and rules back to the repository. Evaluates conditions placed against metrics, goals, sets and then outputs sending events to other components Performs Set Analysis queries and builds and processes sets.
AAAnalytics
Analytics server
AAMetrics
Metrics engine
AAIProfiler
Individual Profiler engine
AARepomgt
Repository manager
AARules
Rules engine
AAQueryManager Set Analysis query manager
104
Server name AASPC
Service Process Analysis engine
Description Used by Process Analysis. Note: The Process Anlaysis alerts are actioned upon and handled by AARules Used by Predictive Analysis. For more information, go to Performance Management > Predictive Analysis and then click Help on the Services bar
PAServer
Predictive Analysis mining engine
Post installation setup for performance management

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

If, when you launch performance management, you receive an error message saying that you cannot connect to performance management, this may mean one of the following:
105
Some of the performance management servers are stopped or disabled. The Initialization User that creates the performance management server proxies may be defined inconsistently in the CMS, InfoView, and the InitConfig.properties file. To verify performance management servers Log into the Central Management Console (CMC), and then click Servers. Verify that all the performance management servers are started. If a server is not running, select the check box next to the server name, and then click Start. Make sure that all servers are enabled. If a server is not enabled, select the check box next to the server name, and then click Enable.
1. 2. 3. 4.
1.
To verify the Initialization User On your performance management server, open the InitConfig.properties file and verify that the Initialization user name and password match those in the CMS. This file is at:
<InstallDir>\Program Files\Business Objects\performance management 11.5
The strings to search for are:

2. 3.
initialization.User= initialization.Password=
Log into InfoView, and then click the Preferences button on the InfoView toolbar. Click the Performance Management tab, and then check the name of the initialization logon user in the Change initialization logon user section is the same as the user name specified in the InitConfig.properties file. Log into the Log into the Central Management Console (CMC), and then click Users. Check that the user defined in the InitConfig.properties is listed among the users. From the CMC home page, click Settings > Rights and check that the initialization user has the appropriate rights.
4. 5. 6.
106
Note: For security reasons, it is recommended that you do not provide a real user ID for the initialization user. The default user ID is PMUser. You need to restart the performance management servers. 7. On the server machine click Start > Programs > BusinessObjects XI Release 2 > BusinessObjects Enterprise > Central Configuration Manager, and then restart all servers.
If you are using performance management from a client machine (that is, a different desktop computer than where the performance manager server is installed), you need to restart your computer.
107
108
Installing Service Pack 2
chapter
Installing Service Pack 2 Service Pack 2 overview
Service Pack 2 overview

This section of the guide provides information on how to upgrade to BusinessObjects Enterprise XI Release 2 Service Pack 2 (SP2). You have these choices when installing SP2:
If you have not previously installed BusinessObjects Enterprise XI Release 2, the full version you install will be cumulative version. The installed version will include both the full version of the product, Service Pack 1, and Service Pack 2. Note:
For information on installing BusinessObjects Enterprise, see Installing BusinessObjects Enterprise on Windows on page 35. If any portion of BusinessObjects Enterprise XI Release 2 is detected, you will receive an error message and the installation will end. Russian and polish language support for the installation is not available in the complete installation the includes Service Pack 2.
If you have not yet installed BusinessObjects Enterprise Release 2, see Installing BusinessObjects Enterprise on Windows on page 35.
Installing Service Pack 2

1. 2. 3. 4. 5. To install Service Pack 2 Run setup.exe from the root directory of your product distribution. Select which language to install from the list, and then click OK. Click Next. Click I accept the License Agreement, and then click Next. Click Next. The installation will begin. Note: For information on content of the service pack, see the release notes in the docs directory of your product distribution.
110
Beta
Installing the Productivity Pack
chapter
Installing the Productivity Pack Productivity Pack upgrade overview
Productivity Pack upgrade overview

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

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

Business Process BI Services is a high-level web service designed to help align an organizations BI investments with the everyday running of its business. Business Process BI Service will help an organization effectively streamline business intelligence delivery, automate data refreshes and integrate Business Objects Enterprise administration directly into common IT processes. For more information, see the Business Process BI Services Guide. Note: Business Proces BI Services is available only for as Java web application servers.
Voyager
Voyager is a powerful OLAP analysis tool that can help you gain insight into business data and make intelligent decisions that impact corporate performance.
112
Beta
OLAP technology differs from traditional OLTP technology. You can perform real-time, interactive analysis on large volumes of OLAP data in Voyager to get answers to your business questions much more quickly than is possible using other techniques. You can identify trends and anomalies within business performance that may otherwise go unnoticed. For an overview of OLAP technology and concepts, see the <BOProductName>BusinessObjects Voyager User's Guide. OLAP data is displayed in the Voyager analysis window with crosstabs and charts. You create a workspace, add crosstab and chart objects to the analysis window, connect those objects to OLAP data sources, and then interactively define queries to explore your data. Voyager is accessed from within InfoView. All you need is a connection to a BusinessObjects Enterprise system that has Voyager installed. You do not need to install Voyager on your local machine. Note:
The Voyager web application and content viewer are only available as Java web applications. There are no corresponding Voyager applications for .NET. In some instances, after the installation is complete, you will have to enter a keycode to enable Voyager. See the <BOProductName>BusinessObjects Voyager Administrator's Guide for information about how to enter the keycodes and when the additional keycodes are required.
Content Search in InfoView

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

Before you begin your upgrade, ensure you have the following information:
The CMS name. The user name with administrative privileges to connect to the CMS. The password for the administrators user name.
Beta
113
The authentication method you use to connect to the CMS. Note: If you are not using Enterprise authentication to connect to the CMS, because you configured and are using a different authentication method, you will need to specify what authentication method your administrator user name uses to connect to the CMS. These are your choices:

1.
Windows Active Directory Windows NT LDAP
To upgrade to BusinessObjects Enterprise XI Release 2 Run setup.exe from the root directory of your product distribution. If Autoplay is enabled for your CD-ROM drive, the setup program will start automatically. Click Install to continue.
2. 3. 4. 5. 6.
Select which language to install from the list, and then click OK. Click Next. Click I accept the License Agreement, and then click Next. Click Next on the Destination Folder screen. The Select features screen will be displayed. Determine which features you want to install on the Select Feature screen.
To install all features, click Next. To deselect a feature:
Left-click on the icon beside the feature name you do not want. Select Entire Feature will be unavailable. Repeat this process until only the features you want remain, then click Next.
Note: For information on what the various options contain, see Feature selection on page 116. 7. If a Tomcat installation is detected, decide whether to allow the installation to configure and deploy the web application server components.
114
Beta
Click Yes to allow the installation to configure and deploy the new web application server components on Tomcat. Click No if you want to manually replace and deploy the WAR files after the installation completes.
Note: See New or updated WAR files on page 126 for a list of the new or modified WAR files and details on where to get further information about deploying them after the installation completes. 8. Complete these fields on the CMS Logon information screen:

9.
CMS Name User Name Password Authentication
Click Next. Your credentials for the CMS will be verified.
10. Click Next to begin the install.
Installation logs
All the actions of the BusinessObjects Enterprise installation program are recorded in a file. You can find this file BOBJPPInstall_0.log the following location: C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Logging\
Beta
115
Installing the Productivity Pack Feature selection
<Installdir>/bobje/logging directory
Distributed installs of Voyager

Like the majority of the BusinessObjects Enterprise Servers, the MultiDimensional Analysis Services Server, which processes Voyager documents, can be scaled to divide the processing load or to distribute the load. This installation type is done in multiple steps:
The Information Anlayzer web application server components would need to be installed on the machine where InfoView is deployed. This is the machine that hosts your web application server and has the WCA installed. The Voyager CMS Add-On must be installed on the machine where your CMS is installed. The Multi-Dimensional Analysis Services Server can be installed on any machine that has the BusinessObjects Enterprise Java SDK installed.
Consult the BusinessObjects Voyager Administrator's Guide for details on prerequisites and other information on Voyager.
Feature selection
You can install all the options included with the Productivity Pack or you can opt to limit your install to specific items. The one required item is the Productivity Pack Shared Components. This includes the updates required to support the new features as well as various enhancements to existing functionality included in XI Release 2.The following table lists the optional available and describes what these options contain.
116
Beta
Beta
117
Option Voyager
Description Voyager contains three subcomponents: Multi Dimensional Analysis Services Server
Voyager web application server component Voyager CMS Add-On.
The Multi Dimensional Analysis Services is the name of the server that processes Voyager documents. After the install, this server can be started or stopped from the CCM or the CMC. The web application server component is the required information to integrate Voyager with InfoView. The CMS Add-On option contains the necessary changes for the CMS to support the new object types created by Voyager. Note: If Tomcat is detected during your installation, and you allow the installation to update and configure your web application server components, this new WAR file will be deployed for you. If Tomcat is not detected during your installation, or you choose not to allow the installation to update and configure your web application server components on Tomcat, you must deploy this WAR file after the installation completes
118
Beta
Option Business Process BI Services
Description This contains Business Process BI Services. If this is installed, a new WAR file called BusinessProccessBI.war is copied to your machine. Note: If Tomcat is detected during your installation, and you allow the installation to update and configure your web application server components, this new WAR file will be deployed for you. If Tomcat is not detected during your installation, or you choose not to allow the installation to update and configure your web application server components on Tomcat, you must deploy this WAR file after the installation completes.
Content Search in InfoView
This option contains two options: Search Server CMS Add-On
The Search Server is a search engine. The CMS Add-On contains the necessary changes for the CMS to support the new object types created by the Content Search in InfoView.
Silent installation
.A silent installation is one that you run from the command line to install BusinessObjects Enterprise on any machine in your system. When you run a silent installation, you can:
Specify all the parameters to be used for the install at the same time on the command line, rather than several at a time on each of the different install screens. Specify other options that control the prompt level you want for the install.
Beta
119
The silent install is run from the command line. The command includes a series of parameters that provide information for installation settings and directory paths. You can also specify options that control the level of prompts during an install. Note: BusinessObjects Enterprise does not support silent installations when the install contents are on multiple CDs. If your install is on multiple CDs, you must first copy the contents from all the CDs to a central location, such as a hard-drive, and then run the silent install from the location that contains the content from all the CDs. The silent BusinessObjects Enterprise installation is particularly useful when you need to perform multiple installations or you do not want to interrupt people who are working on machines in your system. You can also use the silent installation command in your own scripts. For example, if your organization uses scripts to install software on machines, you can add the silent BusinessObjects Enterprise installation command to your scripts.The silent installation command consists of the command setup.exe, followed by the install destination, and a number of parameters that provide information about the installation. Following is an example that installs BusinessObjects Enterprise XI R2 PP, allows Tomcat to deploy the required files an uses Enterprise authentication:
Setup.exe /qn CLIENTLANGUAGE="EN" ADDLOCAL="Complete,IA_Service,IA,IA_Client,IA_CMS,Search _CMS,Search,Search_Service,BPBIS" TOMCAT_DEPLOY="1" CMSUSERNAME="Administrator" CMSAUTHENTICATION="secEnterprise" CMSPASSWORD="password" NAMESERVER="mycmsname" Note: The parameters are case sensitive. Since CMSPORTNUMBER is not
used, port 6400 will be assumed to be the CMS port number. The example uses most of the available parameters. You can choose any number of valid parameters, but it is good practice to keep the silent installation as simple as possible. The following table lists the parameters used in a silent installation of BusinessObjects Enterprise XI R2 Productivity Pack. To use a parameter, place it on the command line after the setup.exe command and the path for the installation files.
120
Beta
Silent install parameters

CLIENTLANGUAGE
Explanation of parameters and valid options. Use this to specify the Language version code for the install.
For English, enter EN. For French, enter FR. For German, enter DE. For Spanish, enter ES. For Japanese enter JP. For Simplified Chinese, enter CHS For Traditional Chinese, enter CHT. For Korean, enter KO. For Dutch, enter NL. For Swedish, enter SV. For Italian, enter IT. For Russian, enter RU. For Polish, enter PL. For Portuguese, enter PT.
ADDLOCAL
Note: If you dont enter this parameter, the regular language selection screen will appear at the beginning of your install, even if you specified the parameters for a no prompt installation. Specifies the names of the components to install. Use this option whenever you use install BusinessObjects Enterprise XI R2 Productivity Pack. This option is mandatory.
Complete
Beta
121
TOMCAT_DEPLOY=0
Explanation of parameters and valid options. Use this option if you want to allow the installation to update the web application server components if an instance of Tomcat is detected during the install. The valid settings are 1 and 0. If you specify 1, the web application server components will be updated on the detected instance of Tomcat; if you specify 0, the web application server components will be copied to your machine. You must deploy them manually after the installation completes.
NAMESERVER=
The default is 0. Use this option to specify the name of your CMS server. This option must be used whenever you install use either IA_Service or Search_Service so that the required changes to support these new features can be made to the CMS. Note: If you specify this parameter, you must also specify these parameters:
CMSUSERNAME CMSPASSWORD
CMSPORTNUMBER=
CMSUSERNAME= CMSPASSWORD=
Use this option to specify the name of the CMS port. If this is not specified, it will default to port 6400. Use this option to specify the user name used to log onto the CMS Use this option to specify the password for the CMS.
122
Beta
CMSAUTHENTICATION=SecXXX
Explanation of parameters and valid options. Use this option to specify the method of authentication used to log onto the CMS. These are the available options, and these must match how you have configured authentication on your deployment: SecEnterprise
SecLDAP Sec WindowsAD SecWindowsNT
IA_Client
If this parameter is not specified, and the authenticating method is required because, SecEnterprise authentication will be used. Use this option to install web application server component required to integrate Voyager with InfoView. This parameter is an argument that can be used with the ADDLOCAL option.
IA_Service
Use this option to install the MultiDimensional Analysis Service Server for Voyager. This parameter is an argument that can be used with the ADDLOCAL option. Use this option to install the required changes in the CMS to install Voyager. This option is required on the machine where your CMS is installed if you are installing Voyager. This parameter is an argument that can be used with the ADDLOCAL option.
IA_CMS
Beta
123
Search_Service
Explanation of parameters and valid options. Use this option to install the Content Search in InfoView feature. This parameter is an argument that can be used with the ADDLOCAL option. Use this option to install the required changes in the CMS to install Content Search in InfoView. This option is required on the machine where your CMS is installed if you are installing Content Search in InfoView. This parameter is an argument that can be used with the ADDLOCAL option. Use this option to install Business Process BI Services. Use this option to prevent the user from being prompted to reboot the machine during the install process. Use this option so the user is only prompted when the installation is complete. Note: You must also enter the CLIENTLANGUAGE parameter as part of your silent install string or the language selection screen will appear at the beginning of your install. Use this option so the user is not prompted during the install, or when the install is complete. Note: You must also enter the CLIENTLANGUAGE parameter as part of your silent install string or the language selection screen will appear at the beginning of your install.
Search_CMS
BPBIS REBOOT=ReallySuppress
/qn+
/qn
Note:
124
Beta
Installing the Productivity Pack Post install component deployment
The silent installation is not available from the BusinessObjects Enterprise Setup program and is intended only for experienced administrators of BusinessObjects Enterprise. The silent installation is not recommended for custom installations. The installation options are simplified and do not allow for the same level of customizing that the BusinessObjects Enterprise Setup program provides.
Post install component deployment

When you install the BusinessObjects Enterprise XI R2 Productivity Pack on Windows, Voyager, Content Search in InfoView and Business Process BI Services are deployed for you under these circumstances:
If you are using IIS. Note: The Voyager web application and content viewer are only available as Java web applications. There are no corresponding Voyager applications for .NET.
If you allowed the installation to update the detected instance of Tomcat.
When you install the BusinessObjects Enterprise XI R2 Productivity Pack, Voyager, Content Search in InfoView and Business Process BI Services are deployed for you if you choose to allow the installation to update the required components on the detected instance of Tomcat. If you chose not to allow the installation to deploy new WAR files or redeploy existing WAR files to Tomcat, or if you are using another supported web application server, certain components must be updated on your web application server before you use them. This means you must do the following:
Undeploy the original WAR files. Delete any content that remains in the directories where the original war files were deployed. If you originally deployed on an existing version Tomcat, this directory would be the following BusinessObjects Enterprise directories where TOMCATDIR is the location where you installed Tomcat:
<TOMCATDIR>/webapps/businessobjects <TOMCATDIR>/webapps/dswsbobje <TOMCATDIR>/webapps/jsfadmin
If you did not deployed on Tomcat, replace TOMCATDIR/webapps with the deployed location that applies to your web application server. Redeploy the updated WAR files.
Beta
125
Installing the Productivity Pack Post install component deployment
New or updated WAR files

Following is a list of the WAR files that have been updated or are new in the install of the Productivity pack: WAR file desktop.war BusinessProcessBI.war Contents InfoView, Voyager, performance management Business Process BI Services
Consult the following sections for information how to deploy the WAR files on your web application server:
Deploying on Tomcat on page 127 Deploying on SAP Web Application Server on page 179 Deploying on Sun Java Application Server on page 143 Deploying on Oracle Application Server on page 167 Deploying on WebSphere on page 137 Deploying on WebLogic on page 153
For more information about the system architecture of an installation of BusinessObjects Enterprise, see the architecture chapter of the BusinessObjects Enterprise Administrators Guide. Uninstalling the Productivity Pack After you have completed your installation of the Productivity Pack, follow these steps to remove it. 1. 2. 3. 4. To uninstall the Productivity Pack Open the Control Panel. From the Start Menu select Settings > Control Panel. Click Add/Remove Programs. Select BusinessObjects Enterprise XI Release 2 Productivity Pack, then click Remove. Click Yes to begin the removal o of the Productivity Pack.
126
Beta
3333
Deploying on Tomcat
chapter
Deploying on Tomcat Before you start
Before you start

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

If you have an existing version of Tomcat 5.0.27, and you want it to work with BusinessObjects Enterprise, you must perform certain steps. These steps are:
Configuring the Java environment variable on page 129 Setting Tomcat properties on page 130 Setting up JAR files on page 131 Deploying the WAR files on page 132
Locations of the WAR files

The table that follows lists the locations of the WAR files. WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, AnalysisHelp.war Location
c:\Program files\business objects\businessobjects enterprise 11.5\java\applications
Note: If you plan on using Crystal Reports Explorer, see Integrating Crystal Reports Explorer with InfoView on page 134 before you deploy this WAR file. Note: Styles.war and AnalysisHelp.war may not be present in your installation. These files are only present if you installed the original version of BusinessObjects Enterprise Release 2 or BusinessObjects Enterprise Release 2 SP1.
128
WAR File dswsbobje.war, BusinessProcessBI.war
Location
c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files\business objects\performance management 11.5
afhelp.war
Note: If performance management is not installed, this WAR file will not be present. Note: Replace <language_code> with the code specific to the language of your installation, for example en or fr.
WAR files modified or added in Productivity Pack

The following table shows the WAR files from BusinessObjects Enterprise R2 that have been modified or added in BusinessObjects Enterprise R2 Productivity Pack. If you have already installed and deployed them on your own version of Tomcat, WebLogic, WebSphere, SAP Web Application Server, or Oracle Application Server, you will need to undeploy these original WAR files replace them with the WAR files installed with the Productivity Pack. WAR files modified or replaced desktop.war BusinessProcessBI.war
Configuring the Java environment variable

After installing the Java SDK, you must set the JAVA_HOME environment variable. If your Java web application server installs the Java SDK as part of its installation process, install the application server first, and then set the environment variable. You need to know the directory path containing your Java SDK bin directory. 1. 2. 3. 4. 5. To set the JAVA_HOME environment variable on Windows Right-click My Computer, and select Properties. Click the Advanced tab. Click Environment Variables. In the System variables area, click New. In the Variable Name box, type JAVA_HOME.
129
6.
Enter the complete path to the directory containing your Java SDK bin directory in the Variable Value box. For example, enter C:\JDKLOCATION\jdk141_02 where JDKLOCATION is the directory where your JDK is installed. Click OK > OK > OK.
7.
Setting Tomcat properties

Check that these values are set for tomcat. Some of these values may have already been set by the installer; Some you will have to add. Note: Whenever you see the following variables, replace them with the path where you have installed the product.

1.
TOMCATDIR is the path where Tomcat is installed. BOBJDIR is the path where BusinessObjects Enterprise is installed. JAVA_HOME is the path where the Java JDK is installed. To verify the settings Open the Apache Tomcat Properties dialog. Go to the Start menu and select Apache Tomcat 5.0 >Configure Tomcat. Note: The previous path assumes you have setup Tomcat as a service. Click Stop to stop Tomcat. Ensure the Startup type is set to Automatic on the General tab. Click on the Logging tab. Ensure the following paths are set. Variable Log path: Redirect stdout redirect stderr Setting C:\TOMCATDIR\logs\ C:\TOMCATDIR\logs\stdout.l og C:\TOMCATDIR\logs\stderr.l og
2. 3. 4. 5.
6. 7. 8.
Click on the Java tab. Ensure Java Virtual Machine is set to this location:
C:\JAVA_HOME\j2re1.4.2\bin\server\jvm.dll
Ensure Java Classpath is set to C:\TOMCATDIR\bin\bootstrap.jar;C:JAVA_HOME\lib\tools.jar
130
9.
Ensure the following options are set under Java Options. Settings -Xrs -Djava.library.path=WINDIR\system32\;BOBJDIR\ BusinessObjects Enterprise 11.5\win32_x86\ ;BOBJDIR\OLAP Intelligence 11.5\DHTML Components\; -Dcatalina.base=TOMCATDIR -Dcatalina.home=TOMCATDIR -Djava.endorsed=TOMCATDIR\common\endorsed\ -Dbusinessobjects.olap.bin=BOBJDIR\OLAP Intelligence 11.5\DHTML Components -Dbusinessobjects.olap.stylesheets =BOBJDIR\OLAP Intelligence 11.5\stylesheets -Daf.configdir=BOBJDIR\Performance Management 11.5
10. Click on the Startup tab. Ensure Class is set to org.apache.catalina.startup.Bootstrap, Arguments to start and Mode to jvm. 11. Click on the Shutdown tab. Ensure Class is set to org.apache.catalina.startup.Bootstrap, Arguments to stop and Mode to jvm. 12. Click OK.
Setting up JAR files

1. 2. To set up the JAR files for BusinessObjects Enterprise Copy BOBJDIR\BusinessObjects Enterprise 11.5\java\applications\ cewcanative.jar to TOMCATDIR\shared\lib. Replace the xalan.jar located in TOMCATDIR\common\endorsed with the one from BOBJDIR\BusinessObjects Enterprise 11.5\java\xalan.jar.
Note: BusinessObjects Enterprise XI R2 requires version 2.5.2 of xalan.jar. These are files used by the XML parser. If you are sure your version of Tomcat has this version, you do not need to replace these files.
131
Deploying the WAR files

1. To deploy the war files Confirm the location of the WAR files. By default, the are located in c:\Program Files\Buisiness Object\BusinessObjects Enterprise 11.5\java\applications. Open a text editor. Create the files listed in the following table and add the content specified in the Content column to the files. This will set the context path for each WAR file. Substitute the variable WARDIR with default location or the specific directory where you placed your files. Note: As a general rule, WAR files must be deployed on the same machine as they were installed. This is because the installation will replace some text variables inside local WAR files with machine and CMS specific values at install. The one exception to this rule is the BusinessProcessBI.war file, which can be copied to any web application server and deployed there. If you plan on using Trusted Authentication on a different web application server than all your other BusinessObjects Enterprise application, see Configuring Trusted Authentication on a separate web application server in the BusinessObjects Enterprise Deployment and Configuration Guide before you deploy the BusinessProcessBI.war file. Note: If you install BusinessObjects Enterprise in a location other than the default installation directory of C:\Program Files\ Business Objects\BusinessObjects Enterprise 11.5\, adjust the path descriptions to match your actual install directories. Filename desktopwar.xml Content <Context docBase="WARDIR/ desktop.war" path="/businessobjects/ enterprise115/desktoplaunch" crossContext="false" debug="0" reloadable="false" trusted="false"/>
2. 3.
webcompadapterwar. <Context docBase="WARDIR/ xml webcompadapter.war" path="/ businessobjects" debug="0" reloadable="false"/> jsfadminwar.xml <Context docBase="WARDIR/ jsfadmin.war" path="/jsfadmin" debug="0" reloadable="false"/>
132
Filename adminwar.xml
Content <Context docBase="WARDIR/ admin.war path="/businessobjects/ enterprise115/adminlaunch" crossContext="false" debug="0" reloadable="false" trusted="false"/> <Context docBase="WARDIR/ adhoc.war path="/businessobjects/ enterprise115/adhoc" crossContext="false" debug="0" reloadable="false" trusted="false"/> <Context docBase="WARDIR/ AnalysisHelp.war" path="/ AnalysisHelp" crossContext="false" debug="0" reloadable="false" trusted="false"/>> <Context docBase="WARDIR\styles.war" path="/ styles" crossContext="false" debug="0" reloadable="false" trusted="false"/> <Context docBase="c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code>\dswsbobj e.war path="dswsbobje" crossContext="false" debug="0" reloadable="false" trusted="false"/> <Context docBase="c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code>\Business ProcessBI.war path="BusinessProcessBI" crossContext="false" debug="0" reloadable="false" trusted="false"/>
adhocwar.xml
analysishelpwar.xml
styleswar.xml
dswsbobjewar.xml
BusinessProcessBI.x ml
Note:
Desktop.war does not depend on any of the other war files so it can be deployed at any time. The remaining files have dependencies on each other so must be deployed in a specific order. First deploy the
133
webcompadapter.war, followed by jsfadmin.war and finally admin.war. Adhoc.war, analysishelp.war, styles.war, dswsbobje.war and BusinessProcessBI.war can now be deployed.
4. 5.
Replace <language_code> with the code specific to the language of your installation, for example en or fr. Save each file to TOMCATDIR\CONF\Catalina\localhost, where TOMCATDIR is replaced with the direcory where Tomcat is installed. Restart Tomcat. Open the Apache Tomcat Properties dialog. Go to the Start menu and select Apache Tomcat 5.0 >Configure Tomcat, and then, click Start to restart Tomcat. Restart Tomcat. Go to the directory ./shutdown.sh
./startup.sh
Integrating Crystal Reports Explorer with InfoView

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

To verify the Tomcat configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. To verify the Tomcat configuration Open a browser window.
134
2.
Enter the url for InfoView in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/desktoplaunch. For example: http://localhost:8080/businessobjects/enterprise115/desktoplaunch Enter the url for the administration launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ adminlaunch. For example: http://localhost:8080/businessobjects/enterprise115/adminlaunch
3.
135
136
Deploying on WebSphere
chapter
Deploying on WebSphere Before you start
Before you start

Before you begin the deployment process you should verified two things. First, you should verify that the application server is running correctly by launching its default page, or administrative console in a web browser.
For IBM WebSphere 5.1, type this:

http://servername:9090/admin.

http://servername:9060/ibm/console
Next you should verify that the CMS is running. To view the status of the CMS, go to the CMC and select Servers.
WAR File contents and context roots

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

The table that follows lists the contents of the WAR files.
138
WAR File desktop.war
Contents Contains Infoview and performance management components Note: If you plan on using Crystal Reports Explorer, see Integrating Crystal Reports Explorer with InfoView on page 149 before you deploy this WAR file. Contains older components of the Central Management Console Contains newer components of the Central Management Console Contains the administrative tools from the admin launchpad. These tools include administrative tool console, Schedule Manager, Instance Manager, View Server Summary, Query Builder, Object Repository Helper Contains performance management help files Contains Crystal Reports Explorer components Contains images, style sheets, and scripts used by the DHTML and Web Authoring components of OLAP Intelligence Contains OLAP Intelligence help files Contains Web Services. Contains Business Process BI Services
webcompadapter.war* jsfadmin.war* admin.war*
afhelp.war adhoc.war* styles.war
AnalysisHelp.war dswsbobje.war BusinesProcessBI.war Note:
If you install performance management after your initial install and deployment of BusinessObjects Enterprise, you will need to undeploy desktop.war and then redeploy it. This is not required if you install BusinessObjects Enterprise at the same time as performance management because the war file is modified by the performance management install before you deploy it. If you will not be using Crystal Report Explorer, you are not required to deploy adhoc.war.
139
If you will not be using OLAP Intelligence, you are not required to deploy AnalysisHelp.war or styles.war. If you will not be using Web Services, you are not required to deploy dswsbobje.war. If you will not be using Business Process BI Services, you are not required to deploy BusinessProcessBI.war. * These files are being patched or replaced as part of the Productivity Pack.
Context roots of the WAR files

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

The table that follows lists the locations of the WAR files. WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, AnalysisHelp.war dswsbobje.war, BusinessProcessBI.war Location
c:\Program files\business objects\businessobjects enterprise 11.5\java\applications c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files\business objects\performance management 11.5
afhelp.war
141
Deploying on WebSphere Deploying on IBM WebSphere
Deploying on IBM WebSphere

If you have WebSphere 5.1 or 6.0 and you want it to work with BusinessObjects Enterprise, you must perform some configuration and deploy the war files so you are able to use InfoView and the Central Management Console. The first part of this section explains how to perform steps such as:
Creating an application server on page 142 Starting the application server on page 143 Making configuration changes for distributed performance management on page 143 Starting the application server on page 143 Modifying the PATH on page 146 Making configuration changes for distributed performance management on page 143 Checking or changing the assigned port number on WebSphere 5.1 on page 147 Checking or changing the assigned port number on WebSphere 6.0 on page 147 Creating a new virtual host on page 148 Assigning an alias to the virtual host on page 148 Deploying the WAR files on page 148
The end of this section explains how you can verify the configuration a deployment. See Verifying the WebSphere Configuration on page 150, for more information.
Creating an application server

An application server is required. If you have already created one specifically for use with BusinessObjects Enterprise, you can skip this step. 1. To create an application server in WebSphere Start the IBM WebSphere Administrative Console in your browser.

2.

http://servername:9090/admin.

http://servername:9060/ibm/console
Logon to the administrative console.
142
3. 4. 5. 6. 7. 8.
Expand Servers and then click on Application Servers. Click New. Enter a name for the server in the Server Name field, and then click Next. Click Finish to create the new application server. Click the hyperlink Save. Click Save to save the configuration files.
Starting the application server
To start the application server on Windows Start the server. There are two ways you can start the server in Windows:
Open a DOS window, change to the directory C:\Program files\IBM\WebSphere\AppServer\bin and type startServer.bat server1 Go to the Start menu and select Programs > IBM WebSphere > Application Server >Start the Server.
Making configuration changes for distributed performance management

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

If you are using WebSphere you must copy the InitConfig.properties file to a different that has no spaces in the directory name. 1. To specify the location of your InitConfig.properties file Create a new folder on the drive on which BusinessObjects Enterprise is installed. Note: The folder name cannot contain spaces. 2. Copy the InitConfig.properties file to the folder you created in the previous step. The default location for this file is as follows:
143
C:\Program Files\Business Objects\Performance Management 11.5
Changing the classpath

1. To change the classpath Click on the server you created in Starting the application server or click on the server designated for use with BusinessObjects Enterprise. Note: If you arent logged on: a. Log into the administrative console. b. Expand Server, a click on Application Servers and then servername. 2. Go to the JVM page.
If you are using WebSphere 5.1, follow these steps to get to the JVM page. a. On the server page, scroll down until you see Process Definition in the Additional Properties column. Scroll down and click on Java Virtual Machine.
b. Click on Process Definition. c.
If you are using WebSphere 6.0, follow these steps to get to the JVM page. a. c. On the server page, select Java and Process Management. Select Java Virtual Machine. b. Select Process Definition.
3.
Enter the absolute path, including the file name for where cewcanative.jar is located in the classpath field. Note: The default location of this file is c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\java\applications\cewcanative.jar. Modify the path if you changed default location.
4.
If you are using performance management, click Generic JVM arguments then type the location of your InitConfig.Properties file. -Daf.configdir=C:\Progra~1\Busines~1\Perform~ Note: If you changed the default location for the InitConfig.properties file, specify the modified location for this file. See Copying your performance management InitConfig. properties file on page 143 for further information.
144
5.
If you are using the DHTML viewer and OLAP Intelligence, click Generic JVM arguments and then add the following single line to the JVM arguments:
-Dbusinessobjects.olap.bin=C:\PROGRA~1\BUSINE~1\ OLAPIN~1.5\DHTMLC~1 -Dbusinessobjects.olap.stylesheets=C:\PROGRA~1\BUSINE~1\ OLAPIN~1.5\styles~1 -Dbusinessobjects.olap.xslt.TransformerFactory= org.apache.xalan.processor.TransformerFactoryImpl
Note:

6. 7. 8.
The text should be entered as a single line, with spaces separating the arguments (denoted by the "-D"). The following argument is not required if you are using WebSphere 5.1:
-Dbusinessobjects.olap.xslt.TransformerFactory
Click Apply, and then click Save. Stop the server. Type stopserver.bat servername Stop the server. Type startserver.bat servername
Setting the heap size

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

1. To set the Path environment variable Locate the win32_X86 folder in the BusinessObjects Enterprise install tree. The default location for this is C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32_x86. 2. If you are deploying OLAP Intelligence and wish to use the DHTML viewer, locate the folder where the DHTML Components are installed. The default location for the DHTML components is C:\Program Files\Business Objects\OLAP Intelligence 11.5\DHTML Components. 3. 4. 5. 6. 7. 8. 9. Right-click on the My Computer icon on your desktop and then click the Advanced tab. Click Environment Variables. Scroll down until you find the Path System variable, and then doubleclick on it. Place your cursor in the Variable Value field. Depress your left arrow key until your cursor will go no further. Add the location of the BusinessObjects Enterprise win32_X86 folder, and then add a semi-colon. Add the location of the OLAP Intelligence DHTML viewer, and then add a semi-colon. Click OK twice.
146
Checking or changing the assigned port number on WebSphere 5.1

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

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

1. 2. 3. 4. To create a new virtual host Expand Environment, select Virtual Host and then click New. Enter the host name in the Name field, and then click OK. Click the hyperlink Save. Click Save to save the configuration files.
Assigning an alias to the virtual host

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

1. 2. 3. To deploy the WAR files Go to the administrative console. Expand Applications, and then click Install New Application Click Browse and find the location of the webcomponentadapter.war. Note: The default location for the WAR files is c:\Program Files\Business objects\BusinessObjects Enterprise 11.5\java\applications. 4. 5. Type the context root for the WAR file in the Context Root field, and click Next. Select these options on the next screen, then click Next:
Generate Default Bindings Use default virtual host name for Web modules
Note: Ensure default_host is displayed in the host name field.
148
6.
Accept the defaults on each page and click Next until you get to this step:

7. 8. 9.
For WebSphere 5.1 Step:3 Map modules to application servers. For WebSphere 6.0 Step:2 Map modules to servers.
Note: Each page may take several minutes to process. Select the application server you created from the Clusters and Servers field. Select the module to apply it to, and then click Apply. Click Next, and then click Finish. You will receive message when the process is complete. 10. Repeat the process for the remaining WAR files you wish to deploy. See Contents of the WAR files on page 138 for information on what each WAR file contains. You are not required to deploy a war file if you dont require a component it contains. Note: Desktop.war does not depend on any of the other war files so it can be deployed at any time. The remaining files have dependencies on each other so must be deployed in a specific order. First deploy the webcomponentadapter.war., followed by jsfadmin.war and finally admin.war. Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war and dswsbobje.war can now be deployed.
Ensuring War file is started

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

If you want to integrate Crystal Reports Explorer with InfoView, you have to modify the war file for infoview (desktop.war) before you it. 1. To integrate Crystal Reports Explorer Locate the desktop.war file. The default location for this file is C:\Program Files\Business
Objects\BusinessObjects Enterprise 11.5\java\applications.
Note: Be sure you make this change before you deploy desktop.war.
149
2. 3. 4. 5.
Open the zip file and extract adhoc-config.xml. This file is located in the WEB-INF directory. Modify the value between <serverpath> and </serverpath> with http://servername:portnumber/businessobjects/enterprise115/adhoc. Save the file. Place it back in desktop.war.
After you deploy adhoc.war, you will be able to access Crystal Reports Explorer if you enter http://servername:portnumber/businessobjects/ enterprise115/ached in your browser.
Verifying the WebSphere Configuration

To verify the configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. 2. To verify the WebSphere configuration Open a browser window. Enter the url for the desktop launchpad in the browser using the format http://[servername]:[port number]/businessobjects/enterprise115/ desktoplaunch. For example: http://localhost:9080/businessobjects/enterprise115/desktoplaunch 3. Enter the url for the administration launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ adminlaunch. For example: http://localhost:9080/businessobjects/enterprise115/adminlaunch Note: You cannot use the shortcuts in the BusinessObjects Enterprise program group to access the BusinessObjects Enterprise Launchpads deployed on your Java web application server. To access them, you must include the port number of the Java web application server in your URL. That is, to access the InfoView running on your Java web application server, type: http://servername:portnum/businessobjects/enterprise115/desktoplaunch/ InfoView/default.htm To access the BusinessObjects Enterprise Administration Launchpad running on your Java web application server, type: http://servername:portnum/businessobjects/enterprise115/adminlaunch/ launchpad.htm
150
where servername is the name of the server, and portnum is the port number of the Java web application server.
151
152
Deploying on WebLogic
chapter
10
Deploying on WebLogic Before you start
Before you start

Before you begin the deployment process, you should verify that the application server is running correctly by launching its default page, or administrative console in a web browser. For BEA WebLogic 8, type http://
servername:7001/console.


The table that follows lists the contents of the WAR files. WAR File webcompadapter.war jsfadmin.war Contents Contains older components of the Central Management Console Contains newer components of the Central Management Console
154
10
WAR File desktop.war
Contents Contains Infoview and performance management components Note: If you plan on using Crystal Reports Explorer, see Integrating Crystal Reports Explorer with InfoView on page 164 before you deploy this WAR file. Contains the administrative tools from the admin launchpad. These tools include administrative tool console, Schedule Manager, Instance Manager, View Server Summary, Query Builder,Object Repository Helper Contains performance management help files Note: If performance management is not installed, this WAR file will not be installed. Contains Crystal Reports Explorer components Contains images, style sheets, and scripts used by the DHTML and Web Authoring components of OLAP Intelligence Contains OLAP Intelligence help files Contains Web Services Contains Business Process BI
admin.war
afhelp.war
adhoc.war styles.war
AnalysisHelp.war dswsbobje.war BusinessProcessBI.war Note:
If you install performance management after your initial install and deployment of BusinessObjects Enterprise, you will need to undeploy desktop.war and then redeploy it. This is not required if you install BusinessObjects Enterprise at the same time as performance management because the war file is modified by the performance management install before you deploy it. If you will not be using Crystal Report Explorer, you are not required to deploy adhoc.war. If you will not be using OLAP Intelligence, you are not required to deploy either AnalysisHelp.war or styles.war.
155
10
If you will not be using Web Services, you are not required to deploy dswsbobje.war. If you will not be using Business Process BI, you are not required to deploy BusinessProcessBI.war. If you will not be using performance management, you are not required to deploy afhelp.war.

The table that follows lists the context roots that should be used when you deploy the war files. War File desktop.war webcompadapter.war jsfadmin.war admin.war afhelp.war styles.war AnalysisHelp.war adhoc.war dswsbobje.war BusinessProcesBI Note: Context Root /businessobjects/enterprise115/desktoplaunch /businessobjects /jsfadmin /businessobjects/enterprise115/adminlaunch /bobj /styles /AnalysisHelp /businessobjects/enterprise115/adhoc /dswsbobje /BusinessProcessBI
It is not recommended that you alter the context root because many of the war file have dependencies on each other. For example, if you change the context root of either jsfadmin.war or webcompadapter.war, calls made between different components of the Central Management Console will not work. Desktop.war can be deployed at any time. The remaining files have dependencies so must be deployed in a specific order. First deploy the webcompadapter.war, followed by jsfadmin.war and finally admin.war. Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war and dswsbobje.war can now be deployed. Desktop.war can be deployed without webcompadapter.war. However, if you deploy it on a web application server without webcompadapter.war, you will not be able to not be able to use the InfoView function to add documents from your local computer to InfoView.
156
Deploying on WebLogic Deploying on BEA WebLogic
10

The table that follows lists the locations of the WAR files. WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, AnalysisHelp.war dswsbobje.war Location
c:\Program files\business objects\businessobjects enterprise 11.5\java\applications c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files \business objects\ performance management 11.5
afhelp.war
Note: If performance management is not installed, this WAR file will not be present. Note: Replace language_code with the code specific to the language of your installation, for example en or fr.
Deploying on BEA WebLogic

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

The WAR files have no weblogic.xml deployment descriptor file inside. This means that WebLogic will deploy each web Module under the Context Root of the file name, (e.g. desktop.war under the Context Root of /desktop), unless you specify otherwise. If you want to choose a context root other than the file name, complete this step; otherwise, skip this step. Note: You can't change the Context Root once the WAR file has been deployed.
Setting a context root with WebLogic Builder

1. 2. 3. To set the context root with WebLogic Builder Open WebLogic builder. From the Start menu, select Programs > Bea Weblogic Platform 8.1 >Other Development Tools >WebLogic Builder. Select File > Open. Browse and select the WAR file you want and click Open. Note: The default location for the files is C:\Program files\Business Objects\Business Objects 115\java\applications. 4. 5. 6. Click Yes when you receive the message Would you like New descriptors created for you?. Click on the Context Path tab. Enter the context path that applies to the WAR file in the context path field. WAR File desktop.war admin.war jsfadmin.war webcompadapter.war adhoc.war afhelp.war AnalysisHelp.war styles.war Context Path /businessobjects/ enterprise115/desktop /businessobjects/ enterprise115/adminlaunch /jsfadmin /businessobjects /businessobjects/ enterprise115/adhoc /bobj /analysishelp /styles
158
10
WAR File dswsbobje.war BusinessProcessBI.war
Context Path /dswsbobje /BusinessProcessBI
Note: Please see Contents of the WAR files on page 154 to determine which war files need to be deployed, based on the components you have installed. 7. 8. 9. Select File, then Save. Select File, then Exit. Repeat this procedure for each of the remaining WAR files you want to deploy.

If you have performance management in a distributed environment, you must copy the InitConfig.properties file from one machine to the other so that you can log on to performance management. If you are using UNIX, you may need to copy the InitConfig.properties file to a different that has no spaces in the directory name. 1. To specify the location of your InitConfig.properties file Create a new folder on the drive on which BusinessObjects Enterprise is installed. Note: The folder name cannot contain spaces. 2. Copy the InitConfig.properties file to the folder you created in the previous step. The default location for this file is as follows: C:\Program Files\Business Objects\Performance Management 11.5
Preparing afhelp.war for deployment

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

This step details how to create a domain on WebLogic with the Configuration Wizard. If you already have a domain created, you can skip this step and perform the rest of the steps on the domain you plan to use for BusinessObjects Enterprise. Note: See the BEA WebLogic documentation for alternate methods of creating a domain. 1. 2. 3. 4. 5. 6. To Create the Domain in WebLogic Launch the WebLogic Configuration Wizard. From the Start menu, select Programs > Bea Weblogic Platform 8.1 >Configuration Wizard. Select Create a new WebLogic configuration, and then click Next. Select Create a new WebLogic configuration, and then click Next. Select Basic WebLogic Server Domain from the list of Configuration Templates, and click Next. Select Express from the Choose Express or Custom Configuration dialog, and click Next. Enter a User Name and Password. Confirm the password, and then click Next. Tip: Remember this information or you will not be able to use WebLogic later. 7. Click Create on the Create WebLogic Configuration dialog.
160
10
Tip: The default name for your domain is mydomain. Modify the Configuration Name field if you want to change the default name. You will receive a message when the configuration completes. 8. Click Done, and then click Exit.
Changing the CLASSPATH in WebLogic

WebLogic needs to know where BusinessObjects Enterprise components are installed. This is done in the following ways:
Setting the CLASSPATH Setting the PATH Setting either the LD_LIBRARY_PATH, the LIBPATH or the SHLIB_PATH, depending on your operating system, in the configuration file WebLogic uses when it starts up. To set the CLASSPATH in WebLogic Open the WebLogic loader script in a text editor. This file is called StartWeblogic.cmd and is found in the directory [WebLogic_Home]\user_projects\domains\mydomain\startWebLogic.cm d, where WebLogic_Home is directory where WebLogic is installed. Note: If you find this file in the directory [WebLogic_Home]\ weblogic81\samples\domains\platform, you have not created a domain, which is required. For further information, see jar uf /the/path/to/ afhelp.war ./WEB-INF/web.xml on page 160.
1.
2. 3.
Locate the line that begins with set CLASSPATH=... Add the path for cewcanative.jar, including cewcanative.jar, to the CLASSPATH variable. By default, the cewcanative.jar file is found in the directory C:\Program Files\Business Objects\BusinessObjects Enterprise 115\java\applications\. If the default path was changed for your installation of BusinessObjects Enterprise, modify the path accordingly. For example: set CLASSPATH=%WEBLOGIC_CLASSPATH%;% POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar ;%WL_HOME%\server\lib\webservices.jar;C:\Program Files\Business Objects\BusinessObjects Enterprise 115\java\applications\cewcanative.Jar;%CLASSPATH% Note: The only space in the definition is between the first occurrence of Business and Objects. If your JAR file is in a different location, change the directory accordingly.
161
10
4.
Save and close the file.
Modifying the PATH

1. 2. 3. 4. 5. To set the Path environment variable Right-click on the My Computer icon on your desktop and then click the Advanced tab. Click Environment Variables. Scroll down until you find the Path System variable, and then doubleclick on it. Place your cursor in the Variable Value field. Depress your left arrow key until your cursor will go no further. Add the location of the BusinessObjects Enterprise win32_X86 folder, and then add a semi-colon. C:\Program Files\Business Objects\BusinessObjects Enterprise 115\win32_x86. 6. If you are deploying OLAP Intelligence and wish to use the DHTML viewer, add the location of the OLAP Intelligence DHTML viewer, and then add a semi-colon. The default location for the DHTML components is C:\Program Files\Business Objects\OLAP Intelligence 11.5\DHTML Components. 7. Click OK twice.
Setting the Java Virtual Machine options for OLAP Intelligence and performance management
If you want to use the OLAP Intelligence DHTML viewer or performance management, you must modify the Java Virtual Machine (JVM) options in WebLogic. 1. To add the JVM options in WebLogic If you want to use the OLAP Intelligence DHTML viewer, open the file startWeblogic.cmd and add the following after the PATH and CLASSPATH settings:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dbusinessobjects.olap.bin=C:\Progra~1\Busine~1\ OLAPIn~1.5\DHTMLC~1 -Dbusinessobjects.olap.stylesheets=C:\Progra~1\Busine~1\ OLAPIn~1.5\styles~1
162
10
-Dbusinessobjects.olap.xslt.TransformerFactory= org.apache.xalan.processor.TransformerFactoryImpl -Djava.library.path=C:\PROGRA~1\BUSINE~1\OLAPIN~1\ DHTMLC~1
Note: The text should be entered as a single line, with spaces separating the arguments (denoted by the "-D"). 2. If you want to use performance management, add the location for the Initconfig.properties file to the Java options. -Daf.configdir="<INSTALLDIR>\BUSINE~1\PERFOR~1.5\ Note: If you changed the default location for the InitConfig.properties file, specify the modified location for this file. See Copying your performance management InitConfig. properties file on page 159 for more information.

1. Start the WebLogic Admin server. To start the admin server, open a console window, navigate to the [WebLogic installdir]\user_projects\mydomain directory, then execute startWebLogic.cmd. Tip: To start the Admin server a different way, you can go to the Start menu and select Programs> Bea Weblogic Platform 8.1 >User Projects>My Domain > Start Server. 2. 3. 4. 5. 6. Launch the Admin console. Open a browser window, type http://<host name>:7001/console and then press Enter. Enter the username and password. Expand Deployments on the left pane, and then select Web Application Modules. Click Deploy a New Web Application Module from the right pane. Navigate to the location of the webcompadapter.war. Note: The default location for the WAR files is c:\Program Files\Business objects\BusinessObjects Enterprise 115\java\applications. 7. 8. 9. Click the button beside the file, and then click Target Module. The Review your choices and deploy window will appear. Click Deploy. It may several minutes for the deployment to complete. Repeat steps 4 to 8 to deploy or the remaining WAR files you wish to deploy.
163
10
See Contents of the WAR files on page 154 for information on what each WAR file contains. You are not required to deploy a war file if you dont require a component it contains. Note: Desktop.war does not depend on any of the other war files so it can be deployed at any time. The remaining files have dependencies so must be deployed in a specific order. First deploy the webcomponentadapter.war., followed by jsfadmin.war and finally admin.war. Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war and dswsbobje.war can now be deployed.

If you want to integrate Crystal Reports Explorer with Infoview, you have to modify the war file for infoview (desktop.war) before you it. 1. To integrate Crystal Reports Explorer Locate the desktop.war file. The default location for this file is C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\java\applications. 2. 3. 4. Open the WAR file and extract adhoc-config.xml. Modify the value between <serverpath> and </serverpath> with http://servername:portnumber/businessobjects/enterprise115/adhoc. Save the file.
After you deploy adhoc.war, uou will be able to access Crystal Reports Explorer if you enter http://servername:portnumber/businessobjects/ enterprise115/adhoc in your browser.
Verifying the WebLogic Configuration

To verify the configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. To verify the WebLogic configuration Open a browser window. Enter the url for the desktop launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ desktoplaunch. For example: http://localhost:7001/businessobjects/enterprise115/desktoplaunch
164
10
2.
Enter the url for the administration launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ adminlaunch. For example: http://localhost:7001/businessobjects/enterprise115/adminlaunch
Note: You cannot use the shortcuts in the BusinessObjects Enterprise program group to access the BusinessObjects Enterprise Launchpads deployed on your Java web application server. To access them, you must include the port number of the Java web application server in your URL.
To access the InfoView running on your Java web application server, type:
http://server01:portnum/businessobjects/enterprise115/ desktoplaunch
To access the BusinessObjects Enterprise Administration Launchpad running on your Java web application server, type:
http://server01:portnum/businessobjects/enterprise115/ adminlaunch
where server01 is the name of the server, and portnum is the port number of the Java web application server.
165
10
166
Deploying on Oracle Application Server
chapter
11
Deploying on Oracle Application Server Before you start
Before you start

Before you begin the deployment process, you should verify that the application server is running correctly by launching its default page, or administrative console in a web browser. For Oracle 10g, type http://
servername:1810/.


The table that follows lists the contents of the WAR files. WAR File webcompadapter.war jsfadmin.war desktop.war Contents Contains older components of the Central Management Console Contains newer components of the Central Management Console Contains Infoview and performance management components
168
11
WAR File admin.war
Contents Contains the administrative tools from the admin launchpad. These tools include administrative tool console, Schedule Manager, Instance Manager, View Server Summary, Query Builder, Object Repository Helper Contains performance management help files Note: If performance management is not installed, this WAR file will not be installed. Contains Crystal Reports Explorer components Contains images, style sheets, and scripts used by the DHTML and Web Authoring components of OLAP Intelligence Contains OLAP Intelligence help files Contains Web Services. Contains Business Process BI
afhelp.war
AnalysisHelp.war dswsbobje.war BusinessProcessBI.war Note:
If you install performance management after your initial install and deployment of BusinessObjects Enterprise, you will need to undeploy desktop.war and then redeploy it. This is not required if you install BusinessObjects Enterprise at the same time as performance management because the war file is modified by the performance management install before you deploy it. If you will not be using Crystal Report Explorer, you are not required to deploy adhoc.war. If you will not be using OLAP Intelligence, you are not required to deploy either AnalysisHelp.war or styles.war. If you will not be using Web Services, you are not required to deploy dswsbobje.war. If you will not be using performance management, you are not required to deploy afhelp.war.
169
11

The table that follows lists the context roots that should be used when you deploy the war files. War File desktop.war webcompadapter.war jsfadmin.war admin.war styles.war afhelp.war AnalysisHelp.war adhoc.war dswsbobje.war BusinessProcessBI.war Context Root /businessobjects/enterprise115/desktoplaunch /businessobjects /jsfadmin /businessobjects/enterprise115/adminlaunch /styles /bobj /AnalysisHelp /businessobjects/enterprise115/adhoc /dswsbobje /BusinessProcessBI
170
Deploying on Oracle Application Server Deploying with Oracle
11
Note:
It is not recommended that you alter the context root because many of the war file have dependencies on each other. For example, if you change the context root of either jsfadmin.war or webcompadapter.war, calls made between different components of the Central Management Console will not work. Desktop.war can be deployed at any time. The remaining files have dependencies so must be deployed in a specific order. First deploy the webcompadapter.war, followed by jsfadmin.war and finally admin.war. Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war and dswsbobje.war can now be deployed. Desktop.war can be deployed without webcompadapter.war. However, if you deploy it on a web application server without webcompadapter.war, you will not be able to not be able to use the InfoView function to add documents from your local computer to InfoView.

The table that follows lists the locations of the WAR files. WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, AnalysisHelp.war dswsbobje.war, BusinessProcessBI.war Location
c:\Program files \business objects\ businessobjects enterprise 11.5 \java\applications c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files\ business objects\ performance management 11.5
afhelp.war
Note: Replace <language_code> with the code specific to the language of your installation, for example en or fr
Deploying with Oracle

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

1. Open a browser window and enter the following: http://<host name>:1810. Enter ias_admin for the username, and the password that was set during the install. Click on the name of the OC4J instance whose class path you will modify. Note: If the instance is not yet started, select the instance, and then click Start. After you receive confirmation that the instance has been started, click on the name of the instance to modify. 3. 4. 5. 6. 7. 8. Click the Administration tab. Click the Global Web Module link under Application Defaults. Click the General link under Properties. Locate the Class Path section of the page Click Add Another Row under Class Paths. Enter the path for cewcanative.jar, including cewcanative.jar, in the path field. If you have not changed the default directory for Business Objects, the setting for this field would be C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\java\applications\ cewcanative.jar. If the default path was changed for your installation of BusinessObjects Enterprise, modify the path accordingly. Click Apply.
2.
9.
10. Click OK after you receive confirmation that the message that the property changes have been saved.
Changing Memory Allocation Pool

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

If you have performance management in a distributed environment, you must copy the InitConfig.properties file from one machine to the other so that you can log on to performance management. If you are using UNIX, you may need to copy the InitConfig.properties file to a different that has no spaces in the directory name. 1. To specify the location of your InitConfig.properties file Create a new folder on the drive on which BusinessObjects Enterprise is installed. Note: The folder name cannot contain spaces. 2. Copy the InitConfig.properties file to the folder you created in the previous step. The default location for this file is as follows: C:\Program Files\Business Objects\Performance Management 11.5
Setting the PATH environment variable

1. 2. 3. 4. To set the PATH Click on the Administration tab for the appropriate instance. Click on Server Properties under Instance Properties. Scroll down until you see Environment Variables. Click Add Environment Variable.
173
11
5. 6.
Type PATH in the Name field. Enter the absolute path to the win32_x86 directory, starting and ending with quotes, in the Value field, and then click Apply. Note: The default path for this is c:\Program Files\Business Objects\BusinessObjects Enterprise11.5\win32_x86. Modify your path if you changed the default path.
Changing the command line options for OLAP Intelligence or performance management
Note: If you are not using OLAP Intelligence or performance management, these steps are not required. 1. To change the command line options If you want to use the DHTML Viewer with OLAP Intelligence, append the following value to your Java Options:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dbusinessobjects.olap.bin=C:\Progra~1\Busine~1\ OLAPIn~1.5\DHTMLC~1 -Dbusinessobjects.olap.stylesheets=C:\Progra~1\Busine~1\ OLAPIn~1.5\styles~1 -Dbusinessobjects.olap.xslt.TransformerFactory= org.apache.xalan.processor.TransformerFactoryImpl -Djava.library.path=C:\PROGRA~1\BUSINE~1\OLAPIN~1\ DHTMLC~1
Note:

2.
The text should be entered as a single line, with spaces separating the arguments (denoted by the "-D"). Append these values only after you have completed." Changing Memory Allocation Pool on page 172. This step contains procedural details on how to set your Java Options.
If you are using performance management, add the following Java arguments that specify the location of your InitConfig.Properties file. -Daf.configdir=C:\Progra~1\Busines~1\Perform~ Note: -If you changed the default location for the InitConfig.properties file, specify the modified location for this file. See Copying your performance management InitConfig. properties file on page 173 for further information.
3.
Click Yes when you receive the message that the application server must be restarted before the changes take affect.
174
11

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

War files can be deployed from two places:
From the Administration console. From the command line. You may wish to use the command line if you encounter problems with the deployment of WAR files when using the Administration Console, due to limited space in Oracles directory /var/tmp. Note: This may be the case when you deploy the desktop.war that includes performance management. Note: The default location for the WAR files is c:\Program Files\Business objects\BusinessObjects Enterprise 11.5\java\applications. Modify your path accordingly if you changed the installation default.
175
11
1. 2.
To deploy the war files from the command line Locate the directory where your instance of Oracle is installed. Go to following directory, where ORACLE_HOME is the location where Oracle Application Server is installed: <ORACLE_HOME>/dcm/bin Issue the following command for each WAR file you want to deploy.
dcmctl deployapplication -co <OC4J_INSTANCE_NAME>-a <APPLICATION NAME> -f <LOCATION OF THE APPLICATION>\<WAR/EAR File Name> -rc <ROOT CONTEXT>
3.
1. 2. 3.
To deploy the war files Click on the Applications tab from the server home. Click Deploy WAR file. Click Browse and then find desktop.war. Note: The default location for the WAR files is c:\Program Files\Business objects\BusinessObjects Enterprise 11.5\java\applications. Modify your path accordingly if you changed the installation default.
4. 5. 6. 7.
Enter the name you want to call the application in the Application Name field. Enter the context root for the WAR file in the Map to URL field. Click Deploy. Repeat the process for jsfadmin.war, admin.war and desktop.war. If you are not using OLAP Intelligence, you do not need to deploy AnalysisHelp.war or styles.war. Note:
Desktop.war does not depend on any of the other war files so it can be deployed at any time. The remaining files have dependencies on each other so must be deployed in a specific order. First deploy the webcomponentadapter.war., followed by jsfadmin.war and finally admin.war. Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war and dswsbobje.war can now be deployed. If you will not be using Crystal Report Explorer, you are not required to deploy adhoc.war. If you will not be using OLAP Intelligence, you are not required to deploy either AnalysisHelp.war or styles.war. If you will not be using Web Services, you are not required to deploy dswsbobje.war.
176
11
If you will not be using performance management, you are not required to deploy afhelp.war.

Desktop.war contains the components for InfoView; Adhoc.war contains the components for Crystal Reports Explorer. If you want to integrate Crystal Reports Explorer with InfoView, you must make some changes in desktop.war before it is deployed. 1. 2. To integrate Crystal Reports Explorer Stop your web server. Locate the desktop.war file. The default location for this file is C:\Program Files\Business
3. 4. 5. 6.
Open the WAR file and extract adhoc-config.xml. Modify the value between <serverpath> and </serverpath> with http://servername:portnumber/businessobjects/enterprise115/adhoc. Save the file. Place it back in desktop.war.
Verifying the Oracle Configuration

To verify the Oracle configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. 2. To verify the Oracle configuration Open a browser window. Enter the url for the desktop launchpad in the browser using the format http://[hostname]:[port number]/businessobjects/enterprise115/ desktoplaunch. For example: http://localhost:1810/businessobjects/enterprise115/desktoplaunch 3. Enter the url for the administration launchpad in the browser using the format http://[hostname]:[port number]/businessobjects/enterprise115/ adminlaunch. For example: http://localhost:1810/businessobjects/enterprise115/adminlaunch
177
11
Note: You cannot use the shortcuts in the BusinessObjects Enterprise program group to access the BusinessObjects Enterprise Launchpads deployed on your Java web application server. To access them, you must include the port number of the Java web application server in your URL. That is, to access the InfoView running on your Java web application server, type: http://server01:portnum/businessobjects/enterprise115/desktoplaunch/ InfoView/default.htm To access the BusinessObjects Enterprise Administration Launchpad running on your Java web application server, type: http://server01:portnum/businessobjects/enterprise115/adminlaunch/ launchpad.htm where server01 is the name of the server, and portnum is the port number of the Java web application server.
178
Deploying on SAP Web Application Server
chapter
12
Deploying on SAP Web Application Server
This section explains how to deploy with SAP Web Application Server, formerly known as NetWeaver. The first part of this section explains how to perform steps such as:
Modifying the PATH Creating an EAR file Deploying the EAR files
180
Deploying on SAP Web Application Server Before you start
12
Before you start

Before you begin the deployment process, you should verify that the application server is running correctly by launching its default page, or administrative console in a web browser. For SAP Web Application Server, type http://servername:50000/index.html.
WAR file contents and context roots

WAR file contents

The table that follows lists the contents of the WAR files. WAR File webcompadapter.war jsfadmin.war desktop.war Contents Contains older components of the Central Management Console Contains newer components of the Central Management Console Contains Infoview and performance management components
181
12
Deploying on SAP Web Application Server Before you start
WAR File admin.war
Contents Contains the administrative tools from the admin launchpad. These tools include administrative tool console, Schedule Manager, Instance Manager, View Server Summary, Query Builder,Object Repository Helper Contains Crystal Reports Explorer components Contains Web Services.
adhoc.war dswsbobje.war Note:
If you install performance management after your initial install and deployment of BusinessObjects Enterprise, you will need to undeploy desktop.war and then redploy it. This is not required if you install BusinessObjects Enterprise at the same time as performance management because the war file is modifed by the performance management install before you deploy it. If you will not be using Crystal Report Explorer, you are not required to deploy adhoc.war. If you will not be using Web Services, you are not required to deploy dswsbobje.war.
WAR file context roots

Use the context roots listed in the following table when you deploy the war files. War File desktop.war webcompadapter.war jsfadminwar. admin.war adhoc.war dswsbobje.war Context Root /businessobjects/enterprise115/desktoplaunch /businessobjects /jsfadmin /businessobjects/enterprise115/adminlaunch /adhoc /dswsbobje
182
Deploying on SAP Web Application Server Deploying with SAP Web Application Server
12
Note: It is not recommended that you alter the context root because many of the war file have dependcies on each other. For example, if you change the context root of either jsfadmin.war or webcompadapter.war, calls made between different components of the Central Management Console will not work.

The table that follows lists the locations of the WAR files. WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, analysishelp.war dswsbobje.war Location
c:\Program files\business objects\businessobjects enterprise 11.5\java\applications c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files\business objects\performance management 11.5
afhelp.war
Deploying with SAP Web Application Server

If you have SAP Web Application Server and you want it to work with BusinessObjects Enterprise, you perform some configuration and deploy the war file so you are able to use InfoView and the Central Management Console. The first part of this section explains how to perform steps such as:
Modifying the PATH Creating an EAR file Note: On SAP Web Application Server, an EAR file is required to deploy applications. The BusinessObjects Enterprise WAR file files are used to create the EAR files.
Deploying the EAR files
183
12
Note: The class path can also altered in this step. The end of this section explains how you can verify the configuration a deployment. See Verifying the Web Application Server Configuration on page 187.
Modifying the PATH

1. To set the Path environment variable Locate the win32_X86 folder in the BusinessObjects Enterprise install tree. The default location for this is C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32_x86. Right-click on the My Computer icon on your desktop and then click the Advanced tab. Click Environment Variables. Scroll down until you find the Path System variable, and then doubleclick on it. Place your cursor in the Variable Value field. Depress your left arrow key until your cursor will go no further. Add the location of the BusinessObjects Enterprise win32_X86 folder, and then add a semi-colon. Tip: If you use the folder option in Windows Explorer, you can simply cut and paste the location of this folder rather than typing it. 7. Click OK twice.
2. 3. 4. 5. 6.
Creating an EAR file

In SAP Web Application Server, you need to put each WAR file in an EAR file before you deploy it. To do this, you can use the SAP Web Application Server deployment tool. 1. To create an EAR file. Launch Choose the SAP Web Application Server deployment tool. Go to the directory where DeployTool.bat is located. Generally it can be found in this directory C:\usr\sap\J2E\JC00\j2ee\deploying. Double-click on DeployTool.bat to launch the tool. Create a new project. Go to the Project menu and select New Project. Enter a project name in the Address filed, and then click OK. Right-click the Assembler tab.
2. 3. 4. 5.
184
12
6. 7.
Right-click on the project name you created, and then choose Add Archive. Navigate to the WAR file for the InfoView at C:\Program
Files\Business Objects\BusinessObjects Enterprise\java\applications\desktop.war.
The name and the path of the WAR file will be displayed in the Address field. 8. 9. Click OK. Skip this step if you dont want to modify the context root for the file: otherwise, enter the name you desire in the Context Root field, and then click Modify.
10. Right click on the project name and select Make Ear. 11. Enter a name for the EAR file in the Address field, and then click OK. When the EAR file creation is done, you will receive a message at the bottom of the window stating ear file created successfully. 12. Follow the previous steps to create an EAR file for webcomponentadapter.war,jsfadmin.war and admin.war. 13. Exit the deployment tool and save your project when you exit.
Deploying the EAR file

1. To deploy the EAR file Go to location C:\usr\sap\J2E\Jc--\J2ee\admin, and then doubleclick on go.bat. The Visual Administrator will launch. 2. 3. Go to the Connect menu and then select Login. Click New. Note: If the J2EE machine name list already contains the name of the machine you want to, skip the next two steps. 4. 5. 6. 7. Enter the machine name in the Display Name field, select Direct connection to Dispatcher mode, and then click Next. Fill out the User Name, Host, and Http: Port field, and then click Save. Select the machine name where you want to deploy you EAR file to in the J2EE machine name dialog and then click Connect. Enter the Administrators password in the Password field, and then click Connect.
185
12
8. 9.
Expand the Server_name you want to deploy on under Dispatcher_ name. Expand Services, and then select Deploy.
10. Select the Server_name under Deploy Services, and then click Deploy. 11. Browse for the EAR file you want to deploy. To browse for files, click the button to the right of the File field in the Deploy Dialog. Note: Desktop.war can be deployed at any time. The remaining files have dependencies on each other so must be deployed in a specific order. First deploy the webcompadapter.war, followed by jsfadmin.war and finally admin.war. 12. Check which file is being deployed:
If the EAR file, contains desktop.war, click on the EAR file in the Choose an EAR file dialog, and then click OK. If the EAR file, contains webcomponentadapter.war, jsfadmin.war or admin.war, the classpath will need to be altered. a. Click on the Change button beside Additional Class Path. The Classpath Management window will appear. b. Find the directory that contains cewcanative.jar in the Directories field. Note: If you have not changed the default directory for Business Objects, the setting for this field would be C:\Program Files\Business Objects\BusinessObjects Enterprise 115.\java\applications\ cewcanative.jar. a. Select cewcanative.jar from the Files field, and then click Add. The absolute path to the jar file, including the jar file itself, will be added to the clasps field. b. Click OK.
13. Click OK in the Deploy dialog. You will informing you what directory the file will be extracted from and informing you that the content of the directory will be deleted after the deploy. 14. Click OK, and then OK again to confirm. The file will begin to deploy, when the status bar reaches 100%, the deployment is complete. The speed of this will vary depending on you processor speed and what other application are using resources when you deploy.
186
12
15. Click Start Application when the status bar reaches 100%. 16. Open a browser and type http://servername:50000/index.html. Note: By default, SAP Web Application Server uses port 50000. If you configured your application server to use a different port number, substitute that port number in the URL. 17. Log on to the service that you will be using with Administrator and password privileges. 18. Click Server Under J2EE, and then click Services>Deploy. 19. For each EAR file that you created, perform the following steps:
Click Server, then click Deploy. Browse to the EAR files location, then click OK. To test the application, click Start Application.

After you have deployed adhoc.war, it needs to be integrated with InfoView. 1. To integrate Crystal Reports Explorer Locate the desktop.war file. The default location for this file is
2. 3. 4. 5.
Open the zip file and extract adhoc-config.xml. Modify the value between <serverpath> and </serverpath> with http://servername:portnumber/businessobjects/enterprise115/adhoc. Save the file. Place it back in desktop.war.
You can now access Crystal Reports Explorer if you enter http:// servername:portnumber/businessobjects/enterprise115/adhoc in your browser.
Verifying the Web Application Server Configuration

To verify the configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. 2. To verify the WebSphere configuration Open a browser window. Enter the url for the desktop launchpad in the browser using the format http://[hostname]:[port number]/desktop/launchpad.html.For example:
187
12
http://localhost:5000/desktop/launchpad.html Enter the url for the administration launchpad in the browser using the format http://[hostname]:[port number]/businessobjects/enterprise115/ adminlaunch/launchpad.html. For example: http://localhost:5000//businessobjects/enterprise115/adminlaunch/ launchpad.html. Note: You cannot use the shortcuts in the BusinessObjects Enterprise program group to access the BusinessObjects Enterprise Launchpads deployed on your Java web application server. To access them, you must include the port number of the Java web application server in your URL. That is, to access the InfoView running on your Java web application server, type: http://server01:portnum/businessobjects/enterprise115/desktoplaunch/ InfoView/default.htm To access the BusinessObjects Enterprise Administration Launchpad running on your Java web application server, type: http://server01:portnum/businessobjects/enterprise115/adminlaunch/ launchpad.htm where server01 is the name of the server, and portnum is the port number of the Java web application server.
188
Importing Objects to BusinessObjects Enterprise
chapter
13
Importing Objects to BusinessObjects Enterprise Importing information
Importing information
The Import Wizard is a locally installed Windows application that allows you to import existing user accounts, groups, folders, and reports to your new BusinessObjects Enterprise system. The Import Wizard runs only on Windows, but you can use it to import information from a source environment that is running on Windows or UNIX to a new BusinessObjects Enterprise system that is running on Windows or on UNIX. You can import information from any of these products:
BusinessObjects Enterprise XI or XI R2 Crystal Enterprise 8.5, 9, or 10 Business Intelligence Archive Resource (BIAR) files Note: A BIAR file is a packaged BI Application Resource. It is a portable, deployable package of the contents of a BI Application that can be used to easily deploy the entire set of interrelated content in a single simple action. From a technical perspective, it is a ZIP file containing the following: A series of other compressed files for all of the reports, universes, and other FRS objects contained in the BI Application. BusinessObjects 5.x or 6.x Note: The Import Wizard migrates Application Foundation objects from your 6.x deployment to performance management XI R2. For information on migration from BusinessObjects 5.x/6.x, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide.
A Deployment Manifest (BusinessObjects.xml).
Text files Text files can be used to import users, groups and profiles or data source credentials. See Using text files with the Import Wizard on page 242 for further information.
The functionality provided by the Import Wizard varies, depending upon the product from which you are importing information. In general, the Import Wizard imports settings that are specific to each object, rather than global system settings. For instance, a global minimum number of characters password restriction is not imported. But a user-level must change password at next log on restriction is imported with the user account.
190
Importing Objects to BusinessObjects Enterprise Importing information from Crystal Enterprise
13
The Import Wizard also has an option that allows you to control what happens when you import an object that already exists in the destination environment. This feature, know as incremental import allows you to decide whether or not to overwrite object contents and object rights. You may want to use this feature if the objects have changed or if passwords, profiles or group memberships have changed since you imported them the first time. See Choosing an import scenario on page 230. For details, see the section for the product from which you are importing information:
Importing information from Crystal Enterprise on page 191 Importing Application Foundation objects on page 195 Importing information from BusinessObjects 5.x or 6.x on page 195
For procedural details, see Using the Import Wizard on page 215.
BusinessObjects documents
Desktop Intelligence (.rep,.rea,.ret) documents, previously known as BusinessObjects full-client documents, are now supported in BusinessObjects Enterprise XI R2. To migrate .rep documents you can use the Import Wizard.
Importing information from Crystal Enterprise

If you have upgraded from Crystal Enterprise, use the Import Wizard to import existing user accounts, groups, folders, report objects, and report instances to BusinessObjects Enterprise XI. You can also use the Import Wizard to import information from an existing version XI installation to a new version XI R2. When doing so, you have the additional option of importing calendars, events, repository objects, and server groups. Events and server groups can also be imported from a version 8.5 or 9 installation. When using the Import Wizard, if any of an objects dependencies are not imported, the wizard makes appropriate modifications to the object (in most cases, the dependency is removed). For example, if a user has Full Control rights on an object, but the user is not imported, the Full Control right for that user is discarded when the object is imported. In the case of objects brought across without their owners, the Administrator becomes the new owner of the objects.
191
13
As another, more involved example, User A owns an object and has Full Control rights while User C has View rights on the same object. If User D runs the Import Wizard and brings the object across along with User C, but not User A, the object becomes owned by the Administrator: User A loses Full Control rights, but User C still has View rights on the object. Note: Always import users if you want to bring across the associated rights for an object, even if the user already exists in the destination system. If the user already exists, the Import Wizard maps all rights for the user on the source system to the existing user on the destination system. If the user is not brought across, all rights information for that user is discarded.
Importing objects from Crystal Enterprise

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

The Import Wizard imports users and groups and their hierarchical relationships. A user or group is imported only if it does not exist already by name. If you import a group that already exists in the destination environment, the list of group members is updated with any additional users who were members of the group in the source environment. These additional users are added to BusinessObjects Enterprise if their accounts do not exist already. User licensing can affect the behavior of the Import Wizard. If the source environment uses Concurrent licensing, the wizard imports all users as Concurrent Users. However, if the source environment uses Named User licensing, the wizard first checks the number of Named User license keys in the destination environment. If there are enough Named User licenses in the destination environment, the wizard imports all users as Named Users. If there are not enough Named User licenses in the destination environment, the wizard imports all users as Concurrent Users. For more information about licensing, see the BusinessObjects Enterprise Administrators Guide. Note: BusinessObjects Enterprise XI does not include a New Sign-Up feature. However, if your Crystal Enterprise source environment includes users that belong to the New Sign-Up group, the group is migrated to the destination BusinessObjects Enterprise XI environment.
192
13
Aliases
If a user in the destination system has an alias that is identical to a user who is being imported, the destination user keeps all aliases, and the imported user loses that particular alias.
Windows AD
When importing users that employ Windows Active Directory authentication, ensure that the administrative credentials are the same on both the source and destination systems. Active Directory authentication must also be enabled on the destination system.
LDAP
When importing users that employ LDAP authentication, the Host list and Base LDAP name need to be the same on both the source and destination systems. LDAP authentication must also be enabled on the destination system.
Folders
Folders are imported, whether or not they exist already in the destination environment. To ensure that existing folders are not overwritten, make sure you choose the Automatically rename top-level folders that match top-level folders on the destination system. option in the Please choose an import scenario dialog box. When this option is selected, the Import Wizard appends a number to the end of any duplicated folder names to indicate the number of copies. For example, if you import a folder called Sales Reports when a folder called Sales Reports already exists, then the imported folder is added to BusinessObjects Enterprise with the name Sales Reports(2).
Report objects
The Import Wizard can import Crystal report objects only if they are based on native drivers, ODBC data sources, OLAP data sources, Crystal Info Views, or Business Views. You can import the report instances for each report object, and the scheduling patterns that you have set up in the source environment are imported automatically. Supported reports are always imported with their parent folders, whether or not they exist already in the destination environment. However, so as not to overwrite existing folders, the Import Wizard appends a number to the end of any duplicated folder names to indicate the number of copies. When you import content from one deployment to another, you can ensure that a particular user account retains ownership of its objects and scheduled instances by importing the user along with the content. If you dont import the user account, the ownership properties of its objects and instances are reset
193
13
to your current administrative account. In the SDK, ownership is reflected by an objects SI_OWNERID property and by a scheduled instancess SI_SUBMITTERID properties.
Rights
When you import folders and reports from one BusinessObjects Enterprise system to another, the associated object rights are imported for every user or group who is imported at the same time. If the user or group is not imported at the same time, the object rights are discarded. For instance, suppose that you import a report that explicitly grants View On Demand rights to the Everyone group in the source environmentbut you do not import the Everyone group. In this case, the newly imported report in the destination environment will not grant the same explicit rights to the Everyone group. Instead, the report inherits any rights that have been set on its parent folder. If you do import the appropriate user or group, and it already exists by name in the destination environment, then the corresponding object rights are imported and applied to the existing user or group. For instance, modifying the example above, suppose that you import the report and the Everyone group. In this case, the Import Wizard imports the object rights along with the report. So the newly imported report in the destination environment will explicitly grant the View On Demand right to the Everyone group.
Events and server groups

When you use the Import Wizard to import information from a Crystal Enterprise 8.5 or later system, you have the additional option to import events and server groups from the source environment. When importing server groups, the wizard does not bring across the servers that belong to that group. You need to manually add servers to the imported group in the Central Management Console (CMC). For more information about how to do this, see the BusinessObjects Enterprise Administrators Guide. Note:
When importing report objects associated with a server group, if the server group exists on the destination system, the report objects are added to the existing group and the source systems server group is not imported. If you have jobs scheduled or pending on a server or server group that you are importing, you might notice odd behavior on the destination system with the individual jobs involved until they run or time out.
Objects that have server group restrictions lose the restrictions if the objects are imported and the server group is not. For example, if a report is scheduled to run only under server group A and that server group is not imported, the
194
Importing Objects to BusinessObjects Enterprise Importing information from BusinessObjects 5.x or 6.x
13
report loses that restriction and will run under any server group. You need to import the server group at the same time as the objects that use it to keep the relationship between them. The same logic applies for events: if an object is set up to wait for an event or to trigger an event, you need to import the event at the same time as the object. Otherwise, the object is imported without the dependency and no longer waits for, or triggers, the event. Note:
If Event A is being imported from the source system but there is already an Event A on the destination system, and it is a different type (for example, a File event instead of a Custom event), the wizard removes the dependency on Event A from the object when it is imported. Events are based on Event Servers and, since servers are not imported, you need to manually reset the event server and file name information on the event in the destination system. Once this is set, the event should work as expected.
Importing information from BusinessObjects 5.x or 6.x

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

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

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

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

Before you use the Import Wizard to import data into the new XI R2 system, you need to check that certain prerequisites are met.
Appropriate rights on page 198 Data sources on page 198 Folder mapping on page 198 UNIX servers on page 199 Locally stored objects on page 199 Updating platforms and versions if required on page 200
Appropriate rights
To use the Import Wizard, you must have the following rights:

Data sources
In BusinessObjects 5.x/6.x, you must have a General Supervisor profile in the repository. In XI R2, you must belong to the Administrator group in the CMS. To import any resource into the CMS, you must have the rights needed to add objects to the destination folder to which the resource is assigned.
Create data sources on each destination server machine for every repository domain in the source deployment. The name and configuration details for the data sources must match the data sources in the source deployment. Certain databases that can host a version 6.x repository are not supported for an XI R2 repository. For the latest information, see the list of supported platforms at: http://support.businessobjects.com/supported_platforms_xi_release2/
Folder mapping
On the Import Wizard machine, map the drives to the source environment directories containing the deployments .key files, personal documents and categories, and users Inboxes:
198
$INSTALLDIR\locData for access to 5.1.x .key files
13

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

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

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

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

All data access is kept from BusinessObjects 5.x/6.x. Connection Server is an integral part of BusinessObjects Enterprise XI R2, and all the databases it supported in BusinessObjects 5.x/6.x continue to be supported in the new environment. Check the list of supported platforms at http:// support.businessobjects.com/supported_platforms_xi_release2/, however, for the specifically supported driver versions. All connectivities supported for BusinessObjects 5.x/6.x are not necessarily supported for version XI R2. Check the list of supported platforms at http:// support.businessobjects.com/supported_platforms_xi_release2/ for detailed information. If you do not migrate data in unsupported database platforms to a supported platform, universes based on them will not work in the destination environment.
Stopping and starting servers
Stop all servers in the source deployment. Start the following servers in the XI R2 deployment:
Central Management Server Input File Repository Server and Output File Repository Server
200
13
What kinds of objects can be imported?

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

The following sections describe what happens to objects that are imported from BusinessObjects 5.x/6.x into XI R2. By default, the Import Wizard does not overwrite objects with the same name that are already stored in the XI R2 database. In general, the Wizard imports settings that are specific to each object, rather than global system settings. The Import Wizard can migrate most document types from BusinessObjects 5.x and 6.x to XI R2. This section provides information on the following document-migration related topics:
201
13
Inbox, personal and corporate documents on page 202 BusinessObjects documents on page 203 Web Intelligence documents on page 205 Third-party documents on page 206 When documents contain no locale on page 206
For details, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide.
Inbox, personal and corporate documents

You can import these types of documents:
Inbox documents on page 202 Personal documents on page 202 Corporate documents on page 203
Inbox documents
In BusinessObjects 5.x/6.x, Inbox documents are stored in the repository until recipients have read them. When a document has been read by a given user, it is copied to the users Inbox folder . See Folder mapping on page 198 for information on the location of these documents in each version. After all recipients have read them, the documents are removed from the repository. The Import Wizard will import both read and unread Inbox documents to XI R2; therefore, you will have to specify the location of the mail folder. The documents are migrated to XI R2 users Inbox folders in the CMS. Documents inherit the rights of the 5.x/6.x Inbox folder. If the Inbox contains duplicate documents, they are also migrated to the FRS. To import 5.x/6.x Inbox documents that reside on a UNIX machine, you need to map a drive from the Windows server running the Import Wizard to the directories on the UNIX machine containing the documents.
Personal documents
In BusinessObjects5.x/6.x personal documents are imported to the users Favorites folder in the destination CMS. Documents inherit the rights of this folder. See Folder mapping on page 198 for information on the location of these documents in each version. The document owner and the Business Objects Administrator have access to these documents. Personal or Corporate categories that referred to these documents in 5.x/6.x continue to refer to them in XI R2.
202
13
To import 5.x/6.x personal documents that reside on a UNIX machine, you need to map a drive from the Windows server running the Import Wizard to the directories on the UNIX machine containing the documents.
Corporate documents
In BusinessObjects 5.x/6.x corporate storage is mapped to the Public Folders folder in the XI R2 CMS repository. Corporate documents are saved in this folder after the import. Each domain is migrated as a folder in the Public folder of the CMS repository. If your 5.x/6.x repository was a distributed one, all the domains are imported into a single place.
BusinessObjects documents
When you import a 5.x/6.x BusinessObjects (.rep) document to XI R2, the following occur:
The universe ID pointer is updated so that it references a universe in the CMS. An InfoObject is created in the CMS for this document and for the saving of this document. Properties are updated and displayed in the CMC.
BusinessObjects template (.ret) documents do not contain cubes or a connection to a universe; therefore, all that occurs is: The locale of the document is updated. An InfoObject is created in the CMS.
Converting BusinessObjects documents

To convert 5.x/6.x .rep documents to .wid format, you can use the Report Conversion Tool, delivered with the XI R2 suite. Alternatively, you can use the Report Conversion Tool to convert .rep documents to .wqy (Web Intelligence 2.x) format. Then, the Import Wizard converts them from .wqy to .wid. See the Report Conversion Tool Guide for more information. Note: .wid documents for which there is no universe (so-called orphan documents) can be imported into XI R2.
203
13
BusinessObjects document rights

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

The Import Wizard can import Web Intelligence documents in .wid format only. It can, however, convert .wqy (Web Intelligence 2.x) documents to .wid format before importing them. The .wid documents can then be used in XI R2. When you import a Web Intelligence document, the following occur:
Universe ID is updated so that it references a universe in the CMS. IDs in the Web Intelligence documents, universes, and connections are converted to cluster unique identifiers (CUIDs), which will distinguish these objects from objects subsequently imported from the source environment. An InfoObject is created in the CMS for this document and for the saving of this document. Properties are updated. If a .wqy and .wid document have the same name, they are both imported, but the .wqy document is renamed to <name of document>_WQY.wid.
Web Intelligence rights

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

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

This section provides information on migrating Broadcast Agent jobs. It covers the following topics:
About migrating Broadcast Agent jobs on page 207 Task scheduling options on page 207 Associated universes on page 208
About migrating Broadcast Agent jobs

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

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

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

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

This section contains information on using the Import Wizard to import universes and universe connections. It covers the following topics:
Importing universes and connections on page 210 Options for importing universes and connections on page 210 Configuring connections on page 211
Importing universes and connections

The Import Wizard will import universes from a 5.x/6.x deployment into a XI R2 deployment. During this process, the relationship between universes, connections, and Web Intelligence documents is maintained. The IDs in the web intelligence documents, universes, and connections will be converted to cluster unique identifier (CUIDS) and the relationship preserved. When you import BusinessObjects Enterprise 5.x/6.x universes, the associated connections are imported automatically. They are converted into connection objects.
The Import Wizard imports any associated connection objects. The connection is saved in the FRS and an InfoObject is created in the CMS. The universe and its linked documents are copied into the FRS. Universe overloads defined in 5.x/6.x, if migrated, are mapped to access restrictions in XI R2. ACEs are created to migrate universe-related security commands. The locale is preserved.This is the process when a universe is imported.
Options for importing universes and connections

The Import Wizard has three modes for importing universes:

210
Import all universes and all connection objects Note: This option does not permit you to select individual universes or connections. Import all universes and only connection objects used by these universes
13
Import the universes and connections that the selected Web Intelligence and BusinessObjects documents use directly Note: This option enables you to select additional universes to import, even if they are not used by any document.
When you select a Web Intelligence or BusinessObjects document to import, the Import Wizard automatically selects the associated universes for import. It does not do this, however, for universes used by scheduled documents (Broadcast Agent jobs). This means that if you are not importing all your universes, you must manually select the ones you need for Broadcast Agent jobs. Note: The Import Wizard also imports any universes with the same name that exist in other domains. BusinessObjects documents may have been created outside the repository, using a short name; that is, a reference to a universe stored on a local machine. If the universe has a short name, its linked documents may not be imported if more than one universe is found in the CMS with the same short name. Universe domains are converted into subfolders under the Universe folder. Each universe folder is named after the corresponding BusinessObjects 5.x/ 6.x universe domain. When you import a universe from a domain, it is placed in the corresponding domain folder. If the universe is a derived universe, then all relevant core universes and their connections are also imported. Note: Designer 5.x/6.x cannot open universes created with Designer XI R2, due to a file format change.
Configuring connections
When you import BusinessObjects 5.x/6.x universes, the associated connections are imported automatically. They are converted into connection objects. Make sure that the Import Wizard can access the 5.x/6.x database the same way that BusinessObjects 5.x/6.x accesses it. You may need to install database drivers or configure connection settings on the machine. For example, if you import SQL Server connection objects from a 5.x/6.x source environment, you must configure the connections on the destination machine via the Control Panel before you import the connection objects. You must use the same name and settings as the connection used on the source machine when you created the domain key.
211
13
BOUSER/BOPASS
In BusinessObjects 5.x/6.x, users could use @Variable('BOUSER') and @Variable('BOPASS') in the connection information for the universe. The variables were replaced at runtime with the users enterprise username and password, and used to log on to the database. For security reasons, XI R2 does not permit the retrieval of users passwords. Therefore, universe connections that previously used the BOUSER and BOPASS variables associated with the BusinessObjects user name and password must now use database credentials (DBUSER and DBPASS). Those database credentials can be populated by the Import Wizard and later edited in the CMC, on the Properties tab for each user account. When migrating, Import Wizard automatically does the following:
Replaces BOUSER and BOPASS with DBUSER and DBPASS in universes. Proposes automatically populating these variables for users to migrate.
You can, however, re-synchronize if users change their passwords.
Synchronizing enterprise and database credentials

There are three ways to synchronize enterprise and database credentials in the XI R2 system:
Choose the Import Wizard option that batch imports user names and passwords from BusinessObjects 5.x/6.x to auto-populate database credentials in XI R2. Run a batch upload of a users file. User names and passwords are loaded from a file, stored and used as database credentials. Create a custom application using Enterprise SDK to set DBUSER and DBPASS information.
Importing access restrictions

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

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

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

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

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

All existing BusinessObjects 5.x/6.x users and groups can be migrated to BusinessObjects Enterprise XI. Users are imported into the BusinessObjects Enterprise repository. For each BusinessObjects 5.x/6.x user, BusinessObjects Enterprise XI creates a user folder, a personal category, and an Inbox folder. User profiles from BusinessObjects 6.x are mapped to default groups in BusinessObjects Enterprise XI as follows: BusinessObjects 5.x/6.x user profile BusinessObjects Enterprise XI default group Added to the Everyone group. Added to the Administrators group. Granted appropriate rights on all imported objects, but not added to the Administrators group. Added to the Everyone group.
All user profiles General Supervisor Supervisor
User/Versatile
214
Importing Objects to BusinessObjects Enterprise Using the Import Wizard
13
Whenever possible, BusinessObjects 6.x security settings are preserved in BusinessObjects Enterprise XI. If a BusinessObjects 6.x right does not map exactly to a BusinessObjects Enterprise XI right, the right will not be granted to the user. Note:
The Import Wizard migrates external user groups (LDAP or Windows AD user groups, for example).
Using the Import Wizard

The Import Wizard provides a series of screens that guide you through the process of importing user accounts, groups, folders, and reports. The screens that appear depend on the source environment and the types of information that you choose to import. When you import information, you first connect to the Central Management Server (CMS) of your existing installation (the source environment) and specify the CMS of your new BusinessObjects Enterprise system (the destination environment). You then select the information that you want to import, and the Import Wizard copies the requested information from the source to the destination. You can choose to merge the contents of the source repository into the destination repository, or you can update the destination with the contents of the source CMS. Before starting this procedure, ensure that you have the Administrator account credentials for both the source and the destination environment. The overall process is divided into the following procedures:
Specifying the source environment on page 216 Specifying the destination environment on page 223 Selecting the type of objects to import on page 225 Selecting specific objects to import on page 232 Finalizing the import on page 241 If you are migrating from BusinessObjects 5.x or 6.x, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide for detailed Import Wizard instructions.
Note:
215
13
The process of importing users, groups and profiles from a text files is a less complex task. Both the format for the text file and the procedure are outlined in Using text files with the Import Wizard on page 242.
Specifying the source environment

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

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

1. To specify a BusinessObjects 6.x source environment Start the Import Wizard. From the Start menu, select Programs > BusinessObjects > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. 4. Click Next. The Source Environment dialog box appears. Choose BusinessObjects 6.x from the Source list. Type the User Name and Password that provides you with administrative rights to the source environment. Note: You must have a General Supervisor profile in the repository. 5. 6. If you want to import Application Foundation objects proceed to Specifying the Application Foundation source information on page 218. If you do not want to import Application Foundation objects, make sure the Import Application Foundation Contents check box is not selected, and then click Next. The Destination Environment dialog box appears. Proceed to Specifying the destination environment on page 223.
7.
217
13
Specifying the Application Foundation source information

This procedure assumes you have completed the step Specifying a BusinessObjects 6.x source environment on page 217. 1. To specifying the Application Foundation source information Select the Import Application Foundation contents check box on the Source Environment dialog box, and then click Next.
Note: You can import Application Foundation objects only if you selected BusinessObjects 6.x (or XI) in the Source list. If you import Application Foundation objects, the Import Wizard displays additional screens and options. The Import Wizard verifies the following:

2.
The connection to the repository. The credential. The validity of the General Supervisor login. The repository version.
In the Dashboard files section of the Application Foundation source screen, browse to the location of the Application Foundation storage folder. By default, it is $INSTALLDIR/Application Foundation/server/conf. In the Application Foundation source repository section, indicate the repositorys details using one of the following methods:
3.
218
13
Check the Use conf file option. This option allows you to specify the location of the AF config file that contains the repository database information rather than entering it manually. Note: If you check this option, the option to upgrade the AF repository in this Import Wizard session will be grayed out. You can only use this option to point to the source repository connection if you are not planning to upgrade the repository using this connection. It is highly recommended that you upgrade a copy of the source repository, and that you point to the connection to the copy when you upgrade the repository.
Manually enter the following information:
The name of the source repository. The database engine. The network layer of the source repository. The user name and password to access the database.
Note: The user name and password you type must belong to an Administrator profile. It is highly recommended that you upgrade a copy of the source repository, and that you point to the connection to the copy when you upgrade the repository. 4. 5. Click Next. The Application Foundation Repository Update dialog box appears. Select one of the following options:
Yes to update the repository in the Import Wizard No to skip the repository update and migrate the repository later Note: If you want to perform the migration in several steps, the Application Foundation repository must be updated at the end of the migration process. You can only update the repository once. If you are migrating rules and schedules, you must migrate them in the same Import Wizard session as the repository update. If you choose not to upgrade the repository, you cannot import rules and schedules. In addition, if you choose not to upgrade the repository, your repository connections will not be active on the migrated environment.
219
13
6.
Click Next.
If you chose not to upgrade the repository, a dialog box listing the objects you can import appears. Click Next to continue. If you chose to upgrade the repository, a warning screen appears. You must acknowledge that you have read the warning by checking the I understand. I want to continue. box to proceed with the repository upgrade.
The Destination Environment dialog box appears. Proceed to Specifying the destination environment on page 223.
Specifying a Crystal Enterprise 8.5 source environment

1. To specify a Crystal Enterprise 8.5 source environment Start the Import Wizard. From the Start menu, select Programs > BusinessObjects > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. 4. 5. 6. Click Next. The Source Environment dialog box appears. Choose Crystal Enterprise 8.5 from the Source list. Enter either the name of the source CMS in the CMS Name field or the name of the source APS in the APS Name field. Type the User Name and Password that provide you with administrative rights to the source environment. Click Next. The Destination Environment dialog box appears. Proceed to Specifying the destination environment on page 223.
Specifying a Crystal Enterprise 9 source environment

1. To specify a Crystal Enterprise 9 source environment Start the Import Wizard. From the Start menu, select Programs > BusinessObjects > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. 4. Click Next. The Source environment dialog box appears. Choose Crystal Enterprise 9 from the Source list. Enter either the name of the source CMS in the CMS Name field or the name of the source APS in the APS Name field.
220
13
5. 6.
Type the User Name and Password that provide you with administrative rights to the source environment. Click Next. The Destination environment dialog box appears. Proceed to Specifying the destination environment on page 223.
Specifying a Crystal Enterprise 10 source environment

1. To specify a Crystal Enterprise 10 source environment Start the Import Wizard. From the Start menu, select Programs > BusinessObjects > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. 4. 5. 6. Click Next. The Source environment dialog box appears. Choose Crystal Enterprise 10 from the Source list. Enter either the name of the source CMS in the CMS Name field or the name of the source APS in the APS Name field. Type the User Name and Password that provide you with administrative rights to the source environment. Click Next. The Destination Environment dialog box appears. Proceed to Specifying the destination environment on page 223.
Specifying a BusinessObjects Enterprise XI or XI R2 source environment

1. To set the source environment Start the Import Wizard. From the Start menu, select Programs > BusinessObjects > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. 4. Click Next. The Source environment dialog box appears. Choose BusinessObjects Enterprise XI or BusinessObjects Enterprise XI R2 from the Source list. Enter either the name of the source CMS in the CMS Name field or the name of the source APS in the APS Name field.
221
13
5. 6.
Type the User Name and Password that provide you with administrative rights to the source environment. Click Next. The Destination Environment dialog box appears. Proceed to Specifying the destination environment on page 223.
Specifying a BIAR file or Text file as your source environment

This section explains how to import from a Text or BIAR file. For details, on how to structure your text files so the Import Wizard can import them, see Using text files with the Import Wizard on page 242. 1. To specifying a BIAR file or Text file as your source Start the Import Wizard. From the Start menu, select Programs > BusinessObjects > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. Click Next. The Source environment dialog box appears. Choose either Business Intelligence Archive Resource (BIAR) File or Text file from the Source list.
222
13
4.
Enter the location of the file in the BIAR file or Import file field, and then click Next.
The Destination Environment dialog box appears. Proceed to Specifying the destination environment on page 223.
Specifying the destination environment

This procedure shows how to specify a destination environment. 1. To set the destination environment Choose the destination environment in which to export.
If you want to export to a CMS a. Type the name of the destination environments Central Management Server in the CMS Name field.
b. Type the User Name and Password of an Enterprise account that provides you with administrative rights to the BusinessObjects Enterprise system. c. Click Next.
223
13
If you want to export to a BIAR file, specify the name and location where you want the BIAR file to be stored. Note: This option only applies if your source environment is XI R2.
2.
Click Next. The Select Objects to import dialog box appears.
224
13
Selecting the type of objects to import

In this stage of the import process, you select the types of objects you want to import and select options related to their import. At a later stage, you will select the objects themselves. You may select BusinessObjects Enterprise XI InfoObjects, including the following performance management InfoObjects:
universes and documents referenced by analytics you are importing analytics (*.afd) rules and schedules (rules remain in the performance management repository. Only schedules and named events that trigger rules are imported here) named events dashboards (corporate and personal)
The options available on the Choose object to import dialog box depend on the version of the source environment. By default, all available objects are checked for import.Events and server groups can be imported from Crystal Enterprise 8.5 or later. Repository objects and calendars can be imported from Crystal Enterprise 10. Universes, categories, Desktop Intelligence and Web Intelligence documents can be imported from BusinessObjects 6.x. All objects except Desktop Intelligence documents can be imported from BusinessObjects Enterprise XI and XI R2. If you have not already started the Import Wizard, see Specifying the source environment on page 216 and Specifying the destination environment on page 223. 1. To select the types of objects to import Choose the types of object to import. Note: The options that appear depend on the source environment and its version, and on whether you selected the Import Application Foundation contents check box. By default, all object types are selected, so you must do one of the following:
Clear the check boxes for the items you dont want to import, and then click Next.
225
13
2.
Accept the defaults, which is to import all documents, and then click Next.
In the Import Scenario dialog box, select the type of import you want.
To merge the source and destination environments, select I want to merge the source system into the destination system.
226
13
If you want to automatically rename top-level folders that match top-level folders on the destination system, select the check box beneath the merge option. To update the destination environment without merging, select I want to update the destination system by using the source system as a reference. If you want to automatically rename objects when an object with the same title already exists in the destination folder, select the check box beneath the update option. For more details on the different scenarios, see Choosing an import scenario on page 230.
3.
If you see the Incremental Import dialog box, select the type of objects whose content you want to overwrite.
These are your choices:
Documents (including dashboards and analytics) Universes Connections
Note: The Incremental Import dialog box appears if you selected the Update option a previous step. 4. If you want to overwrite object rights, select the Overwrite object rights check box, and then click Next; If you dont want to overwrite objects rights, click Next.
227
13
5.
If you are prompted to select specific objects for import, see Selecting specific objects to import on page 232 for details on your specific object type. Note: The specific dialog box that appears will vary based on what you are importing. However, the reason you will see one is because you selected the Merge option a previous step.
6.
If you opted to import users or groups, select one of the security migration options, and then click Next.
These are three security migration options:
Yes, migrate security on imported objects and secure the destination system. This is the most secure option. Yes, migrate security on imported objects Users in the destination system may end up with more rights than in the source system. No, dont migrate security Note:
The Security Migration Options dialog box appear if you selected Import users and user groups.
228
13
Universe overloads are not included in the Security migration. You select overload migration on the Import Options for Universes and Connections dialog box . For more information, see Universe and connection objects on page 240.
For a full discussion of these options, see the BusinessObjects 5.x to XI Release 2 Migration Guide. 7. If you selected the import of objects stored either in inbox or personal folders, type or browse for the path of your Personal and/or Inbox documents in the source environment, and then click Next. Note:

8.
If the files are located on a remote server, you must have mapped the remote server to your local machine. If the files are located on a UNIX server, you must have mapped the UNIX server to a local drive. You do not need to provide a path for corporate documents because they are stored in the repository.
.
If you chose to import universes in the Select Objects to Import dialog box, select one of these import options:
Import all universes and all connection objects This imports all universes from the source environment in one batch. You cannot select individual universes or connections. Import all universes, and only connection objects used by those universes Import universes and connections that the selected Web Intelligence and BusinessObjects documents use directly In a later dialog box, you will be able to select additional universes to import.
229
13
9.
If you want to migrate universe overloads, select the Keep universe overloads for imported users and groups check box.
If you do not select this, then no universe overloads will be migrated. 10. Click Next. 11. If the Ready to Import dialog box appears, go to Finalizing the import on page 241. Proceed to Selecting specific objects to import on page 232. For more information about merging and updating systems, see Crystal Repository chapter in the BusinessObjects Enterprise Administration guide.
Choosing an import scenario

When you choose an import scenario, you can merge the source and destination environments, or you can update the destination environment without merging.
When you merge the environments, the Import Wizard adds all objects from the source to the destination CMS without overwriting objects in the destination environment. This is the safest import option. All of the objects in the destination environment are preserved.
230
13
When you update the destination environment, all objects in the source are added to the destination CMS, but if a source object has the same unique identifier as an object in the destination environment, the destination object is overwritten. Note: When CUIDs are changed, links between documents, rules, and other objects that refer to each other using CUIDs may be impacted. If you import objects with links to other objects, the safest option for migration is the second option (Updating the destination environment).
This procedure assumes you have already specified the source and destination environment and selected the type of objects to import. If you have not already started the Import Wizard, see Specifying the source environment on page 216, Specifying the destination environment on page 223 and Selecting the type of objects to import on page 225.
Updating previously imported objects

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

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

If you chose to import users and groups, the Users and Groups dialog box appears. It may take some time before the users and groups are displayed, because the Import Wizard is retrieving them from the repository. Note: For detailed information on the import of users and groups, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide.
232
13
1.
To select users and groups In the Groups list, select the groups that you want to import.
2. 3.
In the Users list, select specific members of any group. Click Next. Note: Only the General Supervisor type is added to the Administrators Users group:
4.
If the Import Groups Option dialog box appears, select if you want group mappings from LDAP and Active Directory to be migrated to XI R2. Note:
5.
If the Import Groups Option dialog box appears, the 6.x source and the XI R2 destination environments are configured for LDAP or Active Directory. You need to have the same LDAP or Active Directory configuration on the source and destination. For information about setting alias creation and assignment for LDAP and Active Directory users, see the BusinessObjects Enterprise Administrators Guide.
Choose the third-party group mapping you want to migrate and then click Next.
233
13
Populating database credentials

After users and groups are imported, the Populate Database Credentials dialog box appears. This dialog box enables you to automatically set the DBUSER and DBPASS attributes, for all imported users, with their login and password. These can be used as default database credentials for connections. 1. Decide if you want the Import wizard to import database credentials for users.

2.
If you want to populate the database credentials of imported users with their BusinessObjects user name and password, select Yes. If you do not want to do this, select No.
Click Next.
Broadcast Agent
If you are importing Broadcast Agents, the Broadcast Agent dialog box appears.This dialog box enables you to select the Broadcast Agents you want to import. Note: A Broadcast Agent job can be migrated from BusinessObjects 6.x to XI R2 only if the job is supported in XI R2. (For details, see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide.) 1. To select Broadcast Agents for import In the Broadcast Agent dialog box, select the Broadcast Agents whose jobs you want to import. Note that all the jobs, for each Broadcast Agent, are selected by default. 2. Click Next.
Dashboards
If you are importing dashboards, the Dashboards dialog box appears. 1. To select dashboards Select the dashboards you want to import. When you select an application, its submenus are also selected.
234
13
2.
Click Next. The Import Wizard checks whether any dashboards in the source repository include security. If the Import Wizard detects security on any dashboards, the Import Dashboard Option dialog box appears. If none of the dashboards selected for import includes security, skip to step 4.
3.
If dashboards selected for import include security, select one of the following options:
Import and apply page security on all page elements The Import Wizard migrates the dashboard and any sub-menus and applies standard page-level security, which is translated as an ACL in the CMS. With this option, the least restrictive set of rights is applied.
Dont import such dashboards The Import Wizard imports all dashboards, including dashboards with analytic-level security restrictions, but empties all content from pages containing secured elements. Dashboard menu structures are preserved.
Import but move to administrators Favorites folder for revision The Import Wizard imports all dashboards, including secured dashboards, but empties the content of all secured dashboards. When you choose this option, dashboard menu structures are preserved and a copy of each secured dashboard, including its contents, is moved to the administrators favorite folder. A prefix is added to the secured dashboards name so that the administrator can easily identify it after migration, then modify it manually before publishing it to a wider audience.
235
13
Categories
If you are importing categories, the Categories dialog box appears. 1. To select categories Select the check boxes for the categories that you want to import.
For large document domains, you can import incrementally, and import documents one category at a time. 2. 3. If you want to import all the objects associated with the category, select the Import all objects that belong to the selected categories check box. Click Next.
Document domains and documents

The Domains and Documents dialog box appears if you choose to import any of the following document types:
Web Intelligence Desktop Intelligence (BusinessObjects) performance management (Application Foundation) Analytics (Performance Management) (6.x only) Third-party
The list contains a separate branch for each domain. Domains that cannot be opened are greyed out. If you previously chose to import all the documents of a given category, they are preselected and cannot be cleared.
236
13
1.
To select domains and documents Select the check boxes for domains or individual documents that you want to import.
2.
Click Next. The Locales and Platform Options dialog box appears.
In a BusinessObjects 5.x/6.x repository, some Web Intelligence 2.x (.wqy) documents and BusinessObjects documents may not store their locales. In order to set locales in these documents when they are saved in the CMS (after conversion to .wid), the default locales provided by the user are added to the documents.
237
13
3. 4. 5.
Select the locale of the source from the top list. Select the local of the destination from the bottom list. Click Next.
Universes
1. To select universes or universe folders Select the check boxes for the universes that you want to import. The universes that are linked to specific documents cannot be cleared from the list.You can select additional universes that are not used by any imported document. 2. Click Next. If no universe is found, the associated documents will not be imported and a warning message appears. If this occurs, link the documents to a universe, republish them to the repository, and retry the import.
Note: When you import a universe, its connection objects are imported automatically. Before you can import connection objects from BusinessObjects 5.x/6.x, ensure that the Import Wizard can access the database the same way that the source environment accesses it. This may involve installing database drivers or configuring connection settings on the machine. For example, if you import SQL Server connection
238
13
objects from a BusinessObjects 6.x source environment, you must configure the connections on the destination machine via the Control Panel before you import the connection objects. You must use the exact same name and settings as the connection used on the source machine when you created the domain key. To select folders and objects
If you chose to import folders and objects, the Select Folders and Objects dialog box appears. Select the check boxes for the folders and reports that you want to import. Then click Next. Tip: You can also choose to Import all instances of each selected report and object package. This example imports the Report Samples folder and a subset of its contents.
To select repository objects
If you chose to import repository objects, the Import repository objects options dialog box appears. Choose an importing option for repository objects, then click Next.
239
13
Universe and connection objects

If you chose to import universes in the Select Objects to Import dialog box, the Import Options for Universes and Connections dialog box appears. 1. To import universe and connection objects Select an import option:
Import all universes and all connection objects This imports all universes from the source environment in one batch. You cannot select individual universes or connections. Import all universes, and only connection objects used by those universes Import universes and connections that the selected Web Intelligence and BusinessObjects documents use directly In a later dialog box, you will be able to select additional universes to import.
2.
If you want to migrate universe overloads, select the Keep universe overloads for imported users and groups check box. If you do not select this, then no universe overloads will be migrated. Click Next. If you chose to import a subset of the universes from the source environment, the Select Universe Folder and Universes dialog box appears.
3.
240
13
Finalizing the import

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

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

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

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

e
Field Number Field 1 Field 2 Field 3 Field 4 Field 5 Field 6
Contents of field Group name User Name Full name of user Email address of user Profile name for user. Profile value for user.
Note: Profile values must be enclosed in quotes. See Text file format on page 242 for information on using delimiter.
Example user record

Sales,Psanders,Paula Sanderson,psanders@Acme.com, Manager,West Region
The previous record would create an account name or username of psanders in BusinessObjects Enterprise. The name Paula Sanderson, and the e-mail address of psanders@Acme.com would be associated with this account name. The username psanders would be member of the group Sales. The username psanders and would be assigned the profile Manager with the profile value of West Region.
Group Record Format

Field Number Field 1 Field 2 Field 3 Field 4 Contents of field Group name Null Description of group. Field is ignored.
243
13
Field Number Field 5 Field 6
Contents of field Profile name for group. Profile value for group.
Note: Profile values must be enclosed in quotes. See Text file format on page 242 for information on using delimiter.
Example Group record

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

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

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

This section explains how to import any of the following from text file:
Users
244
13
Groups Profiles Data source credentials
For details about the format of these files, see Text file format on page 242. 1. To import from text files Start the Import Wizard. From the Start menu, select Programs > BusinessObjects XI R2 > BusinessObjects Enterprise > Import Wizard. The Import Wizard dialog box appears. 2. 3. 4. 5. 6. Click Next. The Source Environment dialog box appears. Select Text file from the Source list. Click the browse icon. Locate the file to import, and then click Next. Enter the name and credentials for the CMS, and then click Next. The Select options for file import appears.
7.
Decide what you want to import.
To import profiles, users and groups
245
13
a.
Make sure the select type of file to import list is set to Profiles, Users and Groups.
b. If you want your text file to only create profiles, users or groups, but not update the data already entered, clear the update options. c. If you want your text file to only update profiles, users or groups, but not create new profiles, users or groups, clear the create options.
d. To remove all existing users from a group specified in the import file, whose membership in the group is not specified in the file, select Remove users from a group if not included and clear Add users to a group if not a member. e. To add existing users or users in the import file to a group if they are not a member, make sure Add users to a group if not a member is selected. Click Next. Select Data Source Credentials from the list. Click Finish.
f.
To import data source credentials a. c. b. Click Next. The file will be imported. Note: If you are importing data source credentials, none of the remaining steps in this procedure apply.
The select application folders and objects dialog box appears. 8. Click Next.
246
13
9.
The Preview results from file import dialog box appear.
10. Review that the results are what you expect, and then click Next. The results on this screen show the how the first user or group will be created, after all the records in the import file have been parsed. If your record includes both a user and a group, the user preview will be displayed by default. To see how the what group may be created, click Group. 11. Click Finish to begin the import. 12. Click Import to exit the Import Wizard.
247
13
248
Custom SDK Deployments
chapter
14
Custom SDK Deployments Software Development Kit overview
Software Development Kit overview

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

BusinessObjects Enterprise supports web applications that are implemented using Active Server Pages (ASP). Both CSP and ASP drive the COM SDKs.BusinessObjects Enterprise installs the necessary files so that Internet Information Server (IIS) can process the ASP files.
Java Server Pages environment

BusinessObjects Enterprise supports web applications that are implemented using Java Server Pages (JSP). On Windows, you can install the BusinessObjects Enterprise Java SDK and deploy the JSP version of InfoView, or you can install the .NET version of InfoView in a .NET environment. Before you run any of your applications that are implemented using JSP, ensure that you have deployed them to the appropriate folder for the web application server you are using. For more information on deploying WAR and JAR files see the documentation that is specific to your web application server in the following sections:
Deploying on Tomcat on page 127 Deploying on WebLogic on page 153 Deploying on WebSphere on page 137 Deploying on Oracle Application Server on page 167 Deploying on SAP Web Application Server on page 179
.NET environment
To use .NET assemblies, you must set up your development machine and web server to be able to run a reporting application using .NET. To create .NET applications to view or modify Enterprise reports, or to use the Crystal Reports .NET report viewers to view a SOAP report web service, you need to install Visual Studio .NET, Crystal Reports, BusinessObjects Enterprise, and Report Application Server. Crystal Reports enhances VS .NET by adding Crystal Reports features to the Visual Studio .NET IDE. Therefore, you must install your .NET products before you install Crystal Reports, or you must run the Crystal Reports installation program again after you install a .NET product. In general, follow this installation order for setting up your development machine:
14
Custom SDK Deployments .NET environment
Ensure Internet Information Server (IIS) 5 or higher is installed if you intend to host web applications on your development machine. Install Visual Studio .NET or the .NET Framework. Note: If the setup program does not detect Visual Studio .NET or the .NET Framework on the machine, it installs the .NET Framework. Install any optional .NET tools such as Visual J# or the .NET mobile controls. Install Crystal Reports. Install BusinessObjects Enterprise. Note: The BusinessObjects Enterprise .NET assemblies and the .NET Server Components will be installed on your machine if:
You perform a default installation of BusinessObjects Enterprise and select the IIS.NET Web Component Adapter. You perform a Custom installation and select "BusinessObjects Enterprise .NET SDK" from the Developer Components listed in the Select Features dialog box.
If you install BusinessObjects Enterprise before installing a .NET product, the setup program installs .NET framework v1.1 by default. For a web server to run a reporting application using BusinessObjects Enterprise for .NET, the web server must be running the .NET Framework and provide access to the BusinessObjects Enterprise .NET libraries.
Upgrading and Migrating
chapter
15
Upgrading and Migrating What does this section cover?
What does this section cover?

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

This guide does not cover how to migrate from the following versions.
BusinessObjects version 5.x BusinessObjects version 6.x

WebIntelligence 2.x through 6.5.x
For further information on these topics, see the following documents: BusinessObjects 5.x to XI Release 2 Migration Guide BusinessObjects 6.x to XI Release 2 Migration Guide.
Upgrading from Crystal Enterprise or from BusinessObjects Enterprise

The term upgrading in this section refers to both upgrade scenarios:
When you upgrade directly from a previous version. When you uninstall the previous version first and then install the new version.
See Upgrade installation on page 28 for more information. The process of moving from an earlier release of Crystal Enterprise or BusinessObjects Enterprise involves several steps which can be divided into three categories: upgrading, migrating, and importing.
Upgrading consists of replacing existing components and files with the latest BusinessObjects Enterprise versions. Note: Migrating consists of copying data from your old CMS database to a BusinessObjects Enterprise XI Release 2 CMS.
254
Upgrading and Migrating Upgrading from Crystal Enterprise or from BusinessObjects Enterprise
15
This includes moving a Crystal Management Server database, or a BusinessObjects Enterprise XI Release 1 Central Management Server to a new BusinessObjects Enterprise XI Release 2 CMS database, while at the same time updating the database schema to the latest version.
Importing consists of copying objects (reports, users, groups, and so on) and instances from one system to another.
The focus of this section is upgrading and migrating. For information on importing, see Importing Objects to BusinessObjects Enterprise on page 189. Note:
If youre upgrading from Crystal Enterprise 9, you will also need to migrate your Crystal Enterprise Repository and/or your Crystal Reports repository. If your migrating performance management InfoObjects from BusinessObjects Enterprise XI, you will also need to migrate the performance management repository. Repository objects used by Business Views are always imported in Update mode, even when the Merge option is selected.
If you are upgrading or migrating from Crystal Enterprise 9 or 10 or BusinessObjects Enterprise XI, read the following topics:
Preparing for upgrading or migrating on page 256 Migration options on page 257 Disabling and stopping servers on page 257 Upgrading other components on page 269 Migrating the CMS or APS data on page 259 This is done from the Central Configuration Manager Copying data from a Crystal Enterprise 9 repository database on page 261 and Copying data from a Crystal Reports 9 repository database on page 265 This is done from the Repository Migration Wizard. Note: This step only applies if your migrating from Crystal Enterprise 9.
Upgrading other components on page 269 Completing a CMS database migration on page 270
If you are upgrading from BusinessObjects Enterprise 5.x/6.x see the BusinessObjects 5.x to XI Release 2 Migration Guide or the BusinessObjects 6.x to XI Release 2 Migration Guide.
255
15
Upgrading and Migrating Preparing for upgrading or migrating
Preparing for upgrading or migrating

It is expected that you will follow your usual administrative practices before upgrading to BusinessObjects Enterprise or migrating system data from earlier product releases. However, you should also consider the following common tasks and guidelines:
Consult the Release Notes included with your product distribution for further information that may pertain to your reporting environment (release.pdf). Disable and subsequently stop all BusinessObjects Enterprise or Crystal Enterprise components before upgrading. Stop the web servers and/or web application servers that are configured for use with BusinessObjects Enterprise or Crystal Enterprise. Ensure that you have details about the database server and accounts that are used for the existing system database and that will be used by the new system database. For more information, see Setting up the CMS database on page 39. Back up your existing repository or repositories, including the system database. For Crystal Enterprise, also back up the root directories used by the Input and Output File Repository Servers. Back up any custom web applications, HTML pages, or scripts that you have added to your existing deployment. Make sure you log onto the machine as an administrator first When you install or upgrade BusinessObjects Enterprise components. Close any other programs that are running locally before you start the BusinessObjects Enterprise setup program. If you are upgrading from Crystal Enterprise, you must migrate your existing Crystal Management Server or Automated Process Scheduler (APS) to the latest format. Ensure that you first install the new components on a machine with one of these components, so you can immediately create a new CMS database and then migrate system data from the old database. (If youre upgrading from BusinessObjects Enterprise 5.x or 6.x, the migration to BusinessObjects Enterprise 6.5 occurs automatically.)
Note: Silent installations are not recommended for upgrading. Although you can use a silent installation to add components to a machine, using it to replace existing components is not recommended. Alternatively, you can uninstall the existing components and then install the new ones using the silent installation
256
15
Migration options
Several options are available to you, depending upon your current system and your preferred method of upgrading:
Upgrade an earlier version of Crystal Enterprise directly and migrate its system data into a new CMS database. In this scenario, you first upgrade the existing Crystal Management Server or APS and migrate its system database; then you upgrade all other BusinessObjects Enterprise components before bringing the system back online.
Set up a new BusinessObjects Enterprise system alongside your original system, and then migrate old system data into the new CMS database. In this scenario, you need additional hardware for the new BusinessObjects Enterprise system. When the new system is ready, you migrate your original Crystal Management Server, APS database, or BusinessObjects Enterprise XI Relasee 1 CMS so it becomes the CMS database for the new system, and you ensure that the new Input and Output File Repository Servers can access the root directories that were used by the older system. For details, see Configuring your CSP applications for the Web Component Adapter on page 268.
Set up a new BusinessObjects Enterprise system, and then import content from an existing Crystal Enterprise or Crystal Info system. Again, this scenario requires additional hardware for the new BusinessObjects Enterprise system. Instead of migrating an existing database, you selectively import content (user accounts, groups, folders, reports, and so on) into the new system. For details, see Importing content from BusinessObjects Enterprise, Crystal Enterprise, or Crystal Info on page 269.
Note: Before proceeding with any upgrade or migration, see Preparing for upgrading or migrating on page 256. If you require further assistance in upgrading particularly large-scale and/or mission-critical deployments, or in migrating customized reporting applications, it is recommended that you contact a Business Objects Services consultant, who can then assess your reporting environment and assist in the upgrade and migration process.
Disabling and stopping servers

Before you begin your upgrade you must stop and disable any servers from previous versions.
257
15
To disable and stop all Crystal Enterprise and BusinessObjects Enterprise XI servers on Windows 1. Open the Central Configuration Manager (CCM). 2. 3. 4. 5. Click on the Enable/Disable Servers icon on the toolbar. Enter the User Name and Password for the CMS, and then click Connect. Click Disable All and the click OK. Select all the servers in the CCM, right click and select Stop.
Upgrading previous versions components

There are two ways to upgrade components from Crystal Enterprise 9 or 10, or BusinessObjects Enterprise XI to BusinessObjects Enterprise XI: one way is to use the setup program, the other is to uninstall the old version and then install the new. If you have a full standalone server or client install, you can use either method. If you dont have a full standalone server or client install, you must uninstall your earlier components and then proceed with the install method of your choice. Note: A full standalone server install means during the initial install, you installed the complete feature set onto one machine. This includes all the client components, the server components, the SDKs and either the Java or the .NET Web Component Adapter or Web Component Server. A full standalone client install means you installed all of the client components onto one machine. For further information on your install choices, see Choosing an install type on page 25. For information on how to install, see Uninstalling on page 277. For further information on how to install, see Installing BusinessObjects Enterprise on Windows on page 35. If you have a full standalone installation the setup program detects this and leads you through the upgrade process and the creation of a new CMS database. If you have more than one machine, run the installation program first on one of the machine with the CMS or APS. This will allow you to immediately create a new CMS database and then migrate system data from the old Crystal Management Server or APS database. After you migrate the CMS data and copy the data from a Crystal Enterprise 9 or Crystal Report 9 repository, you will need to upgrade any remaining components on other machines. See Upgrading other components for more information.
258
15
Note: If either the full client or server set is not detected, you will receive a message informing you that you must uninstall the previous version before you proceed with your install.
Migrating the CMS or APS data

If you install a new BusinessObjects Enterprise system alongside your original installation, you can use the latest version of the Central Configuration Manager to migrate system data from the old Crystal Management Server, APS database or CMS database into the new BusinessObjects Enterprise XI Release 2 CMS database. In addition, you will need to provide the newly installed File Repository Servers with access to the root directories used by the File Repository Servers in the old Crystal Enterprise system. To copy data from a CMS on Windows 1. 2. Make sure the Central Management Server is stopped. Select the Central Management Server from the CCM, click the Specify CMS Data Source icon the toolbar. The CMS Database Setup dialog box will appear.
3.
Click Copy data from another Data Source, and then click OK.
259
15
The Specify Data Source dialog box appears.
4.
In the Source contains data from version list, click Autodetect (or explicitly select the version of the source CMS database). You must now specify the source CMS database whose contents you want to copy.
5.
Click Specify and then select the database you are going to migrate from, and enter its credentials.
If you are migrating from SQL a. c. Click SQL Server, and then click OK. Select the Data Source Name, and then click OK. b. Click on the Machine Data Source tab. d. Enter the Login Id and Password for the database, and then click OK
If you are migrating from Oracle a. c. Click Oracle native driver, and then click OK. Enter the Login id and the Password for the database, and then click OK. Click DB2 native driver, and then click OK. Enter the Login id and the Password for the database, and then click OK. Click Sybase native driver, and then click OK. b. Enter the database name in the server name field.
If you are migrating from DB2 a. c. b. Enter the database name in the server name field.
If you are migrating from Sybase a.
260
15
b. Enter the database name in the server name field. c. 6. 7. Enter the Login id and the Password for the database, and then click OK.
Click Browse and then select the database you are going to migrate to, and enter its credentials. Click OK on the Specify Data Source dialog box. You will receive a warning message indicating all tables in database you are migrating to will be deleted. Click OK and, when prompted to confirm, click Yes. You will see a status bar that indicates the progress of the migration. The SvcMgr dialog box notifies you when the CMS database setup is complete.
8.
9.
Click OK. Note: At the end of the database migration, you may be prompted to update certain report objects. You cannot complete this step until the File Repository Servers have been upgraded and BusinessObjects Enterprise is back online. Therefore, you must postpone this step until you have finished upgrading components.
Copying data from a Crystal Enterprise 9 repository database

In Crystal Enterprise 9, the Crystal Repository database was hosted on a separate database server that you could connect to through ODBC. The tool you use to migrate this information is called the Repository Migration Wizard and is available on Windows as part of the client tool installation. For information on client tools, see Performing a client tool installation on page 70. In a BusinessObjects Enterprise environment, begin by making a backup copy of the source repository database. Then replace the repository by importing its contents into the CMS database using the Repository Migration Wizard. When you use the Repository Migration Wizard, neither the source nor the destination database is overwritten. Objects from the source repository will be added to the destination repository database. If the Wizard finds identical objects (that is, objects with the same unique identifier) in the source and destination repositories, the source objects will not be copied. When you copy repository objects into BusinessObjects Enterprise XI, only the most recent version of each object is copied. Note: Reports configured to use the source repository will now refer to the destination data source.
261
15
1.
To copy repository data from Crystal Enterprise 9 From the BusinessObjects Enterprise program group, click Repository Migration Wizard. You must run the wizard on the machine containing your source repository. From the Source list in the Select Source Repository dialog, click the name of the repository that you want to import. Type the UserID and Password of a user with administrative rights to the repository database. Click Next. The Select Destination Data Source dialog appears. In the CMS field, type the name of the destination data sources Central Management Server. Type the User Name and Password of an Enterprise account that provides you with administrative rights to the CMS; then click Next. From the Source Repository Objects list, select the items that you want to copy to your BusinessObjects Enterprise repository database. Click Next.
2. 3. 4. 5. 6.
BusinessObjects Enterprise exports the selected repository objects from your BusinessObjects Enterprise Repository, reporting success or failure for each object. 7. Select the folder in your destination repository where objects from your source directory will be placed.
262
15
To add objects to a new folder, select Insert a new folder, and then type the name of the folder.
8. 9.
To delete an existing folder from your repository, select it, and then click Delete the item/folder. Click Next, and then Finish to complete the transfer and close the Repository Migration Wizard.
When you use the Repository Migration Wizard, neither the source nor the destination database is overwritten. Objects from the source repository will be added to the destination repository database. If the Wizard finds identical objects in the source and destination repositories, the source objects will not be copied. When you copy repository objects into BusinessObjects Enterprise XI, only the most recent version of each object is copied. Note: Reports configured to use the source repository will now refer to the destination data source. 1. To copy repository data from Crystal Enterprise 9 From the BusinessObjects Enterprise program group, click Repository Migration Wizard. You must run the wizard on the machine containing your source repository. From the Source list in the Select Source Repository dialog, click the name of the repository that you want to import.
2.
263
15
3. 4. 5. 6.
Type the UserID and Password of a user with administrative rights to the repository database. Click Next. The Select Destination Data Source dialog appears. In the CMS field, type the name of the destination data sources Central Management Server. Type the User Name and Password of an Enterprise account that provides you with administrative rights to the CMS; then click Next. From the Source Repository Objects list, select the items that you want to copy to your BusinessObjects Enterprise repository database. Click Next.
BusinessObjects Enterprise exports the selected repository objects from your BusinessObjects Enterprise Repository, reporting success or failure for each object. 7. Select the folder in your destination repository where objects from your source directory will be placed.
264
15
8.
To delete an existing folder from your repository, select it, and then click Delete the item/folder.
Click Next, and then Finish to complete the transfer and close the Repository Migration Wizard.
When you use the Repository Migration Wizard, neither the source nor the destination database is overwritten. Objects from the source repository will be added to the destination repository database. If the Wizard finds identical objects in the source and destination repositories, the source objects will not be copied. When you copy repository objects into BusinessObjects Enterprise XI, only the most recent version of each object is copied. Note: Reports configured to use the source repository will now refer to the destination data source.
Copying data from a Crystal Reports 9 repository database

The Crystal Repository shipped with Crystal Reports 9 was an Access database (Repository.mdb). By default, it was located in the following directory of your Crystal Reports installation:
C:\Program Files\Common Files\Crystal Decisions\2.0\bin\
265
15
Begin by making a backup copy of this default database. Then replace the default repository by importing its contents into the CMS database using the Repository Migration Wizard. When you use the Repository Migration Wizard, neither the source nor the destination database is overwritten. Objects from the source repository will be added to the destination repository database. If the Wizard finds identical objects in the source and destination repositories, the source objects will not be copied. When you copy repository objects into BusinessObjects Enterprise XI, only the most recent version of each object is copied. Note: Reports configured to use the source repository will now refer to the destination data source. 1. To copy repository data from Crystal Reports 9 From the BusinessObjects Enterprise program group, click Repository Migration Wizard. You must run the wizard on the machine containing your source repository. From the Source list in the Select Source Repository dialog, click the name of the repository that you want to import. If you created security for your repository database, type a User id and Password valid for the repository database. 3. 4. 5. Click Next. Log on to the CMS using a user name with administrative rights to BusinessObjects Enterprise. From the Source Repository Objects list, select the items that you want to copy to your BusinessObjects Enterprise repository database. Click Next.
2.
266
15
6.
Select the folder in your destination repository where objects from your source directory will be placed.
7.
To delete an existing folder from your repository, select it, and then click Delete the item/folder.
Click Next. BusinessObjects Enterprise exports the selected repository objects from your Crystal Reports repository, reporting success or failure for each object.
8.
Click Next, and then Finish to complete the transfer and close the Repository Migration Wizard.
Migrating from the Web Component Server to the Web Component Adapter
In BusinessObjects Enterprise XI, the Web Component Server (WCS) was deprecated. All BusinessObjects Enterprise applications that used the WCS have been migrated to use the Web Component Adapter (WCA). The WCS was a Crystal Enterprise application server that provided two main services: an engine for processing Crystal Server Pages (CSP), and an application engine for CSP web applications.
267
15
Configuring your CSP applications for the Web Component Adapter

CSP-based application hosting is now handled by your Java application server. If you want to use existing CSP-based applications with BusinessObjects Enterprise XI, you need to configure them to work with the Web Component Adapter (WCA). For information about configuring the WCA, see Changing the deployment values for the Web Component Adapter on page 100.
Using an existing web desktop

If you have an existing Crystal Enterprise 10 web desktop that you want to continue using with BusinessObjects Enterprise XI, you must install an extra feature to support the older web application. The v10 Crystal Enterprise Web Desktop Support feature is installed by default when you use the setup program to upgrade from Crystal Enterprise 10 to BusinessObjects Enterprise XI, but it is not installed as part of a New installation. The v10 Crystal Enterprise Web Desktop Support feature adds the web desktop application object to your BusinessObjects Enterprise system. This application object allows the system to recognize an existing web desktop and control user access rights to the desktop. Note: You can use the Custom installation during your initial install and select the feature that supports the Crystal Enterprise 10 web desktop. Alternatively, after your installation, you can add the Crystal Enterprise 10 web desktop from Add /Remove Programs in the Control Panel. For further information see Adding Crystal Enterprise 10 web desktop support on page 77.
You can only use the setup program to upgrade from previous version if you performed a full standalone client or server when you installed Crystal Enterprise 10. A full standalone server install means during the initial install, you installed the complete feature set onto one machine. This includes all the client components, the server components, the SDKs and either the Java or the .NET Web Component Adapter or Web Component Server. A full standalone client install means you installed all of the client components onto one machine. If you are upgrading from Crystal Enterprise 9, you do not need to install the v10 Crystal Enterprise Web Desktop Support feature.
268
Upgrading and Migrating Upgrading other components
15
Importing content from BusinessObjects Enterprise, Crystal Enterprise, or Crystal Info

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

If you perform an upgrade directly, it may not be necessary to upgrade any other components after the install. However, in some cases, you cannot upgrade directly and must uninstall the previous version of software first. This section also explains what you need to do to complete a CMS migration after the new software is installed.
Upgrading the Report Application Server

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

This release of BusinessObjects Enterprise includes an updated version of Crystal Reports. You have two choices:
269
15
You can uninstall the existing version of Crystal Reports, and then run the setup program to upgrade the existing versions of Crystal Reports to replace the old software with Crystal Reports XI. You can have both the new and the old versions on the same machine.
Migrating from Crystal Analysis to OLAP Intelligence

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

When you finish copying data from the source database to the destination database, complete these steps before allowing users to access the system. When migrating from an older version of Crystal Enterprise, servers that existed in the source installation do not appear in the migrated install. This occurs because there cannot be a mix of old and new servers in a BusinessObjects Enterprise installation. Server groups from the old installation appear in the new system, but they will be empty. New servers are automatically detected and added to the servers list (outside of any group) in a disabled state. You must enable these servers before they can be used. You may add the new servers to the imported groups as appropriate. Reports that depend on a particular server group for scheduled processing will not execute until a job server is added to that group. Reports that depend on a particular server group for processing are not available until servers are added to that group. 1. To complete a CMS database migration on Windows If errors occurred during migration, a db_migration log file was created in the logging directory on the machine where you ran the CCM to carry out the migration. The CCM will notify you if you need to check the log file. The default logging directory is:
C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Logging\
2.
If you migrated CMS data from a different CMS database into your current CMS database, you need to make your old input and output directories available to the new Input and Output File Repository Servers. You can do this in several ways:
270
15
Copy the contents of the original input root directory into the root directory that the new Input File Repository Server is already configured to use. Then copy the contents of the original output directory into the root directory that the new Output File Repository is already configured to use. Reconfigure the new Input and Output File Repository Servers to use the old input and output root directories. If the old Input and Output File Repository Servers are running on a dedicated machine, you can run the BusinessObjects Enterprise setup program to upgrade the servers directly. Then you need not move the input and output directories. Instead, modify the -ns option in both servers command lines to have them register with your new CMS.
3. 4. 5.
Use the Central Configuration Manager (CCM) to start the CMS on the local machine. Make sure your web application server is running. Log on to the Central Management Console with the default Administrator account, using Enterprise authentication. Tip: If you just replaced your CMS database with data from an older system, keep in mind that you now need to provide the Administrator password that was valid in the older system.
6. 7. 8.
Go to the Authorization management area and check that your BusinessObjects Enterprise license keys are entered correctly. In the CCM, start and enable the Input File Repository Server and the Output File Repository Server. Go to the Servers management area of the Central Management Console and verify that the Input File Repository Server and the Output File Repository Server are both started and enabled. Click the link to each File Repository Server and, on the Properties tab, check that the Root Directory points to the correct location.
9.
10. Return to the Central Configuration Manager. 11. If objects in your source database require updating, the Update Objects button on the toolbar contains a flashing red exclamation mark. Click Update Objects. 12. When prompted, log on to your CMS with credentials that provide you with administrative privileges to BusinessObjects Enterprise. The Update Objects dialog box tells you how many objects require updating. Objects typically require updating because their internal representation has changed in the new version of BusinessObjects
271
15
Upgrading and Migrating Migrating to performance management XI Release 2
Enterprise, or because the objects require new properties to support the additional features offered by BusinessObjects Enterprise XI. Because your Central Management Server was stopped when the migration occurred, you need to update the objects now. 13. If there are objects that require updating, click Update, otherwise click Cancel. 14. Start and enable the remaining BusinessObjects Enterprise servers. Verify that BusinessObjects Enterprise requests are handled correctly, and check that you can view and schedule reports successfully.
Migrating to performance management XI Release 2

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

Connections to the performance management repository are imported by the Import Wizard. In BusinessObjects Enterprise XI, connections are managed by the Connection Server. Refer to the Designer online help for more information on the Connection Server. You may choose to import all universes and connections, or only those universes and connections referenced by the performance management objects (such as dashboards and analytics) that you have selected for import.
272
Upgrading and Migrating Migrating the performance management repository
15
Each connection you import is stored as an InfoObject in the CMS. Performance management XI makes use of the BusinessObjects Enterprise XI standard connection layer. Performance management XI uses the Connection Server to run the SQL generated by the following Performance Management engines:
Sets Process Analysis Metrics Predictive
Connections are configured in Designer and stored in the CMS. Refer to the Universe Designer's Guide for more information. The ci_connection table that stored connection details in previous versions is obsolete in BusinessObjects Enterprise XI.
Migrating the performance management repository

After you migrate InfoObjects from the CMS, you migrate the performance management repository in the Repository Management section of the System Setup page in performance management setup. Refer to the Performance Management Setup and Administration online help. The performance management XI R2 repository includes new columns in the repository tables to support new features and the new architecture. All universes are stored as InfoObjects in the CMS. Changes to the performance management repository include new fields in the metric table (ci_probe) that store the new metric attributes supported in XI:
metric description metric owner last refresh date
New tables are also added to the ci_target table to support goal import. During the migration process, the Import Wizard verifies that all BusinessObjects universes on which performance management data relies are also selected for import.
273
15
Upgrading and Migrating Migrating schedules
Migrating schedules
In performance management XI, all scheduled tasks are managed by the CMS scheduler. Schedules related to performance management objects are stored in a dedicated Performance Management folder in the Schedule Manager of the CMS.
Migrating rules and named events

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

User rights in BusinessObjects Enterprise XI are managed with Access Levels (ACLs) in the CMS. Objects must be published in the CMS in order to be secured individually with ACLs. 1. 2. 3. To manage ACL rights for performance management users Launch the BusinessObjects Central Management Console. In the Manage menu, select BusinessObjects Applications. Select Performance Management from the list of applications.
274
Upgrading and Migrating Migrating security commands
15
4.
In the Rights tab, click Check User Rights... to display a detailed list of rights per user or user group, or click Add/Remove to change the rights currently granted to users or groups.
Managing rights at the object level in Performance Management XI

In Performance Management XI, you can grant rights to specific analytics, application menus, documents and folders in the Central Management Console. Refer to the BusinessObjects Enterprise Administrators Guide for more details on managing object-level security.
275
15
Upgrading and Migrating Migrating security commands
276
Uninstalling
chapter
16
Uninstalling Uninstalling BusinessObjects Enterprise from Windows
Uninstalling BusinessObjects Enterprise from Windows

Stop your web server before uninstalling BusinessObjects Enterprise. Then disable and stop all BusinessObjects Enterprise servers. If you want to save reports and system information, backup the root directories used by the Input and Output File Repository Servers and backup the CMS database. Before restarting your web server, manually remove any changes that you made to your web servers configuration files when you set up BusinessObjects Enterprise. 1. 2. 3. 4. To remove BusinessObjects Enterprise from Windows 2000 Open the Central Configuration Manager (CCM) and select all of the servers, then right-click the selected servers and choose Stop. In Windows, click Start, point to Settings, and then select Control Panel. Double-click Add/Remove Programs. Select BusinessObjects Enterprise and click Remove. The Add/Remove Programs dialog box prompts you to confirm that you want to remove BusinessObjects Enterprise from your computer. 5. Click Yes. Please wait while the appropriate files are removed and the necessary configuration is carried out. 6. Click Finish. BusinessObjects Enterprise has been uninstalled and you are returned to the Add/Remove Program Properties dialog box. Note:
Your BusinessObjects Enterprise XI installation may have included the installation of a Tomcat java application server. By default, Tomcat installs to C:\Program Files\BusinessObjects\Tomcat\. When BusinessObjects Enterprise XI is uninstalled, the contents of the Tomcat subfolder, as well as any user files, are also removed. Folders or files (such as log files or report files, for example) created outside of the initial installation are not removed. The installer removes only the files that it installed.
Deploying on WebLogic 9.2 with the JDK 1.5
appendix
Deploying on WebLogic 9.2 with the JDK 1.5 Before you start
Before you start

Before you begin the deployment process, you should verify that the application server is running correctly by launching its default page, or administrative console in a web browser. For BEA WebLogic 9.2, type
http://servername:7001/console.


The table that follows lists the contents of the WAR files. WAR File desktop.war Contents Contains InfoView, performance management, and Information Analyzer components. Contains older components of the Central Management Console Contains newer components of the Central Management Console Contains the administrative tools from the admin launchpad. These tools include administrative tool console, Schedule Manager, Instance Manager, View Server Summary, Query Builder, Object Repository Helper Contains Crystal Reports Explorer components Contains images, style sheets, and scripts used by the DHTML and Web Authoring components of OLAP Intelligence Contains OLAP Intelligence help files
webcompadapter.war jsfadmin.war admin.war
AnalysisHelp.war
280
BusinessObjects Enterprise XI Release 2 Installation Guide Addendum
Deploying on WebLogic 9.2 with the JDK 1.5 Before you start
WAR File afhelp.war
Contents Contains performance management help files Note: If performance management is not installed, this WAR file will not be installed. Contains Web Services.
dswsbobje.war Note:
If you install performance management after your initial install and deployment of BusinessObjects Enterprise, you will need to undeploy desktop.war and then redeploy it. This is not required if you install BusinessObjects Enterprise at the same time as performance management because the war file is modified by the performance management install before you deploy it. If you will not be using Crystal Report Explorer, you are not required to deploy adhoc.war. If you will not be using OLAP Intelligence, you are not required to deploy either AnalysisHelp.war or styles.war. If you will not be using Web Services, you are not required to deploy dswsbobje.war. If you will not be using performance management, you are not required to deploy afhelp.war.

The table that follows lists the context roots that should be used when you deploy the war files. War File desktop.war webcompadapter.war jsfadmin.war admin.war afhelp.war styles.war AnalysisHelp.war adhoc.war dswsbobje.war Context Root /businessobjects/enterprise115/desktoplaunch /businessobjects /jsfadmin /businessobjects/enterprise115/adminlaunch /bobj /styles /AnalysisHelp /businessobjects/enterprise115/adhoc /dswsbobje
281
Deploying on WebLogic 9.2 with the JDK 1.5 Deploying on BEA WebLogic 9.2
Note:
It is not recommended that you alter the context root because many of the war file have dependencies on each other. For example, if you change the context root of either jsfadmin.war or webcompadapter.war, calls made between different components of the Central Management Console will not work. Desktop.war does not depend on any of the other war files so it can be deployed at any time. The remaining files have dependencies on each other so must be deployed in a specific order. First deploy the webcompadapter.war, followed by jsfadmin.war and finally admin.war. Adhoc.war, AnalysisHelp.war, styles.war, afhelp.war, dswsbobje.war, and can now be deployed.

The table that follows lists the locations of the WAR files. WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, AnalysisHelp.war dswsbobje.war Location
c:\Program files\business objects\businessobjects enterprise 11.5\java\applications c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files \business objects\ performance management 11.5
afhelp.war
Note: If performance management is not installed, this WAR file will not be present.
Deploying on BEA WebLogic 9.2

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

1. To create a domain in WebLogic on Windows Launch the WebLogic Configuration Wizard. From the Start menu, select Programs > Bea Products > Tools > Configuration Wizard. 2. 3. Select Create a new WebLogic domain, and then click Next. Select Generate a domain configured automatically to support the following BEA products:, then click Next.
283
4.
Enter a User Name and Password. Confirm the password, and then click Next. Tip: Record this information as it will be required later to log on. Ensure the Sun JDK 1.5 is selected on the Configure Server Start Mode and JDK page, then click Next. Tip: The Sun JDK 1.5 is the one that begins with Sun SDK 1.5. Select No on the Customize Environment and Services Settings page, then click Next. Enter the domain name and specify the location of the domain, if you want to modify the defaults, then click Create. You will receive a message when the configuration completes. Click Done. Note: To start the administration server for the domain you are creating, select the check box beside Start Admin Server before you click Done.
5.
6. 7.
8.
Setting the context root

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

1. 2. 3. To set the context root using an editor Create a temporary directory and in this directory, create a new directory called WEB-INF. Create a file called weblogic.xml in the WEB-INF directory. Add the following information to the file:
<weblogic-web-app> <context-root>/context path</context-root>
284
</weblogic-web-app>
4.
Replace context path with the context path that applies to the WAR file. WAR File desktop.war Context Path /businessobjects/ enterprise115/ desktoplaunch /businessobjects/ enterprise115/adminlaunch /businessobjects /bobj /businessobjects/ enterprise115/adhoc /analysishelp /styles /dswsbobje
admin.war webcompadapter.war afhelp.war adhoc.war AnalysisHelp.war styles.war dswsbobje.war 5. 6. Save and close the file.
Add weblogic.xml to the WAR file. From the temporary directory, run this command:
jar -uvf <WAR_NAME_TO_BE_UPDATED> WEB-INF/weblogic.xml
7.
Repeat the steps 3 to 6 until all the required context paths are changed. Tip: You do not need to specify the context path for the WAR files jsfadmin, AnalysisHelp, styles or dswsbobje since WebLogic already assumes a context root is the same as the file name.
Deploying performance management

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

If you have performance management in a distributed environment, you must copy the InitConfig.properties file from one machine to the other so that you can log on to performance management.
285
1. 2.
To specify the location of your InitConfig.properties file on Windows Create a new folder on the drive on which BusinessObjects Enterprise is installed. Copy the InitConfig.properties file to the folder you created in the previous step. The default location for this file is as follows: C:\Program Files\Business Objects\Performance Management 11.5

If you are deploying performance management, you will need to add a web.xml to the afhelp.war. This is the war file that contains the help for performance management; This step must be completed before deploy the WAR file that contains the help for performance management. 1. 2. 3. To prepare the afhelp.war file Create a temporary directory and in this directory, create a new directory called WEB-INF. Create a file called web.xml in the WEB-INF directory. Copy the following text into the web.xml file:
<?xml version="1.0"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3// EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app>  <display-name>afhelp</display-name> <description> afhelp. </description> </web-app>
4.
If you want to use the OLAP Intelligence DHTML viewer or performance management, you must modify the Java Virtual Machine (JVM) options in WebLogic.
286
1.
To add the JVM options in WebLogic Open the WebLogic loader script in a text editor. This file is called StartWeblogic.cmd and is found in the directory [WebLogic_Home]\user_projects\domains\base_domain\bin, where WebLogic_Home is directory where WebLogic is installed and where base_domain is the name of the domain. Note: If you followed the steps in Creating a domain on page 283, enter the domain name you entered in this step. If you already had a domain created for BusinessObjects Enterprise, enter this domain name instead.
2.
If you want to use the OLAP Intelligence DHTML viewer, add the following after the PATH and CLASSPATH settings:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dbusinessobjects.olap.bin=C:\Progra~1\Busine~1\ OLAPIn~1.5\DHTMLC~1 -Dbusinessobjects.olap.stylesheets=C:\Progra~1\Busine~1\ OLAPIn~1.5\styles~1 -Dbusinessobjects.olap.xslt.TransformerFactory= org.apache.xalan.processor.TransformerFactoryImpl -Djava.library.path=C:\PROGRA~1\BUSINE~1\OLAPIN~1\ DHTMLC~1
Note: The text should be entered as a single line, with spaces separating the arguments (denoted by the "-D"). 3. If you want to use performance management, add the location for the Initconfig.properties file to the Java options. -Daf.configdir="<INSTALLDIR>\BUSINE~1\PERFOR~1.5\ Note: If you changed the default location for the InitConfig.properties file, specify the modified location for this file. See Copying your performance management InitConfig. properties file on page 285 for more information. 4. Save and close the file.
Setting required variables in startup script

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

1.
Setting the CLASSPATH Setting the PATH To modify the startup script for windows Open the WebLogic loader script in a text editor.
287
This file is called StartWeblogic.cmd and is found in the directory [WebLogic_Home]\user_projects\domains\base_domain\bin , where WebLogic_Home is directory where WebLogic is installed and where base_domain is the name of the domain. Note: If you followed the steps in Creating a domain on page 283, enter the domain name you entered in this step. If you already had a domain created for BusinessObjects Enterprise, enter this domain name instead. 2. Append the CLASSPATH variable with the location of cewcanative.jar, including cewcanative.jar. By default, the cewcanative.jar file is found in the directory C:\Program Files\Business Objects\BusinessObjects Enterprise 115\java\applications\. If the default path was changed for your installation of BusinessObjects Enterprise, modify the path accordingly. For example:
set CLASSPATH=%WEBLOGIC_CLASSPATH%;% POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar ;%WL_HOME%\server\lib\webservices.jar;C:\Program Files\ Business Objects\BusinessObjects Enterprise 11.5\java\applications\cewcanative.Jar;%CLASSPATH%
Note: The only spaces in the definition are between the first occurrence of Business and Objects and between BusinessObjects and Enterprise. If your JAR file is in a different location, change the directory accordingly. 3. Append the PATH variable with the location of the required DLLs. By default, these are found in the following directory:
C:\Program Files\Business Objects\BusinessObjects Enterprise 115\win32_x86
4.
If you are deploying OLAP Intelligence and wish to use the DHTML viewer, append the PATH variable with the location of the OLAP Intelligence DHTML viewer. This is default location for the DHTML components:
C:\Program Files\Business Objects\OLAP Intelligence 11.5\DHTML Components
5.
Save and close the file.
288
Changing the default parser and transformer

By default, Weblogic 9.2 uses the parser shipped with JDK 1.5. However, previous version of WebLogic and BusinessObjects Enterprise XI Release 2 use a different parser. Before you deploy desktop.war, you need to modify the default version of the parser to use this compatible parser. This version of the parser is still shipped with Weblogic 9.2. 1. 2. 3. 4. 5. 6. 7. 8. 9. To change the version of the parser and transformer Open the administration console. Expand Services. Select XML Registries. Click Lock & Edit. Select New. In the Name field on the Create a New XML Registry page, type BusinessObjects Enterprise Infoview. Enter the following in the Document Builder Factory field:
weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl
Enter the following in the SAX Parser Factory field:

weblogic.apache.xerces.jaxp.SAXParserFactoryImpl
Enter the following in the Transformer Factory field:

weblogic.apache.xalan.processor.TransformerFactoryImpl
10. Click Next. 11. Specify the server instance you want the changes applied to, then click Finish. 12. Click Activate Changes.
Adjusting the size of the JVM permanent generation

If you are performing memory-intensive operations such as viewing Crystal Reports with dynamic and cascading parameters, you may receive an out of memory error. To avoid this possible issue, you can specify the JVM PermSize and MaxPermSize options in the WebLogic startup script. 1. To modify the JVM permanent generation Open the WebLogic startup script in a text editor.
289
This file is called StartWeblogic.cmd and is found in the directory [WebLogic_Home]\user_projects\domains\base_domain, where WebLogic_Home is directory where WebLogic is installed and where base_domain is the name of the domain. Note: If you followed the steps in Creating a domain on page 283, enter the domain name you entered in this step. If you already had a domain created for BusinessObjects Enterprise, enter this domain name instead. 2. Append the following option to the JAVA_OPTIONS:
-XX:PermSize=48m -XX:MaxPermSize=128m
Note: The MaxPermSize can be increased to 256m if necessary. 3. 4. Save and close the file. Restart WebLogic.

1. Start the WebLogic Admin server. To start the admin server, open a console window, navigate to the [WebLogic_installdir]\user_projects\domains\base_domain directory where WebLogic_installdir is the directory where WebLogic is installed and where base_domain is the name of the domain. Note: If you followed the steps in Creating a domain on page 283, enter the domain name you entered in this step. If you already had a domain created for BusinessObjects Enterprise, enter this domain name instead. 2. 3. 4. 5. 6. 7. 8. 9. Execute the following command:
startWebLogic.cmd
Launch the Admin console. Open a browser window, type http://<host name>:7001/console and then press Enter. Enter the username and password. From the Domain Structure area of the page, click domain_name. Click Deployments. Click Lock & Edit. Click Install. The Install Application Assistant will appear. Select the location where the WAR files are.
290
See Locations of the WAR files on page 282 for information on where the WAR files can be found. Note: The location you choose will remain selected throughout this procedure unless you change it. 10. Select desktop.war, then click Next. 11. Click Next, then click Finish. Note: This process takes several minutes for small WAR files to be deployed, and a greater amount of time for the larger WAR files. 12. Click Activate Changes. 13. Select the deployed WAR file and click Start, then select Servicing all requests. 14. Click Yes to confirm. 15. Repeat the process from step 6 to 13, for each of these WAR files in the order they are listed:
webcompadapter.war jsfadmin.war admin.war
16. Repeat the process from step 6 to 13 for any other war files you wish to deploy. Tip: See Contents of the WAR files on page 280 for information on what each WAR file contains. You are not required to deploy a war file if you dont require a component it contains.

If you want to integrate Crystal Reports Explorer with InfoView, you have to modify the war file for InfoView (desktop.war) before you it. 1. To integrate Crystal Reports Explorer Locate the desktop.war file. The default location for this file is C:\Program Files\Business
2. 3. 4.
Open the WAR file and extract adhoc-config.xml from the WEB-INF directory. Modify the value between <serverpath> and </serverpath> with http://servername:portnumber/businessobjects/enterprise115/adhoc. Save the file.
291
After you deploy adhoc.war, you will be able to access Crystal Reports Explorer if you enter http://servername:portnumber/businessobjects/ enterprise115/adhoc in your browser.
Verifying the WebLogic Configuration

To verify the configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. To verify the WebLogic configuration Open a browser window. Enter the url for the desktop launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ desktoplaunch. For example: http://localhost:7001/businessobjects/enterprise115/desktoplaunch 2. Enter the url for the administration launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ adminlaunch. For example: http://localhost:7001/businessobjects/enterprise115/adminlaunch Note: You cannot use the shortcuts in the BusinessObjects Enterprise program group to access the BusinessObjects Enterprise Launchpads deployed on your Java web application server. To access them, you must include the port number of the Java web application server in your URL.
To access the InfoView running on your Java web application server, type:
http://server01:portnum/businessobjects/enterprise115/ desktoplaunch
To access the BusinessObjects Enterprise Administration Launchpad running on your Java web application server, type:
http://server01:portnum/businessobjects/enterprise115/ adminlaunch
where server01 is the name of the server, and portnum is the port number of the Java web application server.
292
Deploying on Tomcat with the JDK 1.5
appendix
Modifying Tomcat to use JDK 1.5

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

1. To create a new version of Tomcat that uses the JDK 1.5 Install the new JDK 1.5 on your machine. Note: This version cannot be installed from the BusinessObjects Enterprise installer. You must download this version from your JDK vendor. 2. 3. Record the directory where the new files are installed. If you had previously deployed on Tomcat with the JDK 1.4 shipped with BusinessObjects Enterprise, stop the instance of Tomcat already running.
294
Note: This can be done either from within the CCM or from Tomcat configuration dialog available from the Start menu. 4. Go to the following directory, where INSTALLDIR is the installation location for the original version of Tomcat shipped with BusinessObjects Enterprise: <INSTALLDIR>\Tomcat\bin This is the default location for this directory: C:\Program Files\Business Objects\Tomcat\bin. 5. 6. 7. 8. 9. Open this file in a text editor: setenv.bat Modify the JAVA_HOME variable with the location of the newly installed JDK 1.5. Save and close the file. Open the Apache Tomcat Properties dialog. Go to the Start menu and select Programs> Tomcat >Tomcat Configuration. Click on the Java tab.
10. Ensure Java Virtual Machine and Java Classpath is set to the location you installed the JDK 1.5. 11. Restart Tomcat.

The table that follows lists the locations of the WAR files.
295
WAR File webcompadapter.war, jsfadmin.war, desktop.war, admin.war, adhoc.war, styles.war, AnalysisHelp.war
Location
c:\Program files\business objects\businessobjects enterprise 11.5\java\applications
Note: If you plan on using Crystal Reports Explorer, see Integrating Crystal Reports Explorer with InfoView on page 300 before you deploy this WAR file. Styles.war and AnalysisHelp.war may not be present in your installation. These files are only present if you installed the original version of BusinessObjects Enterprise Release 2 or BusinessObjects Enterprise Release 2 SP1.
dswsbobje.war, BusinessProcessBI.war
c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code> c:\Program files\business objects\performance management 11.5
afhelp.war
Copying the required Jar file to Tomcat

After you have installed a new version of Tomcat, you must copy the cewcanative.jar file to Tomcats shared\lib directory.
Copying the JAR files Copy the jar file from the following location to the new shared\lib directory of your new Tomcat install:
C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\java\applications\cewcanative.jar
Note: If you modified the default directory where BusinessObjects Enterprise is installed, please modify this directory accordingly.
296
Adding the Java Options

1. To add the required java options on Windows. Open the Apache Tomcat Properties dialog. Go to the Start menu and select Apache Tomcat 5.0 >Configure Tomcat. Note: The previous path assumes you have setup Tomcat as a service. 2. 3. Click on the Java tab. Enter the following java arguments in the Java Options field. Settings for BusinessObjects Enterprise -Djava.library.path=WINDIR\system32\;BOBJDIR\ BusinessObjects Enterprise 11.5\win32_x86\ ;BOBJDIR\OLAP Intelligence 11.5\DHTML Components\; 4. If you are using OLAP Intelligence, in addition to the options from Step 8, set these Java options: Settings for OLAP Intelligence -Dbusinessobjects.olap.bin=BOBJDIR\OLAP Intelligence 11.5\DHTML Components -Dbusinessobjects.olap.xslt.TransformerFactory= org.apache.xalan.processor.TransformerFactoryImpl -Dbusinessobjects.olap.stylesheets =BOBJDIR\OLAP Intelligence 11.5\stylesheets 5. If you are using performance management, in addition to the options from Step 8, set these Java options: Settings for performance management -Daf.configdir=BOBJDIR\Performance Management 11.5 6. Deploy the WAR files. See Deploying the WAR files on page 298 for the specific steps.
297

After you have completed all the steps involved in installing and configuring a new version of Tomcat to work with JDK 1.5, you must deploy the WAR files. 1. To deploy the war files Confirm the location of the WAR files. By default, the WAR files are located in c:\Program Files\Business Object\BusinessObjects Enterprise 11.5\java\applications. Open a text editor. Create the files listed in the following table and add the content specified in the Content column to the files. This will set the context path for each WAR file. Substitute the variable WARDIR with default location or the specific directory where you placed your files. Note: As a general rule, WAR files must be deployed on the same machine as they were installed. This is because the installation will replace some text variables inside local WAR files with machine and CMS specific values at install. Note: If you install BusinessObjects Enterprise in a location other than the default installation directory of C:\Program Files\ Business Objects\BusinessObjects Enterprise 11.5\, adjust the path descriptions to match your actual install directories. Filename desktopwar.xml Content <Context docBase="WARDIR/ desktop.war" path="/businessobjects/ enterprise115/desktoplaunch" crossContext="false" debug="0" reloadable="false" trusted="false"/>
2. 3.
webcompadapterwar. <Context docBase="WARDIR/ xml webcompadapter.war" path="/ businessobjects" debug="0" reloadable="false"/> jsfadminwar.xml <Context docBase="WARDIR/ jsfadmin.war" path="/jsfadmin" debug="0" reloadable="false"/> <Context docBase="WARDIR/ admin.war path="/businessobjects/ enterprise115/adminlaunch" crossContext="false" debug="0" reloadable="false" trusted="false"/>
adminwar.xml
298
Filename adhocwar.xml
Content <Context docBase="WARDIR/ adhoc.war path="/businessobjects/ enterprise115/adhoc" crossContext="false" debug="0" reloadable="false" trusted="false"/> <Context docBase="WARDIR/ AnalysisHelp.war" path="/ AnalysisHelp" crossContext="false" debug="0" reloadable="false" trusted="false"/>> <Context docBase="WARDIR\styles.war" path="/ styles" crossContext="false" debug="0" reloadable="false" trusted="false"/> <Context docBase="c:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Services\<language_code>\dswsbobj e.war path="dswsbobje" crossContext="false" debug="0" reloadable="false" trusted="false"/>
analysishelpwar.xml
styleswar.xml
dswsbobjewar.xml
Note:
Desktop.war does not depend on any of the other war files so it can be deployed at any time. The remaining files have dependencies on each other so must be deployed in a specific order. First deploy the webcompadapter.war, followed by jsfadmin.war and finally admin.war. Adhoc.war, analysishelp.war, styles.war and dswsbobje.war can now be deployed. Replace <language_code> with the code specific to the language of your installation, for example en or fr. Save each file to TOMCATDIR\CONF\Catalina\localhost, where TOMCATDIR is replaced with the directory where Tomcat is installed. Restart Tomcat. Open the Apache Tomcat Properties dialog. Go to the Start menu and select Apache Tomcat 5.0 >Configure Tomcat, and then, click Start to restart Tomcat.
4. 5.
299

Desktop.war contains the components for InfoView; Adhoc.war contains the components for Crystal Reports Explorer. If you want to integrate Crystal Reports Explorer with InfoView, you must make some changes in desktop.war before it is deployed. 1. To integrate Crystal Reports Explorer Locate the desktop.war file. The default location for this file is
2. 3. 4. 5.
Open the WAR file and extract adhoc-config.xm from the WEB-INF directory. Modify the value between <serverpath> and </serverpath> with http://servername:portnumber/businessobjects/enterprise115/adhoc. Save the file. Place it back in desktop.war.
Verifying the Tomcat deployment

To verify the Tomcat configuration, make sure that InfoView and the Central Management Console can be launched in a browser. 1. 2. To verify the Tomcat configuration Open a browser window. Enter the url for InfoView in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/desktoplaunch. For example: http://localhost:8080/businessobjects/enterprise115/desktoplaunch 3. Enter the url for the administration launchpad in the browser using the format http://[host name]:[port number]/businessobjects/enterprise115/ adminlaunch. For example: http://localhost:8080/businessobjects/enterprise115/adminlaunch
300
Business Objects Information Resources
appendix
Business Objects Information Resources Documentation and information services
Documentation and information services

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

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

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

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

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

Look in the docs directory of your product CD for versions of guides in Adobe PDF format.
302BusinessObjects Enterprise XI Release 2 Installation Guide
Business Objects Information Resources Customer support, consulting and training
Send us your feedback

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

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

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

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

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

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

Address Business Objects product information http://www.businessobjects.com Product documentation http://www.businessobjects.com/ support Business Objects Documentation mailbox documentation@businessobjects.com Online Customer Support http://www.businessobjects.com/ support/ Business Objects Consulting Services http://www.businessobjects.com/ services/consulting/ Business Objects Education Services http://www.businessobjects.com/ services/training Content Information about the full range of Business Objects products. Business Objects product documentation, including the Business Objects Documentation Roadmap. Send us feedback or questions about documentation. Information on Customer Support programs, as well as links to technical articles, downloads, and online forums. Information on how Business Objects can help maximize your business intelligence investment. Information on Business Objects training options and modules.
Business Objects Information Resources Useful addresses at a glance
Index
Symbols
@Variable('BOPASS') 212 @Variable('BOUSER') 212 migrating OLAP data providers 204 migration of rights 204 BusinessObjects Enterprise 5.x/6.x 195 BusinessObjects SDK Send to BCA 204 Send to Inbox 204 BusinessObjects, migration of document rights 204
A
ACEs on import of stored procedures 213 on import of universe-related security commands 210 AD authentication, importing from Crystal Enterprise 193 add-ins, migration 204 agnostic documents, importing 206 aliases 193 Allow user to merge dimension for synchronization right 205 Application Foundation checking universe integrity 197 migration 190, 195 Application Foundation repository, modification during import 196 associated documents 238 Auditor 24 authentication LDAP 193 Windows AD 193 Automated Process Scheduler 18
C
Categories folder 214 categories,selecting for import 236 changing the assigned port number WebSphere 5.1 147 WebSphere 6.0 147 checklist for installation 33 client tools, installing 60 CMS database migration 39 CMS, and Application Foundation objects 196 codepage DB2 16 UTF-8 16 components, selecting individually on Windows 61 configuring MySQL 46 your database 47 connections BOUSER/BOPASS variables 212 stored procedures 213 connectivities, recreating in XI R2 200 consultants, Business Objects 304 context root editor 284 WebLogic Builder 158 converting .rep files to .wid 203 .rep files to .wqy 203 corporate documents, storage after import 203 Crystal Enterprise 10 web desktop support 77
B
BEA WebLogic 157, 282 Business Objects consulting services 304, 305 support services 303 training services 304, 305, 305 BusinessObjects documents import limitations 204 importing 203
307
Index
Crystal Reports Explorer 24 integrating with InfoView 134, 299 NetWeaver 187 Oracle 176 Tomcat Crystal Reports Explorer,WebSphere 149 Crystal Server Pages 19 CSP. See Crystal Server Pages CSP deprecation 19 CSV format 242 CUIDs 205 custom installation 26 deselecting features 64 selecting features 64 Windows 61 customer support 303
D
data sources,creating on destination server machines 198 database configuring 46 permissions 32 preparing your existing 31 database configuration 47 database server options 18 MySQL 18 tested database servers 19 database server preparations 31 database, CMS 39 databases supported in XI R2 200 synchronizing enterprise and database credentials 212 using the DBUSER/DBPASS variables 212 DB2 codepages 16 deploying NetWeaver 183 Oracle 171 Tomcat 128 WebLogic 157, 282 WebSphere 142 deploying Ear files 185 deployment environment 19 derived universe 211
Designer 5/6 and XI R2 compatibility 211 and access restrictions in XI R2 212 Desktop Intelligence 23 destination environment, and importing 223 destination environments 216 development environments 19 distributed deployments 66 installing on web server 67 installing only server and client 67 installing only the WCA 74 distributed install, performance management 75 document passwords 204 documentation feedback on 303 on product CD 302 on the web 302 roadmap 302 documents, importing without locales 206 Domain Key file 217 domains importing 214 importing universe domains 211
E
Edit SQL right 205 education. See training environment 199 events 194 Expanded installation on Windows 52 exporting objects 199
F
Favorites folder 202 feedback, on documentation 303 firewalls 41 folders, Universe 211 FRS, connection storage 210 full standalone server install 28
G
General Supervisor login 218 groups, importing 232
308
Index
I
IBM WebSphere 142 IIS 21 Import Groups Option dialog box 233, 233 Import Progress dialog box 241 Import Universe and Connection Objects Options dialog box 229, 240 Import Wizard 60 Application Foundation 190, 195 how it imports domains 214 how it imports universe connections 211 mapping to Inbox and personal files 198 migrating Application Foundation 196 selecting information 225 specifying source 216 specifying source and destination 216, 223 third-party documents 206 importing categories 225, 236 database credentials 242 domains 214 folders from Crystal Enterprise 193 from BusinessObjects Enterprise 5.x/6.x 195 from Crystal Enterprise 191 groups 242 Import Wizard 190 instances from Crystal Enterprise 193 mapping Import Wizard to Inbox and personal documents 198 named events 225 profiles 242 rights 194 selecting information 225 specifying source and destination 216, 216, 223 text files 242 users and groups 232 users with aliases 193 users with LDAP authentication 193 importing content during an upgrade 269 importing groups from Crystal Enterprise 192 importing object rights from Crystal Enterprise 194 importing users 214 importing users, from BusinessObjects Enterprise 5.x/6.x 214
importing, Application Foundation 218 importing, BusinessObjects 5.x source environment 216 importing, BusinessObjects 6.x source environment 217 Inbox documents storage after import 202 inbox documents importing 229 mapping Import Wizard to 198 information resources 302 install types 25 client tools 60 custom installation 26 expand installation 25 new installation 25 silent installation 27 upgrade installation 28 installation checklist 33 installation logs 115 installation overview 14 installing client tools 60 on Windows 36 SDKs 250 Interactive Editing right 205
J
Java web application servers 21
L
locale and .wqy files 206 importing documents without locales 206 migration of universe 210 logs installation 115 LOVs, access from XI R2 197
M
Microsoft Internet Information Server 21 Microsoft SQL Server 39 migrating Application Foundation 190, 195
309
Index
BusinessObjects documents 203 CMS database 39 connections 211 domains 214 from BusinessObjects Enterprise 6.x 254, 307 from Crystal Enterprise 191, 257 from the Web Component Server 267 selecting information 225 specifying source 216 specifying source and destination 216, 223 third-party documents 206 migration of document rights 204 migration, locales 206 minimum requirements, Windows 39 MySQL 18, 39 MySQL configuration 46
Perfomance management, distributed install 75 Performance Manager 23 Personal Categories folder 214 personal documents importing 229 mapping Import Wizard to 198 storage after import 202 Platform COM SDK 204 platforms, updating 200 Populate Database Credentials for Users dialog box 234 post install deployments 97, 125 preparing for installation 33 preparing your database server 31 Public folder 203 Publishing Wizard 60
N
named events 225 NetWeaver creating an EAR file 184 deploying EAR files 185 modifying the path 184 new installation 25
R
.rea files, access from XI R2 197 .rep files, migrating 203 reports, importing from Crystal Enterprise 193 repositories 198 Repository Migration Wizard 261, 265 requirements on Windows 39 resources 302 .ret files, migration 203 rights importing from BusinessObject 5.x or 6.x 198 importing from Crystal Enterprise 194 migration of BusinessObjects document rights 204 row restrictions 212
O
object IDs 213 objects exporting 199 restrictions 212 objects, importing from Crystal Enterprise 193 OLAP Intelligence 22 Online Customer Support 303 optional components 22 Oracle configuring classpath 172 deploying 171 deploying war files 175 setting path environment variable 173 orphan documents, defined 203
S
SAP NetWeaver 183 scheduled documents, migration 208 scheduling, importing from Crystal Enterprise 193 SDK Java 251 .NET 251 overview 250 security commands and WebIntelligence document migration 205
P
passwords, DBUSER/DBPASS variables 212
310
Index
migration of universe-related 210 security, synchronizing credentials 212 selecting for import, categories 236 server communication 15 server groups, importing from Crystal Enterprise 194 server locations 17 server-side installation, Windows 66 setting up server communication 15 firewalls 16 Sybase 16 Unicode 16 silent install parameters 92, 121 silent installation on Windows 91, 119 source environment, specifying 216, 216, 223 SQL Server, importing connection objects from 5.x/ 6.x 211 stand-alone installation, Windows 41 Stored Procedures Access right 213 Supervisor, universe access restrictions 212 support customer 303 locations 303 technical 303 web site 303 supported database servers 18 synchronizing, enterprise and database credentials 212 system requirements 14 system requirements, Windows 39
U
unicode 40 uninstalling from Windows 278 universe connections see connections universes checking integrity of those used by Application Foundation objects 197 exclusive overloads 213 importing associated universes 211 modes of import 210 overload aggregation 213 overload collapsing 213 short name 211 the BOUSER/BOPASS variables 212 using the DBUSER/DBPASS variables 212 UNIX importing Inbox and personal documents 199, 199 updating, platforms and versions 200 upgrade installation 28 upgrading considerations 256 Crystal Analysis 270 Crystal Enterprise 258 Crystal Reports 269 from BusinessObjects Enterprise 6.x 195 from Crystal Enterprise 191 Import Wizard 190 importing content 269 overview 254 Report Application Server 269 upgrading from BusinessObjects 5.x 254 upgrading from BusinessObjects 6.x 254 users, importing 232 users, importing from Crystal Enterprise 192 UTF-8 16
T
table mapping 212 technical support 303 text file delimiter 242 text file format 242 text file separator 242 third-party documents, importing 206 Tomcat 128 configuring the Java environment variable 129 setting properties 130 training, on Business Objects products 304
V
VBA macros migration 197 verifying Java web applications 98 verifying NetWeaver 187 verifying the .NET applications 99 version 5.x/6.x, inbox and personal storage 198 version XI R2
311
Index
access restrictions 212 supported connectivities 200
system requirements 39 .wqy files, locale 206
W
was 19 WCA deploying on Windows 99, 99, 175 installing multiple 102 WCS, migrating from 267 web customer support 303 getting documentation via 302 useful addresses 305 web application servers 21 Web Component Adapter 21 web development environments 19 Web Intelligence Allow user to merge dimension for synchronization right 205 Edit SQL right 205 Interactive Editing right 205 web servers 21, 21 web sites support 303 training 304 WebConnect documents, access from XI R2 197 WebIntelligence documents migration limitations 206 rights migration 205 WebIntelligence, migrating orphan documents 203 WebLogic Builder 158 WebSphere deployment 138, 138, 142, 142 .wid files, migrating orphan documents 203 Windows BusinessObjects Enterprise client tools installation 60 custom installation 61 expanded installation 52 full installation 41 Import Wizard 60 installing on non-system drive 41 Publishing Wizard 60 server-side installation 66 silent installation 91, 119 installation overview 36
312

Business Objects Enterprise XI Release 2 - Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Objects Enterprise XI Release 2 - Installation Guide

Uploaded by

Copyright:

Available Formats

BusinessObjects Enterprise XI Release 2 Installation Guide

BusinessObjects Enterprise XI Release 2 Productivity Pack Windows

Copyright Third-party contributors