This action might not be possible to undo. Are you sure you want to continue?
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.
© 2011 SAP AG. All rights reserved.
Upgrade Overview and Concepts Upgrade Best Practices Technical Implementation
© 2011 SAP AG. All rights reserved.
Upgrade Overview and Concepts
All rights reserved. 5 .Why Upgrading? • Better integration with SAP BW • New dimensional semantic layer • Multi-source universes Data access Usability / Productivity • Harmonized user experience across the suite • Interoperability • Advanced analytical insight • Brand new search capability Cost of Ownership • Integrated platform monitoring • Advanced auditing capabilities • Supportability and root-cause analysis • 64 bits server architecture © 2011 SAP AG.
All rights reserved.Planning your Upgrade Typical Upgrade Timeline Milestone 1 M2 M3 Considerations before M4 upgrading Assessment – magnitude of project Time and Deadlines Resources (IT/HW) Planning Design Down time Training Implementation Cutover Backup Go Live © 2011 SAP AG. 6 .
Checklist .servers are now 64 bits only Version upgrade path Newer systems have a direct upgrade path Older systems may require extra steps Recommendations are provided in this presentation Product Changes Some features may be staged to a later BI 4 release Some products are deprecated or replaced Understand the upgrade path for each product you are using Capture all parameters and customization to understand what it means to the new system 7 Parameters and customization Not automatically upgraded © 2011 SAP AG. . All rights reserved.System Considerations Platforms Platforms supported with BI 4 change Review each component of the landscape to define the appropriate strategy Architecture changes .
Content Considerations Security upgrade Should you carry over the existing users and associated security ? Should you take the opportunity to do some redesign ? Review your options and needs. All rights reserved. Details in this deck. Content inventory and cleanup Should you upgrade the all content or take the opportunity for some cleanup? Recommendation to at least do some cleanup before upgrading Full system vs Staged upgrade Upgrade the entire system Or upgrade one department / group at a time Review the pros and cons depending on your own constraints Acceptance / Validation Should you test the upgrade process? Obviously yes! Test your upgrade on a sandbox 8 © 2011 SAP AG.Checklist . .
Upgrade Best Practices .
All rights reserved.x BOE XI R2 Direct Upgrade using “Upgrade Manager Tool” BOE XI BOE XI 3.x BI 4. BI stands for Business Intelligence CE for Crystal Enterprise. 10 .Versions Upgrade Path No direct Upgrade Go first to XI R2 or XI 3.0 CE8 / CE9 / CE10 BO 5 / BO6 BOE stands for BusinessObjects Enterprise. © 2011 SAP AG.
1 Binaries Audit BI 4.Product Changes . 11 . Need to plan for a workaround InfoView Dashboard Builder BI Launch Pad BI Workspace New interface Report pinning Corporate.0 © 2011 SAP AG. All rights reserved. Personal and My InfoView Dashboards become BI Workspaces but some analytics must be recreated in Xcelsius Encyclopedia / Discussion Performance manager Search End of Life End of Life No upgrade No upgrade New search technology The search index will be re-built in BI 4.BI Platform Components XI R2 / XI 3.0 New binaries New audit schema Upgrade Considerations The full landscape has to be re-installed Historical audit data is not kept.
BI Clients XI R2 / XI 3.Product Changes .0 CR 2011 and CR Enterprise End Of Life Dashboards Upgrade Considerations All reports are by default upgraded to CR 2011 Possible manual upgrade to CR Enterprise Report Conversion Tool converts into Web Intelligence format prior or after the upgrade Flash files will continue to work Conversion to new format is optional Conversion adds new features (globalization. 12 . the others require manual changes Fully upgraded Explorer No UNV support Voyager Analysis. All rights reserved.1 Crystal Reports Desktop Intelligence Xcelsius 2008 BI 4. edition for OLAP Web Intelligence Web Intelligence Web Intelligence SDK No Web Intelligence SDK support Wait until full support and availability of Interactive Analysis (REBEAN) SDK in a later release © 2011 SAP AG. the ones based on UNV and bookmarks are not ! Some of workspaces will be upgrade to Advanced Analysis. UNX queries…) Information Spaces based on Excel are upgraded.
Semantic Layer XIR2 / XI 3.BI Clients .0 No change Information Designer – UNX format Upgrade Considerations None.1 Universe Designer UNV format n/a BI 4.x Relational UNV can be converted to UNX OLAP UNV have to be re-created in UNX (future version will support conversion) © 2011 SAP AG. universes and designer as in XI 3. All rights reserved.Product Changes . 13 .
1 LCM (XI 3.0 Integrated in BI 4.1 is maintained All translations previously done will be retained WDeploy GUI available New tool.Product Changes .0 Upgrade Manager Upgrade Considerations No separate installation required Same feature than XI 3. More details in this presentation WDeploy Import Wizard © 2011 SAP AG.0 client tools Integrated in BI 4. All rights reserved.Tools XI R2 / XI 3.0 No Change Integrated in BI 4.1 only) Report Conversion Translation Manager BI 4. 14 .1 with the support of the Online to Online mode Parity of features with XI 3.
1 and BI 4.0 Existing documents will continue to work Need to update client machines Local content moved with upgrade manager 3.0 No upgrade : wait for availability in a later release Existing DF 3.0 may coexist (2 client versions on the device) Parameters to be re-set or copied Data Federator Live Office Mobile Query as a Web Service (QaaWS) No change QaaWS will continue to work Upgrade Manager will detect dependencies to universes (UNV) Dashboards on QaaWS will continue to work © 2011 SAP AG.0 Upgrade Considerations No separate installation required Integration Kit for SharePoint Not available Partially integrated in BI 4.0 No change Integrated in BI 4. PeopleSoft. JDEdwards. Oracle BI 4.x deployments remain compatible with BI 4.0 Integrated in BI 4.Other Components XI R2 / XI 3.Product Changes . 15 . Siebel.1 Integration Kits for SAP. All rights reserved.
16 XI 3. 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.x BI 4. LCM. etc ) .0 Security model is the same as the one of XI 3 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.0 Continuity + new features have been added since XI R2 In BI 4. IDT.0 you have to : Specify the new “owner right” for existing products Specify rights with new products (IDT.Security Upgrade XI R2 BI 4.
17 . All rights reserved.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 Repository Diagnostic Tool Instance Manager / CMC ■ Fix or delete scheduled jobs that are paused or failed ■ Detect and delete un-used reports after checking with users Auditing Upgrade Management Tool ■ Remove older report instances or un-used instances ■ Fix repository inconsistencies © 2011 SAP AG.
All rights reserved.Special content type • Upgraded with the user • Possible to opt-out Inboxes Personal Documents Reports Instances • Come with the report • Option in Upgrade Management Tool not to import them Scheduler Jobs • Automatically carried over with the scheduled report © 2011 SAP AG. 18 .
19 .Full System vs Staged Upgrade Full / One Shot Upgrade Stage / Incremental Upgrade per department Upgrade all content at once Only 1 system to maintain Upgrade content in stages 2 systems to maintain Requires lockdown of department folder Requires lockdown of the entire system Issues affect the entire system Long downtime Simpler (less options) Issues affect only the department upgraded Short downtime © 2011 SAP AG. All rights reserved.
All rights reserved. .Full System vs Staged Upgrade Small and simple deployment Full / One shot upgrade Larger shared services deployments Do you have a pre-prod to validate the upgrade ? Ye s Can you afford a longer downtime ? Yes Full / One shot upgrade Perform upgrade tests to evaluate the expected downtime 20 No Staged / Incremental upgrade recommended No © 2011 SAP AG.
Input and output” 3. Block all access to the CMS port except between your source and destination © 2011 SAP AG. 21 . Disable and stop all “BusinessObjects servers” except the “CMS.Full System Upgrade Considerations No lockdown or read only options available in BOE To lockdown a BOE system: 1. All rights reserved. Shutdown your application server 2.
All rights reserved.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 © 2011 SAP AG. 22 .
universes. security.Acceptance / Validation In Place Acceptance process right after the actual upgrade to the TEST system On a Sandbox As part of the planning and discover process Products features and functions Compatibility with existing systems Estimate time to upgrade Success of the content upgrade (users. 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 © 2011 SAP AG. 23 . All rights reserved.
Technical Implementation .
All rights reserved.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. 25 .Solution Architecture The general BI 4.
26 .Overview Main 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.Architecture Upgrade .
All rights reserved. use different servers to install and run both systems in parallel On UNIX.0 environment 3 2 content (live to live) New BOE BI 4.Implementation Previous (Xir2 or Xi3.Architecture Upgrade .0 system Installation and configuration of third parties and customization Time On Windows.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 1 Upgrade the BOE New BOE BI 4.0 environment BI 4. use different servers or different user accounts on the same server © 2011 SAP AG. 27 .
0 Qualification * In BI 4. LCM does not move document instances.x) Production to BI 4.x) Qualification Previous (XI R2 / XI 3.x) Development LCM or IW Previous (XI R2 / XI 3. user inboxes and personals documents LCM BI 4.x) Production * Upgrade Manager BI 4.0 Production 28 .0 Production LCM or IW Previous (XI R2 / XI 3.Upgrade Considerations (DEV/ QUAL / PROD) Best practice: upgrade from previous version (XI R2 / XI 3. LCM * BI 4.0 Development © 2011 SAP AG.x) Production to BI 4.0.0 Qualification Current limitation of LCM in BI 4. All rights reserved.0 (to be addressed in a future minor release) may lead to: previous version (XI R2 / XI 3.
© 2011 SAP AG.g. Not document instances. All rights reserved.0 Upgrade Upgrade Manager Upgrade: “Transport and transform content from previous version to newer version” Content includes all objects.The right tool for the job in BI 4. Improvement over previous releases: Now a unique and scalable tool dedicated to upgrade Promotion LCM Promotion: “Transport content from like system to like system” Systems are the same major version E. 29 . Dev to Test to Production Content is primarily document templates and metadata and schedules.
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 destination systems up and running Administrator running Upgrade Manager Ports must be opened between source and destination © 2011 SAP AG. All rights reserved. 30 .
All rights reserved. 1Gb max recommended) Administrator running Upgrade Manager BIAR file Previous version XI R2 or XI 3 © 2011 SAP AG.000 objects.Upgrade Manager BIAR-to-Live Scenario 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. 31 .
Basic Upgrade Workflow Demo . upgrade your entire repository in 4 steps 1 2 34 Available in Windows GUI and Unix command line Get Upgrade Choose the summary Choose the is going to of what scenario & enter End Complete Upgrade be upgraded credentials © 2011 SAP AG. 32 .Full System Replaces Database Migration in Central Configuration Manager Easy. All rights reserved.
All rights reserved.Staged To perform an Incremental Upgrade: 1 2 3 4 5 Choose Upgrade Choose objects Choose the Choose objects to to scenario & exclude & options enter End Incremental copy & options Upgrade credentials © 2011 SAP AG. 33 .Basic Upgrade Workflow Demo .
milestones. All rights reserved. backup and test strategies… Platforms / Product changes Platforms supported with BI 4. 34 .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.Take Away Plan the upgrade Upgrading is a demanding project. Need plan.
1 Security and Authentication settings (AD / LDAP / SSL / SAP) Reporting databases connectivity BOE Server configuration settings Web Application configuration settings BI 4.0 To be set up in BI 4.0 No upgrade.0. BOE specific settings moved from Web.Product Changes . No upgrade InfoView Customization (picture. …) Custom Java code using the BOE SDK and Report Engine SDK To be set up in BI 4.0 Need to validate your custom code will still work in BI 4. 36 .0 Upgrade Considerations No upgrade To be set up in BI 4. Some of the Java functions can be deprecated.0 No upgrade To be set up in BI 4.0 No upgrade To be set up in BI 4.xml file to properties file. logo.Parameters and Customization XI R2 / XI 3. All rights reserved. © 2011 SAP AG.
sap.com/support -> Help & Support -> SAP BusinessObjects Support -> Supported platform documents © 2011 SAP AG. Authentication model .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. JVM…» Go to : BusinessObjects Product Availability Report (PAR) http://service. 37 . All rights reserved.
0 on it.0 sample audit universe and reports (found on the web site) Customize the samples or re-develop reports to match XI 3. Audit solutions that use the XI 3.0 audit database Install the BI 4.x audit database for historical data Move the XI 3.x audit application (universe + reports) into the new system Start BI 4.x and BI 4. And upgrade XI 3.1 audit data and do reporting from BI 4. 38 . All rights reserved.x universes and reports.0 with a fresh 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.x audit schema : Keep existing XI 3.Auditing Overview Keep your XI 3.
All rights reserved.Desktop Intelligence Overview Desktop Intelligence documents will no longer be available in BI 4.0 Query on Query Fold/Unfold Show/Hide Fit to page © 2011 SAP AG. 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. 39 .0 CMS.
1 RCT to convert Deski to Webi report on the same stack CMS XI 3.0 Webi report Link to UNV is preserved © 2011 SAP AG.0 system. The only way for a user to bring Desktop Intelligence content is: Use XI 3.x Deski report CMS XI 3. CUID stay the same 40 .0 RCT to convert Deski to Webi report & to publish it into BI 4.x Webi report Use BI 4.0 Upgrade Manager to promote content Use BI 4.0 CMS.Desktop Intelligence & Report Conversion Tool Desktop Intelligence documents will no longer be available in BI 4. CMS BI 4. All rights reserved.
Thank You! .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.