Comments on: Web Intelligence Hangs, Allocate More Memory to Java

By: Improve Performance - Tweak - Hosts File - DNS Look-up | Business Objects Tips

Sat, 07 Aug 2010 03:36:52 +0000

[...] other day I answered a different article’s comment with a very brief mention of what I’ve been told by SAP-BO was a common tweak. The potential [...]

By: Julian

Julian — Thu, 15 Jul 2010 12:17:47 +0000

Hi MArcV, please see my response in this new article. Thank you for your question.

By: MarcV

MarcV — Wed, 14 Jul 2010 13:41:08 +0000

Julian,

Can you expand on the last comment? I would love to know more about it, as common tweaks should be… common? I have never seen that tweak mentioned anywhere.

Currently, we host everything on one server (yeah, I know). Should we enter the server’s name and IP in the hosts file as if it were on a separate machine? Using Tomcat for the app server, that would affect pretty much everthing that gets served up (logins, screen renders, WebI, Web Services…)

I’m all for speeding things up. What aspects would this affect? WebI/C Reports/LOV/???

Do you know of any consolidated source of “common tweaks”? I usually find one there here, one thing there… which means, you only know about the things that you might be researching if you’re noticing problems. Not knowing about Java having a poor implementation for DNS look-up, we might never have touched on that for our BOXI issues.

By: Julian

Julian — Tue, 06 Jul 2010 15:15:12 +0000

I have never really played with Xcelcius enough to have hit its limits; so I don’t have much advice on this. One thing occurs to me though, I have noticed on my Web Application Servers that are running BO Java applications that I get a good performance improvement (especially with logins) when I list the CMS servers in the Web Application Server’s hosts file. This is actually a common tweak that BO admins use, because of Java’s poor implementation of DNS look-up. I wonder if there is some way a similar addition to your hosts file would improve your performance.

By: John

John — Tue, 06 Jul 2010 15:06:12 +0000

Hei…We are using BO on SAP BW. We are caing some performance issues in Xcelcius wherein a BEx query that takes 5 seconds to execute in BEx is taking around a minute to execute in Xcelcius. The number of rows are about 500. When we did an analysis at Xcelcius side its seen that the actual data retrieval time is only 5 to 10 seconds..

Any pointers on where its taking the rest of the time.. Can it be the issue of a wrong java version.. if yes at server side or clent side??? If you are aware about the recommended java versions then that will also help..

By: Julian

Julian — Fri, 18 Jun 2010 11:24:47 +0000

Hi Chris, it sounds like a cached copy of the universe and/or LOV on the server(s) might be causing your troubles. If you could delete the cache on all effected servers you might resolve the issue. Additionally you might be able to make a small change to the universe and see if that forces the server(s) to flush out their cached copy.

By: Chris

Chris — Fri, 18 Jun 2010 00:52:47 +0000

Also, the issue does not arise with Deski..its only Webi..

By: Chris

Chris — Fri, 18 Jun 2010 00:51:36 +0000

Hello Julian,

Thanks for the reply..However, I want to shed some more light on the issue..I did check the object properties and the auto refresh option is unchecked..The second opinion you had was that of change in table data or indexes..even in that case, the LOV’ should take time to appear only the first time..from the second instance they should retrive these values from the FRS where they are stored..this is not happening..instead, whenever we try to run a report with a prompt, its hitting the database to get the LOV’s instead of getting the values from FRS..This happens as soon as we click on run query..and this is happening only with selected Universes…not all of them..I have checked the FRS location and the LOV file does exist for the object in question…

By: Julian

Julian — Wed, 16 Jun 2010 03:20:29 +0000

Hi Chris, LOVs based on objects are controlled at the object level (properties) in the universe. One option is to force an LOV to always refresh. It is possible that previously this option was set to not automatically refresh the LOV and now someone changed it. Additionally, LOVs are populated by SQL statements and those SQL statements could suddenly have reduced performance if the table data or indexes they are based on changes.

By: Chris

Chris — Tue, 15 Jun 2010 21:30:26 +0000

Hi Julian,

We have two Universes with several Prompts..When ever we are using any of these prompts in a Webi Report and run the query, the LOV’s are getting refreshed automatically…and they are taking about 4-5 Minutes to appear..We never faced this issue with these Universes before..It used to take a maximum of 30 secs for the LOV’s to Pull up..They are fine when we are using Deski..What might be the cause?? We are using XIR2..