Skip to Content
Author's profile photo S man

Pre and post production steps of BODS 12.2.2 upgrade to BODS 4.1

BODS 4.1 upgrade on AIX from BODS 12.2.2:

Note: Few SAP note says Installation of BODS 4.1 on Business Objects enterprise environment should be first and then BODS installation on AIX is next.

At the same time some other SAP notes says BODS on AIX should be first and then BODS 4.1 on Business Objects enterprise environment.

Not sure which is correct but we followed 1st process.

Pre-Installation steps on AIX

  • Copy software to one of the Unix location
  • Check for pre-request of hardware
  • Now stop JobServe and tomcat if still running on system (BODS 12.2.2)
  • Make sure Install Directory should have space of 8-10 gb
  • Now backup below files from Install Directory < bin and conf (BODS 12.2.2)
  • Backup all bods 12.2 files and move them to other location
  • Check for UTF-8
  • Get it into software location and enter below script

./ InstallDir=location of installation directory

  • Now it will prompt for UTF-8 file missing
  • Enter below script to assign UTF-8


  • Now once again enter software setup script

./ InstallDir=location of installation directory

Installation as normal

Note: In the process of installation it will ask for path of DSCONFIG file

Post- Installation steps on AIX:

  • Now check for svrcfg in AIX for job server status
  • If svrcfg get fails to open, that mean environment variables are missing
  • Now get it into Install Dir < bin and execute
  • Now check for svrcfg and make sure it will show up job server
  • Check status of job server
  • Check and make sure SAP note 1659855 to follow for DSConfig.txt

BODS 4.1 on BOE servers (Tomcat and EIM server on Windows 2008 R2):


  • Copy software on one of the windows server
  • Take backup of Install Dir < Tomcat6 <Webapps
  • Stop tomcat of BOE
  • Stop Java based servers on BOE
  • Make sure only one user logged on system
  • Keep CMS, connection, connection32, Event, IFRS and OFRS servers up and running
  • Extract setup.exe file
  • Make sure all other nodes need to be down.

Installation normal process:

Note: product key will be same as BODS product key which used on AIX

Post Installation Steps:

  • Once server restart done, automatically tomcat and Sia need to be up and running
  • Try to launch BOE and Data Services url
  • If any of the url fails to login and throws http error
  • Stop Tomcat and take back of BOE or Data Services folder under Install DIr < Tomcat < webapps
  • Start tomcat
  • After 15 to 20 minutes it will create new BOE or Data Services folders
  • Now check for url
  • If tomcat itself fails to start, then check for jdk files
  • Once all urls are up and running and user see that SSO and authentication fails then copy BOE folder (from backup folder which took before upgrade) and restart tomcat
  • SAP roles need to be imported for BODS (If BW is backend)
  • SAP transport need to move to respective backend system
  • Apply OSS note 1659855 – Mismatch for SAP function
  • Copy InstallDIr\app\11.2.0\grid\jdbc\lib\* to InstallDir:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\im\oracle
  • Follow same steps which have mentioned above for any  Tomcat issue

Note: After BODS installation on windows (BOE servers) sometimes we can see below error. It may happens on clustered environment


  • While performing above mentioned process make sure that clustered CMS need to be up and running in BOE

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member