WebSphere Application Server (WAS) Profile Performance Templates

Answer

Tuning the application server using pre-defined tuning templates

The configuration settings applied by this script and the associated tuning templates should be viewed as potential performance tuning options for you to explore or use as a starting point for additional tuning. The configuration settings that each of the pre-defined templates applies are geared towards optimizing common application server environments or scenarios. Typically, these settings improve performance for many applications.

Because optimizing for performance often involves trade-offs with features, capabilities, or functional behavior, some of these settings might impact application correctness, while other settings might be inappropriate for your environment. Please review the following documentation and consider the impact of these settings to your application inventory and infrastructure.

As with any performance tuning exercise, the settings configured by the predefined templates should be evaluated in a controlled preproduction test environment. You can then create a customized template to refine the tuning settings to meet the specific needs of your applications and production environment.

The standard settings are the standard out-of-the-box default configuration settings that are optimized for general-purpose usage.

The production performance settings are optimized for a production environment where application changes are rare and optimal runtime performance is important.

The development settings are optimized for a development environment where frequent application updates are performed and system resources are at a minimum. Important: Do not use the development settings for production servers.

manageprofiles -create -profileName BenniePerf -startingPort 52250 -applyPerfTuningSetting peak                                  
   
INSTCONFSUCCESS: Success: Profile BenniePerf now exists. Please consult /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/<profileName>/logs/AboutThisProfile.txt for more information about this profile.                                                          $

To change the current template of an existing profile, use the wsadmin applyPerfTuningTemplate.py script.

1. Copy all objects from <WAS_home>/scriptLibraries/perfTuning/V70/ to <WAS_home>/bin/

cp <WAS_home>/scriptLibraries/perfTuning/V70/* <WAS_home>/bin/
<WAS_home> = /QIBM/ProdData/WebSphere/AppServer/v85/<edition>

<edition> = Express, Base, or ND

2. Change to the <WAS_home>/bin directory.

cd <WAS_home>/bin

3. Execute the applyPerfTuningTemplate.py script in the wsadmin environment.

wsadmin -host localhost -port <soap_port> -f applyPerfTuningTemplate.py -nodeName <name> -serverName <name> -templateFile <development.props/default.props/peak.props>

NOTE:  Specify only one templateFile from the list.

4. The server.xml file is changed.

cd /QIBM/ProdData/WebSphere/AppServer/v85/ND/bin
 
wsadmin -host localhost -port 52255 -f applyPerfTuningTemplate.py -nodeName RCHM199B_BenniePerf -serverName BenniePerf -templateFile peak.props  

Output:

WASX7209I: Connected to process "BenniePerf" on node RCHM199B_BenniePerf using SOAP connector;  The type of process is: UnManagedProcess                  
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[-nodeName, RCHM199B_BenniePerf, -serverName, BenniePerf, -templateFile, peak.props]"  

Completed parsing parameters...                                              
 templateFile - peak.props
 serverName - BenniePerf
 nodeName - RCHM199B_BenniePerf
 
resolving node and server targets...                                                                                                                
applying server level tuning parameters for server:                        
 ----------------------------------------------------------------------
 Cell:                 RCHM199B_BenniePerf  Type:            STANDALONE
 Node:                 RCHM199B_BenniePerf  Platform:             os400
                                            Version:            8.5.5.3
 Server:                        BenniePerf  Type:    APPLICATION_SERVER
 ----------------------------------------------------------------------                                                                            
 Applying tuning parameters using property based configuration...        
  Log File : /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/BenniePerf/logs/perfTuning.log                                                            
  Template File : /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/BenniePerf/logs/peak.props                                                          
  NOTE: Please consult the report.log file to review results of property
    based configuration.                                                                                                                                  
  Applying additional tuning parameters via normal wsadmin processing...                                                                                  
    Applying Datasource tuning parameters to Default Datasource  
    Applying Datasource tuning parameters to DefaultEJBTimerDataSource      
Server level tuning complete!                                                
Saving the configuration changes...                                      
NOTE: Server may require restart for all tuning changes to take effect.  
Script completed!                                                        
$  

Restarting the WebSphere Application Server will enable the new configuration changes.