0
Best Practices and Methodologies for Upgrading SAPBusinessObjects Enterprise to SAP BusinessObjects BI 4.0
© 2011 SAP AG. All rights reserved. 2DisclaimerThis presentation outlines our general product direction and should not be ...
© 2011 SAP AG. All rights reserved. 3AgendaUpgrade Overview and ConceptsUpgrade Best PracticesTechnical ImplementationAppe...
Upgrade Overview and Concepts
© 2011 SAP AG. All rights reserved. 5Why Upgrading?• Harmonized user experience across the suite• Interoperability• Advanc...
© 2011 SAP AG. All rights reserved. 6Planning your UpgradeMilestone 1 M2 M3 M4PlanningDesignImplementationCutoverGo LiveTy...
© 2011 SAP AG. All rights reserved. 7Understand the upgradepath for each product youare usingChecklist - System Considerat...
© 2011 SAP AG. All rights reserved. 8Review your optionsand needs. Details inthis deck.Checklist - Content ConsiderationsS...
Upgrade Best Practices
© 2011 SAP AG. All rights reserved. 10Versions Upgrade PathBOE stands for BusinessObjects Enterprise.BI stands for Busines...
© 2011 SAP AG. All rights reserved. 11Product Changes - BI Platform ComponentsXI R2 / XI 3.1 BI 4.0 Upgrade Considerations...
© 2011 SAP AG. All rights reserved. 12Product Changes - BI ClientsXI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsCrystal Repo...
© 2011 SAP AG. All rights reserved. 13XIR2 / XI 3.1 BI 4.0 Upgrade ConsiderationsUniverse Designer -UNV formatNo change  ...
© 2011 SAP AG. All rights reserved. 14XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsLCM (XI 3.1 only) Integrated in BI 4.0 ...
© 2011 SAP AG. All rights reserved. 15Product Changes - Other ComponentsXI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsIntegr...
© 2011 SAP AG. All rights reserved. 16Security UpgradeXI R2  BI 4.0Continuity + new features have beenadded since XI R2XI...
© 2011 SAP AG. All rights reserved. 17Content Inventory and CleanupProject & Risk controlUpgrading content that is notneed...
© 2011 SAP AG. All rights reserved. 18Special content type• Come with the report• Option in Upgrade Management Tool not to...
© 2011 SAP AG. All rights reserved. 19Full / One Shot Upgrade Upgrade all content at once Only 1 system to maintain Req...
© 2011 SAP AG. All rights reserved. 20Full System vs Staged UpgradeSmall and simple deploymentLarger shared services deplo...
© 2011 SAP AG. All rights reserved. 21Full System Upgrade ConsiderationsNo lockdown or read only options available in BOET...
© 2011 SAP AG. All rights reserved. 22Staged Upgrade ConsiderationsTo lockdown a department folder, modify folder rights:...
© 2011 SAP AG. All rights reserved. 23Acceptance / ValidationOn a SandboxAs part of the planningand discover processIn Pla...
Technical Implementation
© 2011 SAP AG. All rights reserved. 25Solution ArchitectureThe general BI 4.0 architecture hasn’t changed compare to XI R2...
© 2011 SAP AG. All rights reserved. 26Architecture Upgrade - OverviewMain steps Setup the new landscape with the new soft...
© 2011 SAP AG. All rights reserved. 27Existing BOE XI R2or XI 3 environmentNew BOE BI 4.0environmentInstallation and confi...
© 2011 SAP AG. All rights reserved. 28Upgrade Considerations (DEV/ QUAL / PROD) Best practice: upgrade from previous vers...
© 2011 SAP AG. All rights reserved. 29Upgrade PromotionUpgrade Manager LCMUpgrade: “Transport and transform content frompr...
© 2011 SAP AG. All rights reserved. 30AdministratorrunningUpgradeManagerUpgrade Manager Live-to-Live Scenario Optimized f...
© 2011 SAP AG. All rights reserved. 31BIAR filePrevious versionXI R2 or XI 3Administratorrunning UpgradeManagerUpgrade Man...
© 2011 SAP AG. All rights reserved. 32Choose theComplete Upgrade1 Replaces DatabaseMigration in CentralConfiguration Mana...
© 2011 SAP AG. All rights reserved. 33To perform an Incremental Upgrade:Basic Upgrade Workflow Demo - StagedChoose theIncr...
© 2011 SAP AG. All rights reserved. 34Take AwayPlan the upgradeUpgrading is a demanding project. Need plan, milestones, ba...
Appendix
© 2011 SAP AG. All rights reserved. 36XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsSecurity and Authenticationsettings(AD /...
© 2011 SAP AG. All rights reserved. 37No Longer Supported (PAR)Checked if your version are still supported? OS Applicati...
© 2011 SAP AG. All rights reserved. 38AuditingOverview Keep your XI 3.1 audit data and do reporting from BI 4.0 on it. An...
© 2011 SAP AG. All rights reserved. 39Desktop IntelligenceOverview Desktop Intelligence documents will no longer be avail...
© 2011 SAP AG. All rights reserved. 40Desktop Intelligence & Report Conversion Tool Desktop Intelligence documents will n...
Thank You!
Upcoming SlideShare
Loading in...5
×

Sap business objects 4.0 migration best practices

560

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
560
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
41
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Sap business objects 4.0 migration best practices"

  1. 1. Best Practices and Methodologies for Upgrading SAPBusinessObjects Enterprise to SAP BusinessObjects BI 4.0
  2. 2. © 2011 SAP AG. All rights reserved. 2DisclaimerThis 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.
  3. 3. © 2011 SAP AG. All rights reserved. 3AgendaUpgrade Overview and ConceptsUpgrade Best PracticesTechnical ImplementationAppendix
  4. 4. Upgrade Overview and Concepts
  5. 5. © 2011 SAP AG. All rights reserved. 5Why Upgrading?• Harmonized user experience across the suite• Interoperability• Advanced analytical insight• Brand new search capabilityUsability / Productivity• Integrated platform monitoring• Advanced auditing capabilities• Supportability and root-cause analysis• 64 bits server architectureCost of Ownership• Better integration with SAP BW• New dimensional semantic layer• Multi-source universesData access
  6. 6. © 2011 SAP AG. All rights reserved. 6Planning your UpgradeMilestone 1 M2 M3 M4PlanningDesignImplementationCutoverGo LiveTypical Upgrade TimelineConsiderations beforeupgrading Assessment – magnitude of project Time and Deadlines Resources (IT/HW)Down time Training Backup
  7. 7. © 2011 SAP AG. All rights reserved. 7Understand the upgradepath for each product youare usingChecklist - System ConsiderationsPlatformsPlatforms supported with BI 4 changeArchitecture changes - servers are now 64 bits onlyVersion upgrade pathNewer systems have a direct upgrade pathOlder systems may require extra stepsProduct ChangesSome features may be staged to a later BI 4 releaseSome products are deprecated or replacedParameters and customizationNot automatically upgradedReview each component ofthe landscape to define theappropriate strategyRecommendations areprovided in this presentationCapture all parameters andcustomization to understandwhat it means to the newsystem
  8. 8. © 2011 SAP AG. All rights reserved. 8Review your optionsand needs. Details inthis deck.Checklist - Content ConsiderationsSecurity upgradeShould you carry over the existing users and associatedsecurity ? Should you take the opportunity to do someredesign ?Content inventory and cleanupShould you upgrade the all content or take the opportunityfor some cleanup?Full system vs Staged upgradeUpgrade the entire systemOr upgrade one department / group at a timeAcceptance / ValidationShould you test the upgrade process?Review the pros andcons depending onyour own constraintsRecommendation to atleast do some cleanupbefore upgradingObviously yes! Testyour upgrade on asandbox
  9. 9. Upgrade Best Practices
  10. 10. © 2011 SAP AG. All rights reserved. 10Versions Upgrade PathBOE stands for BusinessObjects Enterprise.BI stands for Business IntelligenceCE for Crystal Enterprise.BI 4.0Direct Upgrade using“Upgrade Manager Tool”BOE XI 3.xBOE XI R2BO 5 / BO6BOE XICE8 / CE9 /CE10No direct UpgradeGo first to XI R2 or XI 3.x
  11. 11. © 2011 SAP AG. All rights reserved. 11Product Changes - BI Platform ComponentsXI 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 fora workaroundInfoView BI Launch Pad  New interface Report pinningDashboard Builder BI Workspace  Corporate, Personal and My InfoViewDashboards become BI Workspaces but someanalytics must be recreated in XcelsiusEncyclopedia /DiscussionEnd of Life  No upgradePerformancemanagerEnd of Life  No upgradeSearch New search technology  The search index will be re-built in BI 4.0
  12. 12. © 2011 SAP AG. All rights reserved. 12Product Changes - BI ClientsXI 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 Intelligenceformat prior or after the upgradeXcelsius 2008 Dashboards  Flash files will continue to work Conversion to new format is optional Conversion adds new features (globalization, UNXqueries…)Explorer No UNV support  Information Spaces based on Excel are upgraded, theones based on UNV and bookmarks are not !Voyager Analysis, edition for OLAP  Some of workspaces will be upgrade to AdvancedAnalysis, the others require manual changesWeb Intelligence Web Intelligence  Fully upgradedWeb Intelligence SDK No Web IntelligenceSDK support Wait until full support and availability of InteractiveAnalysis (REBEAN) SDK in a later release
  13. 13. © 2011 SAP AG. All rights reserved. 13XIR2 / XI 3.1 BI 4.0 Upgrade ConsiderationsUniverse Designer -UNV formatNo change  None, universes and designer as in XI 3.xn/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 - BI Clients - Semantic Layer
  14. 14. © 2011 SAP AG. All rights reserved. 14XI 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 supportof the Online to Online modeTranslation Manager Integrated in BI 4.0 clienttools Parity of features with XI 3.1 is maintained All translations previously done will beretainedWDeploy Integrated in BI 4.0  WDeploy GUI availableImport Wizard Upgrade Manager  New tool. More details in this presentationProduct Changes - Tools
  15. 15. © 2011 SAP AG. All rights reserved. 15Product Changes - Other ComponentsXI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsIntegration Kitsfor SAP, PeopleSoft,Siebel, JDEdwards,OracleIntegrated in BI 4.0  No separate installation requiredIntegration Kitfor SharePointNot available  No upgrade : wait for availability in a later releaseData Federator Partially integrated in BI 4.0  Existing DF 3.x deployments remain compatible withBI 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 thedevice) Parameters to be re-set or copiedQuery as a WebService(QaaWS)No change  QaaWS will continue to work Upgrade Manager will detect dependencies touniverses (UNV) Dashboards on QaaWS will continue to work
  16. 16. © 2011 SAP AG. All rights reserved. 16Security UpgradeXI R2  BI 4.0Continuity + new features have beenadded since XI R2XI 3.x  BI 4.0Security model is the same as theone of XI 3Set up rights at the root folderSpecify the new “owner right” forexisting products Specify rights with new products(WRC, IDT, LCM, etc) Simplify your security model by : creating Custom Access Level using selective enforcement ofrights (Objects or Sub Object)Specify the new “owner right” forexisting products Specify rights with new products(IDT, LCM, etc )In BI 4.0 you have to : In BI 4.0 you have to :
  17. 17. © 2011 SAP AG. All rights reserved. 17Content Inventory and CleanupProject & Risk controlUpgrading content that is notneeded increases risks and time toupgradeGovernanceLimiting the proliferation ofuniverses and reports allows thebusiness to be more efficient■ 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 inconsistenciesRepositoryDiagnostic ToolInstanceManager / CMCAuditingUpgradeManagement Tool
  18. 18. © 2011 SAP AG. All rights reserved. 18Special content type• Come with the report• Option in Upgrade Management Tool not to importthemReports Instances• Automatically carried over with the scheduledreportScheduler Jobs• Upgraded with the user• Possible to opt-outInboxesPersonal Documents
  19. 19. © 2011 SAP AG. All rights reserved. 19Full / One Shot Upgrade Upgrade all content at once Only 1 system to maintain Requires lockdown of the entiresystem Issues affect the entire system Long downtime Simpler (less options)Stage / Incremental Upgrade per department Upgrade content in stages 2 systems to maintain Requires lockdown of department folder Issues affect only the departmentupgraded Short downtimeFull System vs Staged Upgrade
  20. 20. © 2011 SAP AG. All rights reserved. 20Full System vs Staged UpgradeSmall and simple deploymentLarger shared services deploymentsFull / One shot upgradeNoDo you have a pre-prodto validate the upgrade? Staged /IncrementalupgraderecommendedYesCan you afford a longerdowntime ?NoYesFull / One shot upgradePerform upgrade teststo evaluate theexpected downtime
  21. 21. © 2011 SAP AG. All rights reserved. 21Full System Upgrade ConsiderationsNo lockdown or read only options available in BOETo lockdown a BOE system:1. Shutdown your application server2. 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
  22. 22. © 2011 SAP AG. All rights reserved. 22Staged 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
  23. 23. © 2011 SAP AG. All rights reserved. 23Acceptance / ValidationOn a SandboxAs part of the planningand discover processIn PlaceAcceptance process rightafter the actual upgradeto the TEST system Products features andfunctions Compatibility with existingsystems Estimate time to upgrade Success of the contentupgrade (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 powerusers and VIPs (Inboxes / Personals /Public Folders)■ 10 universes most frequently used
  24. 24. Technical Implementation
  25. 25. © 2011 SAP AG. All rights reserved. 25Solution ArchitectureThe general BI 4.0 architecture hasn’t changed compare to XI R2 and XI 35 main components Web Application Server Back-end Servers 1 Central Management System(CMS) database (infoobjects) 1 File Repository (physical reportsrepository) 1 Audit Database
  26. 26. © 2011 SAP AG. All rights reserved. 26Architecture Upgrade - OverviewMain steps Setup the new landscape with the new software version Move the BI content from the existing system to the new one
  27. 27. © 2011 SAP AG. All rights reserved. 27Existing BOE XI R2or XI 3 environmentNew BOE BI 4.0environmentInstallation and configuration ofthird parties and customizationTime123Previous(Xir2orXi3.1)systemBI4.0systemUpgrade the BOEcontent (live to live)New BOE BI 4.0environmentArchitecture Upgrade - Implementation 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 serverExisting BOE XI R2or XI 3 environmentExisting BOE XI R2or XI 3 environment
  28. 28. © 2011 SAP AG. All rights reserved. 28Upgrade 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 ProductionPrevious (XI R2 / XI 3.x)DevelopmentPrevious (XI R2 / XI 3.x)QualificationPrevious (XI R2 / XI 3.x)ProductionLCMor IWLCMor IWBI 4.0 DevelopmentBI 4.0 QualificationBI 4.0 ProductionLCM **UpgradeManagerLCM* In BI 4.0, LCM does not movedocument instances, user inboxesand personals documents
  29. 29. © 2011 SAP AG. All rights reserved. 29Upgrade PromotionUpgrade Manager LCMUpgrade: “Transport and transform content fromprevious version to newer version” Content includesall objects.Improvement over previous releases: Now a uniqueand scalable tool dedicated to upgradePromotion: “Transport content from like system tolike system”Systems are the same major version E.g. Dev toTest to Production Content is primarily documenttemplates and metadata and schedules. Notdocument instances.The right tool for the job in BI 4.0
  30. 30. © 2011 SAP AG. All rights reserved. 30AdministratorrunningUpgradeManagerUpgrade Manager Live-to-Live Scenario Optimized for a large amount ofobjects. No intermediate step orstorage 2 ways (Incremental or Complete) Required to have source anddestination systems up and running Ports must be opened betweensource and destinationSystemsrunninginparallelandconnected
  31. 31. © 2011 SAP AG. All rights reserved. 31BIAR filePrevious versionXI R2 or XI 3Administratorrunning UpgradeManagerUpgrade Manager BIAR-to-Live Scenario Needs to be used when theprevious and new systemscannot be connected Allows to keep a snapshot of thecontent and possibly re-start theprocess from it Use small BIAR (10,000 objects,1Gb max recommended)
  32. 32. © 2011 SAP AG. All rights reserved. 32Choose theComplete Upgrade1 Replaces DatabaseMigration in CentralConfiguration Manager Easy, upgrade yourentire repository in 4steps Available in WindowsGUI and Unix commandlineBasic Upgrade Workflow Demo - Full SystemChoose Upgradescenario & entercredentials2Get the summaryof what is going tobe upgraded3End4
  33. 33. © 2011 SAP AG. All rights reserved. 33To perform an Incremental Upgrade:Basic Upgrade Workflow Demo - StagedChoose theIncremental Upgrade1 2Choose Upgradescenario & entercredentials3Choose objects tocopy & optionsChoose objects toexclude & options4 5End
  34. 34. © 2011 SAP AG. All rights reserved. 34Take AwayPlan the upgradeUpgrading is a demanding project. Need plan, milestones, backup and test strategies…Platforms / Product changesPlatforms supported with BI 4.0 may be different from your existing systemSome features may be staged to a later BI 4 release / some products are deprecated or replacedContent inventory and cleanupShould you upgrade the all content or take the opportunity for some cleanup?Upgrading content that is not needed just increases risks and time to upgradeFull system versus Staged upgradeShutdown the production system and upgrade it all or upgrade one application / group at a timeValidate the upgradeIdentify what needs to tested and execute a relevant testing campaign
  35. 35. Appendix
  36. 36. © 2011 SAP AG. All rights reserved. 36XI R2 / XI 3.1 BI 4.0 Upgrade ConsiderationsSecurity and Authenticationsettings(AD / LDAP / SSL / SAP)To be set up in BI 4.0  No upgradeReporting databasesconnectivityTo be set up in BI 4.0  No upgradeBOE Server configurationsettingsTo be set up in BI 4.0  No upgradeWeb Application configurationsettingsTo be set up in BI 4.0  No upgrade. BOE specific settings moved fromWeb.xml file to properties file.InfoView Customization (picture,logo, …)To be set up in BI 4.0  No upgradeCustom Java code using theBOE SDK and Report EngineSDK Need to validate your custom code will still workin BI 4.0. Some of the Java functions can bedeprecated.Product Changes - Parameters and Customization
  37. 37. © 2011 SAP AG. All rights reserved. 37No 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
  38. 38. © 2011 SAP AG. All rights reserved. 38AuditingOverview Keep your XI 3.1 audit data and do reporting from BI 4.0 on it. And upgrade XI 3.xuniverses 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 auditcontinuity before and after the upgrade
  39. 39. © 2011 SAP AG. All rights reserved. 39Desktop 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
  40. 40. © 2011 SAP AG. All rights reserved. 40Desktop 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.xDeskireportCMS XI 3.xWebireportUse XI 3.1 RCTto convert Deski to Webireport on the same stackCMS BI 4.0WebireportUse BI 4.0 UpgradeManager to promotecontentUse BI 4.0 RCTto convert Deski to Webireport & to publish it intoBI 4.0 system. Link to UNV is preserved CUID stay the same
  41. 41. Thank You!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×