Business flow

The CAP Feed Poller job fetches the CAP feed and creates a queue entry in the 

AtHoc

 database (EVT_QUEUE_TAB).

For performance optimization, the polling agent maintains the “last-time-stamp” of the most recent feed entry within the payload.

Every new feed is first filtered against “last-time-stamp” and only new entries are picked up.
In the new entries, de-duplication is done based upon a unique identifier to avoid duplicate alerts. The unique identifier is also linked to published alert attribute 
<auid>
 within 
BlackBerry AtHoc
 for future reference.

The CAP Event Processor job running in the background picks up new entries and marks the picked–up entries as In Progress (IPC).

For all entries that are In Progress, the CAP Event Processor agent determines which alert template (scenario) needs to be published for the incoming event type and event name, based on the configuration of the agent.

The alert template (scenario) is published and the event queue entry is marked as Done. If there is an error, the entry is marked as Error.

Each agent maintains a debug log, known as the 

AtHoc

 Event Viewer, that is used during troubleshooting.