Hello All ,

Was just reading through the white paper provided by Remedy for
Mid-Tier performance , in that they have mentioned :

1) arsystem.poolingmaxconnectionsperserver:
Should be set to the approximate number of expected concurrent
operations to a single AR System server.

2) arsystem.poolingmaxtotalconnections:
should be set to the approximate number of expected concurrent
operations to all AR System servers with which this mid tier
communicates.

Can anyone please tell us where these settings can be done ??

Thanks & regards,
Charu

Hello,

The file in question is the config.properties file located in the mid-tier
installation tree, such as (on Windows) "...\AR System\Mid-Tier\WEB-
INF\classes"

Be aware however, I suspect that the advice on the
poolingmaxtotalconnections parameter may be bad. I suspect that this
parameter is acting as a hard limit that results in any mid-tier user's
connection requests over and above it being queued by the mid-tier for
processing later. On Windows/IIS it showed as a growing number of idle IIS
threads and an inability for users to connect past a certain point. I got
much better results removing the "tuning" advice contained in that
whitepaper.

On the other hand, this may have been a problem only when combined with
bugs I suspect existed in mid-tier 5.1.1 related to expiring/time-out of
idle mid-tier sessions, addressed in 5.1.1 patch 1234. Patching or using
mid-tier 5.1.2 may make the idle session problem go away, in which case
presumably there may be a benefit to using the tuning parameters in the
white paper. If possible, load testing and measuring response time would be
ideal for your mid-tier application.

HTH,
Davin