Enterprise Administration > Windchill ESI > Administering Windchill ESI in an ORACLE Applications Environment > Guidelines for Monitoring, Diagnosing, and Resolving Problems > Monitoring Problems > Monitoring with BusinessWorks > BusinessWorks Engine Problems > Suggested Deployment Configuration
  
Suggested Deployment Configuration
The following lists suggested actions that you can configure during deployment, for the various types of failures:
Any Failure: Raise an alert to the administrator
First Failure: Restart the engine
Second Failure: Restart the engine and raise a second failure alert
Subsequent Failure: Restart the engine and send e-mail to the administrator
A configurable counter and timer exists which determines when to reset the failure count to first. Use the timer setting on this counter to set to a particular time frame in which more than two failures in that time frame raises considerable concern about the system’s overall integrity.
1. Navigate down through the TIBCO Administrator GUI:
Application Management > <Application Name> > Configuration > Process Archive.par
2. Click the Monitoring tab:
3. Click the Add button under Events. The Add Event screen will appear:
4. Select the type of event you would like to monitor. For example, when a JMS queue fails, a process becomes suspended. You may configure an alert to monitor for a process suspension:
A systems administrator has the ability to restart the engine using TIBCO BusinessWorks Administrator. For more information, see JMS Problems.