Recently we came across the situation where we must migrate our existing SAP BusinessObjects environment to new hardware.
We need to made this decision because migration of on-premises systems to hosted solution. Lately, this is the trend most of the infrastructure teams moving to clod or hosted solution for cost cutting on hardware and it’s maintenance.
With other SAP systems such as JAVA and ABAP there is plenty of ways to migrate your systems – for example DB backup restore, system export/import… and so on….
Today we are going to talk about SAP BusinessObjects system migration to cloud or hosted solution. This approach can be taken while you want to change server names. I believed this will not be an easy task since there is multiple teams need to be involved to test upon complition of migration…
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 producing EWA (Early Watch Alerts) for SAP business object system through our newly installed SAP Solution Manager 7.2 which always complaining about our installed verion of SAP BO is old and support will be ending soon for OS and DB 🙁
Now this is the perfect time to get this all issue resolved. We convert his move project in to upgrade opportunity. We have decided to migrate all existing reports and users to new hardware/VM and perform system upgrade at the same time 🙂
Now let me walk you through that how we achieved this?
In hosted solution we started installing and configuring new version of Microsoft windows server and SQL instance. Two servers – one with SQL instance. We wanted to have clustered installation due to heavy system load and match with existing installation. Basic infrastructure will be look like as below without any SAP products on it.
In next step we installed new version of SAP business objects system creating cluster as below
Note: This is very high-level diagram for illustration.
Role of First server is primary server and which contain – Tomcat, BO, FRS and SQL instance for CMS database
Second server is like and additional application instance of other SAP applications – containing Tomcat and BusinessObjects
Note: You can use Microsoft clustering or always on to make your CMS and Audit DB HA and very high level installation can be look like as below.
We started exporting objects from our existing SAP Business Objects system using LCM tool and storing in to common share location where we can access files to import in targeted system using LCM
If you have CTS+ configured for SAP business Objects you can add new system as target system
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…)
Note: Make sure you prepare export plan for reports making sure you not leaving anything behind and everything is migrated.
Do not forgot to perform testing reports after migration of report is completed.
Hope you enjoyed reading my experience on SAP BusinessObjects migration process.