Deployment Upgrading

8/3/2019 Deployment Upgrading

1/340

Migrating from a Previous Version

BusinessObjects Enterprise 6 Business Intelligence

Windows and UNIX


2/340

2 Migrating from a Previous Version

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 [email protected].

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 IBMare 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 AcquisitionRegulations 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 insubdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252.227-

7013.

Patents U.S. Patent Numbers 5,555,403, 6,247,008, and 6,578,027.

Part Number 366-50-610-01


3/340

Migrating from a Previous Version 3

Contents

Contents

Contents 3

Preface Maximizing Your Information Resources 9

Information resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 46Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48


4/340


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) . . . . . . . . . . . . . . . . . . . . . 62Phase 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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




5/340


Contents

Chapter 7 Scenario: Basic Web Deployment, Application Server (ASP) 141

Existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143



Chapter 8 Scenario: Basic Web Deployment, Broadcast Agent 151


Build a test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Upgrading the production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158


Chapter 9 Scenario: Application Server, Broadcast Agent, UNIX 161



Upgrade the production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166


Chapter 10 Scenario: Application Server, Broadcast Agent 169



Upgrade the production system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176


Chapter 11 Scenario: Basic Web Deployment, Auditor 179



Upgrade the Auditor cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Final deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Chapter 12 Scenario: Basic Web Deployment, ASP, BusinessObjects (3-tier) 189





6/340


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 207Broadcast Agent Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Broadcast Agent Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Mixed-version deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Channel tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Hierarchical categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 15 BusinessObjects 215Uninstalling/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


7/340


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


8/340


Contents


9/340

preface

Maximizing Your InformationResources


10/340


Maximizing Your Information Resources

Overview

Information, services, and solutions

The Business Objects business intelligence solution is supported by thousandsof 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 ontroubleshooting and best practices, this comprehensive documentation setprovides concrete solutions to your business problems.

Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment. See in thefollowing sections how Business Objects can help you plan for and successfully

meet your specific technical support, education, and consulting requirements.


11/340


Information resources

Information resources

Whatever your Business Objects profile, we can help you quickly access thedocumentation and other information you need.

Where do I start?

Below are a few suggested starting points; there is a summary of useful webaddresses on page 14.

Documentation RoadmapThe Documentation Roadmap references all Business Objects guides andmultimedia, and lets you see at a glance what information is available, fromwhere, and in what format.

View or download the Business Objects Documentation Roadmap at

www.businessobjects.com/services/documentation.htm Documentation from the productsYou can access electronic documentation at any time from the product you areusing. Online help, multimedia, and guides in Adobe PDF format are availablefrom the product Help menus.

Documentation on the webThe full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwww.businessobjects.com/services/support.htm

Buy printed documentationYou can order printed documentation through your local sales office, or from theonline Business Objects Documentation Supply Store atwww.businessobjects.com/services/documentation.htm

Search the Documentation CDSearch across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products. This CD brings together the full setof documentation, plus tips, tricks, multimedia tutorials, and demo materials.

Order the Documentation CD online, from the Business Objects DocumentationSupply Store, or from your local sales office.
http://www.businessobjects.com/services/documentation.htmhttp://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/services/documentation.htmhttp://www.businessobjects.com/services/documentation.htmhttp://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/services/documentation.htm


12/340



MultimediaAre you new to Business Objects? Are you upgrading from a previous release orexpanding, for example, from our desktop to our web solution? Try one of ourmultimedia quick tours or Getting Started tutorials. All are available via the OnlineCustomer 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 thesites listed below for the latest documentation, samples, and tips.

Tips & TricksOpen to everyone, this is a regularly updated source of creative solutions to anynumber of business questions. You can even contribute by sending us your owntips.

www.businessobjects.com/forms/tipsandtricks_login.asp

Product documentationWe regularly update and expand our documentation and multimedia offerings.With a valid maintenance agreement, you can get the latest documentation inseven languages on the Online Customer Support (OCS) website.

Developer Suite OnlineDeveloper Suite Online provides documentation, samples, and tips to those

customers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website.

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is theresomething you particularly like or have found useful? Drop us a line, and we willdo our best to ensure that your suggestion is included in the next release of ourdocumentation: [email protected]

NOTE

If your issue concerns a Business Objects product and not the documentation,please contact our Customer Support experts. For information about CustomerSupport visit: www.businessobjects.com/services/support.htm
http://www.businessobjects.com/http://www.businessobjects.com/forms/tipsandtricks_login.aspmailto:[email protected]://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/services/support.htmmailto:[email protected]://www.businessobjects.com/forms/tipsandtricks_login.asphttp://www.businessobjects.com/


13/340


Services

Services

A global network of Business Objects technology experts provides customersupport, education, and consulting to ensure maximum business intelligencebenefit to your business.

How we can support you?

Business Objects offers customer support plans to best suit the size andrequirements of your deployment. We operate three global customer supportcenters:

Americas: San Jose, California and Atlanta, Georgia

Europe: Maidenhead, United Kingdom

Asia: Tokyo, Japan and Sydney, Australia

Online Customer SupportOur Customer Support website is open to all direct customers with a currentmaintenance agreement, and provides the most up-to-date Business Objectsproduct and technical information. You can log, update, and track cases from thissite 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 WorldwideCustomer 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 stageto the delivery of your deployment project. Expertise is available in relational andmultidimensional 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 offera training package to suit your learning needs and preferred learning style. Findmore information on the Business Objects Education website:www.businessobjects.com/services/education.htm
http://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/services/consulting.htmhttp://www.businessobjects.com/services/education.htmhttp://www.businessobjects.com/services/consulting.htmhttp://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/services/education.htm


14/340



Useful addresses at a glance

Address Content

Business Objects Documentation

www.businessobjects.com/services/documentation.htm

Overview of Business Objects documentation. Linksto Online Customer Support, Documentation Supply

Store, Documentation Roadmap, Tips & Tricks,Documentation mailbox.

Business Objects Documentation

mailbox

[email protected]

Feedback or questions about documentation.

Product documentation

www.businessobjects.com/services/support.htm

The latest Business Objects product

documentation, to download or view online.

Business Objects product information

www.businessobjects.com

Information about the full range of BusinessObjects products.

Developer Suite Online

www.techsupport.businessobjects.com

Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website. Providesall the documentation, latest samples, kits and tips.

Knowledge Base (KB)


Technical articles, documents, case resolutions.

Also, use the Knowledge Exchange to learn whatchallenges other users both customers andemployees face and what strategies they find to

address complex issues. From the KnowledgeBase, click the Knowledge Exchange link.

Tips & Tricks

www.businessobjects.com/forms/tipsandtricks_login.asp

Practical business-focused examples.
http://www.businessobjects.com/services/documentation.htmhttp://www.businessobjects.com/services/documentation.htmmailto:[email protected]://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/services/support.htmhttp://www.businessobjects.com/http://www.techsupport.businessobjects.com/http://www.techsupport.businessobjects.com/http://www.businessobjects.com/forms/tipsandtricks_login.asphttp://www.businessobjects.com/forms/tipsandtricks_login.asphttp://www.businessobjects.com/forms/tipsandtricks_login.asphttp://www.techsupport.businessobjects.com/http://www.techsupport.businessobjects.com/http://www.businessobjects.com/http://www.businessobjects.com/services/support.htmmailto:[email protected]://www.businessobjects.com/services/documentation.htm


15/340


Useful addresses at a glance

Online Customer Support


www.businessobjects.com/services

Starting point for answering questions, resolvingissues.

Information about registering with WorldwideCustomer Support.

Business Objects Education Services

www.businessobjects.com/services/education.htm

The range of Business Objects training options andmodules.

Business Objects Consulting Services

www.businessobjects.com/services/consulting.htm

Information on how Business Objects can helpmaximize your business intelligence investment.

Address Content
http://www.techsupport.businessobjects.com/http://www.businessobjects.com/services/http://www.businessobjects.com/services/education.htmhttp://www.businessobjects.com/services/education.htmhttp://www.businessobjects.com/services/consulting.htmhttp://www.businessobjects.com/services/consulting.htmhttp://www.businessobjects.com/services/consulting.htmhttp://www.businessobjects.com/services/education.htmhttp://www.businessobjects.com/services/http://www.techsupport.businessobjects.com/


16/340



Typographical conventions

The conventions used in this guide are described in the table below.

.

Convention Indicates

This font Code, SQL syntax, computer programs. Forexample: @Select(Country\Country Id).This font is also used for all paths, directories,scripts, commands and files for UNIX.

Some code

more code

Placed at the end of a line of code, the symbol ()indicates that the next line should be enteredcontinuously with no carriage return.

$DIRECTORYPATHNAME The path to a directory in the Business Objects

installation/configuration directory structure. Forexample:

$INSTALLDIR refers to the Business Objectsinstallation directory.

$LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData.


17/340

pa

rt

Introduction


18/340


19/340

chapte

r

About Migrating


20/340


About Migrating

Overview

This guide explains how to migrate (upgrade) your Business Objects system froma 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 anexisting 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 isconsidered an upgrading process, this release does not constitute an officialBusiness 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 inversion 6.x.

This guide does notcover:

updatingto a minor release (such as a service pack) of the same majorversion; for example, updating from BusinessObjects 5.1 to 5.1.3

system-wide changes in operating systems; for example, moving from

Microsoft Windows2000 to Sun Solaris8 (UNIX)

NOTE

In the previous version, Business Objects products could have different versionnumbers; for example, WebIntelligence 2.x and BusinessObjects 5.x. In the newversion, however, all products are series 6.x.


21/340


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 PreviousRelease in the Installation and Update Guide, version 5.1/2.7.


22/340


About Migrating

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. Thesetwo 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 describesseveral 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 therecommended solutions.

Frequently Asked Questions (chapter 21)

For example: Have universes changed between version 2.x/5.x and 6.x? CanBusinessObjects 6.x users access BusinessObjects 5.x documents?


23/340


Windows and UNIX

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


24/340


About Migrating

LDAP directories

Starting with version 6.1 of the Business Objects suite, you can store andmaintain your Business Objects users in a corporate directory. In the currentrelease, the directory used must be LDAP (Lightweight Directory AccessProtocol).

To configure your Business Objects system for use with an LDAP directory, youuse the LDAP Configuration Tool.

Due to the integration with LDAP, there have been changes in several BusinessObjects products.

For more information, see the LDAP Security Connector Guide.


25/340


Terminology

Terminology

Business Objects has recently streamlined its terminology. Below are some ofthe major changes:

Previous term New term

WebIntelligence deployment or system Business Objects deployment orsystem

WebIntelligence server Business Objects server

Enterprise Server Products server products

Zero Admin BusinessObjects BusinessObjects (3-tier mode)

full-client document (.rep) BusinessObjects document

thin-client document (.wqy) WebIntelligence document

Business Objects ServicesAdministrator

Business Objects AdministrationConsole

Cluster Manager primary node

Cluster Node secondary node


26/340


About Migrating


27/340

ch

apte

r

Before You Start


28/340


Before You Start

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


29/340


Upgrade methods

Upgrade methods

This section contains a brief summary of the two upgrade methods, to help youchoose the one that is best suited to your needs. After you choose a method, seechapters 3 and 4 for detailed, step-by-step instructions. This chapter providesonly a general overview.

There are two basic upgrade methods:

Split

You build a test environment with a dedicated repository, alongside yourproduction environment. The system is split into two environments.

When version 6.x operates satisfactorily on the test environment, you shutdown the Business Objects system and upgrade all production machines atthe same time. Versions 2.x/5.x and 6.x never function simultaneously on thesame repository.

Recommended for smaller deployments. Gradual

You upgrade gradually, keeping the 2.x/5.x system running as long aspossible until the new installation is complete or nearly complete. This meansthat two or more clusters (2.x and 6.x mixed) share a single repository. Youdont 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.xrepository (using the Gradual method). However, you cannot run 2.x serverproducts 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 practicalespecially for large deployments.

The Split method is best for small deployments, where it is possible to upgradeto the current version over the weekend or a holiday period without too muchdown time for your company.


30/340


Before You Start

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

Figure 2-1 Copying the original 5.x repository

5.x repository

Copy of

5.x repository

Cluster 1 - 2.x

Cluster 2 - 2.x

Cluster 3 - 2.x


31/340


Upgrade methods

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.

5.x repository

Upgrade to

6.x

Cluster 1 - 2.x

Cluster 2 - 2.x

Cluster 3 - 2.x


32/340


Before You Start

4. Connect this cluster to the 6.x repository. This becomes the test environment.

Figure 2-3 Connecting the test cluster to the repository

5. Verify that the test environment functions properly.

6. Disable access to the Business Objects system for all users.

7. Upgrade all remaining clusters to 6.x.

8. Upgrade the original 5.x production repository to 6.x.

5.x repository

6.x repository

Cluster 1 - 2.x

Production

Cluster 2 - 2.x

Production

Cluster 3 - 6.xTest


33/340


Upgrade methods

9. Reconnect the upgraded original repository to all the clusters.

Figure 2-4 Reconnecting the original repository

Gradual method

This solution is more suitable for larger deployments, where it might beimpractical or impossible to shut down the entire Business Objects system whilethe final production upgrade takes place.

By gradually installing version 6.x alongside the previous version, you continueto use the two systems as long as necessary, switching over gradually accordingto a well-defined plan.

You must use InfoView version 5.1 SP5 or later in this scenario. Certain changeswere introduced in SP5 to enhance its compatibility with a 6.x repository.

6.x repositoryCluster 1 - 6.x

Production

Cluster 2 - 6.x

Production

Cluster 3 - 6.x

Production


34/340


Before You Start

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 theBusiness Objects system for all users.

3. Upgrade the repository to version 6.x. This new 6.x repository will be used forall clusters.

Figure 2-5 Upgrading the repository to 6.x

4. Reconnect clusters and users to the upgraded repository.

Repositoryupgraded to 6.xCluster 1 - 2.x

Production

Cluster 2 - 2.x

Production

Cluster 3 - 2.x

Production


35/340


Upgrade methods

5. Upgrade clusters and users to 6.x products, one cluster at a time.

Figure 2-6 Upgrading clusters one at a time

6.x repositoryCluster 1 - 6.xProduction

Cluster 2 - 2.x

Production

Cluster 3 - 2.x

Production


36/340


Before You Start

Test systems

Although it is preferable to upgrade your system as fast as possible, BusinessObjects recommends that you do not complete the upgrade before testing thechanges that you made.

If you use the Split method (double repository), in effect you are already creatinga 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 tooquickly 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 properlybefore proceeding to the rest of your system.

Create a real test system before beginning the gradual upgrade of your

production system.


37/340


Time-frame for upgrading

Time-frame for upgrading

A number of factors can impact the amount of time needed for the upgrade. Inparticular, the complexity of the Business Objects environment and the generaloperating 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 byWebIntelligence documents contain multiple joins, they take longer to convertto version 6.x. If a refreshed document contains objects that are linked byeither multiple joins or an unoptimized join structure, the upgrade could takelonger than if the join structure was optimizedfor example, using shortcutjoins. 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 timeneeded for upgrading. If you are migrating many documents with numerouscells 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 BusinessObjectsusers. 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 youaccept 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. Youmay need to switch databases or make changes to your middleware.

Check Supported operating systems and platforms on page 40 to see whatthe impact would be on your upgrade.

number and type of server and client platforms that need to be modifiedbefore you start the upgrade of the Business Objects system

38 Mi ti f P i V i


38/340


Before You Start

customized applications

For example, WebIntelligence in a fully-customized JSP environment can betime-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.)



39/340


Repositories

Repositories

The version 6.x repository is virtually unchanged compared to 5.x. There are veryfew new columns and no new tables, only new types of data (such as documenttypes). 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.xSupervisor cannot function with a 6.x repository.

You need to check that your middleware and RDBMS are supported by version6.x. (See Supported operating systems and platforms on page 40.)



40/340


Before You Start

Supported operating systems and platforms

Business Objects recommends that you check the latest information onsupported platforms before you start to upgrade your Business Objects system.

For the full list of currently supported platforms and products, consult yourBusiness Objects representative, or check the latest PAR (Product AvailabilityReport). 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 customersupport.

Business Objects recommends that you check this information whenever youmake a change in your system.

http://www.techsupport.businessobjects.com/sta/PAR.asphttp://www.techsupport.businessobjects.com/sta/PAR.asp


41/340


Compatibility

Compatibility

This section discusses the compatibility between components of your previousand new Business Objects systems.

You can find additional information on compatibility for specific products in theproduct chapters (Part III of this guide, beginning on page 199).

Administration Console

Broadcast Agent

Can a ... Function on a ...

6.x cluster 2.x cluster

6.x Administration

Console

Yes No

2.x AdministrationConsole

No Yes

Can ... Process jobs scheduled in a ...6.x application 5.x application

6.x Broadcast Agent

Scheduler

Yes Yes (2.x/5.x documentskeep 2.x/5.x format)

5.x Broadcast Agent

Scheduler

No, not if they are 6.xdocuments

Yes



42/340

g g

Before You Start

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

IMPORTANT: Version 6.x documents cannot be opened in 2.x/5.x.

Can a ... Connect to a ...

6.x repository 5.x repository

6.x Broadcast Agent

Console

Yes Yes

5.x Broadcast Agent

Console

Yes Yes

Can ... Do the following with 6.x documents:

Retrieve Send or save as

corporate

6.x users Yes Yes

2.x/5.x users No No

Can ... Do the following with 2.x WebIntelligence

documents:

Retrieve Send or save as

corporate6.x users Yes Yes

2.x/5.x users Yes Yes



43/340

Compatibility

Can ... Do the following with 5.x BusinessObjects documents:

Retrieve Send Save as

corporate

6.x InfoView users Yes Yes No

6.x

BusinessObjectsusers

Yes Yes, but document

becomes 6.x

Yes, but document

becomes 6.x

2.x InfoView users Yes Yes Yes

5.x

BusinessObjects

users

Yes Yes Yes

When ... Refresh ...

a 2.x

WebIntelligence

document in

InfoView...

a 5.x

BusinessObjects

document in

BusinessObjects...

a 5.x

BusinessObjects

document in

InfoView...

6.x users it remains 2.x it remains 6.x it remains 5.x

2.x/5.x users it remains 2.x it remains 5.x it remains 5.x

When ... Edit ...

a 2.x WebIntelligence

document...

a 5.x BusinessObjects

document...

6.x users it becomes 6.x it becomes 6.x

2.x/5.x users it remains 2.x it remains 5.x



44/340

Before You Start

BusinessObjects in 3-tier mode

Repository

A 6.x Supervisor and a 5.x Supervisor can function on the same machine. Thesame is true for Designer and BusinessObjects.

Can ... Be started on ...

6.x InfoView 5.x InfoView

6.x BusinessObjects

(3-tier mode)

Yes No

5.x BusinessObjects

(3-tier mode)

No Yes

Can ... Function on a ...


6.x Supervisor Yes No

5.x Supervisor No Yes

6.x Designer Yes No

5.x Designer No Yes

6.x BusinessObjects Yes No

5.x BusinessObjects Yes Yes

Can a ... Be stored in a ...


6.x document Yes No

2.x/5.x document Yes Yes



45/340

Compatibility

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

6.x universe Yes Yes

2.x/5.x universe Yes Yes



46/340

Before You Start

Upgrade issues in international deployments

When you upgrade to version 6.x products, consider a number of changes thatare important for international deployments.

In BusinessObjects, you can now switch the language of the user interfacewithout having to restart your machine. You must have the necessary languagesinstalled. (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 Japaneseand English

You switch the language of the user interface in BusinessObjects viaTools > 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 userinterface language. This charset must be supported by your repository database.

Language and country information for documents is now stored in the documentitself. This prevents incorrect display when a document is shared by users withdifferent language formats. If you are accessing a Unicode database, you mustset the middleware to the charset corresponding to the language data you wantto 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 theDisplay tab of the InfoView Options Pages.

This feature applies to the following languages:

English

French

German Italian

Dutch

Spanish



47/340

Upgrade issues in international deployments

Supported languages

Supported languages are divided into full localization and customizedlocalization. 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 Objectsrepresentative or check the latest Product Availability Report (PAR) to find out

when a customized localization becomes available. As of this writing, the PARcan be accessed at the following URL:


To access this site, you must be registered for Business Objects online customersupport.

http://www.techsupport.businessobjects.com/sta/PAR.asphttp://www.techsupport.businessobjects.com/sta/PAR.asp


48/340

Before You Start

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?


49/340

pa

rt

Upgrade Workflows and

Scenarios


50/340


51/340

ch

apte

r

Generic Workflow: Split Method



52/340


Overview

Chapter 2 (Before You Start) explained what you need to know and do beforeyou start upgrading. In this chapter, we describe the actual upgrade proceduresfor 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 twoenvironments. When version 6.x operates satisfactorily on the test environment,you shut down the Business Objects system and upgrade all productionmachines at the same time. Versions 2.x/5.x and 6.x never functionsimultaneously on the same repository.

To upgrade using the Split method, follow the instructions in this chapter and insubsequent chapters:

This chapter provides the basic procedures you need to follow for upgradingallsystems. This is called the generic workflow.

Then, there are a number of scenarios that correspond to various types ofdeployment. These scenarios explain what you need to doin addition to thegeneric workflowin various specific deployments. Scenarios are containedin 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.xproduction environmentand then use your remaining 2.x/5.x machines foranother purpose. In this case, you would skip Phases 5 and 6. The proceduresin this chapter, however, assume that the entire original production environmentwill be upgraded after the test environment is validated.



53/340

To help you follow the order of the phases, you will see the following diagram atthe 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 necessaryprocedures are complete.



54/340


Phase 1 Modify the platforms

If necessary, upgrade your platforms to products and versions that are supportedby version 6.x. (See Supported operating systems and platforms on page 40.)

For example:

BEA WebLogicv. 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/340

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 tofunction 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 theprocedures below.

Suspend all Broadcast Agent jobs

Set all current jobs in declared Broadcast Agents to Suspended status. If this isnot 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 universedomains.

Then install Supervisor version 6.x on a Windows machine.



56/340


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.xSupervisor 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 (SeeCreate 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/340


5. On the Define the Repository Connection page, select the network layer, andthen 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 therepositorys 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 BusinessObjects 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. Thisupgraded 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 repositoryand asks whether you want to upgrade the repository to 6.x.

2. ClickYes.

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 aSupervisor earlier than 6.x.

3. Redefine the connections to the document and universe domains.

(For more information on repository and Supervisor compatibility, seeCompatibility on page 41.)

Compatibility of database connectionsVersion 6.x can view, modify, and save any connection (personal, shared, orsecured) created with 5.x.

Version 2.x/5.x can open, use, modify, and save a connection created by 6.x.



58/340


Phase 3 Upgrade desktop products (testenvironment)

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 inPhase 2. You can build a new 6.x cluster, but the instructions below assume thatyou are updating a portion of your existing 2.x/5.x system.


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 ofthe 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.xdesktop and administration products.



59/340

Phase 3 Upgrade desktop products (test environment)

To reinstall:1. Verify that the version 6.x license file is installed.

(For more information, see Licenses in the Installation and Configurationguide.)

2. Run the version 6.x Installation wizard.

When the wizard detects an earlier version of desktop products, you areprompted 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 installthe 5.x setup.exe file, and then rerun the 6.x installation.



60/340


Administration ConsoleWhen you upgrade the version 2.x Services Administrator to the 6.xAdministration 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 modulesthan 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 installationThe installation of desktop products on the client machine, via a server, is calledan administrative installation (previously called a master setup/standalone). Ifyou 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 andConfiguration guide.

Upgrade BusinessObjects documents

You upgrade version 5.x BusinessObjects documents to 6.x simply by openingthem in a 6.x product, and then saving the documents. The upgraded documentkeeps 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 productsin the same system: after a document is upgraded to version 6.x, it cannot bereopened by BusinessObjects 5.x.



61/340

Phase 3 Upgrade desktop products (test environment)

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 beenupgraded. Make sure that the document looks the same, and that all functionalityhas been transferred to version 6.x.

REMINDER

Version 6.x documents cannot be opened in 2.x/5.x.



62/340


Phase 4 Upgrade clusters (test environment)

You now continue to create the test environment. In this phase and the previousone, you are creating a test cluster that will be connected to the duplicaterepository you upgraded in Phase 2.

This section covers upgrading of clusters, which includes the upgrading of serverproducts.


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 togetheron the same cluster.

On UNIX, you can have 2.x and 6.x functioning on the same machine, if the twoversions do not share web servers or directories. (See the Installation andConfiguration guide.)



63/340


Shut down the Business Objects system1. 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 thenresubmit 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.xwhen you uninstall and reinstall the server products. However, you need to

manually copy certain files and resubmit them later. This is described below.

WindowsDefault settings for new users

Any changes made to a 2.x clusters default settings for new users are stored ina global profile.txt file. If you changed these settings, Business Objectsrecommends that you manually copy the file (you will resubmit the file afterreinstalling the 6.x server products).

Otherwise, new users will see the standard 6.x default settings when they log into6.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 userinformation. These files are stored at the cluster level, in the machine hosting theWIStorageManager.

Back up the entire Storage directory:

$INSTALLDIR\Server\WebIntelligence 2.5\Storage



64/340


System informationBusiness Objects recommends that you back up the following system informationfiles:

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 ServicesAdministrator by clicking the Global Report button.

Figure 3-3 Global Report button

This generates an HTML report containing the parameters.



65/340


UNIXOn UNIX, you need to back up and transfer the storage and configuration files tothe 6.x Business Objects system.

Storage files

Storage files include the profile.txt file, which contains some of the clustersglobal default settings for user information. If this file is not transferred, users willsee 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 andQT_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.xinclude:

Business Objects server

InfoView

WebIntelligence

BusinessObjects Web Installer Broadcast Agent

Business Objects recommends that you test the server products on a single userbefore deploying them to the entire pool of test users. Have the single user test:

personal and inbox documents

corporate documents

all universes



66/340


If you are satisfied with the results of this mini-test, enable the system for all usersin the test group.

WindowsTo uninstall and reinstall server products:

1. Shut down all Business Objects servers.

2. Uninstall all previous versions of Business Objects products from allmachines in the cluster.

To uninstall an earlier version of server products, use the Setup utility of thatversion. You can launch the Setup utility for the earlier version via theWindows Start menu (Programs > WebIntelligence 2.x > Setup).

Make sure you also uninstall any Business Objects components located onmachines 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 previousversions of either server or desktop products. (Server products andBusinessObjects 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 youcan 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/340


UNIXKeep in mind the following when you upgrade the cluster on UNIX:

The installer cannot automatically upgrade from version 2.x/5.x; you must dothis 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 ConfigurationTool):

Broadcast AgentAfter the upgrade to Broadcast Agent version 6.x, previously scheduled jobs arerecovered and reprocessed by the new Scheduler. If the task is based on aWebIntelligence document or a BusinessObjects document, the document iskept 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 acorporate document in a 6.x Business Objects product (such asBusinessObjects), 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 AgentConsoles. A version 6.x Console can connect to a 5.x repository and a 2.xcluster. 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 onpage 207.)

2.x directory 6.x directory

$WIDATADIR/Config $INSTALLDIR/nodes//

/config

$WIDATADIR/

Universe

$INSTALLDIR/nodes//

/universe



68/340


Resubmit user and system informationYou must now resubmit the user and system information that you copied earlier(see Copy user and system information on page 63.)

WindowsTo 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; forexample, in My InfoView.

Individual settings for transition users

When users modify their personal settings in InfoView, the new profile is storedin an individual profile.txt file that is separate for each user. This is not the sameas the globalprofile.txt file discussed above.

In order for users making the transition from 2.x/5.x to 6.x to preserve theirpersonal user settings, these files are transferred to the 6.x Business Objectssystem.

This is done automatically by the system, but Business Objects recommends thatyou verify that it was completed. In version 6.x, the individual profile.txt files arein:

$INSTALLDIR\nodes\\\storage\user\

If necessary, you can manually transfer the files, or use the Configuration Tool.



69/340


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\

2. Paste the file into the 6.x folders for each user in the machine hostingWIStorageManager:

$INSTALLDIR\nodes\\\storage\user\

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



70/340


NOTE

When transition users log out of InfoView 6.x for the first time, they are promptedto save their individual settings (if they did not already click Save on the Optionspage). 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 userinformation. You can find these files in the Storage directory that you backed upearlier. Note that these files are unique to each user.

Copy the following files:

$INSTALLDIR\Server\WebIntelligence 2.5\storage\list\\mail.txt$INSTALLDIR\Server\WebIntelligence 2.5\storage\list\\unv.txt$INSTALLDIR\Server\WebIntelligence 2.5\storage\mail\\read.txt$INSTALLDIR\Server\WebIntelligence 2.5\storage\user\\attribut.txt

$INSTALLDIR\Server\WebIntelligence 2.5\storage\user\\*.ctgPaste the files (in 6.x) into parallel folders at:

$INSTALLDIR\nodes\\\storage

EXAMPLE

The first file listed above, mail.txtfor the user named would be

pasted into the following location in 6.x:

$INSTALLDIR\nodes\\\storage\list\biguser\mail.txt

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


To transfer the storage files using the Configuration Tool:


71/340


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.

Figure 3-6 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///storage).


Configuration files


72/340


Configuration filesTo 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///config/servers

2. Reset the values you noted when you backed up the files. They have beenrenamed in 6.x to MsgAdminMaxActiveTime andMsgAdminMaxInactiveTime, located in

$INSTALLDIR/nodes///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 retrievethe 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//

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

Reactivate Broadcast Agent jobsReactivate (set to Normal status) all Broadcast Agent jobs that you suspendedbefore upgrading the repository.

Then, verify that Broadcast Agents are being monitored in the AdministrationConsole.


Restart the servers


73/340


Restart the serversOn the test-environment cluster that you upgraded, restart the servers and havethe users log in.

Upgrade WebIntelligence documents

You upgrade WebIntelligence 2.x documents (.wqy) to version 6.x (.wid) byediting them in InfoView version 6.x, and then saving them as a personal orcorporate document.

NOTE

Upgrade of WebIntelligence 2.x documents is supported only for version 2.5 orlater. 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 isupgraded to version 6.x.

Note that the former 2.x (.wqy) document remains in the repository. It will beaccessible 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, youmust delete them manually.

After you upgrade to version 6.x, users see in InfoView the same documents theypreviously had the right to view (in the Personal Documents, CorporateDocuments, 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 Documentexchange on page 42).


Cells set to automatic size


74/340


By default, table cells set to automatic size in WebIntelligence 2.x are set toAutoFit in version 6.x. WebIntelligence documents with many cells set toautomatic size may take a long time to open in InfoView 6.x. Therefore, migratingthese documents could be time-consuming.

If you are migrating many such documents, consider doing one or both of thefollowing:

Perform the migration at a time when server use is minimal.

Before migrating the documents, change the cell settings from automatic sizeto 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 BusinessObjects 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/340



In this phase, you repeat phases 3 and 4, but this time you do it for all themachines 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 thenreconnect it to the upgraded clusters (Phase 6).

Shut down the Audit facility

The Audit facility tracks crucial information on user and system activity (see TheAudit Facility and Auditor on page 201). To ensure a smooth upgrade of thefacility, shut it down before upgrading any Business Objects products in yourproduction system to version 6.x.


To shut down the Audit facility:1 Open the version 2 x Services Administrator


76/340


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.


Phase 6 Upgrade original repository andl


77/340

Phase 6 Upgrade original repository and reconnect clusters

Phase 6 Upgrade original repository andreconnect 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 productionenvironment.

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.


3. At Log to Database, click On.


78/340


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


y y

After you complete the upgrading of product software and documents, try usingthe new features in the latest version. If you encounter any difficulties, seeFrequently Asked Questions on page 319.

For a complete description of these features, see Whats New in this Release onthe documentation website. You can access the site by doing any of thefollowing:

Choosing More Tips and Samples from the Help menu in version 6.x desktopproducts

Clicking the More Tips and Samples link in the InfoView 6.x navigation bar

Going to the website:


Test desktop and administration products

Confirm that you can open and use the basic functionality of the new desktop andadministration products:

BusinessObjects

BusinessQuery for Excel

Designer

Supervisor

Auditor

Administration Console


Test server productsConfirm that you can connect and use the basic functionality of the new server


80/340


y yproducts:

WebIntelligence

InfoView

Broadcast Agent

InfoViewCheck that:

the browser configuration indicator in InfoView (accessed from the Loginpage) 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 theypreviously had the right to view (in the Personal Documents, CorporateDocuments, Inbox, and Scheduled Documents folders). Confirm this for severalusers.

Upgrade several documents from 2.x/5.x to 6.x. Make