Today, EMC announced new releases of EMC Captiva products (i.e. EMC Captiva InputAccel 6.0 and EMC Captiva Dispatcher 6.0). I want to address the benefits of service-oriented infrastructure related to capture as embodied by these new releases.
The big deal with SOA and InputAccel 6.0 (IA6) is the connectivity it enables with other enterprise applications.
Capture depends heavily on validation of the captured data so access to systems that can supply information based on an extracted value or can perform the validation of extracted values is necessary. Service-orientation in IA6 lets capture be part of a company’s composite TCM applications.
Prior to the release of IA6, capture systems “connectivity” was restricted to ODBC, dropping files on file shares, and/or duplicating validation rules in software.
Another potentially big deal is the exposure of Captiva’s capture functionality to other applications (e.g. a web service for importing data into Captiva).
Today Captiva takes (captures) data from scanners, email, fax machines and legacy systems using specialty importers and file shares. Using web services will reduce complexity by allowing for a single method to be used to take in data from all kinds of systems.
Capture processing tends to occur in large batches; so, the “queue” behavior of a file share is useful. However, it lacks a handshake when the data has been picked up.
A web service would be more likely to be used by an interactive process or could be used as a call-back with the file share method to give a handshake.
It will be interesting to see how service-orientation within capture takes hold.
I want to thank my colleague, Clay Mayers, Captiva CTO, for contributing to this post. (Ah, another potential CMA blogger target… )