The amtune-env file contains the following parameters to define the tuning options for an Access Manager deployment:
Access Manager tuning parameters
Installation environment tuning parameters
Application Server 8 tuning parameters
For a description of the Directory Server parameters, see Chapter 3, Directory Server Tuning.
The following table describes the specific parameters for tuning Access Manager.
Table 2–2 Access Manager Tuning Parameters
Parameter |
Description |
---|---|
Sets the tuning mode to one of the following:
Default: REVIEW |
|
Tunes the Solaris OS kernel and TCP/IP settings. Default: true |
|
Generates a script to tune the Directory Server that supports Access Manager. Default: true |
|
Tunes the Access Manager web container, which can be either Web Server or Application Server. Default: true |
|
Tunes the installed instance of Access Manager. Default: true |
|
Identifies the prefix for the amtune log file. If this parameter is set, all operations performed by the amtune scripts are logged. The location of the log file is determined by the com.iplanet.services.debug.directory parameter in the AMConfig.properties file. If this parameter is not set, information is not logged, and all output is sent to /dev/null. Default: amtune |
|
Specifies the percent of available memory used by Access Manager. Currently, Access Manager can use a maximum of 4 GB, which is the per process address space limit for 32-bit applications. Access Manager requires a minimum of 256 MB RAM. When you set AMTUNE_PCT_MEMORY_TO_USE to 100, the maximum space allocated for Access Manager is the minimum between 4 GB and 100% of available RAM. When you set AMTUNE_PCT_MEMORY_TO_USE to 0, Access Manager is configured to use 256 MB RAM Default: 75 The following values are derived from this parameter setting:
AMConfig.properties File Settings Notification thread pool settings: com.iplanet.am.notification.threadpool.size com.iplanet.am.notification.threadpool.threshold SDK cache maximum size setting: com.iplanet.am.sdk.cache.maxsize Session settings: com.iplanet.am.session.httpSession.enabled com.iplanet.am.session.maxSessions |
|
Sets the available stack space per thread in Java (Web container). The per thread stack size is used to tune various thread-related parameters in Access Manager and the Web container. Default: 128 KB Caution: Do not change this value unless absolutely necessary. |
|
Specifies whether session time-out tuning using the next three parameters is enabled. To enable, set to false. Default: true |
|
Sets the maximum session time in minutes. Default: 60 However, the default value might be different for your installation. If the session service is registered and customized at the any other level, the tuning will not apply. Setting this parameter to very high or very low values affects the number of active user sessions an Access Manager deployment can support, so this parameter is optional for tuning purposes. To use this parameter, AM_TUNE_DONT_TOUCH_SESSION_PARAMETERS must be set to false. |
|
Sets the maximum idle time for a session in minutes. Default: 10 However, the default value might be different for your installation. If the Session service is registered and customized at the any other level, the tuning will not apply. Setting this parameter to very high or very low values affects the number of active user sessions an Access Manager deployment can support, so this parameter is optional for tuning purposes. To use this parameter, AM_TUNE_DONT_TOUCH_SESSION_PARAMETERS must be set to false. |
|
Sets the maximum session cache time in minutes. Default: 2 However, the default value might be different for your installation. If the Session service is registered and customized at the any other level, the tuning will not apply. Setting this parameter to very high or very low values affects the number of active use sessions an Access Manager deployment can support, so this parameter is optional for tuning purposes. To use this parameter, AM_TUNE_DONT_TOUCH_SESSION_PARAMETERS must be set to false. |
The following table describes the Access Manager installation environment tuning parameters.
Table 2–3 Installation Environment Tuning Parameters
The following table describes the tuning parameters that you can set when you are using Application Server 8 as the Access Manager web container.
Table 2–4 Application Server 8 Web Container Tuning Parameters