Sap business objects 4.0   migration best practices
Upcoming SlideShare
Loading in...5
×
 

Sap business objects 4.0 migration best practices

on

  • 4,015 views

 

Statistics

Views

Total Views
4,015
Views on SlideShare
4,015
Embed Views
0

Actions

Likes
0
Downloads
92
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Sap business objects 4.0   migration best practices Sap business objects 4.0 migration best practices Presentation Transcript

  • Best Practices and Methodologies for Upgrading SAPBusinessObjects Enterprise to SAP BusinessObjects BI 4.0
  • DisclaimerThis presentation outlines our general product direction and should not be relied on inmaking a purchase decision. This presentation is not subject to your license agreementor any other agreement with SAP. SAP has no obligation to pursue any course ofbusiness outlined in this presentation or to develop or release any functionalitymentioned in this presentation. This presentation and SAPs strategy and possible futuredevelopments are subject to change and may be changed by SAP at any time for anyreason without notice. This document is provided without a warranty of any kind, eitherexpress or implied, including but not limited to, the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement. SAP assumes noresponsibility for errors or omissions in this document, except if such damages werecaused by SAP intentionally or grossly negligent. © 2011 SAP AG. All rights reserved. 2
  • AgendaUpgrade Overview and ConceptsUpgrade Best PracticesTechnical ImplementationAppendix© 2011 SAP AG. All rights reserved. 3
  • Upgrade Overview and Concepts
  • Why Upgrading? • Better integration with SAP BW Data access • New dimensional semantic layer • Multi-source universes • Harmonized user experience across the suite Usability / Productivity • Interoperability • Advanced analytical insight • Brand new search capability • Integrated platform monitoring Cost of Ownership • Advanced auditing capabilities • Supportability and root-cause analysis • 64 bits server architecture© 2011 SAP AG. All rights reserved. 5
  • Planning your UpgradeTypical Upgrade TimelineMilestone 1 M2 M3 Considerations before M4 upgrading  Assessment – magnitude of project Planning  Time and Deadlines  Resources (IT/HW) Design Down time  Training Implementation  Backup Cutover Go Live© 2011 SAP AG. All rights reserved. 6
  • Checklist - System ConsiderationsPlatforms Review each component ofPlatforms supported with BI 4 change the landscape to define theArchitecture changes - servers are now 64 bits only appropriate strategyVersion upgrade path Recommendations areNewer systems have a direct upgrade path provided in this presentationOlder systems may require extra stepsProduct Changes Understand the upgradeSome features may be staged to a later BI 4 release path for each product youSome products are deprecated or replaced are usingParameters and customization Capture all parameters and customization to understandNot automatically upgraded what it means to the new system© 2011 SAP AG. All rights reserved. 7
  • Checklist - Content ConsiderationsSecurity upgrade Review your optionsShould you carry over the existing users and associated and needs. Details insecurity ? Should you take the opportunity to do some this deck.redesign ? Recommendation to atContent inventory and cleanup least do some cleanupShould you upgrade the all content or take the opportunity before upgradingfor some cleanup?Full system vs Staged upgrade Review the pros andUpgrade the entire system cons depending on your own constraintsOr upgrade one department / group at a timeAcceptance / Validation Obviously yes! Test your upgrade on aShould you test the upgrade process? sandbox© 2011 SAP AG. All rights reserved. 8
  • Upgrade Best Practices
  • Versions Upgrade PathNo direct UpgradeGo first to XI R2 or XI 3.x BOE XI R2 Direct Upgrade using BI 4.0 “Upgrade Manager Tool” BOE XI 3.x BOE XI CE8 / CE9 / CE10 BOE stands for BusinessObjects Enterprise. BO 5 / BO6 BI stands for Business Intelligence CE for Crystal Enterprise. © 2011 SAP AG. All rights reserved. 10
  • Product Changes - BI Platform Components XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsBinaries New binaries  The full landscape has to be re-installedAudit New audit schema  Historical audit data is not kept. Need to plan for a workaroundInfoView BI Launch Pad  New interface  Report pinningDashboard Builder BI Workspace  Corporate, Personal and My InfoView Dashboards become BI Workspaces but some analytics must be recreated in XcelsiusEncyclopedia / End of Life  No upgradeDiscussionPerformance End of Life  No upgrademanagerSearch New search technology  The search index will be re-built in BI 4.0 © 2011 SAP AG. All rights reserved. 11
  • Product Changes - BI Clients XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsCrystal Reports CR 2011 and CR Enterprise  All reports are by default upgraded to CR 2011  Possible manual upgrade to CR EnterpriseDesktop Intelligence End Of Life  Report Conversion Tool converts into Web Intelligence format prior or after the upgradeXcelsius 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 changesWeb Intelligence Web Intelligence  Fully upgradedWeb Intelligence SDK No Web Intelligence  Wait until full support and availability of Interactive SDK support Analysis (REBEAN) SDK in a later release © 2011 SAP AG. All rights reserved. 12
  • Product Changes - BI Clients - Semantic Layer XIR2 / XI 3.1 BI 4.0 Upgrade ConsiderationsUniverse Designer - No change  None, universes and designer as in XI 3.xUNV formatn/a Information Designer –  Relational UNV can be converted to UNX UNX format  OLAP UNV have to be re-created in UNX (future version will support conversion) © 2011 SAP AG. All rights reserved. 13
  • Product Changes - Tools XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsLCM (XI 3.1 only) Integrated in BI 4.0  No separate installation requiredReport Conversion No Change  Same feature than XI 3.1 with the support of the Online to Online modeTranslation Manager Integrated in BI 4.0 client  Parity of features with XI 3.1 is maintained tools  All translations previously done will be retainedWDeploy Integrated in BI 4.0  WDeploy GUI available Import Wizard Upgrade Manager  New tool. More details in this presentation © 2011 SAP AG. All rights reserved. 14
  • Product Changes - Other Components XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsIntegration Kits Integrated in BI 4.0  No separate installation required for SAP, PeopleSoft, Siebel, JDEdwards, OracleIntegration Kit Not available  No upgrade : wait for availability in a later release for SharePointData Federator Partially integrated in BI 4.0  Existing DF 3.x deployments remain compatible with BI 4.0Live Office No change  Existing documents will continue to work  Need to update client machinesMobile 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 copiedQuery as a Web No change  QaaWS will continue to workService  Upgrade Manager will detect dependencies to universes (UNV)(QaaWS)  Dashboards on QaaWS will continue to work © 2011 SAP AG. All rights reserved. 15
  • Security Upgrade XI R2  BI 4.0 XI 3.x  BI 4.0 Continuity + new features have been Security model is the same as the added since XI R2 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 Specify the new “owner right” for existing products existing products  Specify rights with new products  Specify rights with new products (WRC, IDT, LCM, etc) (IDT, LCM, etc )  Simplify your security model by :  creating Custom Access Level  using selective enforcement of rights (Objects or Sub Object)© 2011 SAP AG. All rights reserved. 16
  • Content Inventory and Cleanup Project & Risk control Governance Upgrading content that is not Limiting the proliferation of needed increases risks and time to universes and reports allows the Repository upgrade business to be more efficient Diagnostic Tool Instance Manager / CMC ■ Fix or delete scheduled jobs that are paused or failed Auditing ■ Detect and delete un-used reports after checking with users Upgrade ■ Remove older report instances or un-used instances Management Tool ■ Fix repository inconsistencies© 2011 SAP AG. All rights reserved. 17
  • Special content typeInboxes • Upgraded with the userPersonal Documents • Possible to opt-out • Come with the reportReports Instances • Option in Upgrade Management Tool not to import themScheduler Jobs • Automatically carried over with the scheduled report© 2011 SAP AG. All rights reserved. 18
  • Full System vs Staged UpgradeFull / One Shot Upgrade Stage / Incremental Upgrade per department Upgrade all content at once  Upgrade content in stages Only 1 system to maintain  2 systems to maintain Requires lockdown of the entire  Requires lockdown of department foldersystem  Issues affect only the department Issues affect the entire system upgraded Long downtime  Short downtime Simpler (less options)© 2011 SAP AG. All rights reserved. 19
  • Full System vs Staged Upgrade Small and simple deployment Full / One shot upgrade Larger shared services deployments Do you have a pre-prod No to validate the upgrade ? Staged / Ye Incremental s upgrade Can you afford a longer recommended No downtime ? Yes Perform upgrade tests Full / One shot upgrade to evaluate the expected downtime© 2011 SAP AG. All rights reserved. 20
  • 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. 21
  • Staged Upgrade ConsiderationsTo 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© 2011 SAP AG. All rights reserved. 22
  • Acceptance / Validation In Place On a Sandbox Acceptance process right As part of the planning after the actual upgrade and discover process to the TEST system  Products features and  Products features and functions functions  Security model  Compatibility with existing ■ critical folder & groups ■ top 10 most used systems  Estimate time to upgrade  BI Content ■ 50 documents most frequently used  Success of the content ■ 50 documents with longest refresh time upgrade (users, security, ■ 5 most critical documents for power users and VIPs (Inboxes / Personals / universes, reports…) Public Folders) ■ 10 universes most frequently used© 2011 SAP AG. All rights reserved. 23
  • Technical Implementation
  • Solution ArchitectureThe general BI 4.0 architecture hasn’t changed compare to XI R2 and XI 3 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© 2011 SAP AG. All rights reserved. 25
  • Architecture Upgrade - OverviewMain steps Setup the new landscape with the new software version Move the BI content from the existing system to the new one © 2011 SAP AG. All rights reserved. 26
  • Architecture Upgrade - Implementation Previous (Xir2 or Xi3.1) system Existing BOE XI R2 Existing BOE XI R2 Existing BOE XI R2 or XI 3 environment or XI 3 environment or XI 3 environment 1 Upgrade the BOE New BOE BI 4.0 3 content (live to live) BI 4.0 system environment New BOE BI 4.0 environment 2 Installation and configuration of third parties and customization 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© 2011 SAP AG. All rights reserved. 27
  • 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 LCM LCM or IW or IW Previous (XI R2 / XI 3.x) Previous (XI R2 / XI 3.x) Previous (XI R2 / XI 3.x) Development Qualification Production * Upgrade Manager * In BI 4.0, LCM does not move BI 4.0 Qualification document instances, user inboxes and personals documents LCM LCM * BI 4.0 Production BI 4.0 Development © 2011 SAP AG. All rights reserved. 28
  • The right tool for the job in BI 4.0 Upgrade PromotionUpgrade Manager LCMUpgrade: “Transport and transform content from Promotion: “Transport content from like system toprevious version to newer version” Content includes like system”all objects. Systems are the same major version E.g. Dev toImprovement over previous releases: Now a unique Test to Production Content is primarily documentand scalable tool dedicated to upgrade templates and metadata and schedules. Not document instances.© 2011 SAP AG. All rights reserved. 29
  • Upgrade Manager Live-to-Live Scenario  Optimized for a large amount of objects. No intermediate step or storage Systems running in parallel and connected  2 ways (Incremental or Complete)  Required to have source and Administrator destination systems up and running running Upgrade Manager  Ports must be opened between source and destination© 2011 SAP AG. All rights reserved. 30
  • Upgrade Manager BIAR-to-Live Scenario  Needs to be used when the previous and new systems BIAR file cannot be connected Previous version XI R2 or XI 3  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)Administratorrunning UpgradeManager© 2011 SAP AG. All rights reserved. 31
  • Basic Upgrade Workflow Demo - Full System  Replaces Database Migration in Central Configuration Manager  Easy, upgrade your entire repository in 4 steps 1 2 34  Available in Windows GUI and Unix command line Choose the summary Get UpgradeChoose the is going to of what scenario & enter EndComplete Upgrade be upgraded credentials © 2011 SAP AG. All rights reserved. 32
  • Basic Upgrade Workflow Demo - Staged To perform an Incremental Upgrade: 1 2 3 4 5 Choose Upgrade Choose the Choose objects to to Choose objects enter End scenario & exclude & options Incremental copy & options Upgrade credentials© 2011 SAP AG. All rights reserved. 33
  • 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© 2011 SAP AG. All rights reserved. 34
  • Appendix
  • Product Changes - Parameters and Customization XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsSecurity and Authentication To be set up in BI 4.0  No upgradesettings(AD / LDAP / SSL / SAP)Reporting databases To be set up in BI 4.0  No upgradeconnectivityBOE Server configuration To be set up in BI 4.0  No upgradesettingsWeb Application configuration To be set up in BI 4.0  No upgrade. BOE specific settings moved fromsettings Web.xml file to properties file.InfoView Customization (picture, To be set up in BI 4.0  No upgradelogo, …)Custom Java code using the  Need to validate your custom code will still workBOE SDK and Report Engine in BI 4.0. Some of the Java functions can be deprecated.SDK © 2011 SAP AG. All rights reserved. 36
  • 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© 2011 SAP AG. All rights reserved. 37
  • AuditingOverview 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© 2011 SAP AG. All rights reserved. 38
  • Desktop IntelligenceOverview 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 convertedwith RCT 4.0 Query on Query Fold/Unfold Show/Hide Fit to page© 2011 SAP AG. All rights reserved. 39
  • 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: Use XI 3.1 RCT to convert Deski to Webi report on the same stack CMS XI 3.x CMS XI 3.x Deski Webi report report Use BI 4.0 Upgrade Manager to promote content Use BI 4.0 RCT CMS BI 4.0 to convert Deski to Webi Webi report & to publish it into report BI 4.0 system.  Link to UNV is preserved  CUID stay the same© 2011 SAP AG. All rights reserved. 40
  • Thank You!