Running The Notification Server

The Notification Server enables SmartBatch to notify Operators of events that take place in the SmartBatch environment. Typically, these events are created by the Executive Server. User programs and SmartAppLets can also create events by using the SmartBatch programmatic interface.

Notification Setup

The notification setup information must be supplied using the SmartBatch Administrator.  Anytime this setup information changes you should stop the ns.exe process using the Windows Task Manager.  It will automatically be restarted by the Executive Server the next time a notification event is created.  You can also stop the Notification Server by stopping the SmartBatch Executive Server Service.

Running The Notification Server

The Notification Server is started and stopped by the SmartBatch Executive Server.  When the Executive Server starts it will in turn start the notification server (ns.exe).  When the Executive Server creates a notification even it checks to make sure the notification server is running.  If it is not running, it will start it.  

Notification Server Processing

When an Operation completes processing, the Executive Server writes a notification event (if configured to do so) to the SmartBatch database. The Notification Server then reads these notification events and processes them according to the configuration. As it processes, it writes status information to the Notification Status window.  Notification events are written to the database by the Executive Server so that if there is any interruption in processing, the notification event is not lost.  At the same time the Executive Server raises an event in the Notification Servers application domain so that it knows it has notifications to process.

Notification Status Window

Note:  This window may not be visible depending on how the Executive Server is configured.  The Notification Status Window can be accessed via the Windows Tray (typically the lower right corner of the computer screen -- look for the red notification icon).

If no notification events exists, the Notification Status window shows that no notification events exits.  Processing will resumes when a Notification event is created.  Associated with each notification event is an Alert List and a message. The Alert List is a list of Operators to be notified. The Notification Server attempts to notify each available operator on the Alert List. It checks to see if the Operator can be notified based on the current day/time and the Operators availability as configured on the Manage Operators window. If the Operator is available, it is determined if notification is to be done by Page, Email or both. The message is sent to each Operator via the notification method configured. If an error occurs trying to notify the Operator, the attempt is retried. If the number of attempts is exceeded the Operator will not be notified. Once an attempt has been made to notify each Operator on the Alert List, the notification event is deleted. This processing continues for each notification event.