Professional Documents
Culture Documents
Xir2 Mig Bo6 Migration en
Xir2 Mig Bo6 Migration en
Patents
Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Copyright 2006 Business Objects. All rights reserved. Last update: March 2006
Trademarks
Copyright
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 doesnt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
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
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
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
If youre 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
Contents
Appendix B
329
Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . 330 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . 331 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Introduction
chapter
10
Migration fundamentals
12
Migration essentials
chapter
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.
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.
14
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.
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)
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 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
BIAR files
The Import Wizard can also package BI content into Business Intelligence Application Resource (BIAR) format for backup or change management once youve already imported into the new environment. For information on BIAR files, see the Import Wizard online help.
16
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 imports success after each sweep with the Import Wizard; if there are issues, you dont have to begin the entire migration all over again.
For more information on migration strategies, see Formulating your migration strategy on page 222.
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.
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
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 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.
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 Administrators Guide.
20
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:
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.
Specific groups
The following groups exist by default in XI R2:
22
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 Wizards security migration options, see Security migration options on page 166.
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.
24
In 6.x, 2-tier (Desktop) deployments of BusinessObjects dont 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.
In general, the older the version of BusinessObjects used to create fullclient 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.
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.
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 Supervisor, Supervisor over the Web Requirements Comments Install CMC (Central Management Console), as well as Designer Most Supervisor and Supervisor over the Web tasks are carried out by the web-based CMC. Designer, however, now allows you to set the following universe-based parameters:
Designer
Update
Has incorporated some functionality previously included in Supervisor (see previous row in this table). Renamed Desktop Intelligence.
BusinessObjects
Update
26
Software
Requirements Comments Install side-byside + CMS (Central Management Server) install Not true for client-server in XI R2. Can install version XI R2 alongside version 6.x. You must install a CMS (Central Management Server) on the network for login, even for offline mode. Workgroup mode becomes Standalone mode, in which there is no repository connection and no repository. Install from CD required; no downloading from InfoView. Online and offline modes supported. Rework required only if InfoView was customized in version 6.x. Recreate Excel worksheets with Live Office. Results may not be identical.
3-tier mode
Update
BusinessQuery for Excel Server software (Web Intelligence, InfoView, cluster infrastructure)
On Windows On UNIX
Re-install Can install side-by-side on same machine Update Update Recreate Renamed Web Intelligence. Has been redesigned and integrated into the XI R2 framework. 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. Scheduling capabilities are handled by the CMS.
Broadcast Agent
Update + Recreate
Requirements Comments Renamed performance management, which includes these products: Dashboard Manager
Process Tracker is available on a separate CD. Data Integrator Developer Suite Update You can re-install over the existing version. No longer available: Web Intelligence SDK (WIBean/WICOM)
Admin SDK
RECOM (MSFT is replacing COM with .NET) Available: BOE SDK (Java and .NET)
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 Core repository Migration method Comments
Security domains
Import Wizard Users and groups are migrated as users and groups in the CMS.
28
Resources
Migration method
Comments
Import Wizard Universe domains are imported as universe folders in the CMS. Import Wizard Document domains are imported as document folders in the CMS. Import Wizard Check the calculations in migrated documents. VBA add-ins dont 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. 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. Import Wizard Check the calculations in migrated documents. Import Wizard These documents, for migrated users only, are migrated into the users Inbox folder in the CMS. You cannot choose which Inbox documents you migrate (all or nothing). Import Wizard These documents, for migrated users only, are migrated into the users Favorites folder in the CMS. You cannot choose which personal documents you migrate (all or nothing). 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. Import Wizard Stored procedures are migrated as connection rights.
Personal
Semantic layer
Universes
Stored procedures
Resources
Migration method
Comments
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 Recreate A Broadcast Agent job can be migrated from 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:
Broadcasting
Broadcast Agent Publisher Recreate email publications
multiple outputs conditional processing VBA add-ins report bursting (refresh with the profile of each recipient) saved in XML, RTF, HTML, or TXT format
Recreate using the CMC (Central Management Console) scheduling capabilities, or using BusinessObjects XI R2 Publisher.
Broadcast Agent Publisher Recreate web publications Web Intelligence OLAP documents BusinessQueryMD BusinessObjects OLAP documents Recreate Recreate Recreate Recreate using OLAP Intelligence. Recreate using Live Office. Recreate using Web Intelligence or Crystal Reports.
OLAP
Application Foundation
30
Resources
Migration method
Comments
Application Foundation repository Documents (.afd) Sets, metrics, goals, calendars Dashboards, menus, applications Role definitions in Performance Manager 6.5.1
Import Wizard 6.1.b, 6.1.3 through 6.5 repositories are updated in place. Import Wizard Documents pull required universes. Import Wizard Metrics pull required universes. Import Wizard Dashboards pull .afds, .reps and .wids, which pull universes. Recreate
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.
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
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 are now Step in overall migration process 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
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
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.
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 isnt 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 arent 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.
34
chapter
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
Product offering
Here is a list of the applications in each versions 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 Business View Manager Central Management 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 BusinessObjects BusinessQuery Web Intelligence Web Intelligence for OLAP Data Sources Broadcast Agent Developer Suite Set Analyzer
InfoView Desktop Intelligence Live Office Web Intelligence OLAP Intelligence OLAP Intelligence Designer
You publish from InfoView and administer publishing in the CMC. Developer Suite Part of Performance Management Applications (formerly Application Foundation)
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-users 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 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.
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
In BusinessObjects 6.x Repository The BusinessObjects 6.x suite uses a repository a database that is stored in a relational database management system. The repository is used to secure access to your data warehouse and to provide an infrastructure for distributing information to be shared by users. The repository database actually contains the data associated with the security, universe and document domains. Making sure the repository database has enough space is therefore critical.
In BusinessObjects XI R2 The repository exists here as well, as one of the databases maintained by the Central Management Server (CMS). The CMS is the central service/process in the XI R2 system (see its entry further along in this table).
Although the repository database stores specific information about the objects published to it, including users, servers, security, groups, folders, categories and parameters, it does not actually 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). When universe and document domains are imported from a version 6.x deployment, they are made into folders in the CMS database. Although the security domain itself is not imported, you can import its contents (user rights, etc.). Servers Processes in the XI R2 system are called servers. They run as services under Windows, and as processes under UNIX. The CMCs ability to enable/disable and even group servers, for example, concerns processes, not actual Business Objects servers, or server machines. The main server in BusinessObjects Enterprise XI R2 is the CMS. Some examples of other servers are: Job Server
Repository domains The repository must have a security domain. It can also contain universe and document domains.
Modules Processes used in Business Objects transactions which can be configured through the Administration Console are called modules.
A few examples of modules are: Broadcast Agent Manager (which manages Schedulers) WIStorageManager
WIReportServer
File Repository Servers Desktop Intelligence Report Server Web Intelligence Report Server
In BusinessObjects 6.x Business Objects servers At a minimum, the Business Objects server back-end must be installed on the clusters primary node and all secondary nodes. This installs all the processing layer modules on the server machines.
In BusinessObjects XI R2 Central Management Server (CMS) The CMS is a single service which provides framework services, security management, administers scheduling tasks, and also is responsible for maintaining the database (CMS 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). CMS clusters A Central Management Server cluster (CMS cluster) consists of two or more CMSs working together to maintain the system databases and repository. The CMSs can be on the same machine or on different ones. This means that at a minimum only the CMS component must be installed and activated on the machine. Other processes (servers) can be installed and run on other machines. A CMS cluster is called an expanded deployment.
Clusters A cluster is one or more Business Objects servers which provide the functional processing for a given BI portal. Each server hosts the entire set of Business Objects modules, not all of which must necessarily be activated. For versions 6.1 and later, the Session Stack must be activated in order for the server to contribute to cluster processing. When a cluster contains more than one server machine, it is called a distributed deployment.
42
In BusinessObjects XI R2
The distinction between primary and secondary nodes does not apply. When you add a new CMS to a deployment The primary node serves as the containing a previously-installed CMS, you central coordinator among all the 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 default, the new cluster is given the name of the is a primary node. 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 WebIntelligence Application servers Broadcast Agent Desktop Intelligence Web Intelligence Web application servers Scheduling functions are handled by the CMS, which instructs the Job Server to process the job on a schedule managed by the CMS. Web Intelligence Report Server Public folder Favorites folder The Event Server manages file-based events. Schedule-based and custom events, on the other hand, are managed by the CMS.
WIReportServer Corporate document domains Personal document domains File Watcher allows the processing of a scheduled task only when a specified file is present in a specified location.
In BusinessObjects 6.x Profiles Supervisor provides several standard profiles, or roles, for the users of Business Objects products. The user profile determines by default what products a user can use: General Supervisor (all products)
In BusinessObjects XI R2 Defined in the CMC, profiles let you personalize the scheduled publication of reports for groups of recipients. Users with defined profiles applied to the publication will have the publication personalized for them. 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
44
Client Server
The Server option provides three installation options: New Expand Custom
Distributed deployments To distribute processing, you add additional cluster nodes to a cluster. To add a cluster node, you must install Business Objects server on the node machine. This installs the entire set of processes required for system processing on each machine. At a minimum, the Session Stack must be activated on each cluster node to share the transaction load.
You can distribute a single deployments transactional capabilities on the same machine by creating multiple instances of a server, or you can install on additional machines to distribute the load. This capability offers you the ability to scale your system vertically (more services on the same machine) or horizontally (more machines). The CMS does not need to run on each machine.
In BusinessObjects 6.x Installation and the repository Repository creation is completely independent of the installation of Business Objects software.
In BusinessObjects XI R2 Setting up the CMS database, which includes the repository, is an integral part of BusinessObjects 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). Silent installation You must install a Web Component Adapter (WCA) on any machine hosting an application server. The WCA allows your application server to run applications making Crystal Web Requests, and to host the CMC. Not all applications require the WCA. For example, InfoView doesnt need it unless users will be viewing OLAP Intelligence documents. Installing XI R2 on the same machine as the application server is called a server-side installation. When you perform this installation, the client and server components are installed, the default user and group accounts are created, and the sample reports are published to the system. When the installation is complete, the servers are started as services on the local machine. For information on deploying web applications on application servers, see Deploying web applications on page 48 in this table.
Command-line installation Application servers Application servers communicate with the Business Objects cluster through the ORB. If the application server is hosted on a machine which is neither a primary nor secondary node, you must configure the ORB on it in order to allow it to communicate with the cluster. You configure the ORB on the application server machine either by installing the Configuration Tool on that machine, then using it to configure the server as a client node of the cluster, or by configuring the ORB manually.
For information on deploying web applications on application servers, see Deploying web applications on page 48 in this table.
Web servers To configure the web server to work with a If you connect BusinessObjects Enterprise to a web server, the Web Component Adapter (WCA) cluster, you must install a third-party must be installed on the same machine. connector to the clusters application server.
46
In BusinessObjects 6.x For information on deploying web applications on web servers, see Deploying web applications on page 48 in this table. Licenses Before installation, you copy your license file(s) to a directory to which all nodes or application client machines have access. During installation, you specify where these XML files are located. OLAP You install Web Intelligence for OLAP Data Sources using the standard installation process. Configuring clusters and the ORB You create clusters and configure their ORB on their nodes using the Configuration Tool. You configure the clusters primary node and then its secondary nodes. Available web applications
In BusinessObjects XI R2 For information on deploying web applications on web servers, see Deploying web applications on page 48 in this table.
License key strings, different from version 5.x license strings, are stored in the CMS database. You can view your deployments current license keys, as well as add or delete them, using the CMC. OLAP Intelligence is installed from the standard installation CD.
When you install the first Central Management Server (typically a New install), you dont have to define a cluster. In subsequent installs, you are asked if the CMS is part of the cluster, and at that time, the cluster is created.
Central Management Console InfoView Performance Manager applications (formerly Application Foundation), J2EE only Custom web applications developed using the SDK
Custom web applications developed using the SDK Although not part of the BusinessObjects 6.x suite, Application Foundation applications can also be deployed.
In BusinessObjects 6.x Deploying web applications You can deploy web applications in three ways: If youre using IIS or Tomcat/Apache, the Configuration Tool can deploy the applications automatically on web and application servers. You can use the wdeploy tool, a 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.
In BusinessObjects XI R2 If you choose a New installation and are using IIS or Apache/Tomcat, the Business Objects web applications are deployed automatically on the application server, unless you are deploying to an existing Java application server. Otherwise, you must deploy web applications manually. For information, see the BusinessObjects XI Release 2 Installation Guide.
In XI R2 you deploy all the web applications You can choose to deploy web resources on the web application server. applications in two modes: 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 and configuration, using the Supervisor application. After repository creation, you must copy the bomain.key file corresponding to the repository on each node in the cluster. If you do not have a supported database client on the machine, installation can install and configure mySQL for use as the CMS database. To use your own 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 CMSs database. This allows the server to connect to it.
48
In BusinessObjects 6.x Multiple service instances In BusinessObjects 6.x, certain modules such as WIQT, BusinessObjects.exe (Windows)/bolight (UNIX), Connection Server, and WIReportServer, are designed to be multi-instance on cluster nodes. You use the Administration Console to set the number of instances in 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 store information in different languages and centralize all the information in a company, is supported as a data source for Web Intelligence reports. Unicode databases are not supported for repositories or BusinessObjects documents.
In BusinessObjects XI R2 Multiple instances of the same service can run on the same machine (providing vertical scaling), or on separate machines (for horizontal scaling), in any mixture of supported operating systems. The single exception is the Central Management Server, which must run on the same operating system within a single cluster.
All CMS databases must support the Unicode protocol. Desktop Intelligence can use Unicode data sources.
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.
In version XI R2, security is much more granular. You implement an authentication method for each user, when you create the users 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 repositorys 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 the entire cluster, using the Administration Console. You set authentication for 2-tier deployments of BusinessObjects in Supervisor.
You select the authentication method for each user at the creation of the users account, using the CMC. You can assign multiple aliases, or authentication modes, to a single user, or create new aliases 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 dont need to create the settings for each user individually.
Configuring authentication and authorization You set authentication/authorization for the entire cluster.
50
In BusinessObjects 6.x Available authentication modes These options differ according to the version of your source software. Business Objects, or Business Objects standard Windows NT, Windows authentication, or Windows-NTLM Single Sign-On
In BusinessObjects XI R2
Enterprise authentication (automatically enabled when you install the system, and similar to Business Objects standard in version 6.x) Windows NT authentication LDAP authentication Windows AD authentication
Other authentication modes are available through add-in products, such as SAP authentication. Single Sign-On is not a mode in itself, but is available for certain authentication modes. See below. Single Sign-On to BusinessObjects Enterprise XI 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. Because of the use of Access Control Lists (ACL), an industry standard method of controlling cascading security access, the 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, and connections. This means, for example, that you could allow a group to refresh document A, but not refresh document B.
Single Sign-On (SSO) To enable SSO in version 6.x, you must use Netegrity SiteMinder.
Authorization You can 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.
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 Administrators Guide.
52
In BusinessObjects 6.x Repository creation and management You create your clusters repository after Business Objects installation and configuration, using the Supervisor application.
In BusinessObjects XI R2
If you do not have a supported database client on the machine, installation can install and configure mySQL for use as the CMS database. To use your own 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 CMSs database. This allows the server to connect to it.
User/group creation and management You use Supervisor or Supervisor over the Web. You use the CMC.
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 automatically created at repository creation. Two default groups are automatically created at installation: Administrators contains users that have administrative rights. Everyone contains all users created in the system. If youre 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
License key management License keys are stored in the CMS database. You can Before installation, you copy your license key to a directory to which all view your deployments 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.
In BusinessObjects 6.x Using Designer You can use Designer in online or offline mode. Cluster start/stop Under Windows, you can use WINotify or the Start menu; during installation, you can also set the Business Objects server to run automatically as a Windows service. Under UNIX, you start the cluster manually using the wstart command, or use S99WebIntelligence to start it automatically on machine startup.
In BusinessObjects XI R2 You can use Designer in online or standalone mode, which is equivalent to offline mode in version 6.x. You use the CCM to stop a Central Management Server (CMS), regardless of the operating system. At installation, you can also configure the server to start automatically at machine startup. Note: You cannot use the Central Management Console (CMC) to stop a CMS.
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 Administration Console. You can also use the Auditor application for enhanced system monitoring and analysis. You use the CMC. You can also use the CMC to view server metrics, including information about the machine that the server is running onits name, operating system, total hard disk space, free hard disk 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
In BusinessObjects 6.x Setting up scheduling You create and manage schedulers using the Broadcast Agent Managers Properties page in the Administration Console.
In BusinessObjects XI R2
Because the scheduler is incorporated into the CMS, scheduling comes automatically with BusinessObjects 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 objects 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 objects instances by looking at the objects history. A sample application built using the Administration SDK and available from the BusinessObjects Enterprise Users Launchpad also allows you to see all the jobs scheduled by any specific user. InfoView appearance and functionality management You can use Supervisor security commands to prevent users from modifying the default settings in the InfoView Options page. Setting locale You set the clusters language at installation; you can subsequently use the Site Properties tab in the Administration Console to modify it. Users can set the language of their interface in InfoView.
You can modify the appearance and some functionality using the BusinessObjects Enterprise Applications management area in the CMC.
You dont specifically set the CMS locale. Users set the locale for their own interface in InfoView; if they dont, InfoView uses the locale specified on the web server.
Crystal Reports Desktop Intelligence OLAP Intelligence Web Intelligence Crystal Reports 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 must be deployed after Business Objects installation using the Configuration Tool, wdeploy, or manual procedures. It is available in JSP and ASP platforms. The out-of-the-box portal in BusinessObjects Enterprise XI R2 is also called InfoView. Available for both Java and .NET platforms, its interface is somewhat different from the BusinessObjects 6.x application.
56
In BusinessObjects 6.x Categories Within InfoView, you can use categories to organize documents on a particular document list page.
In BusinessObjects XI R2 BusinessObjects Enterprise XI R2 uses both categories and folders to organize documents. 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.
Corporate categories can be created Corporate categories can be created either in InfoView (with reduced management capabilities) or from InfoView, BusinessObjects, 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 restrict access to corporate categories. In the CMC you can restrict users and/or groups access to categories and folders. You can set limits 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.
In BusinessObjects 6.x Scheduling You schedule for refresh documents and files either from 2-tier deployments of BusinessObjects, or from InfoView.
In BusinessObjects XI R2 You schedule for refresh objects using the Publishing Wizard, from the CMC or from InfoView.
You can schedule: BusinessObjects documents Web Intelligence documents Web Intelligence OLAP reports
You can schedule: Crystal reports OLAP Intelligence 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
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. Use the Publishing Wizard when you: or Supervisor Have access to the locally installed application. Adding users and groups and managing security settings from Are adding multiple objects or an entire directory. Supervisor and/or Supervisor over The Publishing Wizard is a locally installed the Web 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 youre 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.
SDK
In BusinessObjects 6.x
SDK or module... Used to customize/ extend... BusinessObjects BusinessObjects, SDK (macros and Designer, the Report add-ins) Viewer component Web Intelligence SDK (scripts) Web Intelligence, InfoView Using this language/ platform... Visual Basic for Applications ASP, JSP JSP
Administrator SDK Users and groups in a strictly controlled environment Web Services
Set of web service .NET, Java (REBean) applications based on the .NET and J2EE frameworks and on InfoView
60
In BusinessObjects Enterprise XI R2
SDK or module BusinessObjects Enterprise SDK Description Using this language/ platform
Includes libraries for Microsoft Visual 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 Server SDK Includes libraries for building a web report design tool. Lets users create new reports or modify existing ones by adding, removing, and modifying objects, such as tables, charts, and fields. Includes libraries for building customized thinclient report viewers that display web-based reports. Also provides an interface to programmatically export Crystal Reports to a variety of other formats. Microsoft Visual Studio .NET, Java, COM
Viewers SDK
Java, COM
Description
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. For customizing and extending Desktop Intelligence; almost identical to version 6.x BusinessObjects SDK Visual Basic for Applications
Designer SDK
For customizing and Visual Basic for extending Designer; Applications almost identical to version 6.x Designer SDK For customizing and extending Web Intelligence Set of services that allow you to create Business Objects Web Service consumer applications that manage sessions, create custom queries, manage documents, and perform listing and publishing actions. REBean, RE .NET
62
64
chapter
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.
66
Understanding user and group migration Users, groups, and their organization
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.
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
68
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 users chances of simply guessing a valid users 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 dont, they will not be re-imported.
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 users 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
Rights aggregation
Aggregation is different in the two environments. In 6.x If the user has a right denied in one group and granted in the other, the user may or may not have the right granted. Aggregation rules for conflicting rights are different for the different types of rights. The value Unspecified defaults to either Granted or Denied depending on the type of right. In XI R2 If a user has a Boolean right denied in one group and granted in the other, then the user has the right denied. If the user has a boolean right unspecified in one group and granted in the other, then the user has the right granted. Unspecified Boolean rights are always considered denied.
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 groups 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.
Understanding user and group migration How users and groups migrate
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
Understanding user and group migration How users and groups migrate
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.
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 Login Password Specific migration information Migrated, although the CMS does not differentiate upper-case and lower-case 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. If the user is disabled in BOBJ, it is disabled in XI R2 after import Not migrated Not migrated
Enable real time user rights Not migrated update Enable Password Modification flag Password Validity settings Object Security level Maps to the User cannot change password property, for which the reverse value is accorded. Administrators must reset this manually at the global level. Expressed as limit rights set on the universe folder; object levels in BusinessObjects 6.x map to appropriately-named user groups.
74
Understanding user and group migration Consequences of importing users and groups
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.
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).
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
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.
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.
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.
78
6.
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 users 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.
80
chapter
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
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
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
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
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 users 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 users 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.
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 CMCs 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
Week periodicity Week periodicity Business day Weekend day Month periodicity
86
User-defined
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.
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.
Inbox
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
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). The Import Wizard imports the scheduled document into Public Folders/ Scheduled migrated documents/<BCA name>. The document is renamed to
<doc_name>_<docID>.<ext>
If the sender of the original schedule does not exist in the CMS, then:
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).
88
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.
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
The Import Wizard has three modes for importing universes: Mode Import all universes and all connection objects What it does Imports all universes and all connection 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 connections that the selected Web Intelligence and BusinessObjects documents use directly Imports all universes and connections used by the selected documents. This option also enables you to select additional universes to import, even if they are not used by any document.
When you select a Web Intelligence or BusinessObjects document to import, the Import Wizard automatically selects the associated universes for import. It does not do this, however, for universes used by scheduled documents (Broadcast Agent jobs). This means that if you are not importing all your universes, you must manually select the ones you need for Broadcast Agent jobs. Note: The Import Wizard also imports any universes with the same name that exist in other domains. BusinessObjects documents may have been created outside the repository, using a short name; that is, a reference to a universe stored on a local machine. If the universe has a short name, its linked documents may not be imported if more than one universe is found in the CMS with the same short name. Universe domains are converted into subfolders under the Universe folder. Each universe folder is named after the corresponding 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
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 users 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
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 users file. User names and passwords are loaded from a file, stored and used as database credentials. create a custom application using Enterprise SDK to set DBUSER and DBPASS information.
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.
92
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.
Documents
Importing documents presents a good opportunity to optimize your document management. For more information, see What objects should you migrate? on page 239.
the documents locale the locale of the machine used to create the document
Once you select these locales, they are stored in the document itself when it is imported to the CMS. The default locales apply to all documents in the current import without locales. Applying wrong locales to a document may cause difficulties; for example, the date or currency may be incorrectly displayed. If the repository contains documents with different locales, it is best practice to run the import step by step (one step for each document language) in order to avoid, for example, setting a default English locale for a Japanese document.
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
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 cant 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.
See Checking for calculation updates on page 301 for more information.
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.
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
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.
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
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
chapter
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
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.
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.
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.
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
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.
Understanding Application Foundation object migration Migrating the Application Foundation repository and its contents
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
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.
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.
Understanding Application Foundation object migration Migrating the Application Foundation repository and its contents
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. Run the Import Wizard to import objects to the CMS and to migrate the Application Foundation repository.
4.
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).
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
and publishes them in the CMS. The docID that referenced the corporate document in the dashboard is replaced by the new CUID in the dashboards migrated XML definition.
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
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 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.
Understanding Application Foundation object migration Migrating rules and named events
2. 3. 4.
If schedules do not migrate correctly, perform the following steps after migration: 1. 2. 3. 4. Log into performance management with a valid administrator profile. In Setup > Parameters > Options > Scheduler Parameters, update the user account under which scheduled programs will run. In Setup > Tools > Check & Cleanup, click Scheduled Programs to launch the Check & Cleanup Scheduled Programs window. Click Select All then Fix to update all scheduled programs.
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.
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.
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.
See the BusinessObjects Enterprise XI Release 2 Administrators Guide for more details on managing ACLs.
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 prerendering are migrated in the Import Wizard. The action that calls for prerendering 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.
chapter
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.
Rights terminology
The following table contains basic terminology you need to know to understand the security models and rights migration. Term collapse Definition 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. 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 rights are set directly on the object, while effective 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. A right that is effectively denied on the principal but effectively granted on the principal's parent (that is, granted explicitly or via inheritance). A security command that is effectively enabled on the principal but effectively denied or hidden on the principal's parent (explicitly or via inheritance). A right that is effectively granted on the principal but effectively denied on the principal's parent (that is, denied explicitly or via inheritance).
custom rights
newly-denied
newly-enabled
newly-granted
Definition A user or group, typically one for whom rights are set on some object 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.
Version 6.x Security commands The right to use certain features of a product. Security command rights are associated with a product such as Web Intelligence or Designer and typically correspond to actions such as Save docs or Rename docs; these are usually distinct actions offered by the user interface. Possible values are: Enabled (UI element visible)
Version XI R2
In XI R2, security commands can be equivalent to application rights set on application objects (like the Designer or Supervisor application object), or object rights, set on content objects or the folder that contains them (like universe or Web Intelligence document objects or domain folders). 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 The right to access the contents of a universe or document domain. Universe/document access 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). Object rights are set on content objects or the folder that contains them (like universe or Web Intelligence document objects or domain folders).
Granted Denied (Except for Designer and Supervisor access rights, which are set to Denied on the root folder at install time.) Enabled Denied
Security command
If Hidden anywhere, then Hidden If Disabled anywhere, then Disabled Otherwise, Enabled
Granted
Denied
If unspecified or Denied anywhere, then Denied If unspecified or Denied anywhere, then Denied
Denied
Denied
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.
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.
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 XI R2 Both group and folder inheritance exist. Rights are inherited from ancestor objects and groups, unless either type of inheritance is explicitly turned off. Turning off inheritance prevents that type (group or object) of inheritance for all the rights for a 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.
Version 6.x The only type of rights inheritance is group inheritance. When a right is set on a group it applies to all subgroups, unless it is overridden for a subgroup or user. Rights set lower down in the group tree take priority. That is, rights on an user's parent take priority over those on the grandparent, and so on.
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.
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.
The following identifies the migration path for integrated rights: Right type in version 6.x Product access rights Migrated to version XI R2 as... Right to view application object (View right) For more information, see Application rights migration on page 128. Value migration: 6.x = XI R2 Granted = Granted Denied = unspecified Positively-phrased security commands: Hidden = Denied Denied = Denied Unspecified = Denied Negatively-phrased security commands: Granted = Denied Denied = Granted Unspecified = Granted (See Negatively- and positively-phrased security command migration below.) Some security commands are combined when they are migrated. See the following section.
Security commands Right to corresponding application object, domain folder, or content object For more information, see Application rights migration on page 128. BusinessObjects security commands migrate as rights set on: the Desktop Intelligence application (application rights) Desktop Intelligence documents or document domain folders (object rights) Web Intelligence security commands migrate as rights set on: the Web Intelligence application
Web Intelligence documents or document domain folders Designer security commands migrate as rights set on: the Designer application
Right to view corresponding domain folder (domains are migrated as folders, and their universes/documents as child objects of the domain folder) For more information, see Document/universe domain rights migration on page 132. Child universes/documents inherit folder rights unless inheritance is broken.
Granted = Granted Denied = Denied Unspecified = Denied The value of the migrated domain access right affects the value of migrated security commands and document access rights. See Combining security commands during migration below.
Right to view corresponding content object For more information, see Document/universe rights migration on page 139.
The following table shows how version 6.x negatively- and positively-phrased security commands are migrated. Positively-phrased security commands Granted are migrated as Granted Denied are migrated as Denied Negatively-phrased security commands Granted are migrated as Unspecified Denied are migrated as Granted
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. 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.
Full collapse
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.
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.
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.)
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
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.
Case B
Net document access (document access combined with domain access) is newly-denied. Both folder and group inheritance are broken.
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
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:
Rights by product/component
This section includes:
BusinessObjects/Desktop Intelligence rights Web Intelligence/Web Intelligence rights Designer rights Connection 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
Application rights in the destination vs. source environments Document rights (.rep or .rea) How source BusinessObjects security commands migrate
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. View Rights in source environment N/A N/A N/A N/A Rights in source environment Drill Through Edit Scope of Analysis Work in Drill Mode Work in Slice-and-Dice Mode Create And Edit Connections Copy to Clipboard Create Documents Create Templates Data Provider Manipulation Document Interactions Edit Euro Converter Rates Euro Converter Manage All Corporate Categories Manage My Corporate Categories Print Documents Refresh Documents
General rights in XI R2
Log on to BusinessObjects and Granted view this object in the CMC Edit this object Inherited Modify the rights users have to Inherited this object Securely modify rights users have to objects Custom rights in XI R2 Drill Through Edit Scope of Analysis Work in Drill Mode Work in Slice-and-Dice Mode Create And Edit Connections Copy to Clipboard Create Documents Create Templates Data Provider Manipulation Document Interactions Edit Euro Converter Rate Euro Converter Manage All Corporate Categories Manage My Corporate Categories Print Documents Refresh Document List and Categories Inherited View Granted Granted Granted Granted Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Granted Inherited
Rights in source environment Refresh Documents Report Interactions Either Retrieve Documents from Other Users, or Retrieve Documents from Repository Save Documents Save for All Users Send Documents to MAPI Send Documents to Repository Use Templates Edit Free-hand SQL Scripts Use Free-hand SQL Edit Personal Data Files Use Personal Data Files Edit Stored Procedures Use Stored Procedures Edit Scripts/VBA Code Install and Uninstall Add-Ins Run Scripts/VBA Code Negation of (Do not always regenerate SQL) Use Queries Use Lists of Values Use User Objects Edit Query Edit Lists of Values Edit Query SQL Refresh Lists of Values Negation of (Restrict SQL to Select only) View Query SQL Change Password
Save Documents Save documents for all users Send Documents to MAPI Export Documents Use Templates Edit Free-hand SQL Use Free-hand SQL Edit Personal Data Files Use Personal Data Files Edit Stored Procedures Use Stored Procedures Edit VBA Code Install Add-Ins Run VBA Code Always Regenerate SQL Use Queries Use List of Values Use User Objects Edit Queries Edit List of Values Edit Query SQL Refresh List of Values Use other SQL requests than Select View SQL Change Password
Granted Inherited Granted Granted Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Granted Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited
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.
Not Specified Not Specified Not Specified Granted Granted Not Specified Not Specified Not Specified
Modify the rights users have to Not Specified Not Specified Not Specified objects Schedule the document to run Delete objects Define server groups to process jobs Delete instances Copy objects to another folder Schedule to destinations View document instances Not Specified Granted Not Specified Granted Granted Granted Not Specified Not Specified Not Specified
Not Specified Not Specified Not Specified Not Specified Granted Not Specified Granted Granted Granted Granted Granted Granted
Pause and Resume document Not Specified Not Specified Not Specified instances Securely modify rights users have to objects Reschedule instances Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified
General rights for Desktop Intelligence documents Schedule on behalf of other users View objects that the user owns Modify the rights that users have to objects that the user owns Delete objects that the user owns Delete instances that the user owns View document instances that the user owns
View
Schedule
View on Demand
Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Granted
Not Specified Not Specified Not Specified Not Specified Granted Granted
Pause and Resume document Not Specified Granted instances that the user owns Securely modify rights users have to objects that the user owns
Reschedule instances that the Not Specified Granted user owns Custom rights for Desktop Intelligence documents Refresh the reports data Edit Query Refresh List of Values Use List of Values View SQL Export the reports data View Schedule
Not Specified Not Specified Granted Not Specified Not Specified Not Specified Not Specified Granted Not Specified Granted Not Specified Granted Granted Granted Granted
Download files associated with Not Specified Not Specified Not Specified the object
BusinessObjects security commands in source environment Analysis Drill Through Edit Scope of Analysis Work in Drill Mode Work in Slice-and-Dice Mode
XI R2 rights
Enforced by
Drill Through Edit Scope of Analysis Work in Drill Mode Work in Slice-and-Dice Mode
Work with BusinessMiner (Application no longer used) Connections Create and Edit Connections Documents Attach Scripts to Scheduled Processing Change File Locations Conditional Formatting Copy to Clipboard Create Documents Create Templates Data Provider Manipulation (Not used in XI R2) (Not used in XI R2) (Not used in XI R2) Copy to Clipboard Create Documents Create Templates Data Provide Manipulation Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence Create and Edit Connections Desktop Intelligence
Delete Corporate (Not needed, enforced by CMS Documents Sent by Other framework) Users
BusinessObjects security commands in source environment Do Not Refresh with the Profile of Each Recipient Document Interactions Euro Converter Manage All Corporate Categories Manage My Corporate Categories Print Documents Refresh Document List and Categories Refresh Documents
XI R2 rights
Enforced by
(Not used in XI R2) Document Interactions Euro Converter Manage All Corporate Categories Manage My Corporate Categories Print Refresh Document List and Categories Refresh Document Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence + document (refresh the reports data) Desktop Intelligence Desktop Intelligence Desktop Intelligence Job Server
Edit Euro Converter Rate Edit Euro Converter Rate Desktop Intelligence
Report Interactions
Report Interactions
Retrieve documents from Import Documents Other Users Retrieve Documents from Import Documents Repository Retrieve Documents from (Not a BusinessObjects Scheduled Processing right - Enforced by framework) Save Documents Save documents for all users Schedule Corporate Documents Send Documents for Scheduled Processing Save Documents Save documents for all users (Not a BusinessObjects right - Enforced by framework) (Not a BusinessObjects right - Enforced by framework)
Job Server
Send Documents to MAPI Send Documents to MAPI Desktop Intelligence Send Documents to Other (Not used in XI R2) Users
BusinessObjects security commands in source environment Send Documents to Repository Use Broadcast Agent Console Use Templates Work with Web Server
XI R2 rights
Enforced by
Export Documents (Not used in XI R2) Use Templates (Broadcast Agent publishing a document on the Web in HTML format. Not used in XI R2) Edit Free-hand SQL Use Free-hand SQL
Desktop Intelligence
Desktop Intelligence
Free-hand SQL Edit Free-hand SQL Scripts Use Free-hand SQL Miscellaneous Cannot View User/Groups (Not used in XI R2) Hierarchy View All Users Multi-dimensional data Edit DB2 OLAP Data Edit Essbase Query Edit Express Query Use DB2 OLAP Data Use Essbase Data Use Express Data Personal data files Edit Personal Data Files Use Personal Data Files Programmability Download VBA from Web (Used only by version 5 Intelligence users) Import/convert scripts (Used only by version 5 users) Edit Personal Data Files Use Personal Data Files Desktop Intelligence Desktop Intelligence (Not used in XI R2) (Not used in XI R2) (Not used in XI R2) (Not used in XI R2) (Not used in XI R2) (Not used in XI R2) (Not used in XI R2) Desktop Intelligence Desktop Intelligence
BusinessObjects security commands in source environment Edit Scripts/VBA Code Install and Uninstall AddIns Run Scripts/VBA Code Query Technique Do not Always Regenerate SQL Edit List of Values Edit Query
XI R2 rights
Enforced by
Edit VBA Code Install Add-Ins Run VBA Code Always Regenerate SQL (Negative rephrasing!) Edit List of Values Edit Query
Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence Desktop Intelligence + document (Edit Query) Desktop Intelligence Desktop Intelligence + document (Refresh List of Values) Desktop Intelligence
Use other SQL Requests than Select (Negative rephrasing!) Use List of Values
Desktop Intelligence + document (Use List of Values) Desktop Intelligence Desktop Intelligence Desktop Intelligence + document (View SQL) Desktop Intelligence Desktop Intelligence Desktop Intelligence
Stored procedures Edit Stored Procedures Use Stored Procedures Tools Change Password Login As Change Password (Not used in XI R2) Edit Stored Procedures Use Stored Procedures
Edit SQL, to control the users ability to edit SQL query Merge dimensions for synchronization, to control the users ability to edit a semantic link for multiple data providers Enable Query - HTML, to control the users 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
Securely modify rights users have to N/A objects Web Intelligence XI R2 application custom rights Java Report Panel: Edit SQL Merge dimensions for synchronization Equivalent in source environment (New in XI R2) (New in XI R2)
Web Intelligence XI R2 application custom rights Enable interactive HTML viewing (if license permits) Enable Query - HTML Report Panel Enable HTML Report Panel Enable Java Report Panel Extend scope of analysis Enable drill mode Create document Java Report Panel: Enable formula toolbar Interactive: General - Enable right click menu Interactive: General - Edit My Preferences Interactive: Left Pane - Enable document summary Interactive: Left Pane - Enable data summary Interactive: Left Pane - enable document structure and filters Interactive: Left Pane - Enable available objects, tables and charts Interactive: Formatting - Enable toolbar and menus Interactive: Reporting - Create and edit report filter Interactive: Reporting - Create and edit sort Interactive: Reporting - Create and edit break Interactive: Reporting - Create and edit predefined calculation
Equivalent in source environment Use Interactive Viewing Use Web Intelligence HTML Report Panel N/A Once migrated, set to Not Specified Use Web Intelligence Java Report Panel Extend Scope of Analysis Allows working in drill mode Allows creation of documents Allows use of the Formula bar when creating documents in the Java Report Panel (New in XI R2)
(New in XI R2) (New in XI R2) (New in XI R2) (New in XI R2) Use Formatting Toolbar (New in XI R2) (New in XI R2) (New in XI R2) (New in XI R2)
Web Intelligence XI R2 application custom rights Interactive: Reporting - Create and edit alerter Interactive: Reporting - Create and edit rank Interactive: Reporting - Insert or duplicate report, table, chart and cell Interactive: Formula - Enable toolbar and variable creation
Equivalent in source environment (New in XI R2) (New in XI R2) (New in XI R2) (New in XI R2)
Not Specified Not Specified Not Specified Granted Not Specified Not Specified Not Specified
Modify the rights users have to Not Specified Not Specified Not Specified objects Schedule the document to run Delete objects Define server groups to process jobs Delete instances Copy objects to another folder Schedule to destinations View document instances Not Specified Granted Not Specified Granted Granted Granted Not Specified Not Specified Not Specified
Not Specified Not Specified Not Specified Not Specified Granted Not Specified Granted Granted Granted Granted Granted Granted
Pause and Resume document Not Specified Not Specified Not Specified instances
Web Intelligence (.wid) XI R2 View document general rights Securely modify rights users have to objects Reschedule instances Schedule on behalf of other users View objects that the user owns Modify the rights that users have to objects that the user owns Delete objects that the user owns Delete instances that the user owns View document instances that the user owns
Schedule
View on Demand
Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Not Specified Granted
Not Specified Not Specified Not Specified Not Specified Granted Granted
Pause and Resume document Not Specified Granted instances that the user owns Securely modify rights users have to objects that the user owns
Reschedule instances that the Not Specified Granted user owns Web Intelligence (.wid) document custom rights Refresh the reports data Edit Query Refresh List of Values Use List of Values View SQL Export the reports data View Schedule
Not Specified Not Specified Granted Not Specified Not Specified Not Specified Not Specified Granted Not Specified Granted Not Specified Granted Granted Granted Granted
Download files associated with Not Specified Not Specified Not Specified the object
Web Intelligence security commands in source environment Manage All Corporate Categories
XI R2 right
Enforced by
(Not used in XI R2 BI platform defined instead with rights on the folder and the categories) (Not used in XI R2 Intelligence tier defined instead with rights on the folder and the categories) (Not used in XI R2 Intelligence tier defined instead with rights on the document and the folder) View Inbox (Not used in XI R2) InfoView
Read Inbox Documents Refresh View of Document Lists and Categories Save and Read Personal Documents Save to Corporate Documents Upload Documents
(Not used in XI R2 defined instead by rights on the folder) (Not used in XI R2 defined instead by rights on the folder) (Not used in XI R2 defined instead by rights on the folder) (Not used in XI R2)
BI platform
BI platform
BI platform
Publications Manage Email Publications Query and Web Panel Allows creation of documents Do Not Always Regenerate SQL Edit Documents Edit Documents Web Intelligence Create Documents (Allows creation of Web Intelligence documents) Web Intelligence
Web Intelligence security commands in source environment Edit Query Refresh Lists of Values Use Formatting Toolbar Use Formula Language / Create Variables Use Lists of Values
XI R2 right
Enforced by
Interactive: Formatting Web Intelligence enable toolbar and menus Interactive: Formula Enable toolbar and variable creation Web Intelligence
(Not used in XI R2 Web Intelligence defined instead with rights on the document) (Not used in XI R2 defined instead by rights on the document) Web Intelligence
View SQL
Designer rights
This section covers:
Application rights in the destination vs. source environment Universe rights How Designer security commands migrate
Log on to the Designer and view this N/A object in the CMC Edit this object Modify the rights users have to this object N/A N/A
Designer application custom rights Check Universe Integrity Refresh Structure Window Use Table Browser Apply Universe Constraints Link Universe
Equivalent in source environment Check Universe Integrity Refresh Structure Window Use Table Browser Apply Universe Constraints 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 Add objects to the folder View objects Edit objects Modify the rights users have to objects Schedule the document to run Delete objects Copy objects to another folder Equivalent in source environment Export universe (to a given folder) Enable universe N/A N/A N/A N/A N/A
Securely modify rights users have to N/A objects View objects that the user owns Edit objects that the user owns Modify the rights users have to objects that the user owns Delete objects that the user owns N/A N/A N/A N/A
Securely modify rights users have to N/A objects that the user owns Universe custom rights New List of Values Print Universe Show Table or Object Values Equivalent in source environment New List of Values Print Universe Show Table or Object Values
Universe custom rights Edit Access Restrictions Unlock Universe Data Access
Designer security commands in source environment Link Universe New List of Values New Universe Prevent from Overwriting Universe Print Universe Show Table or Object Values
XI R2 right
Enforced by
Link Universe New List of Values (Not used in XI R2) Edit Objects (General) Print Universe Show Table or Object 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.
chapter
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
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 Wizards 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.
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 Performance Management folder (top level) access level All Desktop Intelligence rights All Web Intelligence rights All Designer rights Value No Access Not specified Not specified 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.
Understanding Import Wizard options The Merge and Update import scenarios
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.
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.
Understanding Import Wizard options The Merge and Update import scenarios
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).
Special case
If you did not choose the Rename option, the import of objects with the same path and name fails.
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.
Understanding Import Wizard options The Merge and Update import scenarios
Example: Merge with no Rename Source environment Before import After import Destination environment
Folder A (CUID=1234, ID=1) Folder A (CUID=6789, ID=3) Rpt A (CUID=2345, ID=2) Folder A (CUID=6789, ID=3) No change in existing folder content except following addition: Rpt A (CUID=2345, ID=4)
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 objects 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 documents 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.
Understanding Import Wizard options The Merge and Update import scenarios
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:
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.
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 selected Update the object contents and its ACL rights for concurrentlyimported principals. Use this to import objects and their security, especially if they have been modified in the source deployment Import the objects ACL only. Select principals + objects. Object content will not be modified. Use this to overwrite the objects security but not other potential object modifications in the destination CMS. Neither the objects content nor ACL is modified in the CMS. Use this to reimport a set of objects without updating objects that were already imported, but only add the new objects in the source repository.
Only object content is modified. ACLs are not modified. Use this to import objects that may have been modified in the source deployment, without overwriting destination security settings for them.
Understanding Import Wizard options The Merge and Update import scenarios
The source object is added to the CMS, with the same name and CUID. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport (no existing objects from version 6.x deployment) Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2]
Merge No rename
The source object is added to the CMS, with the same name and CUID. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder B [CUID = 1] Destination postimport Folder A [CUID = 3] Rpt A [CUID = 2] Folder B [CUID = 1]
Merge No rename
Different CUID For all objects but folders, import of the source object fails. Same path/name For example:
Understanding Import Wizard options The Merge and Update import scenarios
Objects have...
Result
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 Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder A [CUID = 3] Rpt A [CUID = 4] Destination postimport Folder A [CUID = 3] 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 No rename
Same CUID Import of the source object fails because of the duplicate Same path/name object name. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder A [CUID = 1] Rpt A [CUID = 2] Destination postimport Same as preimport. Folder A import fails due to name clash; Rpt A fails because parent import failed.
Merge rename
The source object is added to the CMS, with the same name and CUID. For example:
Understanding Import Wizard options The Merge and Update import scenarios
Objects have...
Result
Source Folder A [CUID = 1] Rpt A [CUID = 2] Merge Rename Same CUID Different path/ name
The source object is imported with the same name and CUID. The object in the CMS repository with the same CUID loses its CUID. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder B [CUID = 1] Destination postimport Folder A [CUID = 3] Rpt A [CUID = 2] Folder B [CUID = 1]
Merge Rename
Different CUID The source object is added to the CMS repository under a 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 Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder A [CUID = 3] Rpt A [CUID = 4] Destination postimport Folder A(2) [CUID = 1] Rpt A [CUID = 2] Folder A [CUID = 3] Rpt A [CUID = 4]
Merge Rename
Same CUID The source object is imported with a new name and the 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:
Understanding Import Wizard options The Merge and Update import scenarios
Objects have...
Result
Destination postimport Folder A(2) [CUID = 3] Rpt A [CUID = 4] Folder A [CUID = 1] Rpt A [CUID = 2]
Update No rename
The source object is added to the CMS, with the same name and CUID. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport (no existing objects from version 6.x deployment) Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2]
Update No rename
The source object is added to the CMS, keeping its name and updating the object with the same CUID. Properties that dont exist on the incoming object are preserved. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder B [CUID = 1] Rpt A [CUID = 2] Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2]
Update No rename
Different CUID The import of the source object fails: folder fails due to name Same path/name clash; report fails due to parent fail For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder A [CUID = 4] Rpt A [CUID = 3] Destination postimport Import fails.
Understanding Import Wizard options The Merge and Update import scenarios
Objects have...
Result
Same CUID In most cases, the source object is added to the CMS, Same path/name keeping its name and updating the object with the same CUID. Properties that dont 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 Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder A [CUID = 1] Rpt A [CUID = 2] Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2]
Update Rename
The source object is added to the CMS, with the same name and CUID. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder B [CUID = 3] Rpt A [CUID = 4] Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2] Folder B [CUID = 3] Rpt A [CUID = 4]
Update Rename
The source object is added to the CMS, with the same name, but overwriting the object with the same CUID. For example: Source Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder B [CUID = 1] Rpt A [CUID = 2] Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2]
Update Rename
Different CUID The source object is added to the CMS under a new name, Same path/name but keeps the same CUID. For example:
Understanding Import Wizard options The Merge and Update import scenarios
Objects have...
Result
Destination postimport Folder A[2] [CUID = 1] Rpt A [CUID = 2] Folder A [CUID = 3] Rpt A [CUID = 4]
Update Rename
Same CUID The source object is added to the CMS under a new name. It 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 Folder A [CUID = 1] Rpt A [CUID = 2] Destination preimport Folder A [CUID = 1] Rpt A [CUID = 2] Destination postimport Folder A [CUID = 1] Rpt A [CUID = 2]
You import an object named ObjectA then move it to a different folder which wasnt 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.
Understanding Import Wizard options The Merge and Update import scenarios
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.
Understanding Import Wizard options The Merge and Update import scenarios
chapter
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?
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.
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.
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.
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.
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.
chapter
10
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.
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.
10
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.
Features
Desktop Intelligence supports Unicode data sources, as well as report instances and discussions. You can set a value that formats a documents data (ndependently of the UIs 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.
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 Client Server Add-ins
10
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 isnt 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.
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.
10
10
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.
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
10
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.
10
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.
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).
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.
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.
10
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.
10
the Administration Consoles 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.
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. Auditors dashboard capabilities have been superseded by the XI R2 InfoView dashboard capabilities.
10
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 nameIdentifies 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 valueDefines the value of the profile name, such as city = San Diego. Profile targetDefines 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.
10
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 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.
10
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.
10
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 querybased 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.
Recreating security in XI R2
chapter
11
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.
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.
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.
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
11
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.
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
11
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.
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
11
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.
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.
11
11
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.
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.
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.
11
chapter
12
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.
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?
12
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.
12
How you structure you migrations 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 organizations structure, with separate universe and document domains for specific departments, such as sales, HR, or marketing. Migrating this way allows you to treat each departments 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 organizations particular requirements, security testing, and rollout.
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:
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 dont 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.
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
12
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 environments security from scratch in version XI R2s 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.
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. 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. Use predefined access levels whenever possible. Avoid setting advanced rights. This reduces the complexity of your security model.
2.
3.
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.
In the Import Wizards Choose objects to import dialog box, select all source objects including users and groups, domains, documents, universes and connections, and categories. In the Security Migration Options dialog box, select the first or second option, indicating that you want to migrate security. It doesnt matter whether you choose Update or Merge as migration scenario. If you chose Update, it doesnt matter what you select in the Incremental Import dialog box. (If you chose Merge, this dialog box doesnt appear.) This imports all your source users and content into the XI R2 environment, along with the same approximate effective security.
With each pass with the Import Wizard, select the users and/or objects you want to import. Select the first or second option in the Security Migration Options dialog box, indicating that you want to migrate security. The Update migration scenario is automatically selected for you. In the Incremental import dialog box, select whether you want imported objects to overwrite the content of instances already imported into XI R2, and/or the rights for those objects. Select the types of objects you want. This imports selected objects into the and content into the XI R2 environment; the same approximate effective security is retained in the destination environment.
12
Incremental
In the Import Wizards Choose With each pass with the Import 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 Wizards 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 dont box, which specifies you dont want to migrate security. want to migrate security. Choose Update as your It doesnt 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 doesnt 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.
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.
Determining a repositorys ID
You can determine a repositorys ID by running this SQL against the repository database:
SELECT M_GENPAR_C_LABEL FROM OBJ_M_GENPAR WHERE M_GENPAR_N_ID=121
12
Note: Never change the repository ID. Any modification could lead to a number of unwanted side effects that could stop your system from working.
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.
12
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.
12
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.
use different hardware for each life-cycle phase use a different installation of the Business Objects software for each lifecycle 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).
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 lifecycle 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.
12
Business Objects recommends separate, distinct repositories for each lifecycle 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. Copy all the content from your Development XI R2 repository to Test XI R2 repository. Copy all the content from Test to Production.
2. 3.
The CUID of an object in one repository will now have the same CUID as its corresponding objects in the other repositories.
12
This process implies that all development and test work has been promoted to production, since these domains are not migrated.
12
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. Copy all the content from your Development XI R2 repository to Test XI R2 repository. Copy all the content from Test XI R2 to Production XI R2.
2. 3.
The CUID for an object in one repository will now have the same CUID as its corresponding objects in the other repositories.
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.
12
12
This is also the moment to reorganize users and groups into more functional groupings, and review delegated administration.
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.
12
One or multiple VBA macros Non-universe data providers The Show/Hide object feature Conditional formatting The above features are rarely used. You require a strictly web deployment. Users need interaction with reports.
served an enterprise reporting purpose in the first place have sophisticated formatting requirements
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.
12
Pixel-perfect quality reports Printable reports Highly formatted reports Financial reports Regulatory/legal reports
When you import security, the rights imported on the objects are correct, regardless of the folder theyre 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.
12
You can do this before or after the import, but the structure must be in place before users begin using the system. If you dont 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
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 groupdocument 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.
12
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.
Option 1: You can copy the document into the folder corresponding to each group with access to the document. Advantage You dont have to create shared folders. Disadvantage You may end up with lots of copies of documents that may need maintaining.
Option 2: For documents being shared by the same groups, you can create shared folders. Advantage You have only one instance of a shared document to manage. Disadvantage You must create stored folders, which requires the proper analysis up front.
12
Power users Schedule documents Edit documents Publish documents Refresh documents
12
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 View Refresh Create Edit Publish Object right Version XI R2 Object right
Security command (application right) Object right Security command (application right) Application right Security command (application right) Object right Security command (application right) Object right
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 documents 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.
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.
12
chapter
13
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
13
13
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.
13
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.
13
3.
Restart Tomcat.
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
13
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.
$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
13
1.
Central Management Server Input File Repository Server Output File Repository Server 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.
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. 3. 4.
When the Log On page appears, select Enterprise in the Authentication Type list. Type your username and password. 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.
13
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. 2. Configure LDAP from the CMC. You just have to configure the connection parameters, you dont have to map any groups. 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, its 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 users personal content, only users that actually exists (i.e. have user objects) in the repository will have their personal content imported to XI R2.
chapter
14
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 youre migrating Application Foundation
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.
14
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.
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\
14
Using the Import Wizard Setting the source and destination environments
Summary of steps
The remaining steps in the Import Wizard are divided into:
Setting the source and destination environment Selecting the types of objects to import Selecting import options Selecting an import scenario Users and groups Broadcast Agents Categories Document domains and documents Universe and connection objects Universe domains and universes
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 youre 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. 8. 9.
Click Next. The Destination Environment dialog box appears. Type the name of the CMS of the destination environment. 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.
14
Yes, migrate security on imported objects and secure the destination system This is the most secure option. Yes, migrate security on imported objects Users in the destination system may end up with more rights than in the source system. No, dont migrate security 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. 1. 2. To select a security migration option In the Security Migration Options dialog box, select one of the three options. Click Next.
14
1.
To import personal and/or inbox documents 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.
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. 1. To select an import scenario 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 toplevel folders on the destination system, select the check box.
14
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.
Overwrite object contents You select the types of objects for which the content overwrite applies:
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 dont select any overwrite options, the object in the destination repository will not change when you try to import it again.
14
1.
To update previously imported objects In the Incremental Import dialog box, select the type of objects whose content you want to overwrite:
2. 3.
If you want to overwrite object rights, select the Overwrite object rights check box. 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.
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.
14
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.
2.
If you want to populate the database credentials of imported users with their BusinessObjects user name and password, select Yes. If you do not want to do this, select No.
Click Next.
Broadcast Agent
If you are importing Broadcast Agents, the Broadcast 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.) 1. To select Broadcast Agents for import In the Broadcast Agent dialog box, select the Broadcast Agents whose jobs you want to import. Note that all the jobs, for each Broadcast Agent, are selected by default. 2. Click Next.
14
Categories
If you are importing categories, the Categories dialog box appears. 1. To select categories Select the categories you want to import. For large document domains, you can import incrementally, and import documents one category at a time. 2. 3. If you want to import all the objects associated with the category, select the Import all objects that belong to the selected categories check box. Click Next.
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. 1. 2. To select domains and documents Select the domains and individual documents you want to import. When you select a domain, all the documents within it are highlighted. Click Next.
14
1.
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.
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.
2. 3.
To see more information about the events, click View Detail Log, and then see Checking the Import Wizard log file on page 290. Click Done.
14
2.
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.
name of the source repository database engine network layer of the source repository a user name and password to access the database
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. 8. Click Next. The Application Foundation Repository Update dialog box appears. Select one of the following options:
Yes to update the repository in the Import Wizard No to skip the repository update and migrate the repository later
Note: If you want to perform the migration in several steps, the Application Foundation repository must be updated at the end of the migration process. You can only update the repository once. If you are migrating rules and schedules, you must migrate them in the same Import Wizard session as the repository update. 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.
14
1.
To select the types of objects to import 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.
Yes, migrate security on imported objects and secure the destination system This is the most secure option. Yes, migrate security on imported objects Users in the destination system may end up with more rights than in the source system. No, dont migrate security 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.
14
1. 2.
To select a security migration option In the Security Migration Options dialog box, select one of the three options. Click Next.
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.
14
1.
To select an import scenario 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 toplevel 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.
Overwrite object contents You select the types of objects for which the content overwrite applies:
When you reimport an object, it will completely overwrite and replace the object (and its associated files) that you imported earlier.
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 dont select any overwrite options, the object in the destination repository will not change when you try to import it again. 1. To update previously imported objects In the Incremental Import dialog box, select the type of objects whose content you want to overwrite:
2. 3.
If you want to overwrite object rights, select the Overwrite object rights check box. 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.
14
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.
2.
If you want to populate the database credentials of imported users with their BusinessObjects user name and password, select Yes. If you do not want to do this, select No.
Click Next.
Broadcast Agent
If you are importing Broadcast Agents, the Broadcast Agents dialog box appears. This dialog box enables you to select the Broadcast Agents you want to import.
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.) 1. To select Broadcast Agents for import In the Broadcast Agent dialog box, select the Broadcast Agents whose jobs you want to import. Note that all the jobs, for each Broadcast Agent, are selected by default. 2. Click Next.
Dashboards
If you are importing dashboards, the Dashboards dialog box appears. 1. 2. To select dashboards Select the dashboards you want to import. When you select an application, its submenus are also selected. Click Next. The Import Wizard checks whether any dashboards in the source repository include security. If the Import Wizard detects security on any dashboards, the Import Dashboard Option dialog box appears. If none of the dashboards selected for import includes security, skip to step 4. 3. If dashboards selected for import include security, select one of the following options:
Import and apply page security on all page elements The Import Wizard migrates the dashboard and any sub-menus and applies standard page-level security, which is translated as an ACL in the CMS. With this option, the least restrictive set of rights is applied.
Dont import such dashboards The Import Wizard imports all dashboards, including dashboards with analytic-level security restrictions, but empties all content from pages containing secured elements. Dashboard menu structures are preserved.
14
Import but move to administrators Favorites folder for revision The Import Wizard imports all dashboards, including secured dashboards, but empties the content of all secured dashboards. When you choose this option, dashboard menu structures are preserved and a copy of each secured dashboard, including its contents, is moved to the administrators favorite folder. A prefix is added to the secured dashboards name so that the administrator can easily identify it after migration, then modify it manually before publishing it to a wider audience.
Categories
If you are importing categories, the Categories dialog box appears. 1. To select categories Select the categories you want to import. For large document domains, you can import incrementally, and import documents one category at a time. 2. 3. If you want to import all the objects associated with the category, select the Import all objects that belong to the selected categories check box. Click Next.
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. 1. To select domains and documents Select the domains and individual documents you want to import. When you select a domain, all the documents within it are highlighted.
14
2.
Click Next.
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.
14
1.
To select universes 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.
14
2. 3.
To see more information about the events, click View Detail Log, and then see Checking the Import Wizard log file on page 290. Click Done.
14
chapter
15
Checking and adapting the new environment Where you are now
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
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.
2.
15
Checking and adapting the new environment Verifying overall import success
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.
Checking and adapting the new environment Checking user/group and object import
15
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.
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.
15
Documents are not pixel-per-pixel identical. When a cell isnt 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.
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.
15
The settings can be changed on the following lines: <OPTION NAME="cell_width_wrap" VALUE="auto" /> <OPTION NAME="cell_width_autofit" VALUE="auto" /> Note:
Locale
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
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.
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 cant be imported.
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 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 Yes, migrate security on imported objects and secure the destination system Yes, migrate security on imported objects No, don't migrate security Impact Being the most secure option, this denies access to all objects and applications for the Everyone group. You must manually allow the access you want. This is a less secure option, so the settings for the Everyone group are not modified. You may need to manually restrict access. 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 Administrators Guide. 1. 2. 3. 4. For example, to check and adjust the rights for InfoView Log into the CMC. Select BusinessObjects Enterprise Applications > InfoView. Click the Rights tab. Adjust the rights to InfoView for the Everyone group.
15
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
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 Week periodicity Business day Weekend day Month periodicity Weekday Business day Weekend day
User-defined
15
Checking and adapting the new environment Verifying the Performance management environment
chapter
16
302
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 From 5.1.4 through 5.1.9 Calculation issues may arise if the documents contain:
Multiple cubes and global filters 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 The UniverseName() function Unicode fonts Decimal precision
Desktop Intelligence
303
16
global filters complex filters incompatible objects in the same block aggregation levels in synchronized data providers
Global filters
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 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+.
304
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.
305
16
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) US Resort Bahamas Beach Revenue $971,444 Sum: Future Guests 56 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. 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.
In the example:
Complex filters
Complex filters are filters that are based on a formula, for example:
Country <> France
306
16
Incorrect display of lists of values Different behavior when filtering empty values
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.
Data Provider 1: Country, Revenue Data Provider 2: Country, Revenue The second data provider has a query condition that restricts Country to US.
307
16
consideration and the third table with synchronized data providers contains one row: Country(DP1) France Revenue(DP2)
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
16
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:
309
16
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:
This information is synchronized around the one common dimension Country, but the relationship between Year and Reservation Year for any row is arbitrary.
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
16
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.
311
16
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
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.
The Count() function Filtering on empty values Filters on master detail reports containing incompatible objects Rankings The NoFilter() function Duplicate row aggregation
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
313
16
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.
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
16
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
315
16
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:
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 US
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
16
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")
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.
317
16
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
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.
319
16
320
Appendices
appendix
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.
324
Migration checklist for single pass migrations Preparing the destination environment
325
Migration checklist for single pass migrations Importing from the source to destination environment
Correct any problems indicated in the Import Wizard log file, and then reimport 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 reportto-report linking. Check converted .wqy to .wid files.
326
Migration checklist for single pass migrations Transferring or recreating other functions and tasks
327
Migration checklist for single pass migrations Transferring or recreating other functions and tasks
328
appendix
Documentation
You can find answers to your questions on how to install, configure, deploy, and use Business Objects products from the documentation.
Index
Symbols
@Variable('BOPASS') 91 @Variable('BOUSER') 91 Administrators (XI R2 user group) 68, 68 aggregation of rights in 5/6 vs. XI R2 71 rules per right type 122 universe access restrictions 122 agnostic documents importing 98 Allow user to merge dimension for synchronization right 96 analytics migrating 110 Application Foundation checking universe integrity 103 importing objects incrementally 107 migrating analytics 110 migrating dashboards 108 migrating named events 112 migrating objects without the repository 106 migrating rules 112 migrating schedules 111 migrating security commands 113 migration 100115 migration overview 28 migration paths 103 object migration 97 objects that migrate 104 repository upgrade during migration 25 resource migration overview 31 rules containing actions requiring prerendering 115 SVG files 109 Application Foundation objects 265 Application Foundation repository changes in performance management repository 105 ci_task table 111, 111 contents 105 importing repository connections 108 migrating 104
A
Access Control Entities see ACEs Access Control Lists see ACLs access rights see rights ACEs defined 21, 69 on import of stored procedures 93 on import of universe-related security commands 89 ACLs as benefit of XI R2 security 226 defined 69 on import of Application Foundation objects 113 overview 21 universe security 201 ActiveDirectory 51 add-ins migration 95 administration 5/6 vs. XI R2 52 Administration Console Audit facility 54 enabling servers 54 scheduling 55 setting authentication 50 setting locale 55 settings migration 83 tasks assumed by CMC in XI R2 20 Administration Launchpad 293 Administration SDK 206 available sample application 55 administrators in recreated security model 219
Index
modification during import 101 Application Foundation Repository Update dialog box 275 application rights after BusinessObjects migrations 151 after Designer migration 161 after WebIntelligence migrations 155 and full collapse 129 defined 120 migration 128 migration of 5/6 security commands 73 application servers and Desktop Intelligence deployments 193 role in 5/6 and XI R2 46 terminology in XI R2 43 applications importing application by application 224 appsecurity.exe custom security commands 113 auditing 5/6 vs. XI R2 54 how different in XI R2 203 setting up in destination system 259 Auditor analyzing which objects are used 239 capturing scheduling information in source environment 238 dashboard capabilities 203 indicators 203 migration assessment 203 migration overview 27 tasks assumed by CMC in XI R2 20 authentication multiple authentication schemes in XI R2 229 version 5/6 vs. XI R2 49 authorization 5/6 vs. XI R2 51 Autofit and impact on Desktop Intelligence documents 318 in imported Web Intelligence documents 294 Autofit cells different values in Unicode 196, 294
B
backing up repository 253 BIAR files 16, 224 defined 232 in incremental migrations 224 bomain.key file 50 Broadcast Agent capturing scheduling information 238 File Watcher 43 migration overview 27 non-supported jobs 298 tasks assumed by CMC in XI R2 20 Broadcast Agent Console capturing scheduling information 238 viewing scheduled tasks 55 Broadcast Agent dialog box 270 Broadcast Agent Publisher functionality in XI R2 205 migration 30 Broadcast Agent Scheduler job migration 30 Broadcast Agent schedules related to Application Foundation 115 Business Objects consulting services 332, 333 support services 331 training services 332, 333, 333 Business Objects consulting 17 Business Objects servers equivalent in XI R2 42 Business Objects web services 206 BusinessObjects 83 how Desktop Intelligence differs 194 migration of document rights 95 migration overview 26 rights migration 146155 scheduling 58 setting authentication in 2-tier mode 50 what does migrating involve? 197 BusinessObjects 5.1.3 and empty values 307, 307 and incompatible objects 309 and lists of values 307 BusinessObjects 5.1.4+ and empty values 308
Index
and incompatible objects 311 BusinessObjects 5.x and Count() function 314 BusinessObjects Auditor see Auditor BusinessObjects documents how Autofit can change in Desktop Intelligence 318 import limitations 95 importing 94 migrating OLAP data providers 95 migration of rights 95 re-establishing report-to-report links 295 Show/Hide object feature 240 troubleshooting failed import 295 Unicode and sorts 196, 294 Unicode implications 196 when to rewrite using Crystal Reports 240 when you should convert to .wid 240 which ones you should migrate 239 BusinessObjects Enterprise SDK 61 BusinessObjects OLAP migration 30 BusinessObjects SDK Send to BCA 95 Send to Inbox 95 BusinessQuery migration overview 27 BusinessQueryMD migration 30
C
calculations checking after import 293 categories 5/6 vs. XI R2 57 selecting for import 271, 282 Categories dialog box 271 Categories folder 93 CCM as administration tool 52 enabling/disabling CMSs 54 repository creation 46 starting CMSs 54 Central Configuration Manager see CCM Central Management Console see CMC
Central Management Server see CMS checking locale in Web Intelligence documents 295 ci_rule table 112 Client SDK 206 cluster nodes 43 clusters and repositories in XI R2 186 CUID 171 heterogeneous 45 multiple with single repository 188 setting locale 55 starting/stopping 54 version 5/6 vs. XI R2 42 CMC as administration tool 52 auditing 54, 203 category management 57 checking group membership 219 checking group rights on folders 217 checking user/group import 292 logging on 258 overview 20 password restrictions 69 performance management object rights 114 performance management user rights 114 publishing 205 publishing to repository 59 scheduling 204 security management overview 22 setting authentication 50 universe security 201 user/group creation 53 user/group organization 68 viewing scheduled objects 55 CMS 96, 97, 265 and Application Foundation objects 101 authentication 50 backing up database 257 clusters 42 deployment rules 186 ensuring Import Wizard can connect 258 InfoObjects 19 installing Import Wizard on CMS machine 255 license key storage 53
Index
overview 18, 42 Performance Management repository 103 repository 41 repository creation 48 Schedule Manager 111 storage of users and groups 72 Unicode 49 CMS scheduler 111 command-line installation 46 Compact 247 compatibility Designer 200 complex filters 304, 306 and BusinessObjects 5.1.3 307 reports affected by 306 connection rights full collapse 145 migration 145, 164 Connection Server and performance management 108 connections BOUSER/BOPASS variables 91 how the Import Wizard imports 89 migration overview 30 stored procedures 93 to Application Foundation repository 108 connectivities recreating in XI R2 253 consultants, Business Objects 332 converting .rep files to .wid 94 .rep files to .wqy 94 corporate document domains equivalent in XI R2 43 corporate documents storage after import 85 Count() function 313, 314 and BusinessObjects 6.0 315 Crystal Reports audit reports 203 customizing 62 data sources 56 scheduling 58, 204 when to rewrite BusinessObjects reports in 240
Crystal Reports SDK 62 cubes filtering 311 multiple 309 CUIDs 89, 96 as basis for import identification 171, 172 for dashboards 109 custom rights 119 customer support 331
D
Dashboard Manager Schedule HTML generation option 115 dashboards migrating 108 migrating security 109 requiring pre-rendering in .rep files 115 Dashboards dialog box 281 Data Integrator 38 updating 256 data sources creating on destination server machines 254 databases changing query databases 238 changing repository databases 237 migrating 31 supported in XI R2 253 synchronizing enterprise and database credentials 91 Unicode 49 using the DBUSER/DBPASS variables 91 Delegated Administration and universe access restrictions 76 establishing 76 deployment rules in XI R2 184 supported configurations in XI R2 25 deployment configurations migrating 188 derived universe 90 Designer 5/6 and XI R2 compatibility 90 5/6 vs. XI R2 54 and access restrictions in XI R2 92 checking access restrictions post-import 296
Index
compatibility with other versions 200 customizing in XI R2 62 migration assessment 199 migration overview 26 rights migration 161164 security management in XI R2 22 universe access restrictions in XI R2 202 Designer (user profile) 67 Designer SDK 62, 206 Desktop Intelligence and scheduling 195 and universes 196 and VBA macros and add-ins 195 BusinessObjects rights migration to 146155 compatibility between versions 196 customizing 62 default values for rights 149 deployment 193 deployment configurations 25 how different than BusinessObjects 194 installing 3-tier deployments 194 look and feel 194 report-to-report linking 198, 199 scheduling 58, 204 setting document locale 194 UniverseName() function 318 Desktop Intelligence documents accessing through InfoView 196 changes with Unicode 196, 294 setting locale 194 Desktop Intelligence SDK 62, 206, 207 Destination Environment dialog box 265 detail log 273, 285 Detail Log dialog box 291 Developer Suite migration overview 28 version 5/6 offering 60 directed acyclic graph (DAG) 68 distributed deployments version 5/6 vs. XI R2 45 document access rights default and aggregate rules 122 migration 139 net access 139 document domain rights
migration 132 document passwords 95 documentation feedback on 331 on product CD 330 on the web 330 roadmap 330 documents deleting using Compact 247 importing 93 importing without locales 94 migration overview 29 modifications during import 25 net access 139 specifying default locale for import 246 domain access rights 121 and full collapse 132 default and aggregate rules 122 defined 121 standard migration path 127, 127 Domain Key file 264 domains how they migrate 24 importing 93 importing domain by domain 224 importing universe domains 90 selecting for import 271, 282 Domains and Documents dialog box 271 duplicate row aggregation 318
E
Edit SQL right 96 education. See training empty values and BusinessObjects 5.1.3 307, 307 and BusinessObjects 5.1.4+ 308 filtering on 315 Enable Password Modification flag security command 74 Enable real time user rights update security command 74 Enabled/Disabled security command 74 Enterprise authentication 51 Event Server 43 and performance management rules 112
Index
Everyone (XI R2 user group) 68 post-import security settings 296 Excel Save as Excel as scheduling option 204 exporting objects 253
F
Favorites folder 43, 85 feedback, on documentation 331 File Repository Server see FRS File Watcher 43, 204 filters and incompatible objects 310 complex 306 inmaster/detail reports 315 finalizing the import 273, 273, 285, 285 folders checking group rights on in XI R2 217 Universe 90 fonts Unicode differences 196, 294 FRS and geographical distribution 188 connection storage 89 defined 19 deployment 185 object storage 41 full collapse and application rights 129 and connection access rights 145 and domains 132 functions Count() 314 MultiCube() 311
checking group rights on folders 217 checking membership 219 creation in 5/6 vs. XI R2 53 default groups in XI R2 22 impact of Merge/Update import scenarios 75 importing 269 migrating 72 migration overview 22 organization 67 post-import checking 293 principal 120 using inheritance in XI R2 212 which you should migrate 238 Guest (XI R2 user) 68 GUID 171
H
heterogeneous clusters 45
I
Identification strategy security command 74 Impact Analysis 203 import troubleshooting failed document import 295 Import Groups Option dialog box 269, 280 Import Options for Universes and Connections dialog box 271 Import Progress dialog box 273, 285, 291 Import Universe and Connection Objects Options dialog box 283 Import Wizard and BIAR files 224 and third-party documents 98 BIAR files 16 checking the log file 291 Detail Log dialog box 291 ensuring connection to the CMS 258 ensuring correct installation 257 high-level migration scenarios 227 how it compares source and destination objects 170 how it imports analytics 110 how it imports Application Foundation 100
G
General Supervisor 67 migration to XI R2 23 General Supervisor login 265 global filters 304, 304 and BusinessObjects 5.1.3 304 and BusinessObjects 5.1.4 305 groups access rights 69
Index
how it imports Application Foundation object security 113 how it imports Application Foundation objects 104 how it imports Application Foundation repository connections 108 how it imports Application Foundation rules 112 how it imports dashboards 108 how it imports documents 93 how it imports domains 93 how it imports universe connections 90 how it imports universes and connections 89 how it migrates Application Foundation schedules 111 Import Progress dialog box 291 incremental migration options 225 installing 255 launching 263 limitations 83 location of objects for import 83 mapping to Inbox and personal files 257 Merge and Update scenarios 169 optimizing performance 255 options explained 166 overview 15 pre-import steps 252 recommended hardware 16 requirements 15 security migration options 166 Security Migration Options dialog box 167 setting source and destination environments 264 specifying default document locale for import 246 importing categories 271, 282 checking user import 293 choosing an import scenario 267, 277 domains 93 Import Wizard options explained 166 mapping Import Wizard to Inbox and personal documents 257 Merge and Update scenarios 169 merging environments 267, 277
objects without rights 169 objects content or rights 173 post-import checks 290 post-import verification 25 security or not 225 selecting objects 265 setting default document locale 273, 284 universes 200 updating the destination environment 267, 277 users and groups 74, 269 ImportWiz.log file 291 ImpWiz.exe 257, 263 Inbox documents importing 267, 277 mapping Import Wizard to 257 migrating 29 storage after import 85 incompatible objects 304, 308 and BusinessObjects 5.1.3 309 and BusinessObjects 5.1.4+ 311 and filters 310 reports affected by 309 incremental import 223 initial import 223 of Application Foundation objects 107 ongoing updates 224 Update import scenario 172 updating contents/rights of objects 173 indicators 203 indirect filters and calculations 305 InfoObjects defined 19 Information Collection Complete dialog box 269 information resources 330 InfoView deployment 56 Desktop Intelligence document access rights 196 managing settings 55 migration overview 27 publishing 205 scheduling 204 setting locale 55
Index
XI R2 dashboard capabilities 203 XI R2 look and feel 198 inheritance overriding 71 using group inheritance in XI R2 212 using to recreate security in XI R2 217 installation command-line 46 ensuring correct Import Wizard 257 OLAP products 47 options in 5/6 and XI R2 45 required rights 257 silent 46 installing Import Wizard 255 XI R2 254 Interactive Editing right 96 Interactive Metric Trends (IMT) 208
importing documents without locales 94 importing locale by locale 224 migration of universe 89 setting 55 setting default document locale for import 273, 284 setting Desktop Intelligence document locale 194 specifying default document locale 246 Locales and Platform Options dialog box 273, 284 log file 290 Import Wizard 290 Login security command 74 LOVs access from XI R2 98 migration 201
M
Merge import scenario 171 and users/groups 75 merging repositories 228 merging source and destination environments 171 migrating analytics 110 Application Foundation 100, 104 Application Foundation rules 112 Application Foundation schedules 111 Auditor 203 BusinessObjects 193198 BusinessObjects documents 94 connections 90 dashboards 108 defined for third-party software 237 deployment configurations 188 Designer 199 documents 93 documents (overview) 29 domains 93 domains (overview) 28 in a single pass with the Import Wizard 223 incrementally 223 LDAP 79 managing licensing 24 Merge and Update import scenarios 169 objects without their rights 169
J
Job Server 43
K
Keep universe overloads 272 .key files and Desktop Intelligence 194
L
LDAP attribute variables 78 configuring security plug-in 259 migrating to XI R2 77 migration 77 license key management 47 licensing in XI R2 24 life-cycle management using the Update import scenario 230 List of Values see LOVs lists of values and BusinessObjects 5.1.3 307 locale and .wqy files 97 checking in Web Intelligence documents 295 format 246
Index
security or not 225 setting up new folder structure 241 third-party documents 98 to new query databases 31 to new repository database 31 top challenges 2026 universes 199 users with designer rights 202 using consulting 17 WebIntelligence 198 WebIntelligence OLAP 208 migration and BIAR files 224 Application Foundation objects 104 Application Foundation repository 25 application rights 128 assessment and planning 33 broad phases 31 capturing source scheduling information 238 connections 145 custom applications 28 databases 31 document access rights 139 document domain rights 132 domains 24 formulating strategy 222 handling locales 94 high-level migration scenarios 227 Import Wizard options explained 166 Inbox documents 29 incremental 223 initial import 223 LDAP 77 merging environments 171 methods (overview) 17 of groups 72 of rights 118164 of users 72 ongoing updates 224 overview of resource migration 28 personal documents 29 post-import verification 25 repository migration options 228 security commands 73 security migration options 166
single pass 223 standard path for user rights 125 stored procedure rights 145 stored procedures 164 top challenges 2026 troubleshooting schedule migration 111 universe access rights 139 universe domain rights 132 user parameters 69 user profiles 72 what migrates and what doesnt 2631 which objects you should migrate 239 which users/groups should you migrate? 238 migration assessment Auditor and auditing 203 BusinessObjects/Desktop Intelligence 193 Designer and universes 199 publishing 205 scheduling 204 SDKs 206 WebIntelligence OLAP 208 WebIntelligence/Web Intelligence 198 migration method incremental 223 single pass 223 migration planning capturing source scheduling information 238 checking supported platforms and versions 237 choosing a migration method 223 import security or not 225 repository migration scenarios 228 what objects you should migrate 239 which users/groups should you migrate? 238 migration strategy formulating 222 high-level scenarios 227 modules equivalent in XI R2 41 Multicube() function 311 multiple cubes internal handling of 310 MySQL 46
Index
N
.NET Server Controls for BusinessObjects Enterprise 61 Netegrity SiteMinder 51 NoFilter() function 311 and Where clause 317 and Where clause in BusinessObjects 5.x 317 and Where clause in BusinessObjects 6.0 317 Not Specified option best practices 216
P
Password security command 74 Password Validity settings security command 74 passwords using the DBUSER/DBPASS variables 91 performance management 28 managing use rights 114 PIKs 208 repository 105 security migration limitations 115 troubleshooting schedule migration 111 what you cannot migrate 114 whats new in XI R2 207 performance management engines 108 performance management repository 97 Personal Categories folder 93 personal document domains equivalent in XI R2 43 personal documents importing 267, 277 mapping Import Wizard to 257 migrating 29 storage after import 85 planning see migration planning Platform COM SDK 95 platform support list of supported platforms 31 platforms updating 253 XI R2 platform and version support 237 Populate Database Credentials dialog box 270 Populate Database Credentials for Users dialog box 280 Portal Integration Kits for performance management 208 predefined settings 74 pre-rendering and Application Foundation dashboards 115 primary nodes 43 principals defined 66, 120 Process Tracker whats new in XI R2 208 product access rights default and aggregate rules 122
O
object IDs 92 Object Security level security command 74 objects CUID 171 exporting 253 restrictions 92 rights 121 selecting for import 265 storage 41 which should you migrate? 239 OLAP document migration overview 30 installation of OLAP products 47 OLAP data providers and Desktop Intelligence 194 OLAP Intelligence scheduling 58, 204 ONAMES 254 Online Customer Support 331 Only look for documents in personal inbox option 115 openDoc document-to-document links 295 Oracle ONAMES 254 TNSNAMES 254 ORB configuring 47 configuring in version 5/6 46 orphan documents defined 94
Index
defined 120 standard migration path 126 products version 5/6 vs. XI R2 offering 37 profiles how they migrate 72 in version 5/6 44 in XI R2 44, 205 migration to XI R2 23 Public folder 43, 85 publishing in XI R2 205 profiles in XI R2 205 Publishing Wizard 59
Q
Query Builder tool 198, 293 query databases migrating 31
R
.rea files access from XI R2 98 migration 29 Ready to Import dialog box 273 REBean SDK 207 RECOM SDK 206, 207 Rename option Merge import scenario 171 Update import scenario 172 .rep files migrating 94 when locales are not stored in documents 246 Repair and Compact 252 Report Application Server SDK 61, 206 report bursting 44 Report conversion tool 197 overview 16 when you should convert .rep to .wid 240 Report conversion tool Users (XI R2 user group) 68 Report viewers SDK 206 repositories 5/6 vs. XI R2 41
backing up 253 changing databases for migration 237 creating 48 creation in 5/6 vs. XI R2 46, 53 determining ID 229 exporting locally-stored objects 253 geographically-distributed 188 GUID 171 migrating to different repository database 31 migration options 228 publishing to 59 Repair and Compact before import 252 version 5/6 vs. version XI R2 19 when multiple source repositories have the same ID 229 resources 330 restriction sets see universe access restrictions .ret files and migration 94 rights 5/6 vs. XI R2 aggregation rules 122 5/6 vs. XI R2 defaults 122 5/6 vs. XI R2 inheritance 123 aggregation in 5/6 vs. XI R2 71 application rights 120 collapsing 119 custom 119 domain access rights 121 effective 119 explicit 119 migrating objects without rights 169 migrating or not 225 migration 118164 migration of BusinessObjects document rights 95 migration of security commands 73 Modify Rights right (MRR) 76 newly-denied 119 newly-granted 119 object rights 121 product access rights 120 rights collapsing 128 standard migration path 125 terminology in XI R2 119 universe/document access 121
Index
user access 69 version XI R2 76 View right 120 XI R2 aggregation overview 22 rights collapsing defined 128 Rights Fidelity mode 169 rights inheritance breaking in XI R2 124 rights migration overview 22 .rkey files and Desktop Intelligence 194 row restrictions 92 run-time rebinding defined 233
S
Scan and Repair 247 Schedule Manager 111 schedules troubleshooting migration 111 scheduling 5/6 vs. XI R2 58 and VBA macros in XI R2 204 capturing source scheduling information 238 non-supported jobs 298 recreating in XI R2 298 setting up 55 version XI R2 58 viewing scheduled jobs for user 55 viewing tasks 55 what does migration involve? 206 SDK 83 version 5/6 offering 60 version XI R2 offering 61 SDKs version 5/6 vs. XI R2 206 secondary nodes (version 6) 43 Secure Modify Rights right (SMRR) 76 security Administrators group 219 application rights 120 best practices with Not Specified option 216 checking post-import 296
collapse 119 configuring LDAP security plug-in 259 domain access rights 121 importing object security in incremental imports 173 importing objects without 169 importing or not 225 inheritance 5/6 vs. XI R2 70 managing performance management object rights 114 managing performance management user rights 114 migrating dashboard security 109 migration options 166 Modify Rights right 76 object rights 121 overview of differences between 5/6 and XI R2 21 password restrictions in XI R2 69 performance management migration constraints 115 predefined settings 74 product access rights 120 profile migration overview 23 recreating in XI R2 209219 rights collapsing 128 rights migration 118164 rights migration overview 22 Secured Modify Rights right 76 security commands 121 setting for Everyone user group 296 setting up content security in XI R2 214 synchronizing enterprise and database credentials 91 universe 201 version 5/6 vs. XI R2 120 version 5/6 vs. XI R2 inheritance 123 View right 120 XI R2 aggregation overview 22 security commands and BusinessObjects document migration 151 and Designer migration 163 and WebIntelligence document migration 96 combining during migration 127 default and aggregate rules 122
Index
defined 121 how they migrate 73 migrating Application Foundation 113 migration of universe-related 89 negatively-phrased 127 standard migration path 126 Security Migration Options dialog box 167, 266 security models overview of differences between 5/6 and XI R2 21 Select Objects to Import dialog box 265 selecting for import categories 271, 282 objects 265 selectingfor import universes and connections for import 272, 283 semantic layer migration of 29 Server SDKs 206 servers defined for XI R2 41 Session Stack 45 silent installation 46 single pass migration 223 Single Sign-On see SSO software what migrates and what doesnt 26 SQL Server importing connection objects from 5/6 91 SSO 5/6 vs. XI R2 51 stored procedure rights how they migrate 164 stored procedures definition 145 migration overview 29 rights 145 Stored Procedures Access right 93 Supervisor creating repositories 48 how its functions migrate 22 migration overview 26 Repair and Compact 252 running a Compact 247 tasks assumed by CMC in XI R2 20
universe access restrictions 92 user/group creation 53 Supervisor (user profile) 67 Supervisor over the Web migration overview 26 tasks assumed by CMC in XI R2 20 user/group creation 67 Supervisor-Designer (user profile) 67 support customer 331 locations 331 technical 331 web site 331 supported deployment configurations in XI R2 25 supported platforms XI R2 support for platforms and versions 237 SVG files and migration 109 synchronizing enterprise and database credentials 91
T
table mapping 92 technical support 331 third-party documents importing 98 time for importing 263 Timestamp security command 74 TNSNAMES 254 Tomcat 256 training, on Business Objects products 332 troubleshooting document migration 295 schedule migration 111
U
Unicode databases 49 and Desktop Intelligence 194 implications when migrating BusinessObjects documents 196 Unified Web Services Consumer SDK 62 universe access restrictions aggregation rules 122
Index
and Delegated Administration 76 defined 29, 202, 202 equivalent in version 5/6 44 universe access rights and Delegated Administration in XI R2 76 default and aggregate rules 122 defined 121 migration 139 standard migration path 127 universe connections see connections Universe Designers Users (XI R2 user group) 68 universe domain rights migration 132 Universe Folders and Universes dialog box 272 universe overloads equivalent in XI R2 44 universe overloads see universe access restrictions universe restriction sets see universe access restrictions UniverseName() function 318 universes and Desktop Intelligence 196 checking access restrictions after import 296 checking integrity of those used by Application Foundation objects 103 exclusive overloads 92 how they are imported 89 importing associated universes 90 importing local 200 LOV migration 201 migration overview 29 modes of import 90 overload aggregation 92 overload collapsing 92 restriction set aggregation 122 run-time binding 233 security 201 selecting for import 272, 283 short name 90 storage in XI R2 200 the BOUSER/BOPASS variables 91 tools that use 56 using the DBUSER/DBPASS variables 91 UNIX BusinessObjects Enterprise servers on 255
importing Inbox and personal documents 258 mapping to personal/inbox documents 267, 277 .unv files what is contained in (XI R2) 200 Update import scenario 172 and users/groups 75 using for life-cycle management 230 updating platforms and versions 253 previously imported objects 269, 279 the destination environment 172 upgrading defined for third-party software 237 Use Pre-generated HTML when available option 115 User (profile) 67 user creation 5/6 vs. XI R2 53 user groups see groups user/group access rights 69 user/group inheritance 70 usernames case-sensitivity 69 users and licensing in XI R2 24 case-sensitivity for usernames 69 how profiles migrate 72 impact of Merge/Update import scenarios 75 importing 269 migrating 72 migrating external users 77 migrating with designer rights 202 organization 67 parameter migration 69 post-import checking 293 principal 120 which you should migrate 238 Users and Groups dialog box 269
V
VBA 204 VBA add-ins migration 29 VBA macros
Index
and Desktop Intelligence 195 and Desktop Intelligence SDK 207 and scheduling in XI R2 204 migration 98 reason not to convert .rep to .wid 240 Windows vs. UNIX 207 Versatile (user profile) 67 version 5/6 architecture 38 authentication 50 capturing scheduling information 238 clusters 42 command-line installation 46 determining a repositorys ID 229 distributed repository domains 25 domain access rights 121 domain migration 28 heterogeneous clusters 45 how applications migrate 26 how domains migrate 24 Inbox and personal storage 257 installation options 45 module equivalent in XI R2 41 overview of resource migration 28 product access rights 120 product offering 37 profile migration 23 publishing to repository 59 reporting tools 56 rights aggregation 71 rights migration 118164 running Repair and Compact 252 scheduling 58 SDK offering 60 security commands 121 setting locale 55 SSO 51 starting and stopping clusters 54 terminology compared to XI R2 40 universe access rights 121 user/group organization 67 vs. XI R2 inheritance rules 123 web applications 47 version XI R2 access restrictions 92
administration 52 application rights 120 architecture 39 authentication 50 basic concepts 1820 categories and folders 57 default groups 22 deployment rules 184 enabling/disabling servers 54 how version 5/6 applications migrate 26 how version 5/6 software migrates 26 InfoObjects 19 installation options 45 installing 254 licensing model 24 migrating external users 77 Modify Rights right (MRR) 76 multiple authentication schemes 229 object rights 121 object storage 41 password restrictions 69 platform and version support 237 product offering 37 publishing 204, 204 publishing to repository 59 reporting tools 56 repositories 19 rights aggregation 71 rights aggregation overview 22 rights terminology 119 scheduling 204, 204 Secure Modify Rights right (SMRR) 76 servers 41, 41 setting up auditing 259 silent installation 46 SSO 51 starting and stopping CMSs 54 starting server machines 258 supported connectivities 253 supported deployment configurations 25 terminology compared to 5/6 40 universe security 201 universe storage 200 user rights 69 user/group organization 68
Index
View right 120 vs. 5/6 inheritance rules 123 web applications 47 view detail log 273, 285, 291 View right 120 Viewers SDK 61 Visual Basic for Applications 60
W
WCA and web servers 46 defined 46 web customer support 331 getting documentation via 330 useful addresses 333 web application servers 43 web applications 47 customizing in XI R2 61 Web Component Adapter see WCA Web Connect and Desktop Intelligence 195 Web Intelligence Allow user to merge dimension for synchronization right 96 and .unw files 200 Audit reports 203 customizing 62 Edit SQL right 96 Interactive Editing right 96 potential report changes after import 198 scheduling 58, 204 WebIntelligence rights migration to 155161 whats new 198 when should you convert .rep to .wid? 240 Web Intelligence documents Autofit behavior in XI R2 294 checking locale 295 default values for rights 157 re-establishing report-to-report links 295 Web Intelligence Report Server 43 Web Intelligence SDK 62, 207 web servers role in 5/6 and XI R2 46 web services 62
web sites support 331 training 332 WebConnect documents access from XI R2 98 WebIntelligence migrating orphan documents 94 migration assessment 198 migration overview 27 rights migration 155161 what does migration involve? 199 WebIntelligence documents migrating .wqy and .wid files 29 migration 96 migration limitations 97 rights migration 96 troubleshooting failed import 295 .wqy update during import 199 WebIntelligence OLAP migration 30, 83 migration assessment 208 WebIntelligence SDK 206 Welcome page 264 .wid files importing 96 migrating orphan documents 94 migration overview 29 Windows install Import Wizard on Windows machine 254 WIReportServer 43 .wqy files and locale 97 importing 96 migration overview 29 update during import 199 when locales are not stored in documents 246
X
XI R2 auditing overview 203 recreating security in 209219