Live Office pushing the limits

[Former Member]

We are trying to push the limits of what Live Office can extract as data and the number of concurrents users that can achieve it.

Here is how we proceeded.

1. The data that is being retrieved is about 28 fields and 9000 records.

2. We got the "Maximum character output size limit reached" error message so we increased the option "Maximum Character Stream Size " and "Binary Stream Maximum Size " on the webiprocessingserver to 50mb.

3. We then manage to use Live Office to download the data to Excel.

4. We now are having a problem with around 10 users (10 connections total) who try to refresh the data around the same time.

5. We get the "Web server out of memory " and "(LO 26315) Java Heap space (6315) " randomly from users...

6. The Apache server already has an "Maximum memory pool " and "Minimum memory pool " of 1024megs

We would like to know if there is any other thing we can configure to get multiple concurrent connections refreshing their report without any issues? With the amount of data that they are extracting and our current environment. We are not looking to get more like putting more CMS or processors. We are looking at finding the limitations of our system with LO and we think it's around the 9000 records we have achieved. We could be wrong...

I saw a post that says to look into the sizing document of LO which was a link to the admin guide, but couldn't find anything in there about how to test the limits with current environment settings.

Also, we would like to know what kind of data Live Office (from a Universe) can extract with multiple concurrent connections without any issues? 100 users refreshing 100 records? 200 users refreshing 50 records? Can 25 users refresh 1000 records? We would like to have examples of real life usage of Live Office without issues.

BOXI 3.1 SP3

LO SP3

Windows Server

Excel 2007

Thanks,

[Former Member · Accepted solution]

Hi,

I would say since you are getting the "Web server out of memory" which means your tomcat is not supporting the refresh, I would recommend to go for 64 Bit tomcat if you have 64 bit OS, so that you can bump the Java heap size to 4096 MB.

We had similar issue i.e. when 10-15 end users tried to refresh webi reports the tomcat was crashing we upgraded the tomcat now no issues.

if your webi server is crashing with out of memory, would recommend to have webi server groups created and divert the traffic on different webi servers so that the load is balanced.

Thanks,

aKs

[Former Member · Accepted solution]

Thanks for the answer.

Anyone knows how to calculate the size of a 9000 records on 28 columns report (query) on the server that is pulled from a Universe into Excel through Live Office?

I am interested in 3 type of sizes:

- Maximum Character Stream Size MB

- Binary Stream Maximum Size MB

- Java Heap Size MB

I got this formula for the Java Heap Size on SAP Notes but seems it's for BEx reports:

Memory = #result cells * 0.8 KB + #displayed cells * 5 KB

Any info would be appreciated.

Thanks,

BOXI 3.1 SP3

LO SP3

Windows Server

Excel 2007

Edited by: Sing Phommavong on Feb 7, 2012 1:24 PM

[Former Member · Accepted solution]

"if your webi server is crashing with out of memory, would recommend to have webi server groups created and divert the traffic on different webi servers so that the load is balanced."

Server out of memory is coming for the Tomcat web server, not the WEBI server.  But the idea is good...  so if we would like to add more Tomcat to load balance, is there a way to divert the Live Office traffic (port or dns, etc) to hit only say specific Tomcats?  So if one Tomcat goes down, it only affects Live Office traffic as all the rest of BO will not be brough down also.

Thanks,

[denis_konovalov · Accepted solution]

you can deploy just dswsbobje.war on additional tomcats and use special URL for the LO connections...

[Former Member · Accepted solution]

Is there a way to block the traffic on the non Live Office Tomcats?  So that when we try the URL in Live Office, we get an error message that it cannot find the server and such...

We know on the Webi Server, we cannot because it uses the same WEBI processes and config.  So any block/pass to Live Office, we would like to do it from the Tomcat.  Even if they are different services on the BO Servers, we would like to have multiple Tomcats but we only have one BO server.

Thanks.

[denis_konovalov · Accepted solution]

Do not know how to block this traffic on the tomcats, but you can simply undeploy dswsbobje.war on those...

[Former Member · Accepted solution]

Thanks Denis, especially for those quick replies.  We'll have to check what other services will be disabled if we undeploy dswsbobje.war...  If we only affect LO, that's great.

Thanks again.

[Former Member]

Greetings, we are looking at the same item for Live Office and was recently told by SAP that it should not be used for anything greater than 1000 rows.  Our current requirement is to pull down 90k rows.

Have you had a chance to expand your testing or find out any additional information?