Tuning the performance of Rational Asset Manager

For best performance, each application server should have its own local and index folders on a hard disk local to the computer. This should not be the same hard disk on which the application server or operating system is installed.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; in the Disk Storage section, set the Local folder and Index folder parameters.

The search engine can consider the popularity (for example, views and downloads) of assets to deliver more relevant search results; however, this can affect the performance of large repositories.

To disable popularity indexing, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; in the Performance Options section, clear the Enable popularity indexing checkbox.

It is important that the index folder resides on a dedicated drive that is not used for other purposes. Separating the local folder and index folder helps to ensure quick response times when searching for assets.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; in the Disk Storage section, set the Index folder parameter.

Frequently running the statistics index builder leads to poor performance. A default setting of 10 minutes is adequate for most environments.

To set the parameter, log in to Rational Asset Manager as an administrator and click Administration > Configuration; then, in the Job Schedules section, locate the Statistics index builder schedule and click Edit.

Subscriptions can be processed at custom intervals. For better performance, set this interval to a time when Rational Asset Manager experiences a relatively low workload.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; then, in the Job Schedules section, locate the Process subscriptions schedule and click Edit.

User and group information can be processed at custom intervals. For better performance, set this interval to a time when Rational Asset Manager experiences a relatively low workload.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; then, in the Job Schedules section, locate the User / group information update schedule and click Edit.

Review process notifications can be processed at custom intervals. For better performance, set this interval to a time when Rational Asset Manager experiences a relatively low workload.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; then, in the Job Schedules section, locate the Review process notification schedule and click Edit.

It's possible for a single user to exhaust all available sessions on a server. This might be the result of a poorly written script or a denial of service attack. To prevent against this possibility the default maximum sessions per user is set to 10. After a user reaches this limit they will not be able to create new sessions on the server.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration > Configuration; in the Performance Options section, set the Maximum number of sessions per user parameter.

When you submit an asset, Rational Asset Manager creates thumbnail images of artifacts that are attached to the asset. If the asset has many artifacts, submitting an asset can take a long time.

To disable the automatic creation of those thumbnails, log in to Rational Asset Manager as a repository administrator and navigate to Administration > Configuration; in the Performance Options section, clear the Automatically create featured content on asset submission checkbox.

By default, WebSphere Application Server will maintain up to 1000 sessions in memory. However, the Allow Overflow option is also selected, which indicates that additional sessions will be stored in a secondary session table. If you expect to have more than 1000 in memory sessions, you must increase the number for the secondary session table.

If you want to limit the number of sessions to prevent out of memory errors, make sure the Allow overflow checkbox is not selected and set the Maximum in-memory session count to an appropriate setting for your system.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers > Application Servers > Server types > Server name > Session Management > Maximum in-memory session count.

On a server with 4GB of memory is installed, you can specify two instances with a heap size of 1300MB, or one instance with a heap size of 2000MB. You must watch the system paging to make sure that there is enough memory available. If your server has 8GB of memory, then specify 2 instances with a heap size of 2000MB for each instance.

To set the parameter, log in to WebSphere Administrative Console and navigate to Servers > Server types > WebSphere application servers > Java and process management > Process definition > Java virtual machine > Initial heap size and Maximum heap size.

Note that this setting should be applied to the Rational Asset Manager servers. The required setting for the IBM Rational Team Concert™ server is 768MB and is the default value and the maximum setting is 2048MB. In a cluster, the IBM Rational Team Concert server may be installed on its own node if needed.

The default value for a session timeout in WebSphere Application Server is 30 minutes. Setting this value to a shorter time allows for more users, especially if you have many users making quick transactions. Setting this value too low might not allow users to upload very large assets. Remember that most users do not explicitly log out when they are done with a transaction: most sessions will exist until they timeout.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers > Server types > WebSphere application servers > Server name > Session management > Set timeout.

The default value for a write timeout from the server to a client in WebSphere Application Server is 60 seconds. Setting this value to a longer time may prevent failures when download files, especially if the client that is downloading the files has a slow connection or is making many requests.

To change the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers > Server types > WebSphere application servers > Server name > Ports > View associated transports (for the port that you are using for Rational Asset Manager; for example, 9080) > WCInboundDefault > HTTP inbound channel (HTTP 2) > Write timeout.

Your specific server environment or workload might benefit from one of the other garbage collection settings. See http://www.oracle.com/technetwork/java/gc-tuning-5-138395.html for more information on garbage collection settings.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers > Server types > WebSphere application servers > Server name > Java and process management > Process definition > Java virtual machine > Generic JVM arguments.

By default, WebSphere Application Server enables basic performance monitor infrastructure (PMI). Although PMI is a good tool for tuning an application server, for maximum performance, disable this feature after the server has been properly tuned. You must disable it for all instances and node agents.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Monitoring and Tuning > Performance Monitoring Infrastructure (PMI) > Server name > Enable Performance Monitoring Infrastructure (PMI).

Make sure that there are enough JDBC connections available to support all users that are logged into Rational Asset Manager.

To set the parameter, log into the WebSphere Application Server Administrative Console and navigate to Resources > JDBC > Data sources > <Rational Asset Manager data source> > Connection pool properties > Maximum connections.

Refer also to topic "MAXAPPLS and MAXAGENTS parameters" under DB2® tuning.

Refer also to topic "Maximum number of processes for AIX® and Linux" under operating system tuning.

WebSphere Application Server provides the ability cache commonly used prepared statements. If cached statements are being discarded, turn on PMI in WebSphere Application Server and increase the value.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Resources > JDBC > Data sources > <Rational Asset Manager data source> > WebSphere Application Server data source properties > Statement cache size.

Refer also to topic "Further Information for Tuning WebSphere Application Server."

Web container threads are used by the application server to handle requests. If you notice that the CPU of the server is underused, try increasing this number. If it is overused, try reducing this number. Do not set the web container threads above 50.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers > Server types > WebSphere application servers > Server name > Thread pools > WebContainer.

Minimum size: 15

Maximum size: 30

Web container threads are used by the application server to handle requests. If you notice that the CPU of the server is underused, try increasing this number. If it is overused, try reducing this number. Do not set the web container threads above 50.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers > Server types > WebSphere application servers > Server name > Thread pools > WebContainer.

Minimum size: 25

Maximum size: 50

Make sure that MAXAPPLS is set high enough to handle the number of JDBC Connection Pools that are specified in your application server. The MAXAPPLS setting must be greater than or equal to the JDBC Maximum Connections setting.

Setting location: Database parameters

Also refer to topic "JDBC Maximum Connections" under Application Server Tuning

The MAXLOCKS parameter indicates the maximum percentage of available locks within DB2 that an application can hold before escalating row locks to table locks. These table locks can result in deadlocks.

Setting location: Database parameters

The LOCKLIST parameter represents the available memory for locks in DB2. You can use the following formula to set this parameter in a specific environment:

LOCKLIST = [(512 * 64 * MAXAPPLS) / 4096]*2

Do not set this higher than the memory heap that is available to DB2. Setting location: Database parameters

If a single lock is stopping other transactions, this can result in a deadlock. To make sure this does not happen, set the lock time out to 60 seconds.

Setting Location: Database parameters

This will activate the Fast Response Cache Accelerator (FRCA).

Changing this parameter to 60 minutes will give users sufficient time to upload large assets.

Refer also to topic "Session Timeout" under Application Server Tuning

Changing this parameter to 60 minutes will give users sufficient time to upload large assets.

Refer also to topic "Session Timeout" under Application Server Tuning

Changing this parameter to 60 minutes will give users sufficient time to upload large assets.

Refer also to topic "Session Timeout" under Application Server Tuning

1. In the registry editor, navigate to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
2. Right-click Parameters, click New > DWORD Value.
3. Type MaxUserPort for the name of the DWORD value.
4. Right-click the value and click Modify.
5. Set the value to 65534.
6. Under base, select Decimal.
7. Reboot the computer.

1. In the registry editor, navigate to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
2. Right-click Parameters, click New > DWORD Value.
3. Type TcpTimedWaitDelay for the name of the DWORD value.
4. Right-click the value and click Modify.
5. Set the value to 30.
6. Under Base, select Decimal.
7. Reboot the computer.

hosts=local,bind4

no -o tcp_recvspace=65536
no -o tcp_sendspace=65536
no -o udp_sendspace=65536
no -o udp_recvspace=65536
no -o tcp_finwait2=60
no -o tcp_timewait=1
no -o tcp_keepidle=600
no -o tcp_keepintvl=10
no -o tcp_keepinit=40

no:  
tcp_recvspace=65536
tcp_sendspace=65536
udp_sendspace=65536
udp_recvspace=65536
tcp_finwait2=60
tcp_timewait=1
tcp_keepidle=600
tcp_keepintvl=10
tcp_keepinit=40

These commands can also be set on a per-tcpip-interface basis. Check the "lsattr -E -l en0" and if they are not set there, then AIX uses the "no -a" values.

smtctl -m off

Running the smtctl -m off command requires you to then run the bosboot command to make the change permanent. If you do not run bosboot you will lose the effect of running smtctl -m off after a system restart.

The two threads on each physical processor share a Level1 cache. If the threads are unrelated, they corrupt the other cache data, which can end up slowing down the overall throughput as the system waits for more memory fetches to refresh the cache. Consider making a couple of test runs with this on and off to see what setting is best for your workload.

ps -ef | grep yp

If the "netstat -an" shows many sockets in FIN_WAIT_2 state, this means “high connection rates occur” and will correspond to the “Address already in use” message that is in server logs.

"no -a | grep fin"

no -o tcp_finwait2=60

The "no" command is good until reset or until a reboot. To make it permanent, define it in /etc/tunables/nextboot.

This JVM is for the Rational Asset Manager server on WebSphere Application Server. From the WebSphere Application Server administration console, select Application Servers > RAM Server name > Java and Process Management > Process definition > Java Virtual Machine > Generic JVM arguments.

The parameter is -Xlp<size>. You should specify -Xlp with no size to enable the default large paging size. You can also set a specific size. For example -Xlp64 enables 64 KB pages.