Kofax Capture - Manual (Page 7)

Kofax Reporting Administrator's Guide 7
Chapter 1
Overview
Kofax Reporting helps system administrators, business process managers, and other
stakeholders gain visibility into and take control of Kofax-managed business processes. This
product serves as the single conduit across many Kofax products, providing a centralized
storage of historical operational metrics and audit data. In this release, the following Kofax
products are supported:
▪ Kofax Capture
▪ Kofax Transformation Modules
▪ Kofax Front Office Server
Architecture
Kofax Reporting has a distributed architecture where one or more Kofax application sites
deliver information to a central reporting site. Between sites, the information is transported
in a message-based store and forward mode. Three possible transport mechanisms are
supported.
In all three scenarios, Kofax applications provide reporting data via API calls to the reporting
integration API. This API uses web service calls to feed the data into a local transport entry
point.
In the central site, the ETL agent uses web service calls to read data from the central transport
entry point. The data is then transformed and finally stored in the database.
HTTP Transport
The Kofax Reporting API (integrated in Kofax applications, such as Kofax Capture)
communicates with the central site via a message based protocol implemented over web
services. This diagram shows a distributed deployment, where two WSA (web service access)
components are inserted between reporting data producers (Kofax applications on site A)
and the data consumer (central reporting site). This scenario does not require any external
transport mechanisms.