BusinessObjects 6.

x to XI Release 2
Migration Guide

BusinessObjects XI Release 2 Update

Windows and UNIX

Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.

Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.

Copyright Copyright © 2006 Business Objects. All rights reserved.

Last update: March 2006

2 BusinessObjects 6.x to XI Release 2 Migration Guide

Contents
Chapter 1 Introduction 9
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Part I Migration fundamentals

Chapter 2 Migration essentials 13

What this guide covers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
What this chapter covers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tools to help you migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Migration methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Basic XI R2 concepts you need to know . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Top challenges as you migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
What migrates (and what doesn’t) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Migration phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 3 How XI R2 compares with version 6.x 35

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Product offering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Basic terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Installation, configuration, and deployment . . . . . . . . . . . . . . . . . . . . . . . . 45
Security model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Authentication/authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Reporting, analysis, information sharing . . . . . . . . . . . . . . . . . . . . . . . . . . 56
SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

BusinessObjects 6.x to XI Release 2 Migration Guide 3

Contents

Part II Understanding what migration entails

Chapter 4 Understanding user and group migration 65

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Users, groups, and their organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
User/group access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
How users and groups migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Consequences of importing users and groups . . . . . . . . . . . . . . . . . . . . . . 74
Delegated Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Migrating external groups (LDAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 5 Understanding object migration 81

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
What kinds of objects can be imported? . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Broadcast Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Universes and universe connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Stored procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Folders, domains, and categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 6 Understanding Application Foundation object migration 99

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Migrating to Performance Management XI R2 . . . . . . . . . . . . . . . . . . . . . 100
Migrating the Application Foundation repository and its contents . . . . . . . 104
Migrating dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Migrating analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Migrating schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Migrating rules and named events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Migrating security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
What you cannot migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 7 Understanding rights migration 117

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

4 BusinessObjects 6.x to XI Release 2 Migration Guide

 Comparison of the security models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Standard migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Special import scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Rights by product/component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 8 Understanding Import Wizard options 165

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Security migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
The Merge and Update import scenarios . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 9 Understanding deployment configuration migration 183

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
XI R2 deployment rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Migrating deployment configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Part III Migration planning and assessment

Chapter 10 Assessing migration by product and functionality 191

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
BusinessObjects/Desktop Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Web Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Designer and universes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Auditing and Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Scheduling and publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
SDKs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Application Foundation/performance management . . . . . . . . . . . . . . . . . 207
Web Intelligence OLAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Chapter 11 Recreating security in XI R2 209

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Designing your security model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Group security by functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Content security: access to reports and universes . . . . . . . . . . . . . . . . . 214

BusinessObjects 6.x to XI Release 2 Migration Guide 5

Contents

Security model for functionality and content combined . . . . . . . . . . . . . . . 218

Administrators group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 12 Planning the migration 221

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Formulating your migration strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
High-level migration strategy scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Repository migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Migrating to XI R2-supported versions and platforms . . . . . . . . . . . . . . . . 237
Capturing scheduling information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
What users/groups should you migrate? . . . . . . . . . . . . . . . . . . . . . . . . . . 238
What objects should you migrate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Setting up a new folder/group structure . . . . . . . . . . . . . . . . . . . . . . . . . . 241
International considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Cleaning up your source environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Part IV Importing to the destination environment

Chapter 13 Before using the Import Wizard 251

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Before installing XI R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Installing XI R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Before importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Chapter 14 Using the Import Wizard 261

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Launching the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Setting the source and destination environments . . . . . . . . . . . . . . . . . . . 264
Selecting the types of objects to import . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Selecting an import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Importing specific objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Finalizing the import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

6 BusinessObjects 6.x to XI Release 2 Migration Guide

 If you’re migrating Application Foundation . . . . . . . . . . . . . . . . . . . . . . . . 274
Selecting the types of objects to import . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Selecting an import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Importing specific objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Finalizing the import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Part V Verifying and completing the new environment

Chapter 15 Checking and adapting the new environment 289

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Verifying overall import success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Checking user/group and object import . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Checking imported documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Checking universe access restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Checking and adjusting security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Recreating scheduling jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Verifying the Performance management environment . . . . . . . . . . . . . . . 299

Chapter 16 Checking for calculation updates 301

Where you are now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Document conversion during import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
BusinessObjects document migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Part VI Appendices

Appendix A Migration checklist for single pass migrations 323

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Preparing the source environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Preparing the destination environment . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Importing from the source to destination environment . . . . . . . . . . . . . . . 326
Post-import checking and tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Transferring or recreating other functions and tasks . . . . . . . . . . . . . . . . 327

BusinessObjects 6.x to XI Release 2 Migration Guide 7

Contents

Appendix B Business Objects Information Resources 329

Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . 330
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . 331
Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

8 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Introduction

chapter
1 Introduction
About this guide

About this guide

This guide describes how to migrate the BusinessObjects Business
Intelligence suite from a version 6.x source environment to BusinessObjects
Enterprise XI Release 2.
This guide includes improvements to migration that you receive when you
install the BusinessObjects Enterprise XI R2 Migration Pack.
For more information and instructions on installing XI R2, see the
BusinessObjects Enterprise XI R2 Installation Guide.
For information and instructions on installing the BusinessObjects Enterprise
XI R2 Migration Pack, see the Business Objects XI R2 Migration Pack
Installation Notes.

Who should read this guide

This guide is intended for system administrators and IT personnel who are
responsible for the migration.

Business Objects information resources

For more information and assistance, see Appendix B: Business Objects
Information Resources. This appendix describes the Business Objects
documentation, customer support, training, and consulting services, with links
to online resources.

10 BusinessObjects 6.x to XI Release 2 Migration Guide

Migration fundamentals
12 BusinessObjects 6.x to XI Release 2 Migration Guide
BusinessObjects 6.x to XI Release 2 Migration Guide

Migration essentials

chapter
2 Migration essentials
What this guide covers

What this guide covers

This guide describes how to migrate from BusinessObjects version 6.x to
BusinessObjects XI Release 2.
This includes the migration of:
• the Business Objects Business Intelligence suite
• Application Foundation (from version 6.1b)
If you have BusinessObjects Analytics and you want to migrate to
Performance Management Applications on version XI R2, see the
Performance Management Applications Migration Guide.
Note: Unless more specific version numbering is required, the source
version of the Business Objects suite is referred to as version 6.x throughout
this guide, and the destination environment is referred to as version XI R2.
Depending on the precise source version you are using, certain options and
features listed in this guide may not be available.

What this guide does not cover

This guide does not cover:
• migrating from versions of Business Objects previous to version 6.0
• migrating Application Foundation versions previous to version 6.x
Updating or upgrading to version XI R2 from Crystal Enterprise 8 or 9, or from
BusinessObjects XI, is explained in the BusinessObjects Enterprise XI R2
Installation Guide.

What this chapter covers

• Tools to help you migrate
• Migration methods
• Basic XI R2 concepts you need to know
• Top challenges as you migrate
• What migrates (and what doesn’t)
• Migration phases

14 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Tools to help you migrate 2
Tools to help you migrate
Import Wizard
You import most of your source environment to BusinessObjects Enterprise
XI R2 using a single tool called the Import Wizard. The Import Wizard is a
locally installed Windows application that allows you to import most objects in
the repository, including user accounts, groups, folders, universes, and
documents, as well as objects stored in Inbox and personal folders on cluster
servers, to your new BusinessObjects Enterprise system.
The Import Wizard acts as a bridge between the source repository and the
target CMS repository (InfoStore). The Import Wizard:
• imports content from the source repository
• updates content (for example, universe IDs), and converts document
format where necessary (for example, version Web Intelligence 2.x .wqy
documents to version XI R2 Web Intelligence .wid files, as well as version
6.x BusinessObjects .rep files into version XI R2 .rep files)
• exports content into the target repository and physical storage area
At the end of the import, the Import Wizard creates a log file you can check for
information about successful operations and issues.
Exactly how the Import Wizard manipulates each object, as well as how to
use this wizard is fully described later on in this manual.
Note: The Import Wizard imports Application Foundation objects from
version 6.1b and later only.

Import Wizard requirements

The Import Wizard requires that you configure the following connections/
paths before import:
• appropriate middleware installed and correctly configured so that the
Import Wizard, like Supervisor or BusinessObjects, can connect to the
source repository domains
• ID and password to connect to the target repository database
• a path to Storage\Mail on the source server (optional)
• a path to Storage\Users on the source server (optional)

BusinessObjects 6.x to XI Release 2 Migration Guide 15

2 Migration essentials
Tools to help you migrate

The Import Wizard requires:

• a fast hard disk (import may require a series of report Open/Save
operations)
• extensive available disk space for temporary files created during import
Because for any given import session, all documents are copied to a
temporary disk space, free disk space equivalent to the size of your
source repository is required, at a minimum.
• fast connections to both the 6.x and XI R2 systems
When migrating from version 6.x, you must have:
• a BOMain.key file and a General Supervisor profile to be able to connect
with the source repository
• an ID and password to connect to the destination CMS

Backing up your source repository

Business Objects strongly recommends backing up your 6.x source
repository before beginning the migration.
In addition, it is good practice to run the Import Wizard on a copy of the
source repository, and not on the production version. If you follow this
practice, make sure that you point all the domains to the copied repository, so
that the domains are no longer associated with the original (production)
repository.

BIAR files
The Import Wizard can also package BI content into Business Intelligence
Application Resource (BIAR) format for backup or change management once
you’ve already imported into the new environment.
For information on BIAR files, see the Import Wizard online help.

The Report conversion tool

Another tool, called the Report conversion tool, is also available to convert
BusinessObjects documents in version 6.x to Web Intelligence documents
after you import them to the destination environment. As version XI R2
supports these documents, however, this type of conversion is a deployment
choice, and not an integral part of the migration process.
For complete information on this tool and how to use it, see the Report
Conversion Tool Guide.

16 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Migration methods 2
For more information on how to decide what BusinessObjects documents to
migrate or convert, see “What objects should you migrate?” on page 239.

Migration methods
You can migrate to version XI R2 either in a very short time frame, or in a
series of incremental imports over a period of time. Whatever method you
use, you will need to keep both source and destination environments
deployed long enough to be able to compare and ensure that all BI content
has been migrated safely and reliably.
• The single pass method involves migrating to version XI R2 in a single
pass with the Import Wizard.
This method may be more suitable for smaller, less complex
deployments.
• The larger your deployment, the more likely you will want to migrate
gradually. The incremental method allows you to migrate application by
application, domain by domain, or even locale by locale, validating the
import’s success after each sweep with the Import Wizard; if there are
issues, you don’t have to begin the entire migration all over again.
For more information on migration strategies, see “Formulating your migration
strategy” on page 222.

Migrating optimally using consulting

Each migration has its own challenges, whether they concern a high degree
of customization, the use of unusual server/web server/application server/
database configurations, or sheer size.
Regardless of the size or complexity of your deployment, Business Objects
recommends that you take advantage of the Business Objects Professional
Services Organization (PSO) to assist you in determining the ideal
requirements for your organization and how best to shape your initial
deployment.
The PSO is a team of BI experts with all the planning, delivery and
standardization skills you need to drive a successful migration to the XI R2
platform. You can contact PSO either through your Business Objects
representative, or at http://www.businessobjects.com/services/consulting/
default.asp.

BusinessObjects 6.x to XI Release 2 Migration Guide 17

2 Migration essentials
Basic XI R2 concepts you need to know

Basic XI R2 concepts you need to know

Chapter 2 in this guide gives you a much more detailed comparison of version
6.x and XI R2. Before going any further, however, you should understand the
following key differences.

The Central Management Server (CMS)

The CMS is the central process in the XI R2 BusinessObjects Enterprise
intelligence layer.
A single service, it provides framework services, security management,
administers scheduling tasks, and also is responsible for maintaining
databases containing system information, the repository and the audit
database.
Because it maintains the repository database, all connections to the
repository must pass through the CMS, including login from the full client
(renamed Desktop Intelligence in XI R2). This in turn means that all XI R2
deployments include a computer hosting what in version 6.x is called
Business Objects server components.
The main functions of the CMS are:
• Coordinating communication between servers
Servers use the CMS to locate the services exposed by other servers.
• Coordinating communication between the SDK and the backend
The SDK uses the CMS to locate the services exposed by servers.
• Maintaining the CMS repository (InfoStore)
The CMS repository is a database that stores information essential to
system operation. For example, the repository keeps track of available
documents, maintains security information about users and documents,
and know what servers are currently available.
Information is stored in the repository as InfoObjects.
The main core services the CMS exposes include:
• InfoStore service (the repository)
• security and logon service
• deployment service, which controls plugins
• name server, which provides a directory of available servers
The BI platform must have at least one CMS running at all times.

18 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Basic XI R2 concepts you need to know 2
Repositories
Version 6.x deployments are based upon a central repository, which is a
database stored in a relational database management system. The repository
is used to secure access to your data warehouse and provide an
infrastructure for distributing information to be shared by users.
This repository database contains the data associated with the security,
universe and document domains (universes, documents, etc.).

InfoObjects in the CMS

In version XI R2, the repository is one of several system databases
maintained by the CMS. The CMS repository stores information about the
system’s operation and administration, but does not store content data such
as .wid files. For example, when a document is published to the repository,
the meta-data about the document is stored in the CMS repository as an
InfoObject, while the document itself (the .wid file) is physically stored, along
with its data, in separate storage associated with the File Repository Server
(FRS).

InfoObjects store information like ID number, InfoObject type, and scheduling

information that allows BusinessObjects Enterprise to manage each
component.
InfoObjects that do not have associated FRS files (that is, InfoObjects that do
not represent documents, such as users or groups) contain all the information
required to make the managed object functional within the system.

BusinessObjects 6.x to XI Release 2 Migration Guide 19

2 Migration essentials
Top challenges as you migrate

The Central Management Console (CMC)

Version 6.x relies upon a set of tools that allow you to set up and administer
your BI solution, including:
• Supervisor/Supervisor over the Web for creating the repository and
creating users and groups and their access rights
• the Administration Console for administering and monitoring the cluster
and its components
• the Auditor application for auditing and analyzing system usage
• Broadcast Agent for the scheduled processing and distribution of
documents
In XI R2, a centralized web-based administration tool called the Central
Management Console (CMC) provides you with a single interface through
which you can perform almost every administrative task. Through the CMC,
you perform user management tasks such as setting up authentication and
adding users and groups. It allows you to publish, organize, and set security
levels for all BusinessObjects Enterprise content, manage server processes
and create process groups, and audit activity throughout the system. For
more information, see the BusinessObjects Enterprise XI Release 2
Administrator’s Guide.

Top challenges as you migrate

• The security model is different
• The licensing model is different
• Domains are migrated to a single database
• Supported deployment configurations are different
• The Application Foundation repository is upgraded
• Post-import verification is required

20 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Top challenges as you migrate 2
The security model is different
The security model is fundamentally different in function and organization.

In version 6.x In version XI R2

The security model is user/group- Security is object-centric, based on
centric. ACLs.
For example, you select your user/ For example, you select an object
group and apply a right, such as such as a document or folder, and
access to a document. then grant access to it.
Aggregate and inheritance rights Aggregate and inheritance rights are
depend on the type of objects. the same for all objects and are more
secured than in 6.x.
Domains serve as context Each domain becomes a folder.
mechanisms. Migrated document/universe
relationships are still preserved.
Documents are published to/stored Documents are also stored in a
in domains; you then assign which container (a folder), but you no
groups will have access to them. longer specify security at the time of
The same is true of universes. publishing. You create a folder
structure to reflect user/group
access: whoever has access to the
folder has access to the contents of
that folder (inheritance) – just like in
Windows.
The same is true of universes.

ACLs
The security rules that existed in version 6.x (such as product access, objects
rights, and security commands) are enforced in XI R2 by the ACL (Access
Control List) mechanism. An ACL is set on an object to define what rights
users and groups have on that object, and is composed of a list of ACEs
(Access Control Entities), which specify the state of a single right for a single
user/group.

Right values
Rights can only have three values:
• Unspecified
• Denied
• Granted

BusinessObjects 6.x to XI Release 2 Migration Guide 21

2 Migration essentials
Top challenges as you migrate

The version 6.x security command value Hidden does not exist and is
mapped to the Denied value.

Migrated rights
If you migrate security along with users/groups and objects, migration is
designed to maintain the same level of security between the 6.x and the XI R2
CMS repository. Nonetheless, rights after import may be unexpected,
especially after any modification in the CMS, and if you import rights, you will
need to check them carefully in the destination environment.
Version 6.x Supervisor accessed both query databases and the repository
using database middleware. In XI R2, Supervisor is replaced by two different
tools:
• Designer, which allows you to manage connections and access
restrictions, or universe overrides. A restriction can consist of
connections, query limit controls, SQL options, object and row
restrictions, and/or table mappings.
• The Central Management Console (CMC), which allows you to manage
security on users, groups, folders, connections, universes and
documents.
For more detailed information on XI R2 rights and migration, see
“Understanding rights migration” on page 117.

Aggregation
Aggregation is very different in the new environment.
During aggregation, the more restrictive value of an instance is applied.
As a result:
• If you set a right to Denied for a group, even if you set it to Granted for
one of its members, the member won't have the right. The only way to get
around this restriction is to break inheritance in the CMC.
• If users belongs to several groups, and if for one group they inherit a
Denied value for a right, they will have a Denied value, even if they inherit
the Granted value for this right from other groups.
For more details, see “Rights aggregation” on page 71.

Specific groups
The following groups exist by default in XI R2:
• Everyone, which contains all users
• Administrators

22 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Top challenges as you migrate 2
• Universe Designers Users
• Report conversion tool Users
The following users exist by default in XI R2:
• Administrator
• Guest

Profile migration
User profiles, used in version 6.x to define product access, are no longer
used. In XI R2, they are replaced by ACLs for applications, folders, and
documents.
If you choose not to migrate security, profiles are not migrated, and therefore,
General Supervisors and all other types of administrators are no longer
Administrators, unless you manually grant them the necessary rights.
If you choose to migrate security:
• General Supervisors are added to the Everyone, Administrators, and
Report Conversion Tool Users groups. By default, they have most but not
all rights.
• Users whose profiles allow them to run Supervisor (Supervisor/
Supervisor-Designer/Versatile with Supervisor access):
• have the View access level for the groups to which they belong in
version 6.x
• have the Full-Control access level for the users and subgroups of the
groups to which they belong in version 6.x
• Users whose profiles allow them to run Designer (General Supervisor/
Designer/Supervisor-Designer/Versatile with Designer access), on the
other hand, are not added to the Universe Designer Users group.
In the XI R2 user/group model, when users are imported into multiple groups,
multiple instances of the user are not created. The user simply belongs to
multiple groups.
Note: For more detailed information about the implications of the Import
Wizard’s security migration options, see “Security migration options” on
page 166.

BusinessObjects 6.x to XI Release 2 Migration Guide 23

2 Migration essentials
Top challenges as you migrate

The licensing model is different

In XI R2 the product is license model-aware. The license keys issued to you
specify the type of license you can use. The product enables users access
based on the license and the usage or registered number of users within the
repository.
For organizations migrating to XI R2 from version 6.x, two license models are
available:
• Named user licenses are associated with specific users, and allow users
to access the system based on their user name and password.
• Processor licenses are based on the number of processors running
version XI R2.
When migrating from 6.x to XI R2 you may have a named user license. In this
case, the first x migrated users will be set to Named Users, where:
x = (Number of users allowed by the named licenses) - (Number of users
already set to Named Users)
• If x is greater than the number of users that must migrate, then all users
will be able to login.
• If x is less than the number of users to migrate, then the remaining users
will not be able to login; these users will not have been set to use a
Named User license, and you will not have any other license model to
enable these users.
You can set the license model explicitly for each user within the CMC.

Domains are migrated to a single database

In version 6.x, domains serve as context mechanisms. For example, simply
moving a document from one domain to another can result in the document
being run against a production database rather than a test database.
During migration, domains are migrated as folders in the CMS database, with
the domain’s contents stored in the corresponding folders.
Even if the repository is made of several document and universe domains
located in different locations, all the domains are migrated as folders in to a
single CMS repository database.
For more information on what happens to universes when they are migrated,
see “Universes and universe connections” on page 89.

24 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Top challenges as you migrate 2
Supported deployment configurations are different
As the version XI R2 architecture differs from version 6.x, the same types of
deployment configurations are not necessarily supported in the two
environments. Some examples are:
• In 6.x, 2-tier (Desktop) deployments of BusinessObjects don’t require a
Business Objects server to access the repository. In XI R2 you must go
through the CMS server component.
• In 6.x, the various repository domains can be geographically distributed
over multiple sites. In XI R2, the repository databases and file systems
must be in one location.
For more information, see Chapter 9: Understanding deployment
configuration migration.

The Application Foundation repository is upgraded

Objects stored in the Application Foundation repository and locally on the
Application Foundation server are upgraded in the Application Foundation
repository (version 6.1.b and 6.1.3 repositories are first upgraded to version
6.5.1, then upgraded to XI R2) before being migrated to the XI R2 repository.
The Import Wizard also writes new tables and columns to the Application
Foundation repository during migration.
Business Objects strongly recommends that you backup the repository before
migrating.

Post-import verification is required

While importing users/groups and objects from the source deployment using
the Import Wizard is simple, Business Objects recommends that you carefully
check the objects you have imported for changes that may have occurred
during import, and if you have chosen to migrate security, for access right
levels in the new environment.
Certain documents are automatically updated.
• In general, the older the version of BusinessObjects used to create full-
client documents you are importing, the more extensive the calculation
engine changes in the reports in the new environment. For complete
information, see “BusinessObjects document migration” on page 302.

BusinessObjects 6.x to XI Release 2 Migration Guide 25

2 Migration essentials
What migrates (and what doesn’t)

• During import, all Web Intelligence documents in .wqy format from

version 2.x are automatically converted to the version 6.x .wid format.
There may be minor changes in the converted documents. For complete
information, see “Web Intelligence documents” on page 294.

What migrates (and what doesn’t)

This section provides an overview of:
• Software migration
• Resource migration
For more details, see “Assessing migration by product and functionality” on
page 191.

Software migration
The following table presents the different products and their equivalent in
XI R2 after migration.

Software Requirements Comments

Supervisor, Supervisor over Install CMC Most Supervisor and Supervisor over the
the Web (Central Web tasks are carried out by the web-based
Management CMC.
Console), as Designer, however, now allows you to set the
well as following universe-based parameters:
Designer
• connection overloads
• row restrictions
• timestamps
• size restrictions
Designer Update Has incorporated some functionality
previously included in Supervisor (see
previous row in this table).
BusinessObjects Update Renamed Desktop Intelligence.

26 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
What migrates (and what doesn’t) 2
Software Requirements Comments
• 2-tier (Desktop) mode Install side-by- Not true for client-server in XI R2. Can install
side + CMS version XI R2 alongside version 6.x. You
(Central must install a CMS (Central Management
Management Server) on the network for login, even for
Server) install offline mode.
Workgroup mode becomes Standalone
mode, in which there is no repository
connection and no repository.
• 3-tier mode Update Install from CD required; no downloading
from InfoView. Online and offline modes
supported.
• Viewing through InfoView Update + Rework required only if InfoView was
rework customized in version 6.x.
BusinessQuery for Excel Recreate Recreate Excel worksheets with Live Office.
Results may not be identical.
Server software (Web
Intelligence, InfoView, cluster
infrastructure)
• On Windows Re-install
• On UNIX Can install
side-by-side on
same machine
WebIntelligence Update Renamed Web Intelligence.
InfoView Update Has been redesigned and integrated into the
XI R2 framework.
Auditor Recreate XI R2 comes with a special auditing universe
and two sets of pre-defined reports (one for
Web Intelligence, one for Crystal Reports) for
reporting off of the Audit database, in order to
report user, document, application, and
server event monitoring.
Broadcast Agent Update + Scheduling capabilities are handled by the
Recreate CMS.

BusinessObjects 6.x to XI Release 2 Migration Guide 27

2 Migration essentials
What migrates (and what doesn’t)

Software Requirements Comments

Application Foundation Renamed performance management, which
(Dashboard Manager and includes these products:
Performance Manager) • Dashboard Manager
• Performance Manager
• Set Analysis
• Predictive Analysis
• Process Analysis
Process Tracker is available on a separate
CD.
Data Integrator Update You can re-install over the existing version.
Developer Suite No longer available:
• Web Intelligence SDK (WIBean/WICOM)
• Admin SDK
• RECOM (MSFT is replacing COM with
.NET)
Available:
• BOE SDK (Java and .NET)
• Report viewer SDKs
• REBean
• RENET
Custom applications ASP pages need to be rewritten in ASPX to a
new .NET SDK; JSP pages based on
WIBean need to be rewritten; JSP pages
based on REBean still work in XI R2.

Resource migration
Note: Resources exclusive to Crystal Enterprise and BusinessObjects XI are
not included in this table. For information on migrating from these two
environments, see the BusinessObjects Enterprise Installation Guide.

Resources Migration Comments

method
Core repository
• Security domains Import Wizard Users and groups are migrated as users and
groups in the CMS.

28 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
What migrates (and what doesn’t) 2
Resources Migration Comments
method
• Universe domains Import Wizard Universe domains are imported as universe
folders in the CMS.
• Document domains Import Wizard Document domains are imported as
document folders in the CMS.
Documents
• BusinessObjects (.rep) Import Wizard Check the calculations in migrated
documents.
• VBA add-ins (.rea) VBA add-ins don’t work on the server in XI
R2. Instead, you can use embedded VBA
macros (except for VBA macros that include
calls to the platform such as Login or Logout)
to extend Broadcast Agent Scheduler
functionality.
• Web Intelligence (.wqy) Import Wizard As .wqy format is no longer supported in
BusinessObjects Enterprise XI R2, these
files are automatically converted to .wid
format during import. Check the calculations
in migrated documents.
• Web Intelligence (.wid) Import Wizard Check the calculations in migrated
documents.
• Inbox Import Wizard These documents, for migrated users only,
are migrated into the user’s Inbox folder in
the CMS. You cannot choose which Inbox
documents you migrate (all or nothing).
• Personal Import Wizard These documents, for migrated users only,
are migrated into the user’s Favorites folder
in the CMS. You cannot choose which
personal documents you migrate (all or
nothing).
Semantic layer
• Universes Import Wizard Restrictions are migrated and stored as
InfoObjects in the CMS repository. In XI R2
they are called access restrictions (in version
6.x they were called universe overloads), and
are set using Designer.
• Stored procedures Import Wizard Stored procedures are migrated as
connection rights.

BusinessObjects 6.x to XI Release 2 Migration Guide 29

2 Migration essentials
What migrates (and what doesn’t)

Resources Migration Comments

method
• Connections Import Wizard When migrating, Import Wizard
automatically:
• replaces BOUSER and BOPASS with
DBUSER and DBPASS in universes
• proposes the automatic population of
these variables for users to migrate
Broadcasting
• Broadcast Agent Recreate A Broadcast Agent job can be migrated from
Scheduler jobs BusinessObjects Enterprise 6.x to XI R2 only
if the job is supported in XI R2.
A job can be imported only if its first action is
a Refresh.
A job cannot be imported if it has any of the
following:
• multiple outputs
• conditional processing
• VBA add-ins
• report bursting (“refresh with the profile of
each recipient”)
• saved in XML, RTF, HTML, or TXT
format
• Broadcast Agent Publisher Recreate Recreate using the CMC (Central
email publications Management Console) scheduling
capabilities, or using BusinessObjects XI R2
Publisher.
• Broadcast Agent Publisher Recreate
web publications
OLAP
• Web Intelligence OLAP Recreate Recreate using OLAP Intelligence.
documents
• BusinessQueryMD Recreate Recreate using Live Office.
• BusinessObjects OLAP Recreate Recreate using Web Intelligence or Crystal
documents Reports.
Application Foundation

30 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Migration phases 2
Resources Migration Comments
method
• Application Foundation Import Wizard 6.1.b, 6.1.3 through 6.5 repositories are
repository updated in place.
• Documents (.afd) Import Wizard Documents pull required universes.
• Sets, metrics, goals, Import Wizard Metrics pull required universes.
calendars
• Dashboards, menus, Import Wizard Dashboards pull .afds, .reps and .wids, which
applications pull universes.
• Role definitions in Recreate
Performance Manager
6.5.1

Database migration
Migrating to a different repository database
The databases supported as repository databases in version 6.x may not be
supported as CMS databases in version XI R2.
Nonetheless, the Import Wizard can import objects from any supported type
of source repository database seamlessly into any supported CMS repository
database.

Migrating query databases

All data access is kept from version 6.x. Connection Server is an integral part
of BusinessObjects Enterprise XI R2, and all the databases it supported in
version 6.x continue to be supported in the new environment. Check the latest
list of supported platforms for supported driver versions.
For a constantly updated list of supported platforms and versions, see:
http://support.businessobjects.com/supported_platforms_xi_release2/

Migration phases
Migration involves the following broad phases, reflected in the organization of
this guide:
• Understanding what migration entails
• Assessment and planning
• Importing to the destination environment

BusinessObjects 6.x to XI Release 2 Migration Guide 31

2 Migration essentials
Migration phases

• Post-import checking and tuning

For your convenience, throughout this guide, a table at the beginning of each
chapter summarizes the overall migration process in numbered steps, and
indicates where you are in it.
The rows in blue are the steps described in the current chapter.

Where you Step in overall migration process

are now

D 1. Understanding what migration entails

2. Assessment and planning

3. Preparing for import

4. Importing from the source to destination environment
5. Post-import checking and tuning

Understanding what migration entails

Before you install BusinessObjects XI R2, you should understand what the
migration process entails, how the new environment differs, what happens
during migration, and what you should expect once you get there.
Business Objects highly recommends that you read this chapter, as well as
the following chapters carefully:
• For a high-level understanding of how BusinessObjects XI R2 differs from
your source environment, read “How XI R2 compares with version 6.x” on
page 35.
• To understand how different components and characteristics of your
Business Intelligence deployment are migrated from one environment to
the other, as well as specific migration constraints, read carefully:
• “Understanding user and group migration” on page 65
• “Understanding object migration” on page 81
• “Understanding Application Foundation object migration” on page 99
• “Understanding rights migration” on page 117
• “Understanding Import Wizard options” on page 165

32 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration essentials
Migration phases 2
Assessment and planning
Migration assessment and planning means calculating precisely what is
required to migrate to the new environment given your particular source
deployment, and the parts of it you want to migrate to XI R2.
• Familiarize yourself with what migration requires given the version from
which you are migrating, and the products/functionality you want to
migrate. This chapter also details the differences you can expect in XI R2
for each component you want to migrate. See “Assessing migration by
product and functionality” on page 191
• Understand the basic deployment configuration rules for XI R2, and what
it takes to migrate from your version 6.x deployment configuration. See
“Understanding deployment configuration migration” on page 183.
• Understand how your choice of migration method impacts your migration
workflow. In addition, assess your source environment to streamline
migration, by calculating the platform and version changes you will need
to implement and pinpointing obsolete or unused universes and
documents to be excluded from migration, and whether some documents
would be more appropriate converted into or re-written in another format
available in the destination environment.
See “Planning the migration” on page 221.

Importing to the destination environment

• Before you use the Import Wizard to import your BI solution to
BusinessObjects XI R2, you must perform certain tasks such as:
• backing up source content, whether it be stored in the repository, on
cluster servers, or locally
• setting up the database to be used as a repository in the new
environment
• if it isn’t done already, installing version XI R2 on both client and
server machines
• starting the required services to get the new system up and running
• if you aren’t importing for the first time, backing up the destination
CMS after each incremental import
See “Before using the Import Wizard” on page 251.
• Full instructions for using the Import Wizard to import your BI content
from version 6.x to XI R2 are included in “Using the Import Wizard” on
page 261.

BusinessObjects 6.x to XI Release 2 Migration Guide 33

2 Migration essentials
Migration phases

Post-import checking and tuning

This phase includes analyzing the Import Wizard log file to verify the import,
then manually checking and if necessary, tweaking, the objects imported into
the new environment.
This is also when you can transfer or recreate functions or tasks not covered
by the Import Wizard, such as reconstructing document schedules, replicating
customization, and recreating the precise international environment you
require.
See “Checking and adapting the new environment” on page 289 and
“Checking for calculation updates” on page 301.

34 BusinessObjects 6.x to XI Release 2 Migration Guide

How XI R2 compares with
version 6.x

chapter
3 How XI R2 compares with version 6.x
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now

D 1. Understanding what migration entails

• Product offering (6.x vs XI R2)

• Architecture (6.x vs XI R2)
• Basic terminology (6.x vs XI R2)
• Installation, configuration, and deployment (6.x vs XI R2)
• Security model (6.x vs XI R2)
• Authentication/authorization (6.x vs XI R2)
• Architecture (6.x vs XI R2)
• Reporting, analysis, information sharing (6.x vs XI R2)
• Administration (6.x vs XI R2)
• SDK (6.x vs XI R2)
2. Assessment and planning
3. Preparing for import
4. Importing from the source to destination environment
5. Post-import checking and tuning

36 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Product offering 3
Product offering
Here is a list of the applications in each version’s offering. Although the
applications in each row belong to the same area of functionality, those in the
BusinessObjects 6.x column and those in the BusinessObjects XI R2 column
are not necessarily equivalent:

In BusinessObjects 6.x In BusinessObjects XI R2

• Designer • Designer
• Business View Manager
• Supervisor • Central Management Console
• Supervisor over the Web
• Administration Console • Central Configuration Manager
(CCM)
• Central Management Console
(CMC)
• Auditor Auditing is incorporated in the
Central Management Console. It is
not strictly equivalent to version 6.x
Auditor.
• InfoView • InfoView
• BusinessObjects • Desktop Intelligence
• BusinessQuery • Live Office
• Web Intelligence • Web Intelligence
• Web Intelligence for OLAP Data • OLAP Intelligence
Sources
• OLAP Intelligence Designer
• Broadcast Agent You publish from InfoView and
administer publishing in the CMC.
• Developer Suite • Developer Suite
• Set Analyzer • Part of Performance
Management Applications
(formerly Application Foundation)

BusinessObjects 6.x to XI Release 2 Migration Guide 37

3 How XI R2 compares with version 6.x
Architecture

In version 6.x, the Application Foundation and Data Integrator applications

complemented the Business Intelligence suite. With version XI R2,
Application Foundation has been renamed Performance Management and is
part of the suite. Data Integrator is also part of the XI R2 offer but is installed
separately.

Architecture
The overall architecture of the two server systems is organized in a similar
manner.

BusinessObjects 6.x
BusinessObjects 6.x is organized into five logical layers:
• The client tier contains products or features that run on the end-user’s
computer (either as a standalone application or in the web browser).
• The presentation layer contains the third-party web and application
servers, as well as the Business Objects components hosted on them
(server SDKs, portal pages, servlets, WIDispatcher, and HSAL).
• The application services layer provides the essential framework and
services to the processing layer, such as WISessionManager,
WILoginServer, and WIStorageManager.
• The processing layer contains report engines, as well as the additional
components that implement business logic (portal workflows, repository
access, scheduling, etc.).
• The database tier is made up of the databases containing the data used
in documents and reports.

38 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Architecture 3

BusinessObjects XI R2
BusinessObjects Enterprise XI R2 is organized into five tiers:
• The client tier contains client applications.
• The application tier includes the web and application servers, as well as
the Business Objects components hosted on them.
• The intelligence tier manages the XI R2 system, maintaining security
information, routing requests to the appropriate processing layer
services, managing audit information, and storing report instances for
rapid report viewing.
• The processing tier accesses the data and generates reports. This layer
contains fewer “servers,” or processes, than the BusinessObjects 6.x
processing layer. Transactional workflows are therefore simplified, with
each server processing requests for a specific type of object. In a
BusinessObjects 6.x context, this corresponds to a dedicated role such
as WIReportServer, which processes Web Intelligence 6.x reports only,
rather than a provider of shared services such as WIQT, which plays a
shared role in several types of processing workflows.

BusinessObjects 6.x to XI Release 2 Migration Guide 39

3 How XI R2 compares with version 6.x
Basic terminology

• The data tier is made up of the databases containing the data used in reports.

Basic terminology
The following table shows some of the main differences in terminology
between the two releases.

40 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Basic terminology 3
In BusinessObjects 6.x In BusinessObjects XI R2
Repository
The BusinessObjects 6.x suite uses a The repository exists here as well, as one of the
repository — a database that is stored in a databases maintained by the Central
relational database management system. Management Server (CMS). The CMS is the
The repository is used to secure access to central service/process in the XI R2 system (see
your data warehouse and to provide an its entry further along in this table).
infrastructure for distributing information to
be shared by users.
The repository database actually contains Although the repository database stores specific
the data associated with the security, information about the objects published to it,
universe and document domains. Making including users, servers, security, groups, folders,
sure the repository database has enough categories and parameters, it does not actually
space is therefore critical. store physical copies of the objects; it also
contains pointers to the physical objects, such as
Desktop Intelligence .rep files, Web Intelligence
.wid files, Crystal Reports .rpt files, universe files
and third-party documents, stored in a file system
associated with the File Repository Servers
(FRS).
Repository domains
The repository must have a security When universe and document domains are
domain. It can also contain universe and imported from a version 6.x deployment, they are
document domains. made into folders in the CMS database. Although
the security domain itself is not imported, you can
import its contents (user rights, etc.).
Modules Servers
Processes used in Business Objects Processes in the XI R2 system are called servers.
transactions which can be configured They run as services under Windows, and as
through the Administration Console are processes under UNIX.
called modules. The CMC’s ability to enable/disable and even
group servers, for example, concerns processes,
not actual Business Objects servers, or server
machines.
A few examples of modules are: The main server in BusinessObjects Enterprise
• Broadcast Agent Manager (which XI R2 is the CMS. Some examples of other
manages Schedulers) servers are:
• WIStorageManager • Job Server
• WIReportServer • File Repository Servers
• Desktop Intelligence Report Server
• Web Intelligence Report Server

BusinessObjects 6.x to XI Release 2 Migration Guide 41

3 How XI R2 compares with version 6.x
Basic terminology

In BusinessObjects 6.x In BusinessObjects XI R2

Business Objects servers Central Management Server (CMS)
At a minimum, the Business Objects The CMS is a single service which provides
server back-end must be installed on the framework services, security management,
cluster’s primary node and all secondary administers scheduling tasks, and also is
nodes. This installs all the processing responsible for maintaining the database (CMS
layer modules on the server machines. database) containing system information, such as
users/groups, security levels, and services. In
addition it maintains the repository and audit
databases.
The CMS is the main process in the
BusinessObjects Enterprise intelligence layer.
Disabling the CMS is roughly equivalent to
disabling the Session Stack (starting with version
6.1, the set of core processing modules enabled
or disabled as a group).
Clusters CMS clusters
A cluster is one or more Business Objects A Central Management Server cluster (CMS
servers which provide the functional cluster) consists of two or more CMSs working
processing for a given BI portal. Each together to maintain the system databases and
server hosts the entire set of Business repository. The CMSs can be on the same
Objects modules, not all of which must machine or on different ones.
necessarily be activated. For versions 6.1 This means that at a minimum only the CMS
and later, the Session Stack must be component must be installed and activated on
activated in order for the server to the machine. Other processes (servers) can be
contribute to cluster processing. installed and run on other machines.
When a cluster contains more than one A CMS cluster is called an expanded deployment.
server machine, it is called a distributed
deployment.

42 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Basic terminology 3
In BusinessObjects 6.x In BusinessObjects XI R2
Clusters can contain the following The distinction between primary and secondary
elements: nodes does not apply.
• The primary node serves as the When you add a new CMS to a deployment
central coordinator among all the containing a previously-installed CMS, you
nodes in the cluster. There is one and instruct the new CMS to connect to the existing
only one primary node in a cluster; if CMS database and to share the processing
the cluster contains only one node, it workload with any existing CMS machines. By
is a primary node. default, the new cluster is given the name of the
first installed CMS, prefaced by “@”.
• Optional secondary nodes run the
ORB components required to
communicate with the primary node
and start Business Objects processes
on the secondary node(s), as well as
optional services.
Both primary and secondary nodes are
considered cluster nodes.
BusinessObjects Desktop Intelligence
WebIntelligence Web Intelligence
Application servers Web application servers
Broadcast Agent Scheduling functions are handled by the CMS,
which instructs the Job Server to process the job
on a schedule managed by the CMS.
WIReportServer Web Intelligence Report Server
Corporate document domains Public folder
Personal document domains Favorites folder
File Watcher allows the processing of a The Event Server manages file-based events.
scheduled task only when a specified file Schedule-based and custom events, on the other
is present in a specified location. hand, are managed by the CMS.

BusinessObjects 6.x to XI Release 2 Migration Guide 43

3 How XI R2 compares with version 6.x
Basic terminology

In BusinessObjects 6.x In BusinessObjects XI R2

Profiles
Supervisor provides several standard Defined in the CMC, profiles let you personalize
profiles, or roles, for the users of Business the scheduled publication of reports for groups of
Objects products. The user profile recipients. Users with defined profiles applied to
determines by default what products a the publication will have the publication
user can use: personalized for them.
• General Supervisor (all products) In the source environment, this is called report
bursting.
• Supervisor (all products)
• Designer (all products but Supervisor
and Supervisor over the Web)
• Supervisor-Designer (all products)
• User (all products but Designer,
Supervisor, and Supervisor over the
Web)
• Versatile (configurable)
Universe overloads Universe access restrictions

44 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Installation, configuration, and deployment 3
Installation, configuration, and deployment
The following table provides an overview of key differences in installation,
configuration, and deployment.

In BusinessObjects 6.x In BusinessObjects XI R2

Server operating systems
Version 6.x supports heterogeneous The CMS “servers” in an XI R2 cluster must all be
clusters, in which Business Objects running on machines running the same operating
servers are hosted on Windows and UNIX system and version. The other “servers” in the
machines. intelligence layer, however, such as the Job
Server, can be hosted on machines running
completely different (but supported) operating
systems.
Initial installation options
• Desktop • Client
• Server • Server
• Custom The Server option provides three installation
options:
• New
• Expand
• Custom
Distributed deployments
To distribute processing, you add You can distribute a single deployment’s
additional cluster nodes to a cluster. To transactional capabilities on the same machine
add a cluster node, you must install by creating multiple instances of a “server”, or
Business Objects server on the node you can install on additional machines to
machine. distribute the load. This capability offers you the
This installs the entire set of processes ability to scale your system vertically (more
required for system processing on each services on the same machine) or horizontally
machine. At a minimum, the Session (more machines).
Stack must be activated on each cluster The CMS does not need to run on each machine.
node to share the transaction load.

BusinessObjects 6.x to XI Release 2 Migration Guide 45

3 How XI R2 compares with version 6.x
Installation, configuration, and deployment

In BusinessObjects 6.x In BusinessObjects XI R2

Installation and the repository
Repository creation is completely Setting up the CMS database, which includes the
independent of the installation of repository, is an integral part of BusinessObjects
Business Objects software. Enterprise installation.
In a New server installation, if you do not choose
to connect the CMS to an existing database, the
installation procedure automatically installs and
configures MySQL.
After installation, you can select or create a new
CMS database at any time using the Central
Configuration Manager (CCM).
Command-line installation Silent installation
Application servers
Application servers communicate with the You must install a Web Component Adapter
Business Objects cluster through the (WCA) on any machine hosting an application
ORB. server. The WCA allows your application server
If the application server is hosted on a to run applications making Crystal Web
machine which is neither a primary nor Requests, and to host the CMC. Not all
secondary node, you must configure the applications require the WCA. For example,
ORB on it in order to allow it to InfoView doesn’t need it unless users will be
communicate with the cluster. viewing OLAP Intelligence documents.
You configure the ORB on the application Installing XI R2 on the same machine as the
server machine either by installing the application server is called a server-side
Configuration Tool on that machine, then installation.
using it to configure the server as a client When you perform this installation, the client and
node of the cluster, or by configuring the server components are installed, the default user
ORB manually. and group accounts are created, and the sample
reports are published to the system. When the
installation is complete, the servers are started as
services on the local machine.

For information on deploying web For information on deploying web applications on

applications on application servers, see application servers, see “Deploying web
“Deploying web applications” on page 48 applications” on page 48 in this table.
in this table.
Web servers
To configure the web server to work with a If you connect BusinessObjects Enterprise to a
cluster, you must install a third-party web server, the Web Component Adapter (WCA)
connector to the cluster’s application must be installed on the same machine.
server.

46 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Installation, configuration, and deployment 3
In BusinessObjects 6.x In BusinessObjects XI R2
For information on deploying web For information on deploying web applications on
applications on web servers, see web servers, see “Deploying web applications” on
“Deploying web applications” on page 48 page 48 in this table.
in this table.
Licenses
Before installation, you copy your license License key strings, different from version 5.x
file(s) to a directory to which all nodes or license strings, are stored in the CMS database.
application client machines have access. You can view your deployment’s current license
During installation, you specify where keys, as well as add or delete them, using the
these XML files are located. CMC.
OLAP
You install Web Intelligence for OLAP OLAP Intelligence is installed from the standard
Data Sources using the standard installation CD.
installation process.
Configuring clusters and the ORB
You create clusters and configure their When you install the first Central Management
ORB on their nodes using the Server (typically a New install), you don’t have to
Configuration Tool. define a cluster. In subsequent installs, you are
You configure the cluster’s primary node asked if the CMS is part of the cluster, and at that
and then its secondary nodes. time, the cluster is created.

Available web applications

• Administration Console • Central Management Console
• InfoView • InfoView
• Auditor • Performance Manager applications (formerly
• Supervisor over the Web Application Foundation), J2EE only

• Custom web applications developed

• Custom web applications developed using the
SDK
using the SDK
Although not part of the BusinessObjects
6.x suite, Application Foundation
applications can also be deployed.

BusinessObjects 6.x to XI Release 2 Migration Guide 47

3 How XI R2 compares with version 6.x
Installation, configuration, and deployment

In BusinessObjects 6.x In BusinessObjects XI R2

Deploying web applications
You can deploy web applications in three If you choose a New installation and are using IIS
ways: or Apache/Tomcat, the Business Objects web
• If you’re using IIS or Tomcat/Apache, applications are deployed automatically on the
application server, unless you are deploying to an
the Configuration Tool can deploy the
existing Java application server.
applications automatically on web and
application servers. Otherwise, you must deploy web applications
manually. For information, see the
• You can use the wdeploy tool, a BusinessObjects XI Release 2 Installation Guide.
command-line utility that you can run
on all other supported application and/
or web servers.
• You can manually deploy the
application on all other supported web
and/or application servers.
You can choose to deploy web In XI R2 you deploy all the web applications’
applications in two modes: resources on the web application server.
• Distributed mode means deploying
the applications’ static resources on
the web server, and dynamic
resources on the application server.
• Standalone mode means deploying all
the applications’ resources on the
application server.
Repository creation
You create the repository after installation If you do not have a supported database client on
and configuration, using the Supervisor the machine, installation can install and configure
application. mySQL for use as the CMS database. To use
After repository creation, you must copy your own database server, you must create a
the bomain.key file corresponding to the new, empty database on your database server
repository on each node in the cluster. prior to running the installation. This database will
be configured during the install.
Whenever you add a new CMS to a cluster in an
Expand installation, you define the connection to
the initial CMS’s database. This allows the server
to connect to it.

48 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Security model 3
In BusinessObjects 6.x In BusinessObjects XI R2
Multiple service instances
In BusinessObjects 6.x, certain modules Multiple instances of the same service can run on
such as WIQT, BusinessObjects.exe the same machine (providing vertical scaling), or
(Windows)/bolight (UNIX), Connection on separate machines (for horizontal scaling), in
Server, and WIReportServer, are any mixture of supported operating systems. The
designed to be multi-instance on cluster single exception is the Central Management
nodes. You use the Administration Server, which must run on the same operating
Console to set the number of instances in system within a single cluster.
each process pool.
BusinessObjects 6.5 also supports
multiple Business Objects servers on the
same UNIX box.
Unicode databases
The use of Unicode databases, which can All CMS databases must support the Unicode
store information in different languages protocol.
and centralize all the information in a Desktop Intelligence can use Unicode data
company, is supported as a data source sources.
for Web Intelligence reports.
Unicode databases are not supported for
repositories or BusinessObjects
documents.

Security model
BusinessObjects 6.x applications use a very different security model than that
provided with BusinessObjects Enterprise XI R2, and as such, administrators
of BusinessObjects 6.x systems are encouraged to read “Understanding
rights migration” on page 117 with attention.

Authentication/authorization
Through BusinessObjects 6.5.1, authentication is defined for an entire cluster
and/or all desktop users. Implementing an authentication method is broken
down into selecting an authentication mode, then its source, which can be
Repository, External then Repository, or External. You can choose between
Microsoft AD or an LDAP user management system for external
authentication sources.

BusinessObjects 6.x to XI Release 2 Migration Guide 49

3 How XI R2 compares with version 6.x
Authentication/authorization

In version XI R2, security is much more granular. You implement an

authentication method for each user, when you create the user’s account.
When users log into the system, they specify their username and password,
but may enter their authentication method as well.

In BusinessObjects 6.x In BusinessObjects XI R2

bomain.key
The bomain.key file tells Business Objects There is no bomain.key file. At login, the Central
applications where to find the repository’s management Server (CMS) verifies the user
security domain. name and password against the security
information stored in the CMS database. Each
CMS is configured either at installation or
subsequently using the Central Management
Console (CMC) to connect to a specific database.
Setting the authentication and
authorization methods
You set authentication/authorization for You select the authentication method for each
the entire cluster, using the Administration user at the creation of the user’s account, using
Console. the CMC.
You set authentication for 2-tier You can assign multiple aliases, or authentication
deployments of BusinessObjects in modes, to a single user, or create new aliases
Supervisor. then assign them to exiting users in the system.
If you import external users via LDAP, Windows
NT or Active Directory, users are automatically
created. So if you are not using complex
scenarios in which users can log on with both NT
and LDAP authentications, you don’t need to
create the settings for each user individually.
Configuring authentication and
authorization
You set authentication/authorization for You configure authentication in the Authentication
the entire cluster. management area of the CMC.

50 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Authentication/authorization 3
In BusinessObjects 6.x In BusinessObjects XI R2
Available authentication modes
These options differ according to the • Enterprise authentication (automatically
version of your source software. enabled when you install the system, and
• Business Objects, or Business similar to Business Objects standard in
Objects standard version 6.x)
• Windows NT, Windows authentication, • Windows NT authentication
or Windows-NTLM • LDAP authentication
• Single Sign-On • Windows AD authentication
• Basic authentication (user Other authentication modes are available through
authentication is delegated to the web add-in products, such as SAP authentication.
server) Single Sign-On is not a mode in itself, but is
• No authentication available for certain authentication modes. See
below.
Single Sign-On (SSO)
To enable SSO in version 6.x, you must Single Sign-On to BusinessObjects Enterprise XI
use Netegrity SiteMinder. R2 can be provided through the use of third-party
systems such as Windows AD or Netegrity
SiteMinder.
End-to-end single sign-on includes SSO to the
database at the back-end.
Note: If you use SiteMinder, you must use LDAP
for external user management.
Authorization
You can use security commands in Because of the use of Access Control Lists (ACL),
Supervisor to restrict user and group an industry standard method of controlling
access to functionalities in Business cascading security access, the imposition of
Objects products. restrictions is much more granular. You can apply
You cannot restrict access at the object user, group, and role level security at the object
level. For example, if you grant a group level, to documents, categories, folders,
the right to refresh, but not create universes, and connections.
documents, the restriction will apply This means, for example, that you could allow a
regardless of the documents being used. group to refresh document A, but not refresh
document B.

BusinessObjects 6.x to XI Release 2 Migration Guide 51

3 How XI R2 compares with version 6.x
Administration

Administration
The administrative model applied to BusinessObjects Enterprise XI R2 is very
different from the BusinessObjects 6.x model.
• The Central Management Console (CMC)
The CMC allows you to perform user management tasks such as setting
up authentication and adding users and groups. It also allows you to
publish, organize, and set security levels for all of your BusinessObjects
Enterprise Enterprise content. Additionally, the CMC enables you to
manage servers and create server groups, whenever the Central
Management Server (CMS) is running.
• The Central Configuration Manager (CCM)
The CCM is a server-management tool that allows you to view and
configure each of your BusinessObjects Enterprise server components
while Business Objects servers are offline. This tool allows you to start,
stop, enable, and disable Business Objects servers, as well as view and
configure advanced server settings. On Windows, these settings include
default port numbers, CMS database and clustering details, SOCKS
server connections, and more. In addition, on Windows the CCM allows
you to add servers to, or remove servers from your BusinessObjects
Enterprise system.
The CCM comes in two forms. In a Windows environment, the CCM
allows you to manage local and remote servers through its Graphical
User Interface (GUI) or from a command line. In a UNIX environment, the
CCM shell script (ccm.sh) allows you to manage servers from a command
line.
At first, the CCM takes into account only the servers running locally. You
can then connect to servers on a remote machine.
This section covers administrative tasks concerning the repository, users and
groups, universes, server and cluster management, and auditing. For more
information, see the BusinessObjects Enterprise XI Release 2 Administrator’s
Guide.

52 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Administration 3
In BusinessObjects 6.x In BusinessObjects XI R2
Repository creation and
management
You create your cluster’s repository If you do not have a supported database client on the
after Business Objects installation machine, installation can install and configure mySQL
and configuration, using the for use as the CMS database. To use your own
Supervisor application. database server, you must create a new, empty
database on your database server prior to running the
installation. This database will be configured during the
install.
Whenever you add a new CMS to a cluster in an
Expand installation, you define the connection to the
initial CMS’s database. This allows the server to
connect to it.
User/group creation and
management
You use Supervisor or Supervisor You use the CMC.
over the Web.
An initial General Supervisor account By default, Administrator and Guest accounts are
is created when you create the created at installation.
repository.
A “company name” group is Two default groups are automatically created at
automatically created at repository installation:
creation. • Administrators contains users that have
administrative rights.
• Everyone contains all users created in the system.
If you’re using Windows NT/2000, an additional group
called Business Objects NT Users is also created.
Two additional groups are also created for user
administration:
• Designer Users, used to administrate Designers
• Report conversion tool Users
License key management
Before installation, you copy your License keys are stored in the CMS database. You can
license key to a directory to which all view your deployment’s current license keys, as well as
nodes or application client machines add or delete them, using the CMC.
have access. During installation, you
specify where these XML files are
located.

BusinessObjects 6.x to XI Release 2 Migration Guide 53

3 How XI R2 compares with version 6.x
Administration

In BusinessObjects 6.x In BusinessObjects XI R2

Using Designer
You can use Designer in online or You can use Designer in online or standalone mode,
offline mode. which is equivalent to offline mode in version 6.x.
Cluster start/stop
Under Windows, you can use You use the CCM to stop a Central Management
WINotify or the Start menu; during Server (CMS), regardless of the operating system. At
installation, you can also set the installation, you can also configure the server to start
Business Objects server to run automatically at machine startup.
automatically as a Windows service. Note: You cannot use the Central Management
Under UNIX, you start the cluster Console (CMC) to stop a CMS.
manually using the wstart command,
or use S99WebIntelligence to start it
automatically on machine startup.
Cluster server enable/disable
You use the Administration Console. In Windows, you use the Central Configuration
Manager (CCM) to disable a Central Management
Server (CMS).
In UNIX, you use the ccm.sh script.
Caution: You can use the CMC to disable/enable and
even group servers, but this refers to what
BusinessObjects 6.x users refer to as modules, not the
actual cluster nodes.
Server settings management
You use the Administration Console. You use the Central Management Console or the
Central Configuration Manager, depending on the type
of setting you want to define, and whether you are
online or offline.
Audit management
You use the Audit facility in the You use the CMC. You can also use the CMC to view
Administration Console. server metrics, including information about the
You can also use the Auditor machine that the server is running on—its name,
application for enhanced system operating system, total hard disk space, free hard disk
monitoring and analysis. space, total RAM, number of CPUs, and local time.
The CMC allows you to configure what information you
want each server/service to audit.

54 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Administration 3
In BusinessObjects 6.x In BusinessObjects XI R2
Setting up scheduling
You create and manage schedulers
using the Broadcast Agent Because the scheduler is incorporated into the CMS,
Manager’s Properties page in the scheduling comes automatically with BusinessObjects
Administration Console. Enterprise XI R2 and requires little or no additional
configuration beyond setting up access to email
servers, printers and file servers.
Viewing scheduled tasks
You can view the full list of scheduled You cannot view a global list of scheduled jobs.
documents and their status using the You can view the status of one scheduled object at a
Broadcast Agent Console. time in the CMC in the object’s History page. This list
includes all scheduled jobs for the object, as well as
existing instances of the object (i.e. reports that have
already been run and contain data).
In InfoView, you can also view a list of an object’s
instances by looking at the object’s history.
A sample application built using the Administration
SDK and available from the BusinessObjects
Enterprise User’s Launchpad also allows you to see all
the jobs scheduled by any specific user.
InfoView appearance and
functionality management
You can use Supervisor security You can modify the appearance and some functionality
commands to prevent users from using the BusinessObjects Enterprise Applications
modifying the default settings in the management area in the CMC.
InfoView Options page.
Setting locale
You set the cluster’s language at You don’t specifically set the CMS locale. Users set the
installation; you can subsequently locale for their own interface in InfoView; if they don’t,
use the Site Properties tab in the InfoView uses the locale specified on the web server.
Administration Console to modify it.
Users can set the language of their
interface in InfoView.

BusinessObjects 6.x to XI Release 2 Migration Guide 55

3 How XI R2 compares with version 6.x
Reporting, analysis, information sharing

Reporting, analysis, information sharing

This section includes information on available reporting tools, as well as end-
user tasks such as accessing, distributing and scheduling corporate data.

In BusinessObjects 6.x In BusinessObjects XI R2

Reporting tools
• BusinessObjects • Crystal Reports
• Web Intelligence • Desktop Intelligence
• Web Intelligence for OLAP Data • OLAP Intelligence
Sources • Web Intelligence
What reporting tools use
universes? • Crystal Reports
• BusinessObjects • Desktop Intelligence
• Web Intelligence • Web Intelligence
Crystal Reports can also connect directly to
databases using a variety of methods including
ODBC and native drivers, as well as XML and text
files. It can also use Business Views (the semantic
layer from Crystal Enterprise) as a data source.
InfoView
InfoView is a web application that The out-of-the-box portal in BusinessObjects
must be deployed after Business Enterprise XI R2 is also called InfoView. Available for
Objects installation using the both Java and .NET platforms, its interface is
Configuration Tool, wdeploy, or somewhat different from the BusinessObjects 6.x
manual procedures. application.
It is available in JSP and ASP
platforms.

56 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Reporting, analysis, information sharing 3
In BusinessObjects 6.x In BusinessObjects XI R2
Categories
Within InfoView, you can use BusinessObjects Enterprise XI R2 uses both
categories to organize documents on categories and folders to organize documents.
a particular document list page. Folders are used for the storage location of
information, while categories are used more for the
classifying information regardless of its storage
location.
• BusinessObjects Enterprise XI R2 automatically
creates a folder for each user in the system,
called Personal Folders. These folders are
organized within the CMC as User folders. Within
InfoView, these folders are called Favorites
folders. Folders are created and managed from
the CMC.
• Categories are equivalent to BusinessObjects 6.x
categories.
Folders contain actual copies of objects, while
categories simply point to objects.
There are two kinds of categories: There are two types of categories:
• Corporate • Corporate
• Personal • Personal
Corporate categories can be created Corporate categories can be created either in
from InfoView, BusinessObjects, or InfoView (with reduced management capabilities) or
Supervisor. from the CMC (full management capabilities).
As a general supervisor or supervisor,
you can grant specific users or groups
the right to create categories, and to
rename and delete the categories they
create, from BusinessObjects or Web
Intelligence. You do this by enabling
the security command Manage All
Categories or Manage My Categories.
You can use security commands to In the CMC you can restrict users’ and/or groups’
restrict access to corporate access to categories and folders. You can set limits
categories. on folders, which automate regular clean-ups of old
Business Objects content by eliminating excess
instances of particular objects, or object instances
which have remained more than the specified number
of days in the folder.

BusinessObjects 6.x to XI Release 2 Migration Guide 57

3 How XI R2 compares with version 6.x
Reporting, analysis, information sharing

In BusinessObjects 6.x In BusinessObjects XI R2

Scheduling
You schedule for refresh documents You schedule for refresh objects using the Publishing
and files either from 2-tier Wizard, from the CMC or from InfoView.
deployments of BusinessObjects, or
from InfoView.
You can schedule: You can schedule:
• BusinessObjects documents • Crystal reports
• Web Intelligence documents • OLAP Intelligence reports
• Web Intelligence OLAP reports • Web Intelligence documents
• Desktop Intelligence documents
You can also schedule program objects, such as
executables, Java programs, or scripts (Jscripts and
VBscripts) to run at specified times. Note that
customized code is not supported by Business
Objects Support.

58 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
Reporting, analysis, information sharing 3
In BusinessObjects 6.x In BusinessObjects XI R2
Publishing to the repository
You add objects to the repository by: You can publish objects to BusinessObjects
• Exporting universes from Designer Enterprise in several ways.
or Supervisor Use the Publishing Wizard when you:
• Adding users and groups and • Have access to the locally installed application.
managing security settings from • Are adding multiple objects or an entire directory.
Supervisor and/or Supervisor over
the Web The Publishing Wizard is a locally installed
Windows application that enables both
• Saving documents to the administrators and end users to add any
repository from InfoView
supported document to BusinessObjects
• Publishing documents from 2- and Enterprise. The Publishing Wizard does not take
3-tier deployments of into account legacy Business Objects objects,
BusinessObjects such as Desktop Intelligence documents, Web
Intelligence documents, and universes.
Use the CMC when you are:
• Publishing a single object.
• Taking care of other administrative tasks.
• Performing tasks remotely.
Save directly to your Enterprise folders when you are:
• Designing reports with Crystal Reports or Web
Intelligence.
• Using the OLAP Intelligence Application
Designer.
• Creating other objects with BusinessObjects
Enterprise plug-in components.
Upload documents stored on your local computer
when you’re using InfoView.
Use Designer to export universes to the repository.
Use the Import Wizard to migrate objects to an XI R2
repository from BusinessObjects 5/6.

BusinessObjects 6.x to XI Release 2 Migration Guide 59

3 How XI R2 compares with version 6.x
SDK

SDK
In BusinessObjects 6.x

SDK or module... Used to customize/ Using this language/

extend... platform...
BusinessObjects BusinessObjects, Visual Basic for
SDK (macros and Designer, the Report Applications
add-ins) Viewer component
Web Intelligence Web Intelligence, ASP, JSP
SDK (scripts) InfoView
Administrator SDK Users and groups in a JSP
strictly controlled
environment
Web Services Set of web service .NET, Java (REBean)
applications based on the
.NET and J2EE
frameworks and on
InfoView

60 BusinessObjects 6.x to XI Release 2 Migration Guide

 How XI R2 compares with version 6.x
SDK 3
In BusinessObjects Enterprise XI R2

SDK or module Description Using this language/

platform
BusinessObjects Includes libraries for Microsoft Visual
Enterprise SDK building a web report Studio .NET, Java,
delivery tool. Lets users COM
log on to the
BusinessObjects
Enterprise system, create
objects (folders and
reports), and to view,
schedule and export
reports
.NET Server Controls for Set of libraries that allow Microsoft Visual
BusinessObjects you to use visual and non- Studio .NET
Enterprise visual components to
design and implement
BusinessObjects
Enterprise web
applications that use the
.NET framework.
Report Application Includes libraries for Microsoft Visual
Server SDK building a web report Studio .NET, Java,
design tool. Lets users COM
create new reports or
modify existing ones by
adding, removing, and
modifying objects, such
as tables, charts, and
fields.
Viewers SDK Includes libraries for Java, COM
building customized thin-
client report viewers that
display web-based
reports. Also provides an
interface to
programmatically export
Crystal Reports to a
variety of other formats.

BusinessObjects 6.x to XI Release 2 Migration Guide 61

3 How XI R2 compares with version 6.x
SDK

SDK or module Description Using this language/

platform
Crystal Reports SDK For customizing and Microsoft Visual
extending Crystal Studio .NET
Reports. Includes .NET
libraries for building
customized report viewers
that display web and
Windows form-based
reports.
Desktop Intelligence For customizing and Visual Basic for
SDK extending Desktop Applications
Intelligence; almost
identical to version 6.x
BusinessObjects SDK
Designer SDK For customizing and Visual Basic for
extending Designer; Applications
almost identical to version
6.x Designer SDK
Web Intelligence SDK For customizing and REBean, RE .NET
extending Web
Intelligence
Unified Web Services Set of services that allow Microsoft Visual
Consumer SDK you to create Business Studio .NET, Java
Objects Web Service
consumer applications
that manage sessions,
create custom queries,
manage documents, and
perform listing and
publishing actions.

62 BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding what
migration entails
64 BusinessObjects 6.x to XI Release 2 Migration Guide
BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding user and

group migration

chapter
4 Understanding user and group migration
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now

D 1. Understanding what migration entails

• Users, groups, and their organization

• User/group access rights
• How users and groups migrate
• Consequences of importing users and groups
• Migrating external groups (LDAP)
2. Assessment and planning

3. Preparing for import

4. Importing from the source to destination environment
5. Post-import checking and tuning

For more detailed information on user rights, see “Understanding rights

migration” on page 117.

Users, groups, and their organization

Note: Throughout this chapter and the rest of the guide, the term principals is
used to generically describe users and groups.
Both 6.x and XI R2 use a user and group model. The framework in which they
reside, however, is different.

66 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
Users, groups, and their organization 4
In version 6.x
Created and managed via the Supervisor and/or Supervisor over the Web
application, users and groups are organized in a tree structure with one root.
A user can be a member of more than one group, and these separate
memberships are considered different instances of the user.

By default, a single, root group is created, with the “company name” specified
during the Supervisor installation.
Supervisor offers several standard profiles for the various types of users of
Business Objects products. The user profile determines by default what
products a user can use:
• General Supervisor (all products)
The General Supervisor is at the root level. Assigned all rights, this user
can administer all groups, as well as their users and sub-groups.
• Supervisor (all products)
• Designer (all products but Supervisor and Supervisor over the Web)
• Supervisor-Designer (all products)
• User (all products but Designer, Supervisor, and Supervisor over the
Web)
• Versatile (configurable)
Administrators with the proper rights can customize these profiles.
A user can have a different profile in each group.

BusinessObjects 6.x to XI Release 2 Migration Guide 67

4 Understanding user and group migration
Users, groups, and their organization

In version XI R2
In XI R2, users and groups are created and managed using the CMC.
Group structure is a directed acyclic graph (DAG); that is, each group can
have more than one parent. The DAG does not need to be connected; that is,
there may be groups without any relation to other groups.

A user can belong to more than one group, but only one user is actually
created in the CMS. Instances of a user do not exist.
By default, four groups are created at CMS installation:
• Everyone, which contains all users
• Administrators
• Universe Designers Users
• Report conversion tool Users
All imported 6.x users become part of the Everyone group.
The following users exist by default:
• Administrator
• Guest
Profiles in the version 6.x sense do not exist in XI R2.

Special migration cases to be aware of

• User parameter migration
• Username case-sensitivity
• Password restrictions

68 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
User/group access rights 4
User parameter migration
Some user parameters are migrated (Name, Password, Enabled/Disabled).
Some are not (timestamps, predefined settings).

Username case-sensitivity
Version XI R2 is not case-sensitive to usernames, whereas depending on the
repository database, version 6.x can be. This means, for example, that if a
version 6.x repository contains a user called jsmith and another called
JSmith, and you try to import both users, one of the users may not be
migrated.

Password restrictions
In the XI R2 environment, you can use the following CMC options to restrict
password format:
• Enforce mixed-case passwords
This option ensures that passwords contain at least two of the following
character classes: upper-case letters, lower-case letters, numbers, or
punctuation.
• Must contain at least N characters
By enforcing a minimum complexity for passwords, you decrease a
malicious user’s chances of simply guessing a valid user’s password.
In addition, passwords must be at least six characters long.
The first time you import a user from a version 6.x repository, passwords of
any type are accepted. Once users are entered into the CMS, however, their
passwords become subject to the password policy defined in the CMC.
Before updating a user with subsequent incremental imports, then, make sure
that the users in the source repository have all have passwords supported in
the destination CMS. If they don’t, they will not be re-imported.

User/group access rights

The security rules that existed in version 6.x (such as product access, objects
rights, and security commands) are enforced in XI R2 by the ACL (Access
Control List) mechanism, an industry standard method of controlling
cascading security access. An ACL is set on an object to define what rights
users and groups have on that object, and is composed of a list of ACEs
(Access Control Entities), which specify the state of a single right for a single
user/group.

BusinessObjects 6.x to XI Release 2 Migration Guide 69

4 Understanding user and group migration
User/group access rights

In version 6.x, you use security commands in Supervisor to restrict user and
group access to functionalities in Business Objects products.You cannot
restrict access at the object level. For example, if you grant a group the right
to refresh, but not create documents, the restriction will apply regardless of
the documents being used.
Because ACLs are used, the imposition of restrictions in XI R2 is much more
granular. You can apply user, group, and role-level security at the object level,
to documents, categories, folders, universes, and connections.
This means, for example, that you can allow a group to refresh document A,
but not refresh document B.

User/group inheritance
The main challenge during migration is the difference in inheritance rules
between version 6.x and XI R2.
• In 6.x, rights inheritance is propagated through groups only. When a right
is set on a group it applies to all subgroups, unless it is overridden for a
specific subgroup or user. For example, because Tom and Lea belong to
the Marketing group, they inherit all the rights established for the
Marketing group.
Rights set lower down in the group tree take priority -- rights on a user
take priority over those on the user’s parent, and so on.
• In XI R2, rights are inherited both through groups and through folders.
In this environment, for example, Michael and Lea would still inherit all
Marketing group rights. In addition, however, if the rights set for the Sales
Results folder allowed Michael to access that folder, if no subfolder or
document rights contradicted that right, Michael would automatically have
access to all the documents in that folder.

70 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
User/group access rights 4
Rights aggregation
Aggregation is different in the two environments.

In 6.x In XI R2
If the user has a right denied in one If a user has a Boolean right denied
group and granted in the other, the in one group and granted in the
user may or may not have the right other, then the user has the right
granted. denied.
Aggregation rules for conflicting If the user has a boolean right
rights are different for the different unspecified in one group and granted
types of rights. in the other, then the user has the
right granted.
The value Unspecified defaults to Unspecified Boolean rights are
either Granted or Denied depending always considered denied.
on the type of right.

Inherited rights are equal to explicit rights, and when rights conflict, Denied
always takes priority, regardless of the source of the conflicting rights.
Because of this model, and because Denied takes priority over Granted, you
cannot give child users or groups more rights than their parents without
breaking inheritance. You can change a right from unspecified (effectively
denied) to Granted, but not from Denied to Granted.
Tip: Denied is a very powerful value. During aggregation, it wins over any
other values. As a result, Business Objects recommends you prefer
unspecified: by default this means Denied, but it can be overridden by
Granted.

Overriding inheritance
Overriding inheritance therefore works very differently in the two
environments:
• In version 6.x, you can simply grant a user a particular right if that right is
denied to the group it belongs to. The rights placed on the user take
precedence over the parent group’s rights.
• Given the same situation in XI R2, you will have to turn off inheritance
altogether, and this will prevent the user from inheriting any rights from
parent groups of inheritance for all the rights for a user or group on an
object. You cannot turn off inheritance for some rights but not others.

BusinessObjects 6.x to XI Release 2 Migration Guide 71

4 Understanding user and group migration
How users and groups migrate

Troubleshooting overly restrictive rights in XI R2

If you don’t understand why migrated users have far more restricted rights
than you had anticipated, check the rights on the Everyone group.
As the rights applied to the Everyone group apply to all users of the system, if
a right is set to Denied for the Everyone group, the right is denied for all users,
even migrated ones, regardless of whether they had the right granted in the
source environment.

How users and groups migrate

Users
Users are migrated as users to the CMS, where they are stored as
InfoObjects. A user can belong to different groups. Every instance is migrated
as a user belonging to a corresponding group.

Groups
Groups are migrated as groups in the CMS. The Import Wizard migrates the
same hierarchy as in the 6.x repository. For example, if in 6.x a group called
MyCompany contains the groups Group1 and Group2, the same hierarchy is
created in the CMS database in XI R2.
After import, you can take advantage of the more sophisticated XI R2 security
framework to refine this hierarchy: for example, a group can belong to several
groups.

User profiles
In version 6.x, user profiles define the applications user can use in the
Business Objects system. In XI R2, user profiles no longer exist. Application
rights are set through ACLs and rights on the corresponding applications and
documents. During migration, user profiles are imported and reset as
appropriate rights on the application.
For more information on how rights are set during migration, see
“Understanding rights migration” on page 117.
Most version 6.x user profiles map to default groups in the new system. For
example, General Supervisors become members of the Administrators group.
Supervisors, on the other hand, are not mapped to the Administrators group,
but instead simply granted the appropriate rights on all imported objects.
Users with the User/Versatile profile are added to an object level security
group based on their object security levels.

72 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
How users and groups migrate 4
During migration, the following rules apply:
• General Supervisors are added to the Everyone and Administrators
groups.
• Users whose profiles allow them to run Supervisor (Supervisor/
Supervisor-Designer/Versatile with Supervisor access):
• have the View access level for the groups to which they belong in
version 6.x
• have the Full-Control access level for the users and subgroups of the
groups to which they belong in version 6.x
• Users whose profiles allow them to run Designer (General Supervisor/
Designer/Supervisor-Designer/Versatile with Designer access) are not by
default added to the Universe Designer Users group. This group has full
control over the Universes folder.
To allow imported universe designers to use the Designer application and
manage particular universes, therefore, you must grant them specific
rights through the CMC.
Note: in version 6.x, a user can have different profiles in different groups.
This is not possible in XI R2.

User security commands

Security commands in 6.x are applied at the application level. In XI R2, they
are replaced by ACL and application rights, even if in XI R2, ACLs and rights
also cover profiles, document access rights, and delegated administration.
In XI R2, rights can be set at application and object levels.
During migration, the Import Wizard imports security commands. The tables
in Chapter 7: Understanding rights migration describe the equivalence of Web
Intelligence, BusinessObjects and Designer security commands with rights in
XI R2.

BusinessObjects 6.x to XI Release 2 Migration Guide 73

4 Understanding user and group migration
Consequences of importing users and groups

Predefined settings that 6.x administrators can define in the repository to

apply a set of security command settings to multiple users do not exist in XI
R2. You can efficiently reproduce predefined settings, however, by creating
specific groups and then assigning specific rights to these groups. Users
added to these groups will inherit the rights set at the group level.

Security commands Specific migration information

Login Migrated, although the CMS does not differentiate upper-case
and lower-case
Password The first time the user is imported, passwords are imported as
they are. With subsequent imports of the users, however, (for an
update for example), password is checked against CMS
password policy.
Enabled/Disabled If the user is disabled in BOBJ, it is disabled in XI R2 after
import
Timestamp Not migrated
Identification strategy Not migrated
Enable real time user rights Not migrated
update
Enable Password Maps to the User cannot change password property, for which
Modification flag the reverse value is accorded.
Password Validity settings Administrators must reset this manually at the global level.
Object Security level Expressed as limit rights set on the universe folder; object levels
in BusinessObjects 6.x map to appropriately-named user
groups.

Consequences of importing users and groups

You import users and groups using the Import Wizard. Importing principals
allows you, if you want, to migrate the imported users’ application rights; if
you are concurrently importing other objects as well, you can also import the
objects’ rights.
Nonetheless, because of the differences in the 6.x and XI R2 security models
(ACL and rights instead of security commands, profiles, as well as a more
restrictive framework in general), it isn’t possible to have exactly the same
security in 6.x and XI R2.

74 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
Consequences of importing users and groups 4
The Import Wizard imports a snapshot of the 6.x security from the repository
to make security in XI R2 as similar as possible, but once migrated, any
change in rights in the CMS may lead to different results than in 6.x, due to
differences in aggregation and inheritance rules, in how rights are collapsed
at users level during import, and so forth.
If you have a large repository with a very detailed security scheme, you may
decide to take advantage of the new security framework by not importing your
source security, and recreating security directly in XI R2.
If you need some help, you can contact Professional Services who can give
you insight on best practices to recreate security in CMS after an import.
For information on whether to import rights, see “Importing security or not” on
page 225.

How Merge/Update options impact user/group import

In incremental migrations, users and groups may be treated slightly differently
than other objects.

Merge Update
The comparison between source and As with other objects, the Import
destination users/groups is Wizard updates everything if the
performed using objects’ CUIDs CUID is the same; if the CUID does
(cluster unique identifiers). not exist in the destination repository,
The user/group in the destination it creates a new user.
repository is unchanged, except that If the commit fails due to a duplicate
the Import Wizard merges the name, however, the user will not be
hierarchy, or ownership, for the user/ imported. The Import Wizard never
group. makes copies of users and groups.
For example:
Import 1:
Source: Group1 with userA
Destination: Group1 with userA
In the source repository, userA is
now moved into Group2.
Import 2:
Source: Group1 with userA
Destination: Group1 with userA,
Group2 with userA

BusinessObjects 6.x to XI Release 2 Migration Guide 75

4 Understanding user and group migration
Delegated Administration

Delegated Administration
In version 6.x, a supervisor can only modify the rights for the users located in
his/her group or subgroup. In particular, this applies to universe access
restrictions (also known as universe overloads) defined in Supervisor.
With XI R2, universe access restrictions are defined in Designer.

Modify Rights right (MRR) and Secured Modify

Rights right (SMRR)
In XI R2, the Modify Rights right (MRR) allows a user to modify any right for
any user on a particular object. MRR is very powerful and effectively
dominates all other rights, because once users are granted MRR on a
particular object, they can grant themselves or anyone else any rights they
want on the object. For example, if Alex has only View rights and MRR on an
object, she can give herself or any other user full control over the object by
granting all the missing rights.
Securely Modify Rights rights (SMRR) area more restrictive kind of MRR. For
example, a supervisor called Joe, who has SMRR on an object O, can only
grant or deny rights that Joe himself is already granted. So in the example
above, Joe has View rights and SMRR on the object O. Joe cannot give
himself any more rights; he can only give or take away from other users the
View (and SMRR) rights. Additionally, Joe can only change rights for users for
whom he has the SMRR right (this allows you to define the set of users to
which a delegated administrator has access).

How to establish delegated administration in XI R2

To establish delegated administration on a specific object:
• You must create an administrator, or modify an existing administrator,
with SMRR but not MRR on the objects in question.
• The administrator must have Apply Overload rights granted on the object
(that is, a restriction of SMRR).

76 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
Migrating external groups (LDAP) 4
• This administrator must be granted SMRR on all the users or groups for
which he/she is allowed to control rights, but no others.
Note that this means that if the administrator is actually in the
administrators group, he/she will by default inherit full rights to all users.
To prevent this, you must explicitly add him as a principal on the root level
user and group folders, and have inheritance turned off there. For this
reason, it is probably simpler and less error prone if you start with a user
who is not in the administrators group. After this is configured, it should
be possible to define the restrictions required for 6.x compatibility.
Note: When you migrate to XI R2, delegated administration is not completely
accounted for during import, and so some delegated administrators may have
fewer rights after import. The SMRR is added to the correct groups for
delegated administrators, but is not added on any objects, so only half of the
required rights are there.

Migrating external groups (LDAP)

The Import Wizard performs simple LDAP migration from version 6.x:
• It maps static LDAP groups. After migration, administrators need to
create dynamic groups using Enterprise authentication.
• It does not import:
• LDAP users’ Inbox and personal documents
• LDAP users’ ownership of corporate documents
• LDAP attribute variables used in reports

LDAP migration
Platform requirements
In version 6.x you can use Microsoft Active Directory and a Java application
server for LDAP configurations. The application server can also be on UNIX
or Windows. With XI R2, Active Directory is only supported with Microsoft IIS
web/application server.

User/group mapping
In version 6.x, the users you create in the repository depend on the type of
LDAP mapping you choose:
• If you choose user-to-user mapping, then you must create a user in the
repository for each LDAP user you want to allow to login.

BusinessObjects 6.x to XI Release 2 Migration Guide 77

4 Understanding user and group migration
Migrating external groups (LDAP)

• If you choose group-to-group mapping, you need only create a group for
each LDAP group of users that you want to allow to login.
In XI R2, you map in the group(s) from LDAP that you want to allow access to
the system. When you map in a group, a group is created in the repository
with an LDAP alias (the alias contains the DN of the LDAP group that was
mapped so it can be associated with the correct LDAP group).
When you map in any third-party group, you can do either of the following:
• Create users in the repository for each user in the LDAP group.
• Instead of explicitly creating the users, choose to create a user in the
repository for any LDAP user who successfully logs into the
BusinessObjects Enterprise system. These users are full users, who can
be associated with other, non-LDAP groups and have specific rights sets.
This option is useful if you want to map in a very large group, but you
know only a few of the users will ever bother to access Enterprise. Any
created users are added to the appropriate third-party group in
BusinessObjects Enterprise.
After your groups are mapped, you can assign rights to the groups or make
the group a member of other BusinessObjects Enterprise groups (you can
also do this for any users that have been created).
The Import wizard maps static LDAP groups. Dynamic groups are mapped
automatically if you use Enterprise authentication in the new environment.
If mapping cannot be established, groups are imported as non-LDAP
BusinessObjects Enterprise groups.

LDAP attribute variables

In version 6.5, if LDAP attributes were mapped to Business Objects variables
in the Security Configuration Tool, the attributes could be used in reports. The
@VARIABLE(<BOBJvariableName>) in the report would then retrieve the
LDAP attribute value.
These attributes do not migrate to version XI R2. In version XI R2, if they are
used in a report, they are displayed as @variable(<BOBJVariableName>); if
used as a filter, they fail to match anything.

78 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding user and group migration
Migrating external groups (LDAP) 4
What does migration involve?
Before import
1. Connect to your source cluster using an LDAP login.
2. Launch Supervisor to check that all LDAP users are not stored in the
repository and are indeed in the LDAP server.
3. In the source repository, delete any third-party aliases for all users/groups
that no longer exist in the LDAP system.
4. Make sure BusinessObjects Enterprise XI R2 is installed and launched,
including the Import Wizard.
5. Ensure that the connection information to the third-party system is still
valid, so that the Import Wizard can get aggregation information for user/
groups during the import.
6. Configure the LDAP plug-in from the CMC (Authentication > LDAP tab).
You just have to configure the connection parameters, you don’t have to
map any groups.
See the BusinessObjects Enterprise XI Release 2 Administrator’s Guide
for detailed instructions.

Importing
Use the Import Wizard to import your content, making sure you check the
LDAP Authentication option in the Import Groups Option page.
The Import Wizard adds an LDAP alias to every imported group that it can
find in the configured LDAP system, by matching the name of the group to the
name of a group in the LDAP system.
It also updates the LDAP plug-in after the users and groups have been
imported. This adds an LDAP alias to every user that belongs (in the LDAP
system) to one of the groups with an LDAP alias.
Note: If you choose to import user’s personal content, only users that
actually exist (i.e. have user objects) in the repository will have their personal
content imported to XI R2.

After import
1. After import, go through the users and groups in the XI R2 system to
make sure that the Import Wizard made correct assumptions about the
users and groups that were intended to be LDAP users and groups. You
should then delete/re-assign/add LDAP aliases as necessary.
You can optionally map additional LDAP groups at this point. You can, for
example, create dynamic groups if required.

BusinessObjects 6.x to XI Release 2 Migration Guide 79

4 Understanding user and group migration
Migrating external groups (LDAP)

80 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding object
migration

chapter
5 Understanding object migration
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now

D 1. Assessment and planning

• What kinds of objects can be imported?

• Universes and universe connections
• Stored procedures
• Folders, domains, and categories
• Documents
2. Preparing for import
3. Importing from the source to destination environment
4. Post-import checking and tuning

What kinds of objects can be imported?

The following types of objects can be imported from BusinessObjects 6.x
using the Import Wizard:
• Users and user groups
See “Understanding user and group migration” on page 65.
• Universes and connections
• Stored procedures
• Inbox, personal, and corporate documents
• Third-party (“agnostic”) documents (such as .pdf, .ppt, .doc, .xls, .txt, .rtf)
• Personal and corporate categories
• Broadcast Agent Scheduler tasks that are supported in XI R2
• Application Foundation 6.x objects
• Third-party documents used by Application Foundation objects (includes
.svg, .xml, .swf, .csv, .gif, .jpg, .bmp, and .png)

82 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
What kinds of objects can be imported? 5
Potential limitations
In the current version, the Import Wizard does not import:
• Administration Console settings
• Web Intelligence OLAP
• Custom applications and interfaces created using the SDK
• Broadcast Agent Scheduler tasks that are not supported in XI R2
• Broadcast Agent Publisher tasks
• BusinessObjects Auditor
• InfoView personal settings
• Some user settings, such as timestamps
• individual LDAP users (inbox and personal)
• BusinessQuery
These restrictions, and their solutions, are explained in greater detail in the
remainder of the chapter.

Flow of resources
The Import Wizard can import objects only if they are located in:
• the repository (users, groups in the security domain, documents in the
document domains, universes in the universe domains)
• personal and inbox folders

BusinessObjects 6.x to XI Release 2 Migration Guide 83

5 Understanding object migration
What kinds of objects can be imported?

The picture below shows the flow of resources from the source environment
(5.1 in this case) to the destination environment during import.

Files in the FRS are controlled by the platform, not the client. Objects
controlled by the system (InfoObjects) may contain both metadata
(properties, relationships, and so on) and files. The metadata is stored in the
CMS database, and the files are stored in the FRS.
During import, all objects in the source repository are copied to a temporary
folder on the machine running the Import Wizard. The default location of the
folder is defined by the $IMPORTWIZARDTMP system variable. If this variable
is not defined, then it is $TMP\ImportWiz_Temp, where TMP is a Windows
system variable.
If these variables are not defined, then it is $TEMP\ImportWiz_Temp, where
TEMP is a Windows system variable.
If all these variables are not defined, then it is the default temporary folder
created by Windows (normally C:\Document and Settings\%USERNAME%,
followed by \ImportWiz_Temp).
You can modify the $IMPORTWIZARDTMP system variable in the Windows
Control Panel (System > Advanced > Environment Variables > New System
Variable).

84 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
What kinds of objects can be imported? 5
After import, the Temp folder and its contents are deleted.

Corporate documents
Version 6.x corporate storage is mapped to the Public Folders folder in the XI
R2 CMS repository. Corporate documents are saved in this folder after the
import.
Each domain is migrated as a folder in the Public folder of the CMS
repository.
Note: If your 6.x repository was a distributed one, all the domains are
imported into a single place.

Inbox documents
In version 6.x, Inbox documents are stored in the repository until all recipients
have read them. When this occurs, the documents are removed from the
repository.
When a document has been read by a given user, it is copied to the user’s
Inbox folder ($STORAGEDIR\mail\<username>).
The Import Wizard will import both read and unread Inbox documents to XI
R2. Therefore, you will have to specify the location of the mail folder.
The documents are migrated to XI R2 users’ Inbox folders in the CMS.
Documents inherit the rights of the 6.x Inbox folder.
If the Inbox contains duplicate documents, they are also migrated to the FRS,
which manages all document instances that have been scheduled or
published to the repository.
To import 6.x Inbox documents that reside on a UNIX machine, you need to
map a drive from the Windows server running the Import Wizard to the
directories on the UNIX machine containing the documents.

Personal documents
Version 6.x personal documents (stored in
$STORAGEDIR\users\<username>) are imported to the user’s Favorites
folder in the destination CMS.
Documents inherit the rights of this folder. The document owner and the
Business Objects Administrator have access to these documents. Personal or
Corporate categories that referred to these documents in 6.x continue to refer
to them in XI R2.

BusinessObjects 6.x to XI Release 2 Migration Guide 85

5 Understanding object migration
Broadcast Agent

To import 6.x personal documents that reside on a UNIX machine, you need
to map a drive from the Windows server running the Import Wizard to the
directories on the UNIX machine containing the documents.

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

Task scheduling options

In addition, the following 6.x task scheduling options (in either
BusinessObjects or Web Intelligence) are not supported in XI R2:
Daily
• Week periodicity
Weekly
• Week periodicity
Monthly interval
• Business day
• Weekend day
• Month periodicity

86 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
Broadcast Agent 5
User-defined
• Weekday
• Business day
• Weekend day
Note: The migrated document may be assigned a different periodicity in XI
R2.

File Watcher
Deletes that you set in File Watcher may not function in XI R2.
In Broadcast Agent 6.x, in the Task Properties dialog box/Scheduling tab, you
can set the File Watcher feature. If you select one of the delete options:
• Delete the file each time the task starts
• Delete the file only if the task succeeded
• Delete the file after execution of the task
then after the job is imported to XI R2 by the Import Wizard, the File Watcher
details are transferred to the Event Server, but the deletes may not occur.

Associated universes
When you import scheduled documents from 6.x, you must also import the
universes used by these documents.
The universes are not selected automatically during the import. This means
that if you are not importing all your universes, you must manually select the
ones you need for Broadcast Agent jobs.
Make sure universes and connections are correctly set once imported.

How scheduled documents are migrated

The procedure is different, depending on whether the job schedules a
document in Corporate or Inbox.

Corporate
If the document is not already imported in the domain or is not imported at the
same time to the CMS, then the job is not migrated. Verification is performed
by comparing the CUIDs.
Otherwise, the Import Wizard creates an instance of this document using the
schedule parameters of the original job.

BusinessObjects 6.x to XI Release 2 Migration Guide 87

5 Understanding object migration
Broadcast Agent

• No ACL is set at this instance level. The instance inherits the ACL set at
the document level.
• If the document has been scheduled several times in Corporate, then the
same number of instances are created

Inbox
If the sender of the original schedule already exists in the CMS or if the
sender is migrated at the same time, then:
• The Import Wizard imports the scheduled document into the Favorites
folder of this user in the CMS. A folder named Scheduled migrated
documents/<BCA Name> is created under Favorites.
• The document is renamed to <doc_name>_<docID>.<ext>
• An instance is created for the document using the schedule parameters
of the original job
• No ACL is set at this instance level. The instance inherits the ACL set at
the folder level.
• The recipients (user or group) of the schedules are the recipients of the
original schedule, if they already exist in the CMS or if they are migrated
at the same time (name is verified).
If the sender of the original schedule does not exist in the CMS, then:
• The Import Wizard imports the scheduled document into Public Folders/
Scheduled migrated documents/<BCA name>. The document is renamed to
<doc_name>_<docID>.<ext>
• An instance is created for this document using the schedule parameters
of the original job
• No ACL is set at this instance level. The instance inherits the ACL set at
the folder level
• The recipients (user or group) of the schedules are the recipients of the
original schedule, if they already exist in the CMS or if they are migrated
at the same time (name is verified).

Renaming of migrated documents

Sometimes, when a document with an associated job is migrated, a
document with the same name already exists in the destination folder. The
renaming of the migrated document occurs differently, depending on whether
you are migrating in Merge mode or Update mode. (See “The Merge and
Update import scenarios” on page 169.)

88 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
Universes and universe connections 5
Merge mode
If a document with the same name as the 6.x document exists in the
destination folder, a new folder is created.
For example, for the 6.x document Annual.rep being migrated into the folder
named Agent, a new folder named Agent(2) is created, and Annual.rep is
reposted within Agent(2).
The document name and instance name do not change.

Update mode
The document ID is checked in the CMS. If it exists, the old document is
updated with the properties of the newly migrated document. The instances
are also replaced by the newly migrated schedules.
The schedules and the instances are identified by the ID received in the
Scheduled Jobs table of the repository.

Universes and universe connections

The Import Wizard imports universes from a 6.x deployment into an XI R2
deployment. During this process, the relationship between universes,
connections, and Desktop Intelligence/Web Intelligence documents is
maintained.
IDs of the documents, universes, and connections are converted to cluster
unique identifiers (CUIDs). The identifier distinguishes these objects from
objects imported later from the source environment.
When you import a universe:
• the Import Wizard imports any associated connection objects
• the connection is saved in the FRS and an InfoObject is created in the
CMS
• the universe and its linked documents are copied into the FRS
• universe overloads defined in 5.1/6.x, if migrated, are mapped to access
restrictions in XI R2 (see “Access restrictions” on page 92).
• ACEs are created to migrate universe-related security commands
• the locale is preserved

BusinessObjects 6.x to XI Release 2 Migration Guide 89

5 Understanding object migration
Universes and universe connections

The Import Wizard has three modes for importing universes:

Mode What it does

Import all universes and all Imports all universes and all connection
connection objects objects. You cannot select individual
universes or connections.
Import all universes and only Imports all universes, and only connection
connection objects used by objects used by those universes.
these universes
Import the universes and Imports all universes and connections used
connections that the by the selected documents. This option also
selected Web Intelligence enables you to select additional universes to
and BusinessObjects import, even if they are not used by any
documents use directly document.

When you select a Web Intelligence or BusinessObjects document to import,

the Import Wizard automatically selects the associated universes for import. It
does not do this, however, for universes used by scheduled documents
(Broadcast Agent jobs). This means that if you are not importing all your
universes, you must manually select the ones you need for Broadcast Agent
jobs.
Note: The Import Wizard also imports any universes with the same name
that exist in other domains.
BusinessObjects documents may have been created outside the repository,
using a “short name”; that is, a reference to a universe stored on a local
machine. If the universe has a short name, its linked documents may not be
imported if more than one universe is found in the CMS with the same short
name.
Universe domains are converted into subfolders under the Universe folder.
Each universe folder is named after the corresponding version 6.x universe
domain. When you import a universe from a domain, it is placed in the
corresponding domain folder.
If the universe is a derived universe, then all relevant core universes and their
connections are also imported.
Note: Designer 6.x cannot open universes created with Designer XI R2, due
to a file format change.

Connections
When you import version 6.x universes, the associated connections are
imported automatically. They are converted into connection objects.

90 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
Universes and universe connections 5
Make sure that the Import Wizard can access the 6.x database the same way
that version 6.x accesses it. You may need to install database drivers or
configure connection settings on the machine.
For example, if you import SQL Server connection objects from a 6.x source
environment, you must configure the connections on the destination machine
via the Control Panel before you import the connection objects. You must use
the same name and settings as the connection used on the source machine
when you created the domain key.

BOUSER/BOPASS
In version 6.x, users could use @Variable('BOUSER') and
@Variable('BOPASS') in the connection information for the universe. The
variables were replaced at runtime with the user’s enterprise username and
password, and used to log on to the database.
For security reasons, however, XI R2 does not permit the retrieval of users’
passwords. Therefore, universe connections that previously used the
BOUSER and BOPASS variables associated with the BusinessObjects user
name and password must now use database credentials (DBUSER and
DBPASS). Those database credentials can be populated by the Import
Wizard and later edited in the CMC, on the Properties tab for each user
account.
When migrating, Import Wizard automatically:
• replaces BOUSER and BOPASS with DBUSER and DBPASS in
universes
• proposes automatically populating these variables for users to migrate
You can, however, re-synchronize if users change their passwords.
Synchronizing enterprise and database credentials
There are three ways to synchronize enterprise and database credentials in
the XI R2 system. You can:
• choose the Import Wizard option that batch imports user names and
passwords from version 6.x to auto-populate database credentials in XI
R2.
• run a batch upload of a user’s file.
User names and passwords are loaded from a file, stored and used as
database credentials.
• create a custom application using Enterprise SDK to set DBUSER and
DBPASS information.

BusinessObjects 6.x to XI Release 2 Migration Guide 91

5 Understanding object migration
Universes and universe connections

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

Access restriction aggregation

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

Access restriction collapsing

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

92 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
Stored procedures 5
Stored procedures
In version 6.x, you can allocate stored procedures to users.
In XI R2, Use Connection for Stored Procedures is introduced as a new right
for the connection object.
During the import, for all stored procedures accessible to a user, an ACE
(Access Control Entry) is created for the user, with a corresponding
connection. Stored Procedures Access is enabled and the ACE is set to
Granted.

Folders, domains, and categories

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

Documents
Importing documents presents a good opportunity to optimize your document
management. For more information, see “What objects should you migrate?”
on page 239.

BusinessObjects 6.x to XI Release 2 Migration Guide 93

5 Understanding object migration
Documents

When documents contain no locale

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

BusinessObjects documents
When you import a 6.x BusinessObjects (.rep) document to XI R2, the
following occur:
• universe ID pointer is updated so that it references a universe in the
CMS.
• an InfoObject is created in the CMS for this document and for the saving
of this document
• properties are updated and displayed in the CMC
BusinessObjects template (.ret) documents do not contain cubes or a
connection to a universe. Therefore, all that occurs is:
• the locale of the document is updated
• an InfoObject is created in the CMS
To convert 6.x .rep documents to .wid format, you can use the Report
Conversion Tool, delivered with the XI R2 suite. See the Report Conversion
Tool Guide for more information.
Alternatively, you can use the Report Conversion Tool to convert .rep
documents to .wqy (Web Intelligence 2.x) format. Then, the Import Wizard
converts them from .wqy to .wid.
Note: .wid documents for which there is no universe (so-called orphan
documents) can be imported into XI R2.

94 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
Documents 5
BusinessObjects document rights
If you migrate security during the import of BusinessObjects documents,
version 6.x security commands are converted to XI R2 application-level and
document-level rights. Some commands have been eliminated and others
renamed.
The Administrators group in XI R2 has Full-Control access to documents. The
Everyone group has View access.
For a detailed summary of how BusinessObjects security commands are
migrated, see “BusinessObjects/Desktop Intelligence rights” on page 146.

Limitations
Keep in mind the following limitations when you import BusinessObjects
documents:
• XI R2 can read BusinessObjects 6.x .rep documents, but after you save
these documents in XI R2, they can’t be read by a 6.x version of the
software.
• BusinessObjects 6.x cannot open XI R2 Desktop Intelligence documents.
• OLAP data providers are not supported in XI R2.
BusinessObjects 6.x documents based on an OLAP data provider are
view-only in XI R2.
• There is no document password protection, on the server side, in XI R2.
• XI R2 Desktop Intelligence cannot access a version 6.x repository.

BusinessObjects SDK
The platform-related portion of the BusinessObjects SDK has evolved, which
means that code developed for 5.1/6.x will require updates for platform
interactions (authentication, send document, receive document).
Send to Users and Send to Broadcast Agent Server are not available in XI
R2. Instead, you need to use the Platform COM SDK.
The server-side report engine is not multi-document. This means that add-ins
will not be loaded on the server. For example, for a document based on a
custom data provider (DPVBAInterface) implemented in an add-in, refresh will
fail.
Calculator changes
XI R2 uses a different report engine than BusinessObjects 6.x. Therefore,
there are differences in the way the calculator is handled.
Because of this, there may be issues with BusinessObjects documents after
they are imported to XI R2.

BusinessObjects 6.x to XI Release 2 Migration Guide 95

5 Understanding object migration
Documents

See “Checking for calculation updates” on page 301 for more information.

Web Intelligence documents

Because Web Intelligence 2.x documents (.wqy) are no longer supported in
XI R2, the Import Wizard automatically converts them into the .wid format
supported in XI R2 before importing them.
WebIntelligence 6.x documents (.wid) are supported in XI R2, so the Import
Wizard performs no specific conversion when importing them.
When you import a Web Intelligence document:
• universe ID pointer is updated so that it references a universe in the
CMS.
• IDs in the Web Intelligence documents, universes, and connections are
converted to cluster unique identifiers (CUIDs), which will distinguish
these objects from objects subsequently imported from the source
environment.
• An InfoObject is created in the CMS for this document and for the saving
of the document.
• Properties are updated.
• If a .wqy and .wid document have the same name, they are both
imported, but the .wqy document is renamed to <name of
document>_WQY.wid.

Web Intelligence rights

If you choose to migrate security, all security commands in version 6.x Web
Intelligence documents are migrated to XI R2.
A number of rights are new in Web Intelligence XI R2. For example:
• Edit SQL
• Allow user to merge dimension for synchronization
• Interactive Editing rights
The version 6.x security command Allow use of the WebIntelligence HTML
Report Panel has been renamed to Enable Query - HTML. After it is migrated,
set it to Denied.

96 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding object migration
Documents 5
Limitations
There may be an issue with the migration of the following .wqy features to
.wid:
• Autofit/Column width/Wrap text
There may be a difference in the column widths.
• Locale
In some Web Intelligence 2.x versions, locale was not stored in the .wqy
file. If no locale is found in the .wqy file, the Import Wizard prompts you
for a locale.
Customizing the Conversion Settings file
You can customize the Conversion Settings XML file to change cell width and
autowrap settings. The file is located in:
$INSTALLDIR\BusinessObjects Enterprise 11.5\win32_x86\wqyConversionSettings.xml
The settings can be changed on the following lines:
<OPTION NAME="cell_width_wrap" VALUE="auto" />
<OPTION NAME="cell_width_autofit" VALUE="auto" />
Note:
• If value is “auto”, WQY conversion keeps the option as is
• If value is “yes”, WQY conversion switches the option to yes
• If value is “no”, WQY conversion switches the option to no

Application Foundation objects

If you have Application Foundation 6.5.1 or later, you can use the Import
Wizard to import dashboards, analytics, and schedules into the CMS of XI R2.
Note: Application Foundation is called performance management in XI R2.
The performance management repository structure in XI R2 is similar to that
of Application Foundation v. 6.5. There is no significant change in the
architecture.
You can update the Application Foundation repository with the Application
Foundation Repository Update Tool provided with XI R2.
For complete information on importing Application Foundation objects, see
Chapter 6: Understanding Application Foundation object migration.

BusinessObjects 6.x to XI Release 2 Migration Guide 97

5 Understanding object migration
Documents

Third-party documents
BusinessObjects Enterprise 6.x supports third-party (also known as
“agnostic”) documents. The Import Wizard imports these documents into XI
R2 if the format is supported. Formats supported in XI R2 include Adobe
Acrobat PDF; Microsoft Power Point, Word, RTF, and Excel; and *.txt
documents.
For the most up-to-date list of supported formats for third-party documents,
see the list of supported platforms.

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

98 BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding Application
Foundation object migration

chapter
6 Understanding Application Foundation object migration
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now

D 1. Assessment and planning

• Migrating to Performance Management XI R2

• Migrating the Application Foundation repository and its
contents
• Migrating dashboards
• Migrating analytics
• Migrating schedules
• Migrating rules and named events
• Migrating security commands
• What you cannot migrate
2. Preparing for import
3. Importing from the source to destination environment
4. Post-import checking and tuning

Migrating to Performance Management XI

R2
The Import Wizard migrates Application Foundation objects from your 6.x
deployment to performance management XI R2.

100 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating to Performance Management XI R2 6
Objects stored in the Application Foundation repository and locally on the
Application Foundation server are either:
• migrated to the performance management XI R2 repository
Note: The Import Wizard writes new tables and columns to the
Application Foundation repository during the upgrade. Business Objects
strongly recommends that you copy the source repository before
migrating, and that you run the Import Wizard on the copy of the source.
This enables you to keep your source environment intact during and after
migration. Refer to Migrating the Application Foundation repository and
its contents for details.
• imported and published by the Import Wizard to the XI R2 CMS (Central
Management Server)
As in previous versions, performance management relies on its own
dedicated repository as well as the Business Objects repository previously,
now the CMS.

BusinessObjects 6.x to XI Release 2 Migration Guide 101

6 Understanding Application Foundation object migration
Migrating to Performance Management XI R2

During migration from Application Foundation 6.x to performance

management XI R2, certain Application Foundation objects are published to
the CMS, and others remain in the Application Foundation repository, which is
upgraded to support new features in XI R2:

Note: You must install XI R2 and configure and deploy the CMS before
running the Import Wizard. This includes configuring the administrator
account for managing the performance management repository, and making
a copy of the source Application Foundation repository available for the
migration process. See “Planning the migration” on page 221 for information
on the migration workflow.

102 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating to Performance Management XI R2 6
Supported migration paths
The following versions are supported for migration to performance
management XI R2:
• Application Foundation 6.1.b, 6.1.3, 6.5.1, 6.5.2
• performance management XI (see the BusinessObjects Enterprise XI
Release 2 Installation Guide for information on migrating from XI)
When you migrate the Application Foundation 6.1 or 6.5 repository, the Import
Wizard writes new tables and columns to the repository to support the new
features in performance management XI R2 (see “Migrating the Application
Foundation repository and its contents” on page 104 for a list of changes
made to the repository during migration).
Just like the BusinessObjects Enterprise XI R2 repository, the performance
management XI R2 repository is integrated into the CMS.

Using the Import Wizard

See “Using the Import Wizard” on page 261 for a step-by-step explanation on
how to use the Import Wizard to migrate from Application Foundation to
performance management XI R2.

Before using the Import Wizard

Before running the Import Wizard, check the integrity of the source
environment. Business Objects recommends that you:
• copy the source Application Foundation repository before migrating, and
run the Import Wizard on the copy of the source
• run the Scan and Repair utility on the BusinessObjects repository
• check the integrity of universes referenced by Application Foundation
objects (in Setup > System Setup > Tools)
• check the version and integrity of the source Application Foundation
repository
• check the location of the Application Foundation storage folder
• check the location of the inbox and personal folders
• ensure that your database connections are valid
• ensure that the appropriate middleware is installed

BusinessObjects 6.x to XI Release 2 Migration Guide 103

6 Understanding Application Foundation object migration
Migrating the Application Foundation repository and its contents

The Import Wizard assumes that the source environment is clean. The Import
Wizard cannot resolve problems present in the source environment during
migration.
For example, if there are inconsistencies between universe IDs in the
Application Foundation repository (in the ci_source table) and the
BusinessObjects repository, the source ID will not be correctly mapped to the
CUID (the cluster unique ID that is assigned to the universe) assigned by the
Import Wizard during import. Double-check that universes referenced in the
ci_source table have the same id in the BusinessObjects repository before
running the Import Wizard. For information on checking the integrity of the
source environment, see Best Practices for Migrating to BusinessObjects
Performance Management XI R2.

Migrating Application Foundation objects

The following types of objects are supported for migration from
BusinessObjects Application Foundation 6.x:

To find out about this object... See this section...

The Application Foundation repository, Migrating the Application
connections, and data stored in the Foundation repository and its
repository tables (including metrics, contents
goals, and sets)
Dashboards Migrating dashboards
Analytics Migrating analytics
Schedules Migrating schedules
Rules Migrating rules and named events
Agnostic documents Agnostic documents

Migrating the Application Foundation

repository and its contents
The Import Wizard migrates the Application Foundation 6.x repository to
version XI R2. You can also migrate other objects to the CMS without
migrating the repository, and migrate the repository during a later import. The
repository migration is an optional step in the Import Wizard, which enables

104 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating the Application Foundation repository and its contents 6
you to migrate the repository during a later import. By default, the Application
Foundation repository is not selected for migration in the Import Wizard. You
must explicitly select this option.
Note: You must migrate the Application Foundation repository in the same
Import Wizard session during which you import rules, schedules containing
rules, and events. If you choose not to upgrade the repository, you cannot
import these types of objects. In addition, if you choose not to upgrade the
repository, your repository connections will not be active on the migrated
environment.
Business Objects strongly recommends that you copy the Application
Foundation repository before migration and that you run the Import
Wizard on the copy, to ensure that your source environment stays intact
after migration.
The Import Wizard physically changes the Application Foundation repository
during migration. The Import Wizard does not make a copy of the repository
before migrating it. For information on continuing to deploy the source
environment after migrating, see “Maintaining the source repository during
migration” on page 106.
When you upgrade the repository in the Import Wizard, it updates the
Application Foundation repository into the performance management XI R2
repository. The Application Foundation repository contains:
• Dashboard Manager tables, which contain metric attributes and values
• Performance Manager tables, which contain goals, target values,
strategies and roles
• Set Analysis tables, which contain set data
The performance management XI R2 repository includes new columns in the
repository tables to support new features and the new architecture. For
example:
• a new column is added to the table containing universe information (the
ci_source table) to store the newly attributed CUID used to reference the
InfoObject that represents the universe in the CMS. In XI R2, all
universes are stored as InfoObjects in the CMS. Links to other universes
are also automatically updated in the ci_source table.
• new columns are added to the metric table (ci_probe) to store the new
metric attributes supported in XI R2 (metric description, metric owner, last
refresh date)
• new columns are added to the goal table (ci_target) to store new
information about goal import

BusinessObjects 6.x to XI Release 2 Migration Guide 105

6 Understanding Application Foundation object migration
Migrating the Application Foundation repository and its contents

• links to documents are automatically overwritten and upgraded in rule

definitions (in the ci_rule table)
• the following tables become obsolete after the import: ci_task (since
scheduled tasks are now handled in the CMS) and ci_connection (since
connections are now managed by the Connection Server)
During the upgrade process, the Import Wizard detects dependencies
between Application Foundation data and BusinessObjects universes and
automatically imports those universes on which the data relies but that were
not explicitly selected for import.

Verifying the repository import

To check that your 6.x repository was successfully migrated, look for the
following entry in the Import Wizard trace file:
updateAF65DB
If this entry exists, the 6.x repository was upgraded by the Import Wizard. If
you do not see this entry in the file, the repository was not upgraded.
Note: To activate the trace, launch the Import Wizard with the -trace option in
the command line. This generates a trace file in the $INSTALLDIR\logging
folder.

Maintaining the source repository during migration

The Application Foundation repository migration in the Import Wizard is
intrusive to the source repository. The source repository (6.x) is not copied to
the destination environment (XI R2); the repository itself is transformed when
you migrate the Application Foundation repository in the Import Wizard. When
the Import Wizard updates a 6.x repository to XI R2, it modifies existing tables
and writes new columns and tables to the repository, making it unreadable in
version 6.x.
If you plan to continue to deploy the previous version while migrating, perform
the following steps:
1. Copy the 6.x Application Foundation repository that you want to migrate.
2. Configure the connections (the universe and document domains and the
Application Foundation repository connections) on the source
environment so that it functions correctly with the copy of the source
repository.

106 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating the Application Foundation repository and its contents 6
3. Point the Import Wizard to the copy of the source repository. This ensures
that only the copy of the source repository is affected by changes made
by the Import Wizard. The original source repository remains unchanged.
4. Run the Import Wizard to import objects to the CMS and to migrate the
Application Foundation repository.
Optionally, you can maintain the source system and continue to develop
dashboards, analytics and documents on the 6.x version. You can then import
these types of objects to the XI R2 version incrementally as you develop them
on the source system, as long as none of the changes affect the source
repository (refer to “Importing objects incrementally” on page 107 for details).

Importing objects incrementally

You can maintain your source and destination environments in parallel and
continue to develop objects that do not require changes to the repository
(such as dashboards, analytics, and documents) on the source version. You
can then migrate only these new objects to the XI R2 CMS using the Import
Wizard, without reimporting the repository.
Note: The incremental import feature applies to objects whose creation do
not impact the Application Foundation source repository. These include
dashboards, analytics, and documents that are stored in the BusinessObjects
Enterprise repository or the Application Foundation local storage on the
source system and are imported into the destination CMS. This feature
therefore does not apply to metrics, whose creation and modification change
information stored in the Application Foundation source repository. Once you
have migrated the Application Foundation repository, you will no longer be
able to migrate objects that rely on data stored within. The Application
Foundation repository can only be migrated once.
To use the incremental migration feature, select individual objects to import
from the source environment, and specify in the Import Wizard that you do not
want to import the Application Foundation repository. In this case, the
selected objects are imported directly to the XI R2 CMS, and the Application
Foundation source repository is not affected.
Note: You cannot import schedules, rules containing schedules, events, or
universes without migrating the repository. Migrating these objects requires
writing information to the performance management repository and may affect
the source repository.
You may need to import certain objects more than once from the source
environment to the destination environment. In this case, the Import Wizard
allows you to choose between keeping the source copy or the destination
copy of the object after import.

BusinessObjects 6.x to XI Release 2 Migration Guide 107

6 Understanding Application Foundation object migration
Migrating dashboards

Migrating repository connections

Connections to the Application Foundation repository are also migrated by
the Import Wizard. In XI R2, connections are managed by the Connection
Server. See the Designer online help for more information on the Connection
Server.
You can import all universes and connections, or only those universes and
connections referenced by the performance management objects (such as
dashboards and analytics) that you have selected for import. See “If you’re
migrating Application Foundation” on page 274 for information.
Each connection you import is stored as an InfoObject in the CMS.
Performance management XI R2 makes use of the XI R2 standard
connection layer. Performance management XI R2 uses the Connection
Server to run the SQL generated by the following performance management
engines:
• Sets
• SPC
• Metrics
• Predictive
Connections are configured in Designer and stored in the CMS. See the
Designer online help for more information.

Migrating dashboards
The Import Wizard migrates the information that makes up your Corporate
and Personal Application Foundation dashboards.
During migration, the Import Wizard imports the analytics, Web Intelligence
documents, and BusinessObjects documents that compose your dashboards
into the CMS and publishes them as InfoObjects. The XML menus and
submenus that define the structure of your applications and dashboards are
also migrated. In Application Foundation 6.x, XML menus and submenus
were stored in the local storage folder:
Application Foundation\Server\conf\menu.xml
The Import Wizard publishes dashboards as InfoObjects in the CMS.
When you select a dashboard in the Import Wizard, corporate documents
referenced by the dashboard are automatically imported. In version 6.x,
corporate documents are referenced in dashboards by their docID. During
migration, the Import Wizard assigns unique CUIDs to corporate documents

108 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating dashboards 6
and publishes them in the CMS. The docID that referenced the corporate
document in the dashboard is replaced by the new CUID in the dashboard’s
migrated XML definition.

Dashboard menus and submenus

In XI R2, menus and submenus are published to the CMS as InfoObjects.
The Import Wizard parses the XML definition of the dashboard, and
substitutes the DocIDs of the documents and analytics referenced in the
dashboard definition by the new CUID supported in XI R2.
Applications, menus and submenus are published as InfoObjects. Their
structure is maintained. Each dashboard and application is assigned to a
folder, and their submenus are stored in subfolders of the main folder.

Dashboard security
If you migrate security, the security on your Application Foundation 6.x
dashboards at the application and menu levels is migrated and maintained in
performance management XI R2. User rights stored in the Business Objects
repository are now stored in the CMS as access levels, or ACLs.
Note: The Import Wizard does not import analytic-level security within
dashboards. See “Migrating security commands” on page 113 for more
information.

Agnostic documents
The Import Wizard imports the following types of agnostic (third-party)
documents referenced in dashboards and publishes them to the CMS:
• SVG, or snapshot views of analytics
• *.xml and *.swf (flash)
• *.csv used in custom calendar definition
• graphic files (such as *.gif, *.bmp, *.png, *.jpg files) used as backgrounds
in Strategy Builder definitions or Metric Tree backgrounds and in
dashboards

BusinessObjects 6.x to XI Release 2 Migration Guide 109

6 Understanding Application Foundation object migration
Migrating analytics

The Import Wizard publishes these files as InfoObjects in the destination

environment, where they are accessed by the performance management
applications that reference them. The CMS also supports the following object
types as InfoObjects:
• programs
• Microsoft Excel files
• Microsoft Word files
• Microsoft PowerPoint files
• Adobe Acrobat PDFs
• rich text format files
• text files
• hyperlinks
• object packages, which consist of report and/or program objects

Migrating analytics
You can use the Import Wizard to migrate analytics (.afd documents) from the
BusinessObjects 6.x repository to performance management XI R2. During
migration with the Import Wizard, you can select individual analytics for
migration to performance management XI R2. The Import Wizard publishes
the objects you select for migration in the CMS as InfoObjects.
You can migrate both corporate and personal analytics in the Import Wizard.

Migrating links to analytics and documents

Links in analytics and dashboards to other analytics or documents are
migrated by the Import Wizard. The Import Wizard locates links within the
dashboards that you have selected for import. The Import Wizard then reads
the BusinessObjects repository ID attributed to the target document in version
6.x.
During import, the BusinessObjects 6.x repository ID is replaced with a new
CUID when documents are published to the CMS. When links are migrated,
the Import Wizard replaces the document’s BusinessObjects 6.x repository ID
in the link with document’s XI R2 CUID. The reference to the target document
is updated in the link, and the link will therefore open the same document,
migrated to the new repository, using its new CUID.

110 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating schedules 6
Migrating schedules
In Application Foundation 6.x, the scheduler was run as an executable on the
Application Foundation server. Scheduled tasks were stored in the ci_task
table of the Application Foundation repository. The scheduler passed metric
refresh information to the metric refresh engine.
Application Foundation schedule definitions, rules that contain schedules in
their definitions, and named events are imported during the update of the
performance management XI R2 repository in the Import Wizard.
The Import Wizard retrieves schedule descriptions from the ci_task table in
the Application Foundation repository, then publishes and stores all migrated
schedules in the CMS. In performance management XI R2, all scheduled
tasks are managed by the CMS scheduler. Schedules related to performance
management objects are stored in a dedicated performance management
folder in the Schedule Manager of the CMS.
Note: Application Foundation schedules created with Broadcast Agent are
not supported in BusinessObjects Enterprise XI R2 and are therefore not
migrated. See “What you cannot migrate” on page 114 for details.
Tip: If you recreate the CMS on the destination environment, make sure that
the AFScheduleProgram is present in the CMS before you migrate. If the
AFScheduleProgram is not available, and you migrate the repository, you
could lose the schedules in the source repository during migration.

Troubleshooting schedule migration

The situations described below may lead to an incomplete migration of
schedules from the Application Foundation repository.

Migrating with user credentials that are no longer valid

If you attempt to migrate schedules with administrator credentials that are no
longer valid, the AFScheduleProgram is created with invalid security
credentials. The migration is successful, but migrated schedules will not work.
To manually correct this problem after migration:
1. Log into performance management with a valid administrator profile.
2. In Setup > Parameters > Options > Scheduler Parameters, update the
user account under which scheduled programs will run.
3. In Setup > Tools > Check & Cleanup, click Scheduled Programs to
launch the Check & Cleanup Scheduled Programs window.
4. Click Select All then Fix to update all scheduled programs.

BusinessObjects 6.x to XI Release 2 Migration Guide 111

6 Understanding Application Foundation object migration
Migrating rules and named events

Migrating schedules after reinstalling the CMS

If you reinstall the CMS and the AFScheduleProgram is missing from the
CMS, attempts to migrate schedules will fail. To manually correct this problem
before migration:
1. Log into the CMC, and delete any AFScheduleProgram instances that
may have been created (AFScheduleProgram instances are created
when users attempt to access schedules).
2. Log into performance management XI R2 with a valid administrator
profile.
3. In Setup > Parameters > Options > Scheduler Parameters, update the
user account under which scheduled programs will run.
4. Migrate schedules to performance management XI R2.
If schedules do not migrate correctly, perform the following steps after
migration:
1. Log into performance management with a valid administrator profile.
2. In Setup > Parameters > Options > Scheduler Parameters, update the
user account under which scheduled programs will run.
3. In Setup > Tools > Check & Cleanup, click Scheduled Programs to
launch the Check & Cleanup Scheduled Programs window.
4. Click Select All then Fix to update all scheduled programs.

Migrating rules and named events

Rules are composed of events, conditions and actions. In Application
Foundation 6.x, rules are stored in the Application Foundation repository.
In XI R2, rule definitions continue to be stored in the ci_rule table in the
performance management repository but are managed in various locations
depending on the event type:
• Scheduled tasks are managed by the CMS scheduler (see “Migrating
schedules” on page 111).
• Named events are launched by the Event server and managed in the
Central Management Console. The event is then passed on to the
appropriate performance management server for execution. During
migration, named events are imported into the CMS. Named events can
be referenced in a rule defined in performance management.
• Events based on the refresh of metrics and other performance
management objects continue to be managed in the performance
management repository.

112 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
Migrating security commands 6
During migration with the Import Wizard, schedules and rules containing
scheduled tasks are imported from the Application Foundation repository to
the CMS. Links to documents within rule definitions are updated in the ci_rule
table during migration of the Application Foundation repository.
Note: Rules that contain actions requiring the pre-rendering of HTML by the
Broadcast Agent scheduler are migrated, but these types of actions are no
longer supported in performance management XI R2. See “Broadcast Agent
schedules” on page 115 for details.

Migrating security commands

Application Foundation 6.x security is defined:
• in security commands in the Business Objects repository
• in security commands associated with the Application Foundation
application in Supervisor
• in custom security commands created with appsecurity.exe
In XI R2, security is managed in the CMS. If you decide to import security,
when you migrate Application Foundation objects, the Import Wizard reads
the current access rights, converts them into ACLs, then applies the
appropriate ACL to the appropriate InfoObject. For example, the Import
Wizard reads the access rights applied to a specific dashboard and its
submenus, publishes the access rights as ACLs, then applies them as
required to the InfoObjects referenced by the dashboard.
Security commands applied to individual analytics within a dashboard are not
migrated by the Import Wizard. Objects must be published in the CMS in
order to be secured individually with ACLs. Choose one of the following
options for migration of dashboards with analytic-level security restrictions:
• The Import Wizard migrates the dashboard and any sub-menus and
applies standard page-level security, which is translated as an ACL in the
CMS. With this option, the least restrictive set of rights is applied.
• The Import Wizard skips any dashboards with analytic-level security
restrictions during migration.
• The Import Wizard migrates dashboards with analytic-level security
restrictions and saves them directly in an access-restricted folder. The
administrator can then modify these dashboards manually before
publishing them to a wider audience.

BusinessObjects 6.x to XI Release 2 Migration Guide 113

6 Understanding Application Foundation object migration
What you cannot migrate

Managing user rights in Performance Management XI

R2
To manage ACL rights for Performance Management users
1. Launch the Central Management Console.
2. In the Manage menu, select BusinessObjects Applications.
3. Select Performance Management from the list of applications.
4. In the Rights tab, click Check User Rights to display a detailed list of
rights per user or user group, or click Add/Remove to change the rights
currently granted to users or groups.
See the BusinessObjects Enterprise XI Release 2 Administrator’s Guide for more
details on managing ACLs.

Managing rights at the object level in Performance

Management XI R2
In performance management XI R2, you can grant rights to corporate
analytics, application menus, documents and folders in the Central
Management Console.
In performance management XI R2, you cannot create custom security
commands as you could in Application Foundation 6.x. Use the Central
Management Console to secure individual objects.
See the BusinessObjects Enterprise XI Release 2 Administrator’s Guide for more
details on managing object-level security.
The following sections describe product features and objects that cannot be
migrated from Application Foundation 6.x.

What you cannot migrate

The following sections describe product features and objects that cannot be
migrated from Application Foundation 6.x.

114 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Application Foundation object migration
What you cannot migrate 6
Analytic-level security within dashboards
Security on dashboards, application menus and submenus are migrated by
the Import Wizard. Restrictions on individual analytics on a dashboard page
are not migrated, however. See “Migrating security commands” on page 113
for more information.

Broadcast Agent schedules

In Application Foundation 6.x, you can use the Broadcast Agent to schedule a
cache preload for faster HTML rendering. This feature no longer exists in XI
R2. The following options are no longer available:
• When you customize the properties of BusinessObjects documents
imported into dashboards, the Only look for documents in personal
inbox option no longer exists.
• When you customize the properties of BusinessObjects documents
imported into dashboards, the Use Pre-generated HTML when
available option no longer exists.
• When you create or edit rules on the Rules page of Dashboard Manager,
the Schedule HTML generation option no longer exists.
Application Foundation 6.x rules containing actions that required pre-
rendering are migrated in the Import Wizard. The action that calls for pre-
rendering a document is not executed.
Tip: You can check the integrity of rules on the Tools tab of the System
menu. When you run the integrity check on rules, it detects rules that include
actions requiring document pre-rendering with Broadcast Agent scheduler.
After you determine which migrated rules contain obsolete actions, you can
edit the rule to delete the obsolete actions or delete the rule entirely.

Application Foundation 6.x Corporate and Personal dashboards containing

BusinessObjects documents on which pre-rendering was activated are
migrated in the Import Wizard. When the impacted document is called, it is
rendered normally without preloading the cache.

BusinessObjects 6.x to XI Release 2 Migration Guide 115

6 Understanding Application Foundation object migration
What you cannot migrate

116 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding rights
migration

chapter
7 Understanding rights migration
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now

D 1. Understanding what migration entails

• Comparison of the security models

• Standard migration paths
• Special import scenarios
• Rights by product/component
2. Assessment and planning

3. Preparing for import

4. Importing from the source to destination environment
5. Post-import checking and tuning

Security overview
Although the rights model for versions XI R2 and 6.x may seem similar at first
glance, fundamental differences between the inheritance, aggregation, and
default rules of versions 6.x and XI R2 can complicate rights migration.
For example, some version 6.x security commands are phrased in such a
way that granting them is actually placing a restriction on the user or group;
e.g. a user may be granted the right to Do not delete other user's documents.
In XI R2, all rights increase a user's power when they are granted, so
negatively-phrased 6.x rights are rephrased positively in XI R2, and the value
of the corresponding right is reversed during migration.
This chapter provides an overview of the rights models for versions 6.x and XI
R2, describes how their differences impact migration, and then explains the
approaches adopted to ensure equivalent rights in the migrated model.
Note: You do not have to import rights when importing your BI content to XI
R2. For information concerning whether to import security or rebuild security
in the destination environment from scratch, see “Importing security or not” on
page 225.

118 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Security overview 7
Rights terminology
The following table contains basic terminology you need to know to
understand the security models and rights migration.

Term Definition
collapse If certain conditions are met on objects in 6.x, we need to
set rights directly on the corresponding object(s) in XI R2.
This may involve setting rights that were not explicitly set
on the relevant 6.x objects (due to the difference in
aggregation models). This process of copying explicit
rights from 6.x is known as collapsing rights on the XI R2
object. In most cases, inheritance is broken when
collapsing is done.
custom rights Rights that are defined in the plugin pinfile for an object
type (not including the meta-plugin types). The CMS is
not aware of custom rights and cannot enforce them: they
are enforced by the SDK.
explicit vs. Explicit rights are set directly on the object, while effective
effective rights rights are the net result rights considering inheritance,
aggregation, and default settings. When determining
whether a user is able to perform an action, it is only the
effective rights that are important.
newly-denied A right that is effectively denied on the principal but
effectively granted on the principal's parent (that is,
granted explicitly or via inheritance).
newly-enabled A security command that is effectively enabled on the
principal but effectively denied or hidden on the
principal's parent (explicitly or via inheritance).
newly-granted A right that is effectively granted on the principal but
effectively denied on the principal's parent (that is, denied
explicitly or via inheritance).

BusinessObjects 6.x to XI Release 2 Migration Guide 119

7 Understanding rights migration
Comparison of the security models

Term Definition
principal A user or group, typically one for whom rights are set on
some object
View right Abbreviation for the most basic access right to XI R2
objects.
• When referring to application objects, it corresponds
to a version 6.x product access right (in the CMC, the
option is worded Log on to <application_name> and
view this object in the CMC). It gives users/groups
the right to launch and use a product.
• When referring to other objects, it confers the right to
access and view the object.

Comparison of the security models

6.x vs. XI R2 rights types
All XI R2 rights are Boolean, which is to say, Granted, Denied, or unspecified.

Version 6.x Version XI R2

Product access rights Application rights are set on
The right to use products such as application objects (like the Designer
Web Intelligence and Designer, e.g. or Supervisor application object).
Joe tries to log into Designer, but his The View right, which controls the
product access right for Designer is user’s ability to launch and use an
Denied so his logon fails. application, corresponds to a version
There is one product access right per 6.x product access right.
product per user.

120 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Comparison of the security models 7
Version 6.x Version XI R2
Security commands
In XI R2, security commands can be
The right to use certain features of a
product. Security command rights are equivalent to application rights set
associated with a product such as on application objects (like the
Web Intelligence or Designer and Designer or Supervisor application
typically correspond to actions such object), or object rights, set on
as Save docs or Rename docs; these content objects or the folder that
contains them (like universe or Web
are usually distinct actions offered by
the user interface. Intelligence document objects or
Possible values are: domain folders).
• Enabled (UI element visible) For detailed information on how each
6.x security command migrates to XI
• Disabled (UI element grayed-out) R2, see “Rights by product/
• Hidden (UI element not shown) component” on page 146. Many
security commands, however, have
If the right is not specified, it is no meaning in the XI R2 system and
considered enabled. are therefore not migrated.
Applications can have multiple
security commands.
Domain access rights Object rights are set on content
The right to access the contents of a objects or the folder that contains
universe or document domain. them (like universe or
Web Intelligence document objects
Universe/document access or domain folders).
The right to access individual
universes or documents. Users need
both the domain access right and the
universe/document right to use a
document or universe.
Other rights such as overloads and
object level security (not discussed in
this chapter).

BusinessObjects 6.x to XI Release 2 Migration Guide 121

7 Understanding rights migration
Comparison of the security models

6.x vs. XI R2 default and aggregate rules per right type

The fundamental default and aggregate rules governing rights change in
version XI R2, to maintain tighter system security. In the following table, blue
columns contain version 6.x information, and white columns display XI R2
information.

Right Type Default Value Default Value Aggregation Rules Aggregation

(6.x) in Version 6.x in Version in Version 6.x Rules in
XI R2 Version XI R2
Product Granted Denied If Granted or If unspecified or
access right (Except for unspecified Denied anywhere,
Designer and anywhere: Granted then Denied
Supervisor If Denied
access rights, everywhere: Denied
which are set to
Denied on the
root folder at
install time.)
Security Enabled Denied • If Hidden • Hidden in 6.x =
command anywhere, then Denied in XI R2
Hidden • If unspecified or
• If Disabled Denied
anywhere, then anywhere, then
Disabled Denied
• Otherwise,
Enabled
Domain Granted Denied If Granted (or If unspecified or
access right unspecified) Denied anywhere,
anywhere: Granted then Denied
Document/ Denied Denied If Granted If unspecified or
universe anywhere: Granted Denied anywhere,
access right then Denied

Universe restriction set aggregation

When are access restrictions aggregated? Users generally belong to multiple
groups, as they are all part of the Everyone group and are likely to belong to
at least one other group.
In version 6.x, a user can have multiple instances. For users with multiple
instances, instance priorities (defined in Supervisor) are used to resolve
conflicts.

122 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Comparison of the security models 7
In XI R2, there is no notion of user instances. Users can inherit from multiple
groups, so group priorities are used to resolve conflicts:
• Users have higher priority than groups.
• Priority 1 is the highest priority.
You can preview net restrictions for any given user or group. Restriction
preview is available for all 6 tabs.
Connection overloads
In version 6.x, connection overloads are defined in Supervisor.
In XI R2, connection overloads are part of access restrictions. Use Designer
to define an access restriction.

6.x vs. XI R2 inheritance

The main challenge during migration is the difference in inheritance rules
between version 6.x and XI R2:
• In 6.x, rights inheritance is propagated through groups only. For example,
because Tom and Lea belong to the Marketing group, they inherit all the
rights established for the Marketing group.

BusinessObjects 6.x to XI Release 2 Migration Guide 123

7 Understanding rights migration
Comparison of the security models

• In XI R2, rights are inherited both through groups and through objects. In
this environment, for example, Tom and Lea would still inherit all
Marketing group rights. In addition, however, if the rights set for the Sales
Results folder allowed Tom to access that folder, if no subfolder or
document rights contradicted that right, Tom would automatically have
access to all the documents in that folder.

Version 6.x Version XI R2

The only type of rights inheritance is Both group and folder inheritance
group inheritance. exist.
When a right is set on a group it Rights are inherited from ancestor
applies to all subgroups, unless it is objects and groups, unless either
overridden for a subgroup or user. type of inheritance is explicitly turned
Rights set lower down in the group off. Turning off inheritance prevents
tree take priority. That is, rights on an that type (group or object) of
user's parent take priority over those inheritance for all the rights for a
on the grandparent, and so on. principal (user or group) on an object.
You cannot turn off inheritance for
some rights but not others.
Inherited rights are “equal” to explicit
rights, and when rights conflict,
denied always takes priority,
regardless of the source of the
conflicting rights.
Because of this model, and because
denied takes priority over granted,
you cannot give child users or groups
more rights than their parents without
breaking inheritance. You can
change a right from unspecified
(effectively denied) to granted, but
not from denied to granted.

Breaking inheritance in XI R2
In the XI R2 inheritance model, you must break inheritance if you want to
grant a right for a child that has been specifically denied for a parent. (Partly
for this reason, the XI R2 BusinessObjects Enterprise SDK automatically
breaks the inheritance when a role is set on a principal.)
Breaking inheritance allows XI R2 to imitate the 6.x inheritance model
somewhat, but the break applies to all rights; you cannot turn off inheritance
for some rights but not others.

124 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Standard migration paths 7
In XI R2 you can break both group and folder inheritance. Breaking group
inheritance however is more important to consider during import, because
hierarchical folders do not exist in version 6.x.

Standard migration paths

User right migration
Key security features provided by BusinessObjects 6.x (as applied to the
integrated components) are available in version XI R2. Along with the ability
to specify rights at the object level, version XI R2 provides the ability to
specify global rights for Web Intelligence, Desktop Intelligence, and
Performance Management Applications.

BusinessObjects 6.x to XI Release 2 Migration Guide 125

7 Understanding rights migration
Standard migration paths

The following identifies the migration path for integrated rights:

Right type in Migrated to version XI R2 as... Value migration:

version 6.x 6.x = XI R2
Product access Right to view application object (View right) Granted = Granted
rights Denied = unspecified
For more information, see “Application rights
migration” on page 128.
Security commands Right to corresponding application object, Positively-phrased
domain folder, or content object security commands:
For more information, see “Application rights Hidden = Denied
migration” on page 128. Denied = Denied
Unspecified =
BusinessObjects security commands migrate Denied
as rights set on:
• the Desktop Intelligence application Negatively-phrased
(application rights) security commands:
• Desktop Intelligence documents or Granted = Denied
document domain folders (object rights) Denied = Granted
Web Intelligence security commands migrate as Unspecified =
rights set on: Granted
• the Web Intelligence application (See Negatively- and
positively-phrased
• the InfoView application
security command
• Web Intelligence documents or document migration below.)
domain folders
Designer security commands migrate as rights Some security
set on: commands are
• the Designer application combined when they
are migrated. See
• universe domain folders
the following section.

126 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Standard migration paths 7
Domain access Right to view corresponding domain folder Granted = Granted
rights (domains are migrated as folders, and their Denied = Denied
universes/documents as child objects of the
domain folder) Unspecified =
Denied
For more information, see “Document/universe
The value of the
domain rights migration” on page 132. migrated domain
access right affects
Child universes/documents inherit folder rights the value of migrated
unless inheritance is broken. security commands
and document
access rights. See
Combining security
commands during
migration below.
Document/universe Right to view corresponding content object
access rights
For more information, see “Document/universe
rights migration” on page 139.

Combining security commands during migration

Some security commands are combined when they are migrated in order to
better map to XI R2 rights.
When two or more 6.x security commands are mapped to the same XI R2
boolean right, both commands must be granted for the XI R2 right to be
granted; otherwise the XI R2 right is denied.
For example, the two 6.x commands Generate in PDF Format and Generate
in Excel Format are migrated as the single right Export. The Export right is set
to granted only if both the Generate in PDF Format and Generate in Excel
Format rights are set to granted in the source environment. If this is not the
case, the Export right is denied.

Negatively- and positively-phrased security command migration

Negatively-phrased security commands are migrated differently than
positively-phrased ones, because the negatively-phrased rights are re-
worded to be positively-phrased during migration.
For example, if the fictional 6.x right You cannot delete were denied, then the
user would have the right to delete. During migration, the right is changed to
You can delete, and so its value is migrated as granted. The net result is that
the user still has the right to delete.

BusinessObjects 6.x to XI Release 2 Migration Guide 127

7 Understanding rights migration
Special import scenarios

The following table shows how version 6.x negatively- and positively-phrased
security commands are migrated.

Positively-phrased security Negatively-phrased security

commands commands
Granted are migrated as Granted Granted are migrated as Unspecified
Denied are migrated as Denied Denied are migrated as Granted

Special import scenarios

Rights collapsing
Whenever you use the Import Wizard, you choose the groups you want to
import. You can migrate a user or group, known generically as a principal,
without a parent.
This is always the case when the principal is a root group itself, and therefore
has no parents. This is also the case when the principal has a parent in the
source deployment, but you choose not to migrate it. For users, this is true if
any of the groups to which it belongs is not imported.
This case typically triggers rights collapsing. When a parent group is not
migrated, inheritance is broken, and the children become roots themselves.
The children are not “reconnected” to their grandparents; instead, rights are
collapsed on these new roots.
Although the parent is not migrated, any rights set explicitly on the parent are
still considered when collapsing the rights on the now-orphaned child. In
general, the effective rights of imported principals are preserved, even if other
principals which contribute to those rights (such as grandparents) are not
imported.

Application rights migration

The following 6.x rights can be migrated to an application object in XI R2:
• Product access rights
• Security commands

128 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Full collapse
When application objects are migrated, a full collapse of rights is triggered for
users/groups in the following cases:
• A principal is being imported without a parent.
• The effective product access right for a principal is newly-granted.
• A security command is newly-enabled for the principal.
A full collapse for application objects means that:
• Group and folder inheritance is broken.
• The effective security commands on the 6.x application object are
calculated and mapped to the application object in XI R2.
• The effective product access right is calculated and set on the application
object as a View right.

BusinessObjects 6.x to XI Release 2 Migration Guide 129

7 Understanding rights migration
Special import scenarios

Migration (no full collapse)

In some cases in migration, for the sake of efficiency, rights that are not
required are not explicitly set, but left unspecified after the import.
Import scenario 1 (application objects)
Principal Imported with parent
Product access right for principal Newly-granted
Result The View right is set as Granted

130 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Import scenario 1 (application objects)
Principal Imported with parent
Principal’s security command Effectively hidden, or disabled, but
effectively enabled for parent
Result Set as Granted for principal, and
unspecified for the parent (if positively-
phrased)

BusinessObjects 6.x to XI Release 2 Migration Guide 131

7 Understanding rights migration
Special import scenarios

Document/universe domain rights migration

Document and universe domains are migrated as folders. The following 6.x
rights can be migrated to a domain folder in XI R2:
• Domain access rights
• Security commands

Domain right rules

Remember that:
• Some security commands on the Designer application are migrated as XI
R2 rights on universe domain folders.
• Some security commands for the Web Intelligence application are
migrated as XI R2 rights on document domain folders.
• Rights set on documents or universes in the domain may affect rights set
on the domain itself (see “Document/universe rights migration” on
page 139).
• Documents contained in a folder inherit the rights from their parent
domain folder, unless inheritance is broken.

Full collapse
In some domain folder imports, a full collapse of rights is triggered. This
means:
• Group and folder inheritance is broken.
• The effective values for object-level security commands are mapped to
the domain folder.
Full collapsing on the domain folder is triggered in the following cases.

132 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Special import scenario 1 (domain rights)
Principal Imported without parent
Principal’s domain access right Effectively granted
Result Full collapse: View right is added as
Granted, and is inherited by all
documents in folder

BusinessObjects 6.x to XI Release 2 Migration Guide 133

7 Understanding rights migration
Special import scenarios

Special import scenario 2 (domain rights)

Principal Imported without parent
Principal’s domain access right Effectively granted
Result Full collapse: View right is added as
Granted, and is inherited by all
documents in folder

134 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Special import scenario 3 (domain rights)
Principal Imported with parent(s)
Principal’s domain access right Granted
Principal’s security commands Has a newly-enabled security
command
Result Full collapse: View right is added as
Granted, and inherited by all
documents in folder

BusinessObjects 6.x to XI Release 2 Migration Guide 135

7 Understanding rights migration
Special import scenarios

Migration (no full collapse)

The following particular migration cases exist:
Special import scenario 4 (domain rights)
Principal Imported with parent(s)
Principal’s domain access right Granted, but not newly-granted
Principal’s security commands No newly-enabled security commands
Result Full collapse: View right is added as
Granted, and inherited by all
documents in folder
Applicable, newly-denied security commands are mapped to this domain. (In
this case, only newly-denied security commands are migrated. If a security
command was denied for the parent, it is inherited as Denied in the new
system; to reduce the number of rights that are explicitly set, it is not
migrated.)

136 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7

BusinessObjects 6.x to XI Release 2 Migration Guide 137

7 Understanding rights migration
Special import scenarios

Special import scenario 5 (domain rights)

Principal Imported with parent(s)
Principal’s domain access right newly-denied
Result No security commands are migrated (as
the principal doesn’t have access to the
domain, they would be irrelevant).
No View rights are added.
Group and folder inheritance are broken.

138 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Document/universe rights migration
Document and universe access rights in 6.x are migrated to XI R2 as View
rights on the corresponding document or universe object.
Note: Everything described for documents in this section also holds true for
universes as well.

Net access for documents/universes

A document's net access is the document access right aggregated with the
domain access right. This means that if either the document access or
domain access right is denied, the document access right is denied.
The view right on the document can also be inherited from the view right on
the folder to which it belongs in the destination system.

Migration (no full collapse)

The following migration cases exist:
Special import scenario 1 (domains/universes)
Principal Imported with parent Imported without parent
Net document access newly-granted Granted
Result: Any applicable security commands that were set
on the corresponding application are migrated
directly to the document domain containing the
document.
Rights are migrated like this because a newly-granted document right could
mean that inheritance will be broken somewhere up the group structure. If
inheritance is broken, then the security commands will not be inherited
properly and therefore need to be explicitly migrated.
The concepts in this paragraph are illustrated in the two diagrams below. In
the first case (Case A) the containing domain has the View right explicitly
granted during migration. This View right will be inherited by the document in

BusinessObjects 6.x to XI Release 2 Migration Guide 139

7 Understanding rights migration
Special import scenarios

that domain folder. In the second case (Case B), the containing domain will
not have the view right explicitly granted when it is migrated. Therefore it must
be explicitly added to this document as Granted.

140 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Case B

BusinessObjects 6.x to XI Release 2 Migration Guide 141

7 Understanding rights migration
Special import scenarios

Special import scenario 2 (domains/universes)

Principal Imported with parent
Net document access newly-denied
Result: Both folder and group inheritance are broken.

Net document access (document access combined with domain access) is

newly-denied. Both folder and group inheritance are broken.

142 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7

BusinessObjects 6.x to XI Release 2 Migration Guide 143

7 Understanding rights migration
Special import scenarios

Special import scenario 3 (domains/universes)

Principal Imported with parent
Net document access Denied
Containing domain View right = Granted
Result: Both folder and group inheritance are broken.

144 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Special import scenarios 7
Connection objects (stored procedure rights)
migration
A stored procedure is a group of SQL statements that perform a particular
task. Stored procedures are kept in the database.
Version 6.x stored procedure rights, migrated as rights to database
connection objects, control access to the stored procedures kept on that
database.
Granted stored procedure rights are migrated as Granted, and denied stored
procedure rights are migrated as unspecified.
Connections are secured in XI R2 but not in version 6.x. The following XI R2
rights are therefore always set to Granted on the connection object:
• connection access right
• View right
In addition, the stored procedure right is migrated to the connection object. By
default, new connection rights are disabled in XI R2, just as they are in 6.x.

Full collapse
A full collapse of rights is triggered on connection objects when:
• a principal is imported without a parent
• the stored procedure right for a principal is newly-denied

Special import scenario (stored procedures)

Principal Imported without parent
Principal’s stored newly-denied
procedure right
Result: Full collapse

Full collapse for a connection object means:

• folder and group inheritance are broken
• the View right is added as Granted
• the data access right is added as Granted
• the stored procedure right is added:
• Granted is migrated as Granted
• Denied is migrated as unspecified

BusinessObjects 6.x to XI Release 2 Migration Guide 145

7 Understanding rights migration
Rights by product/component

Migration (no full collapse)

Special import scenario (stored procedures)
Principal Imported with parent
Principal’s stored newly-granted
procedure right
Result: The stored procedure right to the connection object
is added as Granted.

Rights by product/component
This section includes:
• BusinessObjects/Desktop Intelligence rights
• Web Intelligence/Web Intelligence rights
• Designer rights
• Connection rights
Note: In this section, XI R2 rights:
• beginning with the words “securely modify” mean that the user with this
right can only grant or deny rights that they have themselves to other
users.
• ending with “on objects that the user owns” are calculated based on who
the owner of the object is

BusinessObjects/Desktop Intelligence rights

This section covers:
• Application rights in the destination vs. source environments
• Document rights (.rep or .rea)
• How source BusinessObjects security commands migrate

Application rights in the destination vs. source environments

The following table lists access rights for the BusinessObjects application,
their values for the View access level, and how they are migrated from
version 6.x.

146 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
In this table:
• General rights are those that BusinessObjects inherits from application
rights (Application object).
• Custom rights are those which concern BusinessObjects only. No Access
means all rights are Denied; Full Control means that all rights are
Granted.

General rights in XI R2 View Rights in source environment

Log on to BusinessObjects and Granted N/A
view this object in the CMC
Edit this object Inherited N/A
Modify the rights users have to Inherited N/A
this object
Securely modify rights users Inherited N/A
have to objects

Custom rights in XI R2 View Rights in source environment

Drill Through Granted Drill Through
Edit Scope of Analysis Granted Edit Scope of Analysis
Work in Drill Mode Granted Work in Drill Mode
Work in Slice-and-Dice Mode Granted Work in Slice-and-Dice Mode
Create And Edit Connections Inherited Create And Edit Connections
Copy to Clipboard Inherited Copy to Clipboard
Create Documents Inherited Create Documents
Create Templates Inherited Create Templates
Data Provider Manipulation Inherited Data Provider Manipulation
Document Interactions Inherited Document Interactions
Edit Euro Converter Rate Inherited Edit Euro Converter Rates
Euro Converter Inherited Euro Converter
Manage All Corporate Inherited Manage All Corporate
Categories Categories
Manage My Corporate Inherited Manage My Corporate
Categories Categories
Print Documents Granted Print Documents
Refresh Document List and Inherited Refresh Documents
Categories

BusinessObjects 6.x to XI Release 2 Migration Guide 147

7 Understanding rights migration
Rights by product/component

Custom rights in XI R2 View Rights in source environment

Refresh Document Granted Refresh Documents
Report Interactions Granted Report Interactions
Import Documents Granted Either Retrieve Documents from
Other Users, or Retrieve
Documents from Repository
Save Documents Granted Save Documents
Save documents for all users Inherited Save for All Users
Send Documents to MAPI Granted Send Documents to MAPI
Export Documents Granted Send Documents to Repository
Use Templates Inherited Use Templates
Edit Free-hand SQL Inherited Edit Free-hand SQL Scripts
Use Free-hand SQL Inherited Use Free-hand SQL
Edit Personal Data Files Inherited Edit Personal Data Files
Use Personal Data Files Inherited Use Personal Data Files
Edit Stored Procedures Inherited Edit Stored Procedures
Use Stored Procedures Inherited Use Stored Procedures
Edit VBA Code Inherited Edit Scripts/VBA Code
Install Add-Ins Inherited Install and Uninstall Add-Ins
Run VBA Code Granted Run Scripts/VBA Code
Always Regenerate SQL Inherited Negation of (Do not always
regenerate SQL)
Use Queries Inherited Use Queries
Use List of Values Inherited Use Lists of Values
Use User Objects Inherited Use User Objects
Edit Queries Inherited Edit Query
Edit List of Values Inherited Edit Lists of Values
Edit Query SQL Inherited Edit Query SQL
Refresh List of Values Inherited Refresh Lists of Values
Use other SQL requests than Inherited Negation of (Restrict SQL to
Select “Select” only)
View SQL Inherited View Query SQL
Change Password Inherited Change Password

148 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
By default, the following ACEs are created for the BusinessObjects
application:
• The Administrators group has the Full-Control access level for this
application.
• The Everyone group has the View access level for this application.

Document rights (.rep or .rea)

In version XI R2, you can set rights on reports or add-in Desktop Intelligence
documents. As these objects use the same desktop plug-in in the XI R2
framework, they have the set of rights.
The following table lists these rights and their values for View, Schedule and
View on Demand access levels. For the No Access role, all rights are Denied;
for the Full Control role, all rights are Granted.
Like Web Intelligence documents, Desktop Intelligence documents inherit
General rights, and have their own set of custom rights.

General rights for Desktop View Schedule View on

Intelligence documents Demand
Add objects to the folder Not Specified Not Specified Not Specified
View objects Granted Granted Granted
Edit objects Not Specified Not Specified Not Specified
Modify the rights users have to Not Specified Not Specified Not Specified
objects
Schedule the document to run Not Specified Granted Granted
Delete objects Not Specified Not Specified Not Specified
Define server groups to Not Specified Granted Granted
process jobs
Delete instances Not Specified Not Specified Not Specified
Copy objects to another folder Not Specified Granted Granted
Schedule to destinations Not Specified Granted Granted
View document instances Granted Granted Granted
Pause and Resume document Not Specified Not Specified Not Specified
instances
Securely modify rights users Not Specified Not Specified Not Specified
have to objects
Reschedule instances Not Specified Not Specified Not Specified

BusinessObjects 6.x to XI Release 2 Migration Guide 149

7 Understanding rights migration
Rights by product/component

General rights for Desktop View Schedule View on

Intelligence documents Demand
Schedule on behalf of other Not Specified Not Specified Not Specified
users
View objects that the user Not Specified Not Specified Not Specified
owns
Edit objects that the user owns Not Specified Granted Granted
Modify the rights that users Not Specified Not Specified Not Specified
have to objects that the user
owns
Delete objects that the user Not Specified Not Specified Not Specified
owns
Delete instances that the user Not Specified Granted Granted
owns
View document instances that Not Specified Not Specified Not Specified
the user owns
Pause and Resume document Not Specified Granted Granted
instances that the user owns
Securely modify rights users Not Specified Not Specified Not Specified
have to objects that the user
owns
Reschedule instances that the Not Specified Granted Granted
user owns

Custom rights for Desktop View Schedule View on

Intelligence documents Demand
Refresh the report’s data Not Specified Not Specified Granted
Edit Query Not Specified Not Specified Not Specified
Refresh List of Values Not Specified Granted Granted
Use List of Values Not Specified Granted Granted
View SQL Not Specified Not Specified Not Specified
Export the report’s data Not Specified Granted Granted
Download files associated with Not Specified Not Specified Not Specified
the object

150 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
How source BusinessObjects security commands migrate
The following table shows how version 6.x security commands are migrated
to version XI R2, and the mechanism by which each security command is
enforced. Some rights are mapped to a right that can be set both at the
application and document level, but 6.x security commands are migrated at
the application level only.
Note: BusinessObjects 6.x releases prior to version 6.5 may not include all of
these security commands

BusinessObjects XI R2 rights Enforced by

security commands in
source environment
Analysis
Drill Through Drill Through Desktop Intelligence
Edit Scope of Analysis Edit Scope of Analysis Desktop Intelligence
Work in Drill Mode Work in Drill Mode Desktop Intelligence
Work in Slice-and-Dice Work in Slice-and-Dice Desktop Intelligence
Mode Mode
Work with BusinessMiner (Application no longer
used)
Connections
Create and Edit Create and Edit Desktop Intelligence
Connections Connections
Documents
Attach Scripts to (Not used in XI R2)
Scheduled Processing
Change File Locations (Not used in XI R2)
Conditional Formatting (Not used in XI R2)
Copy to Clipboard Copy to Clipboard Desktop Intelligence
Create Documents Create Documents Desktop Intelligence
Create Templates Create Templates Desktop Intelligence
Data Provider Data Provide Desktop Intelligence
Manipulation Manipulation
Delete Corporate (Not needed, enforced by CMS
Documents Sent by Other framework)
Users

BusinessObjects 6.x to XI Release 2 Migration Guide 151

7 Understanding rights migration
Rights by product/component

BusinessObjects XI R2 rights Enforced by

security commands in
source environment
Do Not Refresh with the (Not used in XI R2)
Profile of Each Recipient
Document Interactions Document Interactions Desktop Intelligence
Edit Euro Converter Rate Edit Euro Converter Rate Desktop Intelligence
Euro Converter Euro Converter Desktop Intelligence
Manage All Corporate Manage All Corporate Desktop Intelligence
Categories Categories
Manage My Corporate Manage My Corporate Desktop Intelligence
Categories Categories
Print Documents Print Desktop Intelligence
Refresh Document List Refresh Document List Desktop Intelligence
and Categories and Categories
Refresh Documents Refresh Document Desktop Intelligence
+ document (refresh
the report’s data)
Report Interactions Report Interactions Desktop Intelligence
Retrieve documents from Import Documents Desktop Intelligence
Other Users
Retrieve Documents from Import Documents Desktop Intelligence
Repository
Retrieve Documents from (Not a BusinessObjects Job Server
Scheduled Processing right - Enforced by
framework)
Save Documents Save Documents Desktop Intelligence
Save documents for all Save documents for all Desktop Intelligence
users users
Schedule Corporate (Not a BusinessObjects CMS
Documents right - Enforced by
framework)
Send Documents for (Not a BusinessObjects Job Server
Scheduled Processing right - Enforced by
framework)
Send Documents to MAPI Send Documents to MAPI Desktop Intelligence
Send Documents to Other (Not used in XI R2)
Users

152 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
BusinessObjects XI R2 rights Enforced by
security commands in
source environment
Send Documents to Export Documents Desktop Intelligence
Repository
Use Broadcast Agent (Not used in XI R2)
Console
Use Templates Use Templates Desktop Intelligence
Work with Web Server (Broadcast Agent
publishing a document on
the Web in HTML format.
Not used in XI R2)
Free-hand SQL
Edit Free-hand SQL Edit Free-hand SQL Desktop Intelligence
Scripts
Use Free-hand SQL Use Free-hand SQL Desktop Intelligence
Miscellaneous
Cannot View User/Groups (Not used in XI R2)
Hierarchy
View All Users (Not used in XI R2)
Multi-dimensional data
Edit DB2 OLAP Data (Not used in XI R2)
Edit Essbase Query (Not used in XI R2)
Edit Express Query (Not used in XI R2)
Use DB2 OLAP Data (Not used in XI R2)
Use Essbase Data (Not used in XI R2)
Use Express Data (Not used in XI R2)
Personal data files
Edit Personal Data Files Edit Personal Data Files Desktop Intelligence
Use Personal Data Files Use Personal Data Files Desktop Intelligence
Programmability
Download VBA from Web (Used only by version 5
Intelligence users)
Import/convert scripts (Used only by version 5
users)

BusinessObjects 6.x to XI Release 2 Migration Guide 153

7 Understanding rights migration
Rights by product/component

BusinessObjects XI R2 rights Enforced by

security commands in
source environment
Edit Scripts/VBA Code Edit VBA Code Desktop Intelligence
Install and Uninstall Add- Install Add-Ins Desktop Intelligence
Ins
Run Scripts/VBA Code Run VBA Code Desktop Intelligence
Query Technique
Do not Always Always Regenerate SQL Desktop Intelligence
Regenerate SQL (Negative rephrasing!)
Edit List of Values Edit List of Values Desktop Intelligence
Edit Query Edit Query Desktop Intelligence
+ document (Edit
Query)
Edit Query SQL Edit Query SQL Desktop Intelligence
Refresh List of Values Refresh List of Values Desktop Intelligence
+ document
(Refresh List of
Values)
Restrict SQL to “Select” Use other SQL Requests Desktop Intelligence
Only than Select
(Negative rephrasing!)
Use List of Values Use List of Values Desktop Intelligence
+ document (Use
List of Values)
Use Queries Use Queries Desktop Intelligence
Use User Objects Use User Objects Desktop Intelligence
View Query SQL View SQL Desktop Intelligence
+ document (View
SQL)
Stored procedures
Edit Stored Procedures Edit Stored Procedures Desktop Intelligence
Use Stored Procedures Use Stored Procedures Desktop Intelligence
Tools
Change Password Change Password Desktop Intelligence
Login As (Not used in XI R2)

154 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7

Web Intelligence/Web Intelligence rights

In version XI R2, some new rights have been added for the Web Intelligence
application:
• Edit SQL, to control the user’s ability to edit SQL query
• Merge dimensions for synchronization, to control the user’s ability to edit
a semantic link for multiple data providers
• Enable Query - HTML, to control the user’s ability to use the HTML
Report Panel
Rights linked to interactive editing have also been updated to provide more
granularity.
This section covers:
• Application rights in the destination vs. source environment
• Document rights (.wid)
• How Web Intelligence security commands migrate

Application rights in the destination vs. source environment

The following table lists how the Web Intelligence rights are migrated from a
version 6.x system.

Web Intelligence XI R2 application Equivalent in source environment

general rights
Log into Web Intelligence and view N/A
this object in the CMC
Edit this object N/A
Modify the rights users have to this N/A
object
Securely modify rights users have to N/A
objects

Web Intelligence XI R2 application Equivalent in source environment

custom rights
Java Report Panel: Edit SQL (New in XI R2)
Merge dimensions for (New in XI R2)
synchronization

BusinessObjects 6.x to XI Release 2 Migration Guide 155

7 Understanding rights migration
Rights by product/component

Web Intelligence XI R2 application Equivalent in source environment

custom rights
Enable interactive HTML viewing (if Use Interactive Viewing
license permits)
Enable Query - HTML Report Panel Use Web Intelligence HTML Report
Panel
Enable HTML Report Panel N/A
Once migrated, set to “Not Specified”
Enable Java Report Panel Use Web Intelligence Java Report
Panel
Extend scope of analysis Extend Scope of Analysis
Enable drill mode Allows working in drill mode
Create document Allows creation of documents
Java Report Panel: Enable formula Allows use of the Formula bar when
toolbar creating documents in the Java
Report Panel
Interactive: General - Enable right (New in XI R2)
click menu
Interactive: General - Edit “My
Preferences”
Interactive: Left Pane - Enable (New in XI R2)
document summary
Interactive: Left Pane - Enable data (New in XI R2)
summary
Interactive: Left Pane - enable (New in XI R2)
document structure and filters
Interactive: Left Pane - Enable (New in XI R2)
available objects, tables and charts
Interactive: Formatting - Enable Use Formatting Toolbar
toolbar and menus
Interactive: Reporting - Create and (New in XI R2)
edit report filter
Interactive: Reporting - Create and (New in XI R2)
edit sort
Interactive: Reporting - Create and (New in XI R2)
edit break
Interactive: Reporting - Create and (New in XI R2)
edit predefined calculation

156 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
Web Intelligence XI R2 application Equivalent in source environment
custom rights
Interactive: Reporting - Create and (New in XI R2)
edit alerter
Interactive: Reporting - Create and (New in XI R2)
edit rank
Interactive: Reporting - Insert or (New in XI R2)
duplicate report, table, chart and cell
Interactive: Formula - Enable toolbar (New in XI R2)
and variable creation

Document rights (.wid)

In version XI R2, you can set rights on documents. The following table lists
these rights and their values for View, Schedule and View on Demand access
levels. For the No Access role, all rights are Denied; for the Full Control role,
all rights are Granted.
Like Desktop Intelligence documents, Web Intelligence documents inherit
general rights, and have their own set of custom rights.

Web Intelligence (.wid) XI R2 View Schedule View on

document general rights Demand
Add objects to the folder Not Specified Not Specified Not Specified
View objects Granted Granted Granted
Edit objects Not Specified Not Specified Not Specified
Modify the rights users have to Not Specified Not Specified Not Specified
objects
Schedule the document to run Not Specified Granted Granted
Delete objects Not Specified Not Specified Not Specified
Define server groups to Not Specified Granted Granted
process jobs
Delete instances Not Specified Not Specified Not Specified
Copy objects to another folder Not Specified Granted Granted
Schedule to destinations Not Specified Granted Granted
View document instances Granted Granted Granted
Pause and Resume document Not Specified Not Specified Not Specified
instances

BusinessObjects 6.x to XI Release 2 Migration Guide 157

7 Understanding rights migration
Rights by product/component

Web Intelligence (.wid) XI R2 View Schedule View on

document general rights Demand
Securely modify rights users Not Specified Not Specified Not Specified
have to objects
Reschedule instances Not Specified Not Specified Not Specified
Schedule on behalf of other Not Specified Not Specified Not Specified
users
View objects that the user Not Specified Not Specified Not Specified
owns
Edit objects that the user owns Not Specified Granted Granted
Modify the rights that users Not Specified Not Specified Not Specified
have to objects that the user
owns
Delete objects that the user Not Specified Not Specified Not Specified
owns
Delete instances that the user Not Specified Granted Granted
owns
View document instances that Not Specified Not Specified Not Specified
the user owns
Pause and Resume document Not Specified Granted Granted
instances that the user owns
Securely modify rights users Not Specified Not Specified Not Specified
have to objects that the user
owns
Reschedule instances that the Not Specified Granted Granted
user owns

Web Intelligence (.wid) View Schedule View on

document custom rights Demand
Refresh the report’s data Not Specified Not Specified Granted
Edit Query Not Specified Not Specified Not Specified
Refresh List of Values Not Specified Granted Granted
Use List of Values Not Specified Granted Granted
View SQL Not Specified Not Specified Not Specified
Export the report’s data Not Specified Granted Granted
Download files associated with Not Specified Not Specified Not Specified
the object

158 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
How Web Intelligence security commands migrate
The following table shows how version 6.x security commands are migrated
to version XI R2, and the mechanism by which each security command is
enforced. Some rights are mapped to a right that can be set both at the
application and document level, but 6.x security commands are migrated at
the application level only.
Note: Depending on your precise source version, your release may not
include all of these security commands.

Web Intelligence XI R2 right Enforced by

security commands in
source environment
Administration
Change Password (Not used in XI R2)
Download 3-tier (Not used in XI R2)
BusinessObjects
Use interactive viewing Use interactive viewing Web Intelligence
Use the Web Intelligence Enable HTML Report Web Intelligence
HTML Report Panel Panel
Use the Web Intelligence Enable the Java Report Web Intelligence
Java Report Panel Panel
Analysis
Extend Scope of Analysis Extend Scope of Analysis Web Intelligence
Transparent Drill Outside (Not used in XI R2 - used
of Cube only with 5.x documents)
Work in Drill Mode Enable drill mode Web Intelligence
InfoView
Add External Content to Add External Content to InfoView
My InfoView My InfoView
Change Skin (Not used in XI R2)
Customize the Interface Change Homepage InfoView
Manage My Corporate (Not used in XI R2 - BI platform
Categories defined instead with rights
on the folder and the
categories)

BusinessObjects 6.x to XI Release 2 Migration Guide 159

7 Understanding rights migration
Rights by product/component

Web Intelligence XI R2 right Enforced by

security commands in
source environment
Manage All Corporate (Not used in XI R2 - BI platform
Categories defined instead with rights
on the folder and the
categories)
Manage Personal (Not used in XI R2 - Intelligence tier
Categories defined instead with rights
on the folder and the
categories)
Read Corporate (Not used in XI R2 - Intelligence tier
Documents defined instead with rights
on the document and the
folder)
Read Inbox Documents View Inbox InfoView
Refresh View of (Not used in XI R2)
Document Lists and
Categories
Save and Read Personal (Not used in XI R2 - BI platform
Documents defined instead by rights
on the folder)
Save to Corporate (Not used in XI R2 - BI platform
Documents defined instead by rights
on the folder)
Upload Documents (Not used in XI R2 - BI platform
defined instead by rights
on the folder)
Publications
Manage Email (Not used in XI R2)
Publications
Manage Web Publications (Not used in XI R2)
Query and Web Panel
Allows creation of Create Documents Web Intelligence
documents (Allows creation of Web
Intelligence documents)
Do Not Always
Regenerate SQL
Edit Documents Edit Documents Web Intelligence

160 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
Web Intelligence XI R2 right Enforced by
security commands in
source environment
Edit Query Edit Query Web Intelligence
Refresh Lists of Values Refresh List of Values Web Intelligence
Use Formatting Toolbar Interactive: Formatting - Web Intelligence
enable toolbar and menus
Use Formula Language / Interactive: Formula - Web Intelligence
Create Variables Enable toolbar and
variable creation
Use Lists of Values (Not used in XI R2 - Web Intelligence
defined instead with rights
on the document)
View SQL (Not used in XI R2 - Web Intelligence
defined instead by rights
on the document)

Designer rights
This section covers:
• Application rights in the destination vs. source environment
• Universe rights
• How Designer security commands migrate

Application rights in the destination vs. source environment

Designer application general Equivalent in source environment

rights
Log on to the Designer and view this N/A
object in the CMC
Edit this object N/A
Modify the rights users have to this N/A
object
Securely modify rights users have to N/A
objects

BusinessObjects 6.x to XI Release 2 Migration Guide 161

7 Understanding rights migration
Rights by product/component

Designer application custom Equivalent in source environment

rights
Check Universe Integrity Check Universe Integrity
Refresh Structure Window Refresh Structure Window
Use Table Browser Use Table Browser
Apply Universe Constraints Apply Universe Constraints
Link Universe Link Universe

Universe rights
In version XI R2, you can set rights on universes. Universes inherit general
rights, and have their own set of custom rights.

Universe general rights Equivalent in source environment

Add objects to the folder Export universe (to a given folder)
View objects Enable universe
Edit objects N/A
Modify the rights users have to N/A
objects
Schedule the document to run N/A
Delete objects N/A
Copy objects to another folder N/A
Securely modify rights users have to N/A
objects
View objects that the user owns N/A
Edit objects that the user owns N/A
Modify the rights users have to N/A
objects that the user owns
Delete objects that the user owns N/A
Securely modify rights users have to N/A
objects that the user owns

Universe custom rights Equivalent in source environment

New List of Values New List of Values
Print Universe Print Universe
Show Table or Object Values Show Table or Object Values

162 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding rights migration
Rights by product/component 7
Universe custom rights Equivalent in source environment
Edit Access Restrictions (New in XI R2)
Unlock Universe (New in XI R2)
Data Access (New in XI R2)

How Designer security commands migrate

The following table shows how version 6.x security commands are migrated
to version XI R2, and the mechanism by which each security command is
enforced. Some rights are mapped to a right that can be set both at the
application and document level, but 6.x security commands are migrated at
the application level only.
Note: Depending on your precise version, your release may not include all of
these security commands.

Designer security XI R2 right Enforced by

commands in source
environment
Connection
Create, Modify and (Not used in XI R2) BI platform
Remove Connection
View All Secured (Not used in XI R2) BI platform
Connections
Miscellaneous
Check Universe Integrity Check Universe Integrity Designer
Refresh Structure Refresh Structure Designer
Window Window
Use Table Browser Use Table Browser Designer
Tools
Change Password (Not used in XI R2)
Login As (Not used in XI R2)
Universe
Apply Universe Apply Universe Designer
Constraints Constraints
Export List of Values (Not used in XI R2)
Export Universe (Not used in XI R2)
Import Universe (Not used in XI R2)

BusinessObjects 6.x to XI Release 2 Migration Guide 163

7 Understanding rights migration
Rights by product/component

Designer security XI R2 right Enforced by

commands in source
environment
Link Universe Link Universe Designer
New List of Values New List of Values Universe
New Universe (Not used in XI R2)
Prevent from Overwriting Edit Objects (General) Universe
Universe
Print Universe Print Universe Universe
Show Table or Object Show Table or Object Universe
Values Values

Connection rights
In version 6.x, you can allocate stored procedures to users.
In XI R2, a stored procedure is implemented as a new right for the connection
object: Use connection for Stored Procedures.
During migration, for all stored procedures enabled for a user, an ACE
(Access Control Entry) is created for the user, the corresponding connection
and the correct stored procedures access. This ACE is set to Granted.

164 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding Import
Wizard options

chapter
8 Understanding Import Wizard options
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now

D 1. Understanding what migration entails

• Security migration options

• The Merge and Update import scenarios
2. Assessment and planning
3. Preparing for import
4. Importing from the source to destination environment
5. Post-import checking and tuning

Overview
The Import Wizard contains a number of options that impact how selected
principals (users or groups) or objects are imported. These options concern
issues such as:
• whether objects are imported with or without source security settings
• whether imported objects can update existing objects in the CMS and if
so, how
• whether objects can be renamed to coexist with like-named objects

Security migration options

Because of the difference between the 6.x and XI R2 security models — and
the clear superiority of the latter — the recommendation for the migration of
large or complex deployments is to migrate your BI content without migrating
its security, and then rebuild security using the greater granularity and control
of the new environment.
You can import objects without security simply by importing them without any
users or groups.

166 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
Security migration options 8
If you want to import both objects and principals at one time, however, you
can still import the objects without their rights by choosing the appropriate
option in the Import Wizard’s Security Migration Options dialog box.
When you select users/groups to be imported, rights may be imported as well:
• If you have selected objects as well, users’ rights on these objects will be
imported.
• Rights on applications, such as InfoView and Web Intelligence are
always imported.
To give you more flexibility in how these rights are migrated, the Import
Wizard provides three security migration options which allow you to import
objects either with their rights or without them; if you import security, it also
allows you to restrict user rights.

BusinessObjects 6.x to XI Release 2 Migration Guide 167

8 Understanding Import Wizard options
Security migration options

To migrate the rights of the objects you’re importing

Choose one of the first two options:
• The first option imports the objects’ content and rights, in order to
reproduce the version 6.x security model. It also sets additional rights in
the destination CMS pertaining to the imported objects:

Object Value
Performance Management folder (top level) No Access
access level
All Desktop Intelligence rights Not specified
All Web Intelligence rights Not specified
All Designer rights Not specified

As these rights are set for the Everyone group, they apply to all users,
unless they are explicitly assigned another value. To give them access,
administrators must use the CMC to explicitly grant the proper users the
appropriate rights.
This is the most secure option, selected by default.
• The second option imports the objects’ contents and rights, in order to
reproduce the version 6.x security model, but does not set the restrictions
in the target CMS that it sets in the first option.
Default settings are set in the Everyone group for some rights, and apply
to all users. As these default values may be different from the version 6.x
defaults, this may allow migrated users to have more rights than they had
in the source environment.
If you want to avoid this, use the first option (see above) or do not migrate
security and recreate it in the new environment (see next section).
In both cases, the Import Wizard sets the access level for the Everyone group
to No Access for all imported domain folders. This restricts access for all
users for whom no default rights are given.
After the import, you must use the CMC to explicitly give access to users and
groups for specific folders. If you give access to a domain folder to the
Everyone group, all users will have access to this folder and be able to see all
documents in it.
Before doing this, make sure you have thoroughly reviewed the security using
the CMC.

168 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
To migrate objects without their rights
Choose the third option to migrate object content without object rights. Here
are the consequences:
• Security is neither imported nor created for corporate universes (.unv)
and universe domains.
• Security is neither imported nor created for corporate Desktop
Intelligence (.rep, .rea, .ret), Web Intelligence (.wqy, .wid), Analytics (.afd)
and agnostic documents and document domains
• Security is neither imported nor created for connections. This includes
the Stored Procedures right that is not set for the connection object.
• Power user logins such as General Supervisor, Supervisor, and Designer
are not added into administration groups (Administrators, Designer
Users, Report conversion tool Users, etc.).
• Users are not assigned to the appropriate Object Level Security groups,
which apply limits on top-level universe folders.
• Full-control owner rights on the top-level user and user group folders are
not set for Supervisors.
• Application rights (InfoView, Web Intelligence, BusinessObjects/Desktop
Intelligence, Designer) rights are not migrated and not recreated.
As no security is migrated at all, this option is recommended if you want to
redesign the security in your destination repository, and fully benefit from the
XI R2 framework. For help in assessing what this entails, see Chapter 11:
Recreating security in XI R2.

The Merge and Update import scenarios

When you use the Import Wizard, you can choose to merge the source and
destination systems, or you can update the destination environment with the
objects in the source system.

BusinessObjects 6.x to XI Release 2 Migration Guide 169

8 Understanding Import Wizard options
The Merge and Update import scenarios

These options primarily affect behavior when the same objects are imported
into a destination system multiple times. They also affect the conflict
resolution behavior when two different objects with the same name are
imported to the same location.

The options’ difference comes into play only when you re-import objects that
have already been imported into the CMS.
Note: The consequences of all Merge and Update options are summarized
in tables at the end of this section.

How the Import Wizard compares source and

destination objects
Depending on the import scenario, the Import Wizard compares objects by
one of the following:
• name (including path)

170 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
• by CUID, a cluster unique identifier based on object type, object ID/object
name (if no ID), and the repository GUID.
Any object imported from version 6.x is assigned CUID during import. If
the object is imported to the target CMS multiple times, the object is
assigned the same CUID each time.

Merging environments
If you choose the Merge import scenario, the Import Wizard tries to add
objects from the source to the destination CMS without overwriting objects in
the destination environment.
In most cases, the Import Wizard looks for an object with the same path and
name in the CMS repository. If it finds no matching object, the 6.x object is
imported.
If it finds that an object with the same name exists:
• If you have chosen the Rename option, imported like-named objects are
renamed in the CMS. Its children are added under it and not renamed. If
the imported object has the same CUID, the renamed copy is given a
new CUID.
Users and groups cannot be renamed, so import typically fails if duplicate
users/groups exist. Certain other objects are always enforced to use
Update mode, even when Merge is selected (see the following section).
• If you did not choose the Rename option, the import of objects with the
same path and name fails.

Special case
The Import Wizard does not usually combine objects with the same name.
When it tries to locate users and groups in the destination database, however,
it looks for existing objects with the same name as imported objects. If it finds
top-level folders of the same name, it merges them if the Rename option is
not chosen.

BusinessObjects 6.x to XI Release 2 Migration Guide 171

8 Understanding Import Wizard options
The Merge and Update import scenarios

Example: Merge with no Rename

Source environment Destination environment

Before Folder A (CUID=1234, ID=1) Folder A (CUID=6789, ID=3)
import • Rpt A (CUID=2345, ID=2)
After import Folder A (CUID=6789, ID=3)
No change in existing folder
content except following
addition:
• Rpt A (CUID=2345, ID=4)

Updating the destination environment

The Update option applies to the incremental import of objects from a source
to a destination environment.
If you choose the Update option, the Import Wizard compares the CUID of the
imported object with the object CUIDs in the CMS database to determine
whether the object has already been imported.
• If the source object has never been imported, it is given a new CUID and
imported into the CMS repository.
• If a source object has already been imported into the same CMS, and
therefore has the same CUID as an object in the destination
environment, the destination object is updated with the source object’s
parameters.

Rename
In certain Update cases, you should select the Rename option because of
name clashes. For example:
• You update an object. One of the parameters to update is the document’s
name. Unfortunately, another document already has the same name =>
name clash.
• You import an object (there is no other object with the same CUID in the
CMS), but there is another object with a different CUID but with same
name => name clash
If you checked the Rename option, an imported object with the same path
and name as a pre-existing object in the destination CMS, the object import
fails.
Note: Whenever an object (excluding users and groups) is added to the
CMS, even renamed, its children are created beneath it.

172 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
Update the contents/rights of the object
When you import an object more than once from a source to destination
environment, the object may have been modified in the source or destination
environment since the last import.
The following updating options allow you to define in what way you want to
update the same object in the destination environment during incremental
migrations:
• Overwrite object contents
When you reimport an object, it will completely overwrite and replace the
object (and its associated files) that you imported earlier. You can choose
to do this for any or all of the following types of objects:
• Documents (including dashboards and analytics)
• Universes
• Connections
• Overwrite object rights
When you reimport an object, its associated security rights will overwrite
the rights of the object you imported earlier.
Overwrite Object Rights is not selected and cannot be modified if you have
chosen not to migrate security.

BusinessObjects 6.x to XI Release 2 Migration Guide 173

8 Understanding Import Wizard options
The Merge and Update import scenarios

The following table summarizes the effect of checking or unchecking these

options.

Overwrite contents is selected Overwrite contents is

(for any object type) cleared (for all three object
types)
Overwrite object rights is Update the object contents and Import the object’s ACL only.
selected its ACL rights for concurrently- Select principals + objects.
imported principals. Object content will not be
Use this to import objects and modified.
their security, especially if they Use this to overwrite the
have been modified in the objects’ security but not
source deployment other potential object
modifications in the
destination CMS.
Overwrite object rights is Only object content is Neither the object’s content
cleared modified. ACLs are not nor ACL is modified in the
modified. CMS.
Use this to import objects that Use this to reimport a set of
may have been modified in the objects without updating
source deployment, without objects that were already
overwriting destination security imported, but only add the
settings for them. new objects in the source
repository.

Merge vs Update for imported principals

When you are importing principals, the Merge option merges the group
hierarchy of the existing user with the hierarchy of the incoming (source) user.
This means that if a user has parents A and B in 6.x, and has a parent A and
C in the destination system (because the user was imported already and its
group has changed since that time, either in the source or the destination
environment) it will have parents A,B and C in the CMS after the import.
If the Update option is selected (with or without rights fidelity), the existing
user’s hierarchy in the CMS is erased and replaced with the incoming user’s.
In the previous example, the user would only have parents A and B. In other
words, the only parents (other than Everyone) that the imported user will have
in the destination CMS are the parents that were imported at the same time.

174 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
Summary of Merge/Update consequences
The following table summarizes the consequences of choosing a Merge or
Update scenario in conjunction with selecting the Rename option or not.
These scenarios assume that the relevant Update the contents of the
object options (documents, universes, or connections) are selected.
In the Merge scenarios below, the same path case can happen for top level
objects only, because the object will be renamed in the destination CMS, and
so the subfolders belonging to them necessarily won’t have the same path as
in the source environment.
In the examples below, italicized text indicates source objects, either in the
source environment, or after migration to the destination environment.

Import Objects have... Result

scenario
options
Merge Different CUID The source object is added to the CMS, with the same name
No rename Different path/ and CUID.
name For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = (no existing objects Folder A [CUID =
1] from version 6.x 1]
Rpt A [CUID = 2] deployment) Rpt A [CUID = 2]
Merge Same CUID The source object is added to the CMS, with the same name
No rename Different path/ and CUID.
name For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder B Folder A [CUID =
1] [CUID = 1] 3]
Rpt A [CUID = 2] Rpt A [CUID = 2]
Folder B [CUID =
1]
Merge Different CUID For all objects but folders, import of the source object fails.
No rename Same path/name For example:

BusinessObjects 6.x to XI Release 2 Migration Guide 175

8 Understanding Import Wizard options
The Merge and Update import scenarios

Import Objects have... Result

scenario
options
Source Destination pre- Destination post-
import import
Rpt A [CUID = 1] Rpt A [CUID = 2] Same as pre-
import. Rpt A fails
due to name clash.
For folder objects, import succeeds, with incoming objects in
the folder merging into the contents of the same-named
folder in the CMS.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Folder A [CUID =
1] 3] 3]
Rpt A [CUID = 2] Rpt A [CUID = 4] Rpt A [CUID = 4]
Rpt A
[CUID=2]
(Only succeeds if
Rpt A [CUID = 2] is
different object
type than Rpt A
[CUID = 4].)
Merge Same CUID Import of the source object fails because of the duplicate
No rename Same path/name object name.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Same as pre-
1] 1] import. Folder A
Rpt A [CUID = 2] import fails due to
Rpt A [CUID = 2] name clash; Rpt A
fails because
parent import
failed.
Merge Different CUID The source object is added to the CMS, with the same name
rename Different path/ and CUID.
name For example:

176 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
Import Objects have... Result
scenario
options
Source Destination pre- Destination post-
import import
Folder A [CUID = (no existing objects Folder A [CUID =
1] from version 6.x 1]
Rpt A [CUID = 2] deployment) Rpt A [CUID = 2]
Merge Same CUID The source object is imported with the same name and
Rename Different path/ CUID. The object in the CMS repository with the same CUID
name loses its CUID.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder B Folder A [CUID =
1] [CUID = 1] 3]
Rpt A [CUID = 2] Rpt A [CUID = 2]
Folder B [CUID =
1]
Merge Different CUID The source object is added to the CMS repository under a
Rename Same path/name new name and the same CUID. The object in the destination
CMS with the same name retains its name and CUID.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Folder A(2) [CUID
1] 3] = 1]
Rpt A [CUID = 2] Rpt A [CUID = 4] Rpt A [CUID = 2]

Folder A [CUID =
3]
Rpt A [CUID = 4]
Merge Same CUID The source object is imported with a new name and the
Rename Same path/name same CUID. The object in the CMS with the same name and
CUID retains its name and loses its CUID.
For example:

BusinessObjects 6.x to XI Release 2 Migration Guide 177

8 Understanding Import Wizard options
The Merge and Update import scenarios

Import Objects have... Result

scenario
options
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Folder A(2) [CUID
1] 1] = 3]
Rpt A [CUID = 2] Rpt A [CUID = 2] Rpt A [CUID = 4]

Folder A [CUID =
1]
Rpt A [CUID = 2]
Update Different CUID The source object is added to the CMS, with the same name
No rename Different path/ and CUID.
name For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = (no existing objects Folder A [CUID =
1] from version 6.x 1]
Rpt A [CUID = 2] deployment) Rpt A [CUID = 2]
Update Same CUID The source object is added to the CMS, keeping its name
No rename Different path/ and updating the object with the same CUID. Properties that
name don’t exist on the incoming object are preserved.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder B [CUID = Folder A [CUID =
1] 1] 1]
Rpt A [CUID = 2] Rpt A [CUID = 2] Rpt A [CUID = 2]
Update Different CUID The import of the source object fails: folder fails due to name
No rename Same path/name clash; report fails due to parent fail
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Import fails.
1] 4]
Rpt A [CUID = 2] Rpt A [CUID = 3]

178 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
Import Objects have... Result
scenario
options
Update Same CUID In most cases, the source object is added to the CMS,
No rename Same path/name keeping its name and updating the object with the same
CUID. Properties that don’t exist on the incoming object are
preserved.
Other cases however can cause the import to fail. See
“Special cases for updating objects” on page 180.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Folder A [CUID =
1] 1] 1]
Rpt A [CUID = 2] Rpt A [CUID = 2] Rpt A [CUID = 2]
Update Different CUID The source object is added to the CMS, with the same name
Rename Different path/ and CUID.
name For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder B [CUID = Folder A [CUID =
1] 3] 1]
Rpt A [CUID = 2] Rpt A [CUID = 4] Rpt A [CUID = 2]
Folder B [CUID =
3]
Rpt A [CUID = 4]
Update Same CUID The source object is added to the CMS, with the same
Rename Different path/ name, but overwriting the object with the same CUID.
name For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder B [CUID = Folder A [CUID =
1] 1] 1]
Rpt A [CUID = 2] Rpt A [CUID = 2] Rpt A [CUID = 2]
Update Different CUID The source object is added to the CMS under a new name,
Rename Same path/name but keeps the same CUID.
For example:

BusinessObjects 6.x to XI Release 2 Migration Guide 179

8 Understanding Import Wizard options
The Merge and Update import scenarios

Import Objects have... Result

scenario
options
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Folder A[2] [CUID
1] 3] = 1]
Rpt A [CUID = 2] Rpt A [CUID = 4] Rpt A [CUID = 2]
Folder A [CUID =
3]
Rpt A [CUID = 4]
Update Same CUID The source object is added to the CMS under a new name. It
Rename Same path/name updates the object with the same CUID.
Other cases, however, can cause the import to fail. See the
next section.
For example:
Source Destination pre- Destination post-
import import
Folder A [CUID = Folder A [CUID = Folder A [CUID =
1] 1] 1]
Rpt A [CUID = 2] Rpt A [CUID = 2] Rpt A [CUID = 2]

Special cases for updating objects

There are special cases for updating objects in an Update + Rename
scenario.
One is when an object with the same CUID exists, and an object with the
same name but different CUID exists in parent folder of the imported objects.
Since the object with the same CUID as the imported object typically has the
same name and is contained by the same parent, this rare scenario might
occur if:
• You import an object named ObjectA then move it to a different folder
which wasn’t imported. You then create another object called ObjectA in
the folder where the original imported ObjectA object lived. You run
another import, and now have two ObjectA objects, the original one with
the same CUID in some other folder, and the new ObjectZ object in the
original folder, so you get a name clash.

180 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding Import Wizard options
The Merge and Update import scenarios 8
• You import an object called ObjectZ which lives in folder A. You also
import folder B, which is related neither to A nor ObjectZ. After import,
you create a new object ObjectZ in folder B. In the source system, you
move the original ObjectZ object from folder A to B. Now when you
import, the Import Wizard will try to move the ObjectZ in A (which is the
original object and has the same CUID) to folder B, and a name clash
occurs.

BusinessObjects 6.x to XI Release 2 Migration Guide 181

8 Understanding Import Wizard options
The Merge and Update import scenarios

182 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Understanding deployment
configuration migration

chapter
9 Understanding deployment configuration migration
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Understanding what migration entails
D 2. Assessment and planning

• XI R2 deployment rules
• XI R2 deployment rules
3. Preparing for import
4. Importing from the source to destination environment
5. Post-import checking and tuning

XI R2 deployment rules
Rule 1
An XI R2 repository must be connected to at least one CMS.

Why?

184 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding deployment configuration migration
XI R2 deployment rules 9
• The repository is a combination of database schema and the File
Repository Server (FRS). The FRS actually stores the repository content
such as universes and documents, and the database, maintained by the
CMS, contains the InfoObjects describing and pointing to that content.
• Unlike with version 6.x, it is not possible to connect to the repository
directly. All queries to the repository must go through the CMS.
The server itself must be connected to by a web server and an application
server. The web server/application servers are required because security,
users, and scheduling are all managed through the web. There is no longer a
full-client security/administration application like Supervisor.

Rule 2
With XI R2, as with version 6.x, a single server process cannot be connected
to multiple repositories.

BusinessObjects 6.x to XI Release 2 Migration Guide 185

9 Understanding deployment configuration migration
XI R2 deployment rules

Rule 3
Each repository must have its own dedicated server machine, or cluster of
server machines. If you decide to cluster multiple server machines together to
provide more power, the clustering must be Business Objects clustering,
similar to version 6.x.

Unlike version 6.x, an XI R2 repository can only be connected to a single

cluster. Multiple clusters cannot connect to the same repository.

Rule 4
The CMS process is critical to all processes in an XI R2 cluster. All processing
is either initiated or controlled by this process. You can have multiple CMSs
running, but the CMSs must all be running on the same network subnet.
No other processes are restricted by this rule.

186 BusinessObjects 6.x to XI Release 2 Migration Guide

 Understanding deployment configuration migration
XI R2 deployment rules 9

Rule 5
The CMS must be physically located as close to the repository database as
possible, as the amount of interaction between the CMS(s) and the repository
is considerably higher compared to version 6.x.

BusinessObjects 6.x to XI Release 2 Migration Guide 187

9 Understanding deployment configuration migration
Migrating deployment configurations

Rule 6
The File Repository Server (FRS) cannot be geographically distributed. It can
exist in one location only.
Though multiple FRS server processes can be running on different server
machines, connecting to the same file system, only one is active; the others
remain passive, available for failover only.

Migrating deployment configurations

Given the difference in architecture in moving from version 6.x to version XI
R2, migrating from certain 6.x deployment configurations to version XI R2
may require modification and additional administrative steps.
• XI R2 does not support repositories with domains that are geographically
distributed.
• Version XI R2 does not support the use of multiple clusters for a single
repository.

188 BusinessObjects 6.x to XI Release 2 Migration Guide

Migration planning and
assessment
190 BusinessObjects 6.x to XI Release 2 Migration Guide
BusinessObjects 6.x to XI Release 2 Migration Guide

Assessing migration by
product and functionality

chapter
10 Assessing migration by product and functionality
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Understanding what migration entails
D 2. Assessment and planning

• BusinessObjects/Desktop Intelligence
• Web Intelligence
• Designer and universes
• Auditing and Auditor
• Scheduling and publishing
• SDKs
• Application Foundation/performance management
• Web Intelligence OLAP
3. Preparing for import
4. Importing from the source to destination environment
5. Post-import checking and tuning

This chapter describes dimensions of XI R2 migration and their practical

consequences.
Obviously each migration will be a combination of several of these scenarios
(such as BusinessObjects, Web Intelligence, Broadcast Agent Scheduler),
therefore you may need to apply multiple scenarios to match any given
configuration.

192 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
BusinessObjects/Desktop Intelligence 10
BusinessObjects/Desktop Intelligence
Migration involves an update for local BusinessObjects reports, meaning that
you open the report in Desktop Intelligence, and then save it to version XI R2
format, and an Import Wizard import for documents in the repository.
This type of migration requires a side-by-side migration, meaning that both
Desktop Intelligence and BusinessObjects are installed on the same client
machines.

Deployment
2-tier deployments of Desktop Intelligence
For administrators, however, a major deployment difference consists of
having to install a CMS server somewhere on the network. Even for Desktop
deployments, however, you will need a web and application server, as well as
a server to house the CMS somewhere on the network. Unlike in 2-tier
deployments of BusinessObjects, Desktop Intelligence users log in through
the CMS server, via the CORBA protocol.
Here, for example, is a simple source deployment.

This is what the same deployment looks like in the destination environment.

BusinessObjects 6.x to XI Release 2 Migration Guide 193

10 Assessing migration by product and functionality
BusinessObjects/Desktop Intelligence

3-tier deployments of BusinessObjects

Similar to BusinessObjects, Desktop Intelligence calls are still tunnelled
through HTTP.
In XI R2, users cannot download Desktop Intelligence through InfoView, as
they could 3-tier deployments of BusinessObjects in version 6.x. Instead, you
can:
• install Desktop Intelligence manually from a CD
• install from a shared location/directory
• use an install package (like SMS) to automate the install
No .rkey or .key files are required. A <Server Name+.NET or J2EE>.extranet
file is created when the user launches Desktop Intelligence from InfoView.

How Desktop Intelligence differs

Look and feel
Report authors should feel like Desktop Intelligence and BusinessObjects are
the same, except for OLAP data providers and interaction with the platform
(login, send/receive).
Desktop Intelligence documents are displayed differently: version XI R2 has a
new page-by-page HTML viewer, and the ActiveX enhanced report viewer
available in version 6.x is longer available.
You need to redo any portal customization.

Features
• Desktop Intelligence supports Unicode data sources, as well as report
instances and discussions.
• You can set a value that formats a document’s data (ndependently of the
UI’s language). It is this value that is taken into account when calculations
are performed within the document. Each document therefore has its own
locale.
• OLAP data providers are no longer available. You can rebuild those
documents using Crystal Reports, Web Intelligence, or OLAP
Intelligence.

194 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
BusinessObjects/Desktop Intelligence 10
• Many workflows change with Desktop Intelligence:
• All retrieve workflows (from corporate documents, from user, and
from personal documents) are merged into a single Retrieve
workflow.
• You cannot schedule documents from Desktop Intelligence; you use
the CMC. Desktop Intelligence documents you want to schedule or
send to other users must already have been published to the
repository.
• Version 6.x of BusinessObjects cannot connect to an XI R2 repository. If
you want users to be able to connect to both BusinessObjects and
Desktop Intelligence documents, you must have a side-by-side
installation (6.x and XI R2) to connect to both versions of the repository
from XI R2.
• After the import, for Desktop Intelligence documents viewed via InfoView,
report-to-report links need to be updated.
• Documents using Web Connect are not supported.
• You cannot save a Desktop Intelligence document in .bqy format.
• Although you can view and refresh Desktop Intelligence documents
based on stored procedures and imported to Desktop Intelligence, you
cannot edit them.
• You cannot view published Desktop Intelligence documents which have a
read/write password through web-based viewers such as InfoView or
Web Services.
• The following table summarizes Desktop Intelligence support for
processing VBA macros and add-ins:

Macros Add-ins
Client D D
Server D
Potential calculation issues after conversion to new format
Due the changes in the calculation engine over the course of version 5.x to
6.x development, the automatic conversion of BusinessObjects documents to
Desktop Intelligence format during import may in specific cases return
different results than in the original documents. For complete information, see
“Checking for calculation updates” on page 301.

BusinessObjects 6.x to XI Release 2 Migration Guide 195

10 Assessing migration by product and functionality
BusinessObjects/Desktop Intelligence

Unicode implications
Unicode font sizes are different than their non-Unicode equivalents.
Therefore, if you have migrated BusinessObjects documents to Desktop
Intelligence, and have also migrated your 6.x data sources to a Unicode
database, you may encounter the following:
• Documents are not pixel-per-pixel identical.
• When a cell isn’t big enough to display all its contents, it uses “###” to
indicate that the contents have been truncated. Because the Unicode
fonts are sometimes bigger than their non-Unicode equivalents, you may
see ### in cells where previously you saw data.
• The size of documents may be affected.
• Functions like NumberOfPages() may return different values in the case
of Autofit cells. For changes in the calculation engine, see “Checking for
calculation updates” on page 301.
Note: The move to Unicode has no impact on sorts.

Access rights via InfoView

In version 6.x, InfoView was not a formal construct. Security rights for
InfoView are therefore not migrated.
One consequence is that although access rights for BusinessObjects
documents are maintained for the same documents in Desktop Intelligence,
they are not maintained when the documents are accessed via InfoView.
After import, therefore, you must add these rights manually using the CMC.

Compatibility
Repository and server connection
Desktop Intelligence can connect to an XI R2 repository or cluster only.
BusinessObjects cannot connect to an XI R2 repository or cluster.
BusinessObjects 6.x cannot connect to a version XI R2 repository, and cannot
open Desktop Intelligence reports.
Universes
Desktop Intelligence can use any universes imported into, or created in
BusinessObjects Enterprise XI R2. The Import Wizard imports version 6.x
universes, automatically converting them into version XI R2 format.

196 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
BusinessObjects/Desktop Intelligence 10
What does migration involve?
❏ After backing up the source environment and setting up the new XI R2
server environment, install Desktop Intelligence on the same computer(s)
running 6.x versions of BusinessObjects.
Desktop Intelligence cannot access 6.x repositories. If you need to
access a 6.x repository after having installed Desktop Intelligence, you
must access it using your source version of BusinessObjects. To be able
to access both repositories concurrently, you must install Desktop
Intelligence on the same machine as BusinessObjects 6.x (side-by-side
installation). This is recommended in order to compare the two
environments.
❏ Upload all secured local BusinessObjects documents to the repository.
❏ Run the Import Wizard to import all BusinessObjects documents stored in
the repository. They are automatically converted to Desktop Intelligence
XI R2 format and stored in the CMS repository. The Import Wizard
maintains and updates the links between the reports and universes it
migrates, replacing old universe IDs with new ones in the file. Documents
can therefore be refreshed right after migration, whether they contain one
or multiple queries, based on one or multiple universes.
Note: Importing this type of document impacts Import Wizard
performance, as unlike Web Intelligence documents, each
BusinessObjects document must actually be opened during import.
❏ Run the Report conversion tool to convert any required Desktop
Intelligence documents to Web Intelligence format. Business Objects
recommends that you contact your PSO organization to maximize
results.
❏ For BusinessObjects documents stored locally: open existing documents
with BusinessObjects installed on the same machine. Saving a .rep file
with Desktop Intelligence always saves it to XI R2 format.
Open all secured documents in Desktop Intelligence, then save them with
the option Save for all users.
❏ Open each document in both BusinessObjects (in the source
environment) and Desktop Intelligence (in the destination environment)
and compare the two versions for any changes in calculations or
formatting. See “BusinessObjects document migration” on page 302.

BusinessObjects 6.x to XI Release 2 Migration Guide 197

10 Assessing migration by product and functionality
Web Intelligence

❏ If required:
• Re-establish report-to-report hyperlinks.
• Update any VBA macros. Some macros may no longer work
because the platform-related part of the BOSDK object model has
been updated.
❏ Check the rights on the imported documents, using either the CMC or the
Query Builder tool.

Converting Desktop Intelligence documents to Web Intelligence

Moving to a purely web environment can reduce deployment costs. The best
approach to move to the web is to convert some of the Desktop Intelligence
documents you have imported to Web Intelligence using the Report
conversion tool, and to publish other Desktop Intelligence documents to the
web. Typically:
• Documents that require user interaction (drill, sort, filter, calculations,
formatting, etc.) over the web should be converted to Web Intelligence.
• Documents used for enterprise reporting (i.e., that don't require user
interaction) can be published over the web and viewed through the
InfoView portal or some other enterprise portal.
For more information, see “To convert or not to convert (.rep to .wid)” on
page 240.
If you plan to convert Desktop Intelligence documents to Web Intelligence,
Business Objects recommends that you contact your PSO organization to
maximize results.

Web Intelligence
Web Intelligence users and consumers (who view Web Intelligence
documents through a portal such as InfoView) will face two set of changes:
• Portal changes. XI R2 InfoView presents a new look-and-feel. You can
customize it using the BusinessObjects Enterprise SDK.
• Potential Web Intelligence report changes for customers using Web
Intelligence version 2.x
Web Intelligence XI R2 provides a set of new features which give it roughly
the same query and reporting capabilities as BusinessObjects. Here's a
summary of the top new features in XI R2:
• Advanced queries (same as BusinessObjects 6.5)
• Multiple data providers with synchronization

198 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
Designer and universes 10
• Ranking
• Custom sorts
• Formula language (same as BusinessObjects 6.5)
In addition, Web Intelligence provides an unmatched user experience for
report consumers. This includes the ability to drill into reports and to interact
with reports (sort, filter, calculations, formatting, etc.) directly on the HTML
report output.

WQY documents (Web Intelligence version 2.x)

Web Intelligence documents in .wqy format are converted on the fly during
import by the Import Wizard. The converted .wid files are then stored in the
CMS repository.
WID documents (WebIntelligence version 6.x)
You use the Import Wizard to move .wid documents from a version 6
repository to an XI R2 repository.

What does migration involve?

❏ After backing up the source environment and setting up the new
environment, run the Import Wizard to import all Web Intelligence
documents.
❏ Open each document in both Web Intelligence (in the source
environment) and Web Intelligence (in the destination environment), and
compare the two versions for any changes in calculations or formatting.
❏ If required, re-establish report-to-report hyperlinks.
❏ Check the rights on the imported documents, using either the CMC or the
Query Builder tool.

Designer and universes

Migrating the Designer application is a simple update.

BusinessObjects 6.x to XI Release 2 Migration Guide 199

10 Assessing migration by product and functionality
Designer and universes

Universe storage in XI R2
Universe files are stored in the FRS (File Repository Server) as both .unv and
.unw. The difference is transparent to users.
In XI R2, all universe information is contained in the .unv file (except for
universe security, which is separate).

.unw files
.unw files are an internal universe storage format used by Web Intelligence.
These files are stored:
• in the FRS stored in the file system
• in the cache folder used by Web Intelligence
Under no circumstances should you modify or move these files, as it may
cause a universe to become unusable in Web Intelligence.

Creating universe subfolders

In XI R2, you can create subfolders under the main universes folder, allowing
for more fine-tuned management of universes.

Importing universes from a source repository

When the Import Wizard imports universes from the repository, it also
migrates any universe-document or universe-universe links, as well as
universe overloads.

Importing locally-saved universes

You import universes stored on local machines by simply ensuring they are
saved using the Saved for all users option, then opening them with Designer
XI R2. When you save these universes in Designer XI R2, they are saved to
XI R2 format. This does not, however, migrate universe security or links.
• Universes are stored to the new .unw format in the XI R2 FRS for use
with Web Intelligence, but are still saved in .unv format on desktops.
• There is no descending compatibility. Designer 6.x cannot open
universes created with Designer XI R2 due to a file format change (ZIP
vs. OLECF).

200 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
Designer and universes 10
Note: Unlike in previous Business Objects versions, you cannot delete the
repository version of universes and expect to use the locally stored version as
a back up. As the locally stored version is linked to the repository version, the
local version becomes unusable.
For more information on how universes are imported, see “Universes and
universe connections” on page 89.

LOV (List of Values) migration

LOVs in XI R2 are the same as in your source environment. In XI R2:
• BusinessObjects uses both .unv and .lov files (.lov files contain SQL
definitions and LOV data).
• Web Intelligence uses .unw files, which include LOV definitions (SQL
definitions, but no actual data).
When the Import Wizard imports LOVs, both the query definition and the .lov
file are moved. LOVs are not InfoObjects.

Universe security
In XI R2, universe security is composed of:
• ACLs, which define what universe groups/users are allowed to use the
universes
Managed in the CMC via the Universes page, an ACL is created for each
universe folder or each universe.

BusinessObjects 6.x to XI Release 2 Migration Guide 201

10 Assessing migration by product and functionality
Designer and universes

• access restrictions, known as universe access restrictions, are defined

for a particular universe, and consist of:
• Connections
• Controls (query limits)
• SQL
• Object restrictions (hide)
• Row restrictions
• Table mappings
They apply restrictions to users/groups. There is at most one restriction
per user and per group; users inherit restrictions from parent groups.
Access restrictions can be applied to multiple users/groups.
Formerly defined in Supervisor, in XI R2 universe access restrictions are
defined in Designer. After import, access restrictions appear in Designer
when you open a universe.
Access restrictions are created in the CMS and are child objects of a
universe.
Note: For more information about migrating universe access rights, see
“Understanding rights migration” on page 117.

Migrating users with designer rights

If you choose to import security, know that users whose profiles allow them to
run Designer in version 6.x (General Supervisor/Designer/Supervisor-
Designer/Versatile with Designer access) are not by default added to the
Universe Designer Users group.
This group has full control over the Universes folder. To allow imported
universe designers to use the Designer application and manage particular
universes, therefore, you must grant them specific rights through the CMC.

202 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
Auditing and Auditor 10
Auditing and Auditor
In your source deployment, you can audit your cluster’s activity using:
• the Administration Console’s Audit facility, which saves data to a text file
or an Audit database
• the Auditor application that allows you to monitor and analyze user and
system activity for Web Intelligence, InfoView, BusinessObjects in 3-tier
mode, and Broadcast Agent, and then display the results in predefined
BusinessObjects reports known as indicators.

How auditing differs in XI R2

In BusinessObjects Enterprise XI R2, you audit BusinessObjects Enterprise
using the CMC exclusively. The CMC collects audit information from all of the
servers (processes) on the framework (cluster), and then writes it to the BI
Warehouse (audit database).
Unlike in version 6.x, you cannot audit multiple clusters.
Most of the reporting functionality offered by Auditor except Impact Analysis is
provided by a specific universe and two sets of 28 audit reports (Web
Intelligence and Crystal Reports), organized by categories:
• Object Management
• Activity Reporting
• Security Reporting
The reports are generated from the Audit database to report User, Document,
Application and Server event monitoring.
Most Audit reports include report sections, displaying the reported information
grouped or charted in a different manner, such as usage information graphed
by month/week/day, or by server/location. Report sections are displayed in
Web Intelligence as multiple tabs, and in Crystal Reports are packaged as
separate subreports delivered together as a single report. Each of these
report sections is specified separately but together they are delivered in a
single report.
Auditor’s dashboard capabilities have been superseded by the XI R2 InfoView
dashboard capabilities.

BusinessObjects 6.x to XI Release 2 Migration Guide 203

10 Assessing migration by product and functionality
Scheduling and publishing

Scheduling and publishing

In version XI R2, publishing is considered an extension of scheduling.
The CMC and InfoView support basic scheduling capabilities for Crystal
Reports, OLAP Intelligence, Desktop Intelligence, and Web Intelligence
reports, such as scheduled refresh, save, and publishing, prompts, and Save
as Excel. It does not support certain options such as print, then refresh, and
then print.

For Desktop Intelligence jobs

• In XI R2, Conditional processing is not available
• The version 6.x Refresh in the Name Of scheduling option becomes
Refresh on Behalf of.
• In XI R2, scheduling for Desktop Intelligence documents is limited to a
single output. In XI R2, you may need to define multiple jobs where you
had a single job before.
• Report bursting is not supported

VBA macros
In version 6.x, you can embed VBA macros in BusinessObjects documents to
extend the Broadcast Agent Scheduler functionality. In XI R2, VBA add-ins
(.rea files) won't work server side; embedded VBA macros, however, will
continue to work (except for VBA macros that include calls to the platform
such as Login or Logout).
Business Objects therefore recommends that you use VBA macros instead of
VBA add-ins.

For Web Intelligence jobs

Web Intelligence document scheduling jobs can be imported if the job is
supported in XI R2.
There is no File Watcher. There is, however, a service in the framework called
the Event Server that does watch for the creation/modification of arbitrary files
to kick off schedule events.

204 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
Scheduling and publishing 10
Publishing
The functionality provided by Broadcast Agent Publisher is incorporated into
XI R2 and is called publishing. For this release, the key capabilities have
been implemented which will allow many customers to move to this new
release, with the remaining capabilities being added in the following release.
XI R2 has focused on re-engineering Publisher to be an integral part of the
platform, hence it being named publishing, and there are many changes to
existing workflows. For this release, users must re-create their publications in
the destination environment using a combination of InfoView and the CMC:
• InfoView for the publications themselves
• CMC for managing users, groups, and their personalization profiles
Note: You can import users, groups, and profiles from a text file, which
would allow you to transfer this information between Publisher and XI R2.
See the Import Wizard online help for more details for the format of the
text file.

Publishing profiles
Profiles let you personalize the scheduled publication for groups of recipients.
Profiles are defined in the Central Management Console.
Personalization uses the following concepts:
• Profile name—Identifies the name for the personalization to be applied,
such as city or store name. Each user or group can have one or more
profiles defined.
• Profile value—Defines the value of the profile name, such as city = “San
Diego”.
• Profile target—Defines how a profile name applies to a report. Profile
objects can be an object within a universe, a variable within a report, or a
field within a table.

BusinessObjects 6.x to XI Release 2 Migration Guide 205

10 Assessing migration by product and functionality
SDKs

What does migration involve?

• Before importing, documenting and assessing the document scheduling
in your version 6.x deployment
• After the import, recreating some broadcasting using the CMC in XI R2

SDKs
Client SDK
BusinessObjects (renamed Desktop Intelligence SDK) and Designer SDKs
are available in XI R2 and almost unchanged from version 6.5.

Server SDKs
SDKs no longer available in XI R2:
• Web Intelligence SDK
• Administration SDK
• RECOM, as MSFT is replacing COM with .NET
SDKs available in XI R2:
• BusinessObjects Enterprise SDK (Java, .NET, and COM)
• BusinessObjects Enterprise .NET Server Controls
• BusinessObjects Enterprise JavaServer Faces Components
• Report Application Server SDK (Java, .NET, and COM)
• Report viewers SDK (COM, Java)
• Business Objects web services
Documentation and samples are provided to explain how to rewrite an
application based on WICOM or WIBean with RENET or REBean, and with
the BOE SDK.

206 BusinessObjects 6.x to XI Release 2 Migration Guide

 Assessing migration by product and functionality
Application Foundation/performance management 10
Desktop Intelligence SDK
• There are changes to platform-specific calls (Login, Publish, etc.), but the
rest is unchanged.
• VBA macros are carried over during the import of BusinessObjects
documents (they are embedded in the .rep file).
• VBA macros execute correctly on Windows but are ignored on UNIX.

Web Intelligence SDK

• WebIntelligence SDK, Administration SDK and RE COM are superseded
by RE SDK and BOE SDK.
• The REBean and RECOM SDKs are fully supported.

Application Foundation/performance
management
In XI R2, these products are known as performance management.

How performance management differs

With version XI R2, Application Foundation is part of the BusinessObjects
Enterprise platform.

Features
• The analytics displayed in dashboards and scorecards are enhanced to
offer more interactivity and flexibility in display and formatting options.
• New visualization techniques are applied to gauges and charts.
• New metric attributes are available.
• You can add additional metadata about metrics to metrics properties,
providing end users with information about the name of an owner, the last
refresh date, and a metric description. This helps users understand and
identify the source of the information on dashboards and scorecards and
makes it easy for users to take actions that improve business
performance.

BusinessObjects 6.x to XI Release 2 Migration Guide 207

10 Assessing migration by product and functionality
Web Intelligence OLAP

• Instead of entering goals manually, you can now use a universe to import
goals from corporate data sources to populate the values of goals such
as the target or tolerance limits, and then visualize those goals in query-
based analytics such as Interactive Metric Trends (IMT).
• You can build queries that include multiple SQL statements, which allow
you to build powerful queries that match the level of complexity provided
by Web Intelligence, and then visualize results in analytics.
• You can create query-based analytics on universes mapped to OLAP
data sources.
• The workflow for creating new analytics has been simplified.
• Enhanced process tracking includes:
• expanded document attachments to activities to Desktop Intelligence
and OLAP Intelligence
• calling Process Tracker instances via URLs
• Support for activity duration, suggested activity end dates based on
input duration, and enhanced activity date validation
• A variety of Portal Integration Kits is provided.

What does migration involve?

See “Understanding Application Foundation object migration” on page 99.

Web Intelligence OLAP

The migration path for Web Intelligence OLAP users is to recreate their
reports using OLAP Intelligence. Although no migration utility is provided, this
effort is facilitated by the capabilities delivered in OLAP Intelligence, which in
XI R2 represents a superset of Web Intelligence capabilities.
One key technical consideration is to match or reuse the MDX statements
previously generated by Web Intelligence OLAP to achieve certain analyses.
Business Objects recommends getting PSO support if you have large
numbers of this type of document.

208 BusinessObjects 6.x to XI Release 2 Migration Guide

Recreating security in XI R2

chapter
11 Recreating security in XI R2
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Understanding what migration entails
D 2. Assessment and planning

• Designing your security model

• Group security by functionality
• Content security: access to reports and universes
• Security model for functionality and content combined
• Administrators group
3. Preparing for import
4. Importing from the source to destination environment
5. Post-import checking and tuning

This chapter provides guidelines for recreating security in the new

environment, instead of importing it from the source environment.
Note: Creating your security in the new environment is a one-time exercise
that allows you to reap long-term benefits.

Designing your security model

With version 6.x it is good practice to organize security around functionality
and content. With XI R2 this model works even better, due to the availability of
two parents — not available in version 6.x, whose strict tree structure means
that a user can be in multiple groups, but a group can’t have two parents.
Business Objects recommends that you structure your system’s security
around two axes:
• What a user can do
• What content a user can access
The distinction is important, because being able to do something by right,
such as refreshing a document or accessing a universe, is always related to
the content the user has access to.

210 BusinessObjects 6.x to XI Release 2 Migration Guide

 Recreating security in XI R2
Designing your security model 11
A security model should be easy to administer and yet restrictive enough on
both functionality and content so that users cannot do or access things they
should not. You must also ensure that users can see what they are allowed to
see and do what they are allowed to do in the new environment.

Principles for security group design

There are a number of best practices associated with the design of security
group structures.
• Principle of most restrictive: i.e. everything denied, unless explicitly
granted
• Making use of hierarchy in groups and inheritance
• Rolling up profiles of common security levels into parent groups

Security requirements
This chapter takes as an example an organization with four separate
business areas. These business areas do not all share content between
groups, so content used by each group is isolated from each other.
This organization also has five different functional user profiles:
• Universe designers: users with access to the Designer application to
create universes. Practically speaking, these users should also have the
same rights as Report Developers, which makes this profile — even if not
implemented in that way — the most functional of all, apart from
Administrators, who can do everything.
• Report Developers: users who can create documents, whether inside
Web Intelligence to create Web Intelligence ad-hoc reports, or develop
Web Intelligence or Crystal Reports documents for use by other users in
their business area, available through the public folders for their group.
• Power Users: users who can create ad-hoc reports and edit existing ones
for themselves inside Web Intelligence and can share them with others,
but whose reports are not intended or allowed to end up in the public
area.
• Casual Users: users who can view documents and refresh them
• Consumer: users who can only view documents

BusinessObjects 6.x to XI Release 2 Migration Guide 211

11 Recreating security in XI R2
Group security by functionality

Note that not all exact rights and privileges are specified in this list for these
profiles. There are business requirements for additional functionality and
some confusion still exists about some of them, like sending reports to other
users through the system, or via e-mail, FTP or unmanaged (by the
BusinessObjects Enterprise XI R2 environment) disk.
Evaluate these elements of functionality separately for the different groups,
especially where implementation of it has architectural and security
consequences. Make sure therefore that you keep the structure for the
profiles such that you can actually make changes later on without weakening
the security structure.
Note: These profiles or roles are relatively arbitrary. The definitions for
universe and report developers are obvious, but the actual definition of Power
Users, Casual Users or Consumers can be different in different locations, and
even have different names. The point is that you have multiple profiles, which
you will later on combine with a business group.
Separate from these user profiles, you have administrators who administer
the system and fall outside these user profiles.

Group security by functionality

Creating group hierarchies for inheritance
By default, all groups in XI R2 are created on the same level unless you
enforce a hierarchy by making a group a parent, or adding subgroups to an
existing group.
By enforcing or creating a hierarchy, you can use inheritance rules. If you
don’t, although you can easily create a structure that looks good at first, it may
become hard to handle when you add the content, or need to distinguish
between user groups.

Using inheritance and the principle of most-restrictive

You make use of inheritance by creating a general profile, and then splitting it
out again by business area, each still associated with the master profile.
In the diagram below, each profile is set up as a master group, with groups
underneath it created for each business area.

212 BusinessObjects 6.x to XI Release 2 Migration Guide

 Recreating security in XI R2
Group security by functionality 11

Note: The diagrams used in this section list business areas, but they might
also be geographical areas or whatever grouping is most appropriate for your
organization.
These master profile groups cover common functionality into a single profile;
their subgroups tie into a business area (or content or subject area) and
inherit this master profile.
This allows you to make global changes to a profile, overriding it for individual
groups if you need to. For instance, you could think of a profile that by default
doesn't allow for scheduling, but would allow on-demand refresh. Suppose
that the documents in one content area take over 20 minutes to run. In that
case you could subjectively decide that this one group, even though the
master profile doesn't allow it, can schedule documents. That makes this
quite a flexible model.
For example, the top group for all report developers in the environment is the
BO Report Developers group. This group sets the most restrictive settings for
the profile of a report developer: these users are able to create new Web

BusinessObjects 6.x to XI Release 2 Migration Guide 213

11 Recreating security in XI R2
Content security: access to reports and universes

Intelligence and Crystal Reports and edit existing ones, but are not allowed to
publish documents to any public folders outside the development
environment.
Since the groups for report developers within the various business areas
belong to the BO Report Developers group, they inherit all these rights and
privileges and under normal circumstances will not require changes in these
rights. This means you set the main rights and restrictions on functionality
only once for all users.
If, however, report developers in one business area have an important
business requirement for particular types of functionality -- for instance, with
HR needing the ability to save documents away to an FTP location or
unmanaged disk, which according to best practices you should only allow
after an evaluation of security and technological impact -- you can apply this
as an override on the group of HR Report Developers. This change would
only apply to the HR Report Developers, so it makes it easy to grant
additional rights without impacting report developers of other business areas.
This method not only provides flexibility, but allows you to see relatively easily
the specific privileges for an individual group that are different from the
parent, as those would be rights explicitly granted, instead of inherited from
BO Report Developers.

Content security: access to reports and

universes
How inherited rights work in XI R2
In case of the profile groups, you are assuming that all profiles are the same,
and therefore inherit all rights from the parent group. For content areas this
will be a little different, as different groups inheriting from the top group will be
able to do different things to the content that they have access to. It is
therefore good to discuss briefly how XI R2 deals with inherited rights.

214 BusinessObjects 6.x to XI Release 2 Migration Guide

 Recreating security in XI R2
Content security: access to reports and universes 11

In this diagram you see that for each right you have three options. If you set
the right to be Denied on the top group, you cannot override this on lower
levels, so all subgroups will have that right denied. When you grant a right on
a top group (see left branch of the diagram), you can either deny it on a
subgroup, or the right will be granted whether through inheritance or by
setting it more explicitly.
Best practices for security follow the model you see in the right branch of the
diagram. If you use it consistently, it is easy for you to follow the principle of
most-restrictive. On the top level, you either grant a right, or you do not set it.
Since by default a right is denied if it is not specified, this means that for each
child group, you should grant rights that are additional to the most-restrictive
set you granted on the top group.
Note that some of the boxes in the diagram have thicker borders: these are
the paths you should use. That is, you do one of the following:
• deny a right on a top group (which may or may not have subgroups) to
explicitly deny a certain right completely
• grant a right on a parent group, and inherit it — by not specifying it — in
the child group
• do not set the right at the parent, and only grant it if the child group should
have rights, and leave it inherited and not specified when it should not

BusinessObjects 6.x to XI Release 2 Migration Guide 215

11 Recreating security in XI R2
Content security: access to reports and universes

Make full use of the Not Specified option. If you deny something on a high
level, it will always be denied, so only grant rights, and try to not deny unless
you know that it will never be used. Of course, you can change a Denied to
Not Specified, and inheritance should still ensure that if it wasn't explicitly
denied lower down the hierarchy, it will still effectively be denied. But it gets
confusing fast. Grant the least rights you need for any of these profiles, and
then grant explicitly if there are changes or overrides for individual groups.
As a best practice, avoid double grants and double denies. That is, if
something is already granted on a higher level, avoid granting the right again
for a subgroup. If you grant a right to a profile which you later want to revoke
by setting it to Not Specified, if a subgroup has the right granted, still that
group would be able to do it, as the effective right would be set to Granted.
Therefore, following the principle of “least-privilege” or “most-restrictive,” set
the lowest rights on the master profile, and only grant additionally where
needed.
Be careful with Denies. Since a continuous hierarchy of Not Specified leads to
an effective denied, there is no explicit need for setting anything to denied.
Moreover, you would lose the flexibility of changing a master profile and the
change being inherited by the lower groups if the right is denied in the
subgroup. Since you can never grant a right that has been denied in the
parent group, avoid using explicit “denies” in subgroups.

Using business area groups to give access to area-

specific content folders
When it comes to content, implement a model similar to that for functionality,
but now based on a business area. That is, you can build a group structure
that matches up with the business area, and then move all the different profile
groups for that area into its top level.

Now set access to folders for each specific business area at its top level
group, so that it is inherited by all the groups within that business area. In the
example here for Sales, you set the Sales group to have access to the Sales
folder within the <customer name> folder, and no others. Repeat this for each
group, so that each group has its own area that nobody else — but
administrators — is able to see.

216 BusinessObjects 6.x to XI Release 2 Migration Guide

 Recreating security in XI R2
Content security: access to reports and universes 11
Using the principle of most-restrictive and inheritance
Following the above approach locks the system down for access from other
groups, and assigns the folder to those subfolders underneath the main group
for the business area. It also allows you to use the principle of most-restrictive
and inheritance.
Again, try to set the rights on the top group to such an extent that extra rights
are granted explicitly for the subgroups. This means that the rights on the
Sales group for the sales folder should be the same as the lowest common
rights, i.e. the rights and privileges of the Sales Consumers group.
Since this set is the most restrictive, you need to explicitly grant rights to the
other groups within the business area only as per their desired/required
profile. Final Status is the effective right for the user or group for a specific
right or privilege.

Checking group rights on folders

To check the rights any group has on a folder in the CMC, click the link that
corresponds to the folder, then click the folder’s Rights tab. Click the Show
Rights tab, then the name of the group in the Available groups list, then the
Display rights button.
When checking the rights for, say, the HR Casual Users you will be able to
see exactly in the Explicitly column what rights have been explicitly granted to
this group over and above what is allowed within the main Casual Users
group.
When you move a level of functionality up, when you look at power users, you
can see a whole lot more rights explicitly granted.
And finally the universe developers can do almost everything apart from
delete objects and instances.
Note: You can see in this sample that you grant explicitly additional rights for
the groups, different from the master profile, which here is the business area
group. The “granted by inheritance” items come from the business area
profile which sets the most restricted access rights on the business area
folder. The explicitly granted items are rights that this group has over and
above what the base rights are of that business area (i.e. in our example, the
rights that consumers have on the folder. Consumers inherit all their rights,
and no individual grants on the group are set.)

BusinessObjects 6.x to XI Release 2 Migration Guide 217

11 Recreating security in XI R2
Security model for functionality and content combined

Security model for functionality and content

combined
When you combine the two models for functionality and content, each group
has two parents:
• a functionality parent: i.e. BO Report Developers, BO Universe
Designers, BO Power Users, BO Casual Users or BO Consumers
• a content parent, such as Sales, Marketing, Finance, and HR
In the diagram below you see this visualized for the Sales group. The Sales
Report Developers — a child of the BO Report Developers group — also
belongs to the Sales group itself. Similarly, the Sales Universe Designers
belong to both the BO Universe Designers group, as well as the Sales group,
and so forth for all the profile groups. This is not mapping between separate
hierarchy trees for functionality and content, but in fact the exact same group
that has two parents and thus belongs to two hierarchies at the same time,
and will inherit from both. Users only need to be added to the correct business
area specific profile group to inherit the functionality of the master profile, and
the content access of the business area group.

218 BusinessObjects 6.x to XI Release 2 Migration Guide

 Recreating security in XI R2
Administrators group 11
You see the same model for all the other business areas, so that once
implemented, all of the individual profile groups per business area have two
parents: the business area and the functional group.

Checking group membership

In the CMC, by clicking Groups, the name of the group, and then the Member
of tab, you can see the names of all the groups that group belongs to. Two
parent groups should be displayed for each group — apart from the top
groups — they aren’t, the implementation is not correct.)

Summary of benefits
This flexible model makes it easy to grant or deny access to content for an
entire business area, or grant or remove rights to do certain tasks. It allows for
group (or even individual) overrides if you need them, and ensures that users
exist only in a single group, rather than copied into multiple groups as you
would in version 6.x group structures.
If a user needs access to multiple content groups, you can add a separate
group that combines the two content groups and a functionality profile, and
you can inherit from two business area groups and the functionality profile.
You can even have different profiles in the two content areas. In this case you
would pick the highest profile group, and then set the rights on the content as
required.
For example, UserA is a power user in HR, but a report consumer in the
Marketing group. For the HR folder you would then set the rights as for HR
Power Users while setting the rights for the Marketing folder as with
Marketing Consumers.

Administrators group
Entirely separate from this group model, you have an Administrators group.
This group only and exclusively contains system administrators for the
environment, that is, those who configure the servers, perform maintenance
and other system tasks, and are the guardians of the system. These
administrators create users and perform the promotions between
environments. All administrators are IT staff.
Content wise, too, these administrators have access to everything. They have
full rights on the root content folder which contains the Marketing, Sales, HR
and Finance groups.

BusinessObjects 6.x to XI Release 2 Migration Guide 219

11 Recreating security in XI R2
Administrators group

220 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Planning the migration

chapter
12 Planning the migration
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Understanding what migration entails
D 2. Assessment and planning

• Formulating your migration strategy

• Repository migration options
• Migrating to XI R2-supported versions and platforms
• Capturing scheduling information
• What users/groups should you migrate?
• What objects should you migrate?
• Setting up a new folder/group structure
• International considerations
• Cleaning up your source environment
3. Preparing for import
4. Importing from the source to destination environment
5. Post-import checking and tuning

Note: Before planning your migration in detail, Business Objects

recommends that you read all of Part I Migration fundamentals in this guide.

Formulating your migration strategy

The two major decisions impacting your migration strategy are:
• Do you want to migrate all at once, or over time?
• Do you want to migrate security, or recreate security from scratch in the
new environment?

222 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Formulating your migration strategy 12
Choosing your migration method
You can migrate to XI R2 either all at once, or over a period of time.

Single pass
You can migrate to version XI R2 in a single pass with the Import Wizard,
either with or without security.
• Single pass with security
Do a single pass with security if your BI deployment is relatively small,
and you don't want to recreate your security system in the new
environment, or you want to go into production quickly.
Typically, migrating security means you may end up with all documents in
a single folder (assuming you had a single doc domain), which is quick
but far from ideal.
• Single pass without security
Do a single pass without security if you want to recreate security from
scratch (applying best practices etc.) and if you want to migrate all your
groups and applications at the same time, which is unlikely to happen in a
large organization.
Note: Single pass implies moving your XI R2 environment to production
relatively quickly to minimize desynchronized modification of BI content in
source or destination environments. Even after a single pass migration, an
additional period of time is nonetheless required for specific post-migration
procedures, verification of the migrated objects, comparison with the objects
in the source deployment, verification of security, and other adjustments.
There is no such thing as an instant migration.

Incremental
Most migrations are performed gradually, both in the initial, phased import of
BI content, and in the ongoing updating of the destination environment in the
transition period between the final shutdown of the source environment, and
the switch to the destination system.
The initial migration
By importing your source user groups and content into the new environment
gradually, you can validate the import’s success after each pass with the
Import Wizard; if there are issues, you don’t have to begin the entire migration
all over again.

BusinessObjects 6.x to XI Release 2 Migration Guide 223

12 Planning the migration
Formulating your migration strategy

How you structure you migration’s phases can depend on the structure of
your repository or the logical groupings of user groups and resources.
Business Objects recommends using Supervisor to help you analyze your
repository for logical groupings that help speed and ease migration.
You might decide, for example to migrate incrementally by:
• department
Your repository may reflect your organization’s structure, with separate
universe and document domains for specific departments, such as sales,
HR, or marketing. Migrating this way allows you to treat each
department’s import as a separate project that you can test and fine-tune
in the new environment.
• application (by resource type)
Importing by resource type allows you to concentrate on a specific type of
import at a time and limit use of the deployment to specific applications in
the new environment in each stage.
• domain
Importing universe and document domains separately allows the Import
Wizard to perform a single type of import at a time. As documents and
universes are organized by domains, and all the objects in a domain are
migrated to the same folder in the CMS database, domains represent
natural sets of objects within the migration process.
This type of import is also logical given that different domains may be
linked to different databases, or located in different places. Authorization
may also differ from one domain to another.
• locale
In some cases, the locales used in BusinessObjects and Web
Intelligence documents may not be stored in the document definitions. As
XI R2 documents require a locale, when you import documents, the
Import Wizard allows you to choose a default locale for the entire set of
documents you are importing. Importing sets of documents which use the
same locale can therefore streamline the migration process by getting
locales right immediately.
Ongoing updates
For most migration scenarios, safe migration requires a certain period of time,
during which the imported content can be tested, fine-tuned and verified,
often using staging areas and BIAR files for moving the content from the
testing environment to production. The final environment will undoubtedly
need adjusting for your organization’s particular requirements, security
testing, and rollout.

224 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Formulating your migration strategy 12
In most circumstances, therefore, you will be performing ongoing updates on
your destination environment as your source environment continues to
evolve.
The Import Wizard provides a number of incremental update options to give
you more control over precisely what you migrate when you import objects
more than once from the source to the destination repository:
• Overwrite object contents
When you reimport an object, it will completely overwrite and replace the
object (and its associated files) that you imported earlier. You can choose
to do this for any or all of the following types of objects:
• Documents
• Universes
• Connections
• Overwrite object rights
When you reimport an object, its associated security rights will overwrite
the rights of the object you imported earlier.
If you decided not to import security in the Security Migration Options
dialog box, then the Overwrite object rights option is not relevant, and is
therefore not available.
If you don’t select any overwrite options, the object in the destination
repository will not change when you try to import it again.
For more detailed information, see “Understanding Import Wizard options” on
page 165.

Importing security or not

Migrating from one system to the other is an opportunity to review the existing
security structure in the source environment with a view to benefiting
optimally from the more secure framework provided in XI R2.
The following chapters should allow you to appreciate just how different the
6.x and XI R2 frameworks are.
• “Understanding user and group migration” on page 65
• “Understanding object migration” on page 81
• “Understanding rights migration” on page 117
• “Understanding Application Foundation object migration” on page 99

BusinessObjects 6.x to XI Release 2 Migration Guide 225

12 Planning the migration
Formulating your migration strategy

Although you can import version 6.x rights to XI R2 and obtain the same
effective rights in XI R2, because of the difference in security models,
subsequent modifications to rights can have unforeseen consequences.
If you do not have a small deployment, Business Objects recommends
rebuilding your environment’s security from scratch in version XI R2’s
superior security structure.
One of the major advantages of version XI R2 is its flexible and granular
security structure based on ACLs, a common IT standard. These ACLs
encompass what in version 6.x environments are known as security
commands, profiles, document access, and delegated administration.
In version 6.x, you can use security commands to restrict user and group
access to functionalities in Business Objects products.You cannot restrict
access at the object level. For example, if you grant a group the right to
refresh, but not create documents, the restriction will apply regardless of the
documents being used.
In XI R2, the use of ACLs means that imposition of restrictions is much more
granular. You can apply user, group, and role level security at the object level,
to documents, categories, folders, universes, connections, applications, and
even servers and groups of servers.
All hierarchies are based on inheritance:
• Folder hierarchies include “root” folders, and their cascading subfolders,
and continue down through the objects each folder contains.
• Group hierarchies include root groups and their cascading groups.
Common rules are used to compute aggregation and inheritance for these
hierarchies.
The resulting granularity means, for example, that you can allow a group to
refresh document A, but not refresh document B.
See “Security migration options” on page 166 for the Import Wizard options
you can use to migrate your BI deployment without bringing security over with
it.
If you decide to recreate your security in the new environment, see
“Recreating security in XI R2” on page 209 for guidelines.

Overall security recommendations after import

Once you have imported your objects into the destination environment using
the Import Wizard, Business Objects recommends that you start configuring
security by doing the following:

226 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
High-level migration strategy scenarios 12
1. Set the default access level at the global level (all users) to No Access.
Then grant specific access to the appropriate groups for specific folders.
This is the most efficient way of restricting access to only the designated
users.
2. Assign security at the folder level to groups whenever possible. Avoid
setting rights for specific users on specific objects. This reduces the
complexity of your security model.
3. Use predefined access levels whenever possible. Avoid setting advanced
rights. This reduces the complexity of your security model.
The XI R2 security model is a combination of application and object rights. To
develop a model that supports customization of rights, consider defining
functional groups for which you grant advanced object and application rights.

High-level migration strategy scenarios

To understand the implications of each of the Import Wizard options
mentioned in this table, read “Understanding Import Wizard options” on
page 165

Single pass Incremental

Security • In the Import Wizard’s Choose • With each pass with the Import
migrated objects to import dialog box, Wizard, select the users and/or
select all source objects objects you want to import.
including users and groups, • Select the first or second option
domains, documents, universes in the Security Migration Options
and connections, and categories. dialog box, indicating that you
• In the Security Migration Options want to migrate security.
dialog box, select the first or • The Update migration scenario is
second option, indicating that automatically selected for you.
you want to migrate security.
• In the Incremental import dialog
• It doesn’t matter whether you box, select whether you want
choose Update or Merge as imported objects to overwrite the
migration scenario. content of instances already
• If you chose Update, it doesn’t imported into XI R2, and/or the
matter what you select in the rights for those objects. Select
Incremental Import dialog box. (If the types of objects you want.
you chose Merge, this dialog box This imports selected objects into the
doesn’t appear.) and content into the XI R2
This imports all your source users environment; the same approximate
and content into the XI R2 effective security is retained in the
environment, along with the same destination environment.
approximate effective security.

BusinessObjects 6.x to XI Release 2 Migration Guide 227

12 Planning the migration
Repository migration options

Single pass Incremental

Security not • In the Import Wizard’s Choose • With each pass with the Import
migrated objects to import dialog box, Wizard, select the users and/or
select all source objects objects you want to import in the
including users and groups, Import Wizard’s Choose objects
domains, documents, universes to import dialog box.
and connections, and categories. • Select the third option in the
• Select the third option in the Security Migration Options dialog
Security Migration Options dialog box, which specifies you don’t
box, which specifies you don’t want to migrate security.
want to migrate security. • Choose Update as your
• It doesn’t matter whether you migration scenario.
choose Merge or Update as • In the Incremental Import dialog
migration scenario. box, choose to overwrite objects’
• If you chose Update, it doesn’t content. Select the objects you
matter whether you choose to want. The option to overwrite
overwrite objects’ content. The objects’ rights is greyed out.
option to overwrite objects’ rights This imports selected objects into the
is greyed out. XI R2 environment without any
This imports all your source users security.
and content into the XI R2
environment without any security.

Repository migration options

Before you migrate to XI R2 you need to decide if you want to merge your
existing source repositories. You must also determine whether you need
multiple repositories even if you did not in version 6.x.

Merging multiple repositories into one

In your version 6.x deployment, you may have multiple repositories or
security domains. As the reason for multiple repositories may no longer be
valid in XI R2, migration may provide an opportunity to merge existing
repositories into one.

228 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Repository migration options 12
With version 6.x you may have had to support distinct repositories for:
• managing complex security profiles
In XI R2 a user can have a complex security profile. For example a user
can view and refresh some documents, and just view others. This isn't
possible in version 6.x.
• using different authentication/authorization schemes. (Not applicable for
all versions).
In XI R2 it is possible to set up different authentication schemes in which
some users are able to use repository authentication, while others use
Basic or an LDAP authentication. This isn't possible in version 6.x unless
you use different web applications, one for each authentication scheme.
If either of these reasons applies, then you may be able to merge your
repositories into one.

Merging repositories with the same ID

If the source repositories you want to merge in XI R2 have different IDs,
simply use the Import Wizard with the Merge option.
If any two of the source repositories have identical IDs (often the case when a
repository has been copied for an updated version of the Business Objects
suite), however, the Import Wizard may not be able to distinguish between
objects coming from one repository or the other.
This is an issue if you are migrating security, because this migrates
application rights. When you migrate application rights, you migrate
supervisors. And when a user who was a supervisor in version 6.x is created
in the XI R2 repository, to determine which group(s) the user is allowed to
administer, the Import Wizard assigns the user to the group(s) that the original
user had administration rights over. This assignment is based on the ID
number of the source 6.x group(s). If the two repositories have the same
repository ID and share the same group IDs, then this assignment will be
incorrect.
In this case it is therefore good practice to consolidate the repositories into a
single one before migrating to version XI R2.
Determining a repository’s ID
You can determine a repository’s ID by running this SQL against the
repository database:
SELECT M_GENPAR_C_LABEL
FROM OBJ_M_GENPAR
WHERE M_GENPAR_N_ID=121

BusinessObjects 6.x to XI Release 2 Migration Guide 229

12 Planning the migration
Repository migration options

Note: Never change the repository ID. Any modification could lead to a
number of unwanted side effects that could stop your system from working.

Moving from one to multiple repositories in XI R2

There may be different reasons to split a repository into many distinct,
separate repositories under XI R2, than you've seen for version 6.x. In XI R2
you may need a separate, distinct, repository for:
• Different life-cycle phases
• Distributed deployments
Both of these are discussed in the next two sub-sections.

Different life-cycle phases

Before you can determine your migration path, remember how the Import
Wizard works when promoting content from one XI R2 repository to another
XI R2 repository (see “The Merge and Update import scenarios” on page 169
for detailed information).
The Import Wizard offers two import scenarios:
• The Merge scenario adds objects.
There is an option to rename if the object name clashes, if this option is
not selected, then the new object is not created. If there is a name clash,
then a new parent folder is created and the object is created in this new
folder.
• The Update scenario adds and/or updates objects.
This works by comparing objects by Cluster Unique Identifiers (CUIDs). If
the CUID already exists, then the object is updated. If the CUID does not
exist, then a new object is created.
There is also an option to rename if the object name clashes.
• If the CUID matches but there is already an object of the same name,
the new object will only be created, with a new name, if the rename
option is selected.
• Should the CUID not match, the object will only be created if there is
no name clash, unless the rename option is selected, in which case
the object is created but with a new name.

230 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Repository migration options 12
Using the Update scenarios for life-cycle management
The Merge scenario does not replace existing objects, it only adds new
objects. To use the Merge scenario for promoting content from one life cycle
phase to another would therefore require that you delete all the target objects
first, or alternatively perform the merge, and then remove duplicated objects.
The Update scenario replaces existing objects, ideal for promoting content
from one life cycle phase to another. It also allows you to change the names
of objects.
For example, you may have an object in the Prod environment called
Customer Satisfaction v1 document. You can then develop an updated
version to this called Customer Satisfaction v2 document in your Dev
environment. If you are able to promote this object from Dev to Test, then Test
to Prod, the Prod object will not only be updated, but its name will change to
Customer Satisfaction v2 document. Quite an advantage over version 6.x.
To make it possible to promote objects using the Update scenario, you must
make sure that all your objects share CUIDs across all environments.

The diagram above shows two objects:

• Sales Document
• Marketing Document
All three instances of each document share the same CUID across all three
repositories. Because the CUIDs are the same across all environments, this
deployment can use the Update scenario to promote content from one
environment to another.

BusinessObjects 6.x to XI Release 2 Migration Guide 231

12 Planning the migration
Repository migration options

To arrive at this situation, you must follow one of two workflows depending on
whether you deployed your version 6.x system:
• within a single repository: if this is the case there are other important
considerations to be considered
• using separate repositories for each life-cycle phase
Support for separate, distinct repositories for each life-cycle phase in XI R2 is
considerably superior to version 6.x. The Import Wizard is designed to move
content from one repository to another. When using the Import Wizard you
specify which content (documents, universes, connections, users, etc.) you
want to import. The Import Wizard can then either directly load that content
into a target repository, or it can store the selected content into a BIAR file
(Business Intelligence Application Resource). A BIAR file is like a .zip file,
which can be passed around and loaded into a target repository later on. The
file can also be re-applied. One of its advantages is that, should you want to
roll-back, you can simply re-apply your original BIAR file.
For more information on BIAR files, see the Import Wizard online help.
Different life-cycle phases within a single repository
The Update scenario is only available when you use separate, distinct
repositories for each life-cycle phase. If you decide you want to manage
different life-cycle phases within one repository, you will not be able to take
advantage of the benefits of using the Update scenario.
In version 6.x, you can manage different life-cycle phases such as
Development, Test, and Production within a single repository by creating
many different document/universe domains.
With this type of deployment you have the option to:
• use different hardware for each life-cycle phase
• use a different installation of the Business Objects software for each life-
cycle phase. This means you can test a Service Pack or a Hot Fix in
isolation from your production environment.
With XI R2 you no longer have these options. You can still manage all your
different life-cycle phases within one repository, however. One repository
directly implies the same cluster, the same hardware and the same software
version (rules 1 and 3).

232 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Repository migration options 12
To implement this in XI R2, you must create a normal object folder structure
and a universe folder structure for each life-cycle phase. Make sure that only
your production users can see the production folder structures and your
development users can only see the development folder structures etc. You
can then simply move or copy documents and universes from one folder
structure to another when you want to promote from one life-cycle phase to
another. You should create “migration” users that have access to multiple life-
cycle phase folder structures so these users have permissions to copy or
move content.
It is important that your 'normal’ users only have access to one life-cycle
phase folder structure, otherwise documents built on universes will not be
refreshable. This is because of 'run-time rebinding'. A universe data provider,
within a document, is 'binded' to a universe by means of the universe
identifier. The universe identifier is unique within the repository. If at run-time
the universe is not available, because the universe is no longer present or the
user does not have access to it, then it will search for other universes of the
same short filename. As long as only one other universe is found, then the
data provider will automatically re-bind itself to that universe before refreshing
the document. If multiple universes are found, the document will not refresh .
If you manage all your life-cycle phases within one repository, as described
above, it is quite typical for some users to be denied access to certain
connections, but granted access to others. When a universe is promoted from
one life-cycle phase folder structure into another, the universe will point to a
connection that the users may not have access to. Manual intervention will be
required to correct this so that the universe points to the correct connection.

BusinessObjects 6.x to XI Release 2 Migration Guide 233

12 Planning the migration
Repository migration options

Business Objects recommends separate, distinct repositories for each life-

cycle phase. To migrate to this structure from a source environment in which
all life-cycle phases were managed within a single repository, you must take
the following steps.

Note: The diagram uses the term “XI R2 repository” to represent both the
repository and the FRS.
1. Migrate users, documents, universes, connections, and so on from your
source repository to your new Development XI R2 repository. Migrate
only content from your security domain and your production universe and
document domains -- not from your Development and Test domains.
2. Copy all the content from your Development XI R2 repository to Test XI
R2 repository.
3. Copy all the content from Test to Production.
The CUID of an object in one repository will now have the same CUID as its
corresponding objects in the other repositories.

234 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Repository migration options 12

This process implies that all development and test work has been promoted
to production, since these domains are not migrated.

BusinessObjects 6.x to XI Release 2 Migration Guide 235

12 Planning the migration
Repository migration options

Separate repositories for each life-cycle phase

To migrate your source deployment to XI R2 which will enable you to use the
Update scenario you must take the following steps.

1. Migrate all users and content from your Production source repository to
your new Development XI R2 repository. Do not migrate content from
your Development and Test repositories.
2. Copy all the content from your Development XI R2 repository to Test XI
R2 repository.
3. Copy all the content from Test XI R2 to Production XI R2.
The CUID for an object in one repository will now have the same CUID as its
corresponding objects in the other repositories.

236 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Migrating to XI R2-supported versions and platforms 12

If you do not follow this workflow, but decide to migrate each repository to an
XI R2 repository, then each object will have a CUID that is not shared across
the other repositories. You will not benefit from the Update scenario features
mentioned above, and will only be able to use the Merge scenario.
This process implies that all development and test work has been promoted
to production, since these domains are not migrated.

Migrating to XI R2-supported versions and

platforms
Before beginning migration, you must evaluate which platform and version
changes you will need to implement as you move from your source to
destination environment. These factors include supported databases, web
and application servers, web browsers, and operating systems.
In this context, the term upgrading means moving to a newer version of the
same software, such as from IIS 5.0 to IIS 6.0. Migrating, on the other hand,
means moving to a different brand of software completely, such as from
Tomcat to WebLogic.
Note: For a constantly updated list of supported platforms and versions, see:
http://support.businessobjects.com/supported_platforms_xi_release2/

Changing repository databases

The Import Wizard seamlessly migrates your BI content from any supported
version 6.x database to any supported XI R2 database.

BusinessObjects 6.x to XI Release 2 Migration Guide 237

12 Planning the migration
Capturing scheduling information

Changing query databases

You must migrate any data from databases that are not supported for XI R2 to
supported platforms. If you do not, universes based on those databases will
not work.

Capturing scheduling information

If you are planning to schedule documents for batch processing in the new
environment, you need to record scheduling information from the source
system prior to the import because the Import Wizard does not import all jobs
from version 6.x. You may need to recreate some schedules in the XI R2
environment.
You can use the Broadcast Agent Console to capture detailed information
about the documents you have scheduled in your version 6.x deployment,
including the type of document (BusinessObjects or Web Intelligence), its
size, location, and scheduling duration and intervals. For a full list, see the
Broadcast Agent Administrator’s Guide.
From the Console you can export the list of scheduling tasks in .CSV (Comma
Separated Value) format, which makes the list printable and viewable from a
standard text editor.
You can also use Auditor to analyze information concerning Broadcast Agent
usage, such as jobs per user, Broadcast Agent, and frequency. For more
information, see the version 6.x BusinessObjects Auditor Guide.

What users/groups should you migrate?

Migrating to a new system in which users and groups are organized
differently, and security is based on completely different rights inheritance and
aggregation models gives you the opportunity to rethink your current security
system. Instead of trying to superimpose your current user/group security
framework on the new framework, Business Objects recommends that you
assess, before import, how you can best take advantage of the reinforced
security and granularity provided by BusinessObjects Enterprise XI R2.
Before migration, remove useless users and groups. Auditor can help you
assess this. Its predefined indicators let you check for the last time users
logged in, for example, or for users who have never logged in. The User
Information Detail indicator tells you what users are in each group.

238 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
What objects should you migrate? 12
This is also the moment to reorganize users and groups into more functional
groupings, and review delegated administration.

What objects should you migrate?

You should only migrate universes, documents, and categories still useful for
your organization. Business Objects recommends you use BusinessObjects
Auditor to monitor and analyze which documents and universes are used,
and with what frequency.
Auditor comes with a set of pre-defined indicators, each one of which
contains one or more BusinessObjects reports focussing on a specific area of
analysis. These indicators can help you pinpoint those documents and
universes (and even universe objects) which are rarely or no longer used.

BusinessObjects documents
For each BusinessObjects document in the source environment, you have
four migration options:
• Declare the document obsolete and either leave it in the source
environment or delete it altogether.
• Import the document, then re-use it in the new Desktop Intelligence
format.
• Import the document, and then convert it to Web Intelligence format using
the Report conversion tool.
• Rewrite the document in the new environment using Crystal Reports.

Have some documents become obsolete?

Business Objects suggests you use BusinessObjects Auditor to monitor
which documents have become obsolete in your version 6.x deployment.
For example, you can use the pre-defined indicators 10 Least Read Reports
or Document Usage.
One option is to move all the obsolete documents into a specific category
then not select that category when running the Import Wizard.

BusinessObjects 6.x to XI Release 2 Migration Guide 239

12 Planning the migration
What objects should you migrate?

To convert or not to convert (.rep to .wid)

By converting BusinessObjects documents to Web Intelligence format you
can benefit from interactivity over the web in a zero-footprint environment.
This also reduces the size of the document.
Business Objects recommends you not convert BusinessObjects documents
to Web Intelligence format when the documents use:
• One or multiple VBA macros
• Non-universe data providers
• The Show/Hide object feature
• Conditional formatting
Business Objects recommends conversion when:
• The above features are rarely used.
• You require a strictly web deployment.
• Users need interaction with reports.

To rewrite or not to rewrite (.rep to .rpt)

Business Objects recommends you not import certain BusinessObjects
documents, but instead rewrite them directly in Crystal Reports XI R2 when
these documents:
• served an enterprise reporting purpose in the first place
• have sophisticated formatting requirements
For more information, see the Crystal Reports XI R2 User’s Guide.

Enterprise reports
The scenario is typically the following:
• A group of IT experts centralizes users requests and creates reports to
address users’ needs.
• The documents are pushed to a large number of report consumers
through the InfoView portal.
In this type of scenario, it may be better to use Crystal Reports to author the
reports. Crystal Reports provides better scalability and on a large scale, is a
better solution for enterprise reporting.

240 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Setting up a new folder/group structure 12
Highly formatted reports
Crystal Reports may also be a better choice when users require:
• Pixel-perfect quality reports
• Printable reports
• Highly formatted reports
• Financial reports
• Regulatory/legal reports

Setting up a new folder/group structure

To prevent security breaches, you will need to create a new folder and group
structure in the destination environment, and then move documents into the
folders, and users into the groups, before any users begin to use the system.
In version 6.x, you publish documents to a group (this secures the document
so that no one outside that group can see it) and to a document domain (the
container). In version XI R2, you publish to a folder (the container) only; you
do not specify security at that time.
In terms of migration, this difference is exposed in the following manner:
• When you import security, the rights imported on the objects are correct,
regardless of the folder they’re in — and so they make sure that the right
users see the right objects.
• When new objects are published to the folder from XI R2, however, they
inherit the rights of the folder. Anyone having access to the domain folder,
therefore, will have access to all the documents within it, unless the rights
for specific document objects, defined in the CMC, prohibit it.
Instead of having an administrator define specific rights on each document
each time it is published, you must set up a coherent folder and group
structure that will manage access to published documents through
inheritance.

BusinessObjects 6.x to XI Release 2 Migration Guide 241

12 Planning the migration
Setting up a new folder/group structure

You can do this before or after the import, but the structure must be in place
before users begin using the system.
If you don’t import security, you will need to create your new security system
in XI R2 before system use. For detailed information, see “Recreating security
in XI R2” on page 209.
Setting up an adequate initial folder/group structure in the destination
repository involves:
• Creating a new document folder structure in the destination repository
• Creating a new group structure based on role in the destination
repository
• Implementing the relationships between the two

Creating a new document folder structure

Your destination document folder structure should mirror your source group
structure.

242 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Setting up a new folder/group structure 12
• If the document domains in the source repository are generally mapped
one-to-one to a specific user group (only one group has the right to
access the documents in a specific domain), your task is relatively
simple: for each of the groups in the source repository, simply create a
document folder for each group beneath the Public folder.

From the version 6.x groups... ...create these document folders

beneath the pre-existing Public
folder.

• If the source repository is not structured according to clear group-

document domain relationships, then you will need to determine how best
to structure the destination folder system in order to group documents to
be accessed by a single group only.

BusinessObjects 6.x to XI Release 2 Migration Guide 243

12 Planning the migration
Setting up a new folder/group structure

Once you have created your new folder structure, and after you have
imported your documents into their destination domain folders, you copy (do
not move) the documents into the appropriate folders in the new folder
structure.

In the end, all the documents in a given folder should be available to a

specific group.

If documents are shared by multiple groups

You have two options for structuring documents accessed by more than one
group:
• Option 1: You can copy the document into the folder corresponding to
each group with access to the document.

Advantage Disadvantage
You don’t have to create shared You may end up with lots of copies
folders. of documents that may need
maintaining.

• Option 2: For documents being shared by the same groups, you can
create shared folders.

Advantage Disadvantage
You have only one instance of a You must create stored folders,
shared document to manage. which requires the proper analysis
up front.

244 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Setting up a new folder/group structure 12
Creating a new group structure based on role
Now create a new group structure in the destination repository which groups
users not by their business or geographical area (as in the diagrams above),
but by the common sets of rights they are granted on documents.
For example, in version 6.x, the Sales group uses the documents in the
repository’s Sales domain. Not everyone in the Sales group has the same
rights on the objects in that domain: some people can create documents,
some can edit them, others can only view or refresh documents.
For example:
• Power users
• Schedule documents
• Edit documents
• Publish documents
• Refresh documents

BusinessObjects 6.x to XI Release 2 Migration Guide 245

12 Planning the migration
International considerations

Note: The following table sums up the main actions users can take on
documents, as well as the mechanisms which enforce rights to these actions
in version 6.x, and in version XI R2.

Document actions Version 6.x Version XI R2

View Object right Object right
Refresh Security command (application right) Object right
Create Security command (application right) Application right
Edit Security command (application right) Object right
Publish Security command (application right) Object right

Implementing the relationships between the two

Now give access rights to specific document folders to the appropriate role
groups, so that your users can do the right things on the objects within those
folders.
Once this is done, whenever a document is published to a folder, the correct
users automatically have the correct rights to that document, and all the
documents in the folder.

International considerations
Specifying document locales for import
In the 6.x repository, some .wqy and .rep (as well as associated .rea and .ret
files) documents may not store their locale. To set the locales in these
documents when they are saved in the CMS after their conversion into XI R2
format, the Import Wizard asks for default locales:
• the document’s locale
• the locale of the machine used to create the document
Locale format is: language iso-639(lower case) + "_" + country iso-3166
(upper case). For example: en_US.

246 BusinessObjects 6.x to XI Release 2 Migration Guide

 Planning the migration
Cleaning up your source environment 12
Once you select these locales, they are stored in the document itself when it
is imported to the CMS.
• These default locales apply to all documents without locales in the
current import.
• Applying wrong locales to a document may “corrupt” it (date, currency…
incorrectly displayed)
If the repository contains documents with different locales, it is best practice to
run the import by steps, one step for each document language, in order to
avoid setting a default English locale to a Japanese document for example.

Cleaning up your source environment

When documents are removed from the 6.x repository by importing them into
the destination environment, they are logically but not physically deleted.
To physically delete documents that have already been deleted logically, you
should use Supervisor’s Compact action on each document domain (Tools >
Repository > Scan).
Even before importing, it is a good practice to perform a Repair and Compact,
which checks the repository domains for structural and consistency errors,
and deletes useless documents.
Be aware that a Repair and Compact can be a time-consuming procedure.

BusinessObjects 6.x to XI Release 2 Migration Guide 247

12 Planning the migration
Cleaning up your source environment

248 BusinessObjects 6.x to XI Release 2 Migration Guide

Importing to the destination
environment
250 BusinessObjects 6.x to XI Release 2 Migration Guide
BusinessObjects 6.x to XI Release 2 Migration Guide

Before using the Import

Wizard

chapter
13 Before using the Import Wizard
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The phases in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Understanding what migration entails
2. Assessment and planning

D 3. Preparing for import

• Before installing XI R2
• Installing XI R2
• Before importing
4. Importing from the source to destination environment
5. Post-import checking and tuning

Before installing XI R2
Before installing version XI R2, prepare your system by:
• Running a Repair and Compact on your source repository
• Backing up your source repository
• Exporting locally stored objects
• Updating platforms and versions if required
• Creating data sources on destination machines for all domains in source
deployment

Running a Repair and Compact on your source

repository
Use Supervisor to check the integrity of your source repository’s security and
document domains by scanning domains for structural and consistency
errors, as well as physically delete documents that have been logically but not
physically deleted.
To do this, click Tools > Repository > Scan.

252 BusinessObjects 6.x to XI Release 2 Migration Guide

 Before using the Import Wizard
Before installing XI R2 13
Be aware that a Repair and Compact can be a time-consuming procedure.

Backing up your source repository

Business Objects strongly recommends backing up your 6.x source
repository before beginning the migration.
In addition, it is good practice to run the Import Wizard on a copy of the
source repository, and not on the production version. If you follow this
practice, make sure that you point all the domains to the copied repository, so
that the domains are no longer associated with the original (production)
repository.

Exporting locally stored objects

Objects that you are planning to import to the destination environment using
the Import Wizard must reside in the version 6.x repository.
If objects are stored locally on users’ computers, you must make sure the
users export the objects to the repository before you begin the import.
Tip: Create a specific category to store local content.

Updating platforms and versions if required

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

Recreating required connectivities

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

BusinessObjects 6.x to XI Release 2 Migration Guide 253

13 Before using the Import Wizard
Installing XI R2

Migrating query databases

All data access is kept from version 6.x. Connection Server is an integral part
of BusinessObjects Enterprise XI R2, and all the databases it supported in
version 6.x continue to be supported in the new environment. Check the list of
supported platforms at http://support.businessobjects.com/
supported_platforms_xi_release2/, however, for the specifically supported
driver versions.
If you do not migrate data in unsupported database platforms to a supported
platform, universes based on them will not work in the destination
environment.

ONAMES on Oracle
The Import Wizard does not support Oracle systems that use ONAMES
naming servers. You must use TNSNAMES instead.

Creating data sources on destination machines for all

domains in source deployment
Create data sources on each destination server machine for every repository
domain in the source deployment. The name and configuration details for the
data sources must match the data sources in the source deployment.
Certain databases that can host a version 6.x repository are not supported for
an XI R2 repository. For the latest information, see the list of supported
platforms at:
http://support.businessobjects.com/supported_platforms_xi_release2/

Installing XI R2
For complete instructions for installing BusinessObjects Enterprise XI R2, see
the BusinessObjects Enterprise Installation Guide.
❏ Install at least one CMS.
❏ Install Desktop Intelligence on client machines.
❏ Install the Import Wizard on a Windows machine.

254 BusinessObjects 6.x to XI Release 2 Migration Guide

 Before using the Import Wizard
Installing XI R2 13
Where should I install the Import Wizard?
If you are using Windows server machines, the Import Wizard is installed on
the BusinessObjects Enterprise XI R2 server machine by default. This speeds
up the Import Wizard’s connection to the CMS and the File Repository
Servers.
You can install the Import Wizard using a Custom install, either on a
standalone Windows machine, or even on an existing version 6.x Windows
server.
• If you install it on a standalone machine, the import process will not
interfere with server processing in either the source or destination
deployments.
• If you install it on a version 6.x machine, communication is faster with the
source repository and cluster.
Both of these Custom options result in more CORBA traffic with the CMS. You
must also make sure that any firewalls between the Import Wizard machine
and the CMS machine are taken into account and are correctly configured to
permit communication through appropriate ports.

If you are using UNIX server machines

If your XI R2 server runs on UNIX, you need to install the Import Wizard on a
separate Windows machine. You also need to use a third-party utility to map
the Windows drives to UNIX.
See the Microsoft documentation on “Interoperability with UNIX/Planning and
Installing Services for UNIX on Windows 2000 Professional.” As of this
writing, the URL is:
http://www.microsoft.com/resources/documentation/Windows/2000/server/
reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/
server/reskit/en-us/prork/prci_unx_houn.asp

Tips for optimal Import Wizard performance

You can substantially reduce importing time if you install the Import Wizard on
the same machine as the CMS and the CMS repository database.
If the repository is split among different sites, accessing remote domains via
the Import Wizard may take a long time, depending on network traffic and
bandwidth.
To further reduce import duration, Business Objects highly recommends that
you copy the remote source repository domains to the local machine. Update
the repository to these local copies before running the Import Wizard.

BusinessObjects 6.x to XI Release 2 Migration Guide 255

13 Before using the Import Wizard
Before importing

If you are using Tomcat

If you are migrating from v. 6.5 to XI R2, and using Tomcat as application
server, you may encounter a conflict when the Tomcat in both the source and
destination environments try to use the same default port.
If this occurs, you can manually change the port number of one of the Tomcat
applications servers (to 8081, for example).
To change the port number
1. Open the server.xml file.
2. Modify the port number.
For example, if you are using standard authentication, the line to edit
would be:
<Connector
className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8081" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000" useURIValidationHack="false"
disableUploadTimeout="true" />
3. Restart Tomcat.

Updating Data Integrator

To update Data Integrator, simply re-install the product, using the Data
Integrator installation CD.

Before importing
Before importing with the Import Wizard:
❏ Backing up the destination CMS database
❏ Ensuring you have appropriate rights
❏ Checking for correct Import Wizard installation
❏ Mapping the Import Wizard to Inbox and personal files
❏ Ensuring the Import Wizard can connect to the XI R2 CMS
❏ Starting destination servers
❏ Setting up auditing in the destination system
❏ If you count on using an LDAP external user management system,
Configuring the LDAP security plug-in

256 BusinessObjects 6.x to XI Release 2 Migration Guide

 Before using the Import Wizard
Before importing 13
Backing up the destination CMS database
If you have any content in the destination CMS database, make sure you
have a copy in case the database become corrupted.

Ensuring you have appropriate rights

Make sure you have the following rights:
• In version 6.x, you must have a General Supervisor profile.
• In XI R2, you must belong to the Administrator group in the CMS.
• To import any resource into the CMS, you must have the rights needed to
add objects to the destination folder to which the resource is assigned.

Checking for correct Import Wizard installation

Make sure the Import Wizard is properly installed by launching it by clicking
Start > Programs > BusinessObjects 11.5 > BusinessObjects Enterprise >
Import Wizard.
The executable file (ImpWiz.exe) is located in:
$INSTALLDIR\BusinessObjects Enterprise 11.5\win32_x86\

Mapping the Import Wizard to Inbox and personal

files
On the Import Wizard machine, map the drives to the source environment
directories containing the deployment’s .key files, personal documents and
categories, and users’ Inboxes:
• $INSTALLDIR\locData for access to 5.1.x .key files
• $WISTORAGEDIR\user if you are importing personal documents and
categories
• $WISTORAGEDIR\mail if you are importing the read content of users’
Inbox folders
• $INSTALLDIR\nodes\<nodename>\<clustername>\locdata for access to
6.x .key files
• $INSTALLDIR\nodes\<nodename>\<clustername>\storage\user if you
are importing personal documents and categories
• $INSTALLDIR\nodes\<nodename>\<clustername>\storage\mail if you
are importing the read content of users’ Inbox folders

BusinessObjects 6.x to XI Release 2 Migration Guide 257

13 Before using the Import Wizard
Before importing

If your server machines are running UNIX

To import version 6.x Inbox and personal files from one UNIX environment to
another, you must tar the source files from each cluster node, then unzip
them into folders on the Import Wizard Windows machine before running the
import.
On the Import Wizard machine, map drives to the local folders containing the
unzipped source environment directories.

Ensuring the Import Wizard can connect to the XI R2

CMS
The Import Wizard connects to the CMS through CORBA. Make sure you use
appropriate ports if you have to go through a firewall.

Starting destination servers

Before importing, you must start and enable at least the following servers in
the XI R2 environment, using the CMC:
• Central Management Server
• Input File Repository Server
• Output File Repository Server
To log on to the CMC:
1. In an Internet browser:
• Go to the following page:
http://<webserver>/BusinessObjects/enterprise11/admin/
Replace <webserver> with the name of the web server machine that
has the Web Connector component installed. If you changed this
default virtual directory on the web server, you will need to type your
URL accordingly.
• If you have BusinessObjects Enterprise installed locally on your
machine, click Start > Programs > BusinessObjects Enterprise 11.5
>BusinessObjects Enterprise Administration Launchpad.
Inside the Launchpad, click Launch the Central Management
Console.

258 BusinessObjects 6.x to XI Release 2 Migration Guide

 Before using the Import Wizard
Before importing 13
• Go to the following page:
http://<webserver>/BusinessObjects/enterprise11/admin/
Replace <webserver> with the name and port number of your Java
application server.
2. When the Log On page appears, select Enterprise in the Authentication
Type list.
3. Type your username and password.
4. Click Log On.
The CMC Home page appears.
Note: If you cannot access BusinessObjects Enterprise, start the Central
Configuration Manager (CCM) from the BusinessObjects Enterprise
program group. Ensure that all of the servers listed are both started and
enabled.

Setting up auditing in the destination system

Auditing allows you to monitor and record key facts about your XI R2 system.
You can set up auditing to track errors in the import process.
The CMS acts as the system auditor. The BusinessObjects Enterprise
servers are the audited components.
To track errors in the import process, you first determine which servers control
the actions involved in importing. Then you enable auditing of those actions in
the Server Management area of the CMC. The server records the audit
results in a local log file.
For more information and instructions, see the BusinessObjects Enterprise XI
Release 2 Auditor’s Guide.

Configuring the LDAP security plug-in

If you want the Import Wizard to import external LDAP groups, you need to
configure XI R2 with the LDAP server used by your 6.x system. For more
information, see the BusinessObjects Enterprise XI Release 2 Administrator’s
Guide.

BusinessObjects 6.x to XI Release 2 Migration Guide 259

13 Before using the Import Wizard
Before importing

If you plan on using an LDAP provider for authentication, you must configure
the LDAP wizard in the BusinessObjects XI R2 system before importing the
external users.
1. Configure LDAP from the CMC. You just have to configure the connection
parameters, you don’t have to map any groups.
2. Use the Import Wizard to import your content – make sure you check the
option when it asks you about LDAP users.
Note: The Import Wizard will add an LDAP alias to every group brought
over that it can find in the configured LDAP system (it does this by
matching the name of the group to the name of a group in the LDAP
system)
Note: The Import Wizard will do an “update” of the LDAP plug-in after
the users and group have been brought over, this will add an LDAP alias
to every user that belongs (in the LDAP system) to one of the groups with
an LDAP alias.
3. After Import, it’s recommended that the administrator go through the
users and groups in the XI system to make sure that the Import Wizard
made correct assumptions about what users and groups were intended
to be LDAP users and groups. Administrator should delete/re-assign/add
LDAP aliases as necessary. Additional LDAP groups can also be
mapped at this point if you want to.
Note: If you chose to import user’s personal content, only users that actually
exists (i.e. have user objects) in the repository will have their personal content
imported to XI R2.

260 BusinessObjects 6.x to XI Release 2 Migration Guide

BusinessObjects 6.x to XI Release 2 Migration Guide

Using the Import Wizard

chapter
14 Using the Import Wizard
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The steps in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Assessment and planning

2. Preparing for import

D 3. Importing from the source to destination environment

• Launching the Import Wizard

• Setting the source and destination environments
• Selecting the types of objects to import
• Selecting an import scenario
• Importing specific objects
• Finalizing the import
• If you’re migrating Application Foundation
4. Post-import checking and tuning

Overview
The Import Wizard lets you import Business Intelligence resources to XI R2.
These resources include users and user groups, universes, connections, and
documents.
Chapter 5: Understanding object migration explains how the Import Wizard
imports resources. This chapter explains how to perform the import.
Note: Before using the Import Wizard, you must have completed all steps in
Chapter 13: Before using the Import Wizard.

262 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Launching the Import Wizard 14
How long will importing take?
How long importing takes depends on a number of factors. Performance is
best if:
• the Import Wizard is on the same machine as the CMS and the repository
database
• you have copied the source repository domains to the Import Wizard
machine
Document import can be time-consuming, taking up to three seconds per
document. It may take even longer if you are accessing a remote repository
through the network, or if your source repository is geographically distributed.
The size of the documents and the number of users are also key factors, as is
the size of the repository.

Launching the Import Wizard

The Import Wizard guides you through the process of importing user
accounts, groups, universes, documents, and other objects. The dialog boxes
that appear vary, depending on the source environment and the types of
information that you import.
First, you connect to the source repository and specify the destination CMS.
You then select the information you want to import, and the Import Wizard
imports the requested information from the source to the destination.
During import, all objects in the source repository are copied to a temporary
folder on the machine running the Import Wizard. (See “Flow of resources” on
page 83.)
To launch the Import Wizard
• On a Windows machine in the destination environment, do either of the
following:
• From the Windows Start menu, point to Programs >
BusinessObjects 11.5 > BusinessObjects Enterprise > Import
Wizard.
• From the command prompt, run ImpWiz.exe.
ImpWiz.exe is located in:
$INSTALLDIR\BusinessObjects Enterprise 11.5\
win32_x86\
The Welcome page appears.

BusinessObjects 6.x to XI Release 2 Migration Guide 263

14 Using the Import Wizard
Setting the source and destination environments

Summary of steps
The remaining steps in the Import Wizard are divided into:
• Type of import and type of object
• Setting the source and destination environment
• Selecting the types of objects to import
• Selecting import options
• Selecting an import scenario
• Importing specific objects
• Users and groups
• Broadcast Agents
• Categories
• Document domains and documents
• Universe and connection objects
• Universe domains and universes

Setting the source and destination

environments
In this step, you set a source environment and a destination environment.
To set the source and destination environments
1. On the Welcome page of the Import Wizard, click Next.
The Source Environment dialog box appears.
If you are importing Application Foundation objects, go to “If you’re
migrating Application Foundation” on page 274.
2. In the Source list, select BusinessObjects Enterprise 6.x
You are prompted for administrative account information. The fields that
appear depend on the type of source environment you selected.
3. Type a user name and password that give you administrative rights to the
source environment.
Note: You must have a General Supervisor profile in the repository.
4. In the Domain Key File field, type or browse for the path to the .key file
you created for the repository in your source environment.

264 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Selecting the types of objects to import 14
5. If you want to import Application Foundation objects using the Import
Wizard, select the Import Application Foundation Contents check box.
You can import Application Foundation objects only if you selected
BusinessObjects Enterprise 6.x (or XI) in the Source list.
Note: If you are importing Application Foundation objects, go to “If you’re
migrating Application Foundation” on page 274.
6. Click Next.
The Import Wizard verifies the connection to the repository, the
credential, the validity of the General Supervisor login, and the repository
version.
An informational page appears that summarizes the items that can be
imported.
7. Click Next.
The Destination Environment dialog box appears.
8. Type the name of the CMS of the destination environment.
9. Type a user name and password that give you Administrator rights to the
destination environment, and then click Next.
The Import Wizard verifies the login at the CMS.
The Select Objects to Import dialog box appears.

Selecting the types of objects to import

In this stage of the importing process, you select the types of objects you
want to import. At a later stage, you will select the objects themselves.
To select the types of objects to import
1. In the Select Objects to Import dialog box, select the types of objects you
want to import.
The options that appear depend on the source environment and its
version, and on whether you selected the Import Application Foundation
Contents check box. See “If you’re migrating Application Foundation” on
page 274 for details.
Note: The Import Broadcast Agents check box is dimmed and cannot be
selected if there are no Broadcast Agents and no jobs to import in the
repository.
2. Click Next.

BusinessObjects 6.x to XI Release 2 Migration Guide 265

14 Using the Import Wizard
Selecting the types of objects to import

Security Migration Options

If you selected Import users and user groups in the Select Objects to Import
dialog box, the Security Migration Options dialog box appears. (If you did not
select it, go to “Personal and inbox documents” on page 266.)
The Security Migration Options dialog box allows you to select the way you
want to migrate security—and whether you want to migrate security at all.
There are three options:
• Yes, migrate security on imported objects and secure the destination
system
This is the most secure option.
• Yes, migrate security on imported objects
Users in the destination system may end up with more rights than in the
source system.
• No, don’t migrate security
Select this option only if you are rebuilding security in XI R2.
For more information, see “Security migration options” on page 166.
Note: Universe overloads are not included in the Security migration. You
select overload migration in “Universe and connection objects” on page 271.
To select a security migration option
1. In the Security Migration Options dialog box, select one of the three
options.
2. Click Next.

Personal and inbox documents

If, in the Select Objects to Import dialog box, you selected the import of
objects stored either in inbox or personal folders, the Personal Documents
and Inbox Documents dialog box appears. (If you did not select it, go to
“Selecting an import scenario” on page 267.)

266 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Selecting an import scenario 14
To import personal and/or inbox documents
1. Type or browse for the path of your Personal and/or Inbox documents in
the source environment.
If the folders are located on a remote or UNIX server, you must have
mapped them to local drives.
You do not need to provide a path for corporate documents because they
are stored in the repository.
Import Wizard imports both read and unread Inbox documents to XI R2.
2. Click Next.
The Import Scenario dialog box appears.

Selecting an import scenario

You can merge the source and destination environments, or you can update
the destination environment without merging:
• Merging the environments
The Import Wizard adds all objects from the source to the destination
CMS without overwriting objects in the destination environment.
This is the safest import option. All of the objects in the destination
environment are preserved.
• Updating the destination environment
All objects in the source are added to the destination CMS, but if a source
object has the same unique identifier as an object in the destination
environment, the destination object is updated.
For more information, see “The Merge and Update import scenarios” on
page 169.
To select an import scenario
1. In the Import Scenario dialog box, select the type of import you want.
• To merge the source and destination environments, select I want to
merge the source system into the destination system.
If you want to automatically rename top-level folders that match top-
level folders on the destination system, select the check box.

BusinessObjects 6.x to XI Release 2 Migration Guide 267

14 Using the Import Wizard
Selecting an import scenario

• To update the destination environment without merging, select I want

to update the destination system by using the source system as a
reference.
If you want to automatically rename objects when an object with the
same title already exists in the destination folder, select the check
box.
2. Click Next.
If you selected the Update option in the previous step, the Incremental
Import dialog box appears. Go to “Updating previously imported objects”
on page 268.
If you selected the Merge option, you are prompted to select specific
objects for import. See the section below for instructions regarding that
object type.

Updating previously imported objects

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

268 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Importing specific objects 14
To update previously imported objects
1. In the Incremental Import dialog box, select the type of objects whose
content you want to overwrite:
• Documents (including dashboards and analytics)
• Universes
• Connections
2. If you want to overwrite object rights, select the Overwrite object rights
check box.
3. Click Next.
If you are prompted to select specific objects for import, go to the section
below for instructions regarding that object type.
If the Ready to Import dialog box appears, go to “Finalizing the import” on
page 273.

Importing specific objects

If you chose to import users, groups, domains, Web Intelligence documents,
BusinessObjects documents, categories, universes, folders, repository
objects, or Broadcast Agents, you are now prompted to select the specific
objects you want to import. You can import all of the objects or select
individual ones.
At each stage, it may take some time for objects to be displayed, because the
Import Wizard is retrieving them from the repository.

Users and groups

If you are importing users and groups, the Users and Groups dialog box
appears.
For detailed information on the import of users and groups, see
“Understanding user and group migration” on page 65.
To select users and groups
1. In the Groups list, select the groups you want to import.
2. In the Users list, select specific members of any group.
3. Click Next.
If the Import Groups Option dialog box appears, the 6.x source and the XI R2
destination environments are configured for LDAP or Active Directory.

BusinessObjects 6.x to XI Release 2 Migration Guide 269

14 Using the Import Wizard
Importing specific objects

Select if you want group mappings from LDAP and Active Directory to be
migrated to XI R2.
You need to have the same LDAP or Active Directory configuration on the
source and destination.
Select the third-party group mapping you want to migrate and then click Next.

Populating database credentials

After users and groups are imported, the Populate Database Credentials for
Users dialog box appears.
This dialog box enables you to automatically set the DBUSER and DBPASS
attributes, for all imported users, with their login and password. These can be
used as default database credentials for connections (see “BOUSER/
BOPASS” on page 91).
To populate database credentials
1. Do either of the following:
• If you want to populate the database credentials of imported users
with their BusinessObjects user name and password, select Yes.
• If you do not want to do this, select No.
2. Click Next.

Broadcast Agent
If you are importing Broadcast Agents, the Broadcast Agents dialog box
appears.
This dialog box enables you to select the Broadcast Agents you want to
import.
Note: A Broadcast Agent job can be migrated from BusinessObjects
Enterprise 6.x to XI R2 only if the job is supported in XI R2. (For details, see
“Broadcast Agent” on page 86.)
To select Broadcast Agents for import
1. In the Broadcast Agent dialog box, select the Broadcast Agents whose
jobs you want to import.
Note that all the jobs, for each Broadcast Agent, are selected by default.
2. Click Next.

270 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Importing specific objects 14
Categories
If you are importing categories, the Categories dialog box appears.
To select categories
1. Select the categories you want to import.
For large document domains, you can import incrementally, and import
documents one category at a time.
2. If you want to import all the objects associated with the category, select
the Import all objects that belong to the selected categories check box.
3. Click Next.

Document domains and documents

If you are importing one of the following types of corporate document:
• Web Intelligence
• BusinessObjects
• Analytics (performance management)
• Third-party
then the Domains and Documents dialog box appears.
The list contains a separate branch for each domain. Domains that cannot be
opened are dimmed.
If you previously chose to import all the objects of a given category, they are
preselected and cannot be cleared from the list.
To select domains and documents
1. Select the domains and individual documents you want to import.
When you select a domain, all the documents within it are highlighted.
2. Click Next.

Universe and connection objects

If you chose to import universes in the Select Objects to Import dialog box,
the Import Options for Universes and Connections dialog box appears. (If you
did not, go to “Universe domains and universes” on page 272.)

BusinessObjects 6.x to XI Release 2 Migration Guide 271

14 Using the Import Wizard
Importing specific objects

To import universe and connection objects

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

Universe domains and universes

If you chose to import universes and connections that are linked to specific
documents (see “Universes and universe connections” on page 89), the
Universe Folders and Universes dialog box appears.
When you import scheduled documents from 6.x, you must also import the
universes used by these documents. The universes are not selected
automatically during the import. This means that if you are not importing all
your universes, you must manually select the ones you need for Broadcast
Agent jobs.
To select universes
1. Select the universes you want to import.
The universes that are linked to specific documents cannot be cleared
from the list.
You can select additional universes that are not used by any imported
document.

272 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Finalizing the import 14
2. Click Next.
If no universe is found, the associated documents will not be imported
and a warning message appears. If this occurs, link the documents to a
universe, republish them to the repository, and retry the import.

Locales and platform options

In the Locales and Platform Options dialog box, you set the default locales for
2.x/5.x Web Intelligence and BusinessObjects documents. These are the
locale used in the documents and the locale of the platform where the
documents were created.
To set the locales
1. From the lists, select the default locale (language) of the documents and
the platform.
In a version 6.x repository, some Web Intelligence 2.x (.wqy) documents
and BusinessObjects documents may not store their locales. In order to
set locales in these documents when they are saved in the CMS (after
conversion to .wid), the default locales provided by the user are added to
the documents.
2. Click Next.

Finalizing the import

When the Import Wizard completes its collection of information, the Ready to
Import dialog box appears.
This procedure may take some time, because a large quantity of data is being
retrieved.
To finalize the import
1. Click Finish.
The Import Progress dialog box appears. It shows:
• the progress of the import
• a summary of the events taking place
2. To see more information about the events, click View Detail Log, and
then see “Checking the Import Wizard log file” on page 290.
3. Click Done.
The import is now complete.

BusinessObjects 6.x to XI Release 2 Migration Guide 273

14 Using the Import Wizard
If you’re migrating Application Foundation

If you’re migrating Application Foundation

If you are importing Application Foundation objects, follow the procedures
below. This section covers all the procedures in the Import Wizard.
To migrate Application Foundation objects to Performance Management
1. In the Source Environment dialog box, select the source environment
(6.1.b, 6.1.3 and 6.5 are supported for migration to Performance
Management XI R2).
2. Type the name of the BusinessObjects repository security domain and a
user name and password to access it with administrative rights.
Note: The user name and password you type must belong to a General
Supervisor profile.
3. In the Domain Key File field, type or browse for the path to the .key file of
the source environment.
4. Select the Import Application Foundation Contents check box and click
Next.
The Import Wizard verifies the connection to the repository, the
credentials, the validity of the General Supervisor login, and the
repository version.
5. In the Dashboard files section of the Application Foundation source
screen, browse to the location of the Application Foundation storage
folder.
By default, it is $INSTALLDIR/Application Foundation/server/conf.
6. In the Application Foundation source repository section, indicate the
repository’s details using one of the following methods:
• check the Use conf file option
This option allows you to specify the location of the AF config file that
contains the repository database information rather than entering it
manually. It is highly recommended that you upgrade a copy of the
source repository, and that you point to the connection to the copy
when you upgrade the repository.
• manually enter the following repository database information:
• name of the source repository
• database engine
• network layer of the source repository
• a user name and password to access the database

274 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Selecting the types of objects to import 14
Note: The user name and password you type must belong to an
Administrator profile. It is highly recommended that you upgrade a
copy of the source repository, and that you point to the connection to
the copy when you upgrade the repository.
7. Click Next.
The Application Foundation Repository Update dialog box appears.
8. Select one of the following options:
• Yes to update the repository in the Import Wizard
• No to skip the repository update and migrate the repository later
Note: If you want to perform the migration in several steps, the
Application Foundation repository must be updated at the end of the
migration process. You can only update the repository once. If you are
migrating rules and schedules, you must migrate them in the same
Import Wizard session as the repository update.
9. Click Next.
If you chose not to upgrade the repository, a dialog box listing the objects
you can import appears. Click Next to continue.
If you chose to upgrade the repository, a warning message appears. You
must acknowledge that you have read the warning by checking the I
understand. I want to continue. box to proceed with the repository
upgrade.
10. In the Destination Environment dialog box, indicate the name of the
destination CMS into which you want to import migrated objects.
11. Type a user name and password that give you Administrator rights to the
destination environment, and click Next.
The Import Wizard verifies the login at the CMS. A dialog box appears
that summarizes the items that can be imported into the CMS.
12. Click Next.
The Select Objects to Import dialog box appears.

Selecting the types of objects to import

In this stage of the import process, you select the types of objects you want to
import. At a later stage, you will select the objects themselves.

BusinessObjects 6.x to XI Release 2 Migration Guide 275

14 Using the Import Wizard
Selecting the types of objects to import

To select the types of objects to import

1. In the Select Objects to Import dialog box, select the types of objects you
want to import. The Application Foundation objects available in this dialog
box are:
• Universes and documents referenced by analytics you are importing
• Analytics (*.afd)
• Rules and schedules (this option is only available if you selected Yes
for the Application Foundation repository upgrade)
• Named events (this option is only available if you selected Yes for the
Application Foundation repository upgrade)
• Dashboards (corporate and personal)
• Standard Application Foundation security
Note: The Import Broadcast Agents check box is dimmed and cannot be
selected if there are no Broadcast Agents and no jobs to import in the
repository.
2. Click Next.

Security Migration Options

If you selected Import users and user groups in the Select Objects to Import
dialog box, the Security Migration Options dialog box appears. (If you did not
select it, go to “Personal and inbox documents” on page 266.)
The Security Migration Options dialog box allows you to select the way you
want to migrate security—and whether you want to migrate security at all.
There are three options:
• Yes, migrate security on imported objects and secure the destination
system
This is the most secure option.
• Yes, migrate security on imported objects
Users in the destination system may end up with more rights than in the
source system.
• No, don’t migrate security
Select this option only if you are rebuilding security in XI R2.
Note: Universe overloads are not included in the Security migration. You
select overload migration in “Universe and connection objects” on page 271.

276 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Selecting an import scenario 14
To select a security migration option
1. In the Security Migration Options dialog box, select one of the three
options.
2. Click Next.

Personal and inbox documents

If, in the Select Objects to Import dialog box, you selected the import of
objects stored either in inbox or personal folders, the Personal Documents
and Inbox Documents dialog box appears. (If you did not select it, go to
“Selecting an import scenario” on page 267.)
To import personal and/or inbox documents
1. Type or browse for the path of your Personal and/or Inbox documents in
the source environment.
If the folders are located on a remote or UNIX server, you must have
mapped them to local drives.
You do not need to provide a path for corporate documents because they
are stored in the repository.
Import Wizard imports both read and unread Inbox documents to XI R2.
2. Click Next.
The Import Scenario dialog box appears.

Selecting an import scenario

You can merge the source and destination environments, or you can update
the destination environment without merging:
• Merging the environments
The Import Wizard adds all objects from the source to the destination
CMS without overwriting objects in the destination environment.
This is the safest import option. All of the objects in the destination
environment are preserved.
• Updating the destination environment
All objects in the source are added to the destination CMS, but if a source
object has the same unique identifier as an object in the destination
environment, the destination object is updated.

BusinessObjects 6.x to XI Release 2 Migration Guide 277

14 Using the Import Wizard
Selecting an import scenario

To select an import scenario

1. In the Import Scenario dialog box, select the type of import you want.
• To merge the source and destination environments, select I want to
merge the source system into the destination system.
If you want to automatically rename top-level folders that match top-
level folders on the destination system, select the check box.
• To update the destination environment without merging, select I want
to update the destination system by using the source system as a
reference.
If you want to automatically rename objects when an object with the
same title already exists in the destination folder, select the check
box.
2. Click Next.
If you selected the Update option in the previous step, the Incremental
Import dialog box appears. Go to “Updating previously imported objects”
on page 268.
If you selected the Merge option, you are prompted to select specific
objects for import. See the section below for instructions regarding that
object type.

Updating previously imported objects

You may need to import some objects more than once from the source
repository to the destination repository.
In this situation, you have the following update options:
• Overwrite object contents
You select the types of objects for which the content overwrite applies:
• Documents
• Universes
• Connections
When you reimport an object, it will completely overwrite and replace the
object (and its associated files) that you imported earlier.

278 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Importing specific objects 14
• Overwrite object rights
When you reimport an object, its associated security rights will overwrite
the rights of the object you imported earlier.
If you decided not to import security in the Security Migration Options
dialog box, then the Overwrite object rights option is not relevant, and is
therefore not available.
If you don’t select any overwrite options, the object in the destination
repository will not change when you try to import it again.
To update previously imported objects
1. In the Incremental Import dialog box, select the type of objects whose
content you want to overwrite:
• Documents (including dashboards and analytics)
• Universes
• Connections
2. If you want to overwrite object rights, select the Overwrite object rights
check box.
3. Click Next.
If you are prompted to select specific objects for import, go to the section
below for instructions regarding that object type.
If the Ready to Import dialog box appears, go to “Finalizing the import” on
page 273.

Importing specific objects

If you are importing users, groups, domains, WebIntelligence documents,
BusinessObjects documents, categories, universes, folders, repository
objects, or Broadcast Agents, you are now prompted to select the specific
objects you want to import. You can import all of the objects or select
individual ones.
It may take some time before objects are displayed, because the Import
Wizard is retrieving them from the repository.

BusinessObjects 6.x to XI Release 2 Migration Guide 279

14 Using the Import Wizard
Importing specific objects

Users and groups

If you are importing users and groups, the Users and Groups dialog box
appears.
To select users and groups
1. In the Groups list, select the groups you want to import.
2. In the Users list, select specific members of any group.
3. Click Next.
If the Import Groups Option dialog box appears, the 5.x/6.x source and the XI
R2 destination environments are configured for LDAP or Active Directory.
Select if you want group mappings from LDAP and Active Directory to be
migrated to XI R2.
You need to have the same LDAP or Active Directory configuration on the
source and destination.
Select the third-party group mapping you want to migrate, and then click
Next.

Populating database credentials

After users and groups are imported, the Populate Database Credentials for
Users dialog box appears.
This dialog box enables you to automatically set the DBUSER and DBPASS
attributes, for all imported users, with their login and password. These can be
used as default database credentials for connections.
To populate database credentials
1. Do either of the following:
• If you want to populate the database credentials of imported users
with their BusinessObjects user name and password, select Yes.
• If you do not want to do this, select No.
2. Click Next.

Broadcast Agent
If you are importing Broadcast Agents, the Broadcast Agents dialog box
appears.
This dialog box enables you to select the Broadcast Agents you want to
import.

280 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Importing specific objects 14
Note: A Broadcast Agent job can be migrated from BusinessObjects
Enterprise 5.x/6.x to XI R2 only if the job is supported in XI R2. (For details,
see “Broadcast Agent” on page 86.)
To select Broadcast Agents for import
1. In the Broadcast Agent dialog box, select the Broadcast Agents whose
jobs you want to import.
Note that all the jobs, for each Broadcast Agent, are selected by default.
2. Click Next.

Dashboards
If you are importing dashboards, the Dashboards dialog box appears.
To select dashboards
1. Select the dashboards you want to import.
When you select an application, its submenus are also selected.
2. Click Next.
The Import Wizard checks whether any dashboards in the source
repository include security. If the Import Wizard detects security on any
dashboards, the Import Dashboard Option dialog box appears. If none of
the dashboards selected for import includes security, skip to step 4.
3. If dashboards selected for import include security, select one of the
following options:
• Import and apply page security on all page elements
The Import Wizard migrates the dashboard and any sub-menus and
applies standard page-level security, which is translated as an ACL
in the CMS. With this option, the least restrictive set of rights is
applied.
• Don’t import such dashboards
The Import Wizard imports all dashboards, including dashboards
with analytic-level security restrictions, but empties all content from
pages containing secured elements. Dashboard menu structures are
preserved.

BusinessObjects 6.x to XI Release 2 Migration Guide 281

14 Using the Import Wizard
Importing specific objects

• Import but move to administrator’s Favorites folder for revision

The Import Wizard imports all dashboards, including secured
dashboards, but empties the content of all secured dashboards.
When you choose this option, dashboard menu structures are
preserved and a copy of each secured dashboard, including its
contents, is moved to the administrator’s favorite folder. A prefix is
added to the secured dashboard’s name so that the administrator
can easily identify it after migration, then modify it manually before
publishing it to a wider audience.

Categories
If you are importing categories, the Categories dialog box appears.
To select categories
1. Select the categories you want to import.
For large document domains, you can import incrementally, and import
documents one category at a time.
2. If you want to import all the objects associated with the category, select
the Import all objects that belong to the selected categories check box.
3. Click Next.

Document domains and documents

If you are importing one of the following types of corporate document:
• WebIntelligence
• BusinessObjects
• Analytics (performance management)
• Third-party
then the Domains and Documents dialog box appears.
The list contains a separate branch for each domain. Domains that cannot be
opened are dimmed.
If you previously chose to import all the objects of a given category, they are
preselected and cannot be cleared from the list.
To select domains and documents
1. Select the domains and individual documents you want to import.
When you select a domain, all the documents within it are highlighted.

282 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Importing specific objects 14
2. Click Next.

Universe and connection objects

If you chose to import universes in the Select Objects to Import dialog box,
the Import Options for Universes and Connections dialog box appears. (If you
did not, go to “Universe domains and universes” on page 272.)
To import universe and connection objects
1. Select an import option:
• Import all universes and all connection objects
This imports all universes from the source environment in one batch.
You cannot select individual universes or connections.
• Import all universes, and only connection objects used by those
universes
• Import universes and connections that the selected WebIntelligence
and BusinessObjects and Application Foundation documents use
directly
In a later dialog box, you will be able to select additional universes to
import.
2. If you want to migrate universe overloads, select the Keep universe
overloads for imported users and groups check box.
If you do not select this, then no universe overloads will be migrated.
Universe overloads are imported only for users and groups that are
imported into the CMS.
3. Click Next.

Universe domains and universes

If you are importing universes and connections that are linked to specific
documents, the Universe Folders and Universes dialog box appears.
When you import scheduled documents from 6.x, you must also import the
universes used by these documents. The universes are not selected
automatically during the import. This means that if you are not importing all
your universes, you must manually select the ones you need for Broadcast
Agent jobs.

BusinessObjects 6.x to XI Release 2 Migration Guide 283

14 Using the Import Wizard
Importing specific objects

To select universes
1. Select the universes you want to import.
The universes that are linked to specific documents cannot be cleared
from the list.
You can select additional universes that are not used by any imported
document.
2. Click Next.
The Import Wizard checks that universe IDs and names are consistent
between the Application Foundation repository and BusinessObjects
repository, and that the two repositories are of the same version. If the
Import Wizard detects inconsistencies in universe names/ids or
repository versions, universes selected for import (or imported by default
because they are referenced by other objects selected for import) a
warning is displayed and you are prompted to resolve the inconsistencies
before migrating. See Best Practices for Migrating to BusinessObjects
Performance Management XI R2 for more information on resolving
universe inconsistencies.
If the universe is not found, the associated documents will not be
imported and a warning message appears. If this occurs, link the
documents to a universe, republish them to the repository, and retry the
import.

Locales and platform options

In the Locales and Platform Options dialog box, you set the default locales for
2.x/5.x WebIntelligence and BusinessObjects documents. These are the
locale used in the documents and the locale of the platform where the
documents were created.
To set the locales
1. From the lists, select the default locale (language) of the documents and
the platform.
In a version 5.x/6.x repository, some WebIntelligence 2.x (.wqy)
documents and BusinessObjects documents may not store their locales.
In order to set locales in these documents when they are saved in the
CMS (after conversion to .wid), the default locales provided by the user
are added to the documents.
2. Click Next.

284 BusinessObjects 6.x to XI Release 2 Migration Guide

 Using the Import Wizard
Finalizing the import 14
Finalizing the import
When the Import Wizard completes its collection of information, the Ready to
Import dialog box appears.
This procedure may take some time, because a large quantity of data is being
retrieved.
To finalize the import
1. Click Finish.
The Import Progress dialog box appears. It shows:
• the progress of the import
• a summary of the events taking place
2. To see more information about the events, click View Detail Log, and
then see “Checking the Import Wizard log file” on page 290.
3. Click Done.
The import is now complete.

BusinessObjects 6.x to XI Release 2 Migration Guide 285

14 Using the Import Wizard
Finalizing the import

286 BusinessObjects 6.x to XI Release 2 Migration Guide

Verifying and completing
the new environment
288 BusinessObjects 6.x to XI Release 2 Migration Guide
BusinessObjects 6.x to XI Release 2 Migration Guide

Checking and adapting the

new environment

chapter
15 Checking and adapting the new environment
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Assessment and planning

2. Preparing for import

3. Importing from the source to destination environment
D 4. Post-import checking and tuning

• Verifying overall import success

• Checking user/group and object import
• Checking imported documents
• Checking universe access restrictions
• Checking and adjusting security
• Recreating scheduling jobs

Overview
Now that you have finished using the Import Wizard, you need to:
• verify that objects have been properly imported
• verify the functioning of the objects in the destination environment
• perform final adjustments

Verifying overall import success

The sections below explain how to verify that your import was successful.

Checking the Import Wizard log file

During the import, a log file is generated by the Import Wizard. For each item,
the log contains a system-generated ID number, a description of the imported
information, and an explanation of any action taken by the system.

290 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking and adapting the new environment
Verifying overall import success 15
The log stores events that occurred during the import, as well as options
selected before starting the import.
For example, an entry for incorrect password would look as follows in the log
file:

You can access the log via the Import Progress dialog box, or by opening the
log file from the installation directory.
Broadcast Agent documents that cannot be migrated because the job is not
supported in XI R2 will appear in the log according to the first non-supported
job detected by the system, even if there are others.

From the Import Progress dialog box

The Import Progress dialog box appears at the end of the importing process
(see “Finalizing the import” on page 273).
To access the log file via the Import Progress dialog box
1. In the Import Progress dialog box, click View Detail Log.
The Detail Log dialog box appears.
This dialog box lists all the objects the Import Wizard has migrated and
their status, as well as any errors that may have occurred.
2. For more details on a given item, select it from the list.
The details are displayed at the bottom of the dialog box.
3. When you have finished reviewing the log, click OK.

From the installation directory

To open the log file from the installation directory
1. In the XI R2 installation directory, go to \...\win32x86\
The default location is:
C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32x86\
2. Open the ImportWiz.log file.

BusinessObjects 6.x to XI Release 2 Migration Guide 291

15 Checking and adapting the new environment
Verifying overall import success

Checking the import via the CMC

The CMC can display the total user count at the top of the user area.

It can also show the total number of objects, as well as information about the
objects.

You can review the list of users in the CMS and check whether 6.x users and
groups have been correctly created. If you are migrating security, then you
can also check that rights and assignments are correctly set.

292 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking and adapting the new environment
Checking user/group and object import 15
Checking the import using Query Builder
Query Builder is a tool that allows you to type SQL-like expressions to run
queries such as:
• show me the user count
• show me all objects of type rep, wid, wqy
To start Query Builder from the Administration Launchpad, click
Administrative Tools > Query Builder.

Checking user/group and object import

To check whether users/groups and objects were imported, you can also:
• Log into the products
Try to log into the various XI R2 products using a migrated user login.
• Log into InfoView and check whether the documents that should be
visible in the portal, are actually visible. Do the same with Web
Intelligence and Desktop Intelligence.

Checking imported documents

Most imported documents undergo some updating during the import. You
should verify to what extent this has changed the documents.

Desktop Intelligence calculations

In recent years, Business Objects has made a number of improvements to
the BusinessObjects/Desktop Intelligence calculation engine (the part of the
software that calculates report values). As a result, the same report might
sometimes return different values in certain circumstances, depending on the
calculation engine version.
“Checking for calculation updates” on page 301 describes the calculation
engine changes in detail. It helps you identify reports that might return
different values under Desktop Intelligence, explains why these values are
different and how to modify your reports to return the former values.
Because there is more than one group of calculation engine changes, the
precise impact on your reports depends on their original version.
“BusinessObjects document migration” on page 302 describes these groups
of changes in detail.

BusinessObjects 6.x to XI Release 2 Migration Guide 293

15 Checking and adapting the new environment
Checking imported documents

Impact of migrating to a Unicode database

Unicode font sizes are different than their non-Unicode equivalents.
Therefore, if you have migrated BusinessObjects documents to Desktop
Intelligence, and have also migrated your 6.x data sources to a Unicode
database, you may encounter the following:
• Documents are not pixel-per-pixel identical.
• When a cell isn’t big enough to display all its contents, it uses “###” to
indicate that the contents have been truncated.
Because the Unicode fonts are sometimes bigger than their non-Unicode
equivalents, you may see ### in cells where previously you saw data.
• The size of documents may be affected.
• Functions like NumberOfPages() may return different values in the case
of Autofit cells.
For changes in the calculation engine, see “Checking for calculation
updates” on page 301.
Note: The move to Unicode has no impact on sorts.

Web Intelligence documents

Autofit behavior
There may be a difference in column width when documents are converted. In
Web Intelligence 6.x, the Autofit behavior for columns is different than in 5.x:
• In 5.x, Autofit could be applied separately to each cell
The Autofit option is set when cell width = default.
• In Web Intelligence 6.x, Autofit is applied to the whole column whenever it
is applied to a cell.
In XI R2, Autofit has the same behavior as in version 5.x.
When Autofit is combined with wrap text, 5.x takes into account the wrap. Text
is cut when the longest string is found.
However, both XI R2 and 6.x ignore the wrap text property when it is
combined with Autofit.

294 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking and adapting the new environment
Checking imported documents 15
Customizing the Conversion Settings file
You can customize the Conversion Settings XML file to change cell width and
autowrap settings. The file is located in:
$INSTALLDIR\BusinessObjects Enterprise 11.5\win32_x86\wqyConversionSettings.xml
The settings can be changed on the following lines:
<OPTION NAME="cell_width_wrap" VALUE="auto" />
<OPTION NAME="cell_width_autofit" VALUE="auto" />
Note:
• If value is “auto”, WQY conversion keeps the option as is
• If value is “yes”, WQY conversion switches the option to yes
• If value is “no”, WQY conversion switches the option to no

Locale
In some Web Intelligence 2.x versions, locale was not stored in the .wqy file.
Normally, during the import, if no locale is found in the .wqy file, the Import
Wizard prompts you for a locale.
Business Objects recommends checking the locale of converted Web
Intelligence documents, to make sure it has been correctly migrated.

Re-establishing document-to-document links

After the import, if you have integrated document-to-document links using
openDoc in BusinessObjects or Web Intelligence documents, you need to
manually re-establish those links in Desktop Intelligence and
Web Intelligence. (Links based on openanalytic, however, are migrated.)

Troubleshooting documents that have not been

correctly migrated
If during import some documents have not been correctly migrated, you may
get error messages in the Import Wizard log file such as:
• “Failed to get contents” for BusinessObjects documents
• “wqyReader::open failed” for Web Intelligence documents
If this occurs, make sure that the documents are not corrupted in the source
repository. If they are corrupted, they can’t be imported.

BusinessObjects 6.x to XI Release 2 Migration Guide 295

15 Checking and adapting the new environment
Checking universe access restrictions

Also make sure that temporary disk space has not been completely used up
by the Import Wizard temporary files.
Update any VBA macros. Some macros may no longer work because the
platform-related part of the BOSDK object model has been updated.
Documents containing OLAP data providers are migrated by the Import
Wizard, but these data providers can no longer be refreshed. Therefore, the
documents must be rebuilt.

Checking universe access restrictions

Business Objects recommends that you look at universe overloads (access
restrictions) in Designer XI R2 to see what group ordering has been defined
by the Import Wizard for particular universes. You can then fine-tune the
ordering if necessary.

Checking and adjusting security

If you have imported security, you may need to adjust security for users after
migration.

Everyone user group rights

When you migrate to XI R2, all existing users become members of the
Everyone user group. This means that your users may acquire access rights
they did not have previously. Or, they may be denied rights they had before
the migration.

296 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking and adapting the new environment
Checking and adjusting security 15
The new access rights depend on which of the following three options you
selected in the Security Migration Options dialog box of the Import Wizard.

Security migration option Impact

Yes, migrate security on Being the most secure option, this denies
imported objects and secure access to all objects and applications for the
the destination system Everyone group. You must manually allow
the access you want.
Yes, migrate security on This is a less secure option, so the settings
imported objects for the Everyone group are not modified.
You may need to manually restrict access.
No, don't migrate security No security is migrated. The migrated
system is completely open and all users
have access to all resources. You should
only use this option if you are rebuilding
security from the ground up.

No matter which option you selected, Business Objects recommends that you
make sure the Everyone group gives or denies only the rights you want for
your users. Check the rights given or denied to Everyone for:
• BusinessObjects Enterprise applications; for example, InfoView
• folders
Remember that when users have access to a folder, they have access to
the contents of the folder unless explicitly denied.
• documents
• universes
• connections
For detailed information and instructions on setting user rights and access to
applications, see the BusinessObjects Enterprise XI Release 2
Administrator’s Guide.
For example, to check and adjust the rights for InfoView
1. Log into the CMC.
2. Select BusinessObjects Enterprise Applications > InfoView.
3. Click the Rights tab.
4. Adjust the rights to InfoView for the Everyone group.

BusinessObjects 6.x to XI Release 2 Migration Guide 297

15 Checking and adapting the new environment
Recreating scheduling jobs

If you have not imported security

You need to recreate security for your XI R2 environment. For guidelines, see
Chapter 11: Recreating security in XI R2.

Recreating scheduling jobs

A Broadcast Agent job can be migrated from BusinessObjects Enterprise 6.x
to XI R2 only if the job is supported in XI R2. (See “Non-supported jobs” on
page 298 for details.) If a document contains non-supported jobs, the import
of the document will fail.
If a job contains non-supported elements or features, you must drop the
feature or recreate it in the 5.x/6.x system before migrating the document.
When all features are consistent with the XI R2 platform, you can import the
job. You can also recreate non-migrated jobs in XI R2 using the CMC’s
broadcasting features.
As you recreate non-supported jobs manually, take into account that all XI R2
jobs include a refresh and a single output. To output a report to multiple
formats (such as PDF and XLS), you must create multiple jobs.

Non-supported jobs
In XI R2, the first action for scheduled documents is always a refresh.
Therefore, a job can be imported from 6.x only if its first action is a refresh.
A job cannot be imported if it has any of the following:
• multiple outputs
• conditional processing
• custom macros
You can, however, have embedded VBA macros (those that include calls
to the platform, such as Login or Logout, will need to be updated).
• report bursting (“refresh with the profile of each recipient”)
• saved in XML, RTF, HTML, or TXT format

298 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking and adapting the new environment
Verifying the Performance management environment 15
In addition, the following 6.x task scheduling options (in either
BusinessObjects or Web Intelligence) are not supported in XI R2:
Daily
• Week periodicity
Weekly
• Week periodicity
Monthly interval
• Business day
• Weekend day
• Month periodicity
User-defined
• Weekday
• Business day
• Weekend day
Note: The migrated document may be assigned a different periodicity in XI
R2.

Verifying the Performance management

environment
For recommendations on checking the new performance management
environment, refer to Best Practices for Migrating to BusinessObjects
Performance Management XI R2.

BusinessObjects 6.x to XI Release 2 Migration Guide 299

15 Checking and adapting the new environment
Verifying the Performance management environment

300 BusinessObjects 6.x to XI Release 2 Migration Guide

Checking for calculation
updates

chapter
16 Checking for calculation updates
Where you are now

Where you are now

Here is an overview of the migration process, and where you should be now.
The topics in blue are described in this chapter.

Where you Step in overall migration process

are now
1. Understanding what migration entails
2. Assessment and planning
3. Preparing for import
4. Importing from the source to destination environment
D 5. Post-import checking and tuning

• Document conversion during import

• BusinessObjects document migration

Document conversion during import

During the import to the XI R2 environment, the Import Wizard automatically
converts BusinessObjects (.rep) and Web Intelligence (.wqy and .wid)
documents to XI R2 format.
Depending on the type and version of the document, some differences in
format and even results may occur. This chapter explains those differences
and how you can correct them.

BusinessObjects document migration

Business Objects made several adjustments to the BusinessObjects
calculation engine in BusinessObjects 5.x and 6.x. The Desktop Intelligence
calculation engine is based on the BusinessObjects 6.5.1 calculation engine.
Note: The calculation engine is the part of the software that calculates report
results.
In certain circumstances, these adjustments mean that certain versions of
BusinessObjects reports can return different values when migrated to version
XI R2. This section helps you identify reports that might be affected and
explains the steps necessary to modify the reports.

302 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
There are two sets of calculation engine modifications: BusinessObjects 5.1.4
modifications and BusinessObjects 6.0 modifications. These two sets of
modifications are cumulative: if you migrate a report from BusinessObjects
5.1.3 to XI R2, the migrated report contains both sets of modifications.
This chapter also considers Desktop Intelligence modifications that do not,
strictly speaking, affect the calculation engine. Because these modifications
can affect report results in certain circumstances, it makes sense to consider
them here.
The following table contains a brief summary of all modifications:

Document version Calculation issues may arise if the documents

contain:
From 5.1.4 through • Multiple cubes and global filters
5.1.9 • Multiple cubes and complex filters
• Incompatible objects in the same block
• The NoFilter() function
Multiple cubes can occur either when the document
contains multiple data providers, or when a single
data provider contains multiple cubes.
Global filters are filters that apply to an entire report.
Complex filters are filters based on a formula (e.g.
Country <> “France”).
From 6.0 through 6.5 • Blocks with objects from different data providers
and the Count() function to count the rows in the
blocks
• Filters that apply to objects that contain 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
Desktop Intelligence • The UniverseName() function
• Unicode fonts
• Decimal precision

BusinessObjects 6.x to XI Release 2 Migration Guide 303

16 Checking for calculation updates
BusinessObjects document migration

BusinessObjects 5.1.4 modifications

BusinessObjects 5.1.4 modifications affect:
• global filters
• complex filters
• incompatible objects in the same block
• aggregation levels in synchronized data providers

Do you need to read this section?

You could be affected by these modifications if you have BusinessObjects
reports that contain the following:
• multiple data providers or a single data provider with multiple cubes, and
global filters
• multiple data providers or a single data provider with multiple cubes, and
complex filters
• incompatible objects in the same block

Global filters
Global filters are filters that apply to an entire report tab, as opposed to block
filters, which apply to specific blocks only. Global filters behave differently in
BusinessObjects 5.1.3 and 5.1.4+.
Are your reports affected?
If your reports contain global filters and multiple cubes, whether from single or
multiple data providers, your reports are affected by the change in global
filters behavior.
Global filters behavior in BusinessObjects 5.1.3
In this example a report has three data providers containing several linked
objects:
Data Provider 1: Country, Resort, Service, Service Line, Revenue
Data Provider 2: Country, Resort, Service, Service Line, Revenue
Data Provider 1: Country, Resort, City
The City object in Data Provider 3 is not linked to the other data providers, but
Country and Resort in Data Provider 3 are both linked to Country and Resort
of Data Provider 1 and 2.
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.

304 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
The first table is based on Data Provider 1, the second on Data Provider 2
and the third on Data Provider 3. The filter impacts the table based on Data
Provider 3 only: the table has no data because no row matches the filter
criterion.
Global filters behavior in BusinessObjects 5.1.4
BusinessObjects 5.1.4 behavior is modified to account for indirect filters. In the
example, indirect filtering means that all tables do not now show any data
because BusinessObjects indirectly applies the filter on table 3 to the other
two tables. It does this 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.
Obtaining BusinessObjects 5.1.3 results in BusinessObjects 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 can ensure that all tables are not filtered by applying the
filter City=’test’ to table 3 only. Note that 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 cannot apply the filter to it.
Desynchronizing the data providers
The other solution is to desynchronize the data providers. By removing the
links between them, you ensure that BusinessObjects will not apply the filter
indirectly to other data providers.

Indirect filters and calculations

The new indirect filters behavior has implications for calculations. In this
example, you have two data providers:
Data Provider 1: Country, Resort, Revenue
Data Provider 2: Country, Future Guests

BusinessObjects 6.x to XI Release 2 Migration Guide 305

16 Checking for calculation updates
BusinessObjects document migration

You have a report with three blocks. The third block contains the objects
Country (from Data Provider 1), Resort, Revenue and Future Guests. 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 get the
following result:

Country (DP1) Resort Revenue Future Guests

US Bahamas Beach $971,444 56
Sum: 102

The Sum for Future Guests is wrong in BusinessObjects 5.1.3 because the
indirect filters behavior is not implemented. In this case, 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.
Note: if you add a sum to the Future Guests column before applying the
complex filter, BusinessObjects still gives the figure 102, even though the
column contains three figures: 46, 56 and 56. For an explanation of this, see
“Aggregation levels in synchronized data providers” on page 312.
BusinessObjects 5.1.4 calculates the correct sum as follows:
• filter on the first data provider to get a list of rows that need to be
preserved.
• join this set of rows with the second data provider on the data providers’
linked dimensions. This join returns a row only if there is a row in each
data provider.
In the example:
• filter on Resort in the first data provider to return one row (US, Bahamas
Beach).
• join to the second data provider to return one row and the correct value
for Future Guests.

Complex filters
Complex filters are filters that are based on a formula, for example:
Country <> ‘France’

Are your reports affected?

If your reports contain complex filters and multiple cubes, whether from single
or multiple data providers, your reports are affected by the change in complex
filters behavior.

306 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
Complex filters in BusinessObjects 5.1.3
The complex filter algorithm in BusinessObjects 5.1.3 produced errors in
certain situations involving linked data providers. This had the following
symptoms:
• Incorrect display of lists of values
• Different behavior when filtering empty values
Lists of values in BusinessObjects 5.1.3
The following example looks at a list of values associated with a filter. Here
are the details of the report:
• Data Provider 1: Country, Quarter, Year, Revenue
• Data Provider 2: Country, Number of Guests
• The two data providers are synchronized on Country.
• A variable called Test whose formula references objects in both data.
• A complex filter with the formula Test<>’FRA’.
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 always the case.
When you open the report with BusinessObjects 5.1.4+, all values are
selected.
Note: BusinessObjects 5.1.3 and 5.1.4+ give the same results with simple
filters.
Empty values in BusinessObjects 5.1.3
The complex filters fix has implications for filtering on empty values. Before
the fix, this filtering occurred automatically. Now there is no automatic filter on
empty values in a multi-data provider report. The following example illustrates
this.
You have a simple report as follows:
• Data Provider 1: Country, Revenue
• Data Provider 2: Country, Revenue
• The second data provider has a query condition that restricts Country to
“US”.
This is the report display:

Country(DP1) Revenue(DP1)
France $835,420
US $2,451,104

BusinessObjects 6.x to XI Release 2 Migration Guide 307

16 Checking for calculation updates
BusinessObjects document migration

Country)DP2) Revenue(DP2)
US $2,451,104

Country(DP1) Revenue(DP2)
France
US $2,451,104
If you add a complex filter on Revenue on the third table,
<Revenue(DP2)> <> 2451104, BusinessObjects 5.1.3 takes the empty value into
consideration and the third table with synchronized data providers contains
one row:

Country(DP1) Revenue(DP2)
France

Empty values in BusinessObjects 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.
Obtaining BusinessObjects 5.1.3 results in BusinessObjects
5.1.4+
You make BusinessObjects 5.1.4+ behave like BusinessObjects 5.1.3 by
forcing it to account for empty values. To force BusinessObjects, you
incorporate an object from the first data provider into the filter definition. If you
change the filter definition in the above example to
(<Revenue(DP2)> <> 2451104) And (<Country(DP1)> = <Country(DP1)>)
the result is the same as the BusinessObjects 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
BusinessObjects 5.1.4+ contains changes that can affect reports containing
incompatible objects under certain circumstances. 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.

308 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
Determining if your reports are affected
If your reports have incompatible objects that appear in the same block, they
are affected by the change in incompatible objects behavior.
You can quickly tell if a report is affected. Open the Data Manager dialog box
by selecting Data > View Data on the menu.
The Data Manager shows the data cube or cubes that BusinessObjects uses
internally to build the report, and the objects within each cube. Each cube is
populated from one SQL query; if there is more than one cube, the report
contains multiple queries.
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.
If you have reports that satisfy these conditions, they are affected by the
incompatible objects fix in BusinessObjects 5.1.4+
You can further see why these objects are incompatible by examining the
Island Resorts Marketing universe, which 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:
Incompatible objects in BusinessObjects 5.1.3
A report 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:
• Sum Future Guests by Country by Reservation Year
• 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 dialog box. The Data Providers pane on the left shows the cubes
used in the report.
You can also examine the SQL generated by BusinessObjects in the SQL
Viewer dialog box that you access from the Query Panel:

BusinessObjects 6.x to XI Release 2 Migration Guide 309

16 Checking for calculation updates
BusinessObjects document migration

Internal handling of multiple cubes

When processing a report that contains multiple cubes, BusinessObjects
fuses all cubes into a single cube. For the above example, this cube is as
follows:

Country Year Reservation Future Revenue

Year Guests
France FY93 FY96 17 $295,940
France FY94 FY97 15 $280,310
France FY95 FY98 14 $259,170
US FY93 FY96 48 $767,614
US FY94 FY97 8 $826,930
US FY95 <empty> <empty> $856,560

There is no true relationship between the Year and Reservation Year objects
in this cube. The cube contains two different kinds of information, based
around the incompatible objects:
• Revenue by Country by Year
• Future Guests by Country by Reservation Year
This information is synchronized around the one common dimension –
Country, but the relationship between Year and Reservation Year for any row
is arbitrary.
Incompatible objects and filters
A problem arises if you apply a filter on, for example, the Reservation Year
column and exclude Year from the report. If you restrict Reservation Year to
‘FY96’ only, the cube produces the following data:

Country Reservation Future Revenue

Year Guests
France FY96 17 $295,940
US FY96 48 $767,614

In this situation the Revenue column clearly displays incorrect data. It shows
the revenues for France and US for FY93. But 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 US respectively, irrespective
of year. (That is, by Country - the other object on which Revenue is
aggregated.).

310 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
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
BusinessObjects has a function called NoFilter(). When you use this function,
BusinessObjects ignores any user-defined filters when performing
calculations. In BusinessObjects 5.1.3 NoFilter() could cause
BusinessObjects to ignore internal filters (filters applied by BusinessObjects
when processing cubes), resulting in incorrect results.
Incompatible objects in BusinessObjects 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. Furthermore, the NoFilter() function no longer causes
BusinessObjects to ignore internal filters. These changes ensure that the rare
occasions on which BusinessObjects could return incorrect data from blocks
with incompatible objects no longer occur.
Activating the fix
The incompatible objects fix is not active by default in BusinessObjects
5.1.4+. You activate it by setting values in the Windows registry. Because
each case of a potential incompatible objects problem is unique, you need to
discuss your particular case or cases with BusinessObjects Customer
Support, who will advise you which values to use for these registry settings.
The MultiCube() function
MultiCube() is a function that ensures that BusinessObjects takes all cubes
into account when performing calculations in reports that contain
synchronized queries. If you have used MultiCube() in your multi-cube reports,
you should not remove it even after activating the BusinessObjects 5.1.4 fix.
You still need to use MultiCube() in BusinessObjects 5.1.4.

BusinessObjects 6.x to XI Release 2 Migration Guide 311

16 Checking for calculation updates
BusinessObjects document migration

Aggregation levels in synchronized data providers

Whenever you work with synchronized data providers, you must pay close
attention to the structure and semantics of your data, because certain
anomalies can arise from the data structure rather than limitations in
BusinessObjects. “Indirect filters and calculations” on page 305 gives an
example of this. Remember that there are two data providers:
Data Provider 1: Country, Resort, Revenue
Data Provider 2: Country, Future Guests
You build a block that contains dimensions and measures from both data
providers:

Country(DP1) Resort Revenue(DP1)

France French Riviera $835,420
US Bahamas Beach $971,444
US Hawaiian Club $1,479,600

Country(DP2) Future Guests

France 46
US 56

Country(DP1) Resort Revenue(DP1) Future Guests

France French Riviera $835,420 46
US Bahamas Beach $971,444 56
US Hawaiian Club $1,479,600 56
Sum: 102
Count: 3 Count: 2

The Sum and Count figures for the Future Guests column are clearly
anomalous. The point to note is that 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. 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. BusinessObjects is then able to
calculate Future Guests correctly.

312 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
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, you need to make sure that the measure data provider contains
all the compatible dimensions in the block. This ensures that the measure is
aggregated at the correct level in the block.

BusinessObjects 6.0 modifications

BusinessObjects 6.0 modifications affect:
• The Count() function
• Filtering on empty values
• Filters on master detail reports containing incompatible objects
• Rankings
• The NoFilter() function
• Duplicate row aggregation

Do I need to read this section?

You need to read this section if you have reports that contain any of the
following:
• Blocks with objects from different data providers and the Count() function
to count the rows in the blocks
• Filters that apply to objects that contain 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

The Count() function

Count() is a BusinessObjects function that calculates the number of rows in a
data provider.
Are your reports affected?
Your reports are 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 6.x to XI Release 2 Migration Guide 313

16 Checking for calculation updates
BusinessObjects document migration

BusinessObjects splits the query into two or more cubes in order to resolve it.
You do not control the creation of multiple cubes; BusinessObjects does this
internally.
Multiple data providers occur when you explicitly create more than one cube
in a report, by building the report from more than one data provider.
The Count() function in BusinessObjects 5.x
In this example your report contains two data providers:
Data Provider 1: Country, Year, Reservation Year, Number of Guests
Data Provider 2: Country
When you run DP1, BusinessObjects cannot resolve it with a single query
because the Year and Reservation Year objects are incompatible.
BusinessObjects creates two cubes: (Country, Year, Number of Guests) and
(Country, Reservation Year). As a result your report has three cubes in total:
DP1 Cube 1: Country, Year, Number of Guests
DP1 Cube 2: Country, Reservation Year
DP2: Country
It is this combination of multiple cubes and data providers that causes the
Count() function to return different results in BusinessObjects 5.x and 6.0. If
you create a block that contains the Country object from DP2 and the Number
of Guests object from DP1, then apply the Count() function to the Number of
Guests column, you get the following result:

Country Number of Guests

Australia
France 446
Germany
Holland
Japan
UK
US 1105
Count: 7

In this situation 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 315 for an
explanation of empty values.) BusinessObjects 5.x counts these empty
values when performing calculations using the Count() function.

314 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
The Count() function in BusinessObjects 6.0
BusinessObjects 6.0 no longer counts the empty values, with the result that
the Count() function for this block returns 2 rather than 7.
Obtaining BusinessObjects 5.x results in BusinessObjects 6.0
To obtain BusinessObjects 5.x results you need to 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(DP2)>) you get the BusinessObjects 5.x result:

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
Are your reports affected?
If you have reports with filters on objects that return empty values, they are
affected by the enhancement to BusinessObjects filter capability.
BusinessObjects 5.x and 6.0
In BusinessObjects 5.x it is not possible to select an empty value when
creating a filter. BusinessObjects 6.0 allows you to include the empty values
in the filter definition, which 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.0 in master/detail reports that
contain incompatible objects in the section header and body.
Are you reports affected?
Your reports are affected by this issue if they contain incompatible objects that
appear in the header and body sections of a master/detail report.
The following is a BusinessObjects 5.x example:
You have 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.

BusinessObjects 6.x to XI Release 2 Migration Guide 315

16 Checking for calculation updates
BusinessObjects document migration

If you apply a filter on Reservation Year, for example Reservation Year=”FY98”,

the filter also causes the entire contents of the block in the section body to be
filtered.
In BusinessObjects 6.0, the filter on the object in the section header does not
affect the objects in the section body:

Rankings in blocks with different data providers and empty values

In BusinessObjects 6.0, ranking returns correct sub-totals in reports from
rankings on blocks that contain objects from different data providers and
empty values.
Are your reports affected?
Your reports are affected by this issue if they contain rankings with sub-totals
in blocks that contain
• objects from different data providers
• empty values
In this BusinessObjects 5.0 example you have a report with two data
providers:
Data Provider 1: Country
Data Provider 2: Country, Resort, Number of Guests
Your report has a block that contains Country (DP1), Resort and Number of
Guests. You rank the top country by Number of Guests and include sub-totals
in the ranking.

US Bahamas Beach 565

US Hawaiian Club 540
Sum: 1105
Sum Other: 446
Sum All: 1551

The Sum and Sum Other totals are incorrect. Sum totals all Number of
Guests figures in the report, rather than those left in the block by the ranking,
and Sum Other does not include the figures excluded from the block by the
ranking.
These sums are correct in BusinessObjects 6.0.

316 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
The NoFilter() function with a Where clause
NoFilter() is a function that tells BusinessObjects to ignore all filters when
calculating a value.
Are your reports affected?
Your reports are affected by this issue if they use the NoFilter() function with a
Where clause.

NoFilter()…Where in BusinessObjects 5.x

You have 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 BusinessObjects 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 BusinessObjects 6.0
In BusinessObjects 6.0, the position of the NoFilter() parentheses is critical.
NoFilter (Sum(<Revenue>) Where (<Resort>="Bahamas Beach"))
returns the same value as BusinessObjects 5.x, but
NoFilter ((Sum(<Revenue>)) Where (<Service>="Excursion")
returns an empty value. When you use the second syntax, BusinessObjects
does not apply NoFilter() function to the sum before applying the Where clause.
As a result, BusinessObjects returns an empty value, because the application
of the filter (Service=”Bungalow”) followed by the Where clause
(Service=”Excursion”) excludes all revenue values.
Obtaining BusinessObjects 5.x results in BusinessObjects 6.0
To obtain BusinessObjects 5.x results, ensure that your NoFilter()…Where
functions or variables use the syntax that returns the same result as
BusinessObjects 5.x.

BusinessObjects 6.x to XI Release 2 Migration Guide 317

16 Checking for calculation updates
BusinessObjects document migration

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.
BusinessObjects 5.x BusinessObjects 6.0 behavior
In this example you have two data providers:
Data Provider 1: Customer, Reservation Year
Data Provider 2: 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 and include duplicates by selecting the
Avoid Duplicate Rows Aggregation option, BusinessObjects ignores the sort
on Customer.
When you exclude duplicate rows from the table by deselecting the option,
BusinessObjects sorts the table on the Customer object.
BusinessObjects 6.0 applies the sort whether or not the Avoid Duplicate
Rows Aggregation option is selected.

Desktop Intelligence XI R2 modifications

The UniverseName() function
The UniverseName() function now returns the short name of a universe, rather
than the long name. For example, where the function previously returned
“Island Resorts Marketing“, it now returns “beach“.
This change could affect the overall report size if the Autofit properties of the
cell containing the function are enabled. The size of Autofit cells changes in
relation to the data they contain, and the change in cell size might affect the
size of the whole report. Changes in report size could in turn affect functions
whose output relates to the report size, for example NumberOfPages().

Unicode fonts
The sizes of the Unicode fonts used by Desktop Intelligence are not identical
to the sizes of the corresponding non-Unicode fonts. This might have the
following impacts:
• Data in cells which previously displayed all the cell data is now truncated,
resulting in ###s to denote the truncation.

318 BusinessObjects 6.x to XI Release 2 Migration Guide

 Checking for calculation updates
BusinessObjects document migration 16
• Functions that return data relating to the report size - for example
NumberOfPages() - might return different values in reports with cells whose
Autofit properties are enabled. The size of Autofit cells changes in
relation to the data they contain, and these changes in cell size might
affect the size of the whole report.
• Reports are not identical when compared in a pixel-by-pixel comparison.

Decimal precision
Desktop Intelligence supports up to 24 decimal places, as opposed to 10 in
previous versions. This increased precision might affect the output of some
functions, in particular the euro conversion functions.

BusinessObjects 6.x to XI Release 2 Migration Guide 319

16 Checking for calculation updates
BusinessObjects document migration

320 BusinessObjects 6.x to XI Release 2 Migration Guide

Appendices
322 BusinessObjects 6.x to XI Release 2 Migration Guide
BusinessObjects 6.x to XI Release 2 Migration Guide

Migration checklist for single

pass migrations

appendix
A Migration checklist for single pass migrations
Overview

Overview
This appendix provides a migration checklist that you can print out and check
off as you go through a single pass migration.
The items in this checklist do not necessarily need to be performed in the
order in which they appear.

About incremental migrations

The incremental migration approach includes one-off procedures, such as
preparing the source and destination environments, as well as the iterative
procedures that constitute the progressive phases in your overall migration.
The range of potential incremental migration strategies is so vast, however,
that it is not possible to provide a generic migration checklist.

Preparing the source environment

❏ Using Supervisor, run a Repair and Compact on your source repository.
❏ Back up resources stored on the server.
❏ Export resources stored on local machines to the repository.
❏ Back up the Application Foundation repository. Business Objects
recommends you run the Import Wizard on this repository copy.
❏ Back up any custom web applications, HTML pages, or scripts that you
have added to the existing deployment.
❏ Update platforms or versions of all third-party components if required for
XI R2 support.
❏ Make sure both web server and application server software is functioning
and available for your new environment.
❏ If you are going to create a new repository using something other than
the MySQL default databases provided by XI R2 installation, set up your
new repository database according to the list of supported platforms
(http://support.businessobjects.com/supported_platforms_xi_release2/).
❏ Document all source environment database/connection/network/
repository/security/scheduling information.

324 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration checklist for single pass migrations
Preparing the destination environment A
Preparing the destination environment
❏ Close any other programs running locally on the destination deployment
machines before installing BusinessObjects Enterprise.
❏ Install at least one BusinessObjects Enterprise CMS (Central
Management Server).
❏ If you are planning to use Desktop Intelligence, install it on the required
client machines.
❏ If you have not already installed it as part of the overall XI R2 installation,
install the Import Wizard on a Windows machine.
If your BusinessObjects Enterprise deployment is running on UNIX, map
the Import Wizard drives to the UNIX environment.
❏ Make sure the Import Wizard can access any data source in the source
repository.
❏ On the Import Wizard machine, map the drives to the source environment
directories containing the deployment’s .key/.rkey files, personal
documents and categories, and users’ Inboxes.
If your BusinessObjects Enterprise deployment is running on UNIX, tar
the source personal and Inbox documents and import them onto the
Import Wizard machine, unzip them, and then map the machine’s drives
to the appropriate local folders.
❏ If you have any content in the target CMS database, back it up.
❏ If you are migrating Application Foundation, ensure that the
AFScheduleProgram is present in the destination CMS before you
migrate. If the AFScheduleProgram is not available, and you migrate the
repository, you could lose the schedules in the source repository during
migration. This step is particularly important if you recreate the
destination CMS after installation.
❏ Start at least the Central Management Server, the Input File Repository
Server, and the Output File Repository Server in the destination
deployment.
❏ If you use an external lightweight directory access protocol (LDAP)
provider for authentication, configure the LDAP security plug-in using the
CMC in the XI R2 system.

BusinessObjects 6.x to XI Release 2 Migration Guide 325

A Migration checklist for single pass migrations
Importing from the source to destination environment

Importing from the source to destination

environment
❏ Check the list of import constraints.
❏ Launch the Import Wizard.
❏ Set the source and destination environments.
❏ Select and then import all required BI suite, and if appropriate,
Application Foundation-specific objects.

Post-import checking and tuning

❏ Evaluate the import’s success using:
• the Import Wizard log file
• the CMC
• Query Builder
❏ Correct any problems indicated in the Import Wizard log file, and then re-
import the objects that were not imported during the first run due to import
errors.
❏ In the target repository, set up a new folder and group structure to prevent
security breaches once users begin publishing documents to the
repository.
Move the appropriate users into the new group structure, and documents
into the new folder structure.
❏ If you have imported security, ensure that the security settings are
mapped as required, using the CMC. Depending on the option you chose
in the Security Migration Options dialog box, either restrict or allow more
access to objects for the Everyone group.
❏ If you have not imported security, recreate the new security framework.
❏ If you have integrated document-to-document links using openDoc in
BusinessObjects or Web Intelligence documents, manually re-establish
those links in Desktop Intelligence and Web Intelligence. Check
international settings both for the environment and for documents (locale,
etc.).
❏ Start InfoView and check imported universes and documents. Check and
if necessary, tweak imported .rep files, for example, re-establish report-
to-report linking. Check converted .wqy to .wid files.

326 BusinessObjects 6.x to XI Release 2 Migration Guide

 Migration checklist for single pass migrations
Transferring or recreating other functions and tasks A
Transferring or recreating other functions
and tasks
If required:
❏ Recreate non-migrated Broadcast Agent Scheduler jobs using CMC
broadcasting features.
❏ Recreate any BusinessObjects documents you decided not to import, but
instead recreate using Crystal Reports.
❏ Configure BusinessObjects Enterprise’s auditing facilities to meet your
requirements.
❏ Recreate BusinessObjects OLAP reports with Web Intelligence or Crystal
Reports.
❏ Recreate Web Intelligence OLAP documents with OLAP Intelligence.
❏ Recreate BusinessQuery documents with Live Office.
❏ Replicate customization.

BusinessObjects 6.x to XI Release 2 Migration Guide 327

A Migration checklist for single pass migrations
Transferring or recreating other functions and tasks

328 BusinessObjects 6.x to XI Release 2 Migration Guide

Business Objects
Information Resources

appendix
B Business Objects Information Resources
Documentation and information services

Documentation and information services

Business Objects offers a full documentation set covering its products and
their deployment. Additional support and services are also available to help
maximize the return on your business intelligence investment. The following
sections detail where to get Business Objects documentation and how to use
the resources at Business Objects to meet your needs for technical support,
education, and consulting.

Documentation
You can find answers to your questions on how to install, configure, deploy,
and use Business Objects products from the documentation.

What’s in the documentation set?

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

Where is the documentation?

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

Documentation from the products

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

Documentation on the web

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

Documentation on the product CD

Look in the docs directory of your product CD for versions of guides in Adobe
PDF format.

330BusinessObjects 6.x to XI Release 2 Migration Guide

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

Customer support, consulting and training

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

How can we support you?

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

Online Customer Support

The Business Objects Customer Support web site contains information about
Customer Support programs and services. It also has links to a wide range of
technical information including knowledge base articles, downloads, and
support forums.
http://www.businessobjects.com/support/

BusinessObjects 6.x to XI Release 2 Migration Guide331

B Business Objects Information Resources
Customer support, consulting and training

Looking for the best deployment solution for your

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

Looking for training options?

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

332BusinessObjects 6.x to XI Release 2 Migration Guide

 Business Objects Information Resources
Useful addresses at a glance B
Useful addresses at a glance

Address Content
Business Objects product Information about the full range of
information Business Objects products.
http://www.businessobjects.com
Product documentation Business Objects product
http://www.businessobjects.com/ documentation, including the
support Business Objects Documentation
Roadmap.
Business Objects Documentation Send us feedback or questions
mailbox about documentation.
documentation@businessobjects.com
Online Customer Support Information on Customer Support
http://www.businessobjects.com/ programs, as well as links to
support/ technical articles, downloads, and
online forums.
Business Objects Consulting Information on how Business
Services Objects can help maximize your
http://www.businessobjects.com/ business intelligence investment.
services/consulting/
Business Objects Education Information on Business Objects
Services training options and modules.
http://www.businessobjects.com/
services/training

BusinessObjects 6.x to XI Release 2 Migration Guide333

B Business Objects Information Resources
Useful addresses at a glance

334BusinessObjects 6.x to XI Release 2 Migration Guide

Index
Symbols Administrators (XI R2 user group) 68, 68
@Variable('BOPASS') 91 aggregation
@Variable('BOUSER') 91 of rights in 5/6 vs. XI R2 71
rules per right type 122
universe access restrictions 122
A agnostic documents
Access Control Entities see ACEs importing 98
Access Control Lists see ACLs Allow user to merge dimension for synchronization
access rights see rights right 96
ACEs analytics
defined 21, 69 migrating 110
on import of stored procedures 93 Application Foundation
on import of universe-related security checking universe integrity 103
commands 89 importing objects incrementally 107
ACLs migrating analytics 110
as benefit of XI R2 security 226 migrating dashboards 108
defined 69 migrating named events 112
on import of Application Foundation objects migrating objects without the repository 106
113 migrating rules 112
overview 21 migrating schedules 111
universe security 201 migrating security commands 113
ActiveDirectory 51 migration 100–115
add-ins migration overview 28
migration 95 migration paths 103
administration object migration 97
5/6 vs. XI R2 52 objects that migrate 104
Administration Console repository upgrade during migration 25
Audit facility 54 resource migration overview 31
enabling servers 54 rules containing actions requiring pre-
scheduling 55 rendering 115
setting authentication 50 SVG files 109
setting locale 55 Application Foundation objects 265
settings migration 83 Application Foundation repository
tasks assumed by CMC in XI R2 20 changes in performance management
Administration Launchpad 293 repository 105
Administration SDK 206 ci_task table 111, 111
available sample application 55 contents 105
administrators importing repository connections 108
in recreated security model 219 migrating 104

BusinessObjects 6.x to XI Release 2 Migration Guide 335

Index

modification during import 101 B

Application Foundation Repository Update dialog backing up repository 253
box 275 BIAR files 16, 224
application rights defined 232
after BusinessObjects migrations 151 in incremental migrations 224
after Designer migration 161 bomain.key file 50
after WebIntelligence migrations 155 Broadcast Agent
and full collapse 129 capturing scheduling information 238
defined 120 File Watcher 43
migration 128 migration overview 27
migration of 5/6 security commands 73 non-supported jobs 298
application servers tasks assumed by CMC in XI R2 20
and Desktop Intelligence deployments 193 Broadcast Agent Console
role in 5/6 and XI R2 46 capturing scheduling information 238
terminology in XI R2 43 viewing scheduled tasks 55
applications Broadcast Agent dialog box 270
importing application by application 224 Broadcast Agent Publisher
appsecurity.exe functionality in XI R2 205
custom security commands 113 migration 30
auditing Broadcast Agent Scheduler
5/6 vs. XI R2 54 job migration 30
how different in XI R2 203 Broadcast Agent schedules
setting up in destination system 259 related to Application Foundation 115
Auditor Business Objects
analyzing which objects are used 239 consulting services 332, 333
capturing scheduling information in source support services 331
environment 238 training services 332, 333, 333
dashboard capabilities 203 Business Objects consulting 17
indicators 203 Business Objects servers
migration assessment 203 equivalent in XI R2 42
migration overview 27 Business Objects web services 206
tasks assumed by CMC in XI R2 20 BusinessObjects 83
authentication how Desktop Intelligence differs 194
multiple authentication schemes in XI R2 229 migration of document rights 95
version 5/6 vs. XI R2 49 migration overview 26
authorization rights migration 146–155
5/6 vs. XI R2 51 scheduling 58
Autofit setting authentication in 2-tier mode 50
and impact on Desktop Intelligence what does migrating involve? 197
documents 318 BusinessObjects 5.1.3
in imported Web Intelligence documents 294 and empty values 307, 307
Autofit cells and incompatible objects 309
different values in Unicode 196, 294 and lists of values 307
BusinessObjects 5.1.4+
and empty values 308

336 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

and incompatible objects 311 Central Management Server see CMS

BusinessObjects 5.x checking locale
and Count() function 314 in Web Intelligence documents 295
BusinessObjects Auditor see Auditor ci_rule table 112
BusinessObjects documents Client SDK 206
how Autofit can change in Desktop cluster nodes 43
Intelligence 318 clusters
import limitations 95 and repositories in XI R2 186
importing 94 CUID 171
migrating OLAP data providers 95 heterogeneous 45
migration of rights 95 multiple with single repository 188
re-establishing report-to-report links 295 setting locale 55
Show/Hide object feature 240 starting/stopping 54
troubleshooting failed import 295 version 5/6 vs. XI R2 42
Unicode and sorts 196, 294 CMC
Unicode implications 196 as administration tool 52
when to rewrite using Crystal Reports 240 auditing 54, 203
when you should convert to .wid 240 category management 57
which ones you should migrate 239 checking group membership 219
BusinessObjects Enterprise SDK 61 checking group rights on folders 217
BusinessObjects OLAP checking user/group import 292
migration 30 logging on 258
BusinessObjects SDK overview 20
Send to BCA 95 password restrictions 69
Send to Inbox 95 performance management object rights 114
BusinessQuery performance management user rights 114
migration overview 27 publishing 205
BusinessQueryMD publishing to repository 59
migration 30 scheduling 204
security management overview 22
C setting authentication 50
universe security 201
calculations
user/group creation 53
checking after import 293
user/group organization 68
categories
viewing scheduled objects 55
5/6 vs. XI R2 57
CMS 96, 97, 265
selecting for import 271, 282
and Application Foundation objects 101
Categories dialog box 271
authentication 50
Categories folder 93
backing up database 257
CCM
clusters 42
as administration tool 52
deployment rules 186
enabling/disabling CMSs 54
ensuring Import Wizard can connect 258
repository creation 46
InfoObjects 19
starting CMSs 54
installing Import Wizard on CMS machine 255
Central Configuration Manager see CCM
license key storage 53
Central Management Console see CMC

BusinessObjects 6.x to XI Release 2 Migration Guide 337

Index

overview 18, 42 Crystal Reports SDK 62

Performance Management repository 103 cubes
repository 41 filtering 311
repository creation 48 multiple 309
Schedule Manager 111 CUIDs 89, 96
storage of users and groups 72 as basis for import identification 171, 172
Unicode 49 for dashboards 109
CMS scheduler 111 custom rights 119
command-line installation 46 customer support 331
Compact 247
compatibility D
Designer 200
Dashboard Manager
complex filters 304, 306
Schedule HTML generation option 115
and BusinessObjects 5.1.3 307
dashboards
reports affected by 306
migrating 108
connection rights
migrating security 109
full collapse 145
requiring pre-rendering in .rep files 115
migration 145, 164
Dashboards dialog box 281
Connection Server
Data Integrator 38
and performance management 108
updating 256
connections
data sources
BOUSER/BOPASS variables 91
creating on destination server machines 254
how the Import Wizard imports 89
databases
migration overview 30
changing query databases 238
stored procedures 93
changing repository databases 237
to Application Foundation repository 108
migrating 31
connectivities
supported in XI R2 253
recreating in XI R2 253
synchronizing enterprise and database
consultants, Business Objects 332
credentials 91
converting
Unicode 49
.rep files to .wid 94
using the DBUSER/DBPASS variables 91
.rep files to .wqy 94
Delegated Administration
corporate document domains
and universe access restrictions 76
equivalent in XI R2 43
establishing 76
corporate documents
deployment
storage after import 85
rules in XI R2 184
Count() function 313, 314
supported configurations in XI R2 25
and BusinessObjects 6.0 315
deployment configurations
Crystal Reports
migrating 188
audit reports 203
derived universe 90
customizing 62
Designer
data sources 56
5/6 and XI R2 compatibility 90
scheduling 58, 204
5/6 vs. XI R2 54
when to rewrite BusinessObjects reports in
and access restrictions in XI R2 92
240
checking access restrictions post-import 296

338 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

compatibility with other versions 200 migration 132

customizing in XI R2 62 document passwords 95
migration assessment 199 documentation
migration overview 26 feedback on 331
rights migration 161–164 on product CD 330
security management in XI R2 22 on the web 330
universe access restrictions in XI R2 202 roadmap 330
Designer (user profile) 67 documents
Designer SDK 62, 206 deleting using Compact 247
Desktop Intelligence importing 93
and scheduling 195 importing without locales 94
and universes 196 migration overview 29
and VBA macros and add-ins 195 modifications during import 25
BusinessObjects rights migration to 146–155 net access 139
compatibility between versions 196 specifying default locale for import 246
customizing 62 domain access rights 121
default values for rights 149 and full collapse 132
deployment 193 default and aggregate rules 122
deployment configurations 25 defined 121
how different than BusinessObjects 194 standard migration path 127, 127
installing 3-tier deployments 194 Domain Key file 264
look and feel 194 domains
report-to-report linking 198, 199 how they migrate 24
scheduling 58, 204 importing 93
setting document locale 194 importing domain by domain 224
UniverseName() function 318 importing universe domains 90
Desktop Intelligence documents selecting for import 271, 282
accessing through InfoView 196 Domains and Documents dialog box 271
changes with Unicode 196, 294 duplicate row aggregation 318
setting locale 194
Desktop Intelligence SDK 62, 206, 207 E
Destination Environment dialog box 265
Edit SQL right 96
detail log 273, 285
education. See training
Detail Log dialog box 291
empty values
Developer Suite
and BusinessObjects 5.1.3 307, 307
migration overview 28
and BusinessObjects 5.1.4+ 308
version 5/6 offering 60
filtering on 315
directed acyclic graph (DAG) 68
Enable Password Modification flag security
distributed deployments
command 74
version 5/6 vs. XI R2 45
Enable real time user rights update security
document access rights
command 74
default and aggregate rules 122
Enabled/Disabled security command 74
migration 139
Enterprise authentication 51
net access 139
Event Server 43
document domain rights
and performance management rules 112

BusinessObjects 6.x to XI Release 2 Migration Guide 339

Index

Everyone (XI R2 user group) 68 checking group rights on folders 217

post-import security settings 296 checking membership 219
Excel creation in 5/6 vs. XI R2 53
Save as Excel as scheduling option 204 default groups in XI R2 22
exporting objects 253 impact of Merge/Update import scenarios 75
importing 269
F migrating 72
migration overview 22
Favorites folder 43, 85
organization 67
feedback, on documentation 331
post-import checking 293
File Repository Server see FRS
principal 120
File Watcher 43, 204
using inheritance in XI R2 212
filters
which you should migrate 238
and incompatible objects 310
Guest (XI R2 user) 68
complex 306
GUID 171
inmaster/detail reports 315
finalizing the import 273, 273, 285, 285
folders H
checking group rights on in XI R2 217 heterogeneous clusters 45
Universe 90
fonts I
Unicode differences 196, 294
Identification strategy security command 74
FRS
Impact Analysis 203
and geographical distribution 188
import
connection storage 89
troubleshooting failed document import 295
defined 19
Import Groups Option dialog box 269, 280
deployment 185
Import Options for Universes and Connections
object storage 41
dialog box 271
full collapse
Import Progress dialog box 273, 285, 291
and application rights 129
Import Universe and Connection Objects Options
and connection access rights 145
dialog box 283
and domains 132
Import Wizard
functions
and BIAR files 224
Count() 314
and third-party documents 98
MultiCube() 311
BIAR files 16
checking the log file 291
G Detail Log dialog box 291
General Supervisor 67 ensuring connection to the CMS 258
migration to XI R2 23 ensuring correct installation 257
General Supervisor login 265 high-level migration scenarios 227
global filters 304, 304 how it compares source and destination
and BusinessObjects 5.1.3 304 objects 170
and BusinessObjects 5.1.4 305 how it imports analytics 110
groups how it imports Application Foundation 100
access rights 69

340 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

how it imports Application Foundation object objects without rights 169

security 113 objects’ content or rights 173
how it imports Application Foundation objects post-import checks 290
104 post-import verification 25
how it imports Application Foundation security or not 225
repository connections 108 selecting objects 265
how it imports Application Foundation rules setting default document locale 273, 284
112 universes 200
how it imports dashboards 108 updating the destination environment 267,
how it imports documents 93 277
how it imports domains 93 users and groups 74, 269
how it imports universe connections 90 ImportWiz.log file 291
how it imports universes and connections 89 ImpWiz.exe 257, 263
how it migrates Application Foundation Inbox documents
schedules 111 importing 267, 277
Import Progress dialog box 291 mapping Import Wizard to 257
incremental migration options 225 migrating 29
installing 255 storage after import 85
launching 263 incompatible objects 304, 308
limitations 83 and BusinessObjects 5.1.3 309
location of objects for import 83 and BusinessObjects 5.1.4+ 311
mapping to Inbox and personal files 257 and filters 310
Merge and Update scenarios 169 reports affected by 309
optimizing performance 255 incremental import 223
options explained 166 initial import 223
overview 15 of Application Foundation objects 107
pre-import steps 252 ongoing updates 224
recommended hardware 16 Update import scenario 172
requirements 15 updating contents/rights of objects 173
security migration options 166 indicators 203
Security Migration Options dialog box 167 indirect filters
setting source and destination environments and calculations 305
264 InfoObjects
specifying default document locale for import defined 19
246 Information Collection Complete dialog box 269
importing information resources 330
categories 271, 282 InfoView
checking user import 293 deployment 56
choosing an import scenario 267, 277 Desktop Intelligence document access rights
domains 93 196
Import Wizard options explained 166 managing settings 55
mapping Import Wizard to Inbox and personal migration overview 27
documents 257 publishing 205
Merge and Update scenarios 169 scheduling 204
merging environments 267, 277 setting locale 55

BusinessObjects 6.x to XI Release 2 Migration Guide 341

Index

XI R2 dashboard capabilities 203 importing documents without locales 94

XI R2 look and feel 198 importing locale by locale 224
inheritance migration of universe 89
overriding 71 setting 55
using group inheritance in XI R2 212 setting default document locale for import 273,
using to recreate security in XI R2 217 284
installation setting Desktop Intelligence document locale
command-line 46 194
ensuring correct Import Wizard 257 specifying default document locale 246
OLAP products 47 Locales and Platform Options dialog box 273, 284
options in 5/6 and XI R2 45 log file 290
required rights 257 Import Wizard 290
silent 46 Login security command 74
installing LOVs
Import Wizard 255 access from XI R2 98
XI R2 254 migration 201
Interactive Editing right 96
Interactive Metric Trends (IMT) 208 M
Merge import scenario 171
J and users/groups 75
Job Server 43 merging repositories 228
merging source and destination environments 171
K migrating
analytics 110
Keep universe overloads 272
Application Foundation 100, 104
.key files
Application Foundation rules 112
and Desktop Intelligence 194
Application Foundation schedules 111
Auditor 203
L BusinessObjects 193–198
LDAP BusinessObjects documents 94
attribute variables 78 connections 90
configuring security plug-in 259 dashboards 108
migrating to XI R2 77 defined for third-party software 237
migration 77 deployment configurations 188
license key management 47 Designer 199
licensing in XI R2 24 documents 93
life-cycle management documents (overview) 29
using the Update import scenario 230 domains 93
List of Values see LOVs domains (overview) 28
lists of values in a single pass with the Import Wizard 223
and BusinessObjects 5.1.3 307 incrementally 223
locale LDAP 79
and .wqy files 97 managing licensing 24
checking in Web Intelligence documents 295 Merge and Update import scenarios 169
format 246 objects without their rights 169

342 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

security or not 225 single pass 223

setting up new folder structure 241 standard path for user rights 125
third-party documents 98 stored procedure rights 145
to new query databases 31 stored procedures 164
to new repository database 31 top challenges 20–26
top challenges 20–26 troubleshooting schedule migration 111
universes 199 universe access rights 139
users with designer rights 202 universe domain rights 132
using consulting 17 user parameters 69
WebIntelligence 198 user profiles 72
WebIntelligence OLAP 208 what migrates and what doesn’t 26–31
migration which objects you should migrate 239
and BIAR files 224 which users/groups should you migrate? 238
Application Foundation objects 104 migration assessment
Application Foundation repository 25 Auditor and auditing 203
application rights 128 BusinessObjects/Desktop Intelligence 193
assessment and planning 33 Designer and universes 199
broad phases 31 publishing 205
capturing source scheduling information 238 scheduling 204
connections 145 SDKs 206
custom applications 28 WebIntelligence OLAP 208
databases 31 WebIntelligence/Web Intelligence 198
document access rights 139 migration method
document domain rights 132 incremental 223
domains 24 single pass 223
formulating strategy 222 migration planning
handling locales 94 capturing source scheduling information 238
high-level migration scenarios 227 checking supported platforms and versions
Import Wizard options explained 166 237
Inbox documents 29 choosing a migration method 223
incremental 223 import security or not 225
initial import 223 repository migration scenarios 228
LDAP 77 what objects you should migrate 239
merging environments 171 which users/groups should you migrate? 238
methods (overview) 17 migration strategy
of groups 72 formulating 222
of rights 118–164 high-level scenarios 227
of users 72 modules
ongoing updates 224 equivalent in XI R2 41
overview of resource migration 28 Multicube() function 311
personal documents 29 multiple cubes
post-import verification 25 internal handling of 310
repository migration options 228 MySQL 46
security commands 73
security migration options 166

BusinessObjects 6.x to XI Release 2 Migration Guide 343

Index

N P
.NET Server Controls for BusinessObjects Password security command 74
Enterprise 61 Password Validity settings security command 74
Netegrity SiteMinder 51 passwords
NoFilter() function 311 using the DBUSER/DBPASS variables 91
and Where clause 317 performance management 28
and Where clause in BusinessObjects 5.x 317 managing use rights 114
and Where clause in BusinessObjects 6.0 317 PIKs 208
Not Specified option repository 105
best practices 216 security migration limitations 115
troubleshooting schedule migration 111
O what you cannot migrate 114
what’s new in XI R2 207
object IDs 92
performance management engines 108
Object Security level security command 74
performance management repository 97
objects
Personal Categories folder 93
CUID 171
personal document domains
exporting 253
equivalent in XI R2 43
restrictions 92
personal documents
rights 121
importing 267, 277
selecting for import 265
mapping Import Wizard to 257
storage 41
migrating 29
which should you migrate? 239
storage after import 85
OLAP
planning see migration planning
document migration overview 30
Platform COM SDK 95
installation of OLAP products 47
platform support
OLAP data providers
list of supported platforms 31
and Desktop Intelligence 194
platforms
OLAP Intelligence
updating 253
scheduling 58, 204
XI R2 platform and version support 237
ONAMES 254
Populate Database Credentials dialog box 270
Online Customer Support 331
Populate Database Credentials for Users dialog
Only look for documents in personal inbox option
box 280
115
Portal Integration Kits
openDoc
for performance management 208
document-to-document links 295
predefined settings 74
Oracle
pre-rendering
ONAMES 254
and Application Foundation dashboards 115
TNSNAMES 254
primary nodes 43
ORB
principals
configuring 47
defined 66, 120
configuring in version 5/6 46
Process Tracker
orphan documents
what’s new in XI R2 208
defined 94
product access rights
default and aggregate rules 122

344 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

defined 120 backing up 253

standard migration path 126 changing databases for migration 237
products creating 48
version 5/6 vs. XI R2 offering 37 creation in 5/6 vs. XI R2 46, 53
profiles determining ID 229
how they migrate 72 exporting locally-stored objects 253
in version 5/6 44 geographically-distributed 188
in XI R2 44, 205 GUID 171
migration to XI R2 23 migrating to different repository database 31
Public folder 43, 85 migration options 228
publishing publishing to 59
in XI R2 205 Repair and Compact before import 252
profiles in XI R2 205 version 5/6 vs. version XI R2 19
Publishing Wizard 59 when multiple source repositories have the
same ID 229
Q resources 330
restriction sets see universe access restrictions
Query Builder tool 198, 293
.ret files
query databases
and migration 94
migrating 31
rights
5/6 vs. XI R2 aggregation rules 122
R 5/6 vs. XI R2 defaults 122
.rea files 5/6 vs. XI R2 inheritance 123
access from XI R2 98 aggregation in 5/6 vs. XI R2 71
migration 29 application rights 120
Ready to Import dialog box 273 collapsing 119
REBean SDK 207 custom 119
RECOM SDK 206, 207 domain access rights 121
Rename option effective 119
Merge import scenario 171 explicit 119
Update import scenario 172 migrating objects without rights 169
.rep files migrating or not 225
migrating 94 migration 118–164
when locales are not stored in documents 246 migration of BusinessObjects document
Repair and Compact 252 rights 95
Report Application Server SDK 61, 206 migration of security commands 73
report bursting 44 Modify Rights right (MRR) 76
Report conversion tool 197 newly-denied 119
overview 16 newly-granted 119
when you should convert .rep to .wid 240 object rights 121
Report conversion tool Users (XI R2 user group) product access rights 120
68 rights collapsing 128
Report viewers SDK 206 standard migration path 125
repositories terminology in XI R2 119
5/6 vs. XI R2 41 universe/document access 121

BusinessObjects 6.x to XI Release 2 Migration Guide 345

Index

user access 69 collapse 119

version XI R2 76 configuring LDAP security plug-in 259
View right 120 domain access rights 121
XI R2 aggregation overview 22 importing object security in incremental
rights collapsing imports 173
defined 128 importing objects without 169
Rights Fidelity mode 169 importing or not 225
rights inheritance inheritance 5/6 vs. XI R2 70
breaking in XI R2 124 managing performance management object
rights migration rights 114
overview 22 managing performance management user
.rkey files rights 114
and Desktop Intelligence 194 migrating dashboard security 109
row restrictions 92 migration options 166
run-time rebinding Modify Rights right 76
defined 233 object rights 121
overview of differences between 5/6 and XI
S R2 21
password restrictions in XI R2 69
Scan and Repair 247
performance management migration
Schedule Manager 111
constraints 115
schedules
predefined settings 74
troubleshooting migration 111
product access rights 120
scheduling
profile migration overview 23
5/6 vs. XI R2 58
recreating in XI R2 209–219
and VBA macros in XI R2 204
rights collapsing 128
capturing source scheduling information 238
rights migration 118–164
non-supported jobs 298
rights migration overview 22
recreating in XI R2 298
Secured Modify Rights right 76
setting up 55
security commands 121
version XI R2 58
setting for Everyone user group 296
viewing scheduled jobs for user 55
setting up content security in XI R2 214
viewing tasks 55
synchronizing enterprise and database
what does migration involve? 206
credentials 91
SDK 83
universe 201
version 5/6 offering 60
version 5/6 vs. XI R2 120
version XI R2 offering 61
version 5/6 vs. XI R2 inheritance 123
SDKs
View right 120
version 5/6 vs. XI R2 206
XI R2 aggregation overview 22
secondary nodes (version 6) 43
security commands
Secure Modify Rights right (SMRR) 76
and BusinessObjects document migration 151
security
and Designer migration 163
Administrators group 219
and WebIntelligence document migration 96
application rights 120
combining during migration 127
best practices with Not Specified option 216
default and aggregate rules 122
checking post-import 296

346 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

defined 121 universe access restrictions 92

how they migrate 73 user/group creation 53
migrating Application Foundation 113 Supervisor (user profile) 67
migration of universe-related 89 Supervisor over the Web
negatively-phrased 127 migration overview 26
standard migration path 126 tasks assumed by CMC in XI R2 20
Security Migration Options dialog box 167, 266 user/group creation 67
security models Supervisor-Designer (user profile) 67
overview of differences between 5/6 and XI support
R2 21 customer 331
Select Objects to Import dialog box 265 locations 331
selecting for import technical 331
categories 271, 282 web site 331
objects 265 supported deployment configurations
selectingfor import in XI R2 25
universes and connections for import 272, 283 supported platforms
semantic layer XI R2 support for platforms and versions 237
migration of 29 SVG files
Server SDKs 206 and migration 109
servers synchronizing
defined for XI R2 41 enterprise and database credentials 91
Session Stack 45
silent installation 46 T
single pass migration 223
table mapping 92
Single Sign-On see SSO
technical support 331
software
third-party documents
what migrates and what doesn’t 26
importing 98
SQL Server
time for importing 263
importing connection objects from 5/6 91
Timestamp security command 74
SSO
TNSNAMES 254
5/6 vs. XI R2 51
Tomcat 256
stored procedure rights
training, on Business Objects products 332
how they migrate 164
troubleshooting
stored procedures
document migration 295
definition 145
schedule migration 111
migration overview 29
rights 145
Stored Procedures Access right 93 U
Supervisor Unicode databases 49
creating repositories 48 and Desktop Intelligence 194
how its functions migrate 22 implications when migrating BusinessObjects
migration overview 26 documents 196
Repair and Compact 252 Unified Web Services Consumer SDK 62
running a Compact 247 universe access restrictions
tasks assumed by CMC in XI R2 20 aggregation rules 122

BusinessObjects 6.x to XI Release 2 Migration Guide 347

Index

and Delegated Administration 76 importing Inbox and personal documents 258

defined 29, 202, 202 mapping to personal/inbox documents 267,
equivalent in version 5/6 44 277
universe access rights .unv files
and Delegated Administration in XI R2 76 what is contained in (XI R2) 200
default and aggregate rules 122 Update import scenario 172
defined 121 and users/groups 75
migration 139 using for life-cycle management 230
standard migration path 127 updating
universe connections see connections platforms and versions 253
Universe Designers Users (XI R2 user group) 68 previously imported objects 269, 279
universe domain rights the destination environment 172
migration 132 upgrading
Universe Folders and Universes dialog box 272 defined for third-party software 237
universe overloads Use Pre-generated HTML when available option
equivalent in XI R2 44 115
universe overloads see universe access restrictions User (profile) 67
universe restriction sets see universe access user creation
restrictions 5/6 vs. XI R2 53
UniverseName() function 318 user groups see groups
universes user/group access rights 69
and Desktop Intelligence 196 user/group inheritance 70
checking access restrictions after import 296 usernames
checking integrity of those used by Application case-sensitivity 69
Foundation objects 103 users
exclusive overloads 92 and licensing in XI R2 24
how they are imported 89 case-sensitivity for usernames 69
importing associated universes 90 how profiles migrate 72
importing local 200 impact of Merge/Update import scenarios 75
LOV migration 201 importing 269
migration overview 29 migrating 72
modes of import 90 migrating external users 77
overload aggregation 92 migrating with designer rights 202
overload collapsing 92 organization 67
restriction set aggregation 122 parameter migration 69
run-time binding 233 post-import checking 293
security 201 principal 120
selecting for import 272, 283 which you should migrate 238
short name 90 Users and Groups dialog box 269
storage in XI R2 200
the BOUSER/BOPASS variables 91 V
tools that use 56
VBA 204
using the DBUSER/DBPASS variables 91
VBA add-ins
UNIX
migration 29
BusinessObjects Enterprise servers on 255
VBA macros

348 BusinessObjects 6.x to XI Release 2 Migration Guide

 Index

and Desktop Intelligence 195 administration 52

and Desktop Intelligence SDK 207 application rights 120
and scheduling in XI R2 204 architecture 39
migration 98 authentication 50
reason not to convert .rep to .wid 240 basic concepts 18–20
Windows vs. UNIX 207 categories and folders 57
Versatile (user profile) 67 default groups 22
version 5/6 deployment rules 184
architecture 38 enabling/disabling servers 54
authentication 50 how version 5/6 applications migrate 26
capturing scheduling information 238 how version 5/6 software migrates 26
clusters 42 InfoObjects 19
command-line installation 46 installation options 45
determining a repository’s ID 229 installing 254
distributed repository domains 25 licensing model 24
domain access rights 121 migrating external users 77
domain migration 28 Modify Rights right (MRR) 76
heterogeneous clusters 45 multiple authentication schemes 229
how applications migrate 26 object rights 121
how domains migrate 24 object storage 41
Inbox and personal storage 257 password restrictions 69
installation options 45 platform and version support 237
module equivalent in XI R2 41 product offering 37
overview of resource migration 28 publishing 204, 204
product access rights 120 publishing to repository 59
product offering 37 reporting tools 56
profile migration 23 repositories 19
publishing to repository 59 rights aggregation 71
reporting tools 56 rights aggregation overview 22
rights aggregation 71 rights terminology 119
rights migration 118–164 scheduling 204, 204
running Repair and Compact 252 Secure Modify Rights right (SMRR) 76
scheduling 58 servers 41, 41
SDK offering 60 setting up auditing 259
security commands 121 silent installation 46
setting locale 55 SSO 51
SSO 51 starting and stopping CMSs 54
starting and stopping clusters 54 starting server machines 258
terminology compared to XI R2 40 supported connectivities 253
universe access rights 121 supported deployment configurations 25
user/group organization 67 terminology compared to 5/6 40
vs. XI R2 inheritance rules 123 universe security 201
web applications 47 universe storage 200
version XI R2 user rights 69
access restrictions 92 user/group organization 68

BusinessObjects 6.x to XI Release 2 Migration Guide 349

Index

View right 120 web sites

vs. 5/6 inheritance rules 123 support 331
web applications 47 training 332
view detail log 273, 285, 291 WebConnect documents
View right 120 access from XI R2 98
Viewers SDK 61 WebIntelligence
Visual Basic for Applications 60 migrating orphan documents 94
migration assessment 198
W migration overview 27
rights migration 155–161
WCA
what does migration involve? 199
and web servers 46
WebIntelligence documents
defined 46
migrating .wqy and .wid files 29
web
migration 96
customer support 331
migration limitations 97
getting documentation via 330
rights migration 96
useful addresses 333
troubleshooting failed import 295
web application servers 43
.wqy update during import 199
web applications 47
WebIntelligence OLAP
customizing in XI R2 61
migration 30, 83
Web Component Adapter see WCA
migration assessment 208
Web Connect
WebIntelligence SDK 206
and Desktop Intelligence 195
Welcome page 264
Web Intelligence
.wid files
Allow user to merge dimension for
importing 96
synchronization right 96
migrating orphan documents 94
and .unw files 200
migration overview 29
Audit reports 203
Windows
customizing 62
install Import Wizard on Windows machine
Edit SQL right 96
254
Interactive Editing right 96
WIReportServer 43
potential report changes after import 198
.wqy files
scheduling 58, 204
and locale 97
WebIntelligence rights migration to 155–161
importing 96
what’s new 198
migration overview 29
when should you convert .rep to .wid? 240
update during import 199
Web Intelligence documents
when locales are not stored in documents 246
Autofit behavior in XI R2 294
checking locale 295
default values for rights 157 X
re-establishing report-to-report links 295 XI R2
Web Intelligence Report Server 43 auditing overview 203
Web Intelligence SDK 62, 207 recreating security in 209–219
web servers
role in 5/6 and XI R2 46
web services 62

350 BusinessObjects 6.x to XI Release 2 Migration Guide