Você está na página 1de 41

Best Practices and Methodologies for Upgrading SAP

BusinessObjects Enterprise to SAP BusinessObjects BI 4.0

Best Practices and Methodologies for Upgrading SAP BusinessObjects Enterprise to SAP BusinessObjects BI 4.0
Best Practices and Methodologies for Upgrading SAP BusinessObjects Enterprise to SAP BusinessObjects BI 4.0

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality

mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any

reason without notice. This document is provided without a warranty of any kind, either

express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no

responsibility for errors or omissions in this document, except if such damages were

caused by SAP intentionally or grossly negligent.

Agenda

Upgrade Overview and Concepts Upgrade Best Practices Technical Implementation

Appendix

Upgrade Overview and Concepts

Upgrade Overview and Concepts

Why Upgrading?

• Better integration with SAP BW Data access • New dimensional semantic layer • Multi-source
• Better integration with SAP BW
Data access
• New dimensional semantic layer
• Multi-source universes
• Harmonized user experience across the suite • Interoperability Usability / Productivity • Advanced analytical
• Harmonized user experience across the suite
• Interoperability
Usability / Productivity
• Advanced analytical insight
• Brand new search capability
• Integrated platform monitoring • Advanced auditing capabilities Cost of Ownership • Supportability and
• Integrated platform monitoring
• Advanced auditing capabilities
Cost of Ownership
• Supportability and root-cause analysis
• 64 bits server architecture

Planning your Upgrade

Typical Upgrade Timeline

Milestone 1

M2

M3

M4

upgrading

Planning
Planning

Considerations before

Assessment magnitude of project Time and Deadlines

Design
Design

Down time

 Time and Deadlines Design   Down time Implementation  Training  Backup Resources
Implementation
Implementation

Training

Backup

Resources (IT/HW)

Cutover
Cutover
Go Live
Go Live

Checklist - System Considerations

Checklist - System Considerations Platforms Platforms supported with BI 4 change Architecture changes - servers are

Platforms

Platforms supported with BI 4 change

Architecture changes - servers are now 64 bits only

Review each component of

the landscape to define the

appropriate strategy

Version upgrade path

Newer systems have a direct upgrade path

Older systems may require extra steps

Product Changes

Some features may be staged to a later BI 4 release

Some products are deprecated or replaced

Parameters and customization

Not automatically upgraded

Parameters and customization Not automatically upgraded Recommendations are provided in this presentation Understand
Parameters and customization Not automatically upgraded Recommendations are provided in this presentation Understand

Recommendations are

provided in this presentation

Understand the upgrade

path for each product you

are using

Capture all parameters and customization to understand what it means to the new systemin this presentation Understand the upgrade path for each product you are using © 2011 SAP

Checklist - Content Considerations

Security upgrade

Should you carry over the existing users and associated security ? Should you take the opportunity to do some redesign ?

Content inventory and cleanup

Should you upgrade the all content or take the opportunity

for some cleanup?

Full system vs Staged upgrade

Upgrade the entire system

Or upgrade one department / group at a time

Acceptance / Validation

Should you test the upgrade process?

Acceptance / Validation Should you test the upgrade process? Review your options and needs. Details in
Acceptance / Validation Should you test the upgrade process? Review your options and needs. Details in
Acceptance / Validation Should you test the upgrade process? Review your options and needs. Details in
Acceptance / Validation Should you test the upgrade process? Review your options and needs. Details in

Review your options

and needs. Details in this deck.

Recommendation to at

least do some cleanup

before upgrading

Review the pros and

cons depending on your own constraints

Obviously yes! Test

your upgrade on a

sandbox

depending on your own constraints Obviously yes! Test your upgrade on a sandbox © 2011 SAP

Upgrade Best Practices

Upgrade Best Practices

Versions Upgrade Path

No direct Upgrade

Go first to XI R2 or XI 3.x

No direct Upgrade Go first to XI R2 or XI 3.x

BI 4.0

BOE XI R2 BOE XI 3.x BOE XI CE8 / CE9 / CE10 BO 5
BOE XI R2
BOE XI 3.x
BOE XI
CE8 / CE9 /
CE10
BO 5 / BO6
BOE XI R2 BOE XI 3.x BOE XI CE8 / CE9 / CE10 BO 5 /

Direct Upgrade using

Upgrade Manager Tool”

BO 5 / BO6 Direct Upgrade using “ Upgrade Manager Tool” BOE stands for BusinessObjects Enterprise.

BOE stands for BusinessObjects Enterprise. BI stands for Business Intelligence CE for Crystal Enterprise.

Product Changes - BI Platform Components

XI R2 / XI 3.1

BI 4.0

 

Upgrade Considerations

Binaries

New binaries

The full landscape has to be re-installed

Audit

New audit schema

Historical audit data is not kept. Need to plan for a workaround

InfoView

BI Launch Pad

New interface

Report pinning

Dashboard Builder

BI Workspace

Corporate, Personal and My InfoView

Dashboards become BI Workspaces but some analytics must be recreated in Xcelsius

Encyclopedia /

End of Life

No upgrade

Discussion

Performance

End of Life

No upgrade

manager

Search

New search technology

The search index will be re-built in BI 4.0

Product Changes - BI Clients

XI R2 / XI 3.1

BI 4.0

Upgrade Considerations

Crystal Reports

CR 2011 and CR Enterprise

All reports are by default upgraded to CR 2011

Possible manual upgrade to CR Enterprise

Desktop Intelligence

End Of Life

Report Conversion Tool converts into Web Intelligence format prior or after the upgrade

Xcelsius 2008

Dashboards

Flash files will continue to work

Conversion to new format is optional

Conversion adds new features (globalization, UNX queries…)

Explorer

No UNV support

Information Spaces based on Excel are upgraded, the

ones based on UNV and bookmarks are not !

Voyager

Analysis, edition for OLAP

Some of workspaces will be upgrade to Advanced Analysis, the others require manual changes

Web Intelligence

Web Intelligence

Fully upgraded

Web Intelligence SDK

No Web Intelligence

Wait until full support and availability of Interactive

SDK support

Analysis (REBEAN) SDK in a later release

Product Changes - BI Clients - Semantic Layer

XIR2 / XI 3.1

BI 4.0

Upgrade Considerations

Universe Designer - UNV format

No change

None, universes and designer as in XI 3.x

n/a

Information Designer UNX format

Relational UNV can be converted to UNX

OLAP UNV have to be re-created in UNX

 

(future version will support conversion)

Product Changes - Tools

 

XI R2 / XI 3.1

BI 4.0

 

Upgrade Considerations

LCM (XI 3.1 only)

Integrated in BI 4.0

No separate installation required

Report Conversion

No Change

Same feature than XI 3.1 with the support

of the Online to Online mode

Translation Manager

Integrated in BI 4.0 client tools

Parity of features with XI 3.1 is maintained

All translations previously done will be

 

retained

WDeploy

Integrated in BI 4.0

WDeploy GUI available

Import Wizard

Upgrade Manager

New tool. More details in this presentation

Product Changes - Other Components

 

XI R2 / XI 3.1

BI 4.0

 

Upgrade Considerations

Integration Kits

Integrated in BI 4.0

No separate installation required

 

for SAP, PeopleSoft, Siebel, JDEdwards, Oracle

Integration Kit

Not available

No upgrade : wait for availability in a later release

 

for SharePoint

Data Federator

Partially integrated in BI 4.0

Existing DF 3.x deployments remain compatible with

 

BI 4.0

Live Office

No change

Existing documents will continue to work

Need to update client machines

Mobile

Integrated in BI 4.0

Local content moved with upgrade manager

3.1 and BI 4.0 may coexist (2 client versions on the

device)

Parameters to be re-set or copied

Query as a Web

No change

QaaWS will continue to work

Service

Upgrade Manager will detect dependencies to

(QaaWS)

universes (UNV)

Dashboards on QaaWS will continue to work

Security Upgrade

XI R2

BI 4.0

Continuity + new features have been added since XI R2

In BI 4.0 you have to :
In BI 4.0 you have to :

XI 3.x BI 4.0

Security model is the same as the one of XI 3

In BI 4.0 you have to :
In BI 4.0 you have to :

Set up rights at the root folder

Specify the new “owner right” for existing products

Specify rights with new products

(WRC, IDT, LCM, etc)

Simplify your security model by :

creating Custom Access Level

using selective enforcement of rights (Objects or Sub Object)

Specify the new “owner right” for existing products

Specify rights with new products (IDT, LCM, etc )

existing products  Specify rights with new products (IDT, LCM, etc ) © 2011 SAP AG.

Content Inventory and Cleanup

Project & Risk control

Upgrading content that is not

needed increases risks and time to

upgrade

Governance

Limiting the proliferation of

universes and reports allows the

business to be more efficient

and reports allows the business to be more efficient ■ Fix or delete scheduled jobs that

Fix or delete scheduled jobs that are paused or failed

Detect and delete un-used reports after checking with users

Remove older report instances or un-used instances

Fix repository inconsistencies

Repository Diagnostic Tool Instance Manager / CMC Auditing Upgrade Management Tool
Repository
Diagnostic Tool
Instance
Manager / CMC
Auditing
Upgrade
Management Tool

Special content type

• Upgraded with the user Inboxes Personal Documents • Possible to opt-out
• Upgraded with the user
Inboxes
Personal Documents
• Possible to opt-out
• Come with the report Reports Instances • Option in Upgrade Management Tool not to
• Come with the report
Reports Instances
• Option in Upgrade Management Tool not to import
them
• Automatically carried over with the scheduled Scheduler Jobs report
• Automatically carried over with the scheduled
Scheduler Jobs
report

Full System vs Staged Upgrade

Full / One Shot Upgrade

Upgrade all content at once

Only 1 system to maintain

Requires lockdown of the entire

system

Issues affect the entire system

Long downtime

Simpler (less options)

entire system  Long downtime  Simpler (less options) Stage / Incremental Upgrade per department 

Stage / Incremental Upgrade per department

Upgrade content in stages

2 systems to maintain

Requires lockdown of department folder

Issues affect only the department upgraded

Short downtime

folder  Issues affect only the department upgraded  Short downtime © 2011 SAP AG. All

Ye
s

Yes

Full System vs Staged Upgrade

Small and simple deployment Full / One shot upgrade
Small and simple deployment
Full / One shot upgrade

Larger shared services deployments

Do you have a pre-prod

to validate the upgrade

?

Can you afford a longer downtime ?

Full / One shot upgrade

No

No

afford a longer downtime ? Full / One shot upgrade No No Staged / Incremental upgrade

Staged /

Incremental

upgrade

recommended

Perform upgrade tests

to evaluate the

expected downtime

Full System Upgrade Considerations

No lockdown or read only options available in BOE To lockdown a BOE system:

1. Shutdown your application server

2. Disable and stop all “BusinessObjects servers” except the “CMS, Input and output”

3. Block all access to the CMS port except between your source and destination

© 2011 SAP AG. All rights reserved.

3. Block all access to the CMS port except between your source and destination © 2011

21

Staged Upgrade Considerations

To lockdown a department folder, modify folder rights:

XI R2: explicitly deny view objects rights

XI 3: create a custom access level and explicitly deny view objects rights

 XI 3: create a custom access level and explicitly deny view objects rights © 2011

© 2011 SAP AG. All rights reserved.

22

Acceptance / Validation

In Place On a Sandbox As part of the planning Acceptance process right after the
In Place
On a Sandbox
As part of the planning
Acceptance process right
after the actual upgrade
and discover process
to the TEST system

Products features and functions

Compatibility with existing systems

Estimate time to upgrade

Success of the content

upgrade (users, security,

universes, reports…)

Products features and functions

Security model

critical folder & groups

top 10 most used

BI Content

50 documents most frequently used

50 documents with longest refresh time

5 most critical documents for power

users and VIPs (Inboxes / Personals /

Public Folders)

10 universes most frequently used

/ Personals / Public Folders) ■ 10 universes most frequently used © 2011 SAP AG. All

Technical Implementation

Technical Implementation

Solution Architecture

The general BI 4.0 architecture hasn’t changed compare to XI R2 and XI 3

4.0 architecture hasn’t changed compare to XI R2 and XI 3 5 main components  Web

5 main components

Web Application Server

Back-end Servers

1 Central Management System

(CMS) database (infoobjects)

1 File Repository (physical reports repository)

1 Audit Database

Architecture Upgrade - Overview

Main steps

Setup the new landscape with the new software version

Move the BI content from the existing system to the new one

version  Move the BI content from the existing system to the new one © 2011

Architecture Upgrade - Implementation

Architecture Upgrade - Implementation BI 4.0 system Existing BOE XI R2 or XI 3 environment 1

BI 4.0 system

Existing BOE XI R2 or XI 3 environment 1 Previous (Xir2 or Xi3.1) system
Existing BOE XI R2
or XI 3 environment
1
Previous (Xir2 or
Xi3.1) system
Existing BOE XI R2 or XI 3 environment
Existing BOE XI R2
or XI 3
environment
Existing BOE XI R2 or XI 3 environment
Existing BOE XI R2
or XI 3 environment
Upgrade the BOE 3 content (live to live) New BOE BI 4.0
Upgrade the BOE
3
content (live to live)
New BOE BI 4.0
environment 2
environment
2

Installation and configuration of third parties and customization

New BOE BI 4.0 environment
New BOE BI 4.0
environment
third parties and customization New BOE BI 4.0 environment Time  On Windows, use different servers

Time

On Windows, use different servers to install and run both systems in parallel

On UNIX, use different servers or different user accounts on the same server

Upgrade Considerations (DEV/ QUAL / PROD)

Best practice: upgrade from previous version (XI R2 / XI 3.x) Production to BI 4.0 Qualification

Current limitation of LCM in BI 4.0 (to be addressed in a future minor release) may lead to:

previous version (XI R2 / XI 3.x) Production to BI 4.0 Production

version (XI R2 / XI 3.x) Production to BI 4.0 Production LCM or IW LCM or

LCM

or IW

(XI R2 / XI 3.x) Production to BI 4.0 Production LCM or IW LCM or IW

LCM

or IW

XI 3.x) Production to BI 4.0 Production LCM or IW LCM or IW Previous (XI R2
XI 3.x) Production to BI 4.0 Production LCM or IW LCM or IW Previous (XI R2
XI 3.x) Production to BI 4.0 Production LCM or IW LCM or IW Previous (XI R2

Previous (XI R2 / XI 3.x) Production

Previous (XI R2 / XI 3.x) Development

* Upgrade Manager
* Upgrade
Manager
Previous (XI R2 / XI 3.x) Development * Upgrade Manager LCM * Previous (XI R2 /

LCM *

(XI R2 / XI 3.x) Development * Upgrade Manager LCM * Previous (XI R2 / XI

Previous (XI R2 / XI 3.x)

Qualification

* In BI 4.0, LCM does not move

document instances, user inboxes

and personals documents

BI 4.0 Qualification

user inboxes and personals documents BI 4.0 Qualification LCM BI 4.0 Production BI 4.0 Development ©
user inboxes and personals documents BI 4.0 Qualification LCM BI 4.0 Production BI 4.0 Development ©
user inboxes and personals documents BI 4.0 Qualification LCM BI 4.0 Production BI 4.0 Development ©

LCM

BI 4.0 Production

BI 4.0 Development

The right tool for the job in BI 4.0

Upgrade

Promotion

Upgrade Manager

LCM

Upgrade: “Transport and transform content from

previous version to newer version” Content includes all objects.

Improvement over previous releases: Now a unique and scalable tool dedicated to upgrade

Promotion: “Transport content from like system to

like system”

Systems are the same major version E.g. Dev to

Test to Production Content is primarily document templates and metadata and schedules. Not

document instances.

document templates and metadata and schedules. Not document instances. © 2011 SAP AG. All rights reserved.
document templates and metadata and schedules. Not document instances. © 2011 SAP AG. All rights reserved.

Systems running in parallel and connected

Upgrade Manager Live-to-Live Scenario

parallel and connected Upgrade Manager Live-to-Live Scenario Administrator running Upgrade Manager  Optimized for a

Administrator

running

Upgrade

Manager

Live-to-Live Scenario Administrator running Upgrade Manager  Optimized for a large amount of objects. No
Live-to-Live Scenario Administrator running Upgrade Manager  Optimized for a large amount of objects. No
Live-to-Live Scenario Administrator running Upgrade Manager  Optimized for a large amount of objects. No

Optimized for a large amount of objects. No intermediate step or

storage

2 ways (Incremental or Complete)

Required to have source and destination systems up and running

Ports must be opened between

source and destination

Upgrade Manager BIAR-to-Live Scenario

Upgrade Manager BIAR-to-Live Scenario BIAR file Previous version XI R2 or XI 3 Administrator running Upgrade

BIAR file Previous version XI R2 or XI 3

Scenario BIAR file Previous version XI R2 or XI 3 Administrator running Upgrade Manager  Needs

Administrator running Upgrade Manager

version XI R2 or XI 3 Administrator running Upgrade Manager  Needs to be used when
version XI R2 or XI 3 Administrator running Upgrade Manager  Needs to be used when

Needs to be used when the

previous and new systems

cannot be connected

Allows to keep a snapshot of the content and possibly re-start the

process from it

Use small BIAR (10,000 objects, 1Gb max recommended)

Basic Upgrade Workflow Demo - Full System

1 2 3 4 Choose Choose Get the the Upgrade summary scenario & enter of
1
2
3
4
Choose Choose Get the the Upgrade summary
scenario & enter
of what is going to
End
Complete Upgrade
credentials
be upgraded

Replaces Database

Migration in Central Configuration Manager

Easy, upgrade your

entire repository in 4

steps

Available in Windows GUI and Unix command

line

Basic Upgrade Workflow Demo - Staged

To perform an Incremental Upgrade: 1 2 3 4 5 Choose Upgrade Choose the Choose
To perform an Incremental Upgrade:
1
2
3
4
5
Choose Upgrade
Choose the
Choose objects to
Choose objects to
scenario & enter
End
Incremental Upgrade
copy & options
exclude & options
credentials

Take Away

Plan the upgrade

Upgrading is a demanding project. Need plan, milestones, backup and test strategies…

Platforms / Product changes

Platforms supported with BI 4.0 may be different from your existing system

Some features may be staged to a later BI 4 release / some products are deprecated or replaced

Content inventory and cleanup

Should you upgrade the all content or take the opportunity for some cleanup? Upgrading content that is not needed just increases risks and time to upgrade

Full system versus Staged upgrade

Shutdown the production system and upgrade it all or upgrade one application / group at a time

Validate the upgrade

Identify what needs to tested and execute a relevant testing campaign

upgrade Identify what needs to tested and execute a relevant testing campaign © 2011 SAP AG.

Appendix

Appendix

Product Changes - Parameters and Customization

XI R2 / XI 3.1

BI 4.0

 

Upgrade Considerations

Security and Authentication

To be set up in BI 4.0

No upgrade

settings

 

(AD / LDAP / SSL / SAP)

Reporting databases connectivity

To be set up in BI 4.0

No upgrade

BOE Server configuration

To be set up in BI 4.0

No upgrade

settings

 

Web Application configuration settings

To be set up in BI 4.0

No upgrade. BOE specific settings moved from

Web.xml file to properties file.

InfoView Customization (picture,

To be set up in BI 4.0

No upgrade

logo, …)

Custom Java code using the

 

Need to validate your custom code will still work

BOE SDK and Report Engine SDK

in BI 4.0. Some of the Java functions can be deprecated.

No Longer Supported (PAR)

Checked if your version are still supported?

OS

Application Server

CMS repository database

Reporting Databases connectivity

Third parties as / infrastructure like « reverse proxy, Authentication model , JVM…»

Go to : BusinessObjects Product Availability Report (PAR)

http://service.sap.com/support -> Help & Support -> SAP BusinessObjects Support -> Supported platform documents

Auditing

Overview

Keep your XI 3.1 audit data and do reporting from BI 4.0 on it. And upgrade XI 3.x

universes and reports.

Audit solutions that use the XI 3.x audit schema :

Keep existing XI 3.x audit database for historical data

Move the XI 3.x audit application (universe + reports) into the new system

Start BI 4.0 with a fresh BI 4.0 audit database

Install the BI 4.0 sample audit universe and reports (found on the web site)

Customize the samples or re-develop reports to match XI 3.x and BI 4.0 needs

If continuity is needed: Create a multi-source universe and appropriate reports to get audit

continuity before and after the upgrade

Desktop Intelligence

Overview

Desktop Intelligence documents will no longer be available in BI 4.0 CMS.

How to convert Desktop Intelligence Document :

Desktop Intelligence to Web Intelligence (convert with RCT)

New XIR2 & XI 3 Desktop Intelligence Features converted with RCT 4.0

Query on Query

Fold/Unfold

Show/Hide

Fit to page

Desktop Intelligence & Report Conversion Tool

Desktop Intelligence documents will no longer be available in BI 4.0 CMS.

The only way for a user to bring Desktop Intelligence content is:

CMS XI 3.x Deski report
CMS XI 3.x
Deski
report
Use XI 3.1 RCT to convert Deski to Webi report on the same stack
Use XI 3.1 RCT
to convert Deski to Webi
report on the same stack
Use BI 4.0 RCT to convert Deski to Webi report & to publish it into
Use BI 4.0 RCT
to convert Deski to Webi
report & to publish it into
BI 4.0 system.
CMS XI 3.x Webi report
CMS XI 3.x
Webi
report
Use BI 4.0 Upgrade Manager to promote content
Use BI 4.0 Upgrade
Manager to promote
content
CMS BI 4.0 Webi report
CMS BI 4.0
Webi
report

Link to UNV is preserved

CUID stay the same

Thank You!

Thank You!