Tuning tips
Tuning tips provide advice for selecting configuration settings.
You can also search for tuning tips by title or by using key words.
Subtopics
Advice configuration settings
Use this page to select the advice you wish to enable or disable.Application profiling performance considerations
Application profiling enables assembly configuration techniques that improve your application run time, performance and scalability. You can configure tasks that identify incoming requests, identify access intents determining concurrency and other data access characteristics, and profiles that map the tasks to the access intents.Connection pool custom properties
Data access tuning parameters
For better application performance, you can tune some data access resources through the WebSphere® Application Server administrative console.Database performance tuning
Database performance tuning can dramatically affect the throughput of your application. For example, if your application requires high concurrency (multiple, simultaneous interactions with backend data), an improperly tuned database can result in a bottleneck. Database access threads accumulate in a backlog when the database is not configured to accept a sufficient number of incoming requests.DB2 tuning parameters
Read this topic for parameters that you can configure for better database performance.DB2 tuning tips for z/OS
DB2 Universal Database performance tips
You can easily adjust your system QSQSRVR prestart job settings to optimize the process of acquiring connections from DB2 Universal Database™ for IBM® i.Diagnostic alerts
In WebSphere Application Server Version 9.0 the Performance and Diagnostic Advisors are extended to provide more diagnostic alerts to help common troubleshoot problems.EJB method Invocation Queuing
Method invocations to enterprise beans are only queued for remote clients making the method call. An example of a remote client is an Enterprise JavaBeans (EJB) client running in a separate Java virtual machine (JVM) (another address space) from the enterprise bean. In contrast, no queuing occurs if the EJB client, either a servlet or another enterprise bean, is installed in the same JVM on which the EJB method runs, and on the same thread of execution as the EJB client.Internal tracing tips for WebSphere for z/OS
WebSphere Application Server traces can be extremely helpful in detecting and diagnosing problems.JDBC tuning tips for use with DB2
WebSphere Application Server uses JDBC prepared statement caching as a performance enhancing feature. If you are using this feature together with DB2® for z/OS®, be aware of the potential impact on the number of DB2 JDBC cursor objects available.JPA system properties
In addition to the settings that are accessible from the administrative console, you can set Java Persistence API (JPA) system properties by using command-line scripting.LE tuning tips for z/OS
Enabling xplink in the runtime environment and compiling applications with xplink enabled improves performance in z/OS V1R2.Location of executable programs tips for z/OS
If you choose to not put most of the runtime in LPA, you might find that your processor storage gets a bigger workout as the load increases.Object and file security
This topic discusses the various objects and files that contain sensitive information and need to be protected.Object Request Broker tuning guidelines
Use the guidelines in this document any time the Object Request Broker (ORB) is used in a workload.Performance advisor report in Tivoli Performance Viewer
View recommendations and data from the performance advisor in Tivoli® Performance Viewer by clicking the Advisor link in Tivoli Performance Viewer for a server.Performance and Diagnostic Advisor configuration settings
Use this page to specify settings for the Performance and Diagnostic Advisor.processStats script
The processStats script collects and summarizes Performance Monitoring Infrastructure (PMI) data, saving the results to a text file. This file is imported into the IBM Systems Workload Estimator as the basis for a WebSphere Application Server estimate.PropFilePasswordEncoder command reference
The PropFilePasswordEncoder command encodes passwords that are located in plain text property files. This command encodes both Secure Authentication Server (SAS) property files and non-SAS property files. After you encode the passwords, a decoding command does not exist.Resource Recovery Service (RRS) tuning tips for z/OS
Use these tips to tune your z/OS operating system to optimize WebSphere Application Server performance.Security tuning tips
Generally, two things happen when you increase security: the cost per transaction increases and throughput decreases. Consider the following security information when you configure WebSphere Application Server.Session management tuning
WebSphere Application Server session support has features for tuning session performance and operating characteristics, particularly when sessions are configured in a distributed environment. These options support the administrator flexibility in determining the performance and failover characteristics for their environment.Secure Sockets Layer performance tips
Use this page to learn about Secure Sockets Layer (SSL) performance tips. Be sure to consider that performance issues typically involve trade-offs between function and speed. Usually, the more function and the more processing that are involved, the slower the performance.Tuning parameter custom settings
Use this page to customize tuning parameters for distributed sessions.Tuning parameter hot list
The following hot list contains recommendations that have improved performance or scalability, or both, for many applications.Tuning parameter settings
Use this page to set tuning parameters for distributed sessions.Tuning sessions
UNIX System Services (USS) tuning tips for z/OS
Use these tips to tune your z/OS operating system to optimize WebSphere Application Server performance.Web services client to web container optimized communication
To improve performance, an optimized communication path between a web services client application and a web container are located in the same application server process. Requests from the web services client that are normally sent to the web container using a network connection are delivered directly to the web container using an optimized local path. The local path is available because the web services client application and the web container run in the same process.Work area service performance considerations
Workload management (WLM) tuning tips for z/OS
You can use the administrative console to provide the job control language (JCL) PROC name for the servant and the JCL Parm for the servant and thereby set up a dynamic application environment. Even if you set up a dynamic application environment, you must set the WLM goals for your environment.z/OS operating system tuning tips
There are several configuration changes you can make to z/OS system components that might improve product performance.


File name: welc_ref_adm_tuning.html