Business Objects Tuning Servers


Business Objects administrators' job

In ordet to improve system performance, Business Objects administrators can  run load tests and also observe live/organic system performance over time.
Infact the better way to know for certain the impact of any tuning change is to compare the system’s performance before and after the change. This fact present problems on live production systems because the use of the system constantly varies in load volume and the kind of work being done.


Good  CMS Parameters 


Some Central Management Server (CMS) settings which given adequate hardware and database configurations, will almost always benefit all Business Objects XI systems. The first one:


CMS Cache

The cache is the first place you should focus. No CMS running on average server hardware will be harmed by pushing the memory cache parameter to the maximum and most systems will benefit. The only advise here is that if your system has limited memory (you will know by watching RAM utilization) you may steal away your BOXI server’s scarce memory which is being used by the CMS to process its very MANY queries.
 Increasing the maximum number of objects allowed in the CMS memory cache will reduce the number of database calls required and according to the “BusinessObjects Enterprise Adminstrator’s Guide” for BOE XI 3.1  in order to improve performance! 

There are two ways to configure this setting:


Changing the Business Objects Registry Parameter: MaximumObjectsToKeepInMemory


The registry is one place where the change can be made cleanly and hidden. It is more difficult for someone to change this setting, but it is also more likely to be forgotten and taken for granted when it is placed in the registry. Also, keep in mind, if you recreate a Server Intelligence Agent (SIA) then all registry values will be reset to default settings.
The key to change is under the CMS’s instance and it is named “MaximumObjectsToKeepInMemory“. 
It is set to 40000 by default. The upper limit, which you should be   100000. 


The CMS Command Line parameter: 

maxobjectsincache

The other place to enable this parameter is in the CMS server’s command line. This is a less conspicuous place to make the change and I believe that any change made here overrides the corresponding registry parameter. The parameter is called “-maxobjectsincache #” (the admin guide shows it in all lower caps but letter case does not seem to matter).


Note: The command line parameter will override the corresponding registry setting.

Starting CMC from command line

Comments

Popular posts from this blog

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

SAP HANA Introduction

SAP BusinessObjects 4.0 - Suite Presentation