This appendix lists properties in the amtune-env.properties you must modify and verify before running the amtune tool. After you have modified the file to suit your deployment, you can run the amtune tool.
See Using the amtune Toolfor usage details.
Based on this setting, the amtune tool will behave differently.
Suggests tuning recommendations only. In this mode, the amtune tool suggests tuning recommendations, but will not make any changes to the deployment environment.
Implements tuning recommendations. In this mode, amtune implements all of the tuning recommendations that you have defined in here, except for Sun Directory Server. See the note below for Sun Directory Server tuning.
Use extreme caution while using CHANGE mode. In CHANGE mode, the amtune tool may restart the web container on which OpenSSO is deployed. The amtune tool may also recommend a system restart when the operating systems kernel parameters are changed.
For Operating System kernel and TCP parameter tuning, the amtune tool tunes the operating system parameters only on Solaris and Linux. The amtune tool does not tune the operating system parameters on AIX, Windows, MacOS or BSD variants.
Sun Directory Server tuning requires extra levels of confirmation. The amtune tool assumes that OpenSSO Enterprise will use an existing Sun Directory Server in non-exclusive mode, although other applications may use Directory Server. If the Directory Server is installed on a remote machine, it will not be tuned automatically. If the amtune tool detects that the Directory server is installed on a remote machine, it creates an amtune.zip file for tuning the remote Directory Server. For more information, see To Tune a Remote Sun Directory Server in this document.
To selectively tune various components, see the section AMTUNE_TUNE_* section of this document.
On Windows, use a forward slash ( / ) for file separators. Example: c:/sun/webserver7
For tuning multiple data stores, execute amtune multiple times using different values for DS_* parameters and DIRMGR_PASSWORD.
Controls the logging of configuration data (calculated tuning values).
The output is only displayed on the terminal.
The output is displayed on both terminal and in amtune-config.<time stamp>.log file.
Check the <TOOLS_DIR>/<OPENSSO_URI>/logs/amtune-config.<time stamp>.log file for the tuning parameters and their recommended values from each run.
Specifies components to be tuned by amtune.
These settings work in conjunction with the AMTUNE_MODE parameter setting. You can review or change recommended tunings of any set of these components.
Only Solaris and Linux kernel and TCP parameters are supported for tuning.
Only Sun Directory Server is supported for tuning.
Only Sun Application Server 9.1, GlassFish v2, or Sun Web Server 7 are supported for tuning.
$WEB_CONTAINER and $CONTAINER_INSTANCE_DIR values do not have to be filled in.
True or False
Even if only AMTUNE_TUNE_OPENSSO is set to true, if Web Server 7.0 or Application Server 9.1 is the web container for OpenSSO, you must specify values for the following:
$WSADMIN_* or $ASADMIN_*
The amtune tool determines whether these containers are running in 32- or 64-bit JRE mode. The amtune tool restarts the server to check its JRE mode and to determine how much heap size is available for setting OpenSSO cache and session entries. For other web containers, the amtune tool supports only 32-bit JRE. For other web containers, set $AMTUNE_TUNE_WEB_CONTAINER to false. Also note the following:
$WEB_CONTAINER must be set to other.
$CONTAINER_INSTANCE_DIR should be left blank.
OpenSSO parameters will be tuned if the value for AMTUNE_TUNE_OPENSSO is set to true.
By default, the amtune tool runs based on the assumption that the following amount of memory (megabytes) is available for tuning OpenSSO when the web container (both Sun and non-Sun) is running with 32-bit JRE:
The amtune tool also tunes OpenSSO Enterprise when it is deployed on WebSphere 6.1 and 7, and on AIX, although it does not tune AIX system parameters or WebSphere container parameters.
Specifies OpenSSO web container name and version.
For Web Server 7 and Application Server 9.1, the amtune tool tunes JRE heap and per-thread stack sizes, JVM garbage collection algorithms, container worker or acceptor thread, and queue sizes.
For other web containers, the amtune tool does not change JVM or container-specific parameters.
$WEB_CONTAINER must be set to other. It is impossible to detect whether a null value is mistakenly set for Web Server 7 or Application Server 9.1, or is intentionally set for other web containers.
Specifies the OpenSSO web container instance directory.
If the you are using Sun Web Server 7 or Sun application Server 9.1, then this parameter is required.
If you have installed Sun Web Server or Sun Application Server in a non-default location, then change this value before running amtune.
On Windows, if a directory name has spaces, then use a short form such as E:/PROGRA~1/GLASSF~1.
The following parameters are required for tuning JVM options and container parameters of Sun Web Server 7.0.
Set the following parameters when $WEB_CONTAINER= WS7.
Specifies Sun Web Server 7 installation location.
Yes, when $WEB_CONTAINER=WS7
Specifies Sun Web Server administrator.
admin ( Sun Web Server default)
Specifies Sun Web Server administrative host name.
Specifies Sun Web Server 7 administration port.
8989 (Sun Web Server default)
If this port is a secure port, set the $WSADMIN_SECURE value to --ssl=true.
If this port is not a secure port, set the $WSADMIN_SECURE value to --ssl=false.
Flag to indicate whether or not $WSADMIN_PORT is in SSL mode.
Specifies Sun Web Server instance name.
This sample value is the config-name for the default instance https-hostname.domain.com
If you have non-default config-name instances, for example https-test1, enter its config-name test1 here.
Specifies HTTP listener name.
http-listener-1 (Sun Web Server default)
These following parameters are required for tuning JVM options and container parameters of Sun Application Server 9.1 and GlassFish v2.
Set these parameters when $WEB_CONTAINER= AS91.
Specifies Sun Application Server 9.1 or GlassFish v2 installation location.
Specifies Sun Application Server 9.1 or GlassFish v2 administrator.
admin (Sun Application Server or GlassFish default)
Specifies Sun Application Server or GlassFish administrative host name.
Specifies Sun Application Server or GlassFish administrative port.
4849 (Sun Application Server or GlassFish default)
If this port is a secure port, set $ASADMIN_SECURE value to --secure.
If this port is not a secure port, leave the $ASADMIN_SECURE value blank.
Flag that indicates whether or not Sun Application Server or GlassFish is in SSL mode.
--secure (Application Server 9.1 or GlassFish v2 default)
Leave this value blank.
This value is usually set to server with the assumption that this Application Server 9.1 or GlassFish v2 installation is used exclusively for OpenSSO Enterprise
server (Default in Application Server 9.1 or GlassFish v2)
Specifies Sun Application Server HTTP listener name.
http-listener-1 (Default in Sun Application Server 9.1 or GlassFish v2)
Specifies whether Sun Application Server or GlassFish evaluates java security policies listed in the Application Server server.policy file.
false (Application Server or GlassFish default)
Do not modify this parameter setting unless it is a unique deployment requirement. Evaluating Java security policies can add a significant performance overhead.
Specifies the directory where the ssoadm command-line interface is located.
where <TOOLS_DIR> is the directory in which amtune.zip is unzipped, and <OPENSSO_URI> is the deployment URI of OpenSSO.
Specifies administrator of OpenSSO 8.x.
amadmin (Default in OpenSSO)
Specifies OpenSSO URL.
http://<HOST_NAME>:<PORT>/<OPENSSO_URI> (OpenSSO Enterprise default)
Realm names for which user data store LDAP connection pool need to be modified.
Use the pipe ( | ) character as a delimiter for multiple realms.
For all the data stores under each realm, minimum and maximum LDAP connection pool sizes will be tuned.
The parameters in this section are for tuning a Sun Directory Server instance where a user management or service management and configuration data store is installed. When the Directory Server instance is on a remote computer system, after amtune.zip is copied over and unzipped, amtune validates parameter values only on that remote computer system.
Specifies Sun Directory Server fully qualified domain name (FQDN ).
Enter the official host name; do not enter an alias.
Specifies Sun Directory Server port.
Specifies the root suffix of the organization.
Specifies Sun Directory Server instance location
Use a forward slash (/) for file separators on Windows Systems.
Sun Directory Server dsadm/dsconf tools bin directory.
Use a forward slash (/) for file separators on Windows Systems.
Sun Directory Server version.
5.2 or 6.3
Sun Directory Server 6.2 is not supported for tuning due to its data corruption issues.
Directory Manager BIND DN for $DS_INSTANCE_DIR.
cn=Directory Manager (Directory Server default)
The following parameters mainly are used internally by amtune.
Do not modify these parameters unless tests show significant improvement in performance.
Specifies a percentage value how much of the machine's available memory will be used by OpenSSO Enterprise.
0 to 100
Do not modify this percentage unless tests show significant improvement in performance.
OpenSSO Enterprise currently recommends at least 1 GB of RAM in deployment. OpenSSO can use a maximum of 4GB for 32-bit JRE. This is the per-process address space limit for 32-bit applications.
When you set AMTUNE_PCT_MEMORY_TO_USE to 100, the maximum space allocated for OpenSSO is the lesser of 4GB and 100% of available RAM for 32-bit JRE.
When you set AMTUNE_PCT_MEMORY_TO_USE to 0, OpenSSO is configured to use 256MB RAM.
This value is the driving force in tuning OpenSSO. The following values are derived from this setting:
Heap and new generation sizes.
Web Server thread pool and OpenSSO Enterprise authentication, user and service/configuration data store LDAP connection pools and session notification thread pool.
Maximum number of session entries.
For 64-bit JRE, the amtune tool limits the initial heap size (-Xms) to 12 GB for Web Server 7 and Application Server 9.1/Glassfish v2, although it can be increased manually to a bigger heap size, if the Solaris operating system has at least twice as much virtual memory (swap space) as the desired initial JRE heap size. There is no limit for the maximum heap size (-Xmx).
Using 64-bit JRE, the user session cache size and number of sessionsare calculated by the amtune tool, and can be many times of those calculated in case for 32-bit JRE, depending on the available memory. Be sure to review these numbers and determine whether or not they are appropriate .
These parameters are used to calculate the maximum and minimum heap sizes. Options include:
Do not modify these ratios unless tests show significant improvement in performance.
Web Server 7, Application Server 9.1 and GlassFish v2 use about 1/8 of the OpenSSO Enterprise JRE process heap size, leaving about 7/8 for OpenSSO Enterprise. You should change these ratios only for 64-bit JRE. For 32-bit JRE, keep the default values.
Specifies available stack space per thread in JVM. Per-thread stack size is used to tune various thread-related parameters in OpenSSO Enterprise and its web container. Options include:
Do not modify these values.
Maximum amount of memory that should not be exceeded for 32-bit JRE on different platforms. AMTUNE_MAX_MEMORY_TO_USE_IN_MB_X86 is used to limit the maximum JRE heap size on Linux installed on x86 hardware due to limitations on how much JRE heap size can be allowed even with 32-bit JRE.
AMTUNE_MAX_MEMORY_TO_USE_IN_MB_DEFAULT (for Windows)
Do not modify these values. If the maximum values are changed to higher numbers, the web container will not start on these platforms due to a JRE crash.