Troubleshooting
Problem
When deployment is running with heavy load of transactions, performance degradation may be seen. You may minimize the amount of information logged for better performance.
Resolving The Problem
For Production deployment or systems running under heavy load, you can adjust logging level for the WPG application servers, to minimize negative impact on performance caused by the amount of the information logged.
The WPG default log level is *=info:com.ibm.bcg.*=severe. Irrespective of the default value of installation, recommend to put the trace statement *=fatal for best performance for production heavy loading environments. Setting deeper level of tracing on production only when required per business choice, or when explicitly asked by IBM Support for problem analysis.
*=info:com.ibm.bcg.*=severe (default)
*=info:com.ibm.bcg.*=finest (recommended for development environments)
*=fatal (recommended for production deployment or systems running under heavy load)
[Change log level]
- Open the WAS administrative console.
- Click Troubleshooting > Logs and Trace
- Select server name that you want to work with.
(e.g. Simple mode: 'server1'; Simple distributed: 'bcgserver'; Full distributed: 'bcgreceiver' and 'bcgdocmgr' - Click Change Log Level Details.
- Click the Configuration tab. (To change the configuration dynamically, click the Runtime tab.)
- Change the logging statement by entering the trace string, as described above.
- Click Apply and OK to save the changes.
- Restart the server(s).
Product Synonym
WPG
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21596574