Deployment Upgrading

Migrating from a Previous Version
BusinessObjects Enterprise 6 Business Intelligence Windows and UNIX
Copyright
No part of the computer software or this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without permission in writing from Business Objects S.A. The information in this document is subject to change without notice. If you find any problems with this documentation, please report them to Business Objects S.A. in writing at documentation@businessobjects.com. Business Objects S.A. does not warrant that this document is error free. Copyright Business Objects S.A. 2003. All rights reserved. Printed in France.
Trademarks
The Business Objects logo, WebIntelligence, BusinessQuery, the Business Objects tagline, BusinessObjects, BusinessObjects Broadcast Agent, Rapid Mart, Set Analyzer, Personal Trainer, and Rapid Deployment Template are trademarks or registered trademarks of Business Objects S.A. in the United States and/or other countries. Contains IBM Runtime Environment for AIX(R), Java(TM) 2 Technology Edition Runtime Modules (c) Copyright IBM Corporation 1999, 2000. All Rights Reserved. This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j. All other company, product, or brand names mentioned herein, may be the trademarks of their respective owners.
Use restrictions
This software and documentation is commercial computer software under Federal Acquisition regulations, and is provided only under the Restricted Rights of the Federal Acquisition Regulations applicable to commercial computer software provided at private expense. The use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252.2277013. U.S. Patent Numbers 5,555,403, 6,247,008, and 6,578,027. 366-50-610-01
Patents Part Number
Contents
Contents Preface Maximizing Your Information Resources 3 9 Information resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Part I Introduction Chapter 1 About Migrating 19
Structure of the guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Windows and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 LDAP directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Chapter 2 Before You Start 27
Upgrade methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Test systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Time-frame for upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Supported operating systems and platforms . . . . . . . . . . . . . . . . . . . . . . . . 40 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Upgrade issues in international deployments . . . . . . . . . . . . . . . . . . . . . . . 46 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Contents
Part II Upgrade Workflows and Scenarios Chapter 3 Generic Workflow: Split Method 51
Phase 1 Modify the platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Phase 2 Copy and upgrade the repository . . . . . . . . . . . . . . . . . . . . . . . . 55 Phase 3 Upgrade desktop products (test environment) . . . . . . . . . . . . . . 58 Phase 4 Upgrade clusters (test environment) . . . . . . . . . . . . . . . . . . . . . 62 Phase 5 Upgrade production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Phase 6 Upgrade original repository and reconnect clusters . . . . . . . . . . 77 Phase 7 Test functionality and scalability . . . . . . . . . . . . . . . . . . . . . . . . . 79 Phase 8 Check the scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Chapter 4 Generic Workflow: Gradual Method 87
Phase 1 Modify the platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Phase 2 Upgrade the repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Phase 3 Upgrade desktop products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Phase 4 Upgrade clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Phase 5 Test functionality and scalability . . . . . . . . . . . . . . . . . . . . . . . . 113 Phase 6 Check the scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Chapter 5 Scenario: Basic Web Deployment 121
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Intermediate deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Chapter 6 Scenario: Basic Web Deployment, Application Server (JSP) 131
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Intermediate deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Contents
Chapter 7
Scenario: Basic Web Deployment, Application Server (ASP)
141
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Intermediate deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Chapter 8 Scenario: Basic Web Deployment, Broadcast Agent 151
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Build a test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Upgrading the production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Chapter 9 Scenario: Application Server, Broadcast Agent, UNIX 161
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Build a test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Upgrade the production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Chapter 10 Scenario: Application Server, Broadcast Agent 169
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Build a test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Upgrade the production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Chapter 11 Scenario: Basic Web Deployment, Auditor 179
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Intermediate deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Upgrade the Auditor cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Chapter 12 Scenario: Basic Web Deployment, ASP, BusinessObjects (3-tier) 189
Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Intermediate deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Contents
Part III Upgrading Individual Products Chapter 13 The Audit Facility and Auditor 201
Upgrading the Audit facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Upgrading Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Chapter 14 Broadcast Agent 207
Broadcast Agent Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Broadcast Agent Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Mixed-version deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Channel tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Hierarchical categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Chapter 15 BusinessObjects 215
Uninstalling/reinstalling desktop products . . . . . . . . . . . . . . . . . . . . . . . . . 217 Upgrading BusinessObjects documents . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Administrative installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 BusinessObjects in 3-tier mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Calculator enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Basing a query on an existing query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Chapter 16 Designer and BusinessQuery for Excel 253
Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 BusinessQuery for Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Chapter 17 Developer Suite 259
BusinessObjects SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 WebIntelligence SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 The OpenDocument function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Contents
Chapter 18
Supervisor
267
Security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Hierarchical categories and Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Changes in SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Chapter 19 WebIntelligence and InfoView 281
Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Upgrading WebIntelligence documents . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Differences between 2.x/5.x and 6.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Part IV Troubleshooting and FAQ Chapter 20 Troubleshooting 301
General installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Document migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 WebIntelligence/InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 BusinessObjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Audit and administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Broadcast Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Chapter 21 Frequently Asked Questions 319
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Repositories and Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Universes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Desktop products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Server and administration products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Index 333
Contents
Contents
Maximizing Your Information Resources
preface
10
Overview
Information, services, and solutions
The Business Objects business intelligence solution is supported by thousands of pages of documentation, available from the products, on the Internet, on CD, and by extensive online help systems and multimedia. Packed with in-depth technical information, business examples, and advice on troubleshooting and best practices, this comprehensive documentation set provides concrete solutions to your business problems. Business Objects also offers a complete range of support and services to help maximize the return on your business intelligence investment. See in the following sections how Business Objects can help you plan for and successfully meet your specific technical support, education, and consulting requirements.
11
Information resources
Whatever your Business Objects profile, we can help you quickly access the documentation and other information you need.
Where do I start?
Below are a few suggested starting points; there is a summary of useful web addresses on page 14. Documentation Roadmap The Documentation Roadmap references all Business Objects guides and multimedia, and lets you see at a glance what information is available, from where, and in what format. View or download the Business Objects Documentation Roadmap at www.businessobjects.com/services/documentation.htm Documentation from the products You can access electronic documentation at any time from the product you are using. Online help, multimedia, and guides in Adobe PDF format are available from the product Help menus. Documentation on the web The full electronic documentation set is available to customers with a valid maintenance agreement on the Online Customer Support (OCS) website at www.businessobjects.com/services/support.htm Buy printed documentation You can order printed documentation through your local sales office, or from the online Business Objects Documentation Supply Store at www.businessobjects.com/services/documentation.htm Search the Documentation CD Search across the entire documentation set on the Business Objects Documentation CD shipped with our products. This CD brings together the full set of documentation, plus tips, tricks, multimedia tutorials, and demo materials. Order the Documentation CD online, from the Business Objects Documentation Supply Store, or from your local sales office.
Information resources
12
Multimedia Are you new to Business Objects? Are you upgrading from a previous release or expanding, for example, from our desktop to our web solution? Try one of our multimedia quick tours or Getting Started tutorials. All are available via the Online Customer Support (OCS) website or on the Documentation CD.
How can I get the most recent documentation?

You can get our most up-to-date documentation via the web. Regularly check the sites listed below for the latest documentation, samples, and tips. Tips & Tricks Open to everyone, this is a regularly updated source of creative solutions to any number of business questions. You can even contribute by sending us your own tips. www.businessobjects.com/forms/tipsandtricks_login.asp Product documentation We regularly update and expand our documentation and multimedia offerings. With a valid maintenance agreement, you can get the latest documentation in seven languages on the Online Customer Support (OCS) website. Developer Suite Online Developer Suite Online provides documentation, samples, and tips to those customers with a valid maintenance agreement and a Developer Suite license via the Online Customer Support (OCS) website.
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: www.businessobjects.com/services/support.htm
13
Services
A global network of Business Objects technology experts provides customer support, education, and consulting to ensure maximum business intelligence benefit to your business.
How we can support you?

Business Objects offers customer support plans to best suit the size and requirements of your deployment. We operate three global customer support centers: Americas: San Jose, California and Atlanta, Georgia Europe: Maidenhead, United Kingdom Asia: Tokyo, Japan and Sydney, Australia Online Customer Support Our Customer Support website is open to all direct customers with a current maintenance agreement, and provides the most up-to-date Business Objects product and technical information. You can log, update, and track cases from this site using the Business Objects Knowledge Base.
Having an issue with the product?

Have you exhausted the troubleshooting resources at your disposal and still not found a solution to a specific issue? For support in deploying Business Objects products, contact Worldwide Customer Support at: www.businessobjects.com/services/support.htm
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: www.businessobjects.com/services/consulting.htm
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 website: www.businessobjects.com/services/education.htm
Services
14
Useful addresses at a glance

Address
Business Objects Documentation www.businessobjects.com/services/ documentation.htm
Content
Overview of Business Objects documentation. Links to Online Customer Support, Documentation Supply Store, Documentation Roadmap, Tips & Tricks, Documentation mailbox.
Business Objects Documentation mailbox documentation@businessobjects.com Product documentation www.businessobjects.com/services/ support.htm
Feedback or questions about documentation.
The latest Business Objects product documentation, to download or view online.
Business Objects product information Information about the full range of Business Objects products. www.businessobjects.com Developer Suite Online www.techsupport.businessobjects.com Knowledge Base (KB) www.techsupport.businessobjects.com Available to customers with a valid maintenance agreement and a Developer Suite license via the Online Customer Support (OCS) website. Provides all the documentation, latest samples, kits and tips. Technical articles, documents, case resolutions. Also, use the Knowledge Exchange to learn what challenges other users both customers and employees face and what strategies they find to address complex issues. From the Knowledge Base, click the Knowledge Exchange link. Practical business-focused examples.
Tips & Tricks www.businessobjects.com/forms/ tipsandtricks_login.asp
15
Address Online Customer Support www.techsupport.businessobjects.com
Content
Starting point for answering questions, resolving issues. Information about registering with Worldwide Customer Support. The range of Business Objects training options and modules.
www.businessobjects.com/services Business Objects Education Services www.businessobjects.com/services/ education.htm
Business Objects Consulting Services Information on how Business Objects can help maximize your business intelligence investment. www.businessobjects.com/services/ consulting.htm
Useful addresses at a glance
16
Typographical conventions
The conventions used in this guide are described in the table below. . Convention This font Indicates Code, SQL syntax, computer programs. For example: @Select(Country\Country Id). This font is also used for all paths, directories, scripts, commands and files for UNIX. Placed at the end of a line of code, the symbol ( ) indicates that the next line should be entered continuously with no carriage return.
Some code more code
$DIRECTORYPATHNAME The path to a directory in the Business Objects installation/configuration directory structure. For example: $INSTALLDIR refers to the Business Objects installation directory. $LOCDATADIR refers to a subdirectory of the BusinessObjects installation directory called locData.
Introduction
part
About Migrating
chapter
20
Overview
This guide explains how to migrate (upgrade) your Business Objects system from a previous version. It covers both Windows and UNIX systems. As used in this guide, migrating from a previous version means: Transferring the deployment of a Business Objects system from an existing major version (2.x/5.x) to the current major version (6.x), while preserving production information as much as possible.
NOTE
Although moving from Business Objects 5.x to Business Objects 6.1 is considered an upgrading process, this release does not constitute an official Business Objects upgrade. For more information, contact your local Business Objects sales office. The Business Objects system includes three major groups of products: Server products For example, WebIntelligence. Desktop products For example, BusinessObjects. Administration products For example, Supervisor. This group of products is a new classification in version 6.x. This guide does not cover: updating to a minor release (such as a service pack) of the same major version; for example, updating from BusinessObjects 5.1 to 5.1.3 system-wide changes in operating systems; for example, moving from Microsoft Windows 2000 to Sun Solaris 8 (UNIX)
NOTE
In the previous version, Business Objects products could have different version numbers; for example, WebIntelligence 2.x and BusinessObjects 5.x. In the new version, however, all products are series 6.x.
About Migrating
21
Upgrading from a pre-2.x/5.x version

If you are upgrading a Business Objects system from a version earlier than 2.x/ 5.x, you must first upgrade to 2.x/5.x. For details, see Updating from a Previous Release in the Installation and Update Guide, version 5.1/2.7.
22
Structure of the guide

This guide has the following sections: PART I INTRODUCTION About migrating (this chapter) Before you start (chapter 2) What you need to know and do before you start upgrading. PART II UPGRADE WORKFLOWS AND SCENARIOS Generic workflow (chapters 3 and 4) The standard upgrade procedure: what you need to do in every case. These two chapters cover the two basic upgrade methods, Split and Gradual. Scenarios (chapters 5-12) Beyond the generic workflow, this section explains what you need to do additionally or differently in your own particular deployment. It describes several of the most typical upgrade scenarios. PART III UPGRADING INDIVIDUAL PRODUCTS Here you can check procedures for the upgrading of a specific product. (chapters 13-19) PART IV TROUBLESHOOTING AND FAQs Troubleshooting (chapter 20) Issues you may encounter when upgrading to the current version, and the recommended solutions. Frequently Asked Questions (chapter 21) For example: Have universes changed between version 2.x/5.x and 6.x? Can BusinessObjects 6.x users access BusinessObjects 5.x documents?
About Migrating
23
Windows and UNIX

Version 6.x does not support UNIX for desktop products. If you are using UNIX servers, you still need a Windows machine for some upgrading tasks. For example, Supervisor can be installed only on Windows. (For a full discussion of where you need Windows on a deployment with UNIX servers, see the Deployment Guide.)
Windows and UNIX
24
LDAP directories
Starting with version 6.1 of the Business Objects suite, you can store and maintain your Business Objects users in a corporate directory. In the current release, the directory used must be LDAP (Lightweight Directory Access Protocol). To configure your Business Objects system for use with an LDAP directory, you use the LDAP Configuration Tool. Due to the integration with LDAP, there have been changes in several Business Objects products. For more information, see the LDAP Security Connector Guide.
About Migrating
25
Terminology
Business Objects has recently streamlined its terminology. Below are some of the major changes:
Previous term
New term
WebIntelligence deployment or system Business Objects deployment or system WebIntelligence server Enterprise Server Products Zero Admin BusinessObjects full-client document (.rep) thin-client document (.wqy) Business Objects Services Administrator Cluster Manager Cluster Node Business Objects server server products BusinessObjects (3-tier mode) BusinessObjects document WebIntelligence document Business Objects Administration Console primary node secondary node
Terminology
26
About Migrating
Before You Start
chapter
28
Overview
This chapter explains what you need to know and do before you start upgrading. The discussion includes an overview of the conditions in which the upgrading process takes place, to help you better understand the options involved. It also presents a number of preliminary procedures. The chapter includes: a summary of the two upgrade methods, Split and Gradual These methods are explained in detail in chapters 3 and 4. backups and test systems time frame for upgrading supported platforms and operating systems repositories compatibility between the previous and new Business Objects systems. For example: - Can a 6.x application connect to a 5.x repository? - Can a 5.x Supervisor function with a 6.x repository? upgrade issues in international deployments
Before You Start
29
Upgrade methods
This section contains a brief summary of the two upgrade methods, to help you choose the one that is best suited to your needs. After you choose a method, see chapters 3 and 4 for detailed, step-by-step instructions. This chapter provides only a general overview. There are two basic upgrade methods: Split You build a test environment with a dedicated repository, alongside your production environment. The system is split into two environments. When version 6.x operates satisfactorily on the test environment, you shut down the Business Objects system and upgrade all production machines at the same time. Versions 2.x/5.x and 6.x never function simultaneously on the same repository. Recommended for smaller deployments. Gradual You upgrade gradually, keeping the 2.x/5.x system running as long as possible until the new installation is complete or nearly complete. This means that two or more clusters (2.x and 6.x mixed) share a single repository. You dont need a separate test environment. Recommended for larger deployments. A version 2.x cluster and a 6.x cluster can work at the same time on the same 6.x repository (using the Gradual method). However, you cannot run 2.x server products and 6.x server products on the same cluster. Following is a summary of the two methods.
Split method
This is a relatively simple and fast solution, although it is often not practical especially for large deployments. The Split method is best for small deployments, where it is possible to upgrade to the current version over the weekend or a holiday period without too much down time for your company.
Upgrade methods
30
The basic procedure is as follows:

REMINDER This is a summary of the Split method. For detailed, step-by-step operating instructions, see Chapter 3.
1. Create a duplicate repository by copying the original version 5.x repository. The original repository continues to function as part of the production environment.
Cluster 1 - 2.x
5.x repository
Cluster 2 - 2.x
Copy of 5.x repository
Cluster 3 - 2.x
Figure 2-1 Copying the original 5.x repository
Before You Start
31
2. Upgrade the duplicate repository to version 6.x.
Cluster 1 - 2.x
5.x repository
Cluster 2 - 2.x
Upgrade to 6.x
Cluster 3 - 2.x
Figure 2-2 Upgrading the duplicate repository to 6.x
3. Upgrade one cluster to version 6.x, or build a new 6.x cluster.
Upgrade methods
32
4. Connect this cluster to the 6.x repository. This becomes the test environment.
Cluster 1 - 2.x Production
5.x repository
6.x repository
Cluster 3 - 6.x
Test
Figure 2-3 Connecting the test cluster to the repository
5. 6. 7. 8.
Verify that the test environment functions properly. Disable access to the Business Objects system for all users. Upgrade all remaining clusters to 6.x. Upgrade the original 5.x production repository to 6.x.
Before You Start
33
9. Reconnect the upgraded original repository to all the clusters.
6.x repository
Figure 2-4 Reconnecting the original repository
Gradual method
This solution is more suitable for larger deployments, where it might be impractical or impossible to shut down the entire Business Objects system while the final production upgrade takes place. By gradually installing version 6.x alongside the previous version, you continue to use the two systems as long as necessary, switching over gradually according to a well-defined plan. You must use InfoView version 5.1 SP5 or later in this scenario. Certain changes were introduced in SP5 to enhance its compatibility with a 6.x repository.
Upgrade methods
34
The basic procedure is as follows:

REMINDER This is a summary of the Gradual method. For detailed, step-by-step operating instructions, see Chapter 4.
1. Back up the version 5.x repository. 2. Disconnect the clusters from the repository and disable access to the Business Objects system for all users. 3. Upgrade the repository to version 6.x. This new 6.x repository will be used for all clusters.
Repository upgraded to 6.x
Figure 2-5 Upgrading the repository to 6.x
4. Reconnect clusters and users to the upgraded repository.
Before You Start
35
5. Upgrade clusters and users to 6.x products, one cluster at a time.
6.x repository
Figure 2-6 Upgrading clusters one at a time
Upgrade methods
36
Test systems
Although it is preferable to upgrade your system as fast as possible, Business Objects recommends that you do not complete the upgrade before testing the changes that you made. If you use the Split method (double repository), in effect you are already creating a test system. You dont switch over to production until you verify that version 6.x is functioning correctly on a portion of your Business Objects system. With the Gradual method (single repository), be careful not to move users too quickly into the new production systemwithout adequate verification. To prevent problems from occurring, you can do either of the following: Start with a simple, small cluster. Verify that everything is functioning properly before proceeding to the rest of your system. Create a real test system before beginning the gradual upgrade of your production system.
Before You Start
37
Time-frame for upgrading

A number of factors can impact the amount of time needed for the upgrade. In particular, the complexity of the Business Objects environment and the general operating environment can have a substantial effect. The following factors may increase the time needed for upgrading: complexity of version 2.x WebIntelligence (.wqy) documents For example, how many joins do the objects contain? If the objects used by WebIntelligence documents contain multiple joins, they take longer to convert to version 6.x. If a refreshed document contains objects that are linked by either multiple joins or an unoptimized join structure, the upgrade could take longer than if the join structure was optimizedfor example, using shortcut joins. This can be a problem if there is a lot of data to return. For more information, see Designing a Schema in the Designers Guide. In addition, cells set to automatic size (default in 2.x) can increase the time needed for upgrading. If you are migrating many documents with numerous cells set to automatic size, consider doing one or both of the following: - Perform the migration at a time when server use is low - Modify the cell settings from automatic size to a fixed size For details, see Cells set to automatic size on page 284. number of users All else being equal, a large number of users increases upgrading time. Some of this depends on the mix between WebIntelligence and BusinessObjects users. More time is needed for the upgrading of BusinessObjects users. user settings If 2.x/5.x user settings need to be transferred to 6.x, it takes longer than if you accept the default settings in 6.x. number of clusters in the Business Objects deployment middleware/database configuration Certain changes in supported systems were introduced in version 6.x. You may need to switch databases or make changes to your middleware. Check Supported operating systems and platforms on page 40 to see what the impact would be on your upgrade. number and type of server and client platforms that need to be modified before you start the upgrade of the Business Objects system
Time-frame for upgrading
38
customized applications For example, WebIntelligence in a fully-customized JSP environment can be time-consuming because JSP pages must be recreated. application server/web server These may need to be added or upgraded. corporate directory If you are migrating users to an LDAP-based corporate directory, you need to make changes in your Business Objects system. (Business Objects version 6.1 or later; see LDAP directories on page 24.)
Before You Start
39
Repositories
The version 6.x repository is virtually unchanged compared to 5.x. There are very few new columns and no new tables, only new types of data (such as document types). This means that most 2.x/5.x applications and a 2.x cluster (v. 2.6 or later) can function with a 6.x repository. The reverse, however, is not true: Version 6.x applications and a 6.x cluster cannot function with a 5.x repository. A version 6.x Supervisor and a 5.x Supervisor can function on the same machine. However, 6.x Supervisor cannot function with a 5.x repository, and 5.x Supervisor cannot function with a 6.x repository. You need to check that your middleware and RDBMS are supported by version 6.x. (See Supported operating systems and platforms on page 40.)
Repositories
40
Supported operating systems and platforms

Business Objects recommends that you check the latest information on supported platforms before you start to upgrade your Business Objects system. For the full list of currently supported platforms and products, consult your Business Objects representative, or check the latest PAR (Product Availability Report). As of this writing, the PAR can be accessed at the following URL: http://www.techsupport.businessobjects.com To access this site, you must be registered for Business Objects online customer support. Business Objects recommends that you check this information whenever you make a change in your system.
Before You Start
41
Compatibility
This section discusses the compatibility between components of your previous and new Business Objects systems. You can find additional information on compatibility for specific products in the product chapters (Part III of this guide, beginning on page 199).
Administration Console
Can a ... 6.x Administration Console 2.x Administration Console Yes No Function on a ... 6.x cluster 2.x cluster No Yes
Broadcast Agent
Can ... 6.x Broadcast Agent Scheduler 5.x Broadcast Agent Scheduler
Process jobs scheduled in a ... 6.x application Yes No, not if they are 6.x documents 5.x application Yes (2.x/5.x documents keep 2.x/5.x format) Yes
Compatibility
42
Can a ... 6.x Broadcast Agent Console 5.x Broadcast Agent Console Yes Yes
Connect to a ... 6.x repository 5.x repository Yes Yes
A 2.x/5.x and a 6.x Scheduler can function together on the same repository.
Document exchange
In the tables below, retrieve includes from all sources: repository, mail, and file system. IMPORTANT: Version 6.x documents cannot be opened in 2.x/5.x.
Can ...
Do the following with 6.x documents: Retrieve Send or save as corporate Yes No
6.x users 2.x/5.x users
Yes No
Can ...
Do the following with 2.x WebIntelligence documents: Retrieve Send or save as corporate Yes Yes
Yes Yes
Before You Start
43
Can ...
Do the following with 5.x BusinessObjects documents: Retrieve Send Yes Save as corporate No
6.x InfoView users 6.x BusinessObjects users 2.x InfoView users 5.x BusinessObjects users
Yes Yes
Yes, but document Yes, but document becomes 6.x becomes 6.x Yes Yes Yes Yes
Yes Yes
When ... a 2.x WebIntelligence document in InfoView... 6.x users 2.x/5.x users it remains 2.x it remains 2.x
Refresh ... a 5.x BusinessObjects document in BusinessObjects... it remains 6.x it remains 5.x a 5.x BusinessObjects document in InfoView... it remains 5.x it remains 5.x
When ...
Edit ... a 2.x WebIntelligence document... a 5.x BusinessObjects document... it becomes 6.x it remains 5.x
it becomes 6.x it remains 2.x
Compatibility
44
BusinessObjects in 3-tier mode
Can ... 6.x BusinessObjects (3-tier mode) 5.x BusinessObjects (3-tier mode) Yes No
Be started on ... 6.x InfoView 5.x InfoView No Yes
Repository
Can ... 6.x Supervisor 5.x Supervisor 6.x Designer 5.x Designer 6.x BusinessObjects 5.x BusinessObjects Yes No Yes No Yes Yes Function on a ... 6.x repository 5.x repository No Yes No Yes No Yes
A 6.x Supervisor and a 5.x Supervisor can function on the same machine. The same is true for Designer and BusinessObjects.
Can a ... 6.x document 2.x/5.x document Yes Yes
Be stored in a ... 6.x repository 5.x repository No Yes
Before You Start
45
Universes
Can a ...
Be used ... in 6.x Designer and by 6.x users in 5.x Designer and by 2.x/5.x users Yes Yes
6.x universe 2.x/5.x universe
Yes Yes
Compatibility
46
Upgrade issues in international deployments

When you upgrade to version 6.x products, consider a number of changes that are important for international deployments. In BusinessObjects, you can now switch the language of the user interface without having to restart your machine. You must have the necessary languages installed. (For more information, see the BusinessObjects Users Guide.) You can do this only between languages that have the same encoding. This means that: you can switch from one Western European language to another if you have a Japanese operating system, you can switch between Japanese and English You switch the language of the user interface in BusinessObjects via Tools > Options > General > Language. In Business Objects products, when you create a document, universe, user name, and so on, you can use only a single charset, regardless of the user interface language. This charset must be supported by your repository database. Language and country information for documents is now stored in the document itself. This prevents incorrect display when a document is shared by users with different language formats. If you are accessing a Unicode database, you must set the middleware to the charset corresponding to the language data you want to display.
Multilingual user interface (InfoView)

Starting with version 6.1, InfoView users can set their own default (or preferred) language from among the languages installed on the server. This is done on the Display tab of the InfoView Options Pages. This feature applies to the following languages: English French German Italian Dutch Spanish
Before You Start
47
Supported languages
Supported languages are divided into full localization and customized localization. No new full-localization languages are supported in version 6.x. Portuguese (Brazil) is no longer supported. Customized localization languages are not automatically available in version 6.x. They are requested on a case-by-case basis. Consult your Business Objects representative or check the latest Product Availability Report (PAR) to find out when a customized localization becomes available. As of this writing, the PAR can be accessed at the following URL: http://www.techsupport.businessobjects.com To access this site, you must be registered for Business Objects online customer support.
Upgrade issues in international deployments
48
Checklist
Did you... Choose your upgrade method? Consider creating a test system? Evaluate factors that have an impact on the time needed for upgrading? Check your repository and middleware? Review supported platforms and operating systems? Review compatibility? Read about upgrade issues in international deployments?
Before You Start
Upgrade Workflows and Scenarios
part
Generic Workflow: Split Method
chapter
52
Overview
Chapter 2 (Before You Start) explained what you need to know and do before you start upgrading. In this chapter, we describe the actual upgrade procedures for the Split upgrade method. In the Split method, you build a test environment with a dedicated repository, alongside your production environment. The system is split into two environments. When version 6.x operates satisfactorily on the test environment, you shut down the Business Objects system and upgrade all production machines at the same time. Versions 2.x/5.x and 6.x never function simultaneously on the same repository. To upgrade using the Split method, follow the instructions in this chapter and in subsequent chapters: This chapter provides the basic procedures you need to follow for upgrading all systems. This is called the generic workflow. Then, there are a number of scenarios that correspond to various types of deployment. These scenarios explain what you need to doin addition to the generic workflowin various specific deployments. Scenarios are contained in chapters 5-12, one scenario per chapter. The generic workflow for the Split method is divided into the following phases: Phase 1 Modify the platforms Phase 2 Copy and upgrade the repository Phase 3 Upgrade desktop products (test environment) Phase 4 Upgrade the clusters (test environment) Phase 5 Upgrade production system Phase 6 Upgrade the original repository and reconnect clusters Phase 7 Test functionality and scalability Phase 8 Check the scenarios
NOTE
You also have the option of continuing to use the test environment as the new 6.x production environmentand then use your remaining 2.x/5.x machines for another purpose. In this case, you would skip Phases 5 and 6. The procedures in this chapter, however, assume that the entire original production environment will be upgraded after the test environment is validated.
53
To help you follow the order of the phases, you will see the following diagram at the start of each phase:
Business Objects recommends that you implement the phases in this order. At the end of the chapter is a checklist that helps you verify that all necessary procedures are complete.
54
Phase 1 Modify the platforms
If necessary, upgrade your platforms to products and versions that are supported by version 6.x. (See Supported operating systems and platforms on page 40.) For example: BEA WebLogic v. 5.x to 6.x Windows NT4 SP6 Workstation to Windows XP Solaris 7 to Solaris 8 You may also want to take advantage of the upgrade occasion to: improve the deployment of your Business Objects system upgrade other software not connected to Business Objects
55
Phase 2 Copy and upgrade the repository
In this phase, you copy the repository. You then upgrade the duplicate repository, and use it for the test environment. The original 5.x repository continues to function as part of the production environment. This phase includes the following steps: 1. Back up the repository. 2. Suspend all Broadcast Agent jobs. 3. Copy the repository. 4. Install Supervisor version 6.x. 5. Create a new key file (Windows). 6. Upgrade the duplicate repository.
Back up the repository

To ensure the security of your data, back up the repository before beginning the procedures below.
Suspend all Broadcast Agent jobs

Set all current jobs in declared Broadcast Agents to Suspended status. If this is not done, jobs may be lost during the upgrade process. You reset the jobs to Normal status after you upgrade the clusters.
Copy the repository and install Supervisor version 6.x

Copy the repository. Make sure you copy the security, document, and universe domains. Then install Supervisor version 6.x on a Windows machine.
56
A version 6.x Supervisor and a 5.x Supervisor can function on the same machine. However, 6.x Supervisor cannot function with a 5.x repository, and 5.x Supervisor cannot function with a 6.x repository.
Create a new key file (Windows)

Create a new key file for version 6.x.
NOTE
For UNIX, you create the key file near the end of the upgrade process (See Create a new key file (UNIX) on page 72). To create a new key file: 1. Launch Supervisor. 2. In the User Identification login box, click Admin. The Administration Setup wizard appears. 3. Click Begin. The Choose Setup Configuration page appears.
Figure 3-1 Choose Setup Configuration page
4. Select Run a safe recovery, and then click Next.
57
5. On the Define the Repository Connection page, select the network layer, and then click Setup. 6. In the dialog box that appears, verify that the Login tab is selected. Then: - Enter a user name and password for access to the database in which the repositorys security domain was copied. - Select a data source or enter the path name of the database. - Select the physical location in which the key file will be created. The option you select determines how the file is distributed to Business Objects users. This can be either: - in the default shared folder on the network, shData - in $INSTALLDIR\locData, so that each user has a local copy A message appears confirming that the key file was created. 7. Quit the wizard.
Upgrade the duplicate repository

Upgrade the duplicate repository that you created earlier in this phase. This upgraded repository will be used for the test environment. To upgrade the duplicate repository: 1. Log into the version 6.x Supervisor as a general supervisor. When Supervisor opens, it automatically detects the version 5.x repository and asks whether you want to upgrade the repository to 6.x. 2. Click Yes. Keep in mind that: - version 6.x Supervisor does not support any repository earlier than 6.x - after the repository is upgraded to version 6.x, it will not function with a Supervisor earlier than 6.x. 3. Redefine the connections to the document and universe domains. (For more information on repository and Supervisor compatibility, see Compatibility on page 41.) Compatibility of database connections Version 6.x can view, modify, and save any connection (personal, shared, or secured) created with 5.x. Version 2.x/5.x can open, use, modify, and save a connection created by 6.x.
58
Phase 3 Upgrade desktop products (test environment)
You now create a test environment. In this phase and the next, you are creating a test cluster that will be connected to the repository you copied and upgraded in Phase 2. You can build a new 6.x cluster, but the instructions below assume that you are updating a portion of your existing 2.x/5.x system. This phase includes the following steps: reinstall version 6.x desktop products and certain administration products upgrade BusinessObjects documents
Reinstall desktop and administration products

Version 6.x desktop products include: BusinessObjects BusinessQuery for Excel In addition, some 6.x administration products are related to the desktop side of the Business Objects system. These include: Designer Supervisor (already installed in previous phase) Administration Console (web applet or standalone application) Configuration Tool
NOTE
WebIntelligence version 2.x must be uninstalled before installing version 6.x desktop and administration products.
59
To reinstall: 1. Verify that the version 6.x license file is installed. (For more information, see Licenses in the Installation and Configuration guide.) 2. Run the version 6.x Installation wizard. When the wizard detects an earlier version of desktop products, you are prompted to upgrade.
Figure 3-2 Installation wizard
3. To begin the process, select Upgrade your existing release to the new one, and then click Next.
NOTE
If the 5.x setup.exe file was not installed, it is not detected by the wizard, and an error message appears. If this occurs, use the version 5.x installation CD to install the 5.x setup.exe file, and then rerun the 6.x installation.
60
Administration Console When you upgrade the version 2.x Services Administrator to the 6.x Administration Console, keep in mind that: a version 2.x Services Administrator cannot function on a 6.x cluster a version 6.x Administration Console cannot function on a 2.x cluster When you open the new Administration Console, you will see different modules than in version 2.x. These no longer exist in version 6.x: - WIGenerator - WIHSALManager These are new in version 6.x: - Administration server - WILoginServer - WIQT - WIReportServer Administrative installation The installation of desktop products on the client machine, via a server, is called an administrative installation (previously called a master setup/standalone). If you set up the administrative installation using command-line mode, you can: enable users to upgrade via a shared network location prompt users to upgrade when they log in For detailed instructions on administrative installations, see the Installation and
Configuration guide.
Upgrade BusinessObjects documents

You upgrade version 5.x BusinessObjects documents to 6.x simply by opening them in a 6.x product, and then saving the documents. The upgraded document keeps the same type and extension. Only the version number changes. Documents earlier than version 5.x cannot be upgraded from within version 6.x. You must first upgrade them to 5.x from within a 5.x application. Be careful if you have BusinessObjects or BusinessQuery 5.x and 6.x products in the same system: after a document is upgraded to version 6.x, it cannot be reopened by BusinessObjects 5.x.
61
For more information on compatibility between different versions of documents, see Document exchange on page 42. Business Objects recommends that you test documents after they have been upgraded. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x.
REMINDER Version 6.x documents cannot be opened in 2.x/5.x.
62
Phase 4 Upgrade clusters (test environment)
You now continue to create the test environment. In this phase and the previous one, you are creating a test cluster that will be connected to the duplicate repository you upgraded in Phase 2. This section covers upgrading of clusters, which includes the upgrading of server products. This phase includes the following steps: 1. Shut down your Business Objects system. 2. Copy user and system information. 3. Uninstall/reinstall server products. 4. Resubmit user and system information. 5. Create a new key file (UNIX). 6. Reactivate Broadcast Agent jobs. 7. Restart the servers. 8. Upgrade WebIntelligence documents. 9. Verify the test environment. On Windows, you cannot have version 2.x and 6.x machines functioning together on the same cluster. On UNIX, you can have 2.x and 6.x functioning on the same machine, if the two versions do not share web servers or directories. (See the Installation and Configuration guide.)
63
Shut down the Business Objects system

1. Disable access to the Business Objects system for all users. (See the System Administrators Guide.) 2. Shut down the Business Objects system on the primary and secondary nodes (called, in version 2.x, the cluster manager and cluster nodes).
Copy user and system information

There are two types of information that you need to copy from 2.x/5.x, and then resubmit to the upgraded version 6.x Business Objects system: User information - Default settings for new 6.x users - User information contained in the Storage directory System information Most user and system information is automatically transferred from 2.x/5.x to 6.x when you uninstall and reinstall the server products. However, you need to manually copy certain files and resubmit them later. This is described below. Windows Default settings for new users Any changes made to a 2.x clusters default settings for new users are stored in a global profile.txt file. If you changed these settings, Business Objects recommends that you manually copy the file (you will resubmit the file after reinstalling the 6.x server products). Otherwise, new users will see the standard 6.x default settings when they log into 6.x InfoView for the first time. Copy the 2.x/5.x global profile.txt file from: $INSTALLDIR\Server\WebIntelligence 2.5\Config If you stored the file on an external disk, you must copy it from that location. User information in the Storage directory You must copy and resubmit a number of files containing additional 2.x/5.x user information. These files are stored at the cluster level, in the machine hosting the WIStorageManager. Back up the entire Storage directory: $INSTALLDIR\Server\WebIntelligence 2.5\Storage
64
System information Business Objects recommends that you back up the following system information files: Files in the Config folder: $INSTALLDIR\Server\WebIntelligence 2.5\Config Files in the Broadcast Agent folder, including Ini and Log files: $INSTALLDIR\Server\Broadcast Agent 5.0 BOManager folder information, include Ini files: $INSTALLDIR\Server\BusinessObjects Manager 5.0 Other module parameters, such as WIDispatcher You can access these module parameters in the version 2.x Services Administrator by clicking the Global Report button.
Figure 3-3 Global Report button
This generates an HTML report containing the parameters.
65
UNIX On UNIX, you need to back up and transfer the storage and configuration files to the 6.x Business Objects system. Storage files Storage files include the profile.txt file, which contains some of the clusters global default settings for user information. If this file is not transferred, users will see the standard 6.x default settings when they log into 6.x InfoView for the first time. Back up the 2.x storage files, located in the $WISTORAGEDIR directory. Configuration files To back up the configuration files: 1. Back up the following: $INSTALLDIR/Server/WebIntelligence/widispatch/config $INSTALLDIR/Server/WebIntelligence/wisession/config $INSTALLDIR/Server/WebIntelligence/wistorage/config $INSTALLDIR/Server/WebIntelligence/wiapi/apiconfig $INSTALLDIR/Server/BOManager/bin/BOManager.ini $INSTALLDIR/Server/BroadcastServer/bin/BcsScdul.ini 2. Make note of the values of the QT_MAX_ACTIVE_TIME and QT_MAX_INACTIVE_TIME parameters, located in 2.x in: $INSTALLDIR/Server/WebIntelligence/wigenerator/config
Uninstall/reinstall server products

You must uninstall and reinstall server products. Server products in version 6.x include: Business Objects server InfoView WebIntelligence BusinessObjects Web Installer Broadcast Agent Business Objects recommends that you test the server products on a single user before deploying them to the entire pool of test users. Have the single user test: personal and inbox documents corporate documents all universes
66
If you are satisfied with the results of this mini-test, enable the system for all users in the test group. Windows To uninstall and reinstall server products: 1. Shut down all Business Objects servers. 2. Uninstall all previous versions of Business Objects products from all machines in the cluster. To uninstall an earlier version of server products, use the Setup utility of that version. You can launch the Setup utility for the earlier version via the Windows Start menu (Programs > WebIntelligence 2.x > Setup). Make sure you also uninstall any Business Objects components located on machines hosting application servers or web servers. 3. Restart all machines from which previous versions were uninstalled. 4. Install and configure the 6.x primary node on a machine with no previous versions of either server or desktop products. (Server products and BusinessObjects are not supported on the same server machine.) 5. Test the 6.x repository connection to verify that you can access documents. 6. Test the InfoView 6.x Inbox and Personal Documents lists to verify that you can access these files. 7. On each version 2.x cluster node: - Shut down the Business Objects system. - Uninstall 2.x server products. - Restart the machine. - Restart the server on the primary node. - Install 6.x server products. - Restart the machine again. Use the same OSAgent Port value you used when installing the primary node.
67
UNIX Keep in mind the following when you upgrade the cluster on UNIX: The installer cannot automatically upgrade from version 2.x/5.x; you must do this manually. It is not possible to automatically detect a version that is already installed. To install version 6.x server products: 1. On the machine hosting the web server, stop WebIntelligence and the web server. 2. Start the web server and application server that you will use with version 6.x. 3. Install version 6.x server products. 4. Link the following 2.x and 6.x directories (you do this with the Configuration Tool):
2.x directory $WIDATADIR/Config $WIDATADIR/ Universe
6.x directory $INSTALLDIR/nodes/<hostname>/ <clustername>/config $INSTALLDIR/nodes/<hostname>/ <clustername>/universe
Broadcast Agent After the upgrade to Broadcast Agent version 6.x, previously scheduled jobs are recovered and reprocessed by the new Scheduler. If the task is based on a WebIntelligence document or a BusinessObjects document, the document is kept in 2.x/5.x format. Therefore, 2.x/5.x users can still open, edit, and save them. If a 2.x/5.x corporate document is edited (and thus upgraded) and saved as a corporate document in a 6.x Business Objects product (such as BusinessObjects), all previous scheduling information is lost, and 2.x/5.x users can no longer work on it. There are only minor changes between version 5.x and 6.x Broadcast Agent Consoles. A version 6.x Console can connect to a 5.x repository and a 2.x cluster. A version 5.x Console can connect to a 6.x repository with a 2.x cluster, but it cannot display the document type for 6.x tasks. (For more information on upgrading Broadcast Agent, see Broadcast Agent on page 207.)
68
Resubmit user and system information

You must now resubmit the user and system information that you copied earlier (see Copy user and system information on page 63.) Windows To resubmit the global profile.txt file: 1. Paste the file into the following 6.x directory: $INSTALLDIR\bin\config 2. Log into InfoView as a general supervisor. 3. Click Options, and then click the About tab.
Figure 3-4 Set my options as Server Defaults
4. Click OK next to Set my options as Server Defaults. You may also want to set other 6.x global default options at this time; for example, in My InfoView. Individual settings for transition users When users modify their personal settings in InfoView, the new profile is stored in an individual profile.txt file that is separate for each user. This is not the same as the global profile.txt file discussed above. In order for users making the transition from 2.x/5.x to 6.x to preserve their personal user settings, these files are transferred to the 6.x Business Objects system. This is done automatically by the system, but Business Objects recommends that you verify that it was completed. In version 6.x, the individual profile.txt files are in: $INSTALLDIR\nodes\<hostname>\<clustername>\storage\user\<username> If necessary, you can manually transfer the files, or use the Configuration Tool.
69
To manually transfer the individual profile.txt files: 1. Copy each 2.x/5.x profile.txt file from the storage directory that you backed up: $INSTALLDIR\Server\WebIntelligence 2.5\Storage\user\<username> 2. Paste the file into the 6.x folders for each user in the machine hosting WIStorageManager: $INSTALLDIR\nodes\<hostname>\<clustername>\storage\ user\<username> To transfer the files using the Configuration Tool: 1. On the Cluster Management page of the Configuration Tool, highlight Cluster Preferences, select Update Cluster Preferences, and then click Next.
Figure 3-5 Cluster Management page
The Choose location for Business Objects files and directories page appears. 2. Enter the path you want for the storage directory or accept the default ($INSTALLDIR\nodes\<hostname>\<clustername>\storage).
70
NOTE
When transition users log out of InfoView 6.x for the first time, they are prompted to save their individual settings (if they did not already click Save on the Options page). This completes the transfer of individual user settings. User information in the Storage directory You must resubmit a number of files containing additional 2.x/5.x user information. You can find these files in the Storage directory that you backed up earlier. Note that these files are unique to each user. Copy the following files: $INSTALLDIR\Server\WebIntelligence 2.5\storage\list\<username>\mail.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\list\<username>\unv.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\mail\<username>\read.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\user\<username>\attribut.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\user\<username>\*.ctg Paste the files (in 6.x) into parallel folders at: $INSTALLDIR\nodes\<hostname>\<clustername>\storage
EXAMPLE The first file listed above, mail.txtfor the user named <biguser>would be pasted into the following location in 6.x:
$INSTALLDIR\nodes\<hostname>\<clustername>\storage\list\biguser\mail.txt UNIX Storage files There are two ways to transfer the storage files to 6.x: Copy the files that you backed up earlier into the 6.x $STORAGEDIR directory. or Use the Configuration Tool.
71
To transfer the storage files using the Configuration Tool: 1. On the Cluster Management page of the Configuration Tool, highlight Cluster Preferences, select Update Cluster Preferences, and then click Next.
The Choose location for Business Objects files and directories page appears. 2. Enter the path you want for the Storage directory or accept the default ($INSTALLDIR/nodes/<hostname>/<clustername>/storage).
72
Configuration files To transfer the configuration files, which you backed up earlier, to the 6.x system: 1. Copy the files into the 6.x directory and rename them: $INSTALLDIR/<hostname>/<clustername>/config/servers 2. Reset the values you noted when you backed up the files. They have been renamed in 6.x to MsgAdminMaxActiveTime and MsgAdminMaxInactiveTime, located in $INSTALLDIR/nodes/<hostname>/<clustername>/config/ servers/wiqt.cfg
Create a new key file (UNIX)

REMINDER The key file for Windows is created near the beginning of the upgrade process, when the repository is upgraded. (see Create a new key file (Windows) on page 56.)
To create a new key file: 1. Edit the MyWebiEnv.sh file to set up a connection to the database. If you are using the same connectivity in versions 2.x and 6.x, you can retrieve the 2.x settings. In 2.x, the MyWebiEnv.sh file is located in: - WebIntelligence v. 2.6 SP2 or later: $WIDATA/Config/ - earlier versions of 2.x: $WI/SetUp In 6.x, the file is located in $INSTALLDIR/nodes/<hostname>/ <clustername> 2. Run the $INSTALLDIR/setup/wmainkey script. This checks the connection and upgrades the bomain.key file. You can also create it in Windows, and then copy it into: $INSTALLDIR/nodes/<hostname>/<clustername>/locdata/
Reactivate Broadcast Agent jobs

Reactivate (set to Normal status) all Broadcast Agent jobs that you suspended before upgrading the repository. Then, verify that Broadcast Agents are being monitored in the Administration Console.
73
Restart the servers

On the test-environment cluster that you upgraded, restart the servers and have the users log in.
Upgrade WebIntelligence documents

You upgrade WebIntelligence 2.x documents (.wqy) to version 6.x (.wid) by editing them in InfoView version 6.x, and then saving them as a personal or corporate document.
NOTE
Upgrade of WebIntelligence 2.x documents is supported only for version 2.5 or later. Earlier version 2.x documents can only be viewed in 6.x, but not upgraded. To upgrade WebIntelligence documents: 1. Open the WebIntelligence 2.x document in InfoView version 6.x. 2. Click Edit. 3. Make any modifications you want (optional). 4. Save the document as a personal or corporate document. The extension is changed from .wqy to .wid. That is, the document is upgraded to version 6.x. Note that the former 2.x (.wqy) document remains in the repository. It will be accessible to all users on the cluster, but will appear with a different icon than the 6.x document with the same name. If you want to eliminate such documents, you must delete them manually. After you upgrade to version 6.x, users see in InfoView the same documents they previously had the right to view (in the Personal Documents, Corporate Documents, Inbox Documents, and Scheduled Documents lists).
REMINDER WebIntelligence 6.x (.wid) documents cannot be opened in InfoView 5.x. (For more information on compatibility between different versions of documents, see Document
exchange on page 42).
74
Cells set to automatic size By default, table cells set to automatic size in WebIntelligence 2.x are set to AutoFit in version 6.x. WebIntelligence documents with many cells set to automatic size may take a long time to open in InfoView 6.x. Therefore, migrating these documents could be time-consuming. If you are migrating many such documents, consider doing one or both of the following: Perform the migration at a time when server use is minimal. Before migrating the documents, change the cell settings from automatic size to a fixed size. For details, see Cells set to automatic size on page 284.
Verify the test environment

Verify the test environment before upgrading all the machines in your Business Objects system (Phase 5). In this way, any problems can be fixed before you upgrade machines within the production environment.
REMINDER After the upgrade of the production environment is complete, you will perform more thorough tests to verify functionality and scalability. (See Phase 7 Test functionality and scalability on page 79.)
Business Objects recommends that you verify that users can: connect to InfoView import and export documents create and modify documents access their personal and inbox documents access personal and corporate categories In addition, verify that: Broadcast Agent functions properly security has been properly upgraded
75
Phase 5 Upgrade production system
In this phase, you repeat phases 3 and 4, but this time you do it for all the machines in your Business Objects production system. This includes: Upgrading desktop products Upgrading the clusters After all the machines are upgraded, you upgrade the original repository and then reconnect it to the upgraded clusters (Phase 6).
Shut down the Audit facility

The Audit facility tracks crucial information on user and system activity (see The Audit Facility and Auditor on page 201). To ensure a smooth upgrade of the facility, shut it down before upgrading any Business Objects products in your production system to version 6.x.
Phase 5 Upgrade production system
76
To shut down the Audit facility: 1. Open the version 2.x Services Administrator. 2. Click View Log. The User Activity Log page appears.
Figure 3-7 User Activity Log page
3. Set the User Activity Log to Off. 4. Click Apply.
77
Phase 6 Upgrade original repository and reconnect clusters
Follow the same procedures as in Phase 2 (Copy and upgrade the repository), but this time for the original repository that you are using for your production environment. Connect the clusters to the repository.
Upgrade audit database

After the repository is connected, you upgrade the audit database. To upgrade the audit database to 6.x: 1. Open the version 6.x Administration Console. 2. Click Audit. The User Activity Log page appears.
Phase 6 Upgrade original repository and reconnect clusters
78
3. At Log to Database, click On.
Figure 3-8 Log to database
A login dialog box appears. 4. Enter a supervisor-level user name and password. 5. On the User Activity Log page, click Apply. If there is already an audit database, it is upgraded to version 6.x. If there is none, a new 6.x audit database is created.
79
Phase 7 Test functionality and scalability
After you complete the upgrading of product software and documents, try using the new features in the latest version. If you encounter any difficulties, see Frequently Asked Questions on page 319. For a complete description of these features, see Whats New in this Release on the documentation website. You can access the site by doing any of the following: Choosing More Tips and Samples from the Help menu in version 6.x desktop products Clicking the More Tips and Samples link in the InfoView 6.x navigation bar Going to the website: http://www.techsupport.businessobjects.com
Test desktop and administration products

Confirm that you can open and use the basic functionality of the new desktop and administration products: BusinessObjects BusinessQuery for Excel Designer Supervisor Auditor Administration Console
80
Test server products

Confirm that you can connect and use the basic functionality of the new server products: WebIntelligence InfoView Broadcast Agent InfoView Check that: the browser configuration indicator in InfoView (accessed from the Login page) functions properly users can log in users can access applications as per their security profiles user options function correctly Documents After you upgrade InfoView to 6.x, users see the same documents they previously had the right to view (in the Personal Documents, Corporate Documents, Inbox, and Scheduled Documents folders). Confirm this for several users. Upgrade several documents from 2.x/5.x to 6.x. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x. Create a number of new version 6.x BusinessObjects and WebIntelligence documents. Then try: editing refreshing viewing saving as personal document saving as corporate document sending Broadcast Agent Verify the following Broadcast Agent functionality: documents sent by Broadcast Agent before the upgrade are still in users inboxes previously scheduled documents are still listed and scheduled new tasks are properly started and executed
81
Resubmit to Broadcast Agent all corporate documents that are viewed through InfoView. Verify that one of the Faster Document Viewing over the Web options is checked. This prefills the cache. The first time you try to view one of these documents in InfoView, BOManager generates the presentation, and then stores it in a cache on WIStorageManager. When other InfoView users subsequently access the document, instead of having to recontact BOManager and regenerate the file in the requested format, they access the pregenerated file in the cache.
Create and apply categories

Create and test hierarchical categories, a new feature in version 6.x (see the InfoView Users Guide). Confirm that category management is prohibited to all users except General Supervisors. Assign the right for category management to a test user before assigning it to all the users and user groups you want to give it to. Apply categories to both BusinessObjects and WebIntelligence documents.
User settings
Confirm that user settings were properly transferred to the version 6.x system. Select several users, and make sure that they still have the same settings as before the upgrade.
Delete 2.x directories (UNIX)

On UNIX, version 2.x and 6.x server products can function together on the same machine. Nevertheless, Business Objects recommends that you eventually delete the 2.x directories from your UNIX server. You can do this after the new system has been functioning well for at least several weeks.
82
Phase 8 Check the scenarios
This chapter describes the generic workflow needed for every upgrade procedure using the Split method. Chapters 5-12 explain what you may need to do, additionally, in various specific deployments. These individualized instructions are organized into scenarios. Each chapter contains a different scenario. Below are two tables summarizing the scenarios, to help you choose the one that best fits your own deployment. Note that each scenario uses either the Gradual or Split upgrade method. Operating systems are Windows unless stated otherwise. When a given step is a generic procedure, the text refers back to the Generic Workflow chapters (3 and 4) for the full explanation. Only the procedures that differ from the generic will be fully explained within the scenario.
Summary of the scenarios

The tables below provide the following information about each scenario: Split or Gradual upgrade method Whether the cluster is based on UNIX or Windows The existing deployment Special components, such as an application server or Broadcast Agent Note that all the existing deployments contain BusinessObjects (either desktop or 3-tier mode), WebIntelligence, and a web server. The scenarios are models that represent larger deployments. You will see, for example, scenarios with only one or two client machines. This is done to facilitate a clear explanation; in your own deployment, there will almost certainly be multiple machines of this type.
83
Gradual
Basic web deployment Basic web deployment with application server (JSP) Basic web deployment with application server (ASP) Basic web deployment with Broadcast Agent Application server with Broadcast Agent/UNIX Application server with Broadcast Agent/Windows Basic web deployment with Auditor Basic web deployment with ASP and BusinessObjects (3-tier mode)
Auditor
Scenario Split
BusinessObjects (3-tier mode)
Application server (ASP)
Application server (JSP)
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
84
Scenario
Existing deployment/Upgrade method
Starts on page...
121
Basic web deployment
Two version 2.x clusters functioning on the same repository and sharing the same storage. Each cluster contains three machines: cluster manager, cluster node, and web server. There are three client machines, two for users and one for the administrator. There is no Broadcast Agent in the system, and no desktop products on the client user machines. The Gradual upgrade method is used. One version 2.x cluster with an application server. The cluster contains four machines: cluster manager, cluster node, application server, and web server. There are two client machines, one for users and one for the administrator. There is no Broadcast Agent in the system, and no desktop products on the client user machine. The Gradual upgrade method is used. Two version 2.x clusters functioning on the same repository and sharing the same storage. Each cluster contains four machines: cluster manager, cluster node, web server, and application server. The application server contains Active Server Pages (ASP) and Broadcast Agent Publisher. There are three client machines, two for users and one for the administrator. There are no desktop products on the client user machines. The Gradual upgrade method is used. One version 2.x cluster. The cluster contains three machines: cluster manager, cluster node, and web server. There are two client machines, one for users and one for the administrator. Broadcast Agent is functioning. There are no desktop products on the client user machine. The Split upgrade method is used.
Basic web deployment with application server (JSP)
131
Basic web deployment with application server (ASP)
141
Basic web deployment with Broadcast Agent
151
Application server One version 2.x cluster with an application server, on UNIX. The cluster contains one machine, the cluster manager. with Broadcast There is one client user machine and one client Agent/UNIX administrator machine. Broadcast Agent is functioning. There are no desktop products on the client user machine. The Split upgrade method is used.
161
85
Scenario
Starts on page...
169
Application server One version 2.x cluster with an application server. The cluster contains three machines: cluster manager, cluster with Broadcast node, and web server. Broadcast Agent is functioning. Agent/Windows There is one client user machine and one client administration machine. There are no desktop products on the client user machine. The Split upgrade method is used. Basic web deployment with Auditor Two version 2.x clusters sharing the same storage. One of the clusters is dedicated to Auditor. There is a functioning audit database. There is one client user and one client administration machine. The client user has BusinessObjects in 3-tier mode. The Gradual upgrade method is used. Basic web deployment with ASP and BusinessObjects (3-tier mode) Two version 2.x clusters functioning on the same repository and sharing the same storage. Each cluster contains three machines: cluster manager, cluster node, and web server/ application server. The application server contains Active Server Pages (ASP). There are three client machines, two for users and one for the administrator. There is no Broadcast Agent in the system. Client user machines have BusinessObjects in 3-tier mode. The Gradual upgrade method is used.
179
189
86
Checklist
Did you........
modify your platforms (if necessary)? back up the repository? suspend all Broadcast Agent jobs? install version 6.x Supervisor? create a new key file? upgrade the repository? uninstall and reinstall desktop and administration products? upgrade BusinessObjects documents? uninstall and reinstall server products? copy and resubmit user and system information? reactivate Broadcast Agent jobs? restart the servers? upgrade WebIntelligence documents? verify the test environment? shut down the Audit facility? upgrade the remaining clusters? upgrade the original repository? connect the repository to all clusters? upgrade the audit database? test functionality and scalability? check which upgrade scenario fits your deployment?
Generic Workflow: Gradual Method
chapter
88
Overview
Chapter 2 (Before You Start) explained what you need to know and do before you start upgrading. In this chapter, we describe the actual procedures for the Gradual upgrade method. In the Gradual method, you upgrade gradually, keeping the previous system running as long as possible until the new installation is complete or nearly complete. Two or more clusters (2.x and 6.x mixed) share a single repository. A separate test environment is not mandatory. To upgrade using the Gradual method, follow the instructions in this chapter and in subsequent chapters: This chapter provides the basic procedures you need to follow for upgrading all systems. This is called the generic workflow. Then, there are a number of scenarios that correspond to various types of deployment. These scenarios explainin addition to the generic workflow what you need to do in various specific deployments. Scenarios are contained in chapters 5-12, one scenario per chapter. The generic workflow for the Gradual method is divided into the following phases: Phase 1 Modify the platforms Phase 2 Upgrade the repository Phase 3 Upgrade desktop products Phase 4 Upgrade the clusters Phase 5 Test functionality and scalability Phase 6 Check the scenarios To help you follow the order of the phases, you will see the following graphic at the start of each phase:
89
Business Objects recommends that you implement the phases in this order. At the end of the chapter is a checklist that helps you verify that all necessary procedures are complete.
90
Phase 1 Modify the platforms
If necessary, upgrade your platforms to products and versions that are supported by version 6.x. (See Supported operating systems and platforms on page 40.) For example: BEA WebLogic v. 5.x to 6.x Windows NT4 SP6 Workstation to Windows XP Solaris 7 to Solaris 8 You may also want to take advantage of the upgrade occasion to: improve the deployment of your Business Objects system upgrade other software not connected to Business Objects
91
Phase 2 Upgrade the repository
In this phase, you upgrade the repository. The upgraded repository will be used for all machines. This phase includes the following steps: 1. Back up the repository. 2. Suspend all Broadcast Agent jobs. 3. Install Supervisor version 6.x. 4. Create a new key file (Windows). For UNIX, the key file is created near the end of the upgrade process. (see Create a new key file (UNIX) on page 109.) 5. Upgrade the repository. 6. Shut down the Audit facility.
Back up the repository

To ensure the security of your data, back up the repository. Then, log out all users.
Suspend all Broadcast Agent jobs

Set all current jobs in declared Broadcast Agents to Suspended status. If this is not done, jobs may be lost during the upgrade process. You reset the jobs to Normal status after you upgrade the clusters.
92
Install 6.x Supervisor

Install Supervisor version 6.x on a Windows machine. A 6.x Supervisor and a 5.x Supervisor can function on the same machine. However, a 6.x Supervisor cannot function with a 5.x repository, and a 5.x Supervisor cannot function with a 6.x repository.
Create a new key file (Windows)

Create a new key file for version 6.x. To create a new key file: 1. Launch Supervisor. 2. In the User Identification login box, click Admin. The Administration Setup wizard appears. 3. Click Begin. The Choose Setup Configuration page appears.
Figure 4-1 Choose Setup Configuration page
4. Select Run a safe recovery, and then click Next. 5. On the Define the Repository Connection page, select the network layer, and then click Setup.
93
6. In the dialog box that appears, confirm that the Login tab is selected. Then: - Enter a user name and password for access to the database in which the repositorys security domain was copied. - Select a data source or enter the path name of the database. - Select the physical location in which the key file will be created. The option you select determines how the file is distributed to Business Objects users. This can be either: - in the default shared folder on the network, shData - in $INSTALLDIR\locData, so that each user has a local copy. A message appears confirming that the key file was created. 7. Quit the wizard.
Upgrade the repository

All clusters, both 2.x and 6.x, will share the upgraded repository. To upgrade the repository: 1. Log into the version 6.x Supervisor as a general supervisor. When Supervisor opens, it automatically detects the version 5.x repository and asks whether you want to upgrade the repository to 6.x. 2. Click Yes. Keep in mind that: - Version 6.x Supervisor does not support any repository earlier than 6.x. - After the repository is upgraded to version 6.x, it will not function with a Supervisor earlier than 6.x. 3. Redefine the connections to the document and universe domains. Compatibility of database connections Version 6.x can view, modify, and save any connection (personal, shared, or secured) created with 5.x. Version 2.x/5.x can open, use, modify, and save a connection created by 6.x.
Reconnect users to the repository

When you reconnect users to the repository, keep in mind that: after upgrade, 2.x/5.x users no longer have the right to update corporate categories version 5.x administrative applications, such as Designer and Supervisor, cannot connect to the new 6.x repository
94
Shut down the Audit facility

The Audit facility tracks crucial information on user and system activity (see The Audit Facility and Auditor on page 201). To ensure a smooth upgrade of the facility, shut it down before upgrading any Business Objects products to version 6.x. To shut down the Audit facility: 1. Open the 2.x Services Administrator. 2. Click View Log. The User Activity Log page appears.
3. Set the User Activity Log to Off. 4. Click Apply.
95
Phase 3 Upgrade desktop products
On Windows, you cannot have version 2.x/5.x and 6.x machines functioning together on the same cluster. Gradual upgrade implies a mix of 2.x and 6.x clusters, but each cluster contains only one version. Therefore, the upgrade proceeds one cluster at a time. On UNIX, you can have 2.x and 6.x functioning on the same machine, if the two versions do not share web servers or directories. (See the Installation and Configuration guide.) After upgrading desktop/administration products and server products on the first cluster, version 5.x and 6.x products will be functioning simultaneously on your Business Objects system. In other words, there will be mix of 2.x/5.x and 6.x clusters sharing the same repository. To upgrade desktop products, you must: reinstall version 6.x desktop products and certain administration products upgrade BusinessObjects documents
Reinstall desktop and administration products

Version 6.x desktop products include: BusinessObjects BusinessQuery for Excel
96
In addition, some 6.x administration products are related to the desktop side of the Business Objects system. These include: Designer Supervisor (already installed in previous phase) Administration Console (web applet or standalone application) Configuration Tool
NOTE
WebIntelligence version 2.x must be uninstalled before installing version 6.x desktop and administration products. To reinstall: 1. Verify that the version 6.x license file is installed. (For more information, see Licenses in the Installation and Configuration guide.) 2. Run the version 6.x Installation wizard. When the wizard detects an earlier version of desktop products, you are prompted to upgrade.
Figure 4-3 Installation wizard
97
3. To begin the process, select Upgrade your existing release to the new one, and then click Next.
NOTE
If the 5.x setup.exe file was not installed, it is not detected by the wizard, and an error message appears. If this occurs, use the version 5.x installation CD to install the 5.x setup.exe file, and then rerun the 6.x installation. Administration Console When you upgrade the version 2.x Services Administrator to the 6.x Administration Console, keep in mind that: a version 2.x Services Administrator cannot function on a 6.x cluster a version 6.x Administration Console cannot function on a 2.x cluster When you open the new Administration Console, you will see different modules than in version 2.x. These no longer exist in version 6.x: - WIGenerator - WIHSALManager These are new in version 6.x: - Administration server - WILoginServer - WIQT - WIReportServer Administrative installation The installation of desktop products on the client machine, via a server, is called an administrative installation (previously called a master setup/standalone). If you set up the administrative installation using command-line mode, you can: enable users to upgrade via a shared network location prompt users to upgrade when they log in For detailed instructions on administrative installations, see the Installation and Configuration guide.
98
Upgrade BusinessObjects documents

You can upgrade version 5.x BusinessObjects documents to 6.x simply by opening them in a 6.x product, and then saving the documents. The upgraded document keeps the same type, extension, and icon. Only the version number changes. Business Objects recommends that you test documents after they are upgraded. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x. Documents earlier than version 5.x cannot be upgraded in version 6.x. You must first upgrade them to 5.x from within a 5.x application. Keep in mind that in a mixed 5.x/6.x environment, you do not have to upgrade your documents all at once. Be careful if you have BusinessObjects or BusinessQuery 5.x and 6.x products in the same system: after a document is upgraded to version 6.x, it cannot be reopened by BusinessObjects 5.x. For more information on compatibility between different versions of documents, see Document exchange on page 42.
REMINDER Version 6.x documents cannot be opened in 2.x/5.x.
99
Phase 4 Upgrade clusters
This section covers upgrading of clusters, including the upgrading of server products. This phase includes the following steps: 1. Shut down the Business Objects system. 2. Copy user and system information. 3. Uninstall/reinstall server products. 4. Resubmit user and system information. 5. Create a new key file (UNIX). The key file for Windows is created near the beginning of the upgrade process, when the repository is upgraded. (See Create a new key file (Windows) on page 92.) 6. Reactivate all Broadcast Agent jobs. 7. Restart the Business Objects system. 8. Upgrade the audit database 9. Upgrade WebIntelligence documents. You upgrade one cluster at a time. On Windows, you cannot have version 2.x/5.x and 6.x machines working together on the same cluster. Therefore, gradual upgrade means a mix of 2.x and 6.x clusters, but each cluster contains only one version. On UNIX, you can have 2.x and 6.x functioning on the same machine, if the two versions do not share web servers or directories. (See the Installation and Configuration guide.)
100
Shut down the Business Objects system

1. Disable access to the Business Objects system for all users. (See the System Administrators Guide.) 2. Shut down the Business Objects system on the primary and secondary nodes (called, in version 2.x, the cluster manager and cluster nodes).
Copy user and system information

There are two types of information that you need to copy from 2.x/5.x, and then resubmit to the upgraded version 6.x Business Objects system: User information - Default settings for new 6.x users - User information contained in the Storage directory System information Most user and system information is automatically transferred from 2.x/5.x to 6.x when you uninstall and reinstall the server products. However, you need to manually copy certain files and resubmit them after reinstalling the 6.x server products. This is described below. Windows Default settings for new users Any changes made to a 2.x clusters default settings for new users are stored in a global profile.txt file. If you changed these settings, Business Objects recommends that you manually copy the file (you will resubmit the file after reinstalling the 6.x server products). Otherwise, new users will see the standard 6.x default settings when they log into 6.x InfoView for the first time. Copy the 2.x/5.x global profile.txt file from: $INSTALLDIR\Server\WebIntelligence 2.5\Config If you stored the file on an external disk, you must copy it from that location. User information in the Storage directory You must copy a number of files containing additional 2.x/5.x user information. These files are stored at the cluster level, in the machine hosting the WIStorageManager. Copy the entire Storage directory: $INSTALLDIR\Server\WebIntelligence 2.5\Storage
101
System information Business Objects recommends that you back up the following system information files: Files in the Config folder: $INSTALLDIR\Server\WebIntelligence 2.5\Config Files in the Broadcast Agent folder, including Ini and Log files: $INSTALLDIR\Server\Broadcast Agent 5.0 BOManager folder information, include Ini files: $INSTALLDIR\Server\BusinessObjects Manager 5.0 Other module parameters, such as WIDispatcher You can access these module parameters in the version 2.x Services Administrator by clicking the Global Report button.
Figure 4-4 Global Report button
This generates an HTML report containing the parameters.
102
UNIX On UNIX, you need to back up and transfer the storage and configuration files to the 6.x Business Objects system. Storage files Storage files include the profile.txt file, which contains some of the clusters global default settings for user information. If this file is not transferred, users will see the standard 6.x default settings when they log into 6.x InfoView for the first time. Back up the 2.x storage files, located in the $WISTORAGEDIR directory. Configuration files To back up the configuration files: 1. Back up the following: $INSTALLDIR/Server/WebIntelligence/widispatch/config $INSTALLDIR/Server/WebIntelligence/wisession/config $INSTALLDIR/Server/WebIntelligence/wistorage/config $INSTALLDIR/Server/WebIntelligence/wiapi/apiconfig $INSTALLDIR/Server/BOManager/bin/BOManager.ini $INSTALLDIR/Server/BroadcastServer/bin/BcsScdul.ini 2. Make note of the values of the QT_MAX_ACTIVE_TIME and QT_MAX_INACTIVE_TIME parameters, located in 2.x in: $INSTALLDIR/Server/WebIntelligence/wigenerator/config
Uninstall/reinstall server products

You must uninstall and reinstall server products. Server products in version 6.x include: Business Objects server InfoView WebIntelligence BusinessObjects Web Installer Broadcast Agent Business Objects recommends that you test the server products before deploying them to the entire pool of users.
103
Enable the system for a test user. Then have that user test: Personal and Inbox documents Corporate documents All universes If you are satisfied with the results, enable the system for all users. Windows To uninstall and reinstall server products on Windows: 1. On the machine where you want to install the 6.x primary node, verify that all Business Objects servers are shut down, and then uninstall any earlier versions of Business Objects products. To uninstall an earlier version of server products, use the Setup utility of that version. You can launch the Setup utility for the earlier version via the Windows Start menu (Programs > WebIntelligence 2.x > Setup). Make sure you also uninstall any Business Objects components located on machines hosting application servers or web servers. 2. Restart the machine. 3. Install and configure the 6.x primary node on a machine with no previous versions of either server or desktop products. (Server products and BusinessObjects are not supported on the same server machine.) Do not edit any WebIntelligence 2.x documents if you want to use them again in the 2.x clusters. 4. Test the InfoView 6.x Inbox and Personal Documents lists to verify that you can access these files. 5. Test the 6.x repository connection to verify that you can access documents. 6. On each version 2.x cluster node: - Shut down the Business Objects system. - Uninstall 2.x server products. - Restart the machine. - Restart the server on the primary node. - Install 6.x server products. - Restart the machine again.
104
UNIX Keep in mind the following when you upgrade the cluster on UNIX: The installer cannot automatically upgrade from a previous major version; you must do this manually. It is not possible to automatically detect a version that is already installed. To install version 6.x server products: 1. On the machine hosting the web server, stop WebIntelligence and the web server. 2. Start the web server and application server that you will use with version 6.x. 3. Install version 6.x server products. 4. Link the following 2.x and 6.x directories (you do this with the Configuration Tool):
2.x directory $WIDATADIR/Config $WIDATADIR/ Universe
6.x directory $INSTALLDIR/nodes/<hostname>/ <clustername>/config $INSTALLDIR/nodes/<hostname>/ <clustername>/universe
Broadcast Agent After the upgrade to Broadcast Agent version 6.x, previously scheduled jobs are recovered and reprocessed by the new Scheduler. If the task is based on a WebIntelligence document or a BusinessObjects document, the document is kept in 2.x/5.x format. Therefore, 2.x/5.x users can still open, edit, and save them. If a 2.x/5.x corporate document is edited (and thus upgraded) and saved as a corporate document in a 6.x Business Objects product (such as BusinessObjects), all previous scheduling information is lost, and 2.x/5.x users can no longer work on it. There are only minor changes between version 5.x and 6.x Broadcast Agent Consoles. A version 6.x Console can connect to a 5.x repository and a 2.x cluster. A version 5.x Console can connect to a 6.x repository with a 2.x cluster, but it cannot display the document type for 6.x tasks. (For more information on upgrading Broadcast Agent, see Broadcast Agent on page 207.)
105
Resubmit user and system information

You must now resubmit the user and system information that you copied earlier (see Copy user and system information on page 100.) Windows To resubmit the global profile.txt file: 1. Paste the file into the following 6.x directory: $INSTALLDIR\bin\config 2. Log into InfoView as a general supervisor. 3. Click Options, and then click the About tab.
Figure 4-5 Set my options as Server Defaults
4. Click OK next to Set my options as Server Defaults. You may also want to set the other 6.x global default options at this time; for example, in My InfoView. Individual settings for transition users When users modify their personal settings in InfoView, the new profile is stored in an individual profile.txt file that is separate for each user. This is not the same as the global profile.txt file discussed above. In order for users making the transition from 2.x/5.x to 6.x to preserve their personal user settings, these files are transferred to the 6.x Business Objects system. This is done automatically by the system, but Business Objects recommends that you verify that it was completed. In version 6.x, the individual profile.txt files are in: $INSTALLDIR\nodes\<hostname>\<clustername>\storage\user\<username> If necessary, you can manually transfer the files, or use the Configuration Tool.
106
To manually transfer the individual profile.txt files: 1. Copy each 2.x/5.x profile.txt file from the Storage directory that you backed up: $INSTALLDIR\Server\WebIntelligence 2.5\Storage\user\<username> 2. Paste the file into the 6.x folders for each user in the machine hosting the WIStorageManager: $INSTALLDIR\nodes\<hostname>\<clustername>\storage\ user\<username> To transfer the files using the Configuration Tool: 1. On the Cluster Management page of the Confutation Tool, highlight Cluster Preferences, select Update Cluster Preferences, and then click Next.
The Choose location for Business Objects files and directories page appears. 2. Enter the path you want for the Storage directory or accept the default ($INSTALLDIR\nodes\<hostname>\<clustername>\storage).
107
NOTE
When transition users log out of InfoView 6.x for the first time, they are prompted to save their individual settings (if they did not already click Save on the Options page). This completes the transfer of individual user settings. User information in the Storage directory You must resubmit a number of files containing additional 2.x/5.x user information. You can find these files in the Storage directory that you backed up earlier. Note that these files are unique to each user. Copy the following files: $INSTALLDIR\Server\WebIntelligence 2.5\storage\list\<username>\mail.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\list\<username>\unv.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\mail\<username>\read.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\user\<username>\attribut.txt $INSTALLDIR\Server\WebIntelligence 2.5\storage\user\<username>\*.ctg Paste the files (in 6.x) into parallel folders at: $INSTALLDIR\nodes\<hostname>\<clustername>\storage
EXAMPLE The first file listed above, mail.txtfor the user named <biguser>would be pasted into the following location in 6.x:
$INSTALLDIR\nodes\<hostname>\<clustername>\storage\list\biguser\mail.txt UNIX Storage files There are two ways to transfer the storage files: Copy the files that you backed up earlier into the 6.x $STORAGEDIR directory. or Use the Configuration Tool.
108
To transfer the storage files using the Configuration Tool: 1. On the Cluster Management page of the Configuration Tool, highlight Cluster Preferences, select Update Cluster Preferences, and then click Next.
The Choose location for Business Objects files and directories page appears. 2. Enter the path you want for the Storage directory or accept the default ($INSTALLDIR/nodes/<hostname>/<clustername>/Storage).
109
Configuration files To transfer the configuration files, which you backed up earlier, to the 6.x system: 1. Copy the files into the 6.x directory and rename them: $INSTALLDIR/<hostname>/<clustername>/config/servers 2. Reset the values you noted when you backed up the files. They have been renamed in 6.x to MsgAdminMaxActiveTime and MsgAdminMaxInactiveTime, located in $INSTALLDIR/nodes/<hostname>/<clustername>/config/ servers/wiqt.cfg
Create a new key file (UNIX)

REMINDER The key file for Windows is created near the beginning of the upgrade process, when the repository is upgraded. (See Create a new key file (Windows) on page 92.)
To create a new key file: 1. Edit the MyWebiEnv.sh file to set up a connection to the database. If you are using the same connectivity in versions 2.x and 6.x, you can retrieve the 2.x settings. In 2.x, the MyWebiEnv.sh file is located in: - WebIntelligence v. 2.6 SP2 or later: $WIDATA/Config/ - earlier versions of 2.x: $WI/SetUp In 6.x, the file is located in $INSTALLDIR/nodes/<hostname>/ <clustername> 2. Run the $INSTALLDIR/setup/wmainkey script. This checks the connection and upgrades the bomain.key file. You can also create it in Windows, and then copy it into: $INSTALLDIR/nodes/<hostname>/<clustername>/locdata/
Reactivate Broadcast Agent jobs

Reactivate (set to Normal status) all Broadcast Agent jobs that you suspended before upgrading the repository. Then, verify that Broadcast Agents are being monitored in the Administration Console.
110
Restart the Business Objects system

Restart the Business Objects system for all users in the cluster that you upgraded. Then, have the users log in. When you reconnect users to the repository, keep in mind that: after upgrade, 2.x/5.x users no longer can have the right to update corporate categories version 5.x administrative applications, such as Designer and Supervisor, cannot connect to the new 6.x repository
Upgrade audit database

To upgrade the audit database to 6.x: 1. Open the version 6.x Administration Console. 2. Click Audit. The User Activity Log page appears. 3. At Log to Database, click On.
111
Upgrade WebIntelligence documents

NOTE
Upgrade of WebIntelligence 2.x documents is supported only for version 2.5 or later. Earlier version 2.x documents can only be viewed in 6.x. Keep in mind that in a mixed-version (5.x/6.x) environment, you do not have to upgrade your documents all at once. To upgrade WebIntelligence documents: 1. Open the WebIntelligence 2.x document in version 6.x InfoView. 2. Click Edit. 3. Make any modifications you want (optional). 4. Save the document as a personal or corporate document. The extension is changed from .wqy to .wid. That is, the document is upgraded to version 6.x. Note that the former 2.x (.wqy) document remains in the repository. It will be accessible to all users on the cluster, but will appear with a different icon than the 6.x document with the same name. If you want to eliminate such documents, you must delete them manually. After you upgrade to version 6.x, users see in InfoView the same documents they previously had the right to view (in the Personal Documents, Corporate Documents, Inbox Documents, and Scheduled Documents lists).
REMINDER WebIntelligence 6.x (.wid) documents cannot be opened in InfoView 5.x. (For more information on compatibility between different versions of documents, see Document
exchange on page 42).
112
Cells set to automatic size By default, table cells set to automatic size in WebIntelligence 2.x are set to AutoFit in version 6.x. WebIntelligence documents with many cells set to automatic size may take a long time to open in InfoView 6.x. Therefore, migrating these documents could be time-consuming. If you are migrating many such documents, consider doing one or both of the following: Perform the migration at a time when server use is minimal. Before migrating the documents, change the cell settings from automatic size to a fixed size. For details, see Cells set to automatic size on page 284.
113
After you complete the upgrading of product software and documents, try using the new features in the latest version. If you encounter any difficulties, see Frequently Asked Questions on page 319. For a complete description of these features, see Whats New in this Release on the documentation website. You can access the site by doing any of the following: Choosing More Tips and Samples from the Help menu in version 6.x desktop products Clicking the More Tips and Samples link in the InfoView 6.x navigation bar Going to the website: http://www.techsupport.businessobjects.com
Test desktop and administration products

Confirm that you can open and use the basic functionality of the new desktop and administration products: BusinessObjects BusinessQuery for Excel Designer Supervisor Auditor Administration Console
114
Test server products

Confirm that you can connect and use the basic functionality of the new server products: WebIntelligence InfoView Broadcast Agent InfoView Check that: the browser configuration indicator in InfoView (accessed from the Login page) functions properly users can log in users can access applications as per their security profiles user options function correctly Documents After you upgrade InfoView to 6.x, users see the same documents they previously had the right to view (in the Personal Documents, Corporate Documents, Inbox, and Scheduled Documents folders). Confirm this for several users. Upgrade several documents from 2.x/5.x to 6.x. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x. Create a number of new version 6.x BusinessObjects and WebIntelligence documents. Then try: editing refreshing viewing saving as a corporate document saving as a personal document sending Broadcast Agent Verify the following Broadcast Agent functionality: that all documents sent by Broadcast Agent before the upgrade are still in users inboxes that previously scheduled documents are still listed and scheduled that new tasks are properly started and executed
115
Resubmit to Broadcast Agent all corporate documents that are viewed through InfoView. Verify that one of the Faster Document Viewing over the Web options is checked. This prefills the cache. The first time you try to view one of these documents in InfoView, BOManager generates the presentation, and then stores it in a cache on WIStorageManager. When other InfoView users subsequently access the document, instead of having to recontact BOManager and regenerate the file in the requested format, they access the pregenerated file in the cache.
Create and apply categories

Create and test hierarchical categories, a new feature in version 6.x (see the InfoView Users Guide). Confirm that category management is prohibited to all users except General Supervisors. Assign the right for category management to a test user before assigning it to all the users and user groups you want to give it to. Apply categories to both BusinessObjects and WebIntelligence documents.
User settings
Confirm that user settings were properly transferred to the version 6.x system. Select several users, and verify that they still have the same settings as before the upgrade.
Delete 2.x directories (UNIX)

On UNIX, version 2.x and 6.x server products can function together on the same machine. Nevertheless, Business Objects recommends that you eventually delete the 2.x directories from your UNIX server. You can do this after the new system has been functioning well for at least several weeks.
116
This chapter describes the generic workflow needed for every upgrade procedure. Chapters 5-12 explain what you may need to do, additionally, in various specific deployments. These individualized instructions are organized into scenarios. Each chapter contains a different scenario. Below are two tables summarizing the scenarios, to help you choose the one that best fits your own deployment. Note that each scenario uses either the Gradual or Split upgrade method. When a given step is a generic procedure, the text refers back to the Generic Workflow chapters (3 and 4) for the full explanation. Only the procedures that differ from the generic will be fully explained within the scenario.
Summary of the scenarios

The tables below provide the following information about each scenario: Split or Gradual upgrade method Whether the cluster is based on UNIX or Windows The existing deployment Special components, such as an application server or Broadcast Agent Note that all the existing deployments contain BusinessObjects (either desktop or 3-tier mode), WebIntelligence, and a web server. The scenarios are models that represent larger deployments. You will see, for example, scenarios with only one or two client machines. This is done to facilitate a clear explanation; in your own deployment, there will almost certainly be multiple machines of this type.
117
Gradual
Basic web deployment Basic web deployment with application server (JSP) Basic web deployment with application server (ASP) Basic web deployment with Broadcast Agent Application server with Broadcast Agent/UNIX Application server with Broadcast Agent/Windows Basic web deployment with Auditor Basic web deployment with ASP and BusinessObjects (3-tier mode)
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
118
Scenario
Starts on page...
121
Basic web deployment
Two version 2.x clusters functioning on the same repository and sharing the same storage. Each cluster contains three machines: cluster manager, cluster node, and web server. There are three client machines, two for users and one for the administrator. There is no Broadcast Agent in the system, and no desktop products on the client user machines. The Gradual upgrade method is used. One version 2.x cluster with an application server. The cluster contains four machines: cluster manager, cluster node, application server, and web server. There are two client machines, one for users and one for the administrator. There is no Broadcast Agent in the system, and no desktop products on the client user machine. The Gradual upgrade method is used. Two version 2.x clusters functioning on the same repository and sharing the same storage. Each cluster contains four machines: cluster manager, cluster node, web server, and application server. The application server contains Active Server Pages (ASP) and Broadcast Agent Publisher. There are three client machines, two for users and one for the administrator. There are no desktop products on the client user machines. The Gradual upgrade method is used. One version 2.x cluster. The cluster contains three machines: cluster manager, cluster node, and web server. There are two client machines, one for users and one for the administrator. Broadcast Agent is functioning. There are no desktop products on the client user machine. The Split upgrade method is used. One version 2.x cluster with an application server, on UNIX. The cluster contains one machine, the cluster manager. There is one client user machine and one client administrator machine. Broadcast Agent is functioning. There are no desktop products on the client user machine. The Split upgrade method is used.
Basic web deployment with application server (JSP)
131
Basic web deployment with application server (ASP)
141
Basic web deployment with Broadcast Agent
151
Application server with Broadcast Agent/UNIX
161
119
Scenario
Starts on page...
169
Application server with Broadcast Agent/Windows
One version 2.x cluster with an application server. The cluster contains three machines: cluster manager, cluster node, and web server. Broadcast Agent is functioning. There is one client user machine and one client administration machine. There are no desktop products on the client user machine. The Split upgrade method is used. Two version 2.x clusters sharing the same storage. One of the clusters is dedicated to Auditor. There is a functioning audit database. There is one client user and one client administration machine. The client user has BusinessObjects in 3-tier mode. The Gradual upgrade method is used.
Basic web deployment with Auditor
179
Basic web deployment with ASP and BusinessObject s (3-tier mode)
Two version 2.x clusters functioning on the same repository and sharing the same storage. Each cluster contains three machines: cluster manager, cluster node, and web server/ application server. The application server contains Active Server Pages (ASP). There are three client machines, two for users and one for the administrator. There is no Broadcast Agent in the system. Client user machines have BusinessObjects in 3-tier mode. The Gradual upgrade method is used.
189
120
Checklist
Did you...........
modify your platforms (if necessary)? back up the repository? suspend all Broadcast Agent jobs? install version 6.x Supervisor? create a new key file? upgrade the repository? shut down the audit facility? uninstall and reinstall desktop and administration products? upgrade BusinessObjects documents? copy and resubmit user and system information? uninstall and reinstall server products? reactivate Broadcast Agent jobs? restart the Business Objects system? upgrade the audit database? upgrade WebIntelligence documents? test functionality and scalability? check which upgrade scenario fits your deployment?
Scenario: Basic Web Deployment
chapter
122
Overview
In this scenario, we upgrade a Business Objects system consisting of two version 2.x clusters working on the same repository and sharing the same storage. The goal is to upgrade both clusters, in stages, to version 6.x. Unless stated otherwise, the general upgrade procedures follow the Gradual upgrade method outlined in chapters 2 and 4 (see especially Phase 4 Upgrade clusters on page 99). You keep the 2.x/5.x system running as long as possible until the new installation is complete or nearly complete. During the intermediate stage, there will be a mixed deployment that has two different clustersversions 2.x and 6.xsharing the same version 6.x repository. All operating systems are Windows.
Gradual
Basic web deployment with InfoView users
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
123
Existing deployment
The existing deployment is a Business Objects system consisting of two version 2.x clusters functioning on the same repository and sharing the same storage. Desktop products are version 5.x. It looks like this:
2.x/5.x client 2.x/5.x client
Web server
Web server
Shared storage
2.x cluster manager 2.x cluster node 2.x cluster manager 2.x cluster node
Query DB
5.x repository
OLAP DB
2.x/5.x client administration
Figure 5-1 Existing deployment
Existing deployment
124
Cluster structure
Both clusters begin as identical 2.x clusters. Each cluster contains the following three machines: Cluster manager Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence 2.x - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
Figure 5-2 Shared storage set to On
- No BusinessObjects (3-tier mode), Broadcast Agent, or WebIntelligence SDK Cluster node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence 2.x - All single-instance modules deactivated in the 2.x Services Administrator - All other modules enabled - No BusinessObjects (3-tier mode), Broadcast Agent, or WebIntelligence SDK
125
Web server Windows 2000 Internet Information Server (IIS) Business Objects server stopped (HSAL only is functioning on this machine)
Client structure
There are three client machines; two are for users, one is for administration. Client users 1 and 2 Windows 2000 Internet Explorer 5 No middleware No desktop products One client machine will stay connected to the 2.x cluster during the upgrade process, whereas the other will be connected to the 6.x cluster (optional). However, you can still connect it to the 2.x cluster, if necessary. Client administrator Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 5.1 Designer 5.1 BusinessObjects 5.1 After the intermediate deployment is implemented, this machine will be connected to both the 2.x and 6.x clusters.
Existing deployment
126
Intermediate deployment
We now move to a mixed-version deployment phase: Cluster 1 remains version 2.x/5.x. Cluster 2 is upgraded to version 6.x. Both clusters are connected to the same 6.x repository. To implement the intermediate deployment: 1. Cut all links to the version 5.x repository. 2. Disable access to the Business Objects system for all users. 3. Back up the repository. 4. Install version 6.x Supervisor, Designer, and BusinessObjects on the client administration machine. Version 5.x desktop products remain on the machine. 5. Upgrade the repository to version 6.x. 6. Reconnect Cluster 1 users to the repository. They continue to function as if no change occurred. 7. Upgrade Cluster 2. 8. On Cluster 2, upgrade BusinessObjects. 9. Reconnect Cluster 2 users to the repository. 10. Test functionality and scalability. The actual procedures are explained in Chapters 2 and 4. Only the differences are mentioned below.
Upgrade Cluster 2
Make sure you install or do the following: On the primary and secondary nodes Install all version 6.x server products, except BusinessObjects Web Installer and Broadcast Agent. Install the Configuration Tool. Configure the nodes.
127
On the machine with the web server and application server: Install the ASP version of InfoView. Install web server and application server packages. Install the Configuration Tool. Configure the web server. Install and configure the application server. The deployment now looks like this:
2.x/5.x client 6.x client
Web server
Web server Application server
Shared storage
2.x cluster manager 2.x cluster node 6.x primary node 6.x secondary node
Query DB
6.x repository
OLAP DB
2.x/5.x and 6.x client administration
Figure 5-3 Intermediate deployment
128
Cluster 2 structure
After Cluster 2 is upgraded to version 6.x, it has the following structure: Primary node Windows 2000 (upgraded if necessary to meet 6.x requirements) Middleware: Oracle (upgraded if necessary to meet 6.x requirements) Server and administration products - WebIntelligence and InfoView 6.x - All modules enabled; shared storage set to On - No BusinessObjects (3-tier mode), Broadcast Agent, or WebIntelligence SDK Secondary node Windows 2000 (upgraded if necessary to meet 6.x requirements) Middleware: Oracle (upgraded if necessary to meet 6.x requirements) Server and administration products - WebIntelligence and InfoView 6.x - All single-instance modules (such as WIStorageManager) deactivated in the Administration Console - All other modules enabled - No BusinessObjects (3-tier mode), Broadcast Agent, or WebIntelligence SDK Web server and application server Windows 2000 (upgraded if necessary to meet 6.x requirements) IIS as web server and application server (upgraded if necessary to meet 6.x requirements) Configuration Tool to configure the web server and application server Business Objects server component (equivalent of the HSAL component of the Business Objects server in version 2.x) - Includes web server and application server packages.
NOTE
The web server and application server can also be located on the primary node.
129
Final deployment
Now you must upgrade Cluster 1. The procedure is the same as for the cluster you already upgraded (Cluster 2). The final deployment will look like this:
6.x client
6.x client
6.x primary node
6.x secondary node
6.x primary node
6.x secondary node
Query DB
6.x repository
OLAP DB
6.x client administration
Figure 5-4 Final deployment
Final deployment
130
Scenario: Basic Web Deployment, Application Server (JSP)
chapter
132
Overview
In this scenario, we upgrade a Business Objects system that has a version 2.x cluster functioning on a 5.x repository. This system includes an application server. The goal is to upgrade the cluster and the desktop and administration products to version 6.x. All operating systems are Windows. Unless stated otherwise, the general upgrade procedures follow the Gradual upgrade method outlined in chapters 2 and 4 (see especially Phase 4 Upgrade clusters on page 99). You keep the 2.x/5.x system running as long as possible until the new installation is complete. During the intermediate stage, there will be a mixed deployment that has two different clustersversions 2.x and 6.xsharing the same version 6.x repository.
NOTE
The 6.x cluster is a totally new cluster that is added to the system.
Gradual
Upgrading WebIntelligence using application server
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
133
Existing deployment
The existing deployment is a Business Objects system that has a version 2.x cluster functioning on a 5.x repository. Desktop products are version 5.x. There is a web server and an application server. It looks like this:
2.x/5.x client Web server Application server
2.x cluster manager
2.x cluster node
Query DB
5.x repository
OLAP DB
Existing deployment
134
Cluster structure
The version 2.x cluster (Cluster 1) contains the following four machines: Cluster manager Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence 2.x - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
- No Broadcast Agent Cluster node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence 2.x - All single-instance modules (such as WIStorageManager) deactivated in the 2.x Services Administrator - All other modules enabled - No Broadcast Agent
135
Web server Windows 2000 IIS Business Objects server stopped (HSAL only is functioning on this machine) Application server Windows 2000 Tomcat 3.2.1 WebIntelligence SDK (JSP scripts) Business Objects server stopped (HSAL only is functioning on this machine)
Client structure
There are two client machines; one is for a user, one is for the administrator. Client user Windows 2000 Internet Explorer 5 No middleware No desktop products This client machine will stay connected to the 2.x cluster during the upgrade process. Client administration Windows 2000 server Internet Explorer 5 Middleware: Oracle Supervisor 5.x Designer 5.x BusinessObjects 5.x
Existing deployment
136
We now move to a mixed-version deployment phase: The version 2.x cluster and 2.x/5.x client remain as is. A new 6.x cluster is created that has virtually the same components as the 2.x cluster. The new cluster will contain the following: - Primary node - Secondary node - Web server and application server - Client user - Client administration All machinesboth 2.x/5.x and 6.xconnect to the same 6.x repository. To implement the intermediate deployment: 1. Cut all links to the version 5.x repository. 2. Disable access to the Business Objects system for all users. 3. Back up the repository. 4. Upgrade the repository to version 6.x. 5. Build the new 6.x cluster (Cluster 2), with its server and client machines. 6. Have Cluster 2 users log in to the repository. 7. Have Cluster 1 (2.x/5.x) users log in to the repository. They continue to function as if no change occurred. 8. Test functionality and scalability on Cluster 2. 9. Uninstall 2.x/5.x products from Cluster 1 (optional). The actual procedures are explained in Chapters 2 and 4. Only the differences are mentioned below.
Build Cluster 2
You need to build the new 6.x cluster. Below are the components that you must install on each server or client machine. All Business Objects products to be installed are version 6.x. If there are any Business Objects products on the new machines, you must uninstall them before building the new cluster.
137
Primary node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence and InfoView - Administration Console - All single-instance modules (such as WIStorageManager) enabled in the Administration Console - All other modules enabled; shared storage set to On - No Broadcast Agent Secondary node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence and InfoView (JSP version) - All single-instance modules (such as WIStorageManager) deactivated in the Administration Console - All other modules enabled - No Broadcast Agent Web server Windows 2000 Apache Configuration Tool Business Objects web server components stopped (HSAL only is functioning on this machine)
138
Application server Windows 2000 Tomcat 40X JSP scripts These are the same as the 2.x/5.x scripts, with slight modifications. You need to change the calls invoking paths, RE SDK on WQY, and configuration files. You can either: - use InfoView 6.x in JSP mode - upgrade the customized JSP scripts (see the Developer Suite Migration Guide for details.) Configuration Tool Business Objects application server components stopped (HSAL only is functioning on this machine) Client user Windows 2000 Internet Explorer 5 No middleware No desktop products Client administration Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 6.x Designer 6.x BusinessObjects 6.x
139
The deployment now looks like this:
2.x/5.x client 6.x client
2.x/5.x web server
6.x web server 6.x application server
2.x/5.x application server
2.x cluster manager
2.x cluster node
6.x primary node
6.x secondary node
Query DB
OLAP DB
6.x repository
Test functionality and scalability

This is a critical step in the process. Verify that the new 6.x Business Objects system is functioning properly before you uninstall any 2.x/5.x products from Cluster 1.
Uninstall version 2.x/5.x products (optional)

Now that Cluster 2 is functioning properly with the version 6.x Business Objects system, uninstall version 2.x/5.x products from the machines in Cluster 1.
140
Final deployment
The final deployment is the same as before the entire upgrade procedure, except that the system is now version 6.x. The final deployment will look like this:
6.x client Web server Application server
6.x primary node
6.x secondary node
Query DB
6.x repository
OLAP DB
chapter
142
Overview
In this scenario, we upgrade a Business Objects system consisting of two version 2.x clusters working on the same repository and sharing the same storage. The goal is to upgrade both clusters, in stages, to version 6.x, and the desktop and administration products to 6.x. The application server contains ASP (Active Server Pages) scripts and the Business Objects application Broadcast Agent Publisher. (For more information on this component, see the Broadcast Agent Publisher Administrators Guide.) Unless stated otherwise, the general upgrade procedures follow the Gradual upgrade method outlined in chapters 2 and 4 (see especially Phase 4 Upgrade clusters on page 99). You keep the 2.x/5.x system running as long as possible until the new installation is complete or nearly complete. During the intermediate stage, there will be a mixed deployment that has different clustersversions 2.x and 6.xsharing the same version 6.x repository. All operating systems are Windows.
Gradual
Basic web deployment with ASP
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
143
Existing deployment
2.x/5.x client
2.x/5.x client
2.x cluster manager
2.x cluster node
2.x cluster manager
2.x cluster node
Query DB
OLAP DB
5.x repository
Existing deployment
144
Cluster structure
Both clusters begin as identical 2.x clusters. Each cluster contains the following three machines: Cluster manager Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence 2.x - WebIntelligence SDK - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
- No BusinessObjects (3-tier mode) Cluster node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence 2.x - WebIntelligence SDK - All single-instance modules deactivated in the 2.x Services Administrator - All other modules enabled - No BusinessObjects (3-tier mode) or Broadcast Agent
145
Web server/application server Windows 2000 IIS Business Objects server stopped (HSAL only is functioning on this machine) ASP scripts, including Broadcast Agent Publisher.
Client structure
There are three client machines; two are for users, one is for administration. Client users 1 and 2 Windows 2000 Internet Explorer 5 No middleware No desktop products One client user machine will stay connected to the 2.x cluster during the upgrade process, whereas the other will be connected to the 6.x cluster. However, you should still be able to connect it to the 2.x cluster, if necessary. Client administrator 1 Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 5.1 Designer 5.1 BusinessObjects 5.1 After the intermediate deployment is implemented, the client administration machine will be connected to both the 2.x and 6.x clusters.
Existing deployment
146
We now move to a mixed-version deployment phase: Cluster 1 remains version 2.x/5.x. Cluster 2 is upgraded to version 6.x. Both clusters are connected to the same 6.x repository. To implement the intermediate deployment: 1. Cut all links to the version 5.x repository. 2. Disable access to the Business Objects system for all users. 3. Back up the repository. 4. Install version 6.x Supervisor, Designer, and BusinessObjects on the client administration machine. Version 5.x desktop products remain on the machine. 5. Upgrade the repository to version 6.x. 6. Reconnect Cluster 1 users to the web server and/or the repository. They continue to function as if no change had occurred. 7. Upgrade Cluster 2. 8. On Cluster 2, upgrade BusinessObjects. 9. Reconnect Cluster 2 users to the repository. 10. Test functionality and scalability. The actual procedures are explained in Chapters 2 and 4. Only the differences are mentioned below.
Upgrade Cluster 2
Make sure you install or do the following: On the machine with the web server/application server: Install InfoView (web server and application server packages only). Install the Configuration Tool. Configure the web server. Configure the application server. Upgrade the ASP scripts (including Broadcast Agent Publisher) to 6.x.
147
On the primary and secondary nodes Install all version 6.x server products except BusinessObjects Web Installer. Install the ASP version of InfoView. Install the Configuration Tool. Configure the node. The deployment now looks like this:
2.x/5.x client
6.x client
2.x/5.x web server and application server
6.x web server and application server
2.x cluster manager
2.x cluster node
6.x primary node
6.x secondary node
Query DB
OLAP DB
6.x repository
Cluster 2 structure
After Cluster 2 is upgraded to version 6.x, it has the following structure: Primary node Windows 2000 (upgraded if necessary to meet 6.x requirements) Middleware: Oracle (upgraded if necessary to meet 6.x requirements) Server and administration products - WebIntelligence and InfoView 6.x - All modules enabled; shared storage set to On - No BusinessObjects (3-tier mode), Broadcast Agent, or WebIntelligence SDK
148
Secondary node Windows 2000 (upgraded if necessary to meet 6.x requirements) Middleware: Oracle (upgraded if necessary to meet 6.x requirements) Server and administration products - WebIntelligence and InfoView 6.x - All single-instance modules (such as WIStorageManager) deactivated in the Administration Console - All other modules enabled - No BusinessObjects (3-tier mode), or WebIntelligence SDK Web server and application server Windows 2000 (upgraded if necessary to meet 6.x requirements) IIS (upgraded if necessary to meet 6.x requirements) Application server installed Configuration Tool to configure the web server and application server Business Objects server component (equivalent of the HSAL component of the Business Objects server in version 2.x) - Includes web server and application server packages.
NOTE
149
Final deployment
Now you upgrade Cluster 1. The procedure is the same as for the cluster you already updated (Cluster 2). The final deployment will look like this:
6.x client
6.x client
6.x primary node
6.x secondary node
6.x primary node
6.x secondary node
Query DB
6.x repository
OLAP DB
Final deployment
150
Scenario: Basic Web Deployment, Broadcast Agent
chapter
152
Overview
In this scenario, we upgrade a Business Objects system consisting of one version 2.x cluster, two client machines, and Broadcast Agent. You build a test environment that has a completely new 6.x cluster. You keep the 2.x/5.x production system functioning until the 6.x test environment has been installed and verified. Only then is the system shut down, and the switch made to 6.x production. Unless stated otherwise, the general upgrade procedures follow the Split upgrade method outlined in chapters 2 and 3 (see especially Phase 4 Upgrade clusters (test environment) on page 62). In this scenario, you replace the machines on the 2.x cluster with brand new 6.x machines. This new 6.x cluster is then joined in the new deployment by the upgraded client machines. All operating systems are Windows.
Gradual
InfoView users with Broadcast Agent
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
153
Existing deployment
The existing deployment is a Business Objects system with one version 2.x cluster. There is one client user and one client administration machine. Client users do not have any desktop products installed on their machines. It looks like this:
2.x/5.x client
Web server
2.x cluster manager
2.x cluster node
Query DB
5.x repository
Existing deployment
154
Cluster structure
The cluster contains the following three machines: Cluster manager Windows NT4 Middleware: Oracle Server and administration products - WebIntelligence and InfoView 2.x - Broadcast Agent - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
- No BusinessObjects (3-tier mode) or WebIntelligence SDK Cluster node Windows NT Middleware: Oracle Server and administration products - WebIntelligence and InfoView 2.x - Broadcast Agent Manager - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On - No BusinessObjects (3-tier mode) or WebIntelligence SDK
155
Web server Windows NT4 IIS Business Objects server stopped (HSAL only is functioning on this machine)
Client structure
There are two client machines; one is for a user, and one is for administration: Client user Windows 98 Internet Explorer 5 No middleware No desktop products Client administration Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 5.1 Designer 5.1 BusinessObjects 5.1
Existing deployment
156
Build a test environment

To begin the upgrade, you build a test environment that has a dedicated repository. You upgrade the production system only after you see that the test environment operates satisfactorily. Versions 2.x/5.x and 6.x never function simultaneously on the same repository. To build the test environment: 1. Create a duplicate repository by copying the original version 5.x repository. The original repository continues to function as part of the production environment. 2. Upgrade the new duplicate repository to version 6.x. 3. Build a new 6.x cluster. 4. Connect this cluster to the 6.x repository. This becomes the test environment. 5. Verify that the test environment functions properly. The procedures are explained in Chapters 2 and 3. Below are some additional details regarding the new 6.x cluster.
New 6.x cluster

You build the version 6.x cluster on three new machines with no pre-existing Business Objects software. Heres what you need to install on these machines: Primary node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence and InfoView 6.x - Broadcast Agent - Administration Console - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On - No BusinessObjects (3-tier mode) or WebIntelligence SDK
157
Secondary node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence and InfoView 6.x - Broadcast Agent - All modules enabled - No BusinessObjects (3-tier mode) or WebIntelligence SDK Web server and application server Windows 2000 IIS (web server and application server) Configuration Tool to configure the web server and application server InfoView server components - Web server pages - Application server pages
158
Upgrading the production system

Now that the test environment operates satisfactorily, shut down the Business Objects system and upgrade the entire production system at the same time. To do this: 1. Cut all links to the test and production repositories. 2. Disable access to the Business Objects system for all users. 3. Backup the original 5.x production repository. 4. Upgrade the 5.x client machines to 6.x. Install version 6.x Supervisor, Designer, and BusinessObjects on the client administration machine. 5. Upgrade the original 5.x production repository to 6.x. 6. Connect the upgraded repository to the 6.x cluster. 7. Reconnect users to the web server and/or the repository. 8. Test functionality and scalability. The procedures are explained in Chapters 2 and 3.
159
Final deployment
The final, fully upgraded deployment looks like this:
New 6.x client
6.x client
6.x primary node
6.x secondary node
6.x repository Query DB
Final deployment
160
Scenario: Application Server, Broadcast Agent, UNIX
chapter
162
Overview
In this scenario, we upgrade a Business Objects system consisting of one version 2.x cluster and two client machines. Broadcast Agent is functioning. The portal is built with JSPs (Java Server Pages). This is a UNIX cluster. You build a test environment that has a completely new 6.x cluster. You keep the 2.x/5.x production system functioning until the 6.x test environment has been installed and verified. Only then is the system shut down, and the switch made to 6.x production. Unless stated otherwise, the general upgrade procedures follow the Split upgrade method outlined in chapters 2 and 3 (see especially Phase 4 Upgrade clusters (test environment) on page 62). In this scenario, you replace the machine on the 2.x cluster with a brand new 6.x machine. This new 6.x cluster is then joined in the new deployment by the upgraded client machines.
Gradual
Application server with Broadcast Agent/UNIX
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
163
Existing deployment
The existing deployment is a Business Objects system with one version 2.x cluster on UNIX. There is one client user and one client administrator machine. Client users do not have any desktop products installed on their machines. It looks like this:
2.x/5.x client
2.x cluster manager
Existing deployment
164
Cluster structure
The cluster contains one machine, the cluster manager: Cluster manager Sun Solaris Web server (Apache) Application server (Tomcat) Middleware: Oracle Server and administration products - WebIntelligence in JSP mode You can use the JSP sample delivered by Business Objects or a customized JSP application. - Broadcast Agent - All modules enabled in the 2.x Services Administrator
Client structure
There are two client machines; one is for a user, one is for an administrator: Client user Windows 98 Internet Explorer 5 No middleware No desktop products Client administration Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 5.1 Designer 5.1 BusinessObjects 5.1 Broadcast Agent Console 5.1
165

You build a test environment that has a dedicated repository. You upgrade the production system only after you verify that the test environment operates satisfactorily. Versions 2.x/5.x and 6.x never function simultaneously on the same repository. To build the test environment: 1. Create a duplicate repository by copying the original version 5.x repository. The original repository continues to function as part of the production environment. 2. Upgrade the new duplicate repository to version 6.x. 3. Build a new 6.x cluster. 4. Connect this cluster to the 6.x repository. This becomes the test environment. 5. Verify that the test environment functions properly. The procedures are explained in Chapters 2 and 3. Below are some additional details regarding the new 6.x cluster.
New 6.x cluster

You build the new version 6.x cluster on a new machine with no pre-existing Business Objects software: Primary node Sun Solaris Web server (Apache) Application server (Tomcat) Configuration Tool Middleware: Oracle Server and administration products - WebIntelligence in JSP mode You can either use InfoView 6.x in JSP mode or upgrade the customized JSP scripts (see the Developer Suite Migration Guide for details.) - InfoView server components (Web server pages and Application server pages) - Broadcast Agent - All modules enabled in the Administration Console - Administration tools
166
Upgrade the production system

Now that the test environment operates satisfactorily, shut down the Business Objects system and upgrade the entire production system at the same time. To do this: 1. Cut all links to the test and production repositories. 2. Disable access to the Business Objects system for all users. 3. Back up the original 5.x production repository. 4. Install version 6.x on the new client machine. Install Windows XP and IE 5. No middleware is needed. 5. Upgrade the 5.x client machines to 6.x. Install version 6.x Supervisor, Designer, BusinessObjects, and Broadcast Agent Console on the client administration machine. 6. Transfer the JSP scripts. See the Developer Suite Migration Guide. 7. Upgrade the original 5.x production repository to 6.x. 8. Connect the upgraded repository to the 6.x cluster. 9. Reconnect users to the web server and/or the repository. 10. Test functionality and scalability. The procedures are explained in Chapters 2 and 3.
167
Final deployment
New 6.x client
6.x client
6.x primary node Web server Application server
Final deployment
168
Scenario: Application Server, Broadcast Agent
chapter
170
Overview
In this scenario, we upgrade a Business Objects system consisting of one version 2.x cluster and two client machines with Broadcast Agent. The portal is built with JSPs (Java Server Pages). You build a test environment that has a completely new 6.x cluster. You keep the 2.x/5.x production system functioning until the 6.x test environment has been installed and verified. Only then is the system shut down, and the switch made to 6.x production. When this switch is made, you upgrade the existing machines on the cluster manager and cluster node. Unless stated otherwise, the general upgrade procedures follow the Split upgrade method outlined in chapters 2 and 3 (see especially Phase 4 Upgrade clusters (test environment) on page 62). All operating systems are Windows.
Gradual
Application server with Broadcast Agent/Windows
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
171
Existing deployment
The existing deployment is a Business Objects system with one version 2.x cluster on Windows NT. There is one client user and one client administration machine. Client users do not have any desktop products installed on their machines. It looks like this:
2.x/5.x client
2.x cluster manager
2.x cluster node
Existing deployment
172
Cluster structure
The cluster contains three machines: Cluster manager Windows NT4 Middleware: Oracle Server and administration products - WebIntelligence - Broadcast Agent - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
Cluster node Windows NT Middleware: Oracle Server and administration products - WebIntelligence - Broadcast Agent - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
173
Web server and application server Windows NT4 WebIntelligence SDK Application server - If ASP is used: IIS - If JSP is used: Tomcat Business Objects server stopped (HSAL only is functioning on this machine)
Client structure
There are two client machines; one is for a user, one is for an administrator: Client user Windows 98 Internet Explorer 5 No middleware No desktop products Client administration Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 5.1 Designer 5.1 BusinessObjects 5.1 Broadcast Agent Console 5.1
Existing deployment
174

You build a test environment that has a dedicated repository. You upgrade the production system only after you verify that the test environment operates satisfactorily. Versions 2.x/5.x and 6.x never function simultaneously on the same repository. To build the test environment: 1. Create a duplicate repository by copying the original version 5.x repository. The original repository continues to function as part of the production environment. 2. Upgrade the new duplicate repository to version 6.x. 3. Build a new 6.x cluster. 4. Connect this cluster to the 6.x repository. This becomes the test environment. 5. Verify that the test environment functions properly. The procedures are explained in Chapters 2 and 3. Below are some additional details regarding the new 6.x cluster.
New 6.x cluster

You need the following components in the new cluster: Primary node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence and InfoView 6.x - Broadcast Agent - Administration Console - All modules enabled - No BusinessObjects (3-tier mode) or WebIntelligence SDK
175
Secondary node Windows 2000 Middleware: Oracle Server and administration products - WebIntelligence and InfoView 6.x - Broadcast Agent - All modules enabled - No BusinessObjects (3-tier mode) or WebIntelligence SDK Web server and application server Windows 2000 Web server - If ASP is used: IIS - If JSP is used: Apache Application server - If ASP is used: IIS - If JSP is used: Tomcat Configuration Tool to configure the web server and application server InfoView server components - Web server pages - Application server pages
176
Upgrade the production system

Now that the test environment operates satisfactorily, shut down the Business Objects system and upgrade the entire production system at the same time. To do this: 1. Cut all links to the test and production repositories. 2. Disable access to the Business Objects system for all users. 3. Back up the original 5.x production repository. 4. Install version 6.x on the new client machine. Install Windows XP and IE 5. No middleware is needed. 5. Upgrade the 5.x client machines to 6.x. Install version 6.x Supervisor, Designer, BusinessObjects, and Broadcast Agent Console on the client administrator machine. 6. Upgrade the original 5.x production repository to 6.x. 7. Connect the upgraded repository to the 6.x cluster. 8. Reconnect users to the web server and/or the repository. 9. Test functionality and scalability. The actual procedures are explained in Chapters 2 and 3.
177
Final deployment
New 6.x client
6.x client
6.x primary node
6.x secondary node
Final deployment
178
Scenario: Basic Web Deployment, Auditor
chapter
180
Overview
In this scenario, we upgrade a Business Objects system consisting of two version 2.x clusters, two client machines, Auditor, and BusinessObjects (3-tier mode). One of the clusters is dedicated to Auditor. There is a functioning audit database. Unless stated otherwise, the general upgrade procedures follow the Gradual upgrade method outlined in chapters 2 and 4 (see especially Phase 4 Upgrade clusters on page 99). You keep a part of the 2.x/5.x system (the Auditor cluster) running until the end of the process. During the intermediate stage, there will be a mixed deployment that has two different clustersversions 2.x and 6.xsharing the same version 6.x repository. All operating systems are Windows.
Gradual
InfoView users with Auditor
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
181
Existing deployment
The existing deployment is a Business Objects system with two version 2.x clusters sharing the same storage. One of the clusters is dedicated to Auditor. There is one client user and one client administration machine. The client user has BusinessObjects (3-tier mode). There are no desktop products, such as BusinessObjects in 2-tier mode. The existing deployment looks like this:
2.x/5.x client administration and client Auditor
2.x/5.x client
Web server
2.x web server and application server (Auditor in JSP)
2.x cluster manager
2.x cluster node
2.x cluster manager (dedicated to Auditor)
Query DB
2.x audit DB
5.x repository
Existing deployment
182
Cluster structure
There are two clusters; one is the regular 2.x cluster and the other is dedicated to Auditor. Regular 2.x cluster This cluster contains the following three machines: Cluster manager Windows 2000 Server Middleware: Microsoft SQL Server Server and administration products - WebIntelligence 2.x - BusinessObjects (3-tier mode) - All modules enabled in the 2.x Services Administrator Cluster node Windows 2000 Server Middleware: SQL Server Server and administration products - WebIntelligence 2.x - BusinessObjects (3-tier mode) - All modules enabled in the 2.x Services Administrator Web server Windows 2000 Server Web server Business Objects server stopped (HSAL only is functioning on this machine)
183
Auditor cluster The Auditor-dedicated cluster contains the following two machines: Cluster manager Windows 2000 Server Middleware: SQL Server Server and administration products - WebIntelligence 2.x - WebIntelligence SDK - Auditor 5.x (JSP pages only) - All single-instance modules (such as WIStorageManager) activated in the 2.x Services Administrator - All other modules activated Web server/application server Windows 2000 Server Tomcat (as both web server and application server) Business Objects server stopped (HSAL only is functioning on this machine)
Client structure
There are two client machines; one is for a user, and one is for administration: Client user Windows 98 Internet Explorer 5 No middleware BusinessObjects (3-tier mode) Client administration Windows 2000 Server Internet Explorer 5 Middleware: SQL Server Supervisor 5.1 Designer 5.1
Existing deployment
184
We now move to a mixed-version deployment phase: The regular cluster is upgraded to version 6.x. The Auditor-dedicated cluster remains 2.x. Both clusters are connected to the same 6.x repository. To implement the intermediate deployment: 1. Cut all links to the version 5.x repository. 2. Log out users. 3. Back up the repository and the audit database. 4. On the client administration machine, upgrade Supervisor and Designer to version 6.x. 5. Upgrade the repository and the audit database to version 6.x. 6. Reconnect users to the repository. 7. Upgrade the regular cluster (see special remarks below). 8. Connect a new client user machine (see special remarks below). 9. Test functionality and scalability (see special remarks below). The actual procedures are explained in Chapters 2 and 4. Only the differences are mentioned below.
Upgrade the regular cluster

See Chapter 4 for general instructions. Upgrading takes place on the existing machines. Make sure you install or do the following: On the cluster manager and cluster node Install version 6.x Business Objects server and BusinessObjects Web Installer Upgrade WebIntelligence and BusinessObjects (3-tier mode) to version 6.x Install the Configuration Tool Configure the nodes On the machine with the web server and application server Install the version 6.x InfoView web server and application server packages Install the Configuration Tool Install an application server Configure the web server and application server
185
Connect a new client user machine

On the new client user machine, install the following: Windows XP Internet Explorer 5 Version 6.x BusinessObjects (3-tier mode) No middleware needed
Test functionality and scalability

In addition to the testing suggested in Chapter 4 (Phase 5 Test functionality and scalability on page 113), test the functioning of the version 5.x Auditor with the new, largely updated 6.x system. Recall that in general, Auditor 5.x is compatible with version 6.x. This means that: Auditor 5.x can function on a 6.x Business Objects server, using a 6.x audit database. Auditor 5.x reports can be refreshed using 6.x universes. Auditor 5.x views can be used to analyze the content of a version 6.x audit database (but in multi-cluster systems, it cannot determine the cluster in which an event originated). In particular, verify that Auditor documents and universes are functioning correctly.
186
The deployment now looks like this:

6.x client administration and client Auditor
New 6.x client
6.x client
6.x web server and application server
6.x primary node
6.x secondary node
2.x cluster manager (dedicated to Auditor)
Query DB
6.x audit DB
6.x repository
187
Upgrade the Auditor cluster

You now upgrade the Auditor cluster to 6.x: On the primary node Install version 6.x Business Objects server and BusinessObjects Web Installer Upgrade WebIntelligence to version 6.x Install the Configuration Tool Configure the nodes On the machine with the web server and application server Install the version 6.x InfoView application server package Install the Configuration Tool Upgrade Auditor to version 6.x. Using the Configuration Tool, deploy the Auditor pages Configure the web server and application server Upgrade the web server and application server, if necessary
Upgrade the Auditor cluster
188
Final deployment
New 6.x client
6.x client
6.x client administration and client Auditor
Web server
6.x primary node
6.x secondary node
6.x primary node (dedicated to Auditor)
Query DB
6.x audit DB
6.x repository
Scenario: Basic Web Deployment, ASP, BusinessObjects (3-tier)
chapter
190
Overview
In this scenario, we upgrade a Business Objects system consisting of two version 2.x clusters working on the same repository and sharing the same storage. The goal is to upgrade both clusters, in stages, to version 6.x, and the desktop and administration products to 6.x. The application server contains ASP (Active Server Pages) scripts. The client machines use BusinessObjects in 3-tier mode. (For more information on this component, see the Business Objects Users Guide.) Unless stated otherwise, the general upgrade procedures follow the Gradual upgrade method outlined in chapters 2 and 4 (see especially Phase 4 Upgrade clusters on page 99). You keep the 2.x/5.x system running as long as possible until the new installation is complete or nearly complete. During the intermediate stage, there will be a mixed deployment that has different clustersversions 2.x and 6.xsharing the same version 6.x repository. All operating systems are Windows.
Gradual
Basic web deployment with ASP and BusinessObjects (3-tier mode)
Auditor
Scenario Split
WebIntelligence SDK
Broadcast Agent
Windows
UNIX
191
Existing deployment
2.x/5.x client
2.x/5.x client
Shared storage
2.x cluster manager 2.x cluster node 2.x cluster manager 2.x cluster node
Query DB
5.x repository
OLAP DB
Existing deployment
192
Cluster structure
Both clusters begin as identical 2.x clusters. Each cluster contains the following three machines: Cluster manager Windows 2000 Middleware: SQL Server Server and administration products - WebIntelligence 2.x - All single-instance modules (such as WIStorageManager) enabled in the 2.x Services Administrator - All other modules enabled; shared storage set to On
Desktop products - BusinessObjects (3-tier mode)
Cluster node Windows 2000 Middleware: SQL Server Server and administration products - WebIntelligence 2.x - BusinessObjects Web Installer - All single-instance modules deactivated in the 2.x Services Administrator - All other modules enabled
193
Web server/application server Windows 2000 IIS Business Objects server stopped (HSAL only is functioning on this machine) WebIntelligence SDK
Client structure
There are three client machines; two are for users, one is for administration. Client users 1 and 2 Windows 98 Internet Explorer 5 No middleware BusinessObjects (3-tier mode) One client user machine will stay connected to the 2.x cluster during the upgrade process, whereas the other will be connected to the 6.x cluster. However, you should still be able to connect it to the 2.x cluster, if necessary. Client administrator 1 Windows 2000 Server Internet Explorer 5 Middleware: Oracle Supervisor 5.1 Designer 5.1 BusinessObjects 5.1 After the intermediate deployment is implemented, the client administration machine will be connected to both the 2.x and 6.x clusters.
Existing deployment
194
We now move to a mixed-version deployment phase: Cluster 1 remains version 2.x/5.x. Cluster 2 is upgraded to version 6.x. Both clusters are connected to the same 6.x repository. To implement the intermediate deployment: 1. Cut all links to the version 5.x repository. 2. Disable access to the Business Objects system for all users. 3. Back up the repository. 4. Install version 6.x Supervisor, Designer, and BusinessObjects on the client administration machine. Version 5.x desktop products remain on the machine. 5. Upgrade the repository to version 6.x. 6. Reconnect Cluster 1 users to the web server and/or the repository. They continue to function as if no change had occurred. 7. Upgrade Cluster 2. 8. Reconnect Cluster 2 users to the repository. 9. Test functionality and scalability. The actual procedures are explained in Chapters 2 and 4. Only the differences are mentioned below.
Upgrade Cluster 2
Make sure you install or do the following: On the machine with the web server/application server: Install ASP version of InfoView (web server and application packages only). Install the Configuration Tool. Configure the web server. Configure the application server. Do either of the following: - Upgrade the customized ASP scripts to 6.x (see the Developer Suite Migration Guide) - Use InfoView 6.x in ASP mode
195
On the primary and secondary nodes Install all version 6.x server products except Broadcast Agent. Install the Configuration Tool. Configure the node. On the client user machines Upgrade BusinessObjects (3-tier mode). The deployment now looks like this:
2.x/5.x client
6.x client
Shared storage
2.x cluster manager 2.x cluster node 6.x primary node 6.x secondary node
Query DB
6.x repository
OLAP DB
196
Cluster 2 structure
After Cluster 2 is upgraded to version 6.x, it has the following structure: Primary node Windows 2000 (upgraded if necessary to meet 6.x requirements) Middleware: SQL Server (upgraded if necessary to meet 6.x requirements) Server and administration products - WebIntelligence and InfoView 6.x - All modules enabled; shared storage set to On - BusinessObjects Web Installer - Administration Console Secondary node Windows 2000 (upgraded if necessary to meet 6.x requirements) Middleware: SQL Server (upgraded if necessary to meet 6.x requirements) Server and administration products - WebIntelligence and InfoView 6.x - All single-instance modules (such as WIStorageManager) deactivated in the Administration Console - All other modules enabled - BusinessObjects Web Installer Web server and application server Windows 2000 (upgraded if necessary to meet 6.x requirements) IIS as web server and application server (upgraded if necessary to meet 6.x requirements) Configuration Tool to configure the web server and application server InfoView server components (web server and application server pages)
NOTE
197
Final deployment
Now you must upgrade Cluster 1. The procedure is the same as for the cluster you already updated (Cluster 2). The final deployment will look like this:
6.x client 6.x client
6.x primary node
6.x secondary node
6.x primary node
6.x secondary node
Query DB
6.x repository
OLAP DB
Final deployment
198
Upgrading Individual Products
part
The Audit Facility and Auditor
chapter
202
Overview
The Audit facility and BusinessObjects Auditor are separate but related entities. The Audit facility tracks crucial information on user and system activity. Each time any of over 50 predefined events occurs, a record of the event is created and stored by the Audit facility. You can then retrieve and analyze the individual events. The Audit facility is part of the distributed 3-tier system. It is activated via the Administration Console. The Audit facility can gather and store event records in: File mode The system stores the user or system information in flat (.log) files. Database mode The system stores the user or system information to the audit database.
NOTE
For more information, see The Audit facility in the BusinessObjects Auditor Guide. Auditor is a product that enables you to monitor and analyze user activity by accessing the Business Objects repository and the audit database via special documents, called indicators.
Structure of the audit database

The structure of the version 6.x audit database is similar to that of version 2.x. In the transition to 6.x: No tables were deleted No columns were deleted or modified No IDs were removed from lookup tables (events, details, applications) This enables the 2.x/5.x system to log its activity to a version 6.x audit database. In addition, all version 2.x/5.x applications can function with the version 6.x Audit facility. However, because of new events and other new information (such as cluster ID) in the 6.x Audit facility, the reverse is not truethe 6.x Business Objects server cannot log its activity to a version 2.x audit database.
203
Upgrading the Audit facility

To upgrade the Audit facility, you must: 1. Shut down the version 2.x Audit facility before upgrading any Business Objects products to version 6.x. 2. Perform the upgrade of your Business Objects system to 6.x. 3. Upgrade the audit database to version 6.x.
Shut down the 2.x Audit facility

To shut down the Audit facility: 1. Open the 2.x Business Objects Services Administrator. 2. Click View Log. The User Activity Log page appears.
3. Set the User Activity Log to Off. 4. Click Apply. Next, perform the upgrade of your Business Objects system.
Upgrading the Audit facility
204
Upgrade audit database to 6.x

To upgrade the audit database to 6.x: 1. Open the version 6.x Administration Console. 2. Click Audit. The User Activity Log page appears. 3. At Log to Database, click On.
205
Upgrading Auditor
Auditor is now one of the administration products (it was formerly classified as a server product). You upgrade Auditor when you uninstall version 2.x server products and reinstall version 6.x administration products. (See Uninstall/reinstall server products on page 65.)
Database views
Reinstalling Auditor 6.x and upgrading the audit database to 6.x does not automatically upgrade the database views to 6.x. You must delete the 5.x views and create the new 6.x views using the Create and Delete buttons in the Auditor Universe Exporter:
Figure 13-3 Auditor Universe Exporter
For detailed instructions, see the BusinessObjects Auditor Guide. If you do not perform this procedure, your new Auditor version 6.x will continue to use the 5.x views.
Upgrading Auditor
206
Compatibility
In general, Auditor 5.x is compatible with version 6.x. This means that: Auditor 5.x can function on a 6.x Business Objects server, using a 6.x audit database. Auditor 5.x reports can be refreshed using 6.x universes. Auditor 5.x views can be used to analyze the content of a version 6.x audit database (but in multi-cluster systems, it cannot determine the cluster in which an event originated). However, Auditor 6.x is not compatible with version 2.x/5.x. This means that Auditor 6.x: cannot be installed and cannot function on a 2.x Business Objects server cannot analyze the content of a 2.x audit database cannot analyze the content of a 5.x repository cannot have its reports refreshed using Auditor version 5.x universes
NOTE
Neither Auditor nor the Audit facility can function when a 2.x cluster and a 6.x cluster are both connected at the same time to the same audit database.
Broadcast Agent
chapter
208
Overview
Broadcast Agent is one of the server products. You upgrade Broadcast Agent when you uninstall version 2.x server products and reinstall version 6.x (see Uninstall/reinstall server products on page 65). This chapter presents some additional information regarding the upgrading of the product, including mixed-version deployments. After upgrade to Broadcast Agent version 6.x, previously scheduled jobs are recovered and reprocessed by the new Scheduler. If the task is based on a WebIntelligence document or a BusinessObjects document, the document is kept in 2.x/5.x format. Therefore, 2.x/5.x users can still open, edit, and save it. If you edit (and thus upgrade) a 2.x/5.x scheduled corporate document and save it as a corporate document in a 6.x Business Objects product (such as InfoView), all previous scheduling information is lost, and 2.x/5.x users can no longer work on it. You must suspend all Broadcast Agent jobs before upgrading the repository, and then reset them to Normal status after you upgrade the cluster. These procedures are described in the Generic Workflow chapters (chapters 3 and 4). If this is not done, jobs may be lost during the upgrade process.
Broadcast Agent
209
Broadcast Agent Scheduler

A version 5.x Scheduler cannot process 6.x WebIntelligence and BusinessObjects documents. You can associate a 5.x and a 6.x Scheduler to the same Broadcast Agent, if there is a 2.x cluster and a 6.x cluster connected to the same repository. The 6.x Scheduler can perform batch processing of WebIntelligence 6.x (.wid) documents. It can also handle documents with or without prompts (refresh and send to users or save as a corporate document). The 6.x Scheduler can process and distribute 5.x documents and maintain the 5.x format.
Burst to group
You can set a document to be refreshed once for multiple users. The refreshed document is sent to all users who have a given profile (the reference profile). You set the reference profile in Supervisor. This feature, known as burst to group, reduces inefficient refresh actions while ensuring the security of data. Burst to group is set on the Actions tab of the Send Document dialog box, by selecting Refresh with the reference profile of each group.
Broadcast Agent Scheduler
210
Broadcast Agent Console

There are only minor changes between version 5.x and 6.x Broadcast Agent Consoles. A version 6.x Console can connect to a 5.x repository and a 2.x cluster, but in this case it cannot perform Run Now, Interrupt Task, or Purge. A version 5.x Console can connect to a 6.x repository with a 2.x cluster, but in this case: it cannot display the document type for 6.x tasks it cannot perform Run Now or Interrupt Task
Broadcast Agent
211
Mixed-version deployments
Mixed-version deployments (version 6.x desktop products alongside 5.x) may cause problems for document exchange within a company. For example, suppose a 6.x user receives a 5.x BusinessObjects (.rep) document. This user modifies the document, saving it in version 6.x, and then sends it to Broadcast Agent for further processing. Broadcast Agent processes the document. A 5.x user who then receives the document would not be able to open it, because it is now a 6.x document. You can avoid this situation by creating two document domains for a mixed user population: one for 5.x users, the other for 6.x users. BusinessObjects users sending documents to the repository or to Broadcast Agent can select the document domain that corresponds to the version they are working with.
Mixed-version deployments
212
Channel tasks
There is no Channel option in version 6.x, but previous tasks continue to be executed. In 6.x, the Channel option does not appear in the Available Actions list in the Schedule Corporate Documents dialog box. It does, however, appear in the Send to Broadcast Agent dialogue box.
Broadcast Agent
213
Hierarchical categories
Hierarchical categories are a new feature in version 6.x. With hierarchical categories, you can create subcategories within categories, to any depth you want. You can then associate a document with one or more of these categories or subcategories. Every category can have zero, one, or several subcategories. The hierarchy of categories is a simple tree. The top-level categories are displayed in an area called Corporate Home. (For more information, see Categories on page 291.) A version 5.x Broadcast Agent Console displays both 5.x categories and hierarchical categories. The hierarchical category appears as a 5.x name with special characters (such as a forward slash) in the Categories column. If there are no separators in the name, it is assumed that a hierarchical category was not created; they are interpreted as root categories in 6.x. A version 6.x Console can display both 5.x and 6.x categories. If you create a hierarchical structure in 6.x, the 6.x user sees the hierarchy but the 5.x user sees a flat list of categories.
Hierarchical categories
214
Broadcast Agent
BusinessObjects
chapter
216
Overview
BusinessObjects is one of the desktop products. You upgrade BusinessObjects when you uninstall version 5.x desktop products and reinstall version 6.x. You must also upgrade your BusinessObjects (.rep) documents. The order of this procedure within the overall upgrading process varies according to the upgrade method that you are using (see Upgrade methods on page 29). To upgrade BusinessObjects in 3-tier mode, see BusinessObjects in 3-tier mode on page 222.
BusinessObjects
217
Uninstalling/reinstalling desktop products

There are two ways to uninstall and reinstall desktop products: Using the version 6.x Installation wizard to uninstall 5.x and reinstall 6.x. Manually uninstalling version 5.x and then installing 6.x.
NOTE
WebIntelligence version 2.x must be uninstalled before installing any version 6.x desktop product. Version 5.x and 6.x desktop products can be installed on the same machine. If the applications are launched via the Windows Start menu, the two versions can work independently of each other. However, Business Objects recommends that you install versions 5.x and 6.x on different machines.
Using the 6.x Installation wizard

To uninstall and reinstall: 1. Run the version 6.x Setup utility. When the Installation wizard detects an earlier version of desktop products, you are prompted to uninstall the earlier version, and then restart the installation. 2. To begin the process, select Upgrade on the Keep/Upgrade page of the wizard. 3. Follow the instructions in the wizard.
Manually uninstalling 5.x

To uninstall and reinstall: 1. Run the version 5.x Setup utility. This can be accessed via the Windows Start menu (Programs > BusinessObjects 5.x > Setup) or you can use a CD. 2. Uninstall version 5.x. 3. Install 6.x desktop products as a fresh installation.
Uninstalling/reinstalling desktop products
218
Upgrading BusinessObjects documents

You upgrade version 5.x BusinessObjects documents to 6.x simply by opening them in a 6.x product, and then saving the documents. The upgraded document keeps the same type, extension, and icon; only the version number changes. Documents in a version earlier than 5.x cannot be upgraded from within version 6.x. You must first upgrade them to 5.x from within a 5.x application. Be careful if you have BusinessObjects 5.x and 6.x in the same system: After a document is upgraded to version 6.x, it cannot be reopened by BusinessObjects 5.x. Business Objects recommends that you test documents after they have been upgraded. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x.
BusinessObjects
219
Administrative installation
The installation of desktop products on the client machine, via a server, is called an administrative installation (previously called a master setup/standalone). If you set up the administrative installation using command-line mode, you can: enable users to upgrade via a shared network location prompt users to upgrade when they log in For detailed instructions on administrative installations, see the Installation and Configuration guide.
NOTE
The administrative installation in version 6.x replaces the master/standalone setup in 5.x. The master/shared setup, however, is no longer available.
Administrative installation
220
Compatibility
Can ... Do the following for 6.x documents: Retrieve 6.x users 2.x/5.x users Yes No (but .rep documents appear in the list of documents in BusinessObjects) Send or save as corporate Yes No
Can ...
Do the following for 5.x BusinessObjects documents: Retrieve Send Yes, but document becomes 6.x. Save as corporate Not from InfoView; otherwise, you can, but document becomes 6.x. Yes
6.x users
Yes
2.x/5.x users
Yes
Yes
When ...
Refreshes the following ... a 5.x BusinessObjects document in BusinessObjects... a 5.x BusinessObjects document in InfoView... it remains 5.x it remains 5.x
a 6.x user a 2.x/5.x user
BusinessObjects
221
Can ... 6.x BusinessObjects 5.x BusinessObjects Yes Yes
Function on a ... 6.x repository 5.x repository No Yes
Compatibility
222

BusinessObjects in 3-tier mode is a Windows application (busobj.exe) that can be launched in the following ways: from the Windows Start menu from an active InfoView session In the 3-tier BusinessObjects deployment, the middleware is installed on the server, and the client can connect to the repository only through the Business Objects server. All client-server communication is over HTTP. BusinessObjects in 3-tier mode enables you to view BusinessObjects (.rep) documents via a web browser. To upgrade BusinessObjects in 3-tier mode, you must upgrade two separate components: BusinessObjects Web Installer on the cluster. You upgrade the Web Installer when you uninstall version 2.x server products and reinstall version 6.x (see Uninstall/reinstall server products on page 65). BusinessObjects (3-tier mode) on the client machine. This is usually done from within InfoView, but you can also install it on each machine with a CD-ROM. (See Upgrading on the client machine on page 222.)
REMINDER BusinessObjects in 3-tier mode was previously referred to as Zero Admin BusinessObjects.
Compatibility Version 5.x BusinessObjects cannot function with 6.x InfoView, and version 6.x BusinessObjects cannot function with 5.x InfoView.
Upgrading on the client machine

The procedures below should be performed after desktop products, administration products, the clusters, and server products (including InfoView and BusinessObjects Web Installer) are all upgraded to version 6.x. Users install BusinessObjects version 6.x on the client machine by either: accessing the Download page in InfoView version 6.x opening a BusinessObjects document in InfoView 6.x
BusinessObjects
223
By default, the Setup utility uninstalls any previous version of BusinessObjects, and then installs version 6.x. Users are not offered a choice of whether they want to uninstall the previous version. You can change this default, so that: version 5.x BusinessObjects remains in place, alongside the newly-installed 6.x users are asked whether they prefer uninstalling or keeping version 5.x To make these changes, use the command-line mode of the administrative installation. For instructions, see the Installation and Configuration guide. To force 5.x to remain in place, set the MIGRATION feature to a value of 0. To offer users the choice of whether they want to uninstall version 5.x, set the MIGRATIONPROMPT feature to a value of 1. You set these two features by opening the ZABOInstallPopup.asp file, and changing the values in:
<param name="strParams" value="THREETIERBUSOBJ=1 WEB=1 INSTALLLANG=<%= sLocale %> MIGRATION=1 MIGRATIONPROMPT=0 VBAINSTALL=0">
Version compatibility check When you launch BusinessObjects in 3-tier mode or use it to try to access a BusinessObjects document, the system checks compatibility between: the version of InfoView the version of BusinessObjects available for installation via InfoView If any of the components are not compatible, the system prompts you for the necessary upgrade. If you launch BusinessObjects via InfoView version 6.x, the system will always use version 6.x BusinessObjectseven if version 5.x is also installed on the machine. If both versions are installed, and you open a 5.x document via 5.x InfoView, the system uses version 6.x BusinessObjects.
224
Upgrading ActiveX If a previous version of BusinessObjects in 3-tier mode was already installed on the machine before you installed version 6.x, you must manually delete the ZaboCheckAndRunControlClass file from within Internet Explorer. This is because the previous version of ActiveX is not compatible with the current version of BusinessObjects. When you delete the file and rerun BusinessObjects, the new version of ActiveX is automatically downloaded to your machine. To delete the ZaboCheckAndRunControlClass file: 1. After reinstallation of BusinessObjects (3-tier mode), open Internet Explorer. 2. On the Tools menu, select Internet Options. The Internet Options dialog box appears. 3. Click the Settings button. The Settings dialog box appears. 4. Click the View Objects button. You will see your downloaded program files. 5. Delete the ZaboCheckAndRunControlClass file. 6. Rerun BusinessObjects (3-tier mode). The new version of ActiveX is downloaded to your machine.
BusinessObjects
225
Calculator enhancements
Business Objects has discovered a few issues that cause BusinessObjects 5.1 to return incorrect results in certain limited circumstances. These circumstances can occur when reports contain multiple data providers or cubes, or when they use the NoFilter() function. Read this section carefully to determine whether your reports are affected by these issues. Depending on the previous version of your Business Objects system, you need to read all or part of this section: If you are migrating to 6.x from a version of BusinessObjects earlier than 5.1.4, read the entire section. You may need to make adjustments in your reports based on the calculator changes introduced in both versions (5.1.4 and 6.1). If you are migrating to 6.x from version 5.1.4 or later, skip to Changes made in version 6.1 on page 239. You may need to make adjustments in your reports based on the calculator changes introduced in version 6.1 only. All examples are based on the Island Resorts Marketing universe that is delivered with BusinessObjects. This section provides technical information about the changes made to the BusinessObjects calculation engine in versions 5.1.4 and 6.1. For additional details or assistance, contact Online Customer Support or WW Customer Advocacy.
Changes made in version 5.1.4

You need to read this section only if you are migrating to version 6.x from a BusinessObjects version earlier than 5.1.4. Changes made to the calculation engine in version 5.1.4 have an impact on: Global filters Complex filters Incompatible objects in the same block Global filters Global filters apply to an entire report tab whereas block filters apply to specific blocks only. Global filters behave differently in version 5.1.3 and version 5.1.4+.
226
If your reports contain global filters and multiple cubes, whether from single or multiple data providers, they may be affected by the change in global filter behavior. Behavior of global filters in 5.1.3 In the following example, a report has three data providers containing several linked objects. The object City in Query 3 is not linked to the other data providers, but Country and Resort in Query 3 are linked to Country and Resort in Query 1 and Query 2:
Figure 15-1 Linked objects
There is a global filter defined on City with a condition that is not met (City = test). BusinessObjects 5.1.3 creates a report with one table per data provider. The first table is based on Query 1, the second on Query 2 and the third on Query 3. The filter impacts the table based on Query 3 only; the table has no data because no row matches the filter criterion. Behavior of global filters in 5.1.4+ In BusinessObjects 5.1.4, the behavior of global filters was modified to account for indirect filters. In the previous example, indirect filtering means that all tables do not now show data because BusinessObjects indirectly applies the filter on Table 3 to the other two tables. This occurs because the other tables are linked to the table containing the object referenced in the filter. This mechanism is similar to an equi-join in a RDBMS, where the rows returned from all joined tables are determined by a WHERE restriction on any individual table.
BusinessObjects
227
Obtaining 5.1.3 results in 5.1.4+ You can recreate BusinessObjects 5.1.3 behavior in two ways: by moving the filter to the block level, or by desynchronizing the queries. Moving the filter to the block level In the example, you could ensure that all tables are not filtered by applying the filter City=test to Table 3 only. This solution works only if the filtered block contains the object referenced in the filter. If the block does not contain the City object, you would not be able to apply the filter to it. Desynchronizing the queries By removing the links between the data providers, you ensure that BusinessObjects does not apply the filter indirectly to other data providers. Indirect filters and calculations The new indirect-filter behavior has an impact on calculations. In the following example, there are two data providers, containing the (Country, Resort, Revenue) and (Country, Future Guests) objects respectively. Consider a report with three blocks:
Figure 15-2 Report with three blocks
228
The third block contains objects from both data providers. If you add a sum on the Revenue and Future Guest columns in the third block and a complex filter, (Resort=Bahamas Beach) on the Resort object, you obtain the following result:
Figure 15-3 Sum and complex filter
NOTE
If you add a sum to the Future Guests column before applying the complex filter, BusinessObjects still produces the figure 102, even though the column contains three figures46, 56, and 56. For more information, see Aggregation levels in synchronized data providers on page 238. The Sum for Future Guests is incorrect in version 5.1.3 because the indirect-filter behavior is not implemented. The filter on the first data provider is not applied indirectly to the second data provider, with the result that the Future Guests figure is counted twice. In BusinessObjects 5.1.4+, the sum is correct:
Figure 15-4 Correct sum
To arrive at the correct sum: 1. Filter the first data provider to produce a list of rows that need to be preserved. 2. Join this set of rows with the second data provider on the data providers linked dimensions. The join returns a row only if there is a row in each data provider.
BusinessObjects
229
In our example: 1. Filter on Resort in the first data provider to return one row (US, Bahamas Beach). 2. Join to the second data provider to return one row and the correct value for Future Guests.
REMINDER Indirect filters are similar to equi-joins in an RDBMS.
Complex filters Complex filters are filters that are based on a formula, for example:
Country <> France
If your reports contain complex filters and multiple cubes, whether from single or multiple data providers, your reports may be affected by the change in complexfilter behavior. Complex filters in 5.1.3 The complex filter algorithm in BusinessObjects 5.1.3 produced errors in certain situations involving linked data providers. This issue could be seen in: incorrect display of lists of values different behavior when filtering empty values Complex filters in 5.1.4+ The complex filter algorithm was updated in BusinessObjects 5.1.4+; it solves the issue associated with lists of values and empty values. The following sections explain each of these scenarios. Lists of Values in 5.1.3 The following example looks at a list of values associated with a filter. The report contains: two data providers - Data Provider 1 contains the Country, Quarter, Year, and Revenue objects - Data Provider 2 contains the Country and Number of Guests objects The two data providers are synchronized on Country. a variable called Test whose formula references objects in both data providers a complex filter with the formula Test<>FRA
230
When you view the list of values related to the Test variable, all values not equal to FRA should be selected, but this is not the case. For example, you might see something like this:
Figure 15-5 Partial value selection
This is incorrect; US should also be selected because US <> FRA. Lists of Values in 5.1.4+ When you open the report with BusinessObjects 5.1.4+, all values are selected.
NOTE
Versions 5.1.3 and 5.1.4+ return the same results when simple filters are used. Empty values in 5.1.3 The complex filters solution has implications for filtering on empty values. Before the solution, this filtering occurred automatically. Now there is no automatic filter on empty values in a multi-data provider report. The following example illustrates this. Consider a simple report containing two data providers, Q1and Q2. Each data provider contains the Country and Revenue objects, and they are linked on the Country dimension. The second data provider has a query condition that restricts Country to US.
BusinessObjects
231
Here is the report display:
Figure 15-6 Simple report with two data providers
If you add a complex filter on Revenue in the third table, <Revenue(Q2)> <> 2451104, version 5.1.3 takes the empty value into consideration, and the third table with synchronized data providers contains one row:
Figure 15-7 Third table contains one row
232
Empty values in 5.1.4+ In the above example, BusinessObjects 5.1.4+ does not display any results in the third table because the filter does not account for the empty revenue value:
Figure 15-8 Empty revenue value
Obtaining 5.1.3 results in 5.1.4+ You make version 5.1.4+ behave like 5.1.3 by forcing it to account for empty values. To do this, incorporate an object from the first data provider into the filter definition. If you change the filter definition in the above example to (<Revenue(Q2)> <> 2451104) And (<Country(Q1)> = <Country(Q1)>), the result is the same as the 5.1.3 result. By including an object, Country(Q1), from the first data provider, you force BusinessObjects to take the empty value into account. Incompatible objects Sometimes, changes made in BusinessObjects 5.1.4+ can affect reports containing incompatible objects. Incompatible objects are objects that belong to different contexts in a universe. BusinessObjects universe designers often use contexts to resolve loops in database structures. If a query references incompatible objects, it cannot be expressed as a single SQL query. BusinessObjects therefore builds multiple data cubes and synchronizes them. If your reports have incompatible objects that appear in the same block, they may be affected by the change in incompatible-object behavior. To find out whether a report is affected, look at the Data Manager dialog box. You can open the Data Manager dialog box by clicking the Data Manager icon on the toolbar.
BusinessObjects
233
The Data Manager shows the data cubes that BusinessObjects uses internally to build the report, and the objects within each cube. Each cube is populated from one SQL query, so if there is more than one cube, the report contains multiple queries.
Figure 15-9 Synchronized query cubes
If the report has more than one cube or SQL query, check whether objects from different cubes (incompatible objects) appear in the same block of data.
Figure 15-10 Incompatible objects in same block
If you have reports that satisfy these conditions, they may be affected by the incompatible objects solution in BusinessObjects 5.1.4+.
234
You can see why these objects are incompatible by examining the Island Resorts Marketing universe. It has two contexts. The Reservation Year object (derived from reservations.res_date) and the Revenue object (derived from sales.invoice_date) each belong to a different context:
Figure 15-11 Reservation and Reservation Year objects
BusinessObjects
235
Incompatible objects in 5.1.3 Consider a report that contains the Country, Year, Reservation Year, Revenue, and Future Guests objects. Because Reservation Year and Revenue come from different contexts, BusinessObjects needs to perform two steps: 1. Sum Future Guests by Country by Reservation Year 2. Sum Revenue by Country by Year To do this, BusinessObjects generates two SQL statements and builds the following cubes: Cube 1: Country, Year, Revenue Cube 2: Country, Reservation Year, Future Guests You can examine the underlying cube structure of a report using the Data Manager. The Data Providers pane on the left side shows the cubes used in the report.
Figure 15-12 Data Providers pane
236
You can also examine the SQL generated by BusinessObjects in the SQL Viewer, accessed from the Query Panel:
Figure 15-13 SQL Viewer
Internal handling of multiple cubes When processing a report that contains multiple cubes, BusinessObjects fuses all cubes into a single cube. Here is the cube for the above example:
Figure 15-14 Single cube
There is no true relationship between the Year and Reservation Year objects in this cube. The cube contains two different kinds of information, based on the following incompatible objects: Revenue by Country by Year Future Guests by Country by Reservation Year
BusinessObjects
237
This information is synchronized around one common dimension, Country, but the relationship between Year and Reservation Year for any particular row is arbitrary. Incompatible objects and filters There may be an issue if you apply a filter on, for example, the Reservation Year column and include the shaded rows only in the report. If you restrict Reservation Year to FY96, the cube produces the following data:
Figure 15-15 Year omitted from report
The Revenue column displays incorrect data. It shows the revenues for France and the US for FY93. However, because Year (the second object around which Revenue is aggregated) does not appear in the report, it should show the total revenues for France and the US, irrespective of year. (That is, by Countrythe other object on which Revenue is aggregated.) In other words, the aggregation of revenue by country is unrelated to Reservation Year. Cube filtering Cubes are filtered either internally by BusinessObjects, or when a user applies a filter. When BusinessObjects is working with cubes behind the scenes, or when the user drills on a report, BusinessObjects sometimes applies internal filters. The NoFilter() function When you use the NoFilter() function, BusinessObjects ignores any user-defined filters when performing calculations. In 5.1.3, NoFilter() may cause BusinessObjects to ignore internal filters (filters applied by BusinessObjects when processing cubes), which causes incorrect results. Incompatible objects in 5.1.4+ In BusinessObjects 5.1.4+, user-applied filters have no effect on unrelated aggregations when a block contains incompatible objects. In behind-the-scenes processing, BusinessObjects ensures that filters do not affect unrelated aggregations. The NoFilter() function no longer causes BusinessObjects to ignore internal filters. These changes ensure that BusinessObjects returns correct data from blocks with incompatible objects.
238
MultiCube() function The MultiCube() function ensures that BusinessObjects takes all cubes into account when performing calculations in reports that contain synchronized queries. If you used MultiCube() in your reports, do not remove it even after activating the solution provided in BusinessObjects 5.1.4. You still need to use MultiCube() in 5.1.4. Aggregation levels in synchronized data providers Whenever you work with synchronized data providers, pay close attention to the structure and semantics of your data, because certain anomalies can arise from the data structure. The section Indirect filters and calculations on page 227 provides an example. Recall that the data provider Q1 contains (Country, Resort, Revenue) and that Q2 contains (Country, Future Guests). You build a block that contains dimensions and measures from both data providers:
Figure 15-16 Q1 and Q2 data providers
The Sum and Count figures for the Future Guests column are anomalous. Future Guests is compatible with both Country and Resort, yet it is placed in the third block from a data provider that aggregates solely by Country.
BusinessObjects
239
As a result, BusinessObjects recognizes only two values for Future Guests (which is why the sum is anomalous) and does not calculate future guests by country and resort (which is why the values for the two US resorts are anomalous). You remove this anomaly by including the Resort dimension in the data provider that contains Future Guests. The block below also includes Future Guests from an additional data provider, Q3, which contains Country, Resort, and Future Guests:
Figure 15-17 Q3 included
In general, if you place a measure from one data provider in a block containing dimensions from another data provider that are compatible with the measure, make sure that the measure's data provider contains all the compatible dimensions in the block. This ensures that the measure is aggregated at the correct level in the block.
Changes made in version 6.1

The changes made in BusinessObjects version 6.1 affect: the Count() function filtering on empty values filters on master detail reports containing incompatible objects rankings the NoFilter() function duplicate row aggregation
240
This means that your BusinessObjects reports could be affected, if they contain: blocks with objects from different data providers and the Count() function to count the rows in the blocks filters that apply to objects containing empty values master/detail reports with incompatible objects in the section header, and body and filters applied to the header rankings in blocks that contain empty values and objects from different data providers the NoFilter() function used with a Where clause blocks with the Avoid Duplicate Rows Aggregation setting activated Count() function Count() is a BusinessObjects function that calculates the number of rows in a data provider. Your reports may be affected if they contain multiple cubes, multiple data providers, and the Count() function. Multiple cubes occur when a BusinessObjects query contains incompatible objects. As a result, BusinessObjects splits the query into two or more cubes in order to resolve it. You cannot control the creation of multiple cubes; it is handled internally by BusinessObjects. Multiple data providers occur when you create more than one cube in a report by building the report from more than one data provider. Behavior of the Count() function in BusinessObjects 5.x In the example below, a report contains two queries: Q1 (Country, Year, Reservation Year, Number of Guests) and Q2 (Country). When you run Q1, BusinessObjects cannot resolve it with a single query because the Year and Reservation Year objects are incompatible. BusinessObjects therefore creates two cubes: (Country, Year, Number of Guests) and (Country, Reservation Year). As a result, the report has three cubes: Country, Year, Number of Guests (Q1 cube 1) Country, Reservation Year (Q1 cube 2) Country (Q2) The report contains multiple cubes and multiple data providers. It is this combination that causes the Count() function to return different results in BusinessObjects 5.x and 6.1.
BusinessObjects
241
If you create a block that contains the Country object from Q2 and the Number of Guests object from Q1, and then apply the Count() function to the Number of Guests column, you obtain the following result:
Figure 15-18 Count function on Number of Guests
The underlying cube created by BusinessObjects to build the block contains empty values, because not all countries have a value for Number of Guests. (See Filtering on empty values on page 242.) BusinessObjects 5.x counts these empty values when performing calculations using the Count() function. Behavior of the Count() function in version 6.1 BusinessObjects 6.1 no longer counts the empty values, so that the Count() function for this block returns 2 rather than 7.
242
Obtaining 5.x results in 6.1 To obtain BusinessObjects 5.x results, apply the Count() function to a column that does not contain empty values. In the example, the formula for the total is Count(<Number of Guests>). If you change this to Count (<Country(Q2)>), you obtain the BusinessObjects 5.x result:
Figure 15-19 Applying the Count function
Filtering on empty values Empty values occur in a BusinessObjects report for one of two reasons: A query returns empty values For example, SQL queries containing outer joins often return NULL values. BusinessObjects internal cube processing creates a cube that contains empty values For example, the cube underlying the block in the example for the Count() function described above. If you have reports with filters on objects that return empty values, they are affected by the enhancement to BusinessObjects filter capability.
BusinessObjects
243
Filtering on empty values in BusinessObjects 5.x In BusinessObjects 5.x, you cannot select an empty value when creating a filter. The following block is taken from the example for the Count() function above:
Figure 15-20 Filtering on empty values
244
The block has empty values because not all countries have a figure for Number of Guests. If you want to filter on the Number of Guests column, you only need to select the non-empty values:
Figure 15-21 Selecting non-empty values
BusinessObjects
245
Filtering on empty values in BusinessObjects 6.1 BusinessObjects 6.1 allows you to include the empty values in the filter definition:
Figure 15-22 Including empty values in filter definition
This allows you to build filters that, for example, exclude all empty values from the report. Filters in master/detail reports with incompatible objects Filters behave differently in BusinessObjects 6.1 in master/detail reports that contain incompatible objects in the section header and body. Your reports may be affected by this issue if they contain incompatible objects that appear in the header and body sections of a master/detail report.
246
Filters in master/detail reports with incompatible objects in 5.x Consider a report that contains the Country, Resort, Year, Reservation Year, and Revenue objects. (Year and Reservation Year are incompatible objects.) Reservation Year appears in the section header; the section body contains a block with Country, Year, and Revenue. If you apply a filter on Reservation Year, for example Reservation Year=FY98, the filter causes the entire contents of the block in the section body to be filtered:
Figure 15-23 Entire contents of block filtered
Filters in master/detail reports with incompatible objects in 6.1 In BusinessObjects 6.1, the filter on the object in the section header (in this case Reservation Year=FY2001) does not impact the objects in the section body:
Figure 15-24 Objects not affected by filter
Rankings in blocks with different data providers and empty values In version 6.1, ranking returns correct sub-totals in reports from rankings on blocks that contain objects from different data providers and empty values. Your reports may be affected by this if they contain rankings with sub-totals in blocks that contain objects from different data providers and empty values.
BusinessObjects
247
Ranking in 5.x Consider a report with two queries: Q1 (Country) and Q2 (Country, Resort, Number of Guests). The report has a block that contains Country (Q1), Resort, and Number of Guests. You rank the top country by Number of Guests and include sub-totals in the ranking:
Figure 15-25 Sub-totals included in ranking
The Sum and Sum Other totals are incorrect. Sum totals all Number of Guest figures in the report, rather than those left in the block by the ranking. Sum Other does not include the figures excluded from the block by the ranking. Ranking in 6.1 In BusinessObjects 6.1, all the sums are correct:
Figure 15-26 All sums correct
Syntax of the NoFilter() function with a Where clause NoFilter() is a function that tells BusinessObjects to ignore all filters when calculating a value. Your reports may be affected by this if they use the NoFilter() function with a Where clause.
248
NoFilter()Where in 5.x Consider a report containing the Resort, Services, and Revenue objects. You apply a filter on Services to retain the value Bungalow only. The function NoFilter(<Revenue>) returns the total revenue for all services because it ignores the filter. You can refine the NoFilter() function with a Where clause; for example,
NoFilter(<Revenue>) Where (<Service> = "Excursion")
returns the total revenue for all Excursion services. In 5.x, it does not matter where you place the parentheses that enclose the input to the NoFilter() function. For example,
NoFilter (Sum(<Revenue>) Where (<Service>="Excursion"))
and
NoFilter ((Sum(<Revenue>)) Where (<Service>="Excursion")
return the same result. NoFilter()Where in 6.1 In 6.1, the position of the NoFilter() parentheses is critical.
NoFilter (Sum(<Revenue>) Where (<Resort>="Bahamas Beach"))
returns the same value as BusinessObjects 5.x, whereas

NoFilter ((Sum(<Revenue>)) Where (<Service>="Excursion")
returns an empty value. When you use the second syntax, BusinessObjects does not apply the NoFilter() function to the sum before applying the Where clause. As a result, BusinessObjects returns an empty value, because the addition of the filter (Service=Bungalow) followed by the Where clause (Service=Excursion) excludes all revenue values.
Figure 15-27 NoFilter()...Where in 6.1
BusinessObjects
249
Obtaining 5.x results in 6.1 To obtain BusinessObjects 5.x results, ensure that your NoFilter()Where functions and variables use the syntax that returns the same result as 5.x. Duplicate row aggregation The Avoid Duplicate Row Aggregation setting for a block tells BusinessObjects to return a single row for all rows where all column values are duplicated across multiple rows. When you select this option in a block in a report with multiple data providers, BusinessObjects ignores sorts on the block. Duplicate row aggregation in 5.x In the following example, there are two data providers, Q1 (Customer, Reservation Year) and Q2 (Customer). You create a block from Customer and Reservation Year (both from the same data provider) and place a sort on Customer in the block. When you include all rows in the table (including duplicates) by selecting the Avoid Duplicate Rows Aggregation option, BusinessObjects ignores the sort on Customer:
Figure 15-28 Ignoring the sort on Customer
250
When you exclude duplicate rows from the table by deselecting the option, BusinessObjects sorts the table on the Customer object:
Figure 15-29 Table sorted for Customer
Duplicate row aggregation in 6.1 BusinessObjects 6.1 applies the sort whether or not the Avoid Duplicate Rows Aggregation option is selected.
BusinessObjects
251
Basing a query on an existing query

Starting with version 6.1, you can base a query on an existing query within the BusinessObjects Query Panel. In the current version, the following data sources are supported: Universes Personal OLAP Connect OLAP Access Packs For more information, see the BusinessObjects Users Guide: Accessing Data and Data Analysis.
Basing a query on an existing query
252
BusinessObjects
Designer and BusinessQuery for Excel
chapter
254
Overview
This chapter covers the upgrading of Designer and BusinessQuery for Excel.
255
Designer
Designer is one of the administration products (formerly a desktop product). You upgrade Designer when you uninstall version 5.x desktop products and reinstall version 6.x administration products. (See Reinstall desktop and administration products on page 58.) After the upgrade, you continue working with the same universes as before. Full compatibility is maintained. All version 2.x/5.x universes and their associated lists of values must be saved in Designer 6.x before they can be exported to a version 6.x repository. Business Objects recommends that you export any universes from a local drive to the 5.x repository before upgrading. For more information on Designer, see the Designers Guide.
LOV files
If you have version 5.x universes with customized LOV (list of value) files, you must re-export these universes in order to use the LOVs in version 6.x.
Compatibility
There is full upward and downward compatibility between 5.x and 6.x universes, as indicated in the table below. A version 6.x and a 5.x Designer can be installed and function on the same machine.
Can a ...
Be used ... in 6.x Designer and by 6.x users in 5.x Designer and by 5.x users Yes Yes
6.x universe 2.x/5.x universe
Yes Yes
Designer
256
Can a ... 6.x Designer 5.x Designer Yes No
Function on a ... 6.x repository 2.x/5.x repository No Yes
257
BusinessQuery for Excel

BusinessQuery for Excel is one of the desktop products. You upgrade BusinessQuery when you uninstall version 5.x desktop products and reinstall version 6.x. (See Reinstall desktop and administration products on page 58.) The format of BusinessQuery files has not changed in the transition to version 6.x. Therefore: BusinessObjects version 6.x can open, edit, and save BusinessQuery files coming from version 5.x. BusinessObjects 5.x can open, edit, and save BusinessQuery files coming from version 6.x.
Upgrading from version 4.1

You cannot upgrade directly from BusinessQuery version 4.1 to the current version. You must first upgrade to 5.1. For more information, see the BusinessQuery for Excel Users Guide.
BusinessQuery for Excel
258
Developer Suite
chapter
260
Overview
This chapter covers upgrading Developer Suite from version 5.x to 6.x. The discussion here provides a brief overview; for detailed instructions, see the Developer Suite Migration Guide. Developer Suite contains several SDKs: BusinessObjects SDK WebIntelligence SDK Administration SDK You upgrade Developer Suite when you uninstall version 5.x and reinstall version 6.x. This installation is separate from the installation of the Business Objects server, desktop, and administration products.
Changes in supported applications

The following SDK components are no longer supported in version 6.x: Report Viewer Component (part of BusinessObjects SDK) BusinessQuery SDK For applications using these components, you must rewrite the scripts, replacing calls to these SDKs with calls to WebIntelligence SDK or BusinessObjects SDK.
Developer Suite
261
BusinessObjects SDK
BusinessObjects SDK provides you with the tools you need to customize and extend BusinessObjects and Designer. All SDK applications based on version 5.x continue functioning after 6.x is installed.
Upgrading VBA 5.0 scripts to VBA 6.2

A VBA (Microsoft Visual Basic for Applications) script is a program contained within a BusinessObjects document (.rep) or BusinessObjects add-in (.rea). A Visual Basic program is a compiled program developed using Visual Basic. Both use BusinessObjects SDK. Version 2.x/5.x hosted VBA 5.x code, whereas version 6.x hosts VBA 6.2. In Business Objects 6.x, VBA 5.x scripts continue to execute as before. To upgrade a 5.x VBA script, edit and save it in a Business Objects version 6.x application. If the script is not edited or saved, it will remain in its previous version. After you edit and save a VBA script in 6.x, it can no longer be viewed, edited, or executed in 2.x/5.x applications. You can broadcast version 5.x documents using custom scripts. Broadcasting alone does not change the version of the script.
SBL scripts
BusinessObjects 4.x custom applications were created using SBL scripts. It is not possible to upgrade SBL scripts directly to VBA 6.2. You must first upgrade them to VBA 5.0 using BusinessObjects 5.x. For more information, see the version 5.x BusinessObjects SDK Reference Guide.
BusinessObjects SDK
262
WebIntelligence SDK
If an application uses a directory or some of its components that have been copied to a custom location, you need to replace them with the corresponding directories or components for WebIntelligence 6.x.
WebIntelligence applets and ActiveX components

An application may contain references to WebIntelligence 2.x applets or ActiveX components. For example, a reference to launch the query panel. In WebIntelligence 6.x, these components may not have the same name. If this is the case, you must update the reference in the code.
WebIntelligence Reporting SDK

The 5.x WebIntelligence Reporting SDK component has been replaced in version 6.x by the reporting package (REBean or RECOM) included in WebIntelligence SDK. If your application uses Reporting SDK, replace any JSP pages that use it with pages that use the reporting package of the WebIntelligence SDK. For more information, see the Customizing WebIntelligence guide.
Changes in HSAL
There are a number of differences in the HSAL between WebIntelligence versions 2.x and 6.x. For example, in version 2.x/5.x, the HSAL component is provided in many different technologies: CGI, NSAPI, DSO, ISAPI, and as a servlet. In version 6.x, the HSAL is delivered only as an ISAPI dll and as a jhsal servlet. Depending on your Developer Suite 5.x and application server configuration, the HSAL may be referenced using: the default_HsalPath parameter in the wibean.orb.properties file the getHsalPath and setHsalPath methods of the WIBean package, called from an ASP or JSP script page the following WIServer constructor: WIServerImpl(String sORBagentAddr, String sORBagentPort, String sHTTPServerURL, String sHsalPath) You must modify references to the HSAL, depending on your 6.x deployment, and whether the application uses the CGI, NSAPI or DSO version of the HSAL.
Developer Suite
263
Changes in the WICOM/WIBean

The WebIntelligence SDK components WICOM and WIBean are equivalent versions of the WebIntelligence object. WICOM is a Microsoft Common Object Model object that you use to access WebIntelligence using ASP. WIBean is a Java package that you use to access WebIntelligence using JSP. To access the WebIntelligence functions exposed by these components, an application must have access to WICOM or WIBean. In Developer Suite 6.x, you access WICOM250.dll in the same way as in 5.x. Web applications created for Developer Suite 5.x can access the Developer Suite 6.x WICOM250.dll. You do not need to modify the web application. You must change the WIBean used by your applications so that they use the version 6.x WIBean. In Developer Suite 5.x, there are multiple methods an application can use to access the WIBean. In 6.x, WebIntelligence SDK web applications must be deployed as a WAR file and the WebIntelligence SDK components must be contained within the file. You must place the SDK core components inside the WAR file in order to be deployed by the version 6.x Configuration Tool.
Orb parameters
In WebIntelligence 6.x, the orb has been updated. The orb parameters used to locate the WebIntelligence cluster are now set directly when the application is deployed, using information entered into the Configuration Tool.
WebIntelligence documents
When you migrate an application to a WebIntelligence 6.x environment, it can still view WebIntelligence 2.x documents. To view and edit WebIntelligence 6.x documents, you need to use the WebIntelligence SDK REBean or RECOM package in Developer Suite 6.x. When you open a WebIntelligence 2.x document using REBean or RECOM, it is opened as a WebIntelligence 6.x document. You can then save the converted document and replace the existing WebIntelligence 2.x document. For more information and instructions, see the Developer Suite Migration Guide.
WebIntelligence SDK
264
The OpenDocument function

The OpenDocument function enables you to open a WebIntelligence or BusinessObjects document using a URL. You can create a hyperlink to a document from a report or an HTML page. An OpenDocument URL contains the following two parts, separated by a question mark (?): the path for your implementation of OpenDocument parameters Parameters are separated by an ampersand (&). For example: http://ServerName/OpenDocumentImplementation? Param1=Value1
&Param2=Value2
The following sections describe the WebIntelligence 2.x and InfoView 6.x implementations and explain how to migrate a 2.x OpenDocument URL to 6.x.
OpenDocument in WebIntelligence 2.x

In WebIntelligence 2.x, there are three implementations of the OpenDocument function: WIGenerator module of the WebIntelligence server, with the path: http://ServerName/wi/bin/iswi.dll/WIGenerator/ wigenerator/generator/OpenDocument WebIntelligence ASP sample of Developer Suite 5.x, with the path: http://ServerName/wiasp/openDocument.asp WebIntelligence JSP sample of Developer Suite 5.x, with the path: http://ServerName:PortNumber/wijsp/openDocument.jsp
Developer Suite
265
OpenDocument in InfoView 6.x

In InfoView 6.x, there are two implementations of the OpenDocument function: JSP script, openDocument.jsp ASP script, openDocument.asp One of these scripts is installed when you deploy InfoView, depending on whether you are using JSP or ASP. The following are the paths to access the scripts: http://ServerName:PortNumber/VirtualDirectory/scripts/ openDocument.asp http://ServerName:PortNumber/VirtualDirectory/scripts/ openDocument.jsp VirtualDirectory is the virtual directory you specify in the Configuration Tool when you deploy InfoView. By default, it is wijsp for InfoView using JSP and wiasp for InfoView using ASP.
Migrating an OpenDocument URL

To migrate an existing 2.x OpenDocument URL to 6.x, change the 2.x path to one of the paths shown in the previous section (OpenDocument in InfoView 6.x). The URL will then function properly in a 2.x document that you open in 6.x InfoView. However, when you upgrade a WebIntelligence 2.x document to 6.x, the migrated URL will not function in the upgraded 6.x documenteven if you changed the path. This is because the document is assigned a new document ID and document type. After you upgrade the document to version 6.x: 1. Change the old 2.x document ID in the URL to the new 6.x ID. 2. Change the value of the document type in the URL to wid. The URL will then function properly in the upgraded 6.x WebIntelligence document.
NOTE
URLs are case sensitive on all systems except IIS.
The OpenDocument function
266
EXAMPLE Migrating a URL
The following URL uses the WebIntelligence 2.5 WIGenerator implementation of OpenDocument to open the EFASHION document and set Dallas and Chicago as the values for the City prompt:
<a href=http://ServerName/wi/bin/iswi.dll/WIGenerator/ wigenerator/generator/OpenDocument?DocumentName=EFASHION& sDocType=W&iDocId=109&sRepo=Document&sOpen=Y& lsCBMxCity=Dallas&lsCBMxCity=Chicago>Efashion in Dallas and Chicago</a>
To fully migrate the URL for an ASP deployment of InfoView 6.x, you replace the path and the document ID:
<a href=http://ServerName/wiasp/scripts/openDocument.asp? DocumentName=EFASHION&sDocType=wid&iDocId=132&sRepo=Documen t& sOpen=Y&lsCBMxCity=Dallas&lsCBMxCity=Chicago>Efashion in
Dallas and Chicago</a>
Developer Suite
Supervisor
chapter
268
Overview
You upgrade Supervisor from version 5.x to 6.x as part of the broader procedure of upgrading the repository. The basic process is outlined in Chapters 3 and 4. (See Phase 2 Copy and upgrade the repository on page 55 This chapter provides additional, more detailed information about upgrading Supervisor, including security commands and compatibility issues between versions 5.x and 6.x.
Supervisor
269
Security commands
You can restrict access to areas of functionality by using security commands, which are grouped into families. A security command corresponds to a set of one or more menu items and other interface elements such as toolbar buttons or shortcut menu commands. (For more information, see the Supervisors Guide.) All security commands from version 2.x/5.x that are used in 6.x are transferred to version 6.x Supervisor when the repository is upgraded. A few commands have slight changes in their name. Some 2.x/5.x commands are no longer used in 6.x, but they still appear in Supervisor. This has no impact on the functioning of the version 6.x Business Objects system. The version 5.x security commands Formatting Toolbar and Transparent Drill Outside of Cube have no relevance to the version 6.x Java Report Panel or HTML Report Panel. These commands are used in 6.x InfoView only for 2.x documents, and they are identified in 6.x Supervisor by a special icon. Because some users in your organization may still be using version 2.x/5.x while migrating to 6.x, the version 6.x Supervisor lets you manage commands for both versions. In 6.x Supervisor, commands can no longer be viewed by menu, as in 5.x Supervisor.
Changes in security commands

The following two tables summarize the changes made in security commands in the transition to version 6.x. The first table shows new commands only whereas the second shows all changes that were made.
Security commands
270
New commands Application

Supervisor
Command family
Miscellaneous
New command
Manage my hierarchical categories Manage all hierarchical categories
Administrate Broadcast Agents Administrate clusters, modules, and audit Administrate user sessions Log into Administration Console
BusinessObjects
Documents
Refresh view of document list and categories Manage my corporate categories Manage all corporate categories
Supervisor
271
Application
WebIntelligence
Command family
Administration
New command
Download BusinessObjects Use interactive viewing Use WebIntelligence Java report panel Use WebIntelligence HTML report panel
Analysis InfoView
Extend scope of analysis Generate in Excel format Generate in PDF format Manage my hierarchical categories Manage all hierarchical categories Refresh view of document list and categories Upload documents
Query and Reporting
Create document templates Edit query Use formula language/ create variables
Security commands
272
All changes Application

Supervisor
Command family
Miscellaneous
Command
Change made
Manage my New command hierarchical categories Manage all New command hierarchical categories
New command group Administrate Broadcast Agents Administrate clusters, modules, and audit Administrate user sessions New command New command New command
Log into Administration New command Console BusinessObjects Documents Refresh view of document list and categories Manage my corporate categories Manage all corporate categories Do not manage categories WebIntelligence Administration Download BusinessObjects Change password Allow to use WebIntelligence Java report panel New command
New command New command Deleted New command group New command Moved from Options command group New command
New command Allow to use WebIntelligence HTML report panel
Supervisor
273
Application
Command family
Analysis
Command
Change made
New command group
Allow to extend scope of analysis Transparent drill outside of cube Work in drill mode
New command Moved from Query and Web Panel command group Moved from Query and Web Panel command group New command group
InfoView Do not delete other users corporate documents Do not manage repository categories Download BusinessObjects 4.x documents Download BusinessObjects 5.x documents Download WebIntelligence documents
Moved from Document command group Deleted Moved from Document command group Moved from Document command group Moved from Document command group
Manage my New command hierarchical categories Manage all New command hierarchical categories Manage personal categories Save to corporate documents Moved from Document command group Renamed; formerly Publish documents. Moved from Document command group
Security commands
274
Application
Command family
Command
Read corporate documents
Change made
Moved from Document command group
Read inbox documents Moved from Document command group Run and refresh documents Refresh view of document list and categories Save document Schedule documents Moved from Query and Web Panel command group New command
Moved from Document command group Moved from Query and Web Panel command group Moved from Document command group Moved from Document command group New command Renamed; formerly Change list display and default home page Group renamed; formerly Query and web panel
Send documents to users in other groups Send documents to users in own group Upload documents Options Customize the interface
Query and Reporting Create document templates Edit query
New command New command
Use formula language/ New command create variables Use list of values Renamed; formerly Use and refresh list of values
Supervisor
275
Compatibility
Version 6.x and 5.x Supervisor can be installed and function on the same machine.
Can ... 6.x Supervisor 5.x Supervisor 6.x Designer 5.x Designer 6.x BusinessObjects 5.x BusinessObjects Yes No Yes No Yes Yes
Function on a ... 6.x repository 5.x repository No Yes No Yes No Yes
Can a ... 6.x document 2.x/5.x document Yes Yes
Be stored in a ... 6.x repository 5.x repository No Yes
Compatibility
276
Hierarchical categories and Supervisor

In general, version 2.x/5.x categories are upgraded by the system to 6.x categories. However, hierarchical categories, a new feature in version 6.x, are treated somewhat differently. Hierarchical categories can be used in version 2.x/5.x, but not managed in 2.x/ 5.x. Therefore, some user rights are altered in Supervisor after the upgrade occurs. Users that had the right to manage categories in 2.x/5.x have an equivalent right in 6.x. To prevent 2.x/5.x users from managing hierarchical categories, the following happen automatically when Supervisor is upgraded: All 2.x/5.x security commands related to flat category management are set so that category management in 2.x/5.x becomes prohibited. All 6.x security commands related to hierarchical category management are set so that category management in 6.x becomes prohibited by default. The right to manage can then be assigned to individual users and user groups. The previous set of security commands for managing categories in version 2.x/ 5.x no longer appears in 6.x Supervisor. They are now hidden commands that exist only in the database. For more information on hierarchical categories, see Categories on page 291.
Supervisor
277
Channels
Because there are no channels in version 6.x, the Manage Channels button has been removed from the Broadcast Agent tab in the Group Properties dialog box.
Channels
278
Changes in SQL
The version 6.x repository, with all its domains, is basically unchanged compared to 5.x. There are no new columns or tables, only new types of data (such as the version number of the repository). This new data has resulted in several changes in the SQL of the 6.x repository, as described below.
Repository version number

The repository version number was changed from 0 in version 5.x to 1 in version 6.x. This change is registered in the OBJ_M_GENPAR table of the 6.x repository:
update OBJ_M_GENPAR set M_GENPAR_N_TYPE = 0 , M_GENPAR_N_VALUE = 1 , M_GENPAR_C_LABEL = '<Id that was already present>' where M_GENPAR_N_ID = 121 and M_GENPAR_N_APPLID = 0 and M_GENPAR_N_USERID = 0
Security commands
To prevent 2.x/5.x users from managing hierarchical categories after Supervisor is upgraded to 6.x, the 2.x/5.x category commands are automatically transformed into new 6.x category-related commands. When this change is made, the following occurs in the 6.x repository:
NOTE
IDSECCMD_DAR_xxx are WebIntelligence commands, IDSECCMD_ADM are for Supervisor, and IDSECCMD_Managexxx are for BusinessObjects. When the word hierarchical appears in the name, the command is a 6.x one; otherwise, its 2.x/5.x.
select M_RES_N_ID, M_RES_N_ACTLINKID, M_RES_N_RESID, M_RES_N_STATUS, M_RES_N_LAD, M_RES_N_LAT from OBJ_M_RESLINK where M_RES_N_RESTYPE = 7
(retrieves all security commands)

if m_n_resid == IDSECCMD_DAR_MANAGEREPOSITORYCATEGORIES m_n_resid is set (in memory) to IDSECCMD_DAR_MANAGEMYHIERARCHICALCATEGORIES
Supervisor
279
or m_n_resid== IDSECCMD_MANAGECATEGORIES m_n_resid is set (in memory) to IDSECCMD_MANAGEMYHIERARCHICALCATEGORIES or m_n_resid == IDSECCMD_ADM_TOOLCATEGORIES m_n_resId is set (in memory) to IDSECCMD_ADM_MANAGEMYHIERARCHICALCATEGORIES Then, for each security command matching the previous condition:
update OBJ_M_RESLINK set M_RES_N_ACTLINKID = <m_res_n_actlinkid> , M_RES_N_RESID = <m_res_n_id> , M_RES_N_RESTYPE = 7 , M_RES_N_STATUS =<m_res_n_status> , M_RES_N_LAD = 1015437562 , M_RES_N_LAT = 4(update) where M_RES_N_ID = <m_res_n_id>
If there are record sets with m_n_resid = IDSECCMD_ADM_TOOLCATEGORIES, an additional insert is created:
insert into OBJ_M_RESLINK (M_RES_N_ID, M_RES_N_ACTLINKID, M_RES_N_RESID, M_RES_N_RESTYPE, M_RES_N_STATUS, M_RES_N_LAD, M_RES_N_LAT) values (<new record id> , <m_res_n_actlinkid> , IDSECCMD_ADM_MANAGEALLHIERARCHICALCATEGORIES , 7 , <status> , <date> , 2)
Note the following: All 2.x/5.x security commands related to flat category management are set so that category management in 2.x/5.x becomes prohibited. All 6.x security commands related to hierarchical category management and the new commands related to the Administration Console are set for the root group. This means that category management in 6.x becomes prohibited by default, with the exception of any commands that were set in the steps described above (at the root group). The right to manage can then be assigned to individual users and user groups. To accomplish this, the following occurs for new commands that are deactivated at the root level:
insert into OBJ_M_RESLINK (M_RES_N_ID, M_RES_N_ACTLINKID, M_RES_N_RESID, M_RES_N_RESTYPE, M_RES_N_STATUS, M_RES_N_LAD, M_RES_N_LAT) values (<new record id> , 1(root), <command id >, 7 , 2(disabled) , <date> , 2)
with the command ID taken from among:
Changes in SQL
280
NOTE
Some commands are labeled as positive or negative. This is because during the migration step, the status of the commands phrased in the negative is changed before being applied to new commands, to reflect the actual rights. For example, if the (negative) DAR_manage_categories is Enabled, the status of the new DAR_manage_my_hiera_categ is set to Disabled. Similarly, when disabling the 2.x/5.x commands, the actual status applied to WebIntelligence and BusinessObjects commands phrased in the negative is Enabled, so that the actual rights are denied. // Old flat category commands (5.0) IDSECCMD_DAR_MANAGEREPOSITORYCATEGORIES Negative IDSECCMD_MANAGECATEGORIES , // Busobj Negative IDSECCMD_ADM_TOOLCATEGORIES For the new hierarchical categories: IDSECCMD_MANAGEMYHIERARCHICALCATEGORIES IDSECCMD_MANAGEALLHIERARCHICALCATEGORIES , , , , , // Supervisor Positive , // Webi
IDSECCMD_ADM_MANAGEMYHIERARCHICALCATEGORIES IDSECCMD_ADM_MANAGEALLHIERARCHICALCATEGORIES IDSECCMD_DAR_MANAGEMYHIERARCHICALCATEGORIES , IDSECCMD_DAR_MANAGEALLHIERARCHICALCATEGORIES For the new commands related to the Administration Console: IDSECCMD_WEBADM_LOGON IDSECCMD_WEBADM_CLUSTER IDSECCMD_WEBADM_SESSIONS IDSECCMD_WEBADM_BCA , , ,
Supervisor
WebIntelligence and InfoView
chapter
282
Overview
WebIntelligence is one of the server products. You upgrade WebIntelligence when you uninstall version 2.x server products and reinstall version 6.x. This procedure is part of the cluster upgrade, which is covered in depth in Chapters 3 and 4. This chapter presents some additional information regarding the upgrading of the WebIntelligence and InfoView products. This includes detailed information about upgrading documents, as well as the differences in the way documents are viewed and used in versions 2.x and 6.x.
NOTE
To upgrade BusinessObjects (3-tier mode) from InfoView, see Troubleshooting on page 301.
283
The Administration Console (called the Services Administrator in version 2.x) is one of the administration products. You upgrade the 2.x Services Administrator to the 6.x Administration Console when you uninstall version 2.x and reinstall version 6.x desktop and administration products. (See Reinstall desktop and administration products on page 58.) After installation, you must configure the Administration Console using the Configuration Tool. When you open the new Administration Console, you will see different modules than in version 2.x. These no longer exist in version 6.x: - WIGenerator - WIHSALManager These are new in version 6.x: - Administration server - WILoginServer - WIQT - WIReportServer Additional changes in the new Administration Console: The internal.log file no longer exists. The WIAPIBroker module has a new parameter, called Cleanup Period. Enable/Disable Broadcast Agent Manager has been replaced by Start/Stop All Schedulers. You do not need to use a System Administrator account.
Compatibility
Can a ... 6.x Administration Console 2.x Services Administrator Yes No Function on a ... 6.x cluster 2.x cluster No Yes
284
Upgrading WebIntelligence documents

NOTE
Upgrade of WebIntelligence 2.x documents in 6.x is supported only for version 2.5 or later. Earlier version 2.x documents can only be viewed in 6.x. To upgrade WebIntelligence documents: 1. Open the WebIntelligence 2.x document in 6.x InfoView. 2. Click Edit. 3. Make any modifications you want (optional). 4. Save the document as a personal or corporate document. The extension is changed from .wqy to .wid. That is, the document is upgraded to version 6.x. The former 2.x (.wqy) document remains in the repository. It will be accessible to all users on the cluster, but will appear with a different icon than the 6.x document with the same name. If you want to eliminate such documents, you must delete them manually. After you upgrade InfoView to 6.x, users will see the same documents they previously had the right to view in their InfoView document lists. A WebIntelligence 2.x document can be viewed, refreshed, and drilled in version 6.x InfoView, and the format remains 2.x. WebIntelligence version 6.x (.wid) documents cannot be viewed in InfoView 5.x.
Cells set to automatic size

By default, table cells set to automatic size in WebIntelligence version 2.x are set to AutoFit in version 6.x. WebIntelligence documents with many cells set to automatic size may take a long time to open in InfoView 6.x. Therefore, migrating these documents could be time-consuming. If you are migrating many such documents, consider doing one or both of the following: Perform the migration at a time when server use is minimal. Before migrating the documents, change the cell settings from automatic size to a fixed size.
285
Changing automatic size to fixed size To change the cell setting from automatic size to a fixed size in a WebIntelligence document (before migration): 1. Open the document in InfoView version 2.x (v. 2.5 or later). 2. On the Settings page of the web panel, clear the Automatic Size box.
Figure 19-1 Automatic Size box
3. In the Cell Width box, set the fixed size you want. 4. Save the document. You can now migrate the document to version 6.x.
Objects tagged as HTML

This feature enables you to provide a hyperlink from values displayed in a report to a WebIntelligence or BusinessObjects report (or to a web page). For example, if you have a sales revenue report that displays annual results by region, you could include a hyperlink on the table column for region. This would link to a report containing detailed information about the sales force in that region. In WebIntelligence 2.x documents, the HTML tag that contains the hyperlink information is created at the universe level using Designer. When you upgrade WebIntelligence 2.x documents containing HTML tagged objects to version 6.x, you need to set the format properties for the report cells that contain the objects. This ensures that the HTML tag is properly displayed in the Java Report Panel or when saving in PDF or Excel format.
Upgrading WebIntelligence documents
286
To format cells containing HTML-tagged objects: 1. Open the upgraded version 6.x WebIntelligence document in Edit mode. Use the WebIntelligence Java Report Panel as your document editor. 2. In Report view, click a table cell, section header, or free-standing cell containing an HTML tagged object. 3. Click the Cell properties sub-tab. 4. Under Display, select the Read content as checkbox. 5. Click the arrow next to the drop-down list, and then select Hyperlink. If you selected a cell in a table, the Hyperlink property is applied to all of the cells in the same column or row as the selected cell. If you selected a section header, the Hyperlink property is applied to all of the section headers in the selected section. 6. Repeat steps 2 - 5 for any other report cells containing objects tagged as HTML.
287
Differences between 2.x/5.x and 6.x

Substantial improvements were introduced in WebIntelligence and InfoView version 6.x. This section focuses on changes that have an impact on upgrading. For more information, see Whats New in WebIntelligence in the WebIntelligence Users Guide.
Compatibility
The tables below review various aspects of document compatibility. Note that retrieve includes all sources: repository, mail, file system, and so on.
Can ...
Do the following with 6.x documents: Retrieve Send or save as corporate Yes No
Yes No
Can ...
Do the following with 2.x WebIntelligence documents: Retrieve Send or save as corporate Yes Yes
Yes Yes
288
Can ...
Do the following with 5.x BusinessObjects documents: Retrieve Send Yes Yes, but document becomes 6.x. Yes Yes Save as corporate Yes Yes, but document becomes 6.x. Yes Yes
6.x InfoView users 6.x BusinessObjects users 2.x/5.x InfoView users 2.x/5.x BusinessObjects users
Yes Yes
Yes Yes
When ... a 2.x WebIntelligence document in InfoView... 6.x users 2.x/5.x users it remains 2.x it remains 2.x
Refresh the following ... a 5.x BusinessObjects document in BusinessObjects... it becomes 6.x it remains 5.x a 5.x BusinessObjects document in InfoView... it remains 5.x it remains 5.x
When ...
Edit, and then save the following ... a 2.x WebIntelligence document... a 5.x BusinessObjects document... it becomes 6.x it remains 5.x
289
Choice of document editors

In version 6.x, you have a choice of document editors: WebIntelligence HTML Report Panel Designed for basic reporting needs, the HTML Report Panel has wizard-like tabs to take you through the steps required to create and format reports. Starting with version 6.1, you can use drag-and-drop features to build a doucment in the HTML Report Panel. The HTML Report Panel is available only in the JSP version of InfoView 6.x. WebIntelligence Java Report Panel Designed for power users. A Java applet is downloaded to your machine the first time you open the report panel from InfoView.
User options/Start page

In InfoView version 5.x, Start page settings were set from the Start Page options. In version 6.x, the Start Page options have been removed. In InfoView version 6.x, you set these parameters on the Display tab, accessed by clicking the Options command at the top of the Start page.
Figure 19-1 InfoView Options command
Interactive viewing
Interactive viewing is a new feature for version 6.x WebIntelligence documents. It enables you, when viewing documents in HTML mode, to perform filtering and sorting on values by accessing a right-click shortcut menu. This is available only in the JSP version of InfoView 6.x.
290
Interactive viewing is activated via the View tab in the Options Pages.
Figure 19-2 Selecting interactive viewing
For more information, and to find out which features you can access via interactive viewing, see the WebIntelligence Users Guide.
Data upgrade
Data is transferred when you edit a WebIntelligence version 2.x document in InfoView version 6.x. There is no need to rerun the query or refresh the document. Upgraded documents containing data are displayed by default in Results mode.
SQL
The SQL used for the View SQL function is not automatically upgraded. After you upgrade a WebIntelligence document, select Refresh in InfoView to regenerate the SQL. There may be differences between the SQL generated in versions 2.x and 6.x; for example, if you modify the document after upgrading but before regenerating the SQL. In InfoView, you can refresh a FreeHand SQL data provider (client/server mode only). FreeHand SQL uses a personal connection, and it is not available in BusinessObjects (3-tier mode).
291
Categories
InfoView version 6.x categories are compatible with version 5.x; no upgrading is required. Documents will appear in the same categories as in 5.x. Corporate documents are the main way to share documents in InfoView. These documents are classified in categories, and publishers grant read-only access to members of user groups. However, hierarchical categoriesa new feature in version 6.xbehave differently. With hierarchical categories, you create subcategories within categories, to any depth you want. You then associate a document with one or more of these categories or subcategories. Each category can have zero, one, or several subcategories. The picture below shows hierarchical categories as they appear in the upper left corner of the InfoView home page. In this example, the root category Geography contains the subcategory Europe. Europe, in turn, contains the subcategories France, Germany, and Italy.
Figure 19-3 Hierarchical categories
Separators, such as underscores or forward slashes, could be used in version 2.x documents to simulate a hierarchical category. If there were no separators in a category name in version 2.x, it is assumed that an artificial hierarchy was not created. Such a category is then interpreted in 6.x as a root category. If there were separators in version 2.x, the category still appears in 6.x as a root category, but with names containing separators. A forward slash is considered to be a separator. In 6.x InfoView, slashes in category names are not supported.
292
You can continue to create 2.x-style categories in version 6.x InfoView by creating, renaming, or deleting root categories with or without their separators. Of course, you can no longer use the slash as a separator. If you create a hierarchical structure in version 6.x InfoView, the 6.x user will see a hierarchy and the 2.x user will see a flat list of categories. The 2.x category, however, will simulate a real hierarchy; for example, the hierarchical category Finance with subcategory Accounting would appear in 2.x as Finance/ Accounting.
Drill
HTML drill is available in version 6.x. Users with the right to drill on 2.x documents can still drill on these documents after they are upgraded to 6.x. When you upgrade a version 2.x document with Drill mode activated, it is displayed in 6.x in Results mode by default. The same applies to any document containing data. Drilling, by itself, does not cause a 2.x document to be upgraded to 6.x. In 6.x, you can use drill filters as query conditions when retrieving additional data during the drill.
Preferred language
Starting with version 6.1, users can set their own default language for InfoView, from among the languages installed on the server. The user must have the right to edit display options. You can change the default, or preferred language, on the Display tab of the InfoView Options Pages.
Headers and footers/Page number

WebIntelligence version 2.x documents have labels in page headers and footers. Labels become cells in 6.x page headers and footers. Page number is activated by default in a 2.x document. This label becomes a cell in the page footer of a 6.x document. Note that migration of the formula for calculating the total number of pages can be time-consuming. The Row Count/Page feature is not upgraded to 6.x because it is no longer applicable. The Last Refreshed date is activated by default in a 2.x document. This label becomes a cell in the page header of a 6.x document.
293
Multiple reports
WebIntelligence version 6.x documents can contain multiple reports, but 2.x documents do not contain them. Therefore, an upgraded 2.x document will contain a single report that has the same name as the document.
Filters
Query conditions (simple filters) in version 2.x are called query filters in 6.x. These advanced query filters enable you to filter a single query according to multiple business criteria. Filters can include prompts, and these are automatically upgraded to version 6.x. Query filter rules and Boolean operators are also upgraded to version 6.x. In WebIntelligence 2.x documents, you can set certain combinations of filters with the OR and AND operators. In 6.x, the HTML Report Panel does not support this combination of filters. This is resolved by the following: The list of operators available in the HTML Report Panel are OR or AND. If there is a complex filter combination (occurring in the Query Filter and Report Filter steps), the value of the filter combination is Custom. You can keep the Custom value or change it (OR or AND). Global filters on measures already present in a 2.x document remain in the document when it is upgraded to 6.x. In a 2.x document, you can sort objects by predefined orders, ascending, and descending. This remains the same in 6.x.
Scope of analysis
In WebIntelligence 2.x documents, you can select a scope of analysis. Version 6.x also has this feature, but all objects in the scope of analysis are moved to the Result Objects list when the document is migrated. This does not affect the result of the query.
Properties (section and cell)

Section Properties in version 6.x are in the Properties tab of the Outline browser when you select a section. Cell Properties in version 6.x are in the Properties tab of the Outline browser when you select a cell. A cell that spans more than one column is upgraded in 6.x along with its formatting (left, right, or centered).
294
The following are not available in 6.x: Padding setting Section settings/table spacing Show as Index Show as Index from Section Cell Settings is available in 6.x as the Show Map feature.
Object formatting
The following three object format properties can be migrated from version 2.x to 6.x: Format number HTML Image All other object format properties (except for custom object formatting) will be handled by cell properties in 6.x.
295
Tables
The following types of tables are supported:
This table in 2.x... Table
becomes this in 6.x... Vertical table
Financial
Horizontal table
Form
Form
Crosstab
Crosstab
Figure 19-4 Tables in versions 2.x and 6.x
Table Properties in version 6.x are in the Properties tab of the Outline browser when you select a table. In a WebIntelligence version 2.x document, a header can be at the top or left side of a table, or both; this is called setting a header on left. This is not supported in 6.x; in an upgraded document, the cell becomes a column or a row. In a 2.x document, a table can have calculations in the table footer. Version 6.x also has this functionality. Version 2.x Header Repetition (Header-Each Row) is not available in version 6.x. Version 2.x documents with this feature are upgraded by adding a row containing a formula that is associated with the header.
296
In version 2.x, you could set the tables border size to any positive, whole integer. In 6.x, border size must be 0, 1, 3, or 5. Border sizes in 2.x are upgraded to the closest equivalent in 6.x.
Charts
In version 6.x, you can build WebIntelligence reports containing multiple blocks. This enables you, for example, to display tables and charts in the same report. Block Properties in version 6.x are in the Properties tab of the Outline browser when you select a chart block. Chart properties in version 6.x are in the Properties tab of the Outline browser when you select a chart. A chart title is a cell. Zero-based axis is not supported in version 6.x. In 6.x, both positive and negative values are displayed.
Legends
Legend properties in version 6.x are in the Properties tab of the Outline browser when you select a legend.
Calculations
In version 6.x, you can create custom calculations. You can reuse formulas as variables in different reports in the same document. You can add calculations to a WebIntelligence version 2.x document, and format the results with cell settings. In version 6.x, these calculations become formulas in a cell. Version 6.x supports the following functions for 2.x numerical values: Sum Count Average Minimum Maximum Version 6.x also supports the following functions for 2.x non-numerical values: Count Minimum Maximum Percentage calculations on sub-breaks and sub-sections are not supported in version 6.x. An empty row appears in the migrated document.
297
Prompts
Version 2.x prompts are shown in 6.x only when the document is refreshed. The behavior of prompts is the same in 2.x and 6.x.
Color
In WebIntelligence version 2.x documents, you can set a custom value for graphical element color by entering an RGB value. In version 6.x, the HTML Report Panel does not support this feature. Instead, the list of available colors is defined with 16 base colors. If you previously set a custom value, it will appear in the list. You can keep this value or change it by selecting one of the 16 default values. If you change it, the previous custom value is removed and is no longer available.
Format number
In WebIntelligence version 2.x documents, you can set a custom value for Format Number. In version 6.x, the HTML Report Panel does not support this feature. Instead, there is a list of available Format Numbers. If you previously set a custom value, it will appear in the list. You can keep this value or change it by selecting one of the list entries. If you change it, the previous custom value is removed and is no longer available.
298
Troubleshooting and FAQ
part
Troubleshooting
chapter
302
Overview
This chapter covers various issues that may arise during the upgrading process. The cause and solution of each issue is discussed. Troubleshooting is divided into the following categories: General installation Repositories Supervisor Document migration WebIntelligence/InfoView BusinessObjects Audit and administration Broadcast Agent For troubleshooting of Developer Suite migration, see the Developer Suite Migration Guide. Often, an issue is signalled by the appearance of an error message. If you receive an error message, see the Error Message Guide for an explanation. Some issues may occur if you are migrating users to an LDAP corporate directory. See the LDAP Security Connector Guide.
Troubleshooting
303
General installation
Upgrade installation fails
Cause 1 You are trying to upgrade your BusinessObjects installation from a CD but your existing version was installed from a master installation in a shared folder. Solution You must first upgrade the master installation (called an administrative installation in 6.x) in the shared folder, and then upgrade the local installation from this folder (see the Installation and Configuration guide). Cause 2 WebIntelligence version 2.x was not uninstalled before reinstallation of 6.x desktop and administration products. Solution Uninstall WebIntelligence 2.x before beginning the upgrade of desktop and administration products. Cause 3 Your server is not supported for this release. Solution Install the Business Objects products on a server that is supported. (See Supported operating systems and platforms on page 40.)
Upgrade via administrative installation fails

Cause 1 The installation script may be corrupted. Solution Restart the installation. If the problem persists, you first need to uninstall BusinessObjects, and then reinstall directly from the BusinessObjects CD.
General installation
304
Cause 2 The license key file has been moved, deleted, renamed, or corrupted. Solution If this file was renamed or moved, then you need to manually locate the file. If you cannot find it or it was corrupted, replace it with a backup copy of the file, or run the installation again from your original BusinessObjects CD.
Version 2.x/5.x present but not detected

Cause The setup.exe file was improperly installed, therefore version 2.x/5.x will not be detected by the Setup wizard. Solution Use the 5.x installation CD to install the 5.x setup.exe file, and then rerun the 6.x installation.
Troubleshooting
305
Repositories
Repository upgrade fails
When you try to upgrade the repository to version 6.x, the upgrade fails and you receive various error messages. Cause 1 You are trying to upgrade from a repository older than version 5.x. Solution Upgrade the repository to 5.x, then retry the upgrade to 6.x. Cause 2 The 5.x repository contains errors. Solution Run a scan-and-repair operation before performing the upgrade. Cause 3 During the repository upgrade, you did not copy all the domains: security, document, and universe. (See the Supervisors Guide.) Solution Copy the missing domains before performing the upgrade of the repository.
Upgraded 6.x cluster doesnt work with the 5.x repository

Cause A version 6.x cluster (and 6.x applications) cannot function on a 5.x repository. Solution Upgrade the repository to version 6.x.
Scan-and-repair operation fails

Cause The structure or content of the 6.x repository is corrupted. Solution Contact Business Objects Customer Support.
Repositories
306
Upgrade of database connection fails

You are unable to upgrade your connection to the new 6.x repository. Cause 1 There are network problems or the machine that hosts the repository database is down. This problem can also occur during an operation that initiates connections to the repository (for example, sending documents). Solution Verify the network connection by pinging the server that hosts the repository. If the network is running properly, the database administrator can then use middleware to check whether there is any response from the repository database. A supervisor can verify that the connections to the repository and the Data Source Name are correctly set up in Supervisor. (See the Supervisors Guide.) Cause 2 The repository connection information is no longer valid. Solution The General Supervisor must regenerate the key file in order to change the parameters of the connection to your repository. The steps are as follows: 1. Rename the key file to deactivate it. The key file is located either in $INSTALLDIR\locData (for local installations) or $INSTALLDIR\shData (for shared installations). 2. Launch Supervisor using a general supervisor profile. 3. Run a Safe Recovery. 4. In the Advanced tab, select the Disconnect after each transaction parameter. 5. Quit Supervisor. 6. Test the connection.
System wont connect to Informix database

Cause Informix is not supported in version 6.1. Solution Use a different type of database.
Troubleshooting
307
Supervisor
Upgraded Supervisor (6.x) doesnt work
Cause You are using a version 5.x repository. A version 5.x repository cannot function with a 6.x Supervisor. Solution Upgrade the repository to 6.x. (See Phase 2 Copy and upgrade the repository on page 55.)
Supervisor 5.x doesnt work with upgraded repository (6.x)

Cause A version 6.x repository cannot function with a 5.x Supervisor. Solution Upgrade Supervisor to 6.x. (See Copy the repository and install Supervisor version 6.x on page 55.)
Upgrade of v. 4.x Supervisor fails

Cause You cannot directly upgrade a Supervisor earlier than version 5.0 from within version 6.x. Solution Upgrade the 4.x Supervisor to 5.x, and then upgrade from 5.x to 6.x.
Supervisor
308
Document migration
Document migration fails
Cause 1 You are trying to migrate a WebIntelligence document earlier than version 2.5. Solution Using a WebIntelligence version later than 2.5, upgrade the document to at least version 2.5, and then migrate it to 6.x. Cause 2 You are trying to migrate a BusinessObjects document earlier than version 5.0. Solution Using BusinessObjects 5.x, upgrade the document to at least version 5.0, and then migrate it to 6.x. (See Upgrade BusinessObjects documents on page 60.)
Import of 6.x document fails

Cause 1 You are using a version of BusinessObjects or WebIntelligence earlier than 6.x. Pre-6.x versions cannot open 6.x documents. Solution Upgrade BusinessObjects or WebIntelligence to 6.x, or make the document available in 2.x/5.x on the relevant clusters.
Troubleshooting
309
Cause 2 You try to import documents after either: migrating from one database to another running a Safe Recovery to create a new key file When you re-create the key file, only the connection to the security domain is rebuilt. The connections to the universe and document domains remain the same. Solution Do one of the following: Edit the connections so that they point to the new database Change your aliases to point to the new database Create new document and universe domains, and then import the information into them. Verify that the new domains work correctly, and then delete the old domains.
Document refresh in 6.x fails

Cause The repository was not correctly upgraded from version 5.x to 6.x. Solution Upgrade the repository again to 6.x. Before you start, publish all your WebIntelligence documents in the Corporate Documents section of the 5.x repository.
Version 2.x/5.x user cant access documents after upgrade

Cause After a BusinessObjects or WebIntelligence document is migrated to 6.x, it can no longer be opened by 2.x/5.x users. Solution Make the document available in 2.x/5.x format on the users cluster, or upgrade the user to 6.x.
Document migration
310
Old 2.x WebIntelligence documents remain in repository

Cause After you migrate your WebIntelligence documents from version 2.x to 6.x, you notice that the 2.x documents remain in the repository. This is normal. Solution If you want to eliminate such documents, you must delete them manually.
WebIntelligence 2.x document was drilled, but remained in 2.x

Cause This is normal. Drilling, by itself, does not cause a 2.x WebIntelligence document to be upgraded to 6.x. Solution Follow the standard document migration procedure. (See Upgrade WebIntelligence documents on page 73.)
Troubleshooting
311
WebIntelligence/InfoView
InfoView 5.x doesnt work with 6.x repository
Cause If you use the Gradual update method, where 2.x/5.x and 6.x clusters share the same repository, you must use InfoView version 5.1 SP5 or later. Certain changes were introduced in SP5 to enhance its compatibility with a 6.x repository. Solution On the 2.x/5.x clusters, upgrade InfoView to version 5.x SP5 or later. (See the version 5.x WebIntelligence System Administrators Guide.)
User settings revert to factory default

After upgrade to version 6.x, new InfoView users do not see the default settings you had defined in version 5.x. Instead, they see the new 6.x factory default. Cause If you do not copy and resubmit the 5.x global profile.txt file, your preferred default settings are lost during the upgrade. Solution Windows To copy and resubmit the global profile.txt file: 1. Copy the 2.x/5.x global profile.txt file from: $INSTALLDIR\Server\WebIntelligence 2.5\Config If you stored the file on an external disk, you must copy it from that location. 2. After reinstallation of 6.x server products, paste the file into the following 6.x directory: $INSTALLDIR\bin\config 3. Log into InfoView as a general supervisor. 4. On the Options page, click Set my options as server defaults. UNIX See UNIX on page 65.
312
Transition users lose their personal settings

After upgrade to version 6.x, migrated InfoView users do not see the personal settings they had defined for themselves in version 5.x. Cause When users modify their personal settings in InfoView, the new profile is stored in a unique profile.txt file that is separate for each user. (This is not the same as the global profile.txt file discussed in the previous item.) In order for users making the transition from 2.x/5.x to 6.x to preserve their personal user settings, these files are transferred to the 6.x Business Objects system. Normally, this is done automatically by the system. If a problem occurs, you need to copy the files manually. Solution Windows See Individual settings for transition users on page 68. UNIX See User information in the Storage directory on page 63.
Users not permitted to manage categories

After upgrade to version 6.x, both 2.x/5.x and 6.x users discover that they cannot manage categories, even though they could do so before the upgrade.
Troubleshooting
313
Cause Hierarchical categories can be used in version 2.x/5.x, but not managed in 2.x/ 5.x. Therefore, some user rights are altered in Supervisor after the upgrade occurs. To prevent 2.x/5.x users from managing hierarchical categories, the following happen automatically when Supervisor is upgraded: All 2.x/5.x security commands related to flat category management are set so that category management in 2.x/5.x becomes prohibited. All 6.x security commands related to hierarchical category management are set so that category management in 6.x becomes prohibited by default. Solution Manually assign the right to manage categories to individual users and user groups. (See the Supervisors Guide.)
314
BusinessObjects
BusinessObjects doesnt function after upgrade
Cause 1 You are trying to use 6.x BusinessObjects with a 5.x repository. These two components cannot function together. Solution Upgrade the repository to 6.x. (See Phase 2 Copy and upgrade the repository on page 55.) Cause 2 You did not uninstall WebIntelligence 2.x before installing version 6.x desktop products. Solution Uninstall WebIntelligence and then reinstall BusinessObjects 6.x.
Cant launch BusinessObjects (3-tier mode) after upgrade

Cause The previous version of ActiveX is not compatible with 6.x BusinessObjects in 3tier mode. Solution See Upgrading ActiveX on page 224.
Troubleshooting
315
Audit and administration

System activity after upgrade is not being logged by the Audit facility
Cause You are using a version 2.x audit database to log activity from an upgraded 6.x Business Objects system. These two components are not compatible. Solution Upgrade the Audit facility to version 6.x. (See Upgrading the Audit facility on page 203.)
Upgrade of Audit facility doesnt register in the Administration Console

Cause The 2.x Audit facility must be shut down before any Business Objects products are upgraded to 6.x. Otherwise, the upgrade of the Audit facility will fail. Solution Shut down the 2.x Audit facility and restart the upgrade of the Audit facility.
Auditor doesnt work after upgrade

Cause 1 You are trying to run Auditor 6.x along with any or all of the following: version 2.x Business Objects server version 2.x audit database version 5.x repository universes from Auditor 5.x None of these are compatible with Auditor 6.x. Solution Upgrade the entire Business Objects system to 6.x before using Auditor 6.x.
Audit and administration
316
Cause 2 Both 2.x and 6.x clusters are connected at the same time to the same audit database. Auditor can function only when all clusters on a given audit database are of the same version. Solution When you use Auditor, make sure that all the audited clusters are of the same version.
WIGenerator and WIHSAL Manager are not visible

After upgrade to version 6.x, the WIGenerator and WIHSAL Manager modules are no longer visible in the 6.x Administration Console. Cause This is normal. These modules no longer exist in version 6.x.
2.x Services Administrator wont function after cluster upgrade

Cause A version 2.x Services Administrator (called the Administration Console in version 6.x) cannot function with a 6.x cluster. Solution Upgrade the 2.x Services Administrator to the 6.x Administration Console. (See Administration Console on page 60.)
Troubleshooting
317
Broadcast Agent
5.x Scheduler ignores jobs after upgrade to 6.x
Cause A version 5.x Scheduler cannot function with 6.x Business Objects applications. Solution Upgrade Broadcast Agent to version 6.x. (See Broadcast Agent on page 207.)
5.x users receive 6.x documents but cant open them

Cause Version 5.x users cannot open 6.x documents. Suppose a 6.x user receives a 5.x BusinessObjects (.rep) document. This user modifies the document, saving it in version 6.x, and then sends it to Broadcast Agent for further processing. Broadcast Agent processes the document. A 5.x user who then receives the document would not be able to open it, because it is now a 6.x document. Solution Create two document domains for a mixed user population: one for 5.x users, the other for 6.x users. Users sending documents to the repository or to Broadcast Agent can select the document domain that corresponds to the version they are working with.
Jobs disappear after upgrade

Cause Jobs may be lost during the upgrade process if they are not set to Suspended status before the upgrade. Solution Set jobs to Suspended status before upgrading your Business Objects system. After upgrading the cluster, reset the jobs to Normal status.
Broadcast Agent
318
Document type disappears from 6.x tasks in a 5.x Console

Cause After upgrade to 6.x, a 5.x Console can connect to a 6.x repository with a 2.x cluster, but it cannot display the document type for 6.x tasks. Solution Upgrade Broadcast Agent to version 6.x.
Channel option not visible after upgrade

After upgrade to version 6.x, the Channel option does not appear: in the Available Actions list in the Schedule Corporate Documents dialog box in the Broadcast Agent tab of the Group Properties dialog box Cause This is normal. There is no Channel option in version 6.x, but previous tasks continue to be executed.
Access to the Security domain is denied

Cause Access may be denied because the repository was not upgraded to version 6.x. Solution Upgrade the repository to 6.x. (See Phase 2 Copy and upgrade the repository on page 55.)
Troubleshooting
Frequently Asked Questions
chapter
320
Overview
This chapter provides answers to some of the most frequently asked questions concerning upgrading, including the compatibility between previous versions and the current version. The chapter is divided into the following topics: General Installation Repositories and Supervisor Universes Documents Desktop products Server and administration products
321
General
Can I upgrade from a version older than 2.x/5.x? Yes, but you must first upgrade to 2.x/5.x, and then upgrade to 6.x. Do I have to shut down my Business Objects system completely in order to upgrade? No. You can upgrade gradually, keeping the previous system running as long as possible until the new installation is complete or nearly complete. You have a mix of 2.x and 6.x clusters that share a single repository. (See Generic Workflow: Gradual Method on page 87.) Can I run WebIntelligence version 2.x and 6.x on the same cluster? It depends on the operating system. On Windows, you cannot have version 2.x and 6.x machines working on the same cluster. On UNIX, you can have 2.x and 6.x functioning on the same machine, as long as they do not share any web servers or directories. Can version 6.x function alongside previous versions? In mixed deployments that are being upgraded gradually, 6.x can function alongside all previous versions supported for upgrade.
General
322
Installation
Do I have to use a test system? No, but Business Objects recommends that you do. The test system gives you an idea of the problems you are likely to encounter during the actual production upgrade. By learning how to resolve these problems on a reduced scale, you can save time and reduce costs when you upgrade your production system. (See Test systems on page 36.) Does the Installation program help me to upgrade? It does in Windows, but not in UNIX. In Windows, the Installation wizard automatically detects other versions of Business Objects products on your machines hard disk. You are then prompted for the upgrade to 6.x. On UNIX: The Installer does not automatically upgrade from a previous major version; you must do this manually It is not possible to automatically detect a version that is already installed. (See the Installation and Configuration guide.) Can I change the path of installation folders? Yes. The Installation wizard gives you this choice. You can accept the default path or change it. Can I change the location of security and administration files? Yes. Can information in the WIStorageManager be shared between 2.x and 6.x clusters? Yes, with some restrictions. What does the Configuration Tool do? The Configuration Tool helps you configure the version 6.x server products after they are installed. This includes the web server and application server. You can use the tool on both Windows and UNIX. (See the Installation and Configuration guide.)
323
Repositories and Supervisor

Has the repository structure changed with version 6.x? Very little. There are very few new columns and no new tables, only new data (such as document types). (See Repositories on page 39.) Can version 2.x/5.x applications and a 2.x cluster function on a 6.x repository? Yes. Can version 6.x applications and a 6.x cluster function on a 5.x repository? No. Can version 6.x documents be stored in a 5.x repository? No. Can version 2.x/5.x documents be stored in a 6.x repository? Yes. Can version 6.x Supervisor function on a 5.x repository? No. Can version 5.x Supervisor function on a 6.x repository? No. Can a version 6.x Supervisor and 5.x Supervisor function independently on the same machine? Yes. Can I use 2.x/5.x connections in version 6.x? Yes. Version 6.x can view, edit, and save any connection (personal, shared, and secured) created with 2.x/5.x. Can I use 6.x connections in version 2.x/5.x? Yes. Version 2.x/5.x can open, use, modify, and save any connection created in 6.x.
Repositories and Supervisor
324
Universes
Has the structure of universes changed with version 6.x? No. You continue working with the same universes as before. Can a version 2.x/5.x universe be used in 6.x Designer and by 6.x users? Yes. (See Designer on page 255.) Can a version 6.x universe be used in 5.x Designer and by 2.x/5.x users? Yes. Can I use 5.x Designer and 6.x Designer on the same machine? Yes. Can I use 6.x Designer with a 5.x repository? No. Can I use 5.x Designer with a 6.x repository? No.
325
Documents
Can I use version 5.x BusinessObjects and 2.x WebIntelligence documents in 6.x? Yes. Documents you created in version 2.x/5.x can be used in 6.x InfoView and 6.x BusinessObjects. The 2.x/5.x documents can also be upgraded to 6.x. After you upgrade the document to 6.x, it can no longer be used in 2.x/5.x. Can I use version 6.x documents in 2.x/5.x? No. Documents you create or modify in version 6.x cannot be used in a 2.x/5.x application. There is no Save as 5.x feature in version 6.x. How do I upgrade version 5.x BusinessObjects documents? You upgrade version 5.x BusinessObjects documents to 6.x simply by opening them in a 6.x product, and then saving the documents. Business Objects recommends that you test documents after they have been upgraded. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x. (See Upgrading BusinessObjects documents on page 218.) How do I upgrade version 2.x WebIntelligence documents? You upgrade version 2.x WebIntelligence documents to 6.x by editing them in InfoView 6.x, and then saving them as corporate or personal documents. Business Objects recommends that you test documents after they have been upgraded. Make sure that the document looks the same, and that all functionality has been transferred to version 6.x. After you save it as a corporate or personal document in 6.x, it can no longer be opened or viewed in InfoView version 5.x. (See Upgrading WebIntelligence documents on page 284.) Can I open a document that was saved on a machine with a different language? Yes, but you must have on your machine the font corresponding to the language of the cell. (See Upgrade issues in international deployments on page 46.)
Documents
326
Can I use hierarchical categories in version 2.x/5.x? Yes, but you cannot manage them in 2.x/5.x. Therefore, some user rights are modified in Supervisor. (See Hierarchical categories and Supervisor on page 276.)
327
Desktop products
How do I upgrade desktop products? You upgrade desktop products, including BusinessObjects, by uninstalling version 5.x and then reinstalling 6.x. (See Reinstall desktop and administration products on page 58.) Are registry keys automatically transferred? Yes, registry keys are automatically transferred from 5.x to 6.x.

How do I upgrade BusinessObjects in 3-tier mode? You upgrade BusinessObjects in 3-tier mode by doing both of the following: On the cluster installing BusinessObjects Web Installer. On the client machine installing BusinessObjects. (See Troubleshooting on page 301.) Are previous and new versions of BusinessObjects and InfoView compatible? No. Version 5.x BusinessObjects cannot function with 6.x InfoView Version 6.x BusinessObjects cannot function with 5.x InfoView
Desktop products
328
Server and administration products

How do I upgrade my Services Administrator? The Administration Console (called the Services Administrator in version 2.x) is one of the administration products. You upgrade the 2.x Services Administrator to the 6.x Administration Console when you uninstall version 2.x and reinstall version 6.x desktop and administration products. (See Reinstall desktop and administration products on page 58.) Are previous and new Administration Consoles compatible? No. A version 6.x Console cannot function on a 2.x cluster, and a 2.x Services Administrator cannot function on a 6.x cluster.
Auditor/Audit facility
Auditor is now one of the administration products (it was formerly classified as a server product). You upgrade Auditor when you uninstall version 2.x server products and reinstall version 6.x administration products. (See Uninstall/reinstall server products on page 65.) You upgrade the Audit facility by upgrading the audit database. (See The Audit Facility and Auditor on page 201.) Is the version 6.x audit database similar to that in 2.x? Yes, they are very similar. In the transition to 6.x: No tables were deleted No columns were deleted or modified No IDs were removed from lookup tables (events, details, applications) This allows the version 2.x Business Objects system to log its activity to a version 6.x audit database. In addition, all version 2.x/5.x applications can work with the version 6.x Audit facility. However, because of new events and other new information (such as cluster ID) in the 6.x Audit facility, the reverse is not truethe 6.x Business Objects system cannot log its activity to a version 2.x audit database.
329
Is Auditor 5.x compatible with version 6.x? Yes. In general, Auditor 5.x is compatible with version 6.x. This means that: Auditor 5.x can function on a 6.x Business Objects server, using a 6.x audit database Auditor 5.x reports can be refreshed using 6.x universes Auditor 5.x views can be used to analyze the content of a version 6.x audit database Is Auditor 6.x compatible with version 2.x/5.x? No. This means that Auditor 6.x: cannot be installed and cannot function on a 2.x Business Objects server cannot analyze the content of a 2.x audit database cannot analyze the content of a 5.x repository cannot have its reports refreshed using Auditor 5.x universes
Broadcast Agent
Can a version 6.x Broadcast Agent process jobs scheduled in 5.x? Yes. After upgrade to Broadcast Agent version 6.x, previously scheduled jobs are recovered and reprocessed by the new Scheduler. If the task is based on a WebIntelligence document or a BusinessObjects document, the document is kept in 2.x/5.x format. (See Broadcast Agent on page 207.) Can a version 5.x Broadcast Agent process jobs scheduled in 6.x? Yes, if the documents were not upgraded to 6.x. Can version 2.x/5.x users work on jobs after they are upgraded to Broadcast Agent 6.x? Yes; 2.x/5.x users can still open, edit, and save them. If a 2.x/5.x document is upgraded in a 6.x Business Objects product (such as InfoView), all previous scheduling information is lost, and 2.x/5.x users can no longer work on it. Can a version 6.x Broadcast Agent Console connect to a 5.x repository? Yes, but in this case it cannot execute Run Now, Interrupt Task, or Purge.
330
Can a version 5.x Broadcast Agent Console connect to a 6.x repository? Yes, on a 2.x cluster. But in this case: it cannot display the document type for 6.x tasks it cannot execute Run Now, Interrupt Task, or Purge Do I need to upgrade the repository to 6.x in order to use 6.x Broadcast Agent? Yes. What happens to hierarchical categories in Broadcast Agent 5.x? The hierarchical category appears as a version 5.x name with special characters (such as a forward slash) in the Categories column. If there are no separators in the name, it is assumed that a hierarchical category was not created; they are interpreted as root categories in 6.x. (See Hierarchical categories on page 213.) Can I process version 4.x documents in Broadcast Agent 6.x? No. To process version 4.x documents, you must upgrade from Document Agent Server to Broadcast Agent, and then upgrade your machine to BusinessObjects version 6.x.
Developer Suite
How do I upgrade my WebIntelligence, BusinessObjects, and Administration SDKs? You upgrade them when you uninstall version 5.x Developer Suite and reinstall version 6.x. This installation is separate from the installation of the Business Objects server, desktop, and administration products. (See Developer Suite on page 259.) What happens to applications built on 2.x/5.x SDKs? All applications built on version 2.x/5.x SDKs continue functioning after 6.x is installed.
331
What happens to add-ins? Version 6.x opens, edits, and saves all 2.x/5.x add-ins. After it is saved in 6.x, the add-in is no longer available in 2.x/5.x (it is saved under VBA 6.x format). Can I refresh a 2.x/5.x Free-Hand SQL data provider in 6.x? Yes. This is done in InfoView. (FreeHand SQL cannot be refreshed in BusinessObjects 3-tier mode.)
332
333
Index
$STORAGEDIR directory 70, 107 $WISTORAGEDIR directory 102
B
backing up configuration files (UNIX) 65, 102 repository 55, 176 system information 64, 101 backing up the repository 91 backups and test systems 36 BEA WebLogic 54, 90 bomain.key file 72, 109 BOManager 81, 101, 115 Boolean operators 293 border size 296 Broadcast Agent 67, 104, 208-213 Channel option 212 Console 67, 104, 210, 318 hierarchical categories 213 in upgrade scenarios 144, 154, 164, 172, 182, 183, 192 mixed-version deployments 211 reactivating jobs 72, 109 resetting to Normal status 55 Scheduler 67, 104, 208, 209, 317, 329 suspending jobs 55, 91 troubleshooting 317 browser configuration indicator 80 Business Objects consulting services 13, 15 documentation 12 Documentation Supply Store 11 support services 13 training services 13, 15 Business Objects server 103, 172, 206, 315 Business Objects Services Administrator 203 BusinessObjects compatibility 220 troubleshooting 314 upgrading 216-218
A
ActiveX 262 upgrading 224 add-ins (.rea) 261 Administration Console 202, 283, 328 compatibility 283 modules 154, 164, 172, 182, 183 new modules 60, 97, 283 single-instance modules 124, 134, 144, 192 upgrading 97 Administration SDK 260 Administration server 283 Administration Setup wizard 56, 92 administrative installation 60, 97, 219 Apache 164 ASP scripts 126, 144, 145, 192 Audit database structure 202 upgrading 204 Audit facility 202-205 Database mode 202 File mode 202 shutting down 75, 94, 203 troubleshooting 315 upgrading 203 Auditor compatibility 185, 206 database views 205 in upgrade scenarios 180 upgrading 205
Index
334
BusinessObjects 3-tier 222-224 compatibility 222 in upgrade scenarios 154, 181, 182, 183 upgrading client machine 222 version compatibility check 223 BusinessObjects documents upgrading 218 BusinessObjects SDK 261 BusinessObjects Web Installer 222 BusinessQuery compatibility 257 upgrading 257 BusinessQuery SDK 260 BusinessQuery version 4.1 257
consultants Business Objects 13 copying and upgrading repository 55 user and system information 63 corporate categories 110 creating a test system 36 creating key file UNIX 72, 109 Windows 56, 92 custom calculations 296 custom scripts 261 customer support 13 customized localization 47
C
calculations 296 Calculator enhancements 225 categories hierarchical 291 cell properties 293 Channel option 212, 277 charts 296 checking the scenarios 82, 116 Choose Setup Configuration page 56, 92 client machine upgrading BusinessObjects 3-tier 222 Cluster Management page 69, 70, 106, 107 color in documents 297 compatibility 41-45 Administration Console 41 Broadcast Agent 41 BusinessObjects 3-tier 44 database connections 93 document exchange 42 repositories 44 universes 45 config directory 68 Config folder 101 configuration files backing up (UNIX) 65, 102 Configuration Tool 69, 106 Cluster Management page 70, 107 in upgrade scenarios 126 linking directories 67, 104
D
data upgrade 290 database connections compatibility 57, 93 database views 205 default settings (Windows) 100 Define the Repository Connection page 57, 92 deleting 2.x directories (UNIX) 81 demo materials 11 deployment small vs. large 29 Designer compatibility 255 upgrading 255 Developer Suite 12, 14 Display tab 289 document editors 289 document exchange 42 documentation CD 11 feedback on 12 on the web 11 printed, ordering 11 roadmap 11 search 11 Documentation Supply Store 11
Index
335
documents color in 297 compatibility 287 FAQs 325 upgrading 60, 98, 284 drilling 292 duplicating repositories 156
E
education see training
F
FAQs (Frequently Asked Questions) 320-331 desktop products 327 documents 325 installation 322 repositories 323 server and administration products 327 Supervisor 323 universes 324 Faster Document Viewing over the Web 81 feedback on documentation 12 filters 293 format number 297 format numbers 297 Formatting Toolbar command 269 Free-Hand SQL 331 FreeHand SQL 290
gradual upgrade method 29, 33, 88-120 checking the scenarios 116 creating key file (UNIX) 109 creating key file (Windows) 92 installing Supervisor 92 modifying platforms 90 phases 88 reinstalling server products 102 scenarios 122 testing functionality 113 upgrading BusinessObjects 95 upgrading BusinessObjects documents 98 upgrading clusters 99 upgrading repository 91, 93 upgrading WebIntelligence documents 111 Group Properties dialog box 277
H
header repetition 295 headers and footers 292 hidden commands 276 hierarchical categories 213, 291, 313 and Supervisor 276 root categories 291 separators and slashes 291 HSAL 125, 135, 144, 145, 172, 192, 262 HTML Report Panel 289, 293, 297 HTML tags 285 hyperlinked reports 285
G
getHsalPath method 262 global default options 68, 105 global filters 293 global profile.txt file 100, 105, 311 Global Report button 64, 101
I
IIS 144, 172, 192 individual profile.txt file 68, 105 individual settings 68, 105 Informix 306 InfoView 282-297 compatibility 287 drilling 292 in upgrade scenarios 154, 164, 182, 183 interactive viewing 289 JSP version 289 SP5 33 start page 289 user options 289
Index
336
Installation wizard 59, 96, 217 interactive viewing 289 internal.log file 283 international deployments 46 Internet Information Server 125, 144, 172, 192 ISAPI dll 262
N
non-Business Objects software 54 number of users time for upgrading 37
O
object format properties 294 objects tagged as HTML 285 Online Customer Support 13 Options page 70 orb parameters 263
J
Java Report Panel 289 JSP mode (Java Server Pages) 138, 164 scripts 135
K
key file 57 Knowledge Base 14
P
padding setting 294 PAR (product availability report) 40 percentage calculations 296 preliminary procedures 28 profile.txt file 100 UNIX 65, 102 prompts 297
L
languages customized localization 47 supported 47 Last Refreshed date 292 legend properties 296 license file 59, 96 license key file 304 locData directory 93 locData folder 57, 306
Q
QT_MAX_ACTIVE_TIME parameter 65, 102 QT_MAX_INACTIVE_TIME parameter 65, 102
R
reactivating Broadcast Agent jobs 109 REBean 262 RECOM 262, 263 reinstalling server products 65, 102 Report Viewer Component 260 repositories 39 backing up 55, 91, 176 connection 103 duplicating 156, 165 FAQs 323 resubmitting user and system information 68, 105 Row Count/Page feature 292 run a safe recovery 56, 92
M
Manage Channels button 277 MIGRATIONPROMPT feature 223 mixed version deployment 122, 211 mixed version deployments 95 mixed-version deployment 122, 136 modifying platforms 54, 90 modules 154, 164, 172, 182, 183 single-instance 124, 134, 144, 192 MsgAdminMaxActiveTime 72, 109 MsgAdminMaxInactiveTime 72, 109 multimedia quick tours 12 multiple reports 293 My InfoView 68, 105 MyWebiEnv.sh file 72, 109
Index
337
S
SBL scripts 261 scenarios summary 84, 118 Schedule Corporate Documents dialog box 212 Scheduler 67, 104, 208, 317, 329 scope of analysis 293 scripts SBL 261 search documentation 11 section properties 293 security commands 269 hidden 276 new commands 269 summary of changes 272 setHsalPath method 262 Setup utility 59, 96, 217 setup.exe file 59, 97, 304 shared storage 124, 134, 154, 182, 183 shData folder 306 Show as Index 294 single-instance modules 124, 134 split upgrade method 29, 52-82 checking the scenarios 82 copy and upgrade repository 55 creating key file (UNIX) 72 creating key file (Windows) 56 installing Supervisor 55 modifying platforms 54 phases 52 reinstalling server products 65 testing functionality 79 upgrading BusinessObjects 58 upgrading BusinessObjects documents 60 upgrading clusters 62 upgrading production system 75 upgrading repository 57 upgrading WebIntelligence documents 73 SQL Server 182 start page 289 Storage directory 63, 100 Storage files UNIX 65, 102
Supervisor 56, 268-277 compatibility 92, 275 FAQs 323 hierarchical categories 276 security commands 269 troubleshooting 310 version 4.x 307 support customer 13 supported languages 47 suspending Broadcast Agent jobs 55, 91 system information 63 backing up 64, 101
T
tables 295 terminology 25 test environment 52, 58, 74 in upgrade scenarios 156, 165, 174 test systems 36 testing functionality 79, 113 in upgrade scenarios 139 testing server products 80, 114 testing user settings 81, 115 time frame for upgrading 37 Tips & Tricks 12 Tomcat 135, 138, 164, 182 training on Business Objects products 13 transparent drill outside of cube 269 troubleshooting 302-318 Broadcast Agent 317 BusinessObjects 314 installation 303 Supervisor 310
U
universes compatibility 255 FAQs 324
Index
338
UNIX and desktop products 23 and Windows 23 automatic installation 104 automatic upgrade 67 deleting directories 115 mixed version deployments 62, 95 upgrade methods gradual 29, 33, 88-120 checking the scenarios 116 creating key file (UNIX) 109 creating key file (Windows) 92 installing Supervisor 92 modifying platforms 90 phases 88 reinstalling server products 102 testing functionality 113 upgrade repository 91 upgrading BusinessObjects 95 upgrading BusinessObjects documents 98 upgrading clusters 99 upgrading repository 93 upgrading WebIntelligence documents 111 split 29, 52-82 checking the scenarios 82 copy and upgrade repository 55 creating key file (UNIX) 72 creating key file (Windows) 56 installing Supervisor 55 modifying platforms 54 phases 52 reinstalling server products 65 testing functionality 79 upgrading BusinessObjects 58 upgrading BusinessObjects documents 60 upgrading clusters 62 upgrading production system 75 upgrading repository 57 upgrading WebIntelligence documents 73
upgrading about 19 Administration Console 97 audit database 204 Audit facility 203 Auditor 205 Broadcast Agent 67, 104, 208 BusinessObjects 58, 95 BusinessObjects 3-tier 222-224 BusinessObjects documents 60, 98, 218 BusinessQuery 257 clusters 62, 99 defined 20 Designer 255 from pre-2.x/5.x 21 methods 29-35 production system 75 repository 57, 91, 93 Supervisor 268-277 time frame 37 WebIntelligence documents 73, 111, 284 upgrading VBA 261 User Activity Log page 76, 94, 203 User Identification login box 56, 92 user information 63 resubmitting 68 user interface Japanese 46 language 46 user options 289 user settings 63 individual 68, 105 testing 81
V
VBA upgrading 261 version number 20 View Log command 76, 94, 203 View SQL 290 Visual Basic 261
W
WAR file 263
Index
339
web customer support 13 getting documentation via 11 useful addresses 14 WebIntelligence 124, 134, 282-297 compatibility 287 data upgrade 290 document exchange 287 in upgrade scenarios 144, 154, 164, 172, 182, 183, 192 uninstalling 58 v. 2.6 SP2 72, 109 WebIntelligence documents 284 border size 296 calculations 296 cell properties 293 charts 296 color 297 filters 293 format number 297 global filters 293 header repetition 295 headers and footers 292 legend properties 296 multiple reports 293 padding setting 294 scope of analysis 293 section properties 293 table properties 295 tables 295 WebIntelligence Reporting SDK 262 WebIntelligence SDK 134, 260, 262 in upgrade scenarios 144, 192 WIBean 262, 263 wibean.orb.properties file 262 WICOM 263 WICOM250.dll 263 WIDispatcher 101 WIGenerator 60, 97, 283, 316 WIHSALManager 60, 97, 283 WILoginServer 60, 97, 283 Windows 2000 server 125 Windows and UNIX 23 WIQT 60, 97, 283 WIReportServer 60, 97, 283
WIServer 262 WIStorageManager 63, 69, 81, 100, 106, 115, 183 wmainkey script 72, 109
Z
ZaboCheckAndRunControlClass file 224 zero-based axis 296
Index
340
Index

Deployment Upgrading

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Deployment Upgrading

Caricato da

Copyright:

Formati disponibili

Migrating from a Previous Version

BusinessObjects Enterprise 6 Business Intelligence Windows and UNIX

Migrating from a Previous Version

Patents Part Number

Migrating from a Previous Version

Migrating from a Previous Version

Migrating from a Previous Version

Scenario: Basic Web Deployment, Application Server (ASP)

Migrating from a Previous Version

Migrating from a Previous Version

Migrating from a Previous Version

Maximizing Your Information Resources

Migrating from a Previous Version

Maximizing Your Information Resources

Migrating from a Previous Version

Migrating from a Previous Version

How can I get the most recent documentation?

Send us your feedback

Maximizing Your Information Resources

Migrating from a Previous Version

How we can support you?

Having an issue with the product?

Looking for the best deployment solution for your company?

Looking for training options?

Migrating from a Previous Version

Useful addresses at a glance

Business Objects Documentation mailbox documentation@businessobjects.com Product documentation www.businessobjects.com/services/ support.htm

Feedback or questions about documentation.

The latest Business Objects product documentation, to download or view online.

Tips & Tricks www.businessobjects.com/forms/ tipsandtricks_login.asp

Maximizing Your Information Resources

Migrating from a Previous Version

Address Online Customer Support www.techsupport.businessobjects.com

www.businessobjects.com/services Business Objects Education Services www.businessobjects.com/services/ education.htm

Useful addresses at a glance

Migrating from a Previous Version

Some code more code

Maximizing Your Information Resources

Migrating from a Previous Version

Migrating from a Previous Version

Upgrading from a pre-2.x/5.x version

Migrating from a Previous Version

Structure of the guide

Migrating from a Previous Version

Windows and UNIX

Windows and UNIX

Migrating from a Previous Version

Migrating from a Previous Version

Migrating from a Previous Version

Before You Start

Migrating from a Previous Version

Before You Start

Migrating from a Previous Version

Migrating from a Previous Version

The basic procedure is as follows:

Copy of 5.x repository

Figure 2-1 Copying the original 5.x repository

Before You Start

Migrating from a Previous Version

2. Upgrade the duplicate repository to version 6.x.

Figure 2-2 Upgrading the duplicate repository to 6.x

3. Upgrade one cluster to version 6.x, or build a new 6.x cluster.

Migrating from a Previous Version