CA Business Intelligence (CABI) performance tuning recommendations

Document ID : KB000010433
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

CA Business Intelligence (CABI) performance tuning recommendations

Background:

Some of the key components of the CABI are the front facing CABI Web Applications, like BI LaunchPad.  These are the applications that the front end users will interact with day to day. In order to make the day to day experience better for the end users, there are some best practice configurations that can be implemented on the CABI Tomcat application server.

Environment:
CA Business Intelligence 4.1All Supported Windows Operating Systems
Instructions:

Increase Memory Available to Tomcat

1.  Stop Apache Tomcat service via the Central Configuration Manager (CCM)

 

2.  Launch the Tomcat Configuration Program

memory_step1.png

3.  Under the Java Tab, increase the initial memory pool (1GB or 2GB is recommended). This is the memory that Tomcat will use when it starts.  Also increase the maximum memory pool to the value that best fits with that resources available on the CABI server.  Typically most organizations set the max value to either 4GB or 8GB.  In this example we are setting the maximum memory pool to 4GB.

Tomcat config.jpg

4.  Restart Apache Tomcat service via the Central Configuration Manager (CCM)

Delete CABI logs

1.  Stop Server Intelligence Agent (SIA) via the Central Configuration Manager (CCM)

2.  Via Windows Explorer, navigate to the CommonReporting4\SAP BusinessObjects Enterprise XI 4.0\logging directory on the CABI server

3.  Delete all unwanted log file (.GLF files)

4.  Start Server Intelligence Agent (SIA) via the Central Configuration Manager (CCM)

Clear CABI Cache

1.  Stop Server Intelligence Agent (SIA) via the Central Configuration Manager (CCM)

2.  Via Windows Explorer, navigate to the CommonReporting4\SAP BusinessObjects Enterprise XI 4.0\data directory on the CABI server

3.  Take a backup of the contents of the directory to another location outside of the CABI server

4.  Delete all contents of the directory

5.  Start Server Intelligence Agent (SIA) via the Central Configuration Manager (CCM)

Clear Tomcat Cache

1.  Stop Apache Tomcat service via the Central Configuration Manager (CCM)

2.  Via Windows Explorer, navigate to the CommonReporting4\tomcat\work\Catalina\localhost directory on the CABI server

3.  Take a backup of the contents of the directory to another location outside of the CABI server

4.  Delete all contents of the directory

5.  Start Apache Tomcat service via the Central Configuration Manager (CCM)

NOTE:  It might take some considerable time for Tomcat to fully initialize and rebuild its cache.  It is not uncommon for this process to take at least 30 minutes depending on hardware resources available on the CABI server

As always, we strongly recommend having a valid backup before any changes are made and to test all changes in a non Production environment first.

 

Additional Information: