SAP BusinessObjects 4.x Upgrade / Migration to 4.x
1. TEN STEPS FOR A SUCCESSFUL
SAP BUSINESSOBJECTS
BUSINESS INTELLIGENCE
4.X MIGRATION
2. Introduction
There are several reasons why it makes sense for SAP BI users to
upgrade to the new 4.x platform:
BI 4.x stands as SAP’s most complete and unified release
of the reporting suite since the acquisition of BusinessObjects in
2007
The new BI 4.x release is built on a more robust semantic layer,
making it easy to bring multiple data sources into a one-stop
“gimme-all-my-data” shop for ad-hoc users
BI 4.x’s Integrated Life Cycle Manager offers version control like
never before, complete with the ability to rollback deployments
A better interface and auditing schema enables a deeper
understanding of how users are utilizing the product
At Digital Management, Inc. (DMI), we’ve successfully deployed
BusinessObjects for hundreds of leading enterprise clients.
Building on our wealth of experience, we’ve developed a Ten-Step
Methodology for a successful migration. Hallmarks of our approach
include:
An early, full validation phase to help avoid surprises, and
A Go-Live pilot plan for a subset of data and a limited user base,
allowing for the environment to be stabilized before scaling to a
larger number of users.
This free guide outlines our proven Ten-Step Methodology.
SAP is making big strides into the mobile frontier with this release,
with app support for iOS, BlackBerry, and Android devices
And a new Charting Engine shared across all tools enables creation
of high-impact visuals regardless of the tools being used
But doing it right matters. BI 4.x Migration is a complex project, and
every enterprise environment brings a unique set of challenges.
Without the right experience and planning, your organization could
wind up with a costly nightmare:
A prolonged migration project, with run-away costs, delayed
delivery, and a loss in confidence
An unstable environment with a painful transition and increasing
user support costs
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
1
3. Important Considerations
Before starting on your migration project, it’s vital to consider
your migration options, including desired application functionality,
technological enhancements, operational considerations, user
training, change management and ongoing support availability.
Prepare a project timeline based on overall scope, resources
available and acceptable length of services downtime – the critical
times when the environment will be unavailable to users, as well as
training time, and backup time. It is very important to decide on the
scope of the migration. This will determine the magnitude of your
project, its budget and timeline.
Key Considerations:
Audit the BI system to
determine full scope of
migration
Make recommendations
for best migration
approach & choices
Schedule Tasks
& Deadlines
Allocate Resources
(IT/HW)
Do not forget to consider
the “Down time”
Plan & allocate time and
resources for training
(Admin, Developer & End
User training)
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
2
4. The Migration Process:
10 Steps to a Successful Migration
1
5
9
Kickoff and Build Validation
Test Plan
Install and Configure other
BI 4.x Environments
Go-Live
2
6
10
Install and Configure BI 4.x
Validation
Migrate to BI 4.x PROD
Provide Post-Go-Live
Support
3
7
Validate BI 4.x and Execute
Test Scenarios
Test and Verify
4
8
Assess Validation Results &
Plan Migration
Prepare for Go-Live
Moving from SAP Business Objects R2 or XI 3.1 to BI 4.x is a not just an easy upgrade. It’s a step-by-step
migration project that requires proper assessment and strategic planning:
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
3
5. STEP
1
Kickoff and Build Validation Test Plan
Understand the existing BI system and its capabilities.
Server and Environment (32 bit verses 64 bit hardware)
Platform parameters
Databases (CMS and Audit)
Security and Authentication
Contents(Universes, WebIntelligence Reports, Desktop Intelligence
Reports, Crystal Reports, Dashboards, Schedules, Groups,
Instances and so on).
Determine your Migration approach
Evaluate whether migration will be done in one-step (Migrate
entire BI content in one step) or an incremental, multi-step process
(Migrate BI content in increments) according to your business
context.
Create a migration plan
List each component that you will use after the migration and
decide on the specific conversion path that makes sense for your
business. Multiple factors will influence the migration plan for each
component, including changes to tools and connectivity issues.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
4
6. STEP
1
Kickoff and Build Validation Test Plan
A sample migration plan:
Existing Old Tool/Technology
Existing Data Access method/
Connectivity
Crystal Reports 2008
SAP BW with BW Query
UseCrystal Report 2011 or leverage the new Crystal Report
Enterprise that use the new BICS Connectivity
Desktop Intelligence Reports
UNV on ODBC
No longer exists. Plan for a DeskI to WebI conversion using BI
4.x RCT and publish into a BI 4.x system.
Web Intelligence Reports
UNV on SAP BW with BW Query,
UNV on ODBC
Web Intelligence with UNX universe. The UNV format universes
will continue to work; we can keep them but build new Universes
in UNX.
Ad-hoc Reports in personal
folders
BW Query, ODBC Databases
Move or store them in Public Folders before migration.
But business users should test.
Security/Authentication
To be setup
No migration, opportunity to re-design
Preparing a Migration Project Plan is crucial. And of course it needs
to be created before the actual migration begins. Improper risk
assessment and inadequate planning can lead to loss of data and
costly mistakes and delays. To avoid these pitfalls it is best to consult
with experts – either in-house BI Migration specialists or experienced
partners.
Changes due to Migration
Define and document Acceptance
Before moving on to Step #2, it is important to review your migration
plan with the subject matter experts and key users to secure their
acceptance and familiarize them with the new BI setup.
Plan for an intermediate step if required: Note that previous versions
of BusinessObjects (3.1) must be migrated to BusinessObjects XI
R2 before passing to SAP BusinessObjects BI 4.0. BusinessObjects
XI 3.x and BusinessObjects XI R2 can directly upgrade to 4.0 using
“Upgrade Manager tool”
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
5
7. STEP
2
Install and Configure BI 4.x Validation
Install and Configure SAP BusinessObjects 4.xValidation environment
Typically you will have multiple environments:
DEVELOPMENT
TEST
VALIDATION
PRODUCTION
Best Practice:
Upgrade from (XI R2/XI 3.x) PRODUCTION -> SAP BusinessObjects BI 4.xVALIDATION
You can choose to install SAP BusinessObjects BI 4.x (Server, Client tools) on all the environments(parallel
migration) or consider doing a linear migration (Just one installation of SAP BusinessObjects BI 4.x) this is
accomplished by choosing the correct source system which is productive, and up-to-date and then doing
an incremental migration of selected documents.
Get the Validation environment up and running first with all necessary PROD-like configurations.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
6
8. STEP
3
Validate BI 4.x and Execute Test Scenarios
Migrate content to “VALIDATION” environment
Refer to the Migration Project Plan you prepared. Use SAP’s “Upgrade Management Tool” to migrate
Security (Groups, Users, ACL etc), Content - Universes, Reports and Repository objects, Schedules,
Publications etc. Upgrade Management tool can be paired with Import Manager to create BIAR files
that can make your migration easier.
Migrate all of current PROD content to execute the test scenarios.
Execute test scenarios
This is an opportunity to uncover any unique issues related to your environment. Execute a broad
range of test scenarios like:
Report execution (all types) and performance
Complex report production
Database connectivity
Recurring scheduled reports, publications and destinations
Report Instances, Inboxes and Private folders
Security and Authentication configurations
Any SDK applications and firewall issues
Note: In order to install the Upgrade Management tool you need to run the BI 4.x Server install that
requires a 64 bit OS
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
7
9. STEP
4
Assess Validation results
& Plan for migration
Assess Validation test results
Assess the results of the test scenarios executed
Look for any areas of issue and take this into consideration as part of the final migration
Depending on the number and type of issues encountered, make any necessary adjustments to the
migration path
Decide on the best migration path
If many post-migration content problems are identified, Option 2 from the picture above may be
preferred.
Note: Remember to install the required service packs, fix packs and hot fixes.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
8
10. Install & Configure other
BI 4.x Environments
STEP
5
Your new BI 4.x configuration isn’t complete without checking for alignment with:
New security configuration
User group mapping
New folder architecture
User assignments
Middleware and ODBC connections
New owner rights for existing products
BusinessObjects connections
Specification of rights for new products etc.
Your new BI 4.x configuration isn’t complete without checking for alignment with:
REDUCE THE SIZE AND SCOPE OF YOUR MIGRATION
Your migration can proceed more smoothly if you clean up first: Delete scheduled jobs that have
failed, remove un-used reports and un-used instances of reports, fix repository inconsistencies,
backup existing repositories and custom web application, scripts etc.
BI 4.x architecture still includes the five core components that are included in XI R2 and R3: Web
Application Server, Back-end Servers, 1 CMS, 1 File repository, 1 Audit Database. Changes in the BI
platform, especially the adoption of 64 bit and the support of new capabilities such as monitoring or
Analysis will require you to plan for a revised sizing and architecture blueprint.
Feature
Upgrade Considerations
Authentication settings (LDAP & SSO)
Manual Re-Configuration
Reporting databases connectivity
Manual Re-Configuration
BOE Server configuration
Manual Re-Configuration
Tomcat configuration settings
Manual Re-Configuration
InfoView Customization (picture, logo)
Manual Customization
OpenDoc URL Redirects
Track and update all references in other portals
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
9
11. STEP
Migrate to BI 4.x PROD
6
Migrate Content
Migrate all the BI Content using the Upgrade Manager tool from the current version to BI 4.x PROD,
depending on the option selected post Validation assessment.
Maintain a Migration check list and review progress with the project team.
The Migration check list should include all reports, folders, publications and business owners who are
responsible for testing and acceptance.
Optional Migration-related activities
As part of the Migration plan, address the post content migration activities as needed. The following
table provides a useful starting list:
BI 4.x Upgrade - Optional tasks
Feature
Upgrade Considerations
Universes - .unv to .unx
Not needed, and typically not done.
Older Crystal Reports to Latest
Not needed, and typically not done.
QaaWS to Query Design for Dashboards Not needed, and typically not done.
DeskI report conversion
Needed, Scoped and addressed separately,
if required
Audit DB
Out of Scope, leave as is - If needed reports
can be updated using multi source universe
connevted to both the new and old Audit
Desktop Intelligence to WebI Conversion
We recommend using the BI 4.x RCT to save a step. This activity
can be done in parallel with the Migration project, outside the critical path.
Desktop Intelligence & Report Conversion Tool
DeskI to WebI conversion using BI 4.x SCT is easier, saves a step.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
10
12. STEP
Test and Verify
7
Identify what needs to be tested and perform relevant tests.
The most common tests include tests on security, functional test of the BI applications, first pass IT test on
security and content, and second-pass user-acceptance test.
Test and validate Reports and Universes in the new environment with key users and subject matter experts.
Manually test critical reports and dashboards for formatting, calculations, database connectivity & Security,
Note: It is advisable to have an acceptance testing criteria developed for selected solutions moved over to the
new version (for e.g. security model, critical folder and groups, 50 documents most frequently used)
Testing effort Calculator with minimum content manually tested for go-live
Total
% manual
verification
To be
verified
Efforts reg
(hrs)
Total efforts
(hrs)
Webi Reports
1000
5%
50
2
100
Universes
100
10%
10
8
80
Xcelsius
50
5%
3
8
24
Sub total
204
A Sample of recurring
Total
36
240
*All the above number can be modified to change the required eddort, subset of reports to
be selevred base on complexity and business importance
Fix Issues
Provide technical support and guidance to assist users in troubleshooting and answering their queries.
Assist with error resolutions, bug fixes and re-run the tests to confirm.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
11
13. STEP
8
Prepare to Go-LIVE
Have a Production Readiness Checklist ready
Once you have tested the content in the production environment, execute the
“Content promotion plan”
Using the “Life Cycle Manager” for BI 4.x PROD and BI 4.x, QA can be synchronized. Typically, the
current Development content is migrated to the BI 4.x DEV environment
Address any delta content to be migrated over from the current environment for the early pilot
users
Schedule adequate training sessions for pilot users and provide support to utilize the new features
and be productive in the BI 4.x environment
STEP
9 Go-LIVE
Go-LIVE with pilot users and minimal required content
Do a “sanity test” of the environment, access and database connectivity
Plan for contingency. Cut all access to the old environment and make sure the new 4.x system is
adopted
Stabilize the PRODUCTION environment--apart from testing content--Reports, Universes and
Dashboards for consistency of data and fixing connectivity issues. It is essential to do a load test of
the production environment for failover and load balancing. Also make sure you have a plan to test and
validate desired new features of SAP BusinessObjects BI 4.x.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
12
14. STEP
10
Provide Post-Go-LIVE Support
During this phase both the old and new environments are available in parallel. It is vital to get users
migrated to the new environment as early as possible, with minimal transition pain.
Make sure your migration is complete on all environments and provide help and support to users as
they transition to the new environment.
Plan for the conversion of any existing content that was not migrated. (e.g. Delta content and new
development)
Support the testing and on-boarding of any remaining users and content incrementally for a pre-
published period of time
Schedule adequate training sessions for new features as users are on-boarded so they can be
productive in the new environment
Plan for retiring the current BusinessObjects environment and reclaim hardware
Conclusion
Even the most complex migrations become less daunting with proper assessment, comprehensive
project planning, and careful consideration of the human change management aspects of the
project. DMI has certified migration specialists and trained services and support teams who can
assist your migration to SAP BI 4.x--ensuring a short and smooth migration period.
TEN STEPS FOR A SUCCESSFUL SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE 4.X MIGRATION
13