A notification sink is a user-defined stateless session bean that
is called when the task changes state.
A notification sink bean uses the following home and remote interfaces,
which are defined in the deployment descriptor using an
assembly tool, such as the Application Server Toolkit
(AST) or Rational Application Developer:
com.ibm.websphere.scheduler.NotificationSinkHome
com.ibm.websphere.scheduler.NotificationSink
The bean itself needs
to implement the handleEvent() method defined in the remote interface. For
details, see the Interface NotificationSink section of the API
documentation and the Receiving scheduler notifications topic.
A NotificationSink
provides an event notification callback on a task-by-task basis. A notification
sink is set on the TaskInfo interface, using the setNotificationSink() method.
If a notification sink is not specified on a task, all notifications are lost;
however, the status of a task can be determined by calling the getStatus()
method from the Scheduler interface. A notification callback is made for each
of the following events:
- Scheduled
- Suspended
- Resumed
- Fired
- Firing
- Fire Failed
- Complete
- Purged