Was performance tuning pre-preparation

http://www.ibm.com/developerworks/cn/websphere/library/techarticles/0707_wudan/#resources

was Application Server Environment Building Practice Guide

Http://blog.chinaunix.net/uid-20687159-id-1894968.html

Was performance tuning

Http://wenku.baidu.com/link?url=6pbNwpnXyJ8rCk-ciNVg_bRYGxyTlVXRtM0OlehhunLWTAo1MjWjZ_ Yy9vnshfxqnxrcbrzx4lkohkg163ijtqjcal5g9d0qulxr3b99bli

Http://tech.ccidnet.com/art/322/20030603/48448_1.html

http://yishueitian326.blog.163.com/blog/static/28586375200811127337921/

Several key parameter settings that affect the performance of was. Modifications to these parameters are required to restart the server before they take effect.

1. Maximum heap of JVM, minimum heap

2. Maximum and minimum value of Web container thread pool

3. JDBC Connection pool Maximum number of connections, minimum number of connections

Modification of parameters takes effect

After modifying and application related or server-related parameters on the console, you need to restart the server to take effect.

• If you are installing a Web server, reserve the disk space occupied by the Web server on the server where the Web server resides. IBM HTTP servers typically occupy about 110M of space.
• If you install a Web server, you typically also install the Web server plug-in component on the same machine as the Web servers, which takes up about 200M of disk space.
• The space occupied by the WebSphere Application Server system log. The estimation of log space should be combined with the system configuration of logs. The primary log for WebSphere Application server is Systemout.log,systemerr.log. We can set the size of the log file and the number of saved history log files, thus estimating the space needed. Refer to the "adjustments to the required parameters" section to learn how to adjust WebSphere Application server log parameters.
• If you have a Web server, consider the log space of your Web server. If the customer opens the Web server's access log access.log (which is turned on by default), the log grows very fast and reserves enough space.
• ? The space required to back up the file. The WebSphere Application Server provides a backup command (BACKUPCONFIG.BAT/SH) to back up the application server's configuration and its application. We recommend that you back up your system as soon as it is stable. For a typical production system, the WebSphere Application server configuration file often exceeds 100M. When issuing the Backupconfig command, use the-logfile parameter to specify where the backup file will be stored.
• System error Time log, for example, when the JVM occurs OutOfMemory, on most platforms the WebSphere Application server will default to write Javacore files and heapdump files, log the JVM Heap when the error occurs, the thread condition, in case of error diagnosis use. Although you can adjust the application server parameters so that they do not produce such files, it is often necessary to start with such files in order to analyze the problem. Such files are usually particularly large, such as heapdump files, which can reach hundreds of M. If Outofmemroy occurs more than once, the disk space is occupied very quickly. Therefore, you must consider reserving disk space for this type of file.

View was version

C:\users\hb>d:

D:\>CD program Files\ibm\websphere\appserver\bin

D:\Program Files\ibm\websphere\appserver\bin>versioninfo.bat
Wver0010i:copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved.
Wver0012i:versioninfo reporter V1.15.1.26, date 8/9/08

-------------------------------------------------------------------------------

IBM WebSphere Application Server product installation Status report
-------------------------------------------------------------------------------

Date and Time November 29, 2014 10:10 A.M. 11 SEC Report

Installation
-------------------------------------------------------------------------------

Product Catalog D:\Program Files\ibm\websphere\appserver
Version directory D:\Program Files\ibm\websphere\appserver\propertie
\version
DTD Directory D:\Program files\ibm\websphere\appserver\properties\
Ersion\dtd
Log directory D:\Program Files\ibm\websphere\appserver\logs
Backup directory D:\Program Files\ibm\websphere\appserver\propertie
\version\nif\backup
TMP Directory C:\Users\hb\AppData\Local\Temp

Product List
-------------------------------------------------------------------------------

BASE is installed

Products that have been installed
-------------------------------------------------------------------------------

Name IBM WebSphere Application Server
Version 7.0.0.0
Identify BASE
Build Level r0835.03
Build Date 8/31/08

-------------------------------------------------------------------------------

End the installation status report
-------------------------------------------------------------------------------

Start-Stop server, nodeagent, DM sequencing relationship:
Base version, you only need to start and stop the server. There are no components for nodeagent and DM, so there is no need to consider.

nd version of the words, to ensure that the startup: Start nodeagent after the server, stop: first stop the server and then stop nodeagent

D:\Program FILES\IBM\WEBSPHERE\APPSERVER\BIN>CD. View Java version

D:\Program FILES\IBM\WEBSPHERE\APPSERVER>CD Java/bin

D:\Program files\ibm\websphere\appserver\java\bin>java-version
Java Version "1.6.0"
Java (TM) SE Runtime Environment (build pwa6460sr2-20080818_01 (SR2))
IBM J9 VM (Build 2.4, J2re 1.6.0 IBM J9 2.4 Windows Vista amd64-64 jvmwa6460-20
80816_22093 (JIT enabled, AOT enabled)
J9vm-20080816_022093_ledsmr
Jit-r9_20080721_1330ifx2
GC-20080724_AA)
Jcl-20080808_02

D:\Program FILES\IBM\WEBSPHERE\APPSERVER\JAVA\BIN>CD. /..

D:\Program Files\ibm\websphere\appserver>cd Bin

D:\Program files\ibm\websphere\appserver\bin>serverstatus.bat-all//was deployed server state
admu0116i: File D:\Program
Files\ibm\websphere\appserver\profiles\appsrv01\logs\serverstatus.lo

Recording tool information in
admu0128i: Starting a tool with a APPSRV01 profile
Admu0503i: Retrieving server status for all servers
admu0505i: Locate the server in the configuration:
Admu0506i: Server name: Server1
ADMU0002E: An exception occurred while trying to process server server1: Javax.management.JMRuntimeExcepti
N:
ADMN0022E: Unable to getState the Server MBean due to insufficient credentials or empty credentials
For access.

D:\Program files\ibm\websphere\appserver\bin>serverstatus.bat Server1//Server1 Server Status
admu0116i: File D:\Program
Files\ibm\websphere\appserver\profiles\appsrv01\logs\server1\servers
Atus.log
Recording tool information in
admu0128i: Starting a tool with a APPSRV01 profile
Admu0500i: Retrieving server Status for Server1
Admu0508i:application Server "Server1" is STARTED

D:\Program files\ibm\websphere\appserver\bin>

Was performance tuning pre-preparation