Upgrading BI Applications (For Instance, Finance, Marketing, and Sales) From XI Release 2 To XI 3.0: A Live Experience

Upgrading BI applications (for
instance, Finance, Marketing, and

Sales) from XI Release 2 to XI 3.0:
a live experience
XI 3.0
windows
Copyright © 2008 Business Objects, an SAP company. All rights reserved. Business Objects
owns the following U.S. patents, which may cover products that are offered and
licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250;
5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698;
6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068;
6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189;
6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440;
7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and
its logos, BusinessObjects, Business Objects Crystal Vision, Business Process
On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications,
Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal
Vision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, Table
Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts,
RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are
trademarks or registered trademarks in the United States and/or other countries
of Business Objects and/or affiliated companies. SAP is the trademark or registered
trademark of SAP AG in Germany and in several other countries. All other names
mentioned herein may be trademarks of their respective owners.
Third-party Business Objects products in this release may contain redistributions of software
Contributors licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
2008-10-17
Contents
Chapter 1 Preface 7
About this book............................................................................................8
Comments welcome....................................................................................8
Chapter 2 Fundamentals 9
The pre-existing system.............................................................................10
Actors, roles and responsibilities...............................................................10
Project Upgrade Team..........................................................................11
Business Intelligence Team..................................................................12
Operations Team .................................................................................13
Business Solution Owners ..................................................................13
Users....................................................................................................14
What is an upgrade?..................................................................................15
Reasons to upgrade..................................................................................15
Deciding on the major type of upgrade......................................................17
Side-by-side vs. completely new installation from scratch ..................17
Multiple XI 3.0 system installations .....................................................18
Upgrading with Import Wizard, CMS database setup tools, or third-party
tools?....................................................................................................20
Incremental vs. one-shot upgrade .......................................................20
Chapter 3 General approach of the BusinessObjects XI 3.0 upgrade project 23

Phase 1: Assessment and Strategy..........................................................24
Phase 2: Pre-implementation ...................................................................24
Phase 3: Qualification environment installation and upgrade ...................25
Phase 4: Production environment installation...........................................25
Upgrading BI applications (for instance, Finance, Marketing, and Sales) from XI Release 2 to XI 3.0: a live experience
3
Contents
Phase 5: Production environment upgrade and Roll out ..........................25
Chapter 4 Assessment and strategy 27

Step 1: Define the overall plan..................................................................28
Plan......................................................................................................28
Go/No Go meetings..............................................................................29
Regular Communication among Project Upgrade Team members......31
Step 2: Define the requirements................................................................31
Step 3: Analyze and understand the system ............................................33
Step 4: Answer the requirements..............................................................35
Step 5: Finalize the roadmap and hold go / go no meeting.......................37
Chapter 5 Pre-implementation 41
Step 6: Ask for, set up and use the sandbox.............................................42
Order the materials ..............................................................................42
Check the hardware and accounts.......................................................44
Back up and restore the solution .........................................................45
Step 7: Define the architecture..................................................................46
XI 3.0 architecture ...............................................................................46
Explanation of shared services ...........................................................49
Expandable architecture.......................................................................50
Step 8: Define the main upgrade strategy.................................................51
Step 9: Define the test plan strategy.........................................................52
Step 10: Define the training plan...............................................................53
Step 11: Clean the current environment....................................................54
Step 12: Conduct a go/no go meeting to start the test implementation.....55
Chapter 6 Qualification environment installation and upgrade 57

Step 13: Ask for the qualification platform.................................................58
Step 14: Finalize the upgrade wizard strategy .........................................58
4 Upgrading BI applications (for instance, Finance, Marketing, and Sales) from XI Release 2 to XI 3.0: a live
experience
Contents
Step 15: Install in a qualification environment ..........................................60

Install the BusinessObjects Enterprise Servers cluster1 .....................60
Install another set of BusinessObjects Enterprise servers cluster2.....66
Run with the services account..............................................................72
Cluster the file repository servers.........................................................73
Configure server parameters................................................................75
Configuration of Active Directory..........................................................75
Configure the load balancer ................................................................82
Configure the audit database...............................................................82
Back up the installation .......................................................................83
Step 16: Upgrade the qualification system................................................83
Installation of computer running Import Wizard....................................84
Specify BusinessObjects Enterprise XI Release 2 as the source
environment..........................................................................................84
Specify BusinessObjects Enterprise XI 3.0 as the destination
environment..........................................................................................85
Security freeze.....................................................................................86
First instance of the Import Wizard.......................................................86
Set up the XI 3.0 BusinessObjects security model..............................90
Second instance of the Import Wizard.................................................95
Configuration after the Import Wizard has run...................................100
Step 17: Test the qualification system.....................................................100
Functional testing...............................................................................100
User Acceptance Testing (UAT).........................................................109
Benchmark testing..............................................................................110
Step 18: Conduct a go/no go meeting to start the production environment
installation ...............................................................................................110
Chapter 7 Production environment installation 113

Step 19: Ask for the production platform.................................................114
Step 20: Install in a production environment ..........................................115
5
Contents
Step 21: Conduct a go/no go meeting to start the production environment

upgrade ...................................................................................................115
Chapter 8 Production environment upgrade and roll out 117

Step 22: Plan the rollback strategy..........................................................118
Step 23: Communication, user training and cut-over preparation...........118
Step 24: Upgrade the production system ...............................................119
Step 25: Perform the last validation.........................................................120
Step 26: Conduct a go/no go meeting to roll-out the production implementation
.................................................................................................................121
Step 27: Upgrade the desktop client.......................................................122
Step 28: Roll out......................................................................................122
experience
Preface
1
1 Preface
About this book
About this book

Upgrading BI applications (for instance, Finance, Marketing, and Sales) from
XI Release 2 to XI 3.0: a live experience, created as part of the Customer
Intelligence program, is intended to provide Business Objects customers
with enhanced documentation to aid in planning and deployment of
BusinessObjects Enterprise systems.
This upgrade was performed on XI 3.0, but it should work exactly the same
for XI 3.1.
The primary objective was actually to document the upgrading of some BI

applications (for instance, Finance, Marketing, Sales) from XI R2 to XI 3.0.
This book documents a specific end-to-end BusinessObjects Enterprise
deployment upgrade that runs in a Windows environment. It includes planning,
requirements, architecture, installation, configuration, tuning steps, CMC
security settings , use of the Import Wizard, testing, training and final roll out.
The company chose one type of upgrade (in this case Import Wizard), but
each project is different. Depending on your needs, you will choose different
options, such as CMS database setup tools or third-party tools. So, even if
you did not use the same upgrade tools, this book can answer your questions
about other points of your upgrade process.
It can be used as a guide for planning and deployment of BusinessObjects

Enterprise systems, or as a reference for upgrading of individual system
components.
The guide is best used in conjunction with BusinessObjects XI 3.0 installation,
deployment, upgrade, migration, and administration documentation. For
instance:
• BusinesObjects Enterprise XI 3.0 Administrator's Guide
• BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide
for Windows
• BusinessObjects Enterprise XI 3.0 Import Wizard Guide
• BusinessObjects Enterprise XI 3.0 Upgrade Guide
Comments welcome
Your feedback is important to us. You can send your comments about this
book to: jc.raveneau@sap.com
experience
Fundamentals
2
2 Fundamentals
The pre-existing system
Note:
This document introduces you the process of upgrading from an XI R2 system
to an XI 3.0 system, but it should work exactly the same for all XI/XI R2
version to XI 3.0/XI 3.1.
We wrote this documentation at the same time as we followed the real
upgrade of one company. We explain how this company proceeded and give
their roadmap and processes. Of course, the steps and the duration of an
upgrade depend on your organization and system. Each company has a
different structure and systems. So, you need to adapt this document to your
company and system.
The pre-existing system

This company's system is a shared-services platform that hosted all the BI
applications (for instance, Finance, Marketing, Human Resources, R & D,
Sales) . Over the last year, members of the team in charge of this environment
have worked diligently to create an enterprise-wide standard operational
documenting platform built on XI R2. All the departments use it as the central
system to follow their activities.
The system was running on SQL Server 2000 SP3. (The Operations Team
wanted to move to an Oracle 10G CMS database because this is the new
standard for the company.)
The system has more than 6,000 users on production (at least 200 concurrent
users 24 hours/day; 1000 concurrent users at quarter closing), more than
1,500 folders, 10,000 corporate documents, more than 20,000 documents
(Microsoft Excel, Web Intelligence, and Crystal) in Inbox and Favorites folders.
Of those using the Refresh functionality, 95% are running Web Intelligence
and 5% Crystal and Desktop Intelligence. Of those using the Schedule
functionality, 50% are running Web Intelligence and 50% Crystal. Each week
10,000 instances are created.
Actors, roles and responsibilities

Each company has its own business area (insurance, bank, industrial,
agro-alimentary, etc.) However, if you are using a common BI solution, your
company tends to be organized in a standard / common structure. Of course,
the name of your departments will not be exactly the same as in this
document, but the actors, roles and responsibilities will not change.
experience
Fundamentals
Actors, roles and responsibilities 2
In the next five topics, we present the various teams involved in the upgrade
and their roles.
Project Upgrade Team
In the case of an upgrade project, you will have one team who will manage
this project. In this company, the upgrade project was driven by the Business
Intelligence (BI) Team in collaboration with the Operations Team, and
Business Solution Owners. The BI team designated one Project Manager,
who managed one virtual team composed of users from these BI
applications.This team was called the Project Upgrade Team.
11
2 Fundamentals
Business Intelligence Team
Their roles:
The BI Team's role is to manage the BusinessObjects BI applications. They
have three systems: development/sandbox, qualification and production.
They have access to all BI applications (on development, qualification and
production environments). However, they can access the BusinessObjects
systems (computers) only on the development and qualification environments.
In this team are found:

• BI project group (defines and manages each BI project)
• BI architect group (defines the BI implementation and architecture)
• BI administrator group (sets up security on the all environments)
• BI power user group (creates main documents and universes for Business
Owners)
• BI support group (gives support to the Business Solution Owners)
Their interaction with other teams:
The BI Team needs to work with the Operations Team for 2 main reasons:
1. The Operations Team is expert in the installation and configuration of
third-party servers and software (OS, Application servers, Active Directory,
Load balancer, etc.) The Operations Team will set up this third-party
software and later on, the BI Team will only modify some parameters
linked to the BusinessObjects software.
2. The BI Team are not allowed to access the production environment
(servers).
On the production environment, rules are really strict due to the security
policies. The team (Operations Team) who controls the system is different
from the team using it (BI Team), so one cannot do error-prone things on
the system and break it. All operations that need to be done on the production
servers (systems) need to be done by the Operations Team. If the BI Team
wants to do something on these servers, they have to write a request and
create a case to give to the Operations Team. The Operations Team will
execute it following exactly what has been written (for example,
BusinessObjects XI 3.0 installation and some configuration parts are written
by BI Team and executed by Operations Team).
experience
Fundamentals
Actors, roles and responsibilities 2
The BI Team needs to work with the Business Solution Owners. They are
also ultimately responsible for all BusinessObjects security requests, main
template documents and universe creation and for the support of all the
Business Owners. They do not work with users.
Operations Team
Their roles:
The Operations Team's role is to manage all physical servers (on

development, qualification and production environments). They do not need
to have knowledge on the BI applications (even if they may know the product
quite well). They are also in charge of all databases (data, CMS, and audit);
they have to put in place the monitoring on all systems (CPU, RAM, disk
etc.); and ensure that all physical servers are working correctly.

• Operations architect group (defines the network, OS and DB architecture)
• Operations system administrator group (manages hardware and operating
system; manages day-to-day administration tasks and regular back-ups;
performs system maintenance/monitoring; perform code changes for
production and also between environments (Development, Qualification
and Production )
• Operations Database administrator group (manages all databases;
manages regular back-ups)
• Operations support group (troubleshoots the BI computers (only the part
related to the hardware or non-BusinessObjects software) and gives
support to the BI Team.
They work with the BI Team as mentioned above. They do not work with
either users or Business Solution Owners
Business Solution Owners
Their roles:
The Business Solution Owners belong to the various business departments.

They are users that have the overall responsibility for one or more application
13
2 Fundamentals
in their business. As such they are a proxy between the users and the BI
Team.
The Business Solution Owner's role is to support users and, if necessary,

escalate the problems to the BI team. The Business Solution Owners have
regular meetings with the users to explain to them how to use the products
in the everyday life and to see that their needs are being met. As explained
earlier, the BI team cannot talk directly with all users (there are more than
6,000 users in this company), so they need to talk to these Business Solution
Owners. Business Solution Owners also own the BusinessObjects security
on their application. They may perform simple administrative tasks limited
to their application.

• Business Solution Owners support group gives support to the users. (The
Business Solution Owners use CMC, InfoView, Crystal, Web Intelligence,
PMC, etc. to do their daily work, so they see the same situations the users
see.)
• Business Solution Owners' Delegated Administrator can modify some
security rights only on a application level.
• Business Solution Owners power group creates main documents for
users.
The Business Solution Owners have regular meetings with the users to
understand their needs and problems. The Business Solution Owners also
have regular meetings with the BI team to explain to them the users' needs
and problems. They do not interact with the Operations Team. Of course,
for the upgrade project, the Business Solution Owners were heavily impacted
and each department that was impacted by the upgrade designated one or
more of these Business Owners to participate in this project.
Users
Their roles:
The users' role is to use the product and then contact the Business Solution
Owners if they have requests or issues. Users use the product to follow their
business activities, (for instance, Finance, Marketing, Human Resources,
Sales).
experience
Fundamentals
What is an upgrade? 2
• Normal users use InfoView, Crystal, Web Intelligence, PMC, etc. to do
their daily work. They open, refresh, and schedule documents.
• Power user use the same BI applications and they can create or modify
the documents.
They talk to the Business Solution Owners if they have requests or issues.
They do not interact with the BI Team or Operation teams because there are
too many of them. Therefore, each user has one or more contacts (called
Business Solution Owners); each time the user wants an explanation on the
product or wants to change something in this profile or add or modify
documents or universes, the users will contact the Business Solution Owners
who will manage the request or discuss directly with the BI team if they cannot
do it by themselves.
What is an upgrade?
An upgrade is an installation of a new version of the software that requires
no changes to the platform or system architecture. Moving from
BusinessObjects 6.5 to XI/XI R2/XI 3.x was a migration (which does require
changes to the platform or system architecture); from XI /XI R2 to XI 3.x is
an upgrade.
Reasons to upgrade
Below are the most important reasons why this company decided to upgrade.
The main reasons were to answer users' needs, to facilitate the administration
operation and to answer the Operations Team's new orientation.
The users really wanted to use the new features offered by XI 3.0 because
they answered needs that were not answered in XI R2.
• Users wanted to use the new XI 3.0 Web Intelligence features.
• The company's sales team and a number of other 'on the road' roles
needed to view and analyze their data off-line from the server. Since
the strategy is to progressively move from Desktop Intelligence to Web
Intelligence, those users needed the off-line more in Web Intelligence.
The Web Intelligence Rich Client, a standalone version of the Web
Intelligence Java Report Panel, allows the employees on-the-road to
15
2 Fundamentals
Reasons to upgrade
work with Web Intelligence documents without accessing a CMS. They

can show these documents to a customer during meetings, etc. even
without a network connection. This was their most pressing need.
• Users were often bothered by connection timeouts in the middle of
document development when they are on stand-by (phone call, short
break, lunch, etc.) Now they can connect to a CMS and use the Web
Intelligence Rich Client as an online alternative to the Java Report
Panel to solve this problem. Rich Client users can work on their
documents the entire day without risking losing documents because
of a lost connection or time out.
• Quite a few historic Desktop Intelligence users had developed
documents based on personal files such as Excel spreadsheets. This
capability was not available in Web Intelligence XI R2 and was needed
to pursue their 'full Web Intelligence ' strategy. The Web Intelligence
Rich Client allows them to create documents based on personal data
providers such as text or Excel files.
• Other BusinessObjects products (Data Integrator, Metadata Manager,

and BI Mobile) released in XI 3.0 contain new features that the
administrators and users would like to use. In order for them to use these
improved products, the company first has to upgrade the BusinessObjects
Enterprise system.
• In XI R2, in the navigation panel of InfoView, the users wanted to see
subfolders, but could not. When the user clicked the folder that contained
both documents and sub-folders, he could not see the subfolders in the
right navigation panel. Many users were confused about this view. With
the new version, they can see subfolders easily because of improved
navigation.
• The Administration Group wanted to use the new XI 3.0 Platform features.
• In XI R2, an administrator who used the system everyday found it
difficult to view, organize and, even, find users and groups. The new
CMC view in XI 3.0 contains a tree structure that allows the
administrator to find and view, organize and find users and groups
more easily. The use of this feature was the main reason the
Administration Group wanted to move to XI 3.0 as quickly as possible.
• In XI R2, there were five pre-defined access levels and it was not
possible to customize them in any way. In XI 3.0, the administrator
can create and maintain access levels that are customized for their
deployment and security needs. Access levels allow administrators
to set common security levels quickly and uniformly rather than
requiring that individual rights be set one-by-one.
experience
Fundamentals
Deciding on the major type of upgrade 2
• The Administration Group is always concerned about performance,
reliability, and scalability. By using BusinessObjects XI 3.0, they will be
able to take advantage of new technologies and updates that make
BusinessObjects XI 3.0 more robust and easier to scale than earlier
versions.
• The Administration Group wanted to anticipate the future. All subsequent
migrations to newer BusinessObjects technology will become easier if
they are running the latest version. The security model has the same
structure on the new system. Web Intelligence, Desktop Intelligence, and
Crystal Reports keep the same structure (they do not need to be
converted). The same is true for the universes. The Administrator Group
saw the advantage of using new technology in this upgrade, without
converting all the documents and changing the security model. (These
activities would have taken a lot of time.)
• Finally the Operations Team wanted to move the CMS to Oracle 10G
and move the entire system to VMware images.
Deciding on the major type of upgrade

The following four topics describe some of the decisions that were made
about the type of upgrade to be carried out.
Side-by-side vs. completely new installation from

scratch
The advantage of a side-by-side installation would be that you would not

have to buy any new hardware. However, the disadvantage would be to slow
down the performance by overloading the machines (by having the two
system XI R2 and XI 3.0 on the same computer).
Therefore, the project upgrade team chose a completely new installation

from scratch because XI R2 performance needed to be maintained and the
performance of XI 3.0 would not be fast enough on a shared system. In this
case, the hardware was not a show stopper since during the upgrade as the
XI 3.0 system expands and the XI R2 system decreases, the Operations
Team will take back the XI R2 hardware and use it to increase the XI 3.0
system. The Operations Team also decide to move to the VMware technology
because it allows good flexibility in term of ramping up new images and
decommissioning older images.
17
2 Fundamentals
See the drawing below:
Note:
Side by side also introduces a risk since new software has to be installed
and run on the existing production system. This company does not want to
use it for large and/or business critical systems.
Multiple XI 3.0 system installations
The project upgrade team needed to make sure that the upgrade was
performing well. They proceeded using the following three environments:
• Sandbox/development environment: The BI Team familiarized themselves
with the new concepts in an informal manner before moving on to the
qualification environment.
experience
Fundamentals
• Qualification environment: This allowed the BI team and Business Solution
Owners to make sure the system was working by using and validating
the upgrade before it was moved to the production environment. The
architecture of the qualification environment will be very similar to the
Production environment.
• Production environment: The real-world environment capable of handling
their very large system.
More information about why they set up sandbox, qualification and production
environments is to be found in the topic Actors, roles and responsibilities on
page 10.
The sandbox and qualification environments are not mandatory if you do not
have this kind of policy in your company. But on other hand, it is better to
test and learn on the sandbox and then, validate your deployment in a
qualification environment. Once you are confident, you can apply the same
workflow on production.
19
2 Fundamentals
Upgrading with Import Wizard, CMS database setup

tools, or third-party tools?
The project upgrade team had the choice of different method to accomplish
this upgrade.
• The Import Wizard gives you the ability to select and copy specific objects
from a CMS.
• The CMS database setup tools give you the ability to copy the entire CMS
database contents from one environment to another. This option is
available in the Central Configuration Manager. (CCM)
• You can have the same functionality as in the CMS database setup tools
by backing up and restoring the CMS using third-party database tools
then upgrading the CMS by running the update objects within the CCM.
Option 1 (Import Wizard) is the best option if you want to import only a subset
of the source objects into the XI 3.0 system. This is also the only solution if
you want to accomplish an incremental upgrade.
Option 2 (CMS database setup tools) and Option 3 (Third-party databases)

are the simplest and quickest solution if you want to copy your entire CMS
database contents. You can find more information in the BusinessObjects
Enterprise XI 3.0 Upgrade Guide, page 39 or the BusinessObjects Enterprise
XI 3.0 Administration Guide, page 261.
Each upgrade is different, so depending on your upgrade and needs, you

will choose one of these three options. Therefore, this document does not
tell you which tool you have to use; it only describes why this company used
one tool instead of the other.
Incremental vs. one-shot upgrade
The Project Upgrade Team had a choice between an incremental and a

one-shot upgrade. An incremental upgrade means that certain BI applications
(for instance, Finance, Marketing, Human Resources, Sales) begin to run
on XI 3.0, while some BI applications continue to run on XI R2. The main
disadvantages of an incremental upgrade are that both systems, XI R2 and
XI 3.0, must be maintained and the upgrade process will last longer.
experience
Fundamentals
The Project Upgrade Team preferred to use the Import Wizard for this
upgrade, even though it took more time. The Project Upgrade Team had a
number of constraints that prevented them from upgrading all the BI
applications at the same time to the new system. For these reasons, they
chose an incremental solution with the Import Wizard.
1. The Project Upgrade Team realized it would be difficult to find a common
date that would be acceptable to all BI applications. For instance, if this
upgrade occurred at the end of a quarter, no Sarbanes-Oxley documents
would be generated. On the other hand, some Research and Development
division preferred to upgrade the system during these periods.
2. The Project Upgrade Team wanted to roll out and do training BI application
by BI application to maximize user understanding and usage of the new
system. They did not have the resources to train 6,000 users at the same
time!
3. The Project Upgrade Team had to move from a SQL server CMS to an
Oracle CMS. They had to evaluate the issues that they could face from
moving from one CMS version to another. So, they had to complete an
impact analysis for each BI application. It was easier for the Project
Upgrade Team to validate that the results were indeed what they expected
as they went along, BI application by BI application. It takes less time to
validate results for 1,000 documents from one BI application than 30,000
documents from the entire system.
4. The Project Upgrade Team also wanted to reduce the size of the future
system. The XI R2 environment had too many objects and they wanted
to reduce the quantity of the documents to be upgraded in the XI 3.0
system. (The Project Upgrade Team decided not to upgrade all the
Inboxes' folders.) Instead of upgrading everything (using CMS database
or third party tools) and then cleaning, it was better to accomplish the
cleaning during the import. Each BI application can be cleaned one-by-one
during the upgrade. (obsolete documents and instances, universes, etc.)
5. When you move from an old version to a new version, a gap will develop
during the time you are implementing your upgrade. Data will continue
to be added and changed on your old system, except if you completely
stop your old version or switch it to read-only mode. After you have
finished the upgrade and validation, the new system will need to import
all this data so that the new system is completely up-to-date. If you do
an incremental upgrade BI application by BI application, the gap that
develops between the old system (new information added or changed)
and the new system is smaller and can be managed more easily.
6. Finally, the Project Upgrade Team will have to upgrade multiple BI
applications. They wanted to learn from the upgrade of each BI application
21
2 Fundamentals
to improve later upgrades. They also wanted to show that the upgrade
of the first BI application went well as a model for the subsequent BI
application upgrades.
They built and sized a system that supported the BI applications from the
first upgrade, then enlarged the system as they upgraded more BI
applications. They disallowed a particular BI application on XI R2 and moved
the users to XI 3.0. At the same time, other BI applications on XI R2 continued
to run. See the drawing at Side-by-side vs. completely new installation from
scratch on page 17
experience
General approach of the
BusinessObjects XI 3.0
upgrade project
3
3 General approach of the BusinessObjects XI 3.0 upgrade project
Phase 1: Assessment and Strategy
The Project Upgrade Team decided on an approach dividing the project into
5 phases.
Phase 1: Assessment and Strategy

In this phase the goal was to assess the existing system and make a plan
for the upgrade. The Project Upgrade Team:
• Provided a plan.
• Defined the requirements (with the BI Team, the Operations Team, and
Business Solution Owners).
• Asked the BI Team to analyze and evaluate the system.
• Answered the requirements.
• Proposed a roadmap which needed to be validated by all.
Phase 2: Pre-implementation
At this point, members of the Project Upgrade Team began to install and
use the Sandbox/Development environment. After they understood this
environment, they were able to do a better job of writing the technical
procedures.
The Project Upgrade Team (with the collaboration of BI Team, Operations

Team, and Business Solution Owners) was ready to define the architecture,
the upgrade processes, and to document the technical steps for the upgrade
project. They defined the test strategy to run on the qualification and
production system and the training plan.
The Project Upgrade Team signed off with the approval of the three groups.
Then, they asked the BI Team to clean the XI R2 system.
At the end of these tasks, they conducted a go/no go meeting; it was decided
to continue with the project.
experience
General approach of the BusinessObjects XI 3.0 upgrade project
Phase 3: Qualification environment installation and upgrade 3
Phase 3: Qualification environment
installation and upgrade
In this phase, the BI Team ordered the materials as defined earlier. They
also finalized the upgrade wizard strategy, installed the qualification system,
configured the third-party products, such as Active Directory, and performed
the Import Wizard upgrade. Afterwards, the BI Team validated the qualification
upgrade.
While doing this, the BI Team produced a document so that the Operations
Team could later install the production upgrade following it. The BI Team
organized the testing on the qualification system (functional, UAT, and
benchmark testing).
At the end of this phase, a go/no go meeting was held where it was decided
to continue with the project to the next phase.
Phase 4: Production environment

installation
In this phase, the Operations Team followed the documentation made by
the BI Team during the qualification phase. The Operations Team installed
the system and configured the production system.
Then, the BI Team configured the components linked to the BusinessObjects

BI applications.
At the end of this phase, a go/no go meeting was held where it was decided
to continue to the final phase of the project.
Phase 5: Production environment upgrade

and Roll out
The upgrade to XI 3.0 only affected a few BI applications at first. The users
affected by the changed environment were trained on the new system a few
weeks before this. Also, frequent communication was taken with these users
to keep them abreast of what was happening.
25
3 General approach of the BusinessObjects XI 3.0 upgrade project
Phase 5: Production environment upgrade and Roll out
Hereafter, the BI Team used the Import Wizard to upgrade the production
environment.
Then, the BI Team and Business Solution Owners validated the Production
upgrade.
Finally, the Operations Team performed a back-up of the new XI 3.0 system.
In the future, more BI applications will be rolled out one at a time following
this procedure.
experience
Assessment and strategy
4
4 Assessment and strategy
Step 1: Define the overall plan
Table 4-1: Assessement Actors and Roles
Actor Roles
Define the plan and requirements; an-

swer the requirements; provide the final
roadmap in collaboration with the BI
Project Upgrade Team
Team, Operations Team and Business
Solution Owners; and conducted a go
/ no go meeting.
BI Team Analyze the system.
BI Team, Business Solution Owners Need to commit time and resources to

and Operations Team the project.
The first action of the project upgrade team was to build an overview plan
and define the process and criteria to move from one phase to another. This
plan described the main phases of the future upgrade, but only Phase 1
Assessment and Strategy was planned in detail with exact dates. The others
phases were not defined at this stage in detail.
After all the Phase 1 steps had been completed, the Project Upgrade Team
will present the complete roadmap and they will ask for the commitment of
all teams impacted by this project. Then, the upgrade project will start
officially.
Plan
The upgrade team planned the overall schedule, showing the various steps
they would take.
Remember that the time you take to implement your upgrade depends on a
number of factors:
• Size and complexity of your system
• Number of resources to be impacted
experience
Step 1: Define the overall plan 4
• Your knowledge of BusinessObjects technology
Project Name /ID XI 3.0 Live
Deploy BusinessObjects XI 3.0 and use

Project Goal the new features; (new CMC, InfoView
and Web Intelligence Rich Client.)
Phase 1: Assessment and Team

Strategy
Phase 2: Pre-implementation
Phase 3: Qualification environment in- Will be known later (during Step 5: Fi-
stallation and upgrade nalize the roadmap and hold go / go
no meeting on page 37
Phase 4: Production environment instal-
lation
Phase 5: Production environment up-

grade and roll-out
Go/No Go meetings
For each step, the Project Upgrade Team discussed with all the teams
impacted and gave a go/no go for the next step.
Each team had to provide its feedback on the steps of each phase and decide
to move or not to the next phase. In all cases, they had to provide a document
that explained how they would manage the potential risks.
Please see the go/no go decision template below:
29
Each team needs to give their status and commit for the next step: Go or
Conditional Go or No Go
Table 4-3: Go / No Go Table
Team Go / Conditional Go / No Go
Team Name
or
At this time, each team also has to provide any pertinent risk information for
the next stage.
Please find below the Risk template.
Table 4-4: Risk Template
Descrip Probabili Response

Owner Impact Risk response
tion ty Plan
of the Team
% hi/med/low if any if any
task Name
For the qualification upgrade, they used the following template to provide
the feedback on the upgrade and decide if they moved on or not to the
production phase. This presented more details, which they found useful.
experience
Step 2: Define the requirements 4
Topics What was Status
done
Installability
Functionality
Usability
Reliability
Security or
Scalability
Performance Deployability
Regular Communication among Project Upgrade

Team members
In order to follow the project and fix all issues quickly the Project Upgrade
Team defined the following communication plan:
• Semi-weekly calls between the BI Team and the Operations Team to
review and prioritize problems
• Semi-weekly calls between the BI Team and the Business Solution
Owners
• Weekly calls between the Business Solution Owners and the Business
Users
• Weekly calls among the members of the Project Upgrade Team
Step 2: Define the requirements

The Project Upgrade Team defined the following requirements for this
upgrade with the BI Team, Operations Team, and Business Solution Owners:
Requirement Requirement
Number
31
Step 2: Define the requirements
Number
1 The system can be upgraded as an installation from scratch
as described in Side-by-side vs. completely new installation
from scratch on page 17
2 The system can be upgraded incrementally BI application by
BI application as described in Incremental vs. one-shot upgrade
on page 20
3 The system can be set up and used in three environments:
sandbox, qualification, and production as described in Multiple
XI 3.0 system installations on page 18
4 The system can validate the new XI 3.0 functional areas wanted
by users. (See Reasons to upgrade on page 15.)
5 The system can validate the deployment, security and authen-
tication models. The current XI R2 BusinessObjects security
model and the AD authentication needs to be upgraded with
few modifications.
6 The system can validate the new CMS DB version. The system
was running on SQL Server 2000 SP3. The Operations Team
wanted to move to an Oracle 10G CMS database because this
is the new standard for the company.
7 The system can validate the OS platform. The Operations Team
wanted to move all the computers on VMware. The new stan-
dard of this company is to reduce the number of computers
and use virtualization VMware ESX (Enterprise release).
8 The system can validate the clustering and failover for high
availability (used by people around the world and the system
needed to be available 24 hours x 7 days. )
9 The system can validate the WebServer version. The Opera-
tions Team wanted to evaluate new application servers, like
WebSphere or WebLogic.
experience
Step 3: Analyze and understand the system 4
Number
10 The BI applications upgraded first were the less critical BI ap-
plications. They were chosen in order to minimize risks.
11 The BI applications upgraded first needed to have enough
concurrent users to evaluate the stability (the target was be-
tween 10 and 25% of the users upgraded.)
12 The BI applications upgraded first need to belong to a depart-
ment that has the most comprehensive knowledge of Busines-
sObjects products.
Step 3: Analyze and understand the

system
In order to answer the requirement, the Project Upgrade team, needed to
know the system. So, the Project Upgrade Team asked the BI Team to
conduct an audit of the current XI R2 system.
This step is mandatory and extremely important, which is why we dedicated

a topic to this subject. The BI team knew the different BI applications on the
system because they regularly collected business information to understand
them.
The easy way to collect the information was to meet the Business Solution
Owners and also to create BusinessObjects documents based on the audit
system. Without these documents they will not understand who is doing
what, so they will not understand what to do on their system.
The BI Team collected technical details (number of documents, users,

activities etc.) to evaluate the workload and risks for this upgrade. They were
able to understand the criticality of all BI applications and established which
BI applications can be used for this project.
By meeting with the Business Solution Owners of the company, the BI Team
could also identify in terms of business, which BI applications were more
important than others. For example, Marketing is less critical than HR
management which is less critical than quarter closing which is less critical
than sales booking and processing, etc.
33
Step 3: Analyze and understand the system
A document was generated for each BI application. All the Business Solution
Owners were able to open and refresh this type of document for their own
BI applications, so they can monitor the BI application that they are in charge
of. A typical document looks like the following:
The following list shows what was verified for the all the systems and for all
the BI applications.
Deliver documents that show:

• the folder hierarchy
• all folders including their definition
• all groups within the system
experience
Step 4: Answer the requirements 4
• number of users
• top users using the system
• number of concurrent users
• for each user show (through a user dashboard) his last instances
calculated for him (+current month with failed instances)
• for each user show (through a user dashboard) his favorite documents
(top 10 open documents)
• number of documents
• all documents by BI application: the documents within each folder with
number of instances + number of viewed action per documents
• top documents open
• time to refresh documents
• top documents that take the most time to be refreshed
• number of instances per document
• number of universes
• top universes used
• number of documents in My Favorites folder.
• number of scheduled documents
• etc.
Step 4: Answer the requirements

Following the definition of the requirements and after discussions among the
BI Team, Operations Team, Business Solution Owners and users, the
answers below were agreed on:
• Requirement 1: All software will be installed from scratch on new Operating
Systems.
• Requirement 2: The upgrade will be done incrementally BI
application-by-BI application.
• Requirement 3: The Project Upgrade Team chose to install and use three
environments: sandbox, qualification, and production.
• Requirement 4: The Project Upgrade Team validated that the new XI 3.0
functional area met their needs: the new CMC, InfoView and the Web
Intelligence Rich Client.
• Requirement 5: The Project Upgrade Team wanted to keep the same
capabilities as offered by the current XI R2 security model. After doing
some tests on the sandbox, they felt confident that the upgrade would
35
Step 4: Answer the requirements
not break this security model. The AD authentication was also set up, as
they had more than 6,000 users in the CMS.
• Requirement 6: The Project Upgrade Team decided for this first upgrade
to use an Oracle 10G CMS. They provided the following information: type,
size, and number of concurrent access requests. See Step 13: Ask for
the qualification platform on page 58
• Requirement 7: The Project Upgrade Team decided to use VMware ESX
for the OS platform.
• Requirement 8: The Project Upgrade Team made sure that the system
can validate the clustering for all processes and failover for high
availability. These criteria defined by the Project Upgrade Team were:
Application Uptime as % Un-scheduled downtime Environment

(hours)
XI 3.0 More than 99.5 Less than 50 (per year) Production
In this case, they had to cluster all the architecture in order to have one
system running all the time. So, the CMS database, the CMS, all the
processes and the application server will be duplicated.
We will describe the architecture in the topic Step 7: Define the

architecture on page 46
• Requirement 9: The Project Upgrade Team decided not to upgrade the
application server. They decided to stay on Tomcat as it was already on
the existing XI R2 configuration.
• Requirement 10: The Project Upgrade Team looked at a number of BI
applications and chose a less critical BI application to be the first
application upgraded.
• Requirements 11 and 12: Based on their knowledge and using the audit
system, the Project Upgrade Team knew how many users, documents,
refreshes, activities, etc. each BI application was using. They selected a
department where the users had the best knowledge of the
BusinessObjects products and the users were numerous enough to test
for stability.
Based on these requirements, the Project Upgrade Team chose among the
various BI applications, the first three BI applications to upgrade. The BI
applications chosen for the first stages are the less business critical. However,
they have more power users. So, in the workflows of these specific BI
applications, more documents are created than refreshed than in the typical
BI applcation.
experience
Step 5: Finalize the roadmap and hold go / go no meeting 4
Step 5: Finalize the roadmap and hold go
/ go no meeting
In this company, after the Project Upgrade Team had collected enough
information to answer the requirements and understand the XI R2 system,
they proposed the following roadmap:
Note:
The duration of an upgrade depends on the size and complexity of your
current system and also varies depending on which particular upgrade
strategy you will choose and the way you work. It is difficult to answer how
long an upgrade might take; all we can say is anywhere from a couple of
weeks to several months.
The table below shows the different steps and their owners:
37
Step 5: Finalize the roadmap and hold go / go no meeting
Owner
Initiation of the project BI Team
Phase 1
See Step 1: Define the Project Upgrade Team
overall plan on page 28
See Step 2: Define the re- Project Upgrade Team with BI Team, Operations
quirements on page 31 team and Business Solution Owners
See Step 3: Analyze and BI Team with Business Solution Owners
understand the system on
page 33
See Step 4: Answer the BI Team, Operations team and Business Solution
requirements on page 35 Owners
Step 5: Finalize a final Project Upgrade Team with BI Team, Operations
road map. (This topic) Team and Business Solution Owners.
Phase 2
See Step 6: Ask for, set up BI Team and Operations Team
and use the sandbox on
page 42
SeeStep 7: Define the ar- Project Upgrade Team, BI Team and Operations
chitecture on page 46 Team
See Step 8: Define the Project Upgrade Team and BI Team
main upgrade strategy on
page 51
See Step 9: Define the test Project Upgrade Team with BI Team and Business
plan strategy on page 52 Solution Owners
See Step 10: Define the Project Upgrade Team, BI Team, and Business
training plan on page 53 Solution Owners
See Step 11: Clean the BI Team and Business Solution Owners
current environment on
page 54
See Step 12: Conduct a Project Upgrade Team with BI Team, Operations
go/no go meeting to start team and Business Solution Owners
the test implementation on
page 55
experience
Step 5: Finalize the roadmap and hold go / go no meeting 4
Owner
Phase 3
See Step 13: Ask for the BI Team and Operations Team
qualification platform on
page 58
See Step 14: Finalize the BI Team and Business Solution Owners
upgrade wizard strategy
on page 58
See Step 15: Install in a BI Team
qualification environment
on page 60
See Step 16: Upgrade the BI Team
qualification system on
page 83
See Step 17: Test the BI Team and Business Solution Owners
qualification system on
page 100
the production environ-
ment installation on
page 110
Phase 4
See Step 19: Ask for the BI Team and Operations Team
production platform on
page 114
See Step 20: Install in a Operations Team
production environment
on page 115
the production environ-
ment upgrade on page 115
Phase 5
See Step 22: Plan the roll- Project Upgrade Team with the BI Team
back strategy on page 118
39
Step 5: Finalize the roadmap and hold go / go no meeting
Owner
See Step 23: Communica- Project Upgrade Team with the BI Team
tion, user training and cut-
over preparation on
page 118
See Step 24: Upgrade the BI Team
production system on
page 119
See Step 25: Perform the BI Team and Business Solution Owners
last validation on page 120
go/no go meeting to roll- team and Business Solution Owners
out the production imple-
mentation on page 121
See Step 27: Upgrade the BI Team and Business Solution Owners
desktop client on page 122
See Step 28: Roll out on Project Upgrade Team with BI Team, Operations
page 122 team and Business Solution Owners
A go / no go meeting was held and all teams committed to the next Phase:
Pre-implementation.
experience
Pre-implementation
5
5 Pre-implementation
Step 6: Ask for, set up and use the sandbox
Table 5-1: Pre-implementation Actors and Roles
Actor Roles
Defined the strategy and the upgrade

Project Upgrade Team process and conducted the go/ no go
meeting.
Defined the architecture, the upgrade

steps, the test plan, and the training
BI Team plan with the Project Upgrade Team
and the Business Solution Owners.
They also cleaned the XI R2 system.

Step 6: Ask for, set up and use the

sandbox
This was a very informal process performed by the members of the Project
Upgrade Team individually. Of course, they tended to concentrate on their
own area of expertise. They all had to install, configure, and use the Import
Wizard.
Order the materials
The BI Team ordered the materials. As they had already defined and
answered the requirements (Step 2: Define the requirements on page 31
and Step 4: Answer the requirements on page 35 of this document) it was
easy to order the materials. The budget was planned during the assessment
phase and the BI Team created a request to the Operations Team who
delivered the material quickly. You will find the characteristics of the OS and
Database systems in the topics below.
experience
Pre-implementation
Step 6: Ask for, set up and use the sandbox 5
VMware OS
The BI team asked for three environments (sandbox, qualification and

production) on VMware images. The BI Team asked for the following (all the
OSs were Windows 2003 SP2):
For the sandbox:

• 2 computers with 1 CPU each and 2 GB of RAM and 60 GB of disk space.
For the qualification environment:

• The first system will have 2 computers with 4 CPUs each and 4 GB of
RAM and 60 GB of disk space. When they expand the system, they will
add computers with 2 CPU and 2 GB of RAM and 60 GB of disk space.
For the production environment:
• The first system will have 2 computers with 4 CPUs each and 4 GB of
RAM and 60 GB of disk space. When they expand the system, they will
add computers with 2 CPU and 2 GB of RAM and 60 GB of disk space.
We do not describe the CPU speed or the network speed as this is not the
purpose of this document.
The BI Team preferred to increase the size of the cluster by adding another
computer to using a more powerful computer with more CPU and RAM as
described in the topic Expandable architecture on page 50.
Database accounts
The BI Team ordered two accounts on Oracle for each environment. The
database account characteristics are shown in the table below:
Database Name XI 3.0

Database Version Oracle 10.2.0.3 64-bits
Schema Owner(s)
CMS_X and AUDIT_X
One tablespace dedicated for each ac-

count owner and read/write access + table
creation
43
Step 6: Ask for, set up and use the sandbox
Estimated number of concurrent 1 generic user for each account

application users
Estimated number of concurrent 10 for each account
database connections
Estimated initial CMS DB Size on 300 Mo - Max 1 Go (total size)
disk
Estimated initial Audit DB Size on 1 GB - Max 100Go (total size) (for qualifica-
disk tion and production)
Usage Repository and audit data
Demanding times Current usage
Does the database explicitly re- Yes for qualification and production; No for
quire on-site redundancy (cluster- sandbox
ing)?
What is the acceptable data loss 1 day for qualification and production; N/A
time? for sandbox
How long can the database be 5 hours for qualification and production; N/A
shutdown during the weekend for for sandbox
backup?
Is it required to restore objects No
only (versus the entire DB)?
Other comments To increase the performance, the CMS
database, the audit database, and the
BusinessObjects systems need to be as
close as possible. If the documenting
database are also very close, you will im-
prove the performance.
Check the hardware and accounts
The BI Team checked the hardware and accounts provided by the Operations
Team.
The Operations Team copied the BusinessObjects XI 3.0 files from a DVD
to a shared folder on the network, visible from the computers where it will
be installed. For the sandbox and qualification environment, the BI Team
experience
Pre-implementation
Step 6: Ask for, set up and use the sandbox 5
logged on to the VM computer with a network account to validate that they
can access the XI 3.0 shared folder, the Storage Area Network (SAN), the
database data and future CMS and audit accounts. They wanted to validate
than the Oracle connectivity was installed correctly. They used SQL plus
tools to test that the Oracle accounts were accessible.
The BI Team did not do any tests or benches on the empty platform.
For the production environment, BI teams did not have access to these
environments (as we explained in Actors, roles and responsibilities on
page 10). So, the BI team asked the Operations Team to execute this
validation.
Back up and restore the solution
The backup and restore solution was defined by the Project Upgrade Team.
In case of problems, to be able to restore the system, they asked for the
following:
• a snapshot of the BusinessObjects cluster
• CMS and audit database backups
• FRS backups
VMware snap- A weekly snapshot or a on-demand snapshot to be able to roll-

shot back on a stable configuration. (This needs to be done at the
same time as the FRS backup and the CMS / Audit databases
backup.)
45
Step 7: Define the architecture
CMS/Audit A weekly backup or a on-demand backup to be able to roll-

databases back on a stable configuration. (This needs to be done at the
backup same time as the snapshot and FRS backup.)
FRS backup A weekly backup or a on-demand backup to be able to roll-
back on a stable configuration. (This needs to be done at the
same time as the snapshot and CMS / Audit databases back-
up.)

The Project Upgrade Team knew at this point which BI application would be
upgraded first. With the help of a BusinessObjects consultant, they had to
define the architecture and estimated the theoretical system load. The general
idea was to have an high availability.and expandable platform. A cluster of
two computers will be enough to answer these needs.
The BI Team will upgrade the three BI applications using a platform sufficient
to handle them. Then, thanks to the flexibility of BusinessObjects platform,
more servers can be added to the mix as it is decided to ramp up additional
BI applications on XI 3.0. (See Expandable architecture on page 50.)
Of course, each time the Project Upgrade Team modifies the architecture,
they will validate that the system can handle the load using benchmark tests.
These benchmark tests will be done on the qualification environment. See
Benchmark testing on page 110
XI 3.0 architecture
As we explained above (Step 7: Define the architecture on page 46), the

Project Upgrade Team decided to set up an cluster of two computers in order
to answer Requirement 8, which was to have high availability, so that the
system could be used world-wide 24 hours x 7 days.
The following components must be continuously running, and therefore

clustered:
• The CMS database referencing XI 3.0. If the database is not available,
the CMS stops.
experience
Pre-implementation
Step 7: Define the architecture 5
• The CMS server. If no CMS is available, none of the BusinessObjects XI
3.0 components are able to function (including the Desktop products.)
• The J2EE Application server is indispensable for the InfoView portal, the
administration console, and the 3-level mode (Rich Client ZABO).
• The FRS servers. Their mode of active/passive functioning guarantees
that only one component has access to the SAN at a time. If there is no
Input FRS or no Output FRS, a user cannot access the documents, nor
visualize them, nor modify them. The Desktop products cannot import or
export the documents, and cannot access the universes.
Below is a representation of the platform:
They also decided to use the following services:
47
Services \ Computers Computer 1 Computer 2

Tomcat Enabled / Started Enabled / Started
SIA Enabled / Started Enabled / Started
DashboardAnalyticsServer Stopped / Disabled Stopped / Disabled
DashboardServer Stopped / Disabled Stopped / Disabled
PMMetricsServer Stopped / Disabled Stopped / Disabled
PMRepositoryServer Stopped / Disabled Stopped / Disabled
PMRulesServer Stopped / Disabled Stopped / Disabled
PredictiveAnalysisServer Stopped / Disabled Stopped / Disabled
ProcessAnalysisServer Stopped / Disabled Stopped / Disabled
SetsProfileServer Stopped / Disabled Stopped / Disabled
SetsQueryServer Stopped / Disabled Stopped / Disabled
AdaptiveJobServer Enabled / Started Enabled / Started
AdaptiveProcessingServer Enabled / Started Enabled / Started
CentralManagementServer Enabled / Started Enabled / Started
DestinationJobServer Enabled / Started Enabled / Started
EventServer Enabled / Started Enabled / Started
InputFileRepository Enabled / Started Enabled / Stopped
OutputFileRepository Enabled / Started Enabled / Stopped
ProgramJobServer Enabled / Started Enabled / Started
PublicationJobServer Enabled / Started Enabled / Started
CrystalReportsCacheServer Enabled / Started Enabled / Started
CrystalReportsJobServer Enabled / Started Enabled / Started
CrystalReportsProcessingServer Enabled / Started Enabled / Started
ListOfValuesJobServer Enabled / Started Enabled / Started
ReportApplicationServer Enabled / Started Enabled / Started
ConnectionServer Enabled / Started Enabled / Started
DesktopIntelligenceCacheServer Stopped / Disabled Enabled / Started
experience
Pre-implementation
Step 7: Define the architecture 5
Services \ Computers Computer 1 Computer 2
DesktopIntelligenceJobServer Stopped / Disabled Enabled / Started
DesktopIntelligenceProcessingServ- Stopped / Disabled Enabled / Started
er
WebIntelligenceProcessingServer Enabled / Started Enabled / Started
MultiDimensionalAnalysisService- Stopped / Disabled Stopped / Disabled
Server
Explanation of shared services
Note:
Each deployment is different, so you will have to adapt what the Project
Upgrade Team did to your system. The failover and performance features
do not necessarily cohabit well. Sometimes you have to choose which is
more important. Please find below an explanation of the architecture services
and remember that the company's main goal was the failover feature.
• The BI Team disabled and stopped the PMC services, because they did
not plan to use these servers in their system.
• BI Team disabled and stopped the MultiDimensionalAnalysisService
server for the same reason.
• The main server for the functioning of BusinessObjects XI 3.0 that should
be duplicated is the CMS.
• The CMS is essential if you want to log into the system. Therefore, it
will handle the load balancing (round-robin) and the failover.
• The FRS servers (Input / Output): FRS are also very important because
without FRS, Crystal Reports, Desktop Intelligence and Web
Intelligence documents cannot be viewed/scheduled/published. Their
mode of Active/Passive functioning guarantees that only one server
has access to the SAN at a time. The first computer that starts will
have the FRS servers active and the second the FRS servers passive.
• To share the load of the shared processes, they proposed to activate on
the two servers the core servers AdaptiveProcessingServer,
DestinationJobServer, ProgramJobServer, PublicationJobServer. The
Load Balancing algorithm of XI 3.0 will share the load between the two
servers in order to have a failover system.
49
The BI Team also duplicated the Event Servers. However, be careful

because the duplication imposes that the two Event Servers point to the
same repository File Watcher, so that they correctly manage the events
based on the files.
• The BI Team enabled the Desktop Intelligence server only on
COMPUTER02 (because in this deployment, most of the Desktop
Intelligence users accessed directly the documenting database from their
desktop and did not use InfoView). Of course, if the computer which owns
the Desktop Intelligence component fails, they will immediately start a
Desktop Intelligence process on the other computer.
• The BI Team enabled the Web Intelligence and Crystal servers on both
computers as they thought that they would have more users accessing
these two BI applications.
InfoView XI 3.0 (but not CMC) supports clustered application servers. In this
company, it is best practice to have a hardware load balancer in front of the
application servers cluster and it is recommended to ensure that the
application servers cluster works with sticky session (all subsequent requests
are forwarded to the same application server) and that the session is not
serializaed (for best performance).
Note:
In order to improve performance:
• Have the CMS database close to the CMS server.
• Have the JOB server and processing server close to the documenting
databases.
Expandable architecture
The platform should be expandable. The BI Team started with a cluster of

two computers for the first upgrade of BI applications. Afterwards, they ran
benchmarking tests to define exactly how many computers they needed to
add for the second upgrade of BI applications. This process was repeated
as each new upgrade of BI applications was added.
They added only processing server computers (such as Web Intelligence or

Crystal) and Tomcat servers. They put the cache server on the same server
as the application server to increase performance. We did not explain this
part in detail because, when we are writing this document, this part was not
experience
Pre-implementation
Step 8: Define the main upgrade strategy 5
yet started. For more information on adding servers and server clusters, see
the BusinessObjects Enterprise Server Administration Guide.
Another advantage of expandable architecture was that the Project Upgrade

Team thought ahead to new products such as Life Cycle Management (LCM)
which would be released later. They were very interested in this product and
its functions; they often asked about its anticipated release date. They
understood that in order to support LCM, they would have to add more system
resources in the future.
Step 8: Define the main upgrade strategy

As we explained in the topic Incremental vs. one-shot upgrade on page 20,
the Project Upgrade Team decided to perform an incremental upgrade .
51
Step 9: Define the test plan strategy
1. The Project Upgrade Team decided to upgrade only one part of the
environment at a time. The upgrade was accomplished in multiple steps
BI application by BI application.
2. The BI Team cleaned the security model before starting the upgrade and
as they moved from XI R2 to XI 3.0, the Project Upgrade Team decided
to upgrade the security.
They did not want spent time creating a new security system. There were
few risks as the upgrade process will transform the XI R2 model into a
XI 3.0 model and will not break their security model.
3. The BI Team, in consultation with the Business Solution Owners, decided

to select or not to select the Favorites documents. By default Inbox
document were not upgraded. If the users wanted to keep some Inbox
documents, they had to save them in the Favorites folders
Favorites documents were very important as the users of the BI

applications first upgraded primarily use these documents. For BI
applications that will be upgraded later, the BI Team will have to discuss
this with the Business Solution Owners. It is a part of the agreement with
each line of business.
Note:
Importing Favorites folders can create problems. If the users have documents
in the Favorites folder, they also have the universes and the connections
associated with these documents in order to refresh them. You may want to
import the users, the Favorite documents and also some corporate documents
and universes, but not necessarily the universes and connections linked to
the documents which are in the Favorites folders. If your users belong to
multiple departments (A, B, and C) and have access to multiple universes
of these departments and if you select your user thinking he belongs to
Department A, and if you import the Favorites documents, you will also import
universes and connections for Departments B and C. So, you will have to
check and clean the universes and connection once the Import Wizard has
finished.
Step 9: Define the test plan strategy

The project upgrade team defined the test plan strategy.
experience
Pre-implementation
Step 10: Define the training plan 5
Because the BI Team knew quite well the XI R2 system and as they learned
the XI 3.0 system when they installed and tested the sandbox, they were in
charge of creating the test plans.
The BI team developed three kinds of test plans.

1. One type linked to the workflows done essentially by BI team
• The Platform administration
• The CMC administration
• The universe designer
• The main InfoView, Web Intelligence, Crystal and Desktop Intelligence
functionality
2. The second type was linked to the Business BI applications workflows.
They asked the Business Solution Owner to define with the users
• The workflows used every day by the users.
• The workflows using the 10 % of the most important documents
identified by the BI team (during the audit). 10 % seems will give a
good idea of the upgrade. They called these tests: UAT (User
acceptance tests).
3. The third type was the Benchmark testing. The BI Team identified specific
workflows.
They decided to implement 4 scripts to evaluate the stability, to see if the
system was correctly sized, and define the number of users who would
crash the system.
Step 10: Define the training plan

The Project Upgrade Team defined the training strategy.
Since the Project Upgrade Team chose an incremental upgrade, some BI

applications moved to XI 3.0 while others BI applications stayed on XI R2.
This training plan will be communicated BI application by BI application. The
BI applications which moved to XI 3.0 were concerned, the BI applications
which stayed for the moment on XI R2 were not impacted.
The training plan had three parts. Of course, this training was only available
to the users impacted by the upgrade:
1. General communication: Set up a standard document explaining the
added value of the product and the technical reasons for the upgrade.
(The Project Upgrade Team will present the new functionalities.) This
53
Step 11: Clean the current environment
communication will be available one and a half months before the

production start.
2. On-site training for Business Solution Owners. This training will start one
month before the production start.
3. Mandatory e-learning training for the users upgrading to Rich Client. This
training will start one month before the production start.
Step 11: Clean the current environment

The Project Upgrade Team asked the BI Team to clean the XI R2 production
platform. This goal was to reduce the complexity of folders hierarchy, highlight
unused documents, provide a clear access to main documents and maintain
security within groups and users.
The impact will be to improve performance on CMS (queries), reduce FRS

size, reduce failed instances, and facilitate the upgrade.
As we described in the topic Step 3: Analyze and understand the system

on page 33, the BI Team uses many auditor documents to understand,
identify and validate the correct behavior of each BI application and of each
environment.
To accomplish their goal, they defined the following tasks:

• Review appropriate folder structure to store documents (like Windows).
• Simplify the folder structure (Example: a default user has access to 200
folders with 50% empty ones).
• Apply a naming convention on folder/document/group and generalize
description on objects.
• Set access rights on those folders.
• Identify security holes on strategic BI applications.
• Identify breaking inheritance.
• Identify single users with setting security and try to use only groups
security.
• Review universes access.
• Develop and reinforce delegated administration and Power Users strategy.
• Decommission old projects.
• Identify and remove all deprecated users. For example, they had to clean
178 users who had left the company and remove 2,540 enterprise
accounts that came from a previous merge.
experience
Pre-implementation
Step 12: Conduct a go/no go meeting to start the test implementation 5
• Identify and remove old folders and documents (not used in the last 3
months). This will improve navigation.
• Identify and remove old universes (not used in the last 3 months).
• Remove failed instances (date < previous month) and identify recursive
schedules with high level of failure.
• Reduce the number of instances per document. The Favorites folder limit
was too high and the BI Team wanted to reduce it. (Target: 50 per
document) For example, they found that: 20 Favorites folders represent
20% of the total documents. 20 Favorites folders represent 50% of the
total instances. In order to reduce the number of instance, a mail like the
following was sent:
If you receive this email, it means that you are in one of

these top
lists. We encourage you to look at your Favorites on “One-
click InfoView",
delete old documents and instances or publish these docu
ments in public Folders (to
do that, please contact your BI solution owner). It will
reduce repository size
(database and disk space) and improve response time in the
navigation for all
employees. In the next 2 weeks, we will be doing the same
analysis to
control. We also apply a new restriction to limit the
number of instances per
documents.
This cleaning was very helpful; the Business Solution Owners of each BI
application were interested and participated actively. It took one month to
do it, because the BI Team had to identify problems, do some cleaning, and
meet the Business Solution Owners , who had to do their own personal
cleaning. The BI Team had to analyze the system one more time and then
meet the Business Solution Owners who had not yet finished the cleaning.
They did this on a regular basis.
Step 12: Conduct a go/no go meeting to

start the test implementation
All the teams signed off on the project.
The main questions to answer were:

• Are you OK with the upgrade strategy?
55
Step 12: Conduct a go/no go meeting to start the test implementation
• Are you OK with the test plan strategy?

• Are you OK with the training strategy?
• Do you have all the information from the Business Solution Owners ? (All
steps of the Import Wizard) From the Operations Team? (requirements
for the platform)
• Do your resources meet the schedule?
• Do you have the material resources?
• What are the risks? Are you prepared to deal with them?
Table 5-2: Go / No Go Meeting Results
Delivery Teams Go / No Go
BI Team Conditional Go
Operations Team Conditional Go
Business Solution Owner Application

Go
1

Go
2

Go
3
The following risks were identified:
Description Owner Proba- Impact Risk re- Response plan

bility sponse
Other projects BI Team Medium Major Mitiga- Add more resources
can impact the andOper- tion or postpone conflict-
current planning ations plan ing projects.
Team
The Project Upgrade Team decided to continue and move to the next step.
experience
Qualification environment
installation and upgrade
6
6 Qualification environment installation and upgrade
Step 13: Ask for the qualification platform
Table 6-1: Qualification Actors and Roles
Actor Roles
Project Upgrade Team Conduct the go / no go meeting .
Ask for the materials; installed and

configure the qualification environment;
BI Team
upgrade the system; and tested the
environment.
Provide the materials and backup re-

Operations Team
sources.
Business Solution Owners Perform User Acceptance Testing.

We explained in the topic Multiple XI 3.0 system installations on page 18

why they started by setting up a qualification platform.
Step 13: Ask for the qualification

platform
The BI Team made the same requests as for the sandbox/development
environment. Please see Order the materials on page 42 for more
information.
Of course, they used different computers, different databases (CMS and

audit) and different FRS (SAN) than for the sandbox environment.
Step 14: Finalize the upgrade wizard

strategy
As we explained before, the BI Team will upgrade one part of the full XI R2
environment. They selected three BI applications to be part of this upgrade.
experience
Qualification environment installation and upgrade
Step 14: Finalize the upgrade wizard strategy 6
Therefore, they will use the Import Wizard to upgrade these three BI
applications. But in reality, this part of the upgrade is the most complex, there
are many screens in the Import Wizard and they need to know exactly what
to select on each Import Wizard screen.
Of course, they defined the general strategy. (See Step 8: Define the main
upgrade strategy on page 51), but now they have to define the exact contents.
For each BIapplication to be upgraded, the BI Team asked the Business

Solution Owner in charge of the BI application the following questions:
What is to be upgraded? Yes /No

Which users and groups?
Favorites folders?
Do they really need to import Favorites folders?
Which document folders and documents?
Which universe folders and universes?
Do they really need to import discussions?
Do they really need to import the encyclopedia?
Is it acceptable to have downtime on the system in order to
upgrade? If yes, how long?
Is it acceptable to have access to the XI R2 system in read-
only mode (no schedule, save …)? and if yes, for how long?
Once the BI Team got the answer, they met the each Business Solution
Owner to commit on the contents. (See Step 12: Conduct a go/no go meeting
to start the test implementation on page 55)
So, the BI Team could execute the upgrade of the three BI applications. They
will do it first on a sandbox environment (to test the workflow) and later on
the qualification environment (to validate the workflow and write the
procedure), and, finally, on a production environment.
59
Step 15: Install in a qualification environment
Step 15: Install in a qualification

environment
At the same time that they installed the product in the qualification
environment, the BI Team wrote an comprehensive document. This document
will be used by the Operations Team to install the product in the production
environment. The BI Team did the installation using a network account. The
network account is a member of the administrator group and has
administrative privileges on the local machine. See BusinessObjects
Enterprise XI 3.0 Installation and Configuration Guide for Windows page 18.
As the BI Team defined in its requirements, a Windows Server 2003 SP2

Enterprise Edition has to be installed and running. The BI team validated the
correct behavior of the computer in as described in Check the hardware and
accounts on page 44. They needed administrative privileges on both
machines that would host the BusinessObjects Enterprise servers. (Otherwise,
the BusinessObjects servers would not start.)
They designated one machine COMPUTER01 and the other COMPUTER02

and the storage place for the FRS as SAN01.
Install the BusinessObjects Enterprise Servers

cluster1
The BI team will provide the documentation to the Operations Team to install
XI 3.0 on COMPUTER01.
1. They ran setup.exe from a network shared folder where the DVD
BusinessObjects XI 3.0 software was copied.
The "Please Choose Setup Language" dialog was displayed.
2. They selected English for the installation setup from the pull-down list
provided and clicked OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" was displayed.
3. They clicked Next.
The "License Agreement" screen was displayed.
4. They selected "I accept the License Agreement" and clicked Next.
experience
Step 15: Install in a qualification environment 6
The "User Information" screen was displayed.
5. They entered the requested information for Full Name, Organization, and
Product Keycode. They clicked Next.
The "Choose Language Packs" screen was displayed.
6. They installed everything in English as English is the official company
language. They clicked Next.
The "Install Type" screen was displayed. They were going to install the
first cluster, so they had to select New.
7. They selected New and Use an existing database server in the "Install
Type" screen.
They wanted to install all services in order to test the desktop tools (like
Import Wizard and Rich Client.) Then, they were able to validate the
connection properties and Web Intelligence documents on this server,
as well as use the Import Wizard.
They did not install MySQL on this computer because they were going
to use an existing Oracle database.
They did not enable the servers, as they will configure differently on the
cluster.
They wanted to install on the D drive, because this is the company policy.
They did not change the rest of the path.
61
They clicked Next. The "Server Components Configuration" screen was

displayed.
8. They entered the password in both Password and Confirm password.

They wanted to use a password as this is the company policy.
In order to recognize quickly the server, they called the first server Cluster1
and the second Cluster2. They used the default CMS port 6400 as they
will have only one CMS on COMPUTER01, so they will not encounter
any port number issues.
experience
They clicked Next. The "Server Intelligence Agent "screen was displayed.
9. They entered Cluster1 in Node Name. They used the default SIA port
6410 as they will have only one SIA on the COMPUTER01 , so they will
not encounter any port number issues.
63
Then, they clicked Next. The "CMS Database Information" screen was
displayed.
10. They verified that they could access the two Oracle accounts with SQL
plus, for example.
11. In the left pane, they selected Oracle for the CMS Database and they
input the server, username and password credentials.
experience
12. In the right pane, they selected Auditing Database, Oracle, and input
the server, username and password credentials.
By default the Reset existing database is selected.
They had two different accounts for the CMS and AUDIT on 2 table
spaces. This is to optimize the performance and follow the company
policies. They also validated with the Operations Team that these accounts
have enough privileges and space (See Database accounts on page 43).
They clicked Next. The "Select Web Application Server" screen was
displayed.
13. They selected the Install Tomcat application server option. They clicked
Next.
The "Configure Tomcat" screen was displayed
14. They accepted the default values in the input fields. They will modify the
settings later if needed.
They clicked Next.
The "Start Installation" screen is displayed.
65

The installation process began and was completed when BusinessOb
jects Enterprise XI 3.0 has been successfully installed was
displayed.
16. They selected Launch BusinessObjects Administration Console and
clicked Finish to exit.
A new browser window opened and within a few seconds they were
prompted to log into the Central Management Console (CMC).
17. They verified that the connectivity between the BusinessObjects CMS
and the Oracle Server was working by logging onto the CMC.
a. They typed COMPUTER01 in System.
b. They typed Administrator in User name .
c. They typed the password in Password.
d. They clicked Log On to access the CMC.
Accessing the CCM home page verifies that the BusinessObjects

Enterprise CMS is communicating with the Oracle database server.
Install another set of BusinessObjects Enterprise

servers cluster2
The BI team will provide the documentation to the Operations Team to install
XI 3.0 on COMPUTER02.
1. They ran setup.exe from a network shared folder where the DVD
BusinessObjects XI 3.0 software was copied.
The "Please Choose Setup Language" dialog was displayed.
2. They selected English for the installation setup from the pull-down list
provided and clicked OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" was displayed.
The "License Agreement" screen was displayed.
4. They selected I accept the License Agreement and click Next.
experience
The "User Information" screen was displayed.
5. They entered the requested information for Full Name, Organization, and
Product Keycode. They clicked Next.
The "Choose Language Packs" screen was displayed.
6. They selected the Language Packs they wanted to install. They clicked
Next.
They installed only the English as English is the official company language.
The "Install Type" screen was displayed.
They wanted to install a cluster, so the only way to do that was to select
the custom install, otherwise, it will install a single computer.
They wanted to install on the D drive, because this is the company policy.
They did not change the rest of the path and wanted to use the same
path as for Cluster1. It will be easier later on for maintenance to have the
same installation on all servers.
7. They chose Custom or Expand and clicked Next.

The "Select Features" screen was displayed.
They installed the same products as on cluster1. It will be easier later for
the maintenance to have the same configuration on all servers.
8. They configured the screen as follows:

• They expanded Server Components > Central Management Server.
• They clicked the icon beside MySQL and selected Entire Feature will
be unavailable.
• They clicked the icon beside Auditor and selected Entire Feature will
be unavailable.
They unchecked MySQL in order to access the next screen where
they can choose an existing CMS database (on Oracle).
67
• They clicked Next.

The "CMS Cluster" screen was displayed.
9. They selected the If No...option and provided the following configuration

details:
• They typed 6402 in New CMS Port.
Any number can be used as the CMS of cluster2 is on another
computer. There can be no conflict unless the 2 CMSs are on the
same computer with the same port. However, they wanted to make a
difference between the CMS of the COMPUTER01 (CMS port = 6400)
and the CMS of the COMPUTER02 (CMS port = 6402).
experience
• They typed COMPUTER01 in "Existing CMS Hostname".

• They typed 6400 in "Existing CMS Port". They had to put the port of
the first CMS
• They typed the password in "CMS Administrator Password" field. The
administrator password is the password that they entered during the
installation of COMPUTER01.
They clicked Next. The "Server Intelligence Agent" screen was
displayed.
10. They typed CLUSTER2 in "Node Name" and 6412 in "Port".

They could put the number they wanted as they had only one SIA on
COMPUTER02. There cannot be a conflict unless the two SIAs are on
the same computer with the same port. They put the port 6412 in order
to make a difference between the SIA of the COMPUTER01 (SIA port
6410) and COMPUTER02 (SIA port 6412).
69

The "CMS Database Information" screen was displayed.
12. In the left pane, they selected Oracle for the CMS Database and they
input the server, username and password credentials.
experience
They verified that they could access the two accounts with SQL*Plus.
(See Install the BusinessObjects Enterprise Servers cluster1 on page 60).
Note:
The installation will also check that the rights are correct.
13. In the right pane, they selected Auditing Database, Oracle, and input
the server, username and password credentials.
By default the "reset existing database" is grayed out. This is normal as
you have already installed one cluster. They have two different accounts
for the CMS and AUDIT on two servers. This is to optimize the
performance and the company policy.

The "Start Installation" screen was displayed.
15. They clicked Next to start the installation.
The installation process began and was completed when "BusinessObjects
Enterprise XI 3.0 has been successfully installed" was displayed.
71
16. They selected Launch BusinessObjects Administration Console and

clicked Finish to exit.
A new browser window opened and within a few seconds they were
prompted to log into the Central Management Console (CMC).
17. They verified that they can see the 2 computers.
Run with the services account
This was done by the Operations Team on the Production environment

(because the BI Team did not have access to the production computers.)
The company policy was that the BusinessObjects installation was done with
a dedicated account. Therefore, the BusinessObjects servers will run with
another dedicated network account. There are multiple reasons for that:
• They had to access to an SAN, and this was only possible with a network
account.
• They had to set up the AD authentication and this was possible only with
an network account.
1. They stopped the two clusters.

2. They validated that the network account would be part of the administrator
group by right clicking on their computer, selecting manage, going to
Local and Users and Groups, selecting Groups, Administrators and
adding the network user (in this case networkaccount1).
3. They accessed the SIA properties by clicking it.
4. They unchecked the system account and added the network account.
experience
5. They started the SIAs on both servers.
Cluster the file repository servers
In this case, the FRS will be on an SAN. (An SAN unit is essentially a
self-contained computer connected to a network, with the sole purpose of
supplying file-based data storage services to other devices on the network.)
In order to have access to this SAN you need to have one network account.
They will use storage on the following SAN, SAN01 in the following directory:
\\SAN01\FileRep\Input
This folder will store data for the File Repository servers installed on
COMPUTER01 and COMPUTER02. The folder must contain two subfolders:
Input and Output. They had to enable sharing for the Filestore folder and set
Full, Change, and Read permissions for their network service account in this
case: networkaccount1.
73
1. By default, documents and universes were installed in the current FRS

file (install directory\Business Objects\Business Objects
enterprise 12.0\FileStore\Input.
The BI Team had to be logged into the Central Management Console on
COMPUTER01 for the procedure below. To complete the setup, they had
to cluster all the File Repository servers.
By default the Output is empty. The output file is used for instances when
scheduling documents. However, they have the defaults documents in
the Input.
They had to move these folders with their contents to the new locations:
\\SAN01\FileRep\Input\
\\SAN01\FileRep\Output\
2. They double-clicked the cluster1.InputFileRepository entry.

The cluster.InputFileRepository properties were displayed.
3. They replaced the current value in the File Store Directory field by typing
\\SAN01\FileRep\Input\. They also replaced the current value in the
Temporay Directory field by typing \\SAN01 \FileRep\Input\temp\.
Note:
The “\” at the end is very important; if it is not used, errors will result.
4. They double-clicked the cluster1.OuputFileRepository entry.

The cluster.OutputFileRepository properties were displayed. They
replaced the current value in the File Store Directory field by typing
\\SAN01\FileRep\Output\. They also replaced the current value in the
Temporay Directory field by typing \\SAN01 \FileRep\Output\temp\.
Note:
The “\” at the end is very important; if it is not used, errors will result.
5. They clicked Save.
experience
6. They restarted their server.

Since everything had been correctly set up, they no longer received any
error messages.
7. They repeated Steps 3, 4, 5 and 6 for COMPUTER02.
Configure server parameters
The BI team specified some parameters directly into the "Server Intelligence
Agent Properties" window in order to improve the performance of the CMS:
Command Parameter
CMS -maxobjectsincache 100000
CMS -ndbqthreads 5
The first option, maxobjectsincache, specifies the number of objects the

CMS can store in memory so that if a request is within this limit, it does not
access the database. The second option, ndbqthreads, specifies the number
of allowable connections the CMS can make to the database. Both are geared
to optimizing database access time; the first by reducing the number of times
it needs to be able to access the database and the second by increasing the
pipe by which the database can be accessed. See BusinessObjects
Enterprise XI 3.0 Administration Guide, page 515. (Central Management
Server chapter).
Configuration of Active Directory
The BI team set up the AD authentication with the help of the Operations
Team.
75
Configure the system in Active Directory
This step was done by the Operations Team (as the BI Team did not have
access to the Active directory). In order to configure the system in Active
Directory authentication they had to do a number of steps. The BI Team
asked the Operations Team to create one service account with specific rights.
• In this case, the service account used is networkaccount1.
• The Operations Team needs to give to this account the following properties
in the Active Directory:
• The account is trusted for delegation.
• Use DES encryption if the JDK version being used is lower than
V1.5.
• Uncheck the option User must change password at next logon.
Configure the service account rights
In order to support the Active Directory authentication, you must grant the
service account the right to act as part of the operating system and log on
as a service. This must be done on each machine running the Server
Intelligence Agent Service.
This was done by the Operations Team on the production environment (as
the BI Team did not have access to the production computers). To configure
Local Security model:
1. They clicked Start > Administrative Tools > Local Security Model
2. They clicked Local Policies, and then clicked User Rights Assignment.
3. They double-clicked Act as part of the operating system .
4. They clicked Add.
5. They added the user account that has been trusted for delegation and
clicked OK.
6. They double-clicked Logon as service. OK.
7. They clicked Add.
8. They added the user account that has been trusted for delegation and
clicked OK.
experience
Register Service Principle Name (SPN)
1. The Operations Team installed the SETSPN utility from Microsoft to a

Domain Controller. For the Windows 2003 domain controller, the SETSPN
utility is part of a Windows 2003 support tools and can be downloaded
from the following location:
http://www.microsoft.com/downloads/details.aspx?FamilyId=6EC50B78-
8BE1-4E81-B3BE-4E7AC4F0912D
2. Afterwards, they ran the SETSPN utility to register HTTP using the
command below:
SETSPN.exe –A HTTP/COMPUTER01.dom.com networkaccount1
Note:
At any point they could type SETSPN.exe –L networkaccount1 to get
a listing of what is currently registered for the account.
Configure the AD plug-in
This was done by the BI Team and the Operations Team.

First, the Operations Team configured the BusinessObjects Services (See
Run with the services account on page 72).
For AD authentication to function, Business Object Server Intelligence Agent
service should run under the domain account that has been trusted for
delegation.
In order to support Kerberos AD, the BI Team had to configure the Windows
AD security plug-in in the CMC to use Kerberos authentication. This included:
• Ensuring Windows AD authentication was enabled.
• Setting up an AD account. The BI Team asked the Operations Team for
one Active Directory user account. In this case the account is named:
ADreadOnly.
• Enabling Kerberos and setting the service principal name.
To configure the Windows AD security plug-in:

1. They went to the "Authentication management area" of the CMC.
2. They clicked the Windows AD tab.
77
3. They ensured that the Windows Active Directory Authentication is enabled

check box is selected.
4. They specified the AD administrator account:
• They clicked AD Administrator Name.
• They entered the name and password for the account ADReadOnly
and the default AD Domain. They used the ADReadOnly account to
register the groups that will have access to InfoView.
• They clicked Update.
5. In the "Mapped AD Member Group" area, they mapped the AD group for
the AD users who require access to BusinessObjects Enterprise via AD
authentication.
6. Under Authentication Options they selected the following:
• They selected the Use Kerberos authentication check box.
• In the Service Principal Name box, they entered the service principal
name of the service account. They entered the account which runs
the SIA server: in this case, networkaccount1.
7. They updated and logged out of the CMC
Note:
The format for the AD Administrator Name field is Domain\User. The AD
Administrator account (in this case ADreadOnly) requires read access to
Active Directory only; it does not require any other rights.
experience
Configure Tomcat web.xml file
This was done by the BI Team on the sandbox and qualification environments.
the BI Team did not have access to these servers). The Operations Team
made the following modifications to the web.config file to ensure Windows
authentication is enabled.
To configure InfoView for AD authentication mode , configure theweb.config

file in the \Tomcat55\webapps\InfoViewApp\WEB-INF directory:
1. They edited the web.xml.
2. They changed the authentication procedure to secWinAD:

79


<Context-param>
<param-name>authentication.default</param-name>
<param-value>secWinAD</param-value>
</context-param>
Configure the module Krb5AuthLoginModule
the BI Team did not have access to these servers).
• They created a folder C:\windows\AD to store the following two files:
krb5.ini and bscLogin.conf. They created these files on all computers
that run application servers.
The contents of the krb5.ini were the following:
[libdefaults]
default_realm = DOM.COM
dns_lookup_kdc = true
dns_lookup_realm = true
[domain_realm]
.dom.com=DOM.COM
dom.com=DOM.COM
[realms]
DOM.COM = {
kdc = AD1.DOM.COM
kdc = ad1.DOM.COM
default_domain = DOM.COM
}
The Contents of the bscLogin.conf were:
com.businessobjects.security.jgss.initiate
{
com.sun.security.auth.module.Krb5LoginModule required;
};
Active Directory creates a Kerberos token which is used in the authentication

process. This token is stored in the HTTP header.
experience
Configure the HTTP header size with Tomcat
To configure the HTTP header size with Tomcat:

1. On the server with Tomcat installed, they opened the server.xml file.
On Windows, this file is located at <TomcatDeployedLocation>/conf
2. They found the corresponding <Connector …> tag for the port number
you have configured.
For example, if you are using the default port of 8080, find the <Connector
…> tag with port=”8080” in it.
For example:
<Connector URIEncoding="UTF-8" acceptCount="100" connection

Timeout="20000" debug="0"
disableUploadTimeout="true" enableLookups="false" maxS
pareThreads="75" maxThreads="150"
minSpareThreads="25" port="8080" redirectPort="8443" />
3. They added the following value within the <Connector …> tag:
maxHttpHeaderSize=”16384”
For example:
<Connector URIEncoding="UTF-8" acceptCount="100" connec

tionTimeout="20000" debug="0"
disableUploadTimeout="true" enableLookups="false" maxS
pareThreads="75" maxThreads="150"
maxHttpHeaderSize=”16384” minSpareThreads="25" port="8080"
redirectPort="8443" />
4. They saved and closed the server.xml file.

5. They restarted Tomcat.
81
Configure the Tomcat Java option
• The Operations Team launch the Tomcat Configuration program and

added the following Java command in the Java Options of the Java tab.
-Djava.security.auth.login.config=c:\windows\AD\bscLogin.conf
-Djava.security.krb5.conf=c:\windows\AD\krb5.ini
Configure the load balancer
This configuration was done by the Operations Team.
Sorry, but we do not have the information describing how they did it. However,
you can find more information in the BusinessObjects XI Release 2 Pattern
Book for Windows. Even though this book is about XI R2, the information
given will help you.
Configure the audit database
Using the existing BusinessObjects Enterprise XI R2 auditing database with

the BusinessObjects Enterprise XI 3.0 auditing database is not supported.
When performing an upgrade to BusinessObjects Enterprise XI 3.0, the
installer does not copy the contents of the existing auditing database. So,
the BI Team must specify a new database for the XI 3.0 auditing system to
recreate all settings for the XI 3.0 version.
We explain in the topic Step 3: Analyze and understand the system on page
33 that the audit system is mandatory for the BI Team in order to know what
is happening on the system.
The BI team developed an audit system on the XI R2 environment and they

had to recreate it on the XI 3.0 environment because the audit upgrade was
experience
Step 16: Upgrade the qualification system 6
not supported, but also because they moved from an SQLserver databases
to Oracle databases and some SQL functions of the universes and documents
needed to be modified in order to be interpreted by the new Oracle database.
As the BI Team did an incremental upgrade, they had to monitor two audit
systems (one on the XI R2 system - for the BI applications not migrated yet
and one on the XI 3.0 system for the upgraded BI applications.)
For more information on configuring the auditing database, see the

BusinessObjects Enterprise XI 3.0 Upgrade Guide.
Back up the installation
The BI Team decided with the Operations Team to do a snapshot of the

VMware image just after the configuration had been completed. They also
made a back-up of the CMS and Audit databases and the FRS.
Step 16: Upgrade the qualification system

XI 3.0 was installed and backed up. The BI Team then started the upgrade.
Since they had already defined the main strategy (Deciding on the major
type of upgrade on page 17) and since they had received all the necessary
details from the Business Solution Owners (Step 14: Finalize the upgrade
wizard strategy on page 58), the BI Team was able to proceed with the
upgrade.
The BI team proceeded in four stages and ran multiple instances of Import
Wizard.
1. In the first upgrade, they upgraded all users/groups and the XI R2 security
model to XI 3.0. At this point, the security on the XI R2 system was frozen.
Nobody was allow to modify it, since all the upgrade phase was started.
(See Security freeze on page 86)
2. Once, the first upgrade was done, they validated the global security model
on the XI 3.0 system.
3. After the validation of the global security model, the BI Team started to
upgrade the BI applications.
• They imported the users/groups and folders of the BI application they
wanted to upgrade, but they did not change the security model on XI
83
3.0. The security model on XI 3.0 was upgraded during the first
upgrade. Thereafter, because this is the new reference, it must not
be changed again or updated with rights coming from the older XI R2
system.
4. They validated the upgraded BI applications.
This cycle continued until all the necessary upgrades were performed.
Installation of computer running Import Wizard
As we explained earlier Business Intelligence Team on page 12, the BI Team

cannot access the BusinessObjects servers in production. So, they asked
the Operations Team for another computer (with 1 CPU and 2 GB of RAM
and 60 GB of disk space) and they installed the XI 3.0 BusinessObjects
client. The only request for this computer was to be as close as possible
physically to the XI R2 CMS database and the XI 3.0 CMS database in order
to improve the performance of the Import Wizard between the source and
the destination environments. This book does not explain how the BI Team
installed the XI 3.0 BusinessObjects client as they used the installed default.
Specify BusinessObjects Enterprise XI Release 2 as

the source environment
The BI Team launched the XI 3.0 Import Wizard. As they have an XI R2

system, they specified BusinessObjects Enterprise XI Release 2 as the
source environment.
They launched the XI 3.0 Import Wizard, while the XI R2 production

environment system was up and running. The BI Team asked the Operations
Team to monitor the XI R2 system to see if the Import Wizard did not slow
down the XI R2 production system. The Operations Team did not raise any
performance issues on these servers.
To specify BusinessObjects Enterprise XI Release 2 as the source

environment:
1. They chose BusinessObjects Enterprise XI Release 2 from the source
list.
2. They entered the name of the source CMS in the CMS Name field.
experience
3. They typed the User Name and Password of the administrator account.
They needed to have the administrator account in order to be able to
upgrade all users/groups and the security.

The "Destination environment" screen appeared.
Specify BusinessObjects Enterprise XI 3.0 as the

destination environment
They selected the destination environment to which the wizard will export
content.
They chose to export BusinessObjects Enterprise XI 3.0. and then did the
following:
85
1. They typed the name of the destination environment's Central

Management Server in the CMS Name field.
2. They entered a User Name and Password of the administrator account.
They needed to have the administrator account in order to be able to
upgrade all users / groups and the security.
Security freeze
During the upgrade, the security model will be upgraded from XI R2 to XI

3.0.
Once this upgrade has started, the XI 3.0 system will be the new reference,
so the security changes on XI R2 need to be frozen indefinitively. No one
can modify it. However, this will not prevent users from doing their regular
jobs.
First instance of the Import Wizard
After the installation and the configuration, the BI team began the upgrade.
Their first concern was to set up the global security model. In order to set
the global security model, all the users and groups must be imported along
with the application rights and root folders rights to which they are attached.
After this is accomplished, then the global security model is initially set. Then,
you can customize it to your needs.
Their goals were to:

• Upgrade all the users/groups.
• Upgrade the application rights and root folder rights.
Import all users and groups
The BI team had to import all users and groups, along with the application
rights and root folders rights to which they are attached.
The XI R2 system was configured with AD authentication, so before importing

the users who belonged to Windows Active Directory authentication group,
experience
the BI Team ensured that the Active Directory authentication was set up and
enabled in the same way on both the source and destination systems.
They also had to be careful about the licenses they used. User licensing can
affect the behavior of the Import Wizard. See the BusinessObjects Enterprise
XI 3.0 Import Wizard Guide.
Import the application rights and root folder rights
In XI R2, the BI Team set the rights of everyone group in a way that, by
default, users who belongs only to the everyone group have no access to
any document folders. When a particular user group needed to have access
to a specific document folder, the BI team gave the rights View, Schedule
or Full control to this particular user group for this specific document folder.
In XI 3.0 there is a new setting in the Import Wizard: Import root folder
rights, which is not checked by default. This setting allows importing the XI
R2 top level folder rights to the XI 3.0. So, in this case the XI 3.0
environment will have the same behavior as the XI R2 environment.
Note:
Otherwise, by default on the XI 3.0 environment, the document root folder
rights are set in a certain way: that the View objects rights are set to Not
Specified so that a user group cannot see the Public Folders, so any
document folders under the Public Folders, even if this user group has
View, Schedule or Full control rights to these specific document folders.
So, in order to view the Public Folders, the View objects right needs to be
granted (see Set up the XI 3.0 BusinessObjects security model on page 90).
As The BI team had explicitly specified rights on all application rights
(InfoView, CMC, Designer, Web Intelligence, Crystal, Desktop Intelligence,
etc.) and top level folder ("Central Management Console Settings tab")
on the XI R2 system. As they want to keep the same behavior on XI 3.0,
they needed to import them.
1. The BI Team selected Import users and users group, Import
application rights, and Import root folder rights. Later they will upgrade
all users.
87
2. They clicked Next to continue.
Merge or Update?
The BI Team used the Update option because they wanted to update the
destination system by using the source as reference. They did not check the
automatic rename, because the BI team wanted to upgrade everything and
overwrite what was already on the destination system.
experience
Overwrite
Because the XI 3.0 software had been installed a few steps earlier, the CMS
had only the default settings on the root folders (User, Group, Inbox, Universe,
Connection, etc. ), and default application rights (InfoView, CMC, Designer,
Web Intelligence, Crystal Reports, Desktop Intelligence, etc) and had the
default groups "Administrator" and "Everyone."
The BI Team wanted to overwrite everything that already existed by default.

This is why they chose Overwrite object contents, Overwrite group and
user membership and Overwrite object rights.
89
Back up the first instance
The BI Team decided with the Operations Team to do a snapshot of the

VMware image just after the first upgrade, they also made a back-up of the
CMS, the Audit databases and the FRS.
Set up the XI 3.0 BusinessObjects security model
General security model rules
Below find some rules that are the same on XI R2 and XI 3.0:
experience
Every user is always in the Everyone group. It is not possible to remove a
user from this group.
Explicitly Denied rights can interfere with explicitly Granted rights in ways
that are not expected. When rights conflict, explicitly Denied takes priority
over explicitly Granted.
Not Specified rights are considered Denied only if the right was never
specified for the user, as well as considering all possible group and object
inheritances.
General security model setup
In this topic, we describe the company security model setup. It does not
mean you will have the same model; it depends of your environment.
For security reasons Sarbanes-Oxley (SOX), the BI team wanted to know

exactly who has access to what. They preferred to be more restricted by
default.
As they had more than 1500 document folder to manage, they considered
it easier to have by default restricted rights on all document folders and to
open only to specific document folder than to have by default open rights on
all documents folders and restricted to specific document folder.
The BI Team avoided setting explicitly Denied rights and they leave the
maximum number of rights to Not Specified (so effectively Denied for default
users - see General security model rules on page 90). They gave only to
specific document folder explicitly Granted rights for particular user group.
So these particular groups could see these specific folder and other user
group could not.
91
XI R2 settings
In XI R2, the Top Level Folder rights can only be set on the Central
Management Console Settings tab. The BI Team set the Everyone group
to Not Specified everywhere (except for Desktop Intelligence), so that the
Everyone group rights do not interfere with other rights that the BI Team will
set.
In conclusion, by default in this environment, user groups have no access

to any document folders. Only a particular user group has access to a specific
document folder after the BI team gave to these particular user group the
rights View, Schedule or Full Control on the specific document folder.
XI 3.0 settings
Note:
After one default installation, the document root folder rights are set in a
certain way: the View objects rights are set to Not Specified so that a user
group cannot see the Public Folders, and therefore cannot see any
document folders under the Public Folders, even if this user group has
View, Schedule or Full control rights to these specific document folders.
In order to view the Public Folders, the View objects rights needed to be
granted on the Public Folders.
After the BI team performed the first upgrade (and the root folder imported)
on the document root folder, the Everyone group had advanced access for
the all folders security. (In this case, advanced means set to Not Specified
for all general global rights except for Desktop Intelligence).
In this case, all user groups (except the administrator user) cannot see Public
Folders , so they cannot see any document folder under the Public Fold
ers. In fact the Public Folders needs to be accessible for all user group
but not the document folder under the Public Folder.
The BI team has to modify only one right. In the CMC, on the folders tab,
they right click all folders and select manage, they selected security and
selected : all folder security.
They selected the Everyone group and selected assign security, they
selected > advanced > add/remove rights and they granted the View
experience
objects, but for Apply to Object only, not for Apply to SubObject (last
column). See the design below.
In conclusion, by default, all user groups can see Public Folders, but only
the Public Folders (not the document folders under the Public Folders
). Depending of their rights , the user group can or cannot see a specific
document folder.
After this change, the security model has the same behavior as in XI R2,
that means
93
experience
Second instance of the Import Wizard
Once all the users/groups had been upgraded on the XI 3.0 system and the
global security (on application rights and roots folders) had been set up, the
BI team started the upgrade of the first three BI applications. At this time, all
the document folders that will be upgraded from the XI R2 system do not
exist in the XI 3.0 system.
Their goals were to:
1. Upgrade specific users/groups (given by the departments impacted in
the upgrade).
2. Not to upgrade the Inbox folders. The BI Team asked the users to move
any documents they wanted to import from the Inbox folder to the Favorites
folders.
3. Upgrade Favorites folders. (The BI applications impacted by this first
upgrade extensively used the Favorites folders. A cleaning had been
effected recently before the upgrade so that the number of Favorites
documents was reduced.)
4. Not to upgrade discussions, encyclopedia, and categories (as these BI
applications did not use them).
5. Not to upgrade events and server groups (as they did not use events and
the server groups for the three BI applications impacted).
6. Not to upgrade the calendar and profiles (not used by these BI
applications).
7. Upgrade only universes linked to the document migrated (the BI Team
received the list from the Business Solution Owners impacted in the
upgrade).
The BI Team started the second upgrade by:
1. Specifying the source environment.
2. Specifying the destination environment.
Import Favorites folders for selected users
As the BI Team had decided to import Favorite folders for these BI

applications, they selected the option Import favorite folders for selected
users.
95
Import folder and object rights
As we explained before, after the user/groups and global security were

upgraded, the next step was to upgrade the specific users and
documents/universes folders.
When the folders and documents are imported from one BusinessObjects
Enterprise system to another, the associated object rights are imported for
every user or group who was imported at the same time. If the user or group
was not imported at the same time, the object rights were discarded. This is
the reason why we have to re-import all users and groups associated with
particular documents/universes folders.
Import the application rights and root folder rights
The BI Team unselected Import application rights and Import root folder
rights because they did not want to overwrite the global security which was
already customized.
experience
Merge or Update?
Because at this point the XI 3.0 environment has become the reference for
all BI applications already migrated, the BI Team did not want to overwrite
any objects already present in the XI 3.0 system. They selected the merge
option so that the Import Wizard would add all the selected objects from the
source to the destination without overwriting any objects on the destination
environment. All of the objects on the destination environment are preserved.
See the BusinessObjects Enterprise XI 3.0 Import Wizard Guide, page 15.
Normally, all the objects added to the XI 3.0 system will be new, except the
users/ groups.
97
Import documents / universes
The BI Team selected the BI applications that they wanted to update and
checked Import all instances of each selected objects.
Universe Import Options
The BI team selected the option Import the universes and connections
that the selected Web Intelligence and Desktop Intelligence documents
use directly. They used this option because they could select additional
universes to import on the next screen. They mainly wanted to validate that
they would import only the universes defined by the Business Solution
Owners.
To import universe overloads, they selected Keep universe overloads for
imported users and groups. Since they were importing universe overloads,
they had to also select the users, groups, and universes on previous screens
in the Import Wizard.
experience
Complete the Import Wizard
The "Import Summary" window appears when the Import Wizard is finished.
The window displays the results of the import.
As they will re-import users and groups which already exist in the destination
system, they will have the following warning for all users or groups already
existing on the destination system:
The User XXX already exists on the destination system. Only

group membership information will be updated.
The information that appears in the Detail Log is also written to a log file.
The log file starts with the name ImportWiz, and is located in the default
path <BusinessObjects installation path>\Business
Objects\BusinessObjects Enterprise 12.0\Logging\. The BI team
analyzed these documents to be sure that the import was successful.
99
Step 17: Test the qualification system
Configuration after the Import Wizard has run
After the Import Wizard has been run (depending on which objects you
exported), you must perform one of the following actions:
• If you import events (this company did not import events), you must run
the EventUpdater script. See the BusinessObjects Enterprise XI 3.0
Upgrade Guide, "Updating Imported Events", page 50.
• If you want to use the Search Index Program (this company is not using
this program for the moment) , see BusinessObjects Enterprise XI 3.0
Upgrade Guide, "Adding the Search Index Program", page 46.

Once the upgrade was done, the BI team has now to test and validate the
system. The BI Team developed different types of tests: Functional, User
Acceptance Testing and benchmark testing.
Functional testing
First, the BI Team validated the security model on the XI 3.0 system. They
validated that the users and groups had the correct rights on the BI
applications, the root folders, and some document folders. They focused
their tests mainly on the CMC, the platform and power user tools such as
Import Wizard and Designer. During this phase only the BI Team participated
in this testing. You will find in the following topics some examples of their
tests.
experience
Step 17: Test the qualification system 6
Platform validation
Table 6-2: Platform Validation (BI Team)
Category Type Subject Description
Start / Stop a serv- Start / Stop a serv-

Server Manage-
Platform er from CMC - im- er from CMC - im-
ment
pact on CMC pact on CMC
From CCM / From

CMC : mix all
Server Manage- combinations and
Platform Disable a server
ment check that informa-
tion is the same in
both interfaces
Server Manage- Validate servers What is the error

Platform
ment stopped message
Test failover on
Web Intelligence
servers / job
Server Manage-
Platform Failover testing servers / CR
ment
servers / CMS
servers / web apps
servers
Server Manage- Test cluster of Test cluster of

Platform
ment / Clustering CMS CMS
Test cluster of Test cluster of

Server Manage- Web Intelligence / Web Intelligence /
Platform
ment / Clustering crystal / job Crystal / Job
servers servers
Server Manage- Test cluster of web Test cluster of web

Platform
ment / Clustering apps servers apps servers
101
Review the set of

Test capture of data, volume of
Platform Auditing
data in Auditing the database, type
of database, etc.
CMC validation
Table 6-3: CMC Validation (BI Team)
CMC Security / Folder Test view right Test view right
Test schedule
CMC Security / Folder Test schedule right
right
Test view and re- Test view and re-

CMC Security / Folder
fresh right fresh right
CMC Security / Folder Test full control Test full control
CMC Security / Folder Test edit right Test edit right
Test the advanced Test the advanced

rights rights
Test no access Test no access

rights rights
Test right to copy / Test right to copy

move /delete / move /delete
CMC Security / User Test create user Test create user
CMC Security / User Test remove user Test remove user
experience
Test impact of in-

heritance with
CMC Security Test inherited right
larger restricted
rights
Test explicit / not Test explicit / not

CMC Security
specified rights specified rights
Test combination Test combination

CMC Security of user and group of user and group
rights rights
Identify which
Test impact of ac-
rights need to be
cess rights on uni-
CMC Security / Universe granted / denied to
verse to run a
allow refreshing a
query
universe query
Identify which
Test impact of ac-
rights need to be
Security / Universe cess rights on uni-
CMC granted / denied to
Connection verse connection
allow refreshing a
to run a query
universe query
Security / Sched- Access to in- If no instance has

CMC
uler stances been created
If there are exist-

ing instances gen-
erated by the user
Security / Sched- Access to in-
CMC / another user:the
uler stances
right to view all in-
stances that the
user owns
Security / Applica- Web Intelligence:

CMC Test this right
tion Edit query right

CMC Test this right
tion View SQL right
103

CMC Test this right
tion Modify SQL right
Security / Applica- Universe Designer:

CMC Test this right
tion Test access right
Universe Designer:
Security / Applica-
CMC Test right to import Test this right
tion
universes
Universe Designer:
Security / Applica-
CMC Test right to export Test this right
tion
universes
Universe Designer:
Security / Applica-
CMC Test right to edit Test this right
tion
connections
Universe Designer:
Security / Applica-
CMC Test right to create Test this right
tion
connections
Security / Applica- Crystal: Test ac-

CMC Test this right
tion cess right
Security / Applica- Crystal: Test right

CMC Test this right
tion to import docs

CMC Test this right
tion to export docs

CMC Test this right
tion to create docs
Define default ac- Define default ac-

CMC Settings cess to docs on cess to docs on
the last instance the last instance
Define the neces- Define the neces-

CMC Sent to Inbox sary rights to send sary rights to send
to Inbox to Inbox
experience
Test NT authentica- Test NT authenti-

CMC Authentication
tion cation
Test AD authentica- Test AD authenti-

CMC Authentication
tion cation
Universe Designer validation
Table 6-4: Universe Designer validation (BI Team)
Import universes
Universe Designer Import Import universes from General Fold-
er
Import universes
Universe Designer Import Import universes
from other folders
Export universes
Universe Designer Export Export universes
to other folders
Export other uni-

Universe Designer Export Export universes
verses
New universe fold-

Universe Designer Folder Create folder
er on the root
Create new con-

Universe Designer Connection Create connection
nection
Edit existing con-

Universe Designer Connection Edit connection
nection
Edit other connec- Edit other connec-

Universe Designer Connection
tions tions
105
Enhance a uni- Make changes in

Universe Designer Universe
verse the universe
InfoView/Web Intelligence/Crystal/Desktop Intelligence/Rich

Client validation
Table 6-5: InfoView/Web Intelligence/Crystal/Desktop Intelligence/Rich Client validation

(BI Team)
Test Number Category Type Subject Description
Windows AD
1 InfoView Login Login
login
Check view
View a docu-
2 InfoView View document
ment
rights
Check edit
Edit a docu-
3 InfoView Edit rights on docu-
ment
ment
Check refresh
4 InfoView Refresh Refresh data rights on docu-
ment
Check sched-
Schedule a
5 InfoView Schedule ule rights on
document
document
Web Intelli- Web Intelli-

6 InfoView Create
gence gence
Save a docu- Web Intelli-

7 InfoView Save
ment gence
experience
Drill in the doc- Web Intelli-

8 InfoView Drill
ument gence
Export a docu- Web Intelli-

9 InfoView Export
ment gence
Send a docu- Web Intelli-

10 InfoView Send
ment gence
Desktop Intelli- Desktop Intelli-

11 InfoView Create
gence gence
Desktop Intelli-
12 InfoView Create Create a folder
gence
Desktop Intelli-
13 InfoView Delete Delete a folder
gence
Desktop Intelli-
14 InfoView Search Search objects
gence
Delete a docu- Desktop Intelli-

15 InfoView Delete
ment gence
Personal docu-
View Personal
16 InfoView View ments are
documents
there
Personal in-
17 InfoView View View Inbox
box is there
Save Personal Save personal

18 InfoView Save
documents document
Save inbox
19 InfoView Save Save Inbox
document
Delete / move
Delete person-
20 InfoView Delete personal docu-
al document
ment
107
Delete a docu- Delete / move

21 InfoView Delete ment from the inbox docu-
inbox ment
Navigate set
user settings
(Interactive
Viewing, num- non-regression non-regres-
22 InfoView
ber of docs test sion test
per page, re-
gional options,
start folder
Edit, create,
save, sched-
Web Intelli- ule, export, re- non-regression non-regres-
1
gence fresh, TDC, test sion test
hyperlinks,
drill
Edit, create,
Crystal Re- save, sched- non-regression non-regres-
2
ports ule, export, re- test sion test
fresh
Edit, create,
save, sched-
Desktop Intelli- non-regression non-regres-
3 ule, export, re-
gence test sion test
fresh, import,
export
Edit, create,
save, sched-
ule, export, re-
non-regression non-regres-
4 Rich Client fresh, TCD,
test sion test
hyperlinks,
drill, filter in
ZABO mode
experience
Edit, create,
save, sched-
ule, export, re-
test sion test
hyperlinks,
drill, filter in of-
fline mode
Edit, create,
save, sched-
ule, export, re-
test sion test
hyperlinks,
drill, filter in
online mode
Edit, create,
save, sched-
ule, export, re-
fresh, TCD, non-regression non-regres-
7 Rich Client
hyperlinks, test sion test
drill, filter in
standalone
mode
Web Intelli-
8 Rich Client Install Install
gence
User Acceptance Testing (UAT)
Afterwards, the BI Team asked each Business Solution Owner impacted by

this upgrade to define with the users:
• The workflows used everyday by the users.
• The workflows using 10% of the most important documents identified by
the BI Team (during the audit). Ten% seems to give a good idea of the
upgrade. They called these tests UAT (User Acceptance Tests).
109
Step 18: Conduct a go/no go meeting to start the production environment installation
From this point on the users (who participated in this testing) worked on both
systems, the XI R2 (this will remain the reference) and XI 3.0 (only for test
validation). All the documents created or changed on the XI 3.0 system will
not be used on the final XI 3.0 system. It must be explained to the users that
the documents' being on the XI 3.0 system was for testing purposes only.
Benchmark testing
The third type of testing that was done was the benchmark testing. The BI
Team identified specific workflows. They decided to implement four scripts
to evaluate the stability of the system.
• Script 1: document view (small, medium, and large documents)
• Script 2: document refresh (small, medium, and large documents)
• Script 3: document view and refresh (very large documents).
• Script 4: run in batch scheduling documents for all BI applications.
The goal of the benchmark testing was to identify whether the system was
correctly sized for the number of users and documents upgraded or whether
they needed to add more computers. See Expandable architecture on
page 50
Each time a new application was upgraded, the BI Team performed

benchmark testing because they wanted to:
• Define the number of computers to add.
• Define the number of users who would cause a crash.
• Validate the stability during 72 hours. The target for concurrent users is
20% of the total users upgraded to XI 3.0.

start the production environment
installation
After they had evaluated and tested the installation, the import wizard , the
security and the stability, the Project Upgrade Team organized the go / no
meeting. Each team had to provide the status of the different topics to see
if they could move to the production phase.
experience
Step 18: Conduct a go/no go meeting to start the production environment installation 6
Project Upgrade Team Go
BI Team Go
Operations Team Go
Table 6-7: Go / No Go Decision
Topics What was done Status
Completed installation
Functionality testing at a level equiva-
lent to XI R2.
• Import Wizard works

fine
Usability • Active Directory
works fine
• CMC: Improvement in
Access level granular-
ity
• CMC: More intuitive
for administrators
Reliability • InfoView: More intu-
itive navigation for
users
• Publishing tested with
Web Intelligence
• Import Wizard works

fine
Security • Active Directory works
fine
111
Step 18: Conduct a go/no go meeting to start the production environment installation
Topics What was done Status
Scalability Benchmark passed.
Performance Deployabil- Rich Client remote install

ity OK
experience
Production environment
installation
7
7 Production environment installation
Step 19: Ask for the production platform
Table 7-1: Production Actors and Roles
Actor Roles
Project Upgrade Team Conduct the go / no go meeting.
Ask for the materials and configure the

BI Team
production environment.
Provide the materials, install the produc-

Operations Team tion system and provide backup re-
sources.

The BI team was not allowed to verify the installation and configuration of
the BusinessObjects product on the production server. Therefore, the BI
Team performed these steps on the qualification system; also they wrote
and provided the Operations Team with this documentation. This document
reflected exactly what they needed to do.
Therefore, Step 20 is exactly the same as Step 15. The difference is that
Step 20 was done on the production environment.
Step 19: Ask for the production platform

The BI team ordered the same materials for the production platform as for
the qualification system. In this company, the policy is to have exactly the
same production environment as the one tested in the qualification
environment. However, because of resource limitations, your production
environment may be larger than your qualification environment. If you cannot
replicate it one-on-one, try to use only two computers or CPU in production
for one computer or CPU in the qualification environment.
Of course, the BI Team used different computers, different databases (CMS

and audit) and different FRS (SAN) than for the Qualification environment.
See Order the materials on page 42
experience
Production environment installation
Step 20: Install in a production environment 7
Step 20: Install in a production
environment
The installation was done by the Operations Team.
• They repeated the steps in Step 15: Install in a qualification environment
on page 60
This step was completely done by the Operation Team following the BI
Team's documentation and advice. Additionally, during the installation BI
team member was available to answer immediately any question from the
Operations Team.

start the production environment upgrade
After the installation was finished, the Project Upgrade Team conducted a
go / no go meeting to decide whether they could move to the next phase:
production environment upgrade and roll out. It was a go; there were no
outstanding issues, so they moved to the next phase.
BI Team Go
Operations Team Go
115
7 Production environment installation
Step 21: Conduct a go/no go meeting to start the production environment upgrade
experience
Production environment
upgrade and roll out
8
8 Production environment upgrade and roll out
Step 22: Plan the rollback strategy
Table 8-1: Roll-out Actors and Roles
Actor Roles
Project Upgrade Team Conduct the go / no go meeting.
Perform the last upgrade and tested

BI Team
the system.
Operations Team Provide the backup resources.
Perform User Acceptance Testing

Business Solution Owners
(UAT).

Step 22: Plan the rollback strategy

When the BI Team upgraded the system, they did not delete any folders,
files, or documents on the XI R2 system. Once the upgrade has been finished,
these folders will be hidden using the security rights. If something had gone
wrong during the upgrade, they could always fallback on the XI R2 system
and delay the BI applications' rollout. Each upgraded BI application was
validated in the XI 3.0 qualification environment, making sure that no problems
were to be encountered in the production environment. The rollout for the
production environment was performed by the BI Team and Business Solution
Owners over a weekend to validate the environment. A decision to roll back
or roll out was taken at the end of the weekend.
Step 23: Communication, user training

and cut-over preparation
The communication and training plan had four parts. Of course, the BI Team
only communicated to the users impacted by the upgrade:
1. Six weeks before the upgrade production start: The BI Team had already
validated and tested the new functionalities during the sandbox and
experience
Production environment upgrade and roll out
Step 24: Upgrade the production system 8
qualification phases. Therefore, they were able to explain to the users
how to use the new product, added value of the product, and the technical
reasons for the upgrade. An example of the communication written by
the BI team follows:
BusinessObjects XI 3.0 is coming.
As you know, a new release of BusinessObjects named Busines

sObjects XI 3.0 will be available.
The BI team is already involved in its evaluation and will
deploy BI applications on production soon.
During our tests, we made some discoveries and we would like
to share with you this knowledge to attract attention to
the changes.
We decided to send 3 weekly technical newsletters on the

following content:
* Architecture and CMC
* InfoView, Web Intelligence & Rich Client
* InfoView & Crystal Reports
Here is the first newsletter focused on Architecture and

CMC.
Do not hesitate to contact us if needed.
2. Four weeks before the upgrade production start: The BI Team offered
on-site training for Business Solution Owners. Mandatory e-learning
training for the users upgrading to Rich Client was also offered.
3. One week before the upgrade production start: All the users who are
taking part in the upgrade should have been trained at this point. The
Project Upgrade Team explained to the users exactly what was going to
be happening in the coming days for the upgrade.
4. One day before the upgrade production start: On the XI R2, all the users
who are taking part in the upgrade have to reduce their activities on the
system. Creating, modifying and saving documents was not advised. Only
refreshing was permitted. This way, the users were sure that they would
not lose their work. If a user should happen to lose some work, the BI
Team will import the documents later. This case will be exceptional and
not communicated to the users generally.
Step 24: Upgrade the production system

When the BI Team moved some BI applications from XI R2 to XI 3.0, a gap
developed during the time they were implementing the upgrade. Data
continued to be added and changed on the XI R2 system, except if they had
119
Step 25: Perform the last validation
completely stopped the XI R2 or switched it to read-only mode. To minimize

this gap, the BI Team asked users who were impacted by the upgrade to
only use the refresh function during the final 24 hours. In order to further
reduce the gap, the BI Team did this upgrade in one day during the weekend
when no one was working. Their goal was to deal with the fewest
modifications between the two systems.
Before starting the upgrade, the BI Team asked the Operations Team to
back up the XI 3.0 environment. Normally, since the workflow for the
production system was the same as for the qualification system and the
environments are identical, the results should be the successful as they were
for the qualification system.
They applied the same workflow and exactly the same steps as for the
qualification environment system. See Step 16: Upgrade the qualification
system on page 83.
Step 25: Perform the last validation

After the upgrade was completed, the BI Team spent the second day of
weekend validating that the importation was correctly done. Some Business
Solution Owners also participated in this validation. The purpose was to
ensure that the upgrade was done successfully and the users did not face
issues the next morning.
As we explained Step 8: Define the main upgrade strategy on page 51

importing documents from the Favorites folders can import more than just
the universes and connection that you expected to get. So, you will have to
check and clean the universes and connection once the Import Wizard has
finished.
The BI Team also hid the XI R2 BI applications that had been upgraded to
the XI 3.0 system, so that if a user accidently tried to work in the XI R2
system, he would not find his old documents. If the user really needs to
access the old system, it would still be possible by making the files visible.
The diagram below shows the workflow for the upgrade, including the
validation phase.
experience
Production environment upgrade and roll out
Step 26: Conduct a go/no go meeting to roll-out the production implementation 8

roll-out the production implementation
At the end of the weekend, the Project Upgrade Team with the BI Team and
the Business Solution Owners, organized the last go/no go meeting to decide
whether the XI 3.0 system will roll out.
• Hold a go / no go meeting.
121
Step 27: Upgrade the desktop client
BI Team Go
Operations Team Go

Go
1

Go
2

Go
3
The meeting was a Go, so the first three BI applications went into
production on the XI 3.0 system, but the BI Team and the Business
Solution Owners must help the users get started.
Step 27: Upgrade the desktop client

The user were about to begin using Web Intelligence Rich Client. The BI
Team did not want users to continue using Desktop Intelligence. Since the
Web Intelligence Rich Client was a new product, it did not need to be
upgraded. The Business Solution Owners asked the users to download the
Web Intelligence Rich Client from the InfoView server and install it on their
client with the default settings.
Step 28: Roll out

The first three BI applications have been rolled out. Other BI applications
were added later. The Project Upgrade Team followed steps 23 to 25 each
time a new BI application was added.
experience

Upgrading BI Applications (For Instance, Finance, Marketing, and Sales) From XI Release 2 To XI 3.0: A Live Experience

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Upgrading BI Applications (For Instance, Finance, Marketing, and Sales) From XI Release 2 To XI 3.0: A Live Experience

Uploaded by

Copyright:

Available Formats

Upgrading BI applications (for

instance, Finance, Marketing, and

Chapter 3 General approach of the BusinessObjects XI 3.0 upgrade project 23

Phase 5: Production environment upgrade and Roll out ..........................25

Chapter 4 Assessment and strategy 27

Chapter 6 Qualification environment installation and upgrade 57

Step 15: Install in a qualification environment ..........................................60

Chapter 7 Production environment installation 113

Step 21: Conduct a go/no go meeting to start the production environment

Chapter 8 Production environment upgrade and roll out 117

About this book

The primary objective was actually to document the upgrading of some BI

It can be used as a guide for planning and deployment of BusinessObjects

The pre-existing system

Actors, roles and responsibilities

Project Upgrade Team

Business Intelligence Team

In this team are found:

The Operations Team's role is to manage all physical servers (on

In this team are found:

Business Solution Owners

The Business Solution Owners belong to the various business departments.

The Business Solution Owner's role is to support users and, if necessary,

In this team are found:

work with Web Intelligence documents without accessing a CMS. They

• Other BusinessObjects products (Data Integrator, Metadata Manager,

Deciding on the major type of upgrade

Side-by-side vs. completely new installation from

The advantage of a side-by-side installation would be that you would not

Therefore, the project upgrade team chose a completely new installation

See the drawing below:

Multiple XI 3.0 system installations

Upgrading with Import Wizard, CMS database setup

Option 2 (CMS database setup tools) and Option 3 (Third-party databases)

Each upgrade is different, so depending on your upgrade and needs, you

Incremental vs. one-shot upgrade

The Project Upgrade Team had a choice between an incremental and a

Phase 1: Assessment and Strategy

The Project Upgrade Team (with the collaboration of BI Team, Operations

Phase 4: Production environment

Then, the BI Team configured the components linked to the BusinessObjects

Phase 5: Production environment upgrade

Table 4-1: Assessement Actors and Roles

Define the plan and requirements; an-

BI Team Analyze the system.

BI Team, Business Solution Owners Need to commit time and resources to

Step 1: Define the overall plan

Project Name /ID XI 3.0 Live

Deploy BusinessObjects XI 3.0 and use

Phase 1: Assessment and Team

Phase 5: Production environment up-

Please see the go/no go decision template below:

Table 4-3: Go / No Go Table

Please find below the Risk template.

Table 4-4: Risk Template

Descrip Probabili Response

Regular Communication among Project Upgrade

Step 2: Define the requirements

Step 3: Analyze and understand the

This step is mandatory and extremely important, which is why we dedicated

The BI Team collected technical details (number of documents, users,

Deliver documents that show: