We are having read timeout problems involvinfg several packages. So we started investigating what is the root cause.

We found that queries involving wMService, wMSession, wMError and wM tables are taking a long time.

Tables wMSession and wMService grew huge. Can we truncate these tables? What are the possible options?

Are there any guidelines for setup/configuration of this wM databases?

Review the IS Administrator’s Guide, the webMethods Logging Guide and the webMethods Database Guide. All are available on Advantage.

Look in WmMonitor/pub.monitor.archive. You can create wrapper services for the services in that folder and then schedule your wrapper services so the tables are archived periodically. You can also clean up those tables from the Monitor console (ie. http://:/WmMonitor)

• Percio