BO4 SAMPLE MIGRATION PLAN By Sergei Peleshuk February 2013

Transcription

BO4 SAMPLE MIGRATION PLAN By Sergei Peleshuk February 2013
BO4 SAMPLE MIGRATION
PLAN
By Sergei Peleshuk
February 2013
www.biportal.org
www.biportal.org
| 2
BO/BW Development Principles
• BO Universes and BEx Queries go through the cycle:
• Dev → Test → Preprod → Prod
• Universes and Bex queries will be developed in Dev, tested in Test
and when approved transported to Preprod and Prod environments
• Webi reports in Test will be used for testing Universes
• BO reports go through the cycle:
• Preprod → Prod
• BO Preprod will connect to BW Prod data
• Presentation layer reports, dashboards, analysis workbooks and
information spaces will be developed and tested in BO Preprod
and, when approved, promoted to BO Prod
• Regional BO objects are promoted to BO Prod by Regional IT;
Local objects by Local IT
www.biportal.org
| 3
Development Cycle
Key users
develop/test
Local BEx queries
Regional BEx queries
Key users
develop
End users
develop/test/use
test
(not used)
use
BW 7.3
Sandbox
Dev
Test
Preprod
Prod
Sandbox
Dev
Test
Preprod
Prod
Perf. test
use
develop / test
use
BO4
Universes & BO Analysis
workbooks (Regional)
Presentation layer
(WebI Reports, Crystal Reports,
Dashboards, Analysis Workbooks,
BO Explorer Information Spaces)
develop
test
Test Universes
with Webi
1. Upgrade to BO4 sandbox
• Provide Local IT Key users with the new tools
and accounts needed to work in the new BO4
environments
• Migrate BO2/3 Universes to a BO4 sandbox
environment
• Adapt Universes (if any)
• Ensure the most important reports still return
correct results
BO4 Migration Overview
Use BO4
Upgrade Manager
BO XI Rx
CMS
BO4 CMS
Sandbox
Use BO4 life cycle
management
BO4 CMS
Development
BO4 CMS
Staging
Use BO4 life cycle
management
BO4 CMS
Pre Prod
Use BO4 life cycle
management
BO4 CMS
Prod
Use BO4 life cycle
management
2. Adjust procedures, prepare for UAT
• Align Local Data Warehouses with BO4
environments.
• Align Local Release procedures with BO4
Lifecycle Management
• Promote Universes to all non-Production
environments.
• Test and adjust the most important reports
• Prepare Production environment
3. Business validation
• Validate all Business Critical Reports
• Introduce corrections to reports if needed
• Obtain final GO
4. Move to Production
• Promote reports to BO4 Prod
• Provide users access to the BO4 Prod
environment
• Reconciliation step
• Disable access to the old BO environments
• Assist Users with migration
• Postproduction support
Non SAP Landscape Example
Environment
SQL Database
BO4
Production
Production
Prod
PreProduction
Pre-Prod
Role
•Refresh of validated reports
•Bursting / Scheduling
•Ad Hoc reporting
•Report Development
•Functionnal Testing
Staging
Development
Staging
Dev
Staging
Dev
•Universe development
•Technical testing
Roles & Responsibilities
• Local IT
• Promotion of Local reports to Production
• Local Universe and Local Data Warehouse development
• User Support and guidance
• Regional BO4 Administrators
• Promotion of Universe to Production
• Upgrade Universes from BO2 to BO4 (one shot)
• Availability of different BO4 environments
• Providing development tools
• User Account Management