Time-based event detection

When the PROCESSCONTROL and PROCESSACTION tables are set up properly, either automatically as a result of the business system calling into Event Manager or by manually adding records to these tables. Events can be reevaluated by starting the EventDetectionScheduleController.

The EventDetectionScheduleController is a Java™ class. Its main() method opens a socket on the server where it is run. After the socket is opened, you issue an EventDetectionCommand to tell the EventDetectionScheduleController how to interact with Event Manager on the server.

You can issue an EventDetectionCommand to do one of four things:
  • Start processing an event category, specifying an event category ID.
  • Cancel processing an event category, specifying an event category ID.
  • Get status on the EventDetectionScheduleController (for example, which event categories are currently being processed).
  • Shut down the EventDetectionScheduleController.
Using the EventDetectionScheduleController, you can detect events of different categories concurrently.
Five scripts are provided to process time-based event detection:
  • startScheduleController.sh
  • runEventDetection.sh
  • cancelEventDetection.sh
  • statusScheduleController.sh
  • shutdownScheduleController.sh
Here are some example usages for the scripts:
  • To begin processing events for LifeEvents category, run the following scripts:
    • startScheduleController.sh
    • runEventDetection.sh or runEventDetection.sh 1 -cycle 10000
      Note: the event category ID of LifeEvents is 1
  • To stop processing event for LifeEvents while continuing with other scheduled event detections, run the script cancelEventDetection.sh 1.
  • To stop processing all scheduled event detections and shut down the scheduler, run the script shutdownScheduleController.sh.
Note: if this is the first time you use startScheduleController.sh to connect to a server, or if the SSL signer on the server has been changed, you will be prompted to add the signer to your trust store in the console where the startScheduleController.sh runs when you schedule the event detection by running the runEventDetection.sh in a separate console.

Verify that the digest value matches what is displayed at the server, and type y to add the signer to your trust store. You only need to do this once as long as you are connecting to the same server and the SSL signer on the server has not been changed.


Last updated: 17 May 2017