KnowledgeLake Branch Capture Server works in conjunction with Capture Server to enable all KnowledgeLake Capture products used in a branch office to aggregate, schedule and/or throttle content committal via the WAN into one secure, reliable and audited document delivery process. KnowledgeLake Branch Capture Server moves files to KnowledgeLake Capture Server where they are saved to Microsoft® SharePoint®.
Note: An instance of KnowledgeLake Capture Server 2010 (sold separately) is required in order to successfully install KnowledgeLake Branch Capture Server. Capture Server is the mechanism that processes batches, monitors Branch Capture Server and releases to SharePoint.
Create batches from multi-function devices, fax servers or any other interface.
- Ability to accept batches from KnowledgeLake Connect and from KnowledgeLake Capture before submitting them to Capture Server for file format conversion, release to SharePoint and other processing
- Batch import plug-in for comma delimited files, so that indexing information in CSV files is automatically included when batches are created
- Batch import plug-in for watching network directories, enabling any capture device to save image files to a shared network folder
- Caching mechanism, so that documents can be captured at full scanner speed in remote locations
Miscellaneous
Manage branch and home office resources most efficiently.
- Scheduled release of scanned documents to the centralized SharePoint server
- Ability to define a maximum bandwidth allocation—and schedule when the throttle occurs—so that document committal does not consume all available branch office bandwidth
- Audit trail for documents scanned in the branch office which are then delivered to and consolidated at the home office
Technical Highlights
- Lets you extend the power of Capture Server to remote offices
- Graphical AJAX interface to monitor the health and activity of the Capture Server
- Ability to schedule processing during off-peak hours
- Efficient binary protocol transfer
- HTTP connection without the need for any database calls
|
