Rajesh Ponnurangam

Infosol

The Four Big Steps

Preparing for the Upgrade 1

Installing BI Platform on Amazon Cloud (AWS) 2

Migrating Reports using Upgrade Management Tool (UMT) 3

Configuring and testing the new BI Platform 4

Preparing for the Upgrade

• Perform Inventory Clean up • Run Report Diagnostic Tool • Back up Repositories • Back up Custom web application, HTML pages and scripts

Simple queries to use against the repository To list all the Users SELECT * FROM CI_SYSTEMOBJECTS WHERE SI_KIND=’USER’ To list all the Universes SELECT * FROM CI_APPOBJECTS WHERE SI_KIND=’UNIVERSE’ To list all the Crystal reports SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND=‘CRYSTAL’

Installation Pre installation Checklist

• Access to servers, database repositories and Setup VPN/remote desktop etc • Backup of CMS and Audit database, FRS, Tomcat and Image of the Virtual

Server where Crystal Reports is installed (at least a day before the upgrade is done) Note* database backup and the Virtual server backup should happen around the same time frame.

• Download Crystal Server 2016 4.2 SP4 and place it on the Primary server (AWS) where installation needs to be performed.

• Download the license keys and place it on the Primary server (note pad file) • Disable Antiviruses and Fire wall or any Scans on the Server that needs to be

upgraded during the time/day of upgrade. • Prepare the AWS hardware based SAP PAM requirements • Create 2 databases – One for crystal repository and other for Audit store. • Install Microsoft VC++ 2015 Redistributable on server

Back Up Plan If the change is significant then we will roll back the server to its original state and try again.

BI 4.2 on AWS

SAP BusinessObjects BI4.x is being certified and supported for deployments on Amazon Web Services (AWS). It is strongly recommended to select a AWS location nearby your (organizations) datacenter / datasource to reduce a potential performance impact due to network latency. 1. Sizing 2. Provisioning 3. Deployment and configuration of BI 4.2

Migrating Reports using UMT Preparing the Upgrade management tool

Perform the following tasks in your existing XI3.x, XIR2SP2 deployment: • Stop all of the servers, except for the Central Management Server (CMS),and the

File Repository Server (FRS). Perform the following tasks in your new BI4.X deployment: • If you are using third-party authentication (AD, LDAP, SAP) you must configure the

authentication plug-in in the CMC in your new BI4.0 deployment and map all the user groups (AD, LDAP) or roles (SAP) that you are planning to export from your existing deployment.

• Stop all of the servers (including all Job Servers) in the destination deployment, except for the CMS, FRS, and the Report Application Server (if you plan to upgrade Crystal Reports documents).

UMT Upgrade Options

Complete Upgrade Incremental Upgrade

Upgrade all content at once Upgrade content in stages

Only 1 system to maintain 2 systems to maintain

Lock down entire system Lock down only department folder

Issues may affect entire system Issues affect only department folder

Longer downtime Shorter downtime

BI Content that is upgraded with upgrade management tool • Security, Access Levels, Users/User Groups,Calendars, Events, • Folders, Categories, Personal Documents, Repository Objects • Web Intelligence, Crystal Reports, QaaWS • Universes (unv), Connections, Scheduled Jobs, Instances • Remote Connections, Replication Jobs • Mobile Subscriptions, Offline Documents

BI Content that requires manual actions

UNV to UNX If you decide to upgrade your UNV to UNX (universes created in the new BI4.0 Information Designer) after running the upgrade management tool you will have to open them in the Information Designer to upgrade them. Notice that only relational universes can be converted, OLAP universes can't be converted. Crystal Report to Crystal Enterprise if you want to upgrade from SAP Crystal Reports 2011 to SAP Crystal Reports for Enterprise you will have to open each report in SAP Crystal Reports for Enterprise and map the report columns with UNX objects on the Field Mapping window.

BI Content that is not upgraded

Opendocument The OpenDocument URL has changed between versions, so you can either manually update your OpenDocument URLs or you can configure your Web Server to redirect Audit Database The audit database has a new schema, so you can upgrade your existing audit database. You can keep it for historical process and start the new database in BI4.0. If you want to create reports from both databases you can use the Information Designer to create a multisource universe. LCM Jobs According to the BI 4.x upgrade guide, XI 3.x Lifecycle Management (LCM) jobs cannot be migrated to BI platform 4.x because their contents are version-specific. By default, the migration of LCM objects is disabled.

Best Practices for UMT Migration Planning - Steps Prior to an Upgrade

• Prior to an upgrade, ensure that the source system is backed up • Scan for inconsistencies using the Repository Diagnostics Tool using both CMS

and FRS Scan & Repair options • Check all systems for possible issues to make sure all systems (Source, Target,

and UMT) are up and running without any issues • Before starting the migration process, make sure to clear your CMC

Temporary storage section by setting appropriate limits on the Temporary Storage folders within the Source and Target CMC

• Before starting the migration process, make sure to Disable Auditing on Source and Target environments to prevent logging of unnecessary events when doing the bulk operation as well as avoid performance issues

• Prior to starting migration, disabling the Platform Search / indexing has been seen to improve the overall performance during the migration process

• When performing an upgrade, Ensure that there is absolutely no user activity on both the Source and Target environments

Best Practices for UMT Migration Planning - Steps Prior to an Upgrade

• From where should you run the UMT? • Depending on migration (content) size, UMT can take up large amounts of

memory and Temporary disc space, hence it is better to run UMT on a central machine with plenty of resources such as RAM, disk / temp space and providing the UMT process with a large Java heap size.

• Temp space of at least 2x (filestore size) may be needed for best UMT performance

• Configure UMT to run with as much Java Heap as possible using the Java -Xmx argument (e.g.: -Xmx24g) on the UMT command line to increase the overall performance and stability of the UMT.

• Ensure only required servers and processes are running on Source, Target and UMT servers

Executing the UMT Process

• Take screen shots of every step in UMT

• Pause all the recurring schedules

BI 4.2 Configuration – After Report Migration

BI 4.2 Configuration – After Report Migration

• The first thing to do – Stop the Adaptive Job Server

• After pausing the recurring schedules, turn on the Adaptive job server and add the destinations required for the implementation

BI 4.2 Configuration – After Report Migration

Verify emailing the report to multiple users and not just one person

BI 4.2 Configuration – After Report Migration

BI 4.2 Configuration – Windows AD Setup

• Configured Active Directory Manual Authentication • No SSO Configuration • Configure the AD plugin page • Enterprise users were synced with Active Directory Groups

BI 4.2 Configuration – Windows AD Setup

• No extra space with in krb5.ini

AMAZON WORKSPACES

• Fully managed, secure virtual cloud desktops running on AWS • Desktop As A Service (DaaS)

Crystal Designer Installation issues

• Install Visuall C++ 2005 Service Pack 1 Redistributables

Crystal Designer Installation issues

• Disable the Crystal Reports Start Page Online Resource by renaming the file start.html and offlinestart.htm

• Cause:- The version of Crystal Reports 2016 designer, does not match the version of the SAP BusinessObjects Business Intelligence Platform it attempts to connect to

Crystal Designer Configurations

• Crystal Reports developed on OLEDB Connection were changed to ODBC Connection

• By Design, Crystal Reports limits the number of Database objects to 8000. The number of objects returned in Crystal Reports is determined by the setting in Windows registry: NtablesMax

• This setting can be changed in regedit

Crystal Designer Configurations

• An Alternate option is to Disable the Stored Procedures in File -> Options

Crystal Designer Configurations

• Transition from Infoview to BI LaunchPad • By default BI LaunchPad preferences in disabled

Preparing for Go Live

• Increase Tomcat Timeout • Go to <BI 4.0 Install

folder>\SAP BusinessObjects\Tomcat6\webapps\BOE\WEB-INF folder • Open web.xml in Notepad

Preparing for Go Live

• Restricting CMC Access to Users

Preparing for Go Live

• Change in Security Model • “No Access” to Everyone Group

Preparing for Go Live

GO Live

• BI Administrator’s Cockpit – A Life saver

References

• BI 4.2 on AWS – https://archive.sap.com/documents/docs/DOC-62148?platform=hootsuite

• Upgrade Best Practices - https://wiki.scn.sap.com/wiki/display/BOBJ/How+to+Upgrade+to+BI4.0

• Query Builder Basics - https://blogs.sap.com/2013/06/17/businessobjects-query-builder-basics/

https://wiki.scn.sap.com/wiki/display/BOBJ/Query+Builder • UMT Migration Best Practices - https://launchpad.support.sap.com/#/notes/1904814 • Report Diagnostic Tool -

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=143065487 • Crystal Designer Issues

• https://apps.support.sap.com/sap/support/knowledge/public/en/1520706 • https://apps.support.sap.com/sap/support/knowledge/public/en/1215994

• Windows AD - 1631734 - How To Setup Windows Active Directory plugin and SSO for BI4.x

- Best Practices

#askQuestions @infosolinc @rajeshbipro #LetsSpeakBO

Thank You!