BO4 - Optimum number of webi processing servers - number of connections exceeded

[former_member272336]

Hi,

We had situation where the number of connections was being execeeded.

Had 4 webi processing serevsr (2 on each node) with 50 connections each.

Each has max memory threshold of 9gb ram.  Each node 24gb ram in total.

When look on machine generally under 10gb ram being used at any time so considering another webi processing server.

We have upped max number of connections to 70 on each webi porc server and advised users to cleanly logout of system to hopefully free up more sessions and therefore connections.

We also plan to reduce session timeout to 30 minutes  and idel connection timeout.

Were higher but being advised no reports taking over 30 minutes

Thoughts and any advice for us optimising number of connections avaiable

Thanks

[Former Member · Accepted solution]

ARe you still getting errors intermittently of maximum connections reached?

You can actually see the number of connection in each servers metric which would help to know whether the load is being transffered appropriately.

Are we confident that the load is not very high at any given point of time? I suspect that the issue would possibly be due to connections not getting released. Keep a tab on the health of connection / wip servers.

[former_member272336 · Accepted solution]

Hi,

Thanks for all advice - appreciate your points.

sizing done by consultants and recommendation was 9gb ram.

Where is the number of connections metric on teh webi processing server.

When look at server metrix on the wips don't see number of connections - see number of sessions - is this it?

Could add more wips but advise to have each uniform memory -size.

Generally on server looks to be plent of memory available so could add another wips but is there any danger if each configure for max memory threshold of 9gb ram and have 2 already on the 24gb ram server, this could take it above threshold.

What would you recommend re idle connection timeout - ours currently quite high 120 minutes - in process of adjusting session timeout to 30 minutes so would you alos suggest taking this down to 30 minutes to  improve recycling of connections?

Thanks

[Former Member · Accepted solution]

When you right click on WIPS, select Properties, you should see the 'Maximum connections'.

And looks like your Idle connection timeout is too high - Reduce that to 60 minutes.

[former_member272336 · Accepted solution]

Hi,

Thanks for reply - given our ssesion timeout in our web.xml is being set to 30 minutes propse to reduce our idle connection timeout to same as assume no point in having it higher than session timeout?

Woudl you agree?

Thanks

[Former Member · Accepted solution]

i will not agree for that.

Idle Connection Timeout (minutes): it is for WIPS

Specifies the amount of time, in minutes, that the server waits for a request from an idle connection. Setting a value that is too low can cause a request to close prematurely. Setting a value that too high can caused requests to be queued while the server waits for idle requests to be closed.

Default value is 20 (minutes)

Session Timeout in (web.xml): this is for the Web application server/Tomcat

This will be for the Web application server/Tomcat timeout. Tomcat session will be activated from the user logged into the Launchpad and keep for 30 Mins

[former_member272336 · Accepted solution]

Thanks for reply.

[former_member272336 · Accepted solution]

Hi,

Ther is property on the wips of max number of connections but what metrics when right-clcik and select metrics shows the number of connections being used.

There is a number of sessions but donnot see any number of connections.

Thanks

[Former Member · Accepted solution]

Please check the METRICS SPECIFIC TO THE WEB INTELLIGENCE PROCESSING SERVER in the below to have brief on the server metrics.

SAP note 1772632 - Explanation of Server Monitoring Metrics for SAP BusinessObjects Business Intelligence 4.0

[former_member272336 · Accepted solution]

Hi,

Thanks for note - really useful.

Looks like no specific number of connections metric to try and see number of connections being used by the webi processing server to see if has hiot the max number of connections.

Thanks

[Former Member · Accepted solution]

Current number of active sessions will give the number of connections begin used in webi processing server.

you can create a watch in the monitoring, T0 you by mail when it reaches near to your Max connection setting in the WIPS.

[former_member272336 · Accepted solution]

Thanks again for advice.

On equestion - there are monitoring watches that come out of box.

If adjust the number of connections - does the watch get automatically adjusted?

[Former Member · Accepted solution]

No, we have to change the Caution value or Danger value manually by selecting the the respective watch

[former_member272336 · Accepted solution]

Hi,

Thanks for reply.

[Former Member]

Default Max connections fro the WIPS is 50, however, the recomended value is 25.

but in your case it was set to 75. some time anyone of the WIPS may spike up and consume full memory and server resources.

I would suggest you to have more WIPS have 25 connections each to perform better

Seems like your system is not sized properly.

You should do a sizing exercise to determine proper number of webi report servers and their max connections settings :details are here :

http://www.service.sap.com/sizing

[former_member136842]

Hi,

i`m also more a fan of having less connections per WIPS but therefore more WIPS per Node. Also 9GB of RAM assigned for each WIPS is quite a lot.

I would create more WIPS with the default connection setting of 50 per process and assign 4 GB of RAM.

But i think you will get lots of different opinions here.

Regards

-Seb.