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

Post a Comment

Popular posts from this blog

SAP HANA Introduction

Image
SAP HANA:The future of database technology The capacity of main memory in servers has continuously increased over the years, whereas prices have dramatically dropped. Today, a single enterprise class server can hold several  terabytes of main memory. At the same time, prices for server main memory dramatically  dropped over the last few decades. This increase in capacity and reduction in cost makes it a  viable approach to keep huge amounts of business data in memory. This section discusses  the benefits and challenges. In few words you can understand SAP HANA plus  analyzing this evaluation: Typical access speeds Disk     4,000,000 ns Memory         0.4 ns Speed   10,000,000 Falling prices move processing from Disk/SSD to In-Memory In-Memory Computing The elements of In-Memory computing are not new. However, dramatically improved hardware economics and  technology innovations in software has now made it possible for SAP to deliver on its vision of the
Read more

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

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=G-NL0CYP13VZ"></script> <script>   window.dataLayer = window.dataLayer || [];   function gtag(){dataLayer.push(arguments);}   gtag('js', new Date());   gtag('config', 'G-NL0CYP13VZ'); </script> Cannot find the BusinessObjects Enterprise report source. (LO 26608) Environment SAP BO XI 4.1 SP 5 two nodes Cluster Windows Server 2012 While refreshing dashboard (based on Live Office connection) from BI Launchpad with a no administrator user the above exception was erased. SAP says: Cause The document is not available; for example it does not exist, or it has been removed. Action Check the report path from CMS and use SetLocation in Live Office to re-define the report source. Otherwise, check if the user has sufficient rights to view the object. Solution In our case  we fixed this problem was to remo
Read more

FWM 01002 - Unable to reconnect to the CMS. The session has been logged off or has expired.

An error has occurred: Unable to reconnect to the CMS.  The session has been logged off or has expired. (FWM 01002) Environment BO XI R 3.1 SP 4 In order to solve this issue we found a  SAP released note 1422296  1422296 - Error:' Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' with BusinessObjects XI 3.1. Symptom Not able to schedule WebIntelligence reports. Reports fail with error:'Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Environment BusinessObjects XI 3.1. Reproducing the Issue Schedule a WebIntelligence report to run now. Reports fails with error:u2018Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Resolution 1. From Central Configuration Manager, disable all the services and re-enable them. 2. Log into Central Management Console and go to the server area. 3. Go to the properties of Central Man
Read more