Sharing knowledge gained from moving SAP BusinessObjects to a new environment
We recently encountered the need to transfer our old SAP BusinessObjects installation to new hardware.
This choice is required due to the transfer of on-premises systems to a hosted solution. Recently, most infrastructure teams have been migrating to the cloud or hosted solutions in order to save money on hardware and maintenance.
Other SAP systems, such as JAVA and ABAP, include several migration options, such as DB backup and restore system export/import, and so on. and so forth…
Today’s topic is SAP BusinessObjects system migration to a cloud or hosted solution. This method may be used if you wish to modify the names of your servers. I anticipated that this would be a difficult process because different teams would be required to test once the migration was completed…
Existing (On-premises) installation of SAP BusinessObjects is as below
- Windows server: 2012 (installed on VMWare environment)
- SQL Instance: 2008
- Web tire: Tomcat
- Business Object: 4.0 SPS04
We are creating EWA (Early Watch Alerts) for SAP business object system using our recently installed SAP Solution Manager 7.2, which is always screaming that our installed version of SAP BO is outdated and support for OS and DB will be ending soon 🙁
This is the ideal moment to settle all of the issues. We turn his relocation project into an upgrading opportunity. We’ve chosen to transfer all current reports and users to new hardware/VMs while also doing a system update 🙂
Now, let me walk you through how we accomplished this.
We began installing and configuring a new version of the Microsoft Windows Server and SQL instance in the hosted solution. Two servers, one of which has a SQL instance. We desired a clustered installation because of the high system load and to mirror the existing arrangement. The basic infrastructure will look like this without any SAP products.
In the following step, we installed a new version of the SAP business objects system, creating a cluster as seen below.
Please keep in mind that this is a very high-level graphic for illustrative purposes only.
The primary server’s role is to hold Tomcat, BO, FRS, and a SQL instance for the CMS database.
The second server functions similarly to an additional application instance of other SAP applications – it has Tomcat and BusinessObjects.
Note: To make your CMS and Audit DB HA, you may utilise Microsoft clustering or always-on, and a very high-level installation can look like this.
We began by exporting items from our old SAP Business Objects system using the LCM tool and putting them in a shared share location from which we could retrieve files to import into the targeted system using the LCM tool.
Using LCM (LifeCycle Management) tool
If you have CTS+ configured for SAP business Objects you can add a new system as the target system.
SAP Note: 1634962 – How to import or export a LCMBIAR file using LCMCLI command line utility
Objects to export and import
- Users and Security assigned to users (This includes Group and users)
- Connections of reports (Make sure to create ODBC connections manually if any in use)
- Reports (universe, WebI reports etc…)