This article provides recommended procedures for maintaining and monitoring IBM Lotus Sametime Gateway.
Log files life-cycle and maintenance
To specify the maximum size and number of log files to be stored on the server see "Setting log file size and rotation" in the Lotus Sametime information center.
Make yourself a calendar appointment for renewing any SSL certificates in usage.
Renewing process: http://www-10.lotus.com/ldd/stwiki.nsf/dx/how-to-renew-the-ssl-cert-for-a-sametime-gateway-server
How to monitor the STGW communities connection on/off runtime status:
What is the recommended periodic maintenance for the Sametime Gateway DB2?
The DB is used to hold the system configuration.
The DB might also be used to save IM and Awareness events if the Sametime Gateway Event Plug-in is enabled. If the Event Plug-in isn't in use, there's no periodic DB maintenance needed.
If the Event Plug-in is used, by default it's not, one should create a DB process to periodically remove old records to prevent the DB from running out of space.
What is the recommended periodic recycling of the Sametime Gateway Websphere processes?
A process restart might be carried out every 1-2 months.
Dependant on your redundancy topology and high-availability settings, following a server restart, the system will require time to regain awareness back..
What is the recommended periodic file system cleanup of the Sametime Gateway Websphere nodes?
See how to set log files size and rotation here: http://publib.boulder.ibm.com/infocenter/sametime/v8r0/topic/com.ibm.help.sametime.802.doc/Gateway/rtc_tuning_logsize_rotation_t.html
Upon a Websphere application server crash, trace and dump files will be automatically created in the relevant Websphere server profile directory:
(For example: "C:\Program Files\IBM\WebSphere\AppServer\profiles\RTCGW_Profile\")
These files are important for troubleshooting purposes, and should be allowed to be created. On the other hand, they tend to be quite big (~1GB) and should be deleted from the file system if not needed (a more than a week old file is a good candidate for deletion).
The files to be deleted have a contestant file name pattern, for example: name pattern: