PaperSave Enterprise Deployment White-Paper

Transcription

1 PaperSave Enterprise Deployment White-Paper An affiliate of Morrison, Brown, Argiz & Farra, LLP 1001 Brickell Bay Drive, 9 th Floor Miami, Florida Voice Fax

2 Introduction: PaperSave provides a complete and secure electronic storage system that seamlessly integrates into supported host information systems by attaching source documents relating to transactions or records within those systems directly to those records. Once documents have been associated with a given record, PaperSave allows for the instantaneous on-screen access to those documents. As a result any source document retained through PaperSave can be found instantly within the security confines of the host information system simply by navigating to the related record. PaperSave was designed with scalability in mind. It is a multi-tiered system that can consist of multiple application servers, multiple batch scanning servers, and multiple data servers. PaperSave also uses one of the most highly scaleable database engines on the market (Microsoft SQL Server), to host the database. All of these components can be installed in any combination on one or many machines. Please refer to the diagram in the PaperSave components interaction diagram section of this document. As a result, a successful PaperSave implementation requires a design that effectively uses the right combination of PaperSave components and physical hardware resources to most efficiently handle and fit within the customer's process/volume and environment. It is recommended that a PaperSave consultant from Solutions@MBA be involved in the design of any Enterprise implementation. PaperSave consultants can provide the proper guidance and expert advice on the PaperSave configuration and hardware required to meet a prospect's needs. The primary purpose of this whitepaper is to provide PaperSave enterprise customers/prospects and or their consultants with the proper guidance during the design of the environmental requirements necessary to support a successful PaperSave implementation. This white paper is broken up into two sections. The first section (PaperSave Enterprise Recommended Deployment Guidelines) describes scenarios/requirements that enterprise organizations are likely to encounter/have when maintaining/planning their PaperSave implementation, and the specific guidelines that govern those scenarios. The second section provides detailed hardware requirements for the machines and peripherals required to host/support PaperSave components/features. Please note that multiple PaperSave components can be installed on the same computer as long as the computer meets the recommended requirements outlined for the most resource intensive component installed on that computer. Exceptions to this rule are specifically outlined in the PaperSave Enterprise Recommended Deployment Guidelines section of this document. For more information or to ask specific questions, please contact your PaperSave representative, call (877) Paper-99 or send an to info@papersave.com. Page 2

3 PaperSave Component Interactions Diagram: Page 3

4 PaperSave Enterprise Recommended Deployment Guidelines: The following table outlines how PaperSave should be used under certain common Enterprise scenarios/customer requirements. Enterprise Customer Requirement Scenarios Customer needs to store a large volume (1 Million+) of PaperSave documents, or the documents stored within PaperSave have an average size of over 10MB+. PaperSave Deployment Recommendations by relevant component. Database Server: The customer will need either a dedicated machine for the PaperSave database server component or a dedicated IO system for the PaperSave database. A dedicated server will ensure that there is no contention for any database server resources between the PaperSave database & the host system's database. As an alternative, customers can use a Shared SQL Server as long as the PaperSave database is hosted on a dedicated IO controller. This will ensure that there is no IO contention between the host system's database and the PaperSave database. The customer requires high concurrent usage of the PaperSave database for both adding and retrieving PaperSave documents. This would be defined as the concurrent (not serial) retrieval or submission of 20+ documents at any given time. Wide Area Network/Multi- Site environment that is not using Thin-Client computing, but is instead connected via Private Point to Point lines, VPNs, or other WAN technology based on TCP/IP. Database Server: The customer will need either a dedicated machine for the PaperSave database server component or a dedicated IO system for the PaperSave database. A dedicated server will ensure that there is no contention for any database server resources between the PaperSave database & the host system's database. As an alternative, customers can use a Shared SQL Server as long as the PaperSave database is hosted on a dedicated IO controller. This will ensure that there is no IO contention between the host system's database and the PaperSave database. Database Server: The customer will need a machine to host the PaperSave database server component that is installed in a central location that is in the same physical LAN as the machine on which the Data Server is installed. Basically, there must be a high-speed (100MB/s+) connection between the Data Server & the Database Server. Data Server: The customer will need the data server to be installed in a central location that is accessible from all of the sites. There could be multiple data servers serving this purpose, but all of them must be located in the same physical LAN as the Database Server. The Data Server service can also be installed on the same machine that SQL Server is installed on. Application Server: The customer will need an application server to be installed at every site. This application server must have TCP/IP access to the Data Server, and while the connection can be a low speed connection, it must still be broadband speeds (1MB/s+). Page 4

5 Batch Scanning Server: The customer will need a Batch Scanning server installed at every site if and only if it is using PaperSave batch scanning features such as ScanFirst or ScanLater. The batch scanning server must sit in the same physical LAN as the application server. The customer needs to process 50+ stacks of ScanLater or ScanFirst coversheet separated documents a day or the individual stacks submitted to the Batch Scanning Server through ScanFirst or ScanLater are 50+ pages in size (50 page MTIFFs). The customer requires the performance of High-End scanning at the desktop using ScanNow. High End Scanning is defined as the scanning (using ScanNow ) of documents that are in grayscale, or color, or are greater than 600dpi, or are 10+ pages on average. The client would like to install & use the PaperSave client within a thin-client computing environment such as Citrix Presentation Server or Microsoft Windows Terminal Server. Batch Scanning Server: The customer will need a dedicated Batch Scanning Server, whose specifications match the specifications of a Medium/High-Usage Batch Scanning Server. Details on these are outlined in the PaperSave Recommended Hardware Guidelines section of this document. Imaging Hardware: The customer will need a scanner capable of handling large volume of scans at high speeds. A high-volume workgroup scanner is therefore a requirement for this scenario. Details on High-Volume scanners are outlined in the PaperSave Recommended Hardware Guidelines section of this document. PaperSave Client: The PaperSave Client using ScanNow must be installed on a higherend workstation fit for high-end imaging applications. Details on this are outlined in the PaperSave Recommended Hardware Guidelines section of this document. PaperSave Client: Most versions of Citrix and all versions of Microsoft Windows Terminal Server Remote-Scan lack support for TWAIN over their respective remote desktop protocols (ICA & RDP respectively). To bridge this gap in peripheral support a third party TWAIN over ICA or TWAIN over RDP component such as the one sold by Remote-Scan ( is required in order to allow ScanNow to work over the thin-client session. Page 5

6 PaperSave Recommended Hardware Guidelines: The following table outlines the recommended general hardware configuration for each PaperSave component under potentially different usage requirements. Please note that multiple PaperSave components can be installed on the same computer as long as the computer meets the recommended requirements outlined for the most resource intensive component installed on that computer. Exceptions to this rule are specifically outlined in the PaperSave Enterprise Recommended Deployment Guidelines section of this document. Microsoft SQL Server Database Server: This is the server that has Microsoft SQL Server installed on it, and is hosting the PaperSave database. These specifications assume that the SQL Server is used as a shared SQL Server, and that it may also host databases other than PaperSave 's. However, there are enterprise scenarios that would require that a customer use a dedicated Microsoft SQL Server machine that hosts the PaperSave database exclusively. These scenarios are described in this document under the section titled PaperSave Enterprise Recommended Deployment Guidelines. Memory 2-gigahertz (GHz) or faster processor recommended Server 2003 Enterprise Edition, Standard Edition, or Datacenter Edition with SP 1 or ; Windows Small Business Server 2003 with SP 1 or 2 gigabyte (GB) or more recommended RAID 5 or RAID 10 redundant storage is required. Also, please refer to the PaperSave Space Calculator for an accurate estimation of the space required to host PaperSave documents based on the customer's specific influx of documents Other Requirements Microsoft SQL Server 2000 or Microsoft SQL Server 2005 Data Server: This is the server responsible for hosting the PaperSave Data Server windows service. This service is typically installed on the same server as the Microsoft SQL Server instance hosting the PaperSave database. However, there are scenarios where a customer may want to install this on a machine other than the server hosting Microsoft SQL Server. This scenario is covered under the section titled PaperSave Enterprise Recommended Deployment Guidelines. 1-gigahertz (MHz) or faster processor recommended Page 6

7 Memory Other Requirements 256 megabytes (MB) or more recommended 20 MB of free space..net Framework version 1.1, MDAC 2.7, Free TCP/IP port to use as the Data Port Application Server: This is the server responsible for hosting the PaperSave Application Server windows service. This service should be installed on a server that is in the same LAN as the machines that run the PaperSave clients. Typically this service is installed on the same server as the Data Server. However, there are scenarios where a customer may want to install this service on a machine other than the server hosting the PaperSave data server. These scenarios are covered under the section titled PaperSave Enterprise Recommended Deployment Guidelines. Memory Other Requirements 1-gigahertz (MHz) or faster processor recommended 256 megabytes (MB) or more recommended 20 MB of free space..net Framework version 1.1, Free TCP/IP port to use as the Application Port Batch Scanning Server (Low Usage): This is the server responsible for hosting the PaperSave Batch Scanning Server windows service. Low Usage is defined as less than 50 stacks of ScanLater or ScanFirst coversheet separated documents to process a day and where the stacks are less than 20 pages in size (20 page MTIFFs). This service should be installed on a server that is in the same LAN as the machines that run the PaperSave clients. Typically a low usage Batch Scanning Server would be installed on the same server as the PaperSave Application Server service. However, there are scenarios where a customer may want to install this service on a machine other than the server hosting the PaperSave Application Server service. These scenarios are covered under the section titled PaperSave Enterprise Recommended Deployment Guidelines. 1-gigahertz (GHz) or faster processor recommended Page 7

8 Memory 750 megabyte (MB) or more recommended 20 MB of free space. Other Requirements.NET Framework version 1.1 Batch Scanning Server (Medium Usage): This is the server responsible for hosting the PaperSave Batch Scanning Server windows service. Medium Usage is defined as between 50 and 100 stacks of ScanLater or ScanFirst coversheet separated documents to process a day and where the stacks are less than 50 pages in size (50 page MTIFFs) or any number of stacks to process a day where the stacks are between 50 and 100 pages in size. This service should be installed on a server that is in the same LAN as the machines that run the PaperSave clients. Typically a medium usage Batch Scanning Server would be installed on a low usage or dedicated server/workstation. Please refer to the section titled PaperSave Enterprise Recommended Deployment Guidelines for more details. Memory 1.5-gigahertz (GHz) or faster processor recommended 1 gigabyte (GB) or more recommended 20 MB of free space plus enough free space for the Dump directory used to house backup copies of processed stacks. Please refer to the section titled PaperSave Enterprise Recommended Deployment Guidelines for more details Other Requirements.NET Framework version 1.1 Batch Scanning Server (High Usage): This is the server responsible for hosting the PaperSave Batch Scanning Server windows service. High Usage is defined as greater than 100 stacks of ScanLater or ScanFirst coversheet separated documents to process a day or where the stacks are greater than 100 pages in size (100 page MTIFFs). This service should be installed on a server that is in the same LAN as the machines that run the PaperSave clients. Typically a high usage Batch Scanning Server requires a dedicated server/workstation. Please refer to the section titled PaperSave Enterprise Recommended Deployment Guidelines for more details. 2-gigahertz (GHz) or faster processor recommended Page 8

9 Memory 1.5 gigabyte (GB) or more recommended 20 MB of free space plus enough free space for the Dump directory used to house backup copies of processed stacks. Please refer to the section titled PaperSave Enterprise Recommended Deployment Guidelines for more details Other Requirements.NET Framework version 1.1 PaperSave Client Machine (Low-Medium End Scanning): This is any machine that runs the Host System Client integrated with PaperSave, the PaperSave Management Console, or the PaperSave workflow queue explorer. Low-Medium End Scanning is defined as the scanning (using ScanNow ) of documents that are in black and white, no greater than 600dpi, and are less than 10 pages on average. These specifications also apply to machines that have PaperSave clients installed on them, and are not using ScanNow Memory Other Requirements 600-megahertz (MHz) or faster processor recommended 512 megabyte (MB) or more recommended 40 MB of free space.net Framework version 1.1, TWAIN Compatible Scanner if using ScanNow PaperSave Client Machine (High-End Scanning): This is any machine that runs the Host System Client integrated with PaperSave, were High-End scanning is required. High End Scanning is defined as the scanning (using ScanNow ) of documents that are in grayscale, or color, or are greater than 600dpi, or are greater than 10 pages on average. 1-gigahertz (MHz) or faster processor recommended Page 9

10 Memory Other Requirements 1 gigabyte (MB) or more recommended 40 MB of free space.net Framework version 1.1, TWAIN Compatible Scanner if using ScanNow Scanner Specifications for ScanNow : Resolution Scanning Speeds Scanning Mode Document Feeding DPI 15ppm Black & 200DPI Simplex and Duplex 50+ Page Automatic Document Feeder, Automatic Page Size Detection Software Driver TWAIN driver (Windows 2000, Windows XP, Windows 2003) Scanner Specifications for ScanLater & ScanFirst (Low/Medium -Volume): Resolution Scanning Speeds Scanning Mode Document Feeding Software Driver DPI 25+ ppm Black & 200DPI Simplex and Duplex 100+ Page Automatic Document Feeder, Automatic Page Size Detection TWAIN driver (Windows 2000, WindowsXP, Windows 2003) with desktop acquisition and routing software (such as Microsoft Office Scanning or Eastman's Imaging Professional) or Network Interface Card/Feature capable of routing documents to folder locations as CCIT compressed Multi-Page TIFFs. Scanner Specifications for ScanLater & ScanFirst (High-Volume): Resolution Scanning Speeds Scanning Mode Document Feeding Software Driver DPI 50+ ppm Black & 200DPI Simplex and Duplex 200+ Page Automatic Document Feeder, Automatic Page Size Detection TWAIN driver (Windows 2000, WindowsXP, Windows 2003) with desktop acquisition and routing software (such as Microsoft Office Scanning or Eastman's Imaging Professional) or Network Interface Card/Feature capable of routing documents to folder locations as CCIT compressed Multi-Page TIFFs. Page 10