Tuning The Access Gateway For Performance - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

For a command that the Administration Console can successfully send to the Access Gateway,
the page displays a Command Execution Details section with the name of the command and the
command results.
For a command that fails because the Administration Console cannot communicate with the
Access Gateway, the page displays the following additional fields:
Number of Tries: Specifies the number of times the command was executed.
Command Try Log: Lists each try and the results.
3 Select one of the following actions:
Delete: To delete a command, click Delete. Click OK in the confirmation dialog box.
Refresh: To update the current cache of recently executed commands, click Refresh.
4 Click Close to return to the Command Status page.
4.10 Tuning the Access Gateway for
Performance
Use the following information to improve the performance of your Access Gateway cluster.
Maximum Number of User Sessions: Currently, we recommend that you keep the maximum
number of user sessions per Access Gateway to 5000 sessions. If your Access Gateways are
exceeding this number or getting close to it, we recommend that you add another Access Gateway to
the cluster.
If you want to support more than 5000 sessions per Access Gateway, you need to modify the Java
memory parameters. For configuration information, see
LDAP Attributes: If you have policies that use LDAP attributes, configure the Embedded Service
Provider to obtain these attribute values at authentication. When a policy needs to be evaluated for a
user, the values are then available in cache. If the values are not in cache, an LDAP query must be
sent to retrieve them. If the user then accesses another resource that requires different LDAP
attributes, another query must be sent. For configuration information, see
Embedded Service Provider" in the
Identity Server Configuration: A number of the configuration options for the Identity Server add
authentication overhead. You need to balance possible performance enhancements with your needs
to enable these options. For example, limiting user sessions adds another check to the authentication
process. If your security model does not require limiting user sessions, you should not enable this
feature. For other configuration options that affect the performance of the Identity Server, see
"Tuning the Identity Server for
Guide.
Web Servers: Web servers or services can be a major cause of slowness because they are processing
the most information. You need to examine the content on the Web servers. If users are requesting
static pages with multiple images, performance should be improved by having the Access Gateway
cache these pages. For information on cache configuration options, see
Caching Options," on page
If your Web servers are serving dynamic content, you can upgrade your Web servers to faster
hardware, or you can add another server to the group of Web servers serving the dynamic content.
Novell Access Manager 3.1 SP2 Identity Server
Performance" in the Novell Access Manager 3.1 SP2 Identity Server
170.
Java Memory Allocations.
"Sending Attributes to the
Section 5.1, "Configuring
Access Gateway Maintenance 165
Guide.