Introduction
Purpose
The purpose of this document is to provide information to support:
daily operations, by clearly describing all the tasks which need to be carried out to keep the Universal Messaging system running and thus prevent unplanned outages
special operations, e.g. outage planning and all special tasks from shutdown to startup
monitoring, by describing different KPIs to be tracked to measure the performance and general health of the Universal Messaging system
troubleshooting, by ensuring that all required information is available. Especially in the case of problems that might arise, this document contains the information required by operations staff to recover from the situations and also collect diagnostic data required by the Software AG support team to find the root cause and recommend changes and/or prevent it from recurring.
all other active and proactive tasks, e.g. purging, archiving and other cleanup tasks performed to keep the UM system running within the expected performance limits, and prevent unplanned outages
Audience
This guide is intended for the IT team delivering a solution involving the Universal Messaging product, and the IT Operations team which manages the daily operations of a solution using the Universal Messaging product.