This article explains how to upgrade to SAP Business Intelligence 4.0. This info exists in the Upgrade Guide on the Help Portal.
- BusinessObjects Enterprise XI 3.1 SP2
- LifeCycleManager XI3.1 SP2
Table of contents
Overall upgrade process
There are 4 main steps to upgrade to BI4.0:
- Preparing for upgrades
- Installing the BI platform
- Using the upgrade management tool
- Configuring the BI platform
1. Preparing for upgrades
Before upgrading to BI4.0 there are some tasks that you need to perform in both your existing deployment and the new deployment system.
To configure the existing deployment
- Perform inventory and cleanup, to ensure that only the required content is upgraded
- Run the Repository Diagnostic Tool to detect any inconsistencies between the File Repository and the CMS repository. The upgrade management tool will not run successfully if there are inconsistencies between the File Repository and the CMS repository.
- Identify any content that the upgrade management tool can't upgrade, along with the process required to upgrade that content. There is some content like Voyager Workspaces or Desktop Intelligence documents that require manual intervention before running the upgrade management tool.
- Back up existing repositories, including the system database and the Input and Output File Repository Servers.
- Back up custom web applications, HTML pages, and scripts in your existing deployment.
To configure the planned BI 4.0 deployment
- Setup and configure the Middleware and ODBC connections.
- Ensure that your machines meet the deployment system's requirements, you can find information about the supported platforms in the Platform Availability Matrix (PAM) http://service.sap.com/support -> Help and Support -> SAP BusinessObjects Support -> Documentation -> Supported Platform s/PARs -> SAP BusinessObjects BI 4.0
- More info on the Repository Diagnostic Tool can be found here: http://wiki.sdn.sap.com/wiki/display/BOBJ/How+to+use+Repository+Diagnostic+Tool
- The following article has a good overview on what you need to know before upgrading: http://wiki.sdn.sap.com/wiki/display/BOBJ/All+you+need+to+know+before+upgrading+to+BI4.0
2. Installing the BI platform
You can either create a deployment in a separate environment or a side-by-side deployment. You cannot do an in-place upgrade.
To install the BI platform in a separate environment
Installing in a separate environment is the recommended option.
- Install BI4.0 on a separate server
- Use the upgrade management tool to upgrade your content
- Decommission XIR3.x or XIR2SP2 servers.
To install the BI platform side-by-side with anther deployment
A side-by-side deployment is possible but not recommended. You can install BI4.0 on the same server where either XI3.x or XIR2SP2 is running if your existing server satisfies all the BI4.0 requirements. Consult the PAM to make sure you have the supported platforms for the different components in BI4.0
- Install BI4.0 your existing XI3.x or XIR2 servers. You will have two versions of the BI platform running on the same hardware, so make sure that you specify unique Central Management Server (CMS) cluster.
- Create a unique name and port number for your BI4.0 deployment (other than 6400) to avoid conflicts between deployments.
- Use the upgrade management tool to upgrade your content.
- After BI4.0 is successfully deployed, uninstall XI3.x or XIR2SP2.
3. Using the upgrade management tool
Once you have BI4.0 installed, you are ready to begin preparations for running the upgrade management tool. The upgrade management tool is a new tool in BI4.0 that allows you to upgrade your BI content from XIR3.x and XIR2SP2 environments. After completing the preparations, you can run the upgrade management tool.
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.0 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. The upgrade management tool can only import groups and users that are already configured and mapped in the BI4.0 destination system.
- 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).
Where to run the upgrade management tool
There are some considerations to have in mind when deciding where to run the upgrade management tool:
- The upgrade management tool is available as a GUI interface for Windows and as a command line interface for Unix/Linux.
- When you run the GUI upgrade management tool you are given the option of doing a complete upgrade or an incremental upgrade. (A comparison of complete vs incremental upgrades is outlined in the section below.) If you are using the command line, you can only do a complete upgrade.
- The upgrade management tool requires that the features that you are going to upgrade are available on the machine where you are running it. This means that you need the components installed with the different BI platform servers.
- You need to run the BI 4.0 Server to install the upgrade management tool. The server install requires a 64bit OS.
- UMT reads from source, saves on the local Hard Disk and writes to the target.
- The OS's Temp directory should have at least 10GB free disk space. Don’t run out of ‘temp’ disk space!
- Greatly reduce upgrade time by setting JavaHeap to use as much RAM as possible in the ‘command line’ (in the shortcut) for UMT.
Complete upgrade vs incremental upgrade
In a complete upgrade, all the Business Intelligence content is upgraded from the source deployment to the destination deployment.A complete upgrade replaces the functionality that was available in the Central Configuration Manager (CCM) in BusinessObjects Enterprise XI3.x
Incremental upgrades allow you to migrate individual objects to a destination deployment. The incremental upgrade replaces the functionality that previously existed in the Import Wizard.
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
Running the upgrade management tool
When you run the upgrade management tool, your BI content will be migrated and upgraded to the new BI4.0 system. However, there is some content that will require manual action in order to be upgraded.
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 action to upgrade
How to upgrade?
When you run the upgrade management tool universes (UNV) created in the Universe Designed are migrated to BI4.0 as UNV and they will continue to work as they are in BI4.0; there is no need to do any modifications. 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. More detailed information on how to Convert Relational universes (UNV to UNX) can be found here: http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+of+the+relational+universes+in+BI+4.x%2C+from+UNV+to+UNX
Crystal Reports are upgraded to SAP Crystal Reports 2011 by the upgrade management tool and they will work fine in BI 4.0, 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. You can find more information regarding these two versions here: http://wiki.sdn.sap.com/wiki/display/BOBJ/From+Crystal+Reports+2008+to+SAP+Crystal+Reports+2011+or+SAP+Crystal+Reports+for+Enterprise
Voyager workspaces are upgraded by the upgrade management tool. However, some work must be done before and after running the upgrade management tool in order for the workspaces to be upgraded:
Xcelsius dashboards are migrated by the upgrade management tool as they are. They will continue to work fine and can be opened in SAP Dashboards.
The upgrade management tool migrates the QaaWS and UNV. It is based on BI4.0. When running the upgrade management tool you will be prompted for the Target Web Application Server Name so that it can be updated accordingly in QaaSW services.
The OpenDocument URL has changed between versions, so you can either manually update your OpenDocument URLs to the following: http://<server>:<port>/BOE/OpenDocument/opendoc/<platformSpecific>?iDocID=<doc ID>...
BI Content that is not upgraded
Not Upgraded, what can you do with this content?
The upgrade management tool does not upgrade desktop intelligence documents as Desktop intelligence has reached end of life. Desktop Intelligence documents don't work in BI4.0, so upgrade Management will not migrate them to a BI4.0 system. You can convert Desktop Intelligence documents to Web Intelligence. You can convert them to Web Intelligence using the Report Conversion Tool in your existing XI3.x deployment and then bring those Web Intelligence documents with the upgrade management tool, or you can convert your Desktop Intelligence documents residing in your existing XI3.x using BI 4.0 Conversion Tool and then publish them to your new BI4.0 deployment. For more details review the following document:
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.
If you are using the version management feature in the LifeCycle Management console in XI3.x, note that the content in the Subversion repository will not be upgraded by the upgrade management tool because the repository is external. XI3.x has Subversion v1.4.x. while BI4.0 has Subversion v1.6.x. Therefore, you will need to use Subversion commands to export, import and upgrade the Subversion repository.
|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. However, if you want to keep the history of your InfoObjects, you can force the migration by adding the following option to the upgrade management tool: -Dumt.systemVar.omitLCMObjects=false|
4. Configuring the BI platform
- For third-party groups, authentication use the CMC to configure the windows AD. For AD authentication click on Update. For SAP authentication go to the Update tab and click Update Aliases.
- Specify the new owner right for existing products.
- Specify rights with new products (WRC, IDT, LCM, etc).
- If you are upgrading from XIR2SP2, set up rights at the root folder.
- Perform any required updates to documents that were not upgraded by the upgrade management tool.