The purpose of this document is to improve performance of SAP Business Objects Data Services Management console 4.x.


Environment Details:

Operating system: Windows Server 2008 64 Bit/Red Hat Linux 2.6.32

Database: Microsoft SQL Server 2008 R2/Oracle

Web Application: Tomcat

SAP Business Objects Tools: SAP Business Objects Information Platform Services 4.1 SP2; SAP Data Services 4.2 SP1

Repository version: BODS 4.X

I got real problems with performance in SAP Business Objects Data Services Management Console. For instance, my real time services, Jobs & Adapters were opening very long time.

All Status in SAP Business Objects Data Services Management Console will take more time to load

In LINUX Operating System below are the settings:

  • Let’s modify the Tomcat setting, because by default they have low value.
  • JavaHeapSize (-Xmx) from 2G to 4G
  • MaxThreads from default (200) to 900
  • JavaHeapSize we should modify:

cd <boe/boips inst folder>/sap_bobj/tomcat/bin

modify setenv.sh

# set the JAVA_OPTS for tomcat


JAVA_OPTS=”-d64 -Dbobj.enterprise.home=${BOBJEDIR}enterprise_xi40 -Djava.awt.headless=true -Djava.net.preferIPv4Stack=false –Xmx4g -XX:MaxPermSize=384m -XX:+HeapDumpOnOutOfMemoryError -Xloggc:<bo_inst_folder>/sap_bobj/tomcat/logs/tomcat.gc.log -XX:+PrintGCDetails -XX:+UseParallelOldGC”

  • MaxThreads we would modify:

cd <boe/boips_inst_folder>/sap_bobj/tomcat/conf modify
Define a non-SSL HTTP/1.1 Connector on port 8080


<Connector port=”8080″ protocol=”HTTP/1.1″ connectionTimeout=”20000″ redirectPort=”8443″ maxThreads=”900″ URIEncoding=”UTF-8″/>

<!– A “Connector” using the shared thread pool–>


<Connector executor=”tomcatThreadPool”

  port=”8080″ protocol=”HTTP/1.1″


  redirectPort=”8443″ />


  • Cleaning of old installed patches and service packs from BOE/BOIPS. What does it mean?
    Just go to <boe/boips inst folder> and run ./modifyOrRemoveProducts.sh (for Linux):
    It is clear that i have many various installation on my server. But it is important to delete old installation!
  • Cleaning of log directory, in <boe/boips inst folder>/sap_bobj/tomcat/logs
  • Cleaning of logging directory, in <boe/boips inst folder>/sap_bobj/logging
  • Cleaning of Access Server old logs directory, in <boe/boips inst folder>/DataServices/conf/<Access Server Name>error<date>.txt & trace<date>.txt old logs
  • Cleaning of Job Server old logs directory, in <boe/boips inst folder>/DataServices/adapters/logs
  • Cleaning of old Adapter logs directory, in <boe/boips inst folder>/adapters/logs
  • Cleaning of old RFC logs directory, in <boe/boips inst folder>/
  • Deleting Trace-Files
  • Setting in Central management console to delete old logs of Data services older than 5 days

By Default:

By Default - DS Settings.png

After doing changes:

By Default - DS Settings I.png

  • Tuning APS, for start you can use CMC Wizard.
  • APS properties for tracing set to unspecified (-> means bo_trace.ini are used)

In Windows Operating System below are the settings:

  • Let’s modify the Tomcat setting, because by default they have low value.
  • JavaHeapSize (-Xmx) from 2048 to 4096
  • MaxThreads from default (200) to 900


set PATH=%PATH%;C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\

set JAVA_HOME=C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\

set JAVA_OPTS=%JAVA_OPTS% -Xmx2048m -XX:MaxPermSize=384m

Path: cd <boe/boips inst folder>/SAP BusinessObjects\tomcat\bin\setenv

Tomcat Settings.png

Path: cd <boe/boips inst folder>/SAP BusinessObjects\tomcat\conf\ server.xml

Maxuimum Thread.png

Best Architecture for Deployment of SAP Business Objects Data Services: 

There are many pros and cons for deployment of SAP Business Objects Data Services with SAP BOE 4.X, as per the Best practices below are the possible scenario

Possible Architecture.PNG

Reference Material:

YouTube Video: Splitting BI 4.0 Adaptive Processing Servers


Best Practices for SAPBO BI 4.0 Adaptive Processing Servers 


SAP BI 4.0 Ecosystem how-to videos


Performance Optimization Guide – SAP Data Services 4.2:


Administrator Guide – SAP Data Services 4.2:


SAP Data Services 4.2:



1640036 Added memory usage when splitting Adaptive Processing Server (APS) services


1580280 Adaptive Processing Server and Adaptive Job Server in SAP BI 4.0 are using high amounts of memory and are hard to manage and troubleshoot


1694041 – BI 4.0 Consulting:- How to size the Adaptive Processing Server


1452165 – How to increase the maximum memory pool for Apache Tomcat used by Management Console – Data Services / Data Integrator


1452186 – What is the maximum memory pool limit for Apache Tomcat used by Management Console? – Data Services / Data Integrator


1644004 – Enable or disable RFC Server trace logging (traces DQM traffic between SAP & DS)


1529071 – Sizing how many RFC Servers you should use


1544413 – Troubleshooting RFC Server – composite note


1764059 – Troubleshooting RFC Server – can’t find log file


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. jassy pang

    HI,Daya,The management console of data services is very slow. I have to wait about 20 minutes to access it .Each time I restart the server ,the management console become fast untill about 4 days later,it is back to be slow.Could you have some good ideas?

  2. Daya Jha Post author

    Hi Jassy,

    Could you please check confirm are you using Tomcat as a web application sever, If Yes then as per your H/W change the configuration.

    Launch the Tomcat Configuration program from the Windows start menu.

    Increase Initial memory pool, Maximum Memory Pool & Thread Stack Size as per the H/W.

    Reference Link:-



Leave a Reply