1 / 164

Capture Server 4.4

Capture Server 4.4. For SharePoint 2010. Capture Server 4.4. In This Presentation Overview Requirements Installation Configuration Process Designer Capture Server Agent Capture Server Monitor Web Capture Release to Capture Server Test Capture Server Import Designer. Overview.

anevay
Download Presentation

Capture Server 4.4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Capture Server 4.4 For SharePoint 2010

  2. Capture Server 4.4 • In This Presentation • Overview • Requirements • Installation • Configuration • Process Designer • Capture Server Agent • Capture Server Monitor • Web Capture • Release to Capture Server • Test Capture Server • Import Designer

  3. Overview

  4. Capture Server Overview • Capture Server is an enterprise-friendly batch processing application. • A batch of captured documents follows a configurable Processconsisting of any number of Activities. • The Capture Server architecture provides scalability and flexibility to handle the most demanding business needs.

  5. Capture Server Overview • Most Capture Server activities occur with little or no manual intervention needed. • However, some activities can be configured so that they are managed manually by users. • For example, the activity named Capture Server Index is a manual activity that allows operators to use KnowledgeLake Capture or Web Capture to apply metadata to documents.

  6. Capture Server Overview • Releasing a batch to Capture Server: • A scan-only workstation scans documents then releases the batch to Capture Server, where it enters a fully automated process that requires no manual intervention. • Capture Server completes its work on the batch, and releases the documents in the batch to SharePoint. Release to Capture Server Scanner 1 Capture Server Release to SharePoint Repository Scan-Only Workstation 2 SharePoint Server

  7. Capture Server Overview • Indexing a batch from Capture Server: • A scan-only workstation scans documents then releases the batch to Capture Server, where it enters a process that requires the batch be indexed manually. • An index-only workstation retrieves the batch from Capture Server and indexes the documents. • The index-only workstation sends the batch back to Capture Server to complete the process. • Capture Server completes the process, and releases the documents in the batch to SharePoint. Capture Server 1 Release to Capture Server Scanner 2 Scan-Only Workstation Retrieve from Capture Server for Index Send Back to Capture Server Release to SharePoint 4 3 Index-Only Workstation SharePoint Server

  8. Capture Server Architecture • Capture Server consists of various components. • These components may exist on a single server in a Basic installation, or may be installed among multiple servers in an Advanced installation. • This architecture provides scalability, and the option to maximize efficiency regardless of the volume of documents. • Communication Server • Batch Server • Activity Server • Import Server • Image Processing Server • Agent Server • Index Client • Web Monitor • Web Capture

  9. Communication Server • The Communication Server is the hub of Capture Server, and is the only component that communicates directly with the Capture Server SQL database. • All other components of Capture Server communicate to the Communication Server

  10. Batch Server • The Batch Server analyzes and tracks Capture Server batches by talking with the Communication Server. • The Batch Server: • Locates queued jobs. • Assigns the appropriate activities for the batch to follow. • Tracks the progress of these jobs.

  11. Activity Server • The Activity Server calls the Communication Server for batches that need to be processed, then queues the batches to delegate them to Activity Workers housed on the Activity Server. • Activity Workers are executable files that perform the activities in the Capture Server processes. • You can install multiple Activity Servers throughout your enterprise, making Capture Server scalable for large volume requirements.

  12. Import Server • The Import Server is used for CSV or XML file imports and directory watchers. • The Import Server reads CSV and XML files, imports documents into a new batch, and assigns metadata to those documents. • Import jobs are created and configured with the Import Designer application.

  13. Image Processing Server • The Image Processing Server is a type of Activity Server that detects barcodes and patch codes for document separation and auto-population of index fields. • It also performs image cleanup with technologies such as deskew, border removal, page orientation, and despeckle.

  14. Capture Server Agent • Capture Server Agent is a tray application installed on all Capture Server servers. • Through the Communication Server, it monitors the Capture Server SQL database and allows an administrator to start and stop Capture Server components on that server.

  15. Index Client • The KnowledgeLake Index Client is a desktop application that is installed on user workstations. • Using the Index Client, the user can index documents and perform QA on Capture Server batches.

  16. Capture Server Web Monitor • The Capture Server Web Monitor is used by Capture Server administrators. • It allows administrators to: • Check the status of Capture Server and related services. • View errors and re-submit batches. • Remotely start and stop servers through the Agent Server.

  17. Branch Capture Server Web Service • Branch Capture Server is used in conjunction with Capture Server, typically in a remote or satellite office. • Users in the remote office release batches from KnowledgeLake Capture to Branch Capture Server. • The Web Service configuration is the path that Branch Capture Server will release batches into.

  18. Capture Server Web Capture • Web Capture permits users to scan and index documents from within a browser window. • Users can also perform document assembly, annotate documents, and perform ad-hoc scanning. • The Web Monitor and Web Capture components must be installed on an IIS Server.

  19. Process Designer • The Process Designer is used to configure Processes and register Activities with the various activity servers.

  20. Requirements

  21. Capture Server Requirements Supported Systems: • Microsoft Windows SharePoint Services 2.0 or Microsoft SharePoint Portal Server 2003 -or- Microsoft Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007 -or- Microsoft SharePoint Server (“SharePoint 2010”) -or- KnowledgeLake Imaging for SharePoint 2.x, 3.x, 4.xKnowledgeLake Imaging for SharePoint 2.x, 3.x, 4.x • Microsoft Windows Server 2003 or 2008 or 2008 R2 (32-bit or 64-bit) • Microsoft .NET Framework 4 • Microsoft SQL Server 2005, Microsoft SQL Server 2008 or 2008 R2, or Microsoft SQL Server 2012. NOTE: To use Web Capture, Microsoft SQL must be configured for mixed-mode authentication. • Internet Information Services 6.0 or 7.0 (for Web Capture, Web Monitor and Web Service) • Microsoft Windows XP, Windows 7, or Vista (for Index Client on client machines) • ASP.Net server role (Windows Server 2008) -or- ASP.Net enabled in IIS (Windows Server 2003) • IIS 6 Management Compatibility server role (Windows Server 2008) • Windows Authentication server role (Windows Server 2008)

  22. Capture Server Requirements Server Hardware Requirements: • 2.5 gigahertz (GHz) or faster dual core processor (quad core recommended) • 4 gigabyte (GB) RAM minimum, 6 GB recommended • 1 gigabyte (GB) hard disk space for installation files • Additional hard disk space large enough for batch creation and document storage

  23. Capture Server Requirements Index Client Hardware Requirements: • 2.5 gigahertz (GHz) processor or faster, dual core processor recommended • 1 gigabyte (GB) RAM minimum, 2 GB recommended • 100 megabyte (MB) hard disk space • 64 MB Video Card that supports 1024x768 resolution • TWAIN compatible device required for scanning Additional Requirements: • Internet Explorer 6.0, 7.0, 8.0, or 9.0 on workstations using Web Capture and Web Monitor

  24. Capture Server Requirements • Additional considerations apply when installing Capture Server on a Windows Server 2008 machine: • The Application Pool running any Capture Server Web Application must have the Managed Pipeline Mode configured to Classic.

  25. Capture Server Requirements • Additional considerations apply when installing Capture Server on a Windows Server 2008 machine: • In the Role Services section, you must also install: • IIS 6.0 Management Compatibility • ASP.NET • Static Content • Windows Authentication

  26. Capture Server Requirements • Additional considerations apply when installing Capture Server on a Windows Server 2008 machine: • The application pool identity account running any Capture Server web service needs to be included in the IIS_IUSRS group. • The IIS_IUSRS group is equivalent to the IIS_WPG group in Windows Server 2003. Read about installing Capture Server on Microsoft Server 2008 in Appendix 2 of the Capture Server 4.4 Administrator Guide, p 134

  27. Capture Server Requirements Configuring the Web Capture Silverlight Index Panel (1 of 4) • Client Access Policy for MSS (2010) • When connecting to an MSS (2010) site, the Web Capture index panel uses the Microsoft Silverlight™ 4 plug-in. • For Web Capture’s index panel to retrieve columns for SharePoint content types, a clientaccesspolicy.xml file must be added to the virtual directory for each web front end.

  28. Capture Server Requirements Configuring the Web Capture Silverlight Index Panel (2 of 4) • Client Access Policy for MSS (2010) • Silverlight does not allow remote calls without extra configuration. To make remote calls to a SharePoint server a client access policy file needs to be placed in the appropriate virtual directory folder on each SharePoint web front end. • This article explains why: http://msdn.microsoft.com/en-us/library/cc645032(VS.95).aspx • This article explains how: http://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx

  29. Capture Server Requirements Configuring the Web Capture Silverlight Index Panel (3 of 4) • Client Access Policy for MSS (2010) • Here is an example of the XML: <?xml version="1.0" encoding="utf-8" ?> <access-policy> <cross-domain-access> <policy> <allow-from http-request-headers="*"> <domain uri="*" /> </allow-from> <grant-to> <resource path="/" include-subpaths="true" /> </grant-to> </policy> </cross-domain-access> </access-policy>

  30. Capture Server Requirements Configuring the Web Capture Silverlight Index Panel (4 of 4) • Client Access Policy for MSS (2010) • To apply the required XML file in the proper configuration, enable and run the KnowledgeLake Client Access Policy Deployment timer job from Central Administration. • The XML file will need to be customized to suit the security requirements at your location. • In the KLU SharePoint 2010 training environment, the clientaccesspolicy.xml file is found on the SharePoint Server at: C:\inetpub\wwwroot\wss\VirtualDirectories\80 Read about the Client Access Policy in the Capture Server 4.4 Administrator Guide, p 29

  31. Installation

  32. Installation • Use Existing Communication Server or Select Next

  33. Installation • Nota Bene: • Installation of Capture Server must be performed by a user with the “SecurityAdmin” and “DBCreator” roles in Microsoft SQL Server. • You can do an installation with all Capture Server components on a single server, or an installation with selected components installed on multiple servers. The license you purchased from KnowledgeLake determines what installation type you can successfully use.

  34. Installation • Run KL_CS.exe. • An extraction utility window opens. • Enter a destination for the Capture Server setup files. • You may keep the default location on the desktop, or browse to a location of your own choosing. • Select whether or not you would like to Launch Setup When Finished  • Click Extract.

  35. Installation • Click Yes when prompted to create the destination directory. • The extraction process will begin.

  36. Installation • The extraction process begins…

  37. Installation • …and will prompt you when the extraction is complete. • Click OK to continue the installation. • Wait a moment for the installation to begin automatically.

  38. Installation • Select Basic Capture Server for your installation type. • Click Next to continue.

  39. Installation • Accept the terms of the license agreement. • Click Next to continue.

  40. Installation • You may keep the default installation directory or define one of your own choosing. • Capture Server components that will be installed are listed. • If you use an existing Communication Server you will not select this option. • Click Next.

  41. Installation • The installation proceeds in the usual manner, and will run for several minutes.

  42. Installation • You are notified when the installation is complete. • Prior to using Capture Server, you must run Capture Server Configuration. • If you want to run it immediately, leave  Launch Configuration checked prior to clicking Finish. • If you choose to not run configuration after the Capture Server installation is complete, Configuration may be launched at any time from the Start menu, in the KnowledgeLake program group. • Click Finish.

  43. Configuration

  44. Capture Server Configuration • The Capture Server Configuration Utility is launched immediately when you click Finish, after the component installation sequence is complete… • …unless you unchecked the box for Launch Configuration at the final step of the installation For complete instructions on configuring Capture Server, see the Capture Server 4.4 Administrator Guide, pages 18-34

  45. Capture Server Configuration • Capture Server Configuration may be launched at any time after installation is complete. • Find it in the Start Menu of the computer running Capture Server, in the KnowledgeLake program group.

  46. Capture Server Configuration • Installation of Capture Server must be performed by a user with the “SecurityAdmin” and “DBCreator” roles in Microsoft SQL Server.

  47. Capture Server Configuration • Capture Server Configuration takes you through a series of screens where you set up the unique details of your installation.

  48. Capture Server Configuration • Save Everything: In order for Capture Server to function correctly, you must click Save for all components. • Components that need to be saved display a red icon in the bottom-right of the Configuration Utility. • After initial configurations have been saved for the current component, the icon will change to green.

  49. Capture Server Configuration • Configure the Communication Service Database • Your first step is to configure the KLCaptureServer database in Microsoft SQL. • This must be completed before other components appear in the configuration. • Enter the name of the Database Server (your “SQL box”), and a password for the KLCaptureServer_User. • Click Validate Database first, which will create the user and present a success message, then click Save.

More Related