Business flow

The following steps describe the business flow for integrating the CAP Gateway for Honeywell:

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

BlackBerry AtHoc

database queue.

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

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.

For all entries that are In Progress, the agent determines which alert template (scenario) needs to be published for the incoming event code, 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.