Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
DayaJha
Active Contributor

Purpose:


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



Overview:


Environment Details:


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


Database: Microsoft SQL Server 2008 R2/Oracle 11.2.0.3


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

  • JavaHeapSize we should modify: 


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


 

modify setenv.sh

# set the JAVA_OPTS for tomcat


 











Code:



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"




 

  • Non- SSL we would modify:


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


 











Code:



    -->
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxThreads="150" URIEncoding="UTF-8"/>

<!-- A "Connector" using the shared thread pool-->

<!--

<Connector executor="tomcatThreadPool"

port="8080" protocol="HTTP/1.1"

connectionTimeout="20000"

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:



After doing changes:





  • 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













Code:



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


 


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



 

 


 


Reference Material:


YouTube Video: Splitting BI 4.0 Adaptive Processing Servers

http://youtu.be/2Uyi0V7RdwA

 

 

Best Practices for SAPBO BI 4.0 Adaptive Processing Servers 

http://scn.sap.com/docs/DOC-31711


SAP BI 4.0 Ecosystem how-to videos

http://scn.sap.com/docs/DOC-34251

 


Performance Optimization Guide - SAP Data Services 4.2:

 

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_perf_opt_en.pdf

 

 

Administrator Guide - SAP Data Services 4.2:

 

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_admin_en.pdf

 

SAP Data Services 4.2:


https://help.sap.com/bods


SNotes:


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

https://service.sap.com/sap/support/notes/1640036


 

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


https://service.sap.com/sap/support/notes/1580280


 

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


https://service.sap.com/sap/support/notes/1694041


 

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


https://service.sap.com/sap/support/notes/1452165


 

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


https://service.sap.com/sap/support/notes/1452186


 

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

https://service.sap.com/sap/support/notes/1644004


 

1529071 - Sizing how many RFC Servers you should use


https://service.sap.com/sap/support/notes/1529071


 

1544413 - Troubleshooting RFC Server - composite note


https://service.sap.com/sap/support/notes/1544413


 

1764059 - Troubleshooting RFC Server - can't find log file


https://service.sap.com/sap/support/notes/1764059

5 Comments
Labels in this area