SAP BusinessObjects BI4.0 Upgrade Workflows

Transcription

1 SAP BUSINESSOBJECTS BI4.0 Upgrade workflows Dhirendra Gehlot Business Analytics BI Competency Center Aug 2011

2 SAP BusinessObjects BI4.0 Upgrade Workflows 1.Upgrade Manager Tool 2.Upgrade Overview 3.Platform Setup 4.Security Upgrade 5.QaaWS, Dashboard Upgrade 6.Mobile Content Upgrade 7.Desktop Intelligence to Web Intelligence 8.Crystal Reports 2008 to Explorer InfoSpaces Upgrade 10.OpenDocument calls 11.UNV to UNX (Optional) 12.Web Intelligence Report Data Source to UNX or Bex (Optional) 13.Crystal Reports 2008/2011 to Crystal Reports for Enterprise (Optional) 2011 SAP AG. All rights reserved. 2

3 BI 4.0 Upgrade Manager Tool Upgrade Manager Tool (UMT) is a new tool in BI4.0 Upgrade contents from XIR2SP2 and newer to BI4.0 On Windows GUI Interface Supports Complete Upgrade and Incremental Upgrade On Unix Command Line Interface Supports Complete Upgrade 2011 SAP AG. All rights reserved. 3

16 BI 4.0 Upgrade Sequence Inventory and House Keeping Source Environment Identify Upgrade Gaps and Solutions Install and Configure BI 4.0 Platform Prepare for Content Upgrade Upgrade Content Validate Upgraded Content Go-Live 2011 SAP AG. All rights reserved. 16

17 BI 4.0 Content Upgrade Overview Contents Upgrade As It Is Security, Access Levels, Users/User Groups, Calendars, Events, Folders, Categories, Personal Documents, Repository Objects Web Intelligence, Crystal Reports, Xcelisus Dashboard, QaaWS Universes, Connections, Scheduled Jobs, Instances Remote Connections, Replication Jobs, LCM Jobs Mobile Subscriptions, Offline Documents MS Excel and BWA based Explorer Infospaces Contents Upgrade Require Manual Work Voyager workspaces OLAP Connections OpenDocument Calls 2011 SAP AG. All rights reserved. 17

18 BI 4.0 Content Upgrade Overview Contents Not Upgraded Desktop Intelligence Documents Universe based Explorer Infospaces Versioned Contents (Version Management System Repository) Audit Database Encyclopedia Performance Manager Custom Code 2011 SAP AG. All rights reserved. 18

19 BI 4.0 Upgrade BI4.0 Server Platform Setup In Place Upgrade Install Not supported Side by Side Install BI4.0 can be installed on the BOEXIR2 or BOE3.x Server, provided Server OS is 64-bit, and meets BI4.0 Install Prerequisites Two BusinessObjects systems run in parallel on the same hardware Configure BI4.0 environment Use Upgrade Manager Tool to upgrade content to BI4.0 Remove BOEXIR2 or BOE3.x Separate Environments (recommended ) Install BI4.0 on a separate server Configure BI4.0 environment Use Upgrade Manager Tool to upgrade content to BI4.0 Decommission BOEXIR2 or BOE3.x Servers 2011 SAP AG. All rights reserved. 19

20 Security Upgrade Workflow Before Upgrade Configure Authentication in the BI4.0 environment Enable Authentication plug-ins and map user groups Ensure that the administrator account for the 3rd party authentication is same in both source and target environments After Upgrade Manually update the Authentication Plug-Ins from CMC Click Update Roles Only to update only the migrated users for SAP Plug-in Click Update Roles and Aliases to create all the aliases for all of the users that belong to the currently-mapped roles. Specify the new owner right for existing products Specify rights with new products (WRC, IDT, LCM, etc) Set up rights at the root folder (If upgrading from XIr2) 2011 SAP AG. All rights reserved. 20

21 QaaWS Upgrade Workflow UMT moves the QaaWS and UNV it is based on to BI4.0 UMT ask for the Target Web Application Server Name Updates Web Application Server name in the the QaaWS call QaaWS works as it is in BI4.0 QaaWS supports UNV Universe QaaWS doesnt support UNX Universe If you convert the UNV to UNX You must use Query Design from Dashboard to repleace QaaWS bsed work flow Remove QaaWS when it is not needed anymore Remove UNV universe file when it is not needed anymore 2011 SAP AG. All rights reserved. 21

22 Xcelsius Dashboard Upgrade Workflow Xcelsius model is upgraded by UMT Upgraded model would still work as it in the BI4.0. Upgraded model can be edited using SAP Dashboard. Embedded URLs in Xcelsius models and Flash files are not upgraded QaaWS connections, for example Manually update the embedded URLs Republish the Dashboard to the platform with upgraded URLs Any hardcoded references to server name (web service url, host name etc) Would require manual change after upgrade Dashboards that use relative paths, don t required manual changes Except for OpenDocument calls Provide BI4.0 Web Services URL during upgrade QaaWS upgrade requires target Web Services URL 2011 SAP AG. All rights reserved. 22

23 Xcelsius Dashboard Upgrade Workflow Dashboard can be published to platform as Dashboard Design Object or Dashboard Design Object to Replace Flash Object. Dashboard Design Object Converts the dashboard to the new format and create the new Flash behind the scenes Secure / hide the old Flash file from end users if you want to keep a backup of the old version (but do not display it to the end users) Dashboard Design Object to Replace Flash Object Converts the dashboard to the new format and create the new Flash behind the scenes Delete the existing Flash file Avoid any confusion with the old version of the dashboard Live Office connection upgrade change the session to Session in the URL link ( If session remains lowercase, the link will not work correctly SAP AG. All rights reserved. 23

24 Mobile Upgrade Workflow Mobile Server Backup the config files on Mobile 3.x Server cluster.config server.config Copy config files onto the SAP BusinessObjects Mobile 4.0 Server UMT upgrades Mobile subscriptions UMT upgrades Offline Documents Stored on CMS Mobile Client Install new Mobile 4.0 Client on Device Restore offline/local documents to Mobile Device On the device, log into the Mobile application Launch the menu and select Preferences. Launch the menu again and select Recover Local Store. The documents stored in the Mobile Offline Data Store on the CMS for that user are restored to the Local Documents folder on the device SAP AG. All rights reserved. 24

25 DeskI to WebI Upgrade Workflow Desktop Intelligence (DeskI) documents are no longer available in BI 4.0 CMS All Deski reports will have to be converted to WebI or recreated in a different format (e.g. with Crystal Reports for Enterprise). DeskI documents can be converted to WebI using Report Conversion Tool (RCT) RCT does not convert all types of DeskI Documents Conversion Approach 1 Use RCT3.x to convert DeskI3.x to WebI3.x Publish converted documents to BOE3.x Validate new WebI document to original DeskI3.x document Use UMT to upgrade content from BOE3.x to BI4.0 Conversion Approach 2 Use RCT4.0 to convert Deski3.x to Webi4.0 Publish converted report to BI4.0 Validate new WebI document to original Deski3.x document 2011 SAP AG. All rights reserved. 25

26 Crystal Reports 2008 to Reports 2011 Upgrade Workflow Crystal Reports saved in reporsitory are automatically upgraded to Crystal Reports 2011 Crystal Reports saved on local desktop can be converted to Crystal Report 2011 Converion of Crystal Reports 2008 to Crystal Reports 2011 Open Report in Crystal Reports 2011 You would be prompted to acknowledge upgrade is non reversible Complete upgrade There is no batch conversion tool 2011 SAP AG. All rights reserved. 26

27 Explorer InfoSpace Upgrade Workflow Explorer Infospaces based on MS Excel, and BWA are upgraded by UMT Explorer Infospaces based on UNV Universe are not upgraded Explorer 4.0 InfoSpace supports only UNX universe The Explorer InfoSpace Upgrade path Complete upgrade to BI4.0 Convert UNV(s) to UNX(s) OR Create New UNX(s) Recreate the Explorer InfoSpaces based on UNX Universe 2011 SAP AG. All rights reserved. 27

28 OpenDocument Call Upgrade Workflow OpenDocument in SAP BusinessObjects XIR2 Name>... sdocname=reportname... OpenDocument in SAP BusinessObjects XI3.1 ID>... OpenDocument in SAP BusinessObjects BI4.0 ID>... Option 1: Manual Approach Update all OpenDocument references manually Option 2: Set up Redirect in Web Server For BOE3.1 to BI4.0 migration, Redirect:../OpenDocument/opendoc/openDocument.jsp To:../BOE/OpenDocument/opendoc/openDocument.jspOpenDocument For BOXIR2 to BI4.0 migration, Redirect:../businessobjects/enterprise115/desktoplaunch/opendoc/openDocument.jsp To:../BOE/OpenDocument/opendoc/openDocument.jspOpenDocument 2011 SAP AG. All rights reserved. 28

29 UNV to UNX Upgrade Workflow (Optional) UNX Universes New in BI4.0 Information Design Tool (IDT) creates UNX universes UNV to UNX conversation. Convert UNV to UNX using IDT Verify the converted UNX Export the UNX to enterprise Webi reports based on the UNV will not automatically start using converted UNX Manually update Webi report to use converted UNX OLAP UNV to UNX Conversion is NOT Supported 2011 SAP AG. All rights reserved. 29

30 UNV to UNX Upgrade Workflow (Optional) Conversion of SAP BW UNV to UNX is NOT Supported Approach 1 (Preferred) Continue to use XI 3.1 UNV as it is in BI4.0 OLAP UNV is supported in BI4.0 New development on the legacy Universe format, while supported, would probably not be an advisable investment Approach 2 Remap Web Intelligence reports to use native BICS connectivity 2011 SAP AG. All rights reserved. 30

31 Converting Webi to consume UNX or Bex Workflow (Optional) Create BICS connection from IDT From BI Launch Pad, select report Modify Report Go to Data Access Tab > Change Source Select Query to be changed Change Data Source Wizard is launched Select Specify a new data source Select BICS connection On Object Mapping screen map objects Key figures would be mapped automatically Characteristics with L00, L01, prefix would require manual mapping Map or Remove objects Exit Data Source Wizard for Data Source change to take place Repeat process until all Data Sources are changed Save Webi Report There is no batch conversion tool 2011 SAP AG. All rights reserved. 31

32 Crystal Reports to Crystal Reports for Enterprise Upgrade Workflow (Optional) Converion of Crystal Reports 2008 or Crystal Reports 2011 to Crystal Reports for Enterprise. Create a UNX universe using IDT tool that has reporting elements Open Report in Crystal Reports for Enterprise You would be prompted to acknowledge upgrade is non reversible Select UNX Universe Map the report columns with UNX objects on Field Mapping Page Complete upgrade There is no batch conversion tool 2011 SAP AG. All rights reserved. 32

33 Further Information Product Documentation Product Availability Matrix (PAM), Release Notes Installation Guide, and Administration Guide Deployment Planning Guide, Master Upgrade Guide, and Enterprise Upgrade Guide Best Practices and Methodologies for Upgrading to SAP BusinessObjects BI Deski to Webi ce BOPedia Forum SAP AG. All rights reserved. 33

34 Thank You! Contact information: Dhirendra Gehlot Business Analytics BI Competency Center

35 2011 SAP AG. All rights reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages SAP AG. All rights reserved. 35