I would like to share my experience with SAP Business Object system Upgrade from lower version like BOBJ 3.x to latest BOBJ version 4.0 SPx. I used “Upgrade Management Tool” to perform this upgrade. I have identified the following major steps for the entire upgrade process and will brief up as follows :
SAP BOBJ upgrade steps :
- Install the Target BOBJ 4.0 SPx server (as per installation guide)
- Install Upgrade Management Tool (UMT) on a Windows system.
- Perform all pre-requisite tasks.
- Perform upgrade using UMT
- Perform all post upgrade tasks
1. Install the Target BOBJ 4.0 SPx server (as per installation guide)
I am not going to cover basic installation of the Target system. In this example, I have considered that Target system BOBJ 4.0 SP2 has been installed on RHEL (Redhat Enterprise Linux) 5.3 with DB2 LUW 9.5 database.
Check whether Target system is up and running using following URL
Verify all services are running.
2. Install Upgrade Management Tool
SAP released the Upgrade Management Tool (UMT) as a part of Business Object Server installation kit for Windows of x86_64 platform. That means you need to install Upgrade Management Tool on 64-bit Windows OS. You can install this tool on source, target or any standalone Windows 64-bit machine.
In this example I am using BOBJ 4.0 SP2. Start the installation by executing ‘setup.exe’ from the installation media (DVD – 51041015).
Fig 1 : UMT installation
I am not going to show you all screenshots, only few important screenshots :
Under Administrator Tools , select the “Upgrade management tool”. No need to select any other component.
Fig 2 : UMT selection
Another important input is – exiting CMS server info. In this regard, you can provide information about target system as follows :
Fig 3 : CMS input
Finish the installation.
3. Perform all pre-upgrade tasks ( on the source system )
In this example source system BOBJ 3.x is running on Windows 2003 with MS SQL database.
3.1 Run Deployment Diagnostic Tools ( on the source system )
This tool will verify all major services of BOBJ system – including CMS, Crystal report service, Job services and Web intelligent tier. Diagnostic tool will re-cycle all services except CMS.
Start the tool from BOBJ 3.x program group as follows:
Fig 4 : Diagnostic Tool
Perform the check with the user ‘Administrator’ or any user having similar right.
Typical Diagnostic Tool test result as follows:
Fig 5 : Result of Diagnostic Tool
For any error, fix the error and re-run the tool.
3.2 Take Repository Backup ( of both source and target systems).
Before repository scan, take a backup of source system repository ( as .BIAR file ) using – serverconfig utility.
3.3 Run Repository Diagnostic check on the source system
BOBJ repository is the metadata of all objects or components within the BOBJ system. Inconsistent object in repository will throw an error during upgrade. Perform a repository diagnostic check with ‘reposcan.exe’ utility to determine any inconsistent object in the repository and fix the issue before actual upgrade.You need to pass a parameter file called ‘repo-input.txt’ while executing ‘reposcan.exe’ utility as the follows :
reposcan.exe -optionsfile "repo_input.txt"
A generic “repo_input.txt” as follows :
-dbdriver <database driver name>
-connect "UID=<user-id>;PWD=<password>;DSN=<dns-name>;HOSTNAME=<source system>;PORT=3306"
-inputfrsdir "path of inputFRS"
-outputfrsdir "path of outputFRS"
-scanfrs
-scancms
Scan will take sometime, based on number of objects available in your system and it will display the scan result as follows ;
Fig 6 : Result of repository scan
Check the log file in “reposcan” directory under BOBJ and resolve all issues associated with inconsistent objects.
3.4 Take database and InputFRS + outputFRS file system
Take the file system backup of both InputFRS and outputFRS directory and ideally this backup must be sync with repository or database backup. If possible take the backup of entire “bobje” folder or file system.
3.5 Take backup of any manually deploy web services.
Take the backup all manually deployed web services and re-deploy after upgrade.
4. Perform Upgrade
n Check the size of /tmp directory in source system and make sure the sufficient space is available.
n Change the Javaheap to 2 GB on the source system.
n Stop all services in both source and Target system except mandatory services ( CMS, input and output File Repository services.)
n If SAP integration for Target system has been completed beforehand, take backup of the following property files
web.xml
BIlaunchpad.properties
OpenDocument.properties
global.properties
Start upgrade tool – ‘Upgrade Management Tool” :
Fig 7: Start UMT
Next bigger question is whether you will go ahead with “Complete Upgrade” or “Incremental Upgrade” option. In case of “Complete upgrade”, you do not have a choice for object selection and upgrade process will upgrade all objects (folders). However “incremental upgrade” option will give you opportunity to select your object list.
Fig 8 : Upgrade options
Next specify the source and target host or CMS server
Fig 9 : Source and target system info
UMT will give you an opportunity to select all folders and objects based on your upgrade needs.
Fig 10 : Folder structure
Next UMT will give you an opportunity make a selection for users and groups.
Fig 11: Users and Groups
Confirm all selection and continue with the upgrade.UMT will verify all object dependency.
Fig 12 : Object dependency
After object dependency run, start the actual upgrade and it will show the upgrade progress as follows:
Fig 13 : Upgrade progress
Based on the number of objects, upgrade process may run for a while. Once the upgrade process is completed, verify the upgrade logs.
Fig 14 : Upgrade completed
5. Post upgrade tasks
n Take an offline database and InputFRS+OutputFRS backup at the same time.
n Verify and setup all generic parameter in web.xml file .
n Verify and setup all data source connection and adjust odbc.ini file.
n Verify and adjust all access control for folders and reports.
n Install addition servers ( App Server / Non-CMS server ) – optional step.
n Install BOBJ Explorer service for BWA and perform the configuration – optional step.
n Perform cluster setup using Apache + Tomcat – optional step.
n Convert all old universe ( .UNV file ) to (.UNX file) – optional step.
n Perform all configuration steps to integrate BOBJ with SAP – optional steps.
n Re-deploy all third party and customize web services ( if exist )
n Distribute and rollout BOBJ 4.0 client tools and developers tools ( Crystal Report, DashBoard etc) to all developer’s workstations.
n Adjust all access control and authorization.
- SAP Managed Tags:
3 Comments
