Overview

PrizmDoc Application Services (PAS) is a service that provides application-level logic for the Viewer; such as enabling document viewing through the PrizmDoc Server, saving and loading of markup, and handling opening of documents and creating viewing sessions. This service is designed to be a gateway between the Viewer and PrizmDoc Server, and takes the place of the Web Tier samples available in previous versions of the product.

PAS is intended to run on the same server as your web tier, although that is not required. As it is a standalone service, it can run anywhere between your web application and PrizmDoc Server, including on its own separate machine if necessary.

Architecture in the Out-of-Box Product using PAS

The only requirement that PAS has is that a single, configurable endpoint from the Viewer is proxied to PAS. If logic beyond the default behavior is required (such as customized storage of markup, for example), PAS exposes a flexible API allowing the user to handle only very specific viewer requests while delegating all others to PAS.

With the introduction of PAS, the Web Tier Samples in PrizmDoc Viewer only include a small amount of proxy code, which accomplishes the forwarding of viewer requests to PAS. This provides minimal code for customers to implement, and it is code that should not need updates often.

Web Server of Your Choice

The minimal code that comes with the Web Tier Samples is only an example; any proxy into PAS can accomplish the same task with the same minimal code. For a more performant solution, we would encourage you to handle proxying through your web server of choice (such as Apache, NginX, or IIS), allowing your web application to only contain your own logic, without the need to integrate any Accusoft sample code. This is outlined by the architecture below:

For more information on how to configure PAS, refer to the topic Configure PrizmDoc PAS.

Pre-Conversion and Caching with Application Services

In PrizmDoc Viewer v11.0 we introduced new features which support the ability to do pre-conversion and long term caching of documents in a central location. To make use of this new functionality, an external instance of a database will need to be configured to run with PAS. The introduction of PAS handles session management and other stateful operations and lets the PrizmDoc Server handle the document conversion and processing.

Using PAS in a Cluster Environment

PAS is designed to scale out well. In order to install and run PAS on multiple servers, you will need to consider the following:

• You will need a load balancer to accept incoming requests and route them to any instance of PAS. Since any request can be handled by any instance in the cluster, any on-the-shelf load balancing solution should do the job.
• All instances of PAS will need to be configured with the same PrizmDoc Server installation (for single-server or cluster).
• All instances of PAS will need to be configured with the same storage solution, in order to have access to the same data. This includes using shared filesystem storage, such as a NAS, for all filesystem files, as well as a shared database when working with Pre-Conversion Services.

The following is an illustration of this architecture:

For more information on installing PAS on a cluster, refer to the topic Run PAS on Clusters.

Note that PAS is installed "ready to run" via any of our 4 web tier samples (C#, MVC, Java, PHP). This section describes how you can set up your server to handle the proxying these samples implement and eliminate the need for our web tier samples altogether.

This section contains the following "How To" information:

• Set up Your Database for use with PAS
• Migrate to PrizmDoc Application Services (PAS)
• Handle Specific Routes with PAS
• Perform Document Comparison
• Pre-Convert Documents
• Pre-Populate Fields in the E-Signature Viewer
• Work with Viewing Packages

For information on administering PAS, refer to Administering PrizmDoc Viewer > PAS.