To minimize the impact on performance when accessing an
LDAP server, assign performance settings to the IBM® WebSphere® Application
Server.
About this task
Configure context pools to minimize the impact on performance
by adding opened connections and contexts to internally maintained
pools and reusing them.
Procedure
- Log on to the WebSphere Integrated
Solutions console that manages the SIP Proxy/Registrar server as the WebSphere administrator.
- Click .
- In the User account repository section, click Configure.
- In the Repositories in the realm table, click the Repository
identifier.
- In the Additional properties section, click Performance.
- Select the Limit search time check
box.
- In the Milliseconds field, type 30,000.
- In the Context pool section, in the Initial
size field, specify 10.
- In the Preferred size field, specify 10.
- In the Context pool section, in the Maximum
size field, specify 20. Each context
is associated with one socket connection.
- Select the Context pool times out check
box.
- In the Seconds field, specify the
number of seconds to keep the idle connections in the context pool.
- If you have an idle connection time-out set in the LDAP server,
specify a smaller value in the Seconds field.
For example, if the idle connection time-out on the LDAP server is
set to 1 hour (3600 seconds), specify 3500 (seconds) in this field.
- If there is a firewall between the WebSphere Application Server and the LDAP
server, specify a value that is smaller than both the firewall's inactivity
time-out setting and the LDAP server's idle connections time-out setting.
- If the LDAP server is fronted by a load balancer, specify a value
that is smaller than both the load balancer's inactivity time-out
setting and the LDAP server's idle connections time-out setting.
- Click OK.
- Save the change to the master configuration by clicking
the Save link in the "Messages" box at the
beginning of the page.