Netscape Application Server uses an event notification system to inform you through email of critical situations. This is useful when you cannot actively monitor the server. By using event notification, the passive monitoring system saves you from having to watch the monitor chart to make critical assessments of the server, such as whether a process is running. The Monitor chart provides more detailed information, where as event notification provides necessary information.
About the Events for Which You Can Receive Notification
Event notification currently sends an email to an account you specify, for the events you specify. You can specify notification for the following critical events:
The event of a Netscape Application Server process going down is particularly critical because these processes must be running in order to support an application.
For an application written in Java, the Executive Server and Java Server processes must be running. If the application is written in C++, the Executive Server and C++ Server processes must be running.
If one or more of the Executive Server, Java Server, or C++ Server processes go down, the Administrative Server attempts to restart each downed process. If the process cannot be restarted by the Administrative Server process, the application stops running and can result in lost transactions. For more information about the Administrative Server restart procedure, see "About Increasing Fault Tolerance and Server Resources."
It is not easy to predict and prevent all situations that might cause a process to fail. Recurring failures are usually attributed to problems within the application code, but other failures can also happen. Regardless of what causes a process to fail, when it does happen it is useful to be notified immediately.
In addition to process failure events, you can also be notified when the Administrative Server has exceeded the number of times it has attempted to restart a process.
What to Do When You Are Notified
.
|
Previous
