6.0 Service Pack 2

3150 Miami Green Way, 11th Floor, Miami, Florida – 33146. USA

877 727 3799 305 373 0056 www.papersave.com

PaperSave is a product of WhiteOwl - www.whiteowlsolutions.com

PaperSave®Cloud

Deployment WhitePaper 6.0 Service Pack 2

http://www.papersave.com/

Information in this document is subject to change without notice. Contact your PaperSave Representative for the latest information.

Page i

Table of Contents 1 INTRODUCTION ..........................................................................................................................................................1

2 PAPERSAVE® RECOMMENDED DEPLOYMENT GUIDELINES ....................................................................................3

2.1 UNDERSTANDING PAPERSAVE CLOUD ON-PREMISE COMPONENTS: ...............................................................5

2.1.1 PAPERSAVE DATA ACCESS WEB SERVICE:....................................................................................................5

2.1.1.1 PAPERSAVE DATA ACCESS WEB SERVICE DEPLOYMENT RECOMMENDATIONS: ......................................... 5

2.1.2 PAPERSAVE CLIENT: .......................................................................................................................................5

2.1.3 PAPERSAVE CLIENT FOR TERMINAL SERVER: ...............................................................................................6

2.1.4 PAPERSAVE MS OFFICE ADD-IN: .................................................................................................................6

2.2 DEPLOYMENT SCENARIOS FOR PAPERSAVE DATA ACCESS WEB SERVICE: .......................................................7

2.2.1 SHARED SERVER FOR PAPERSAVE DATA ACCESS WEB SERVICE: ................................................................7

2.2.2 DEDICATED SERVER FOR PAPERSAVE DATA ACCESS WEB SERVICE: ..........................................................8

3 PAPERSAVE® RECOMMENDED HARDWARE GUIDELINES: .......................................................................................9

3.1 PAPERSAVE OCR (OPTIONAL) ............................................................................................................................9

3.2 INTERNET REQUIREMENTS....................................................................................................................................9

3.3 DATA ACCESS SERVICE: ..................................................................................................................................... 10

3.4 PAPERSAVE® WINDOWS CLIENT MACHINE (UP TO LOW/MEDIUM END SCANNING): ............................... 10

3.5 PAPERSAVE® WEB CLIENT MACHINE (UP TO LOW/MEDIUM END SCANNING): ......................................... 12

3.6 PAPERSAVE® WEB OR WINDOWS CLIENT MACHINE (HIGH-END SCANNING): .......................................... 14

3.6.1 RECOMMENDED SCANNER SPECIFICATIONS FOR SCANNOW™: ............................................................. 16

3.6.2 RECOMMENDED SCANNER SPECIFICATIONS FOR SCANLATER™ OR SCANFIRST™ INTO WORKFLOW

(LOW/MEDIUM -VOLUME): ....................................................................................................................... 17

3.6.3 RECOMMENDED SCANNER SPECIFICATIONS FOR SCANLATER™ & WORKFLOW™ (HIGH-VOLUME): .. 18


Page 1

1 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.

PaperSave is available as a ‘Software as a Service (SAAS)’ based solution delivered through the cloud on

subscription called PaperSaveCloud™. PaperSaveCloud™ is identical to the On-Premises version. Users

enjoy the same user interfaces regardless of where their PaperSave services are being delivered from,

with minimal difference in functionality and operation between the two. The infrastructure to support

PaperSaveCloud™ runs within the Tier 1 Microsoft Azure Cloud. PaperSaveCloud™ utilizes the PaperSave

Data Access Web Service which is a simple secure component used to expose data outside of

PaperSaveCloud™, to PaperSaveCloud™, for features that require secure and direct access to that data

over the internet.

The primary purpose of this whitepaper is to provide PaperSave® customers/prospects and or their

consultants with the proper guidance during the design of the environmental requirements necessary to

support a successful PaperSaveCloud™ implementation. For more information or to ask specific

questions, please contact your PaperSave® representative, call (877) Paper-99 or send an eMail to

[email protected].

http://downloads.papersave.com/Documentation/6.0%20SP2/Data%20Access%20Web%20Service/Installation%20Guides/HTML/Installation%20Guide%20for%20PaperSave%20Data%20Access%20Web%20Service.html

http://downloads.papersave.com/Documentation/6.0%20SP2/Data%20Access%20Web%20Service/Installation%20Guides/HTML/Installation%20Guide%20for%20PaperSave%20Data%20Access%20Web%20Service.html

mailto:[email protected]


Page 2

Architecture for PaperSaveCloud™ Deployment

PaperSave Web Server

PaperSave Windows Client delivered over Microsoft ClickOnce™

PaperSave Mobile Server

Client’s PaperSave Tenant Services

PaperSave Data Access Web Service Server

Client’s Environment

Host Application Server

Host Application Database Server

Cloud

Clie

nt

Wo

rkst

atio

ns


Page 3

2 PAPERSAVE® RECOMMENDED DEPLOYMENT GUIDELINES

The following table outlines how PaperSave® should be used under certain common scenarios/customer

requirements.

Customer Requirements Scenarios PaperSave® Deployment Recommendations

by relevant component

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.

PaperSave® Client

The PaperSave® Client using ScanNow™ must be

installed on a higher-end workstation running

Microsoft Windows, fit for high-end imaging

applications. Details on this are outlined in the

PaperSave® Recommended Hardware Guidelines

section of this document.

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.

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 (www.remotescan.com) or TS Scan is

required in order to allow ScanNow™ to work over

the thin-client session.

The client would like to add documents using

PaperSave but no Host Application is installed on

that box

PaperSave® MS Office Add-in

The PaperSave MS Office Add-in must be installed

on a workstation running Microsoft Office.

The Client would like to use PaperSave from the

Host Application on a Client workstation.

PaperSave® Client for Host Application

The PaperSave Client for Host Application must be

installed on a workstation where the Host

Application is installed/accessed for the user to be

able to use PaperSave from the Host Application.

However, below Host Applications does not need

to have PaperSave Client for Host Application

installed on the workstation.

1. Blackbaud Enterprise CRM

2. Dynamics CRM

The Client would like to use PaperSave on

Terminal Sever.

PaperSave® Client for Terminal Server

http://www.remotescan.com/


Page 4

The PaperSave Client for Terminal Server must be

installed (in addition to the PaperSave Client for

Host Application) on the Terminal Server where

the Host Application is installed/accessed for the

user to be able to use PaperSave.


Page 5

2.1 UNDERSTANDING PAPERSAVE CLOUD ON-PREMISE

COMPONENTS:

2.1.1 PAPERSAVE DATA ACCESS WEB SERVICE:

PaperSave Data Access Web Service acts as an intermediary that allows accessing host data (if not

accessible directly) located on different server through PaperSave Application Server hosted on cloud.

For example If PaperSave Application Server X hosted on cloud, wants to access the data (which is not

accessible directly) from Database Server Y hosted On Premise, in this scenario, one needs to install

PaperSave Data Access Web Service on the Web Server that is externally facing and has access to

PaperSave Application Server and the Host server.

2.1.1.1 PAPERSAVE DATA ACCESS WEB SERVICE DEPLOYMENT RECOMMENDATIONS:

1. PaperSave Data Access Web Service should be installed on a separate site under IIS.

2. The site should be secured with a SSL Certificate and protected through a corporate Firewall so

that the only IP that can access it is the IP of your PaperSaveCloud™ server. This is provided to

you by your project team.

3. The site should be bind with an IP address.

4. There should be a dedicated domain user, which runs the PaperSave Data Access Service. The

same user should have data_reader rights over the Host Application’s Company database(s).

5. There should be another and only domain user, which has browsing rights for PaperSave Data

Access Web Service.

2.1.2 PAPERSAVE CLIENT:

The PaperSave Client enables the user to use PaperSave within an integrated ERP/CRM system by

integrating the PaperSave related code into that system for systems that require workstation level

integration deployment. Please note that not all PaperSave integrated systems will require a PaperSave

Client install. When necessary, the PaperSave Client needs to be installed on Workstation running the

integrated application and it must be pointed to the customer’s PaperSaveCloud™ instance. Please find

below the list of PaperSave Clients for each integrated application that requires a PaperSave Client.

1. Microsoft Dynamics GP requires the PaperSave Client for Dynamics GP

2. Microsoft Dynamics SL requires the PaperSave Client for Dynamics SL

3. Microsoft Dynamics AX requires the PaperSave Client for Dynamics AX

4. Blackbaud’s The Financial Edge requires the PaperSave Client for Financial Edge

5. Blackbaud’s The Raiser’s Edge requires the PaperSave Client for Raiser’s Edge


Page 6

6. Blackbaud’s Student Information System requires the PaperSave Client for Student Information

Systems.

7. Blackbaud’s Education Edge requires the PaperSave Client for Education Edge.

The following integrated applications do not require a PaperSave Client install on each workstation using

that application:

1. Blackbaud Enterprise CRM

2. Dynamics CRM

2.1.3 PAPERSAVE CLIENT FOR TERMINAL SERVER:

On a typical workstation, the PaperSave Runtime components are downloaded and installed on-demand

into user’s profile (by users) using a Microsoft deployment technology called ClickOnce™. The value in

deploying our runtime components in that fashion is that the customer’s IT does not have to manually

install the PaperSave Runtime components and can rely on the user’s installing them themselves without

giving users administrator level access to their machines. ClickOnce™ applications also automatically

update themselves whenever the server base binaries that the ClickOnce™ application is being streamed

from are updated. Since ClickOnce™ accomplishes all of this by deploying applications into the user’s

profile; it means that space is taken up on each machine with an installation of PaperSave’s binaries for

each user using that machine. That ramification is undesirable on Terminal Server machines because that

would mean that the PaperSave binaries would be installed for each user profile on those machines

potentially taking up unnecessary space. The PaperSave Client for Terminal Server deploys the PaperSave

binaries on a machine level so that all users using PaperSave applications from the Terminal Server are

using them from a common rather than from each user’s profile. The PaperSave client for Terminal Server

must be installed on a Terminal Server pointed to the customer’s PaperSaveCloud™ instance.

Note: If users need to use PaperSave from within one of the applications PaperSave integrates into then

both the PaperSave Client for Terminal Server and the PaperSave Client must be installed on that Terminal

Server.

2.1.4 PAPERSAVE MS OFFICE ADD-IN:

PaperSave MS Office Add-In enables adding documents to PaperSave from within Microsoft Word,

PowerPoint, Excel, Outlook, and Windows Explorer. PaperSave MS Office Add-In must be installed on a

machine running Microsoft Office and must be pointed to the customer’s PaperSaveCloud™ instance.


Page 7

2.2 DEPLOYMENT SCENARIOS FOR PAPERSAVE DATA ACCESS WEB

SERVICE:

2.2.1 SHARED SERVER FOR PAPERSAVE DATA ACCESS WEB SERVICE:

Shared Server for PaperSave Data Access Web Service


Cloud

Clie

nt

Wo

rkst

atio

ns


PaperSaveCloud™ Environment

Host Application & PaperSave Data Access Web Service Server


Page 8

2.2.2 DEDICATED SERVER FOR PAPERSAVE DATA ACCESS WEB SERVICE:

Dedicated Server for PaperSave Data Access Web Service

PaperSave Data Access Web Service Server


Host Application Server


Cloud

Clie

nt

Wo

rkst

atio

ns

PaperSaveCloud™ Environment


Page 9

3 PAPERSAVE® RECOMMENDED HARDWARE GUIDELINES:

The following tables outline the recommended general system 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.

3.1 PAPERSAVE OCR (OPTIONAL)

PaperSave 6.0 Service Pack 2 introduces new PaperSave embedded OCR Module with out of the box

Accounts Payable Invoice Templates and built in operator learning features. PaperSaveCloudTM Customers

do not need specific additional hardware or software requirements to use the PaperSave OCR module.

The PaperSave OCR module will be securely communicating with our OCR service in PaperSave’s Cloud

to securely execute the extraction of your data from your images.

3.2 INTERNET REQUIREMENTS Bandwidth/Speed Minimum of 600kbps per concurrent user

Site Connectivity Broadband (business grade cable modem or DSL)

or dedicated circuit (fractional/full T1) scaled to

aggregate of concurrent hosted application(s)

users (600kbps per), private line, or frame relay.


Page 10

3.3 DATA ACCESS SERVICE:

This is the server responsible for hosting the PaperSave® Data Access Web service. This service should

be installed on a server that is in the same LAN as the host application that PaperSave is being connected

to. Typically, this service is installed on any externally facing web server. However, there are scenarios

where a customer may want to install this on a dedicated machine or in their DMZ.

Processor Dual Core CPU with 2.5 GHz processing speed or

higher

Operating System Windows Server 2008R2, 2008, Standard

(32-bit and x64 versions)

Windows Server 2008R2, 2008, Enterprise


Windows Server 2008R2, 2008, Datacenter


Windows Server 2012

Windows Server 2012 R2

Memory 2 GB RAM or higher

Hard Disk 1 GB of available hard disk space

Other Requirements .Net Framework 3.5 SP1

.Net Framework 4.5

10/100 Mbit LAN or higher

3.4 PAPERSAVE® WINDOWS CLIENT MACHINE (UP TO LOW/MEDIUM

END SCANNING):

This machine runs the Host Client System, integrated with the PaperSave® Client, running in Windows

Client mode or running on any other Windows based PaperSave User Interface. 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 with the output style-setting equal to

Searchable PDF set within the Scan Settings configuration in the respective user interface. These

specifications also apply to machines that utilize PaperSave® Windows User Interfaces on them, and are

not performing any scanning.


higher

Operating System Windows Vista Professional, Ultimate,

Enterprise, Business (x86 and x64 versions)

Windows 7 Professional, Ultimate,



Page 11



Windows 8.1 Professional, Ultimate,


Windows 10*

Mac OS** 10.9.1

*PaperSave is compatible with Windows 10

although with following two known issues with

Microsoft Edge Browser:

PaperSave Scanning functions will not

work with Microsoft Edge

Drag & Drop will not work with Microsoft

Edge

**Scanning through PaperSave within PaperSave

Web Client User Interfaces is not supported on

Mac machines.

Note: Windows XP is not supported.

Memory 2 GB or more dedicated to PaperSave and

minimum of 4 GB or more total RAM

Hard Disk 2 GB of free space for PaperSave binaries and

temp files


.Net Framework 4.5


TWAIN Compatible Scanner if using

ScanNow™

Recommended Scanners Recommended USB (local) Scanners

Fujitsu fi-6 series TWAIN-Compliant USB

Scanner


Scanner

If the scanner chosen is not from our

recommended list of USB scanners, then the

scanner must be TWAIN-Compliant in order to be

used within for ScanNow™ or PaperSave Scan

(Capture) feature(s).


Page 12

3.5 PAPERSAVE® WEB CLIENT MACHINE (UP TO LOW/MEDIUM END

SCANNING):

This machine runs the Host Client System, integrated with the PaperSave® Client, running in Web Client

mode or running on any other Web based PaperSave User Interface. Low-Medium End Scanning is

defined as the scanning (using ScanNow™ or PaperSave Scan/Capture) of documents that are in black

and white, no greater than 600dpi, and are less than 10 pages on average with the output style setting

equal to Searchable PDF set within the Scan Settings configuration in the respective user interface. These

specifications also apply to machines that utilize PaperSave® Windows User Interfaces on them, and are

not performing any scanning. Please note that scanning within PaperSave Web Client User Interfaces is

only supported when the Web Client is being used within Internet Explorer 10+ on a Windows machine

with .NET 4.5 installed on it.


higher









Windows 10*

Mac OS** 10.9.1







Edge



Mac machines.


Memory 1 GB or more dedicated to PaperSave and

minimum of 3 GB or more total RAM

Hard Disk 500 MB of free space for PaperSave temp files


Page 13

Browsers

Microsoft Internet Explorer 10+, Mozilla Firefox*,

Apple Safari*, Google Chrome* (all latest versions)

Note:

Scanning with PaperSave Web Client User

Interfaces is only supported when the

Web Client is being used within Internet

Explorer 10+ on a Windows Machine with

.NET 3.5 installed on it.

Editing annotations within the Web Client

is only supported for PDFs; and requires

Silverlight 4.0 that is supported on all the

above-mentioned browsers.

Apple Safari is only supported for Mac.

*Print, Email and Scan functionality within

PaperSave’s web client requires installing

small utility applications that are delivered

over Microsoft’s ClickOnce deployment

technology. ClickOnce applications can be

deployed by a user simply by clicking on

a link and following accepting simple

terms. ClickOnce applications also update

automatically when the PaperSave’s

server systems are updated. ClickOnce

applications are only supported on

Windows Operating systems (not on

Macs). To ensure maximum compatibly

with minimum effort we recommend

using Internet Explorer as your default

browser for the PaperSave Web Client.

Internet Explorer supports ClickOnce URLs

out of the box. Other browsers are also

able to support ClickOnce URLs but they

require the use of third party plugins in

order to do so. These plugins are freely

available on the plugins store of all the

major non-Microsoft browsers at the time

that this document was produced.


.Net Framework 4.5



ScanNow™

https://msdn.microsoft.com/en-us/library/142dbbz4(v=vs.90).aspx


Page 14



Scanner


Scanner


recommended list of UBS scanners, then the

scanner must be TWAIN-Compliant in order to be

used within for ScanNow™ or PaperSave Scan

(Capture) feature(s).

3.6 PAPERSAVE® WEB OR WINDOWS 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, are greater than 600dpi, or are greater than 10 pages on average.


higher









Windows 10*

Mac OS** 10.9.1







Edge


Page 15



Mac machines.


Memory 2 GB or more recommended

Hard Disk 2 GB of free space dedicated to PaperSave


.Net Framework 4.5



ScanNow™



Scanner


Scanner


recommended list of UBS scanners, then

the scanner must be TWAIN-Compliant in

order to be used within for ScanNow™ or

PaperSave Scan (Capture) feature(s).


Page 16

3.6.1 RECOMMENDED SCANNER SPECIFICATIONS FOR SCANNOW™:

Resolution 200-800 DPI

Scanning

Speeds

30+ppm Black & White @ 200DPI

Scanning

Mode

Simplex and Duplex

Document

Feeding

50+ Page Automatic Document Feeder, Automatic Page Size Detection

Software

Driver

TWAIN driver (Windows 7, Windows 8, Windows 8.1, Windows 2008, Windows 2012) ),

with embedded image processing software/features such as those provided by Fujitsu

PaperStream IP, or Kofax Virtual Rescan (VRS).


Page 17

3.6.2 RECOMMENDED SCANNER SPECIFICATIONS FOR SCANLATER™ OR

SCANFIRST™ INTO WORKFLOW (LOW/MEDIUM -VOLUME):


Scanning

Speeds


Scanning

Mode

Simplex and Duplex

Document

Feeding


Software

Driver

Using the PaperSave Scan (Capture) user interface (Recommended):98

TWAIN driver (Windows 7, Windows 8, Windows 8.1, Windows 2008, Windows

2012) ), with embedded image processing software/features such as those

provided by Fujitsu PaperStream IP, or Kofax Virtual Rescan (VRS).

Using a network scanner that will not be connected to a computer (Supported but

not recommended):

The network scanner should have embedded image-processing software/features

such as those provided by Fujitsu PaperStream IP, or Kofax Virtual Rescan (VRS).

The scanner should also be capable of routing documents to folder locations or

eMail boxes (for ScanFirst™ only) as CCIT compressed Multi-Page TIFFs that are

OCR readable. You can confirm that a TIFF produced by a network scanner is OCR

readable by using the Barcode Test Utility found at this URL:

http://downloads.papersave.com/PaperSave/6.0%20SP2/PaperSave%20Barcode

%20Test%20Utility%206.0%20SP2.exe

http://downloads.papersave.com/PaperSave/6.0%20SP2/PaperSave%20Barcode%20Test%20Utility%206.0%20SP2.exe



Page 18

3.6.3 RECOMMENDED SCANNER SPECIFICATIONS FOR SCANLATER™ &

WORKFLOW™ (HIGH-VOLUME):


Scanning

Speeds


Scanning

Mode

Simplex and Duplex

Document

Feeding


Software

Driver

Using the PaperSave Scan (Capture) user interface (Recommended):98

TWAIN driver (Windows 7, Windows 8, Windows 8.1, Windows 2008, Windows

2012) ), with embedded image processing software/features such as those

provided by Fujitsu PaperStream IP, or Kofax Virtual Rescan (VRS).

Using a network scanner that will not be connected to a computer (Supported but

not recommended):

The network scanner should have embedded image-processing software/features

such as those provided by Fujitsu PaperStream IP, or Kofax Virtual Rescan (VRS).

The scanner should also be capable of routing documents to folder locations or

eMail boxes (for ScanFirst™ only) as CCIT compressed Multi-Page TIFFs that are

OCR readable. You can confirm that a TIFF produced by a network scanner is OCR

readable by using the Barcode Test Utility found at this URL:

http://downloads.papersave.com/PaperSave/6.0%20SP2/PaperSave%20Barcode%20Test

%20Utility%206.0%20SP2.exe



Documents

6.0 Service Pack 2