When ProjectDox is installed, shared folders are created on a SAN or NAS with a top-level folder of ProjectDoxSupport for a load balanced environment. In a standard environment, the placement can be distributed differently. The "Implementing ProjectDox" document contains drawings of specific implementations and placement of the folders and Services. Below is the list of folders and a description of their functions:
PdoxTemp
This folder temporarily stores uploaded files (deposited via port 80) to start the publishing paradigm and requests for file downloads from ProjectDox. This folder is cleared on regular intervals (typically 24 hours) by the ProjectDox Utility Service.
Queue
The Queue folder requires bi-directional port 80 access to the Job Processor Server. It holds tickets that the Job Processor will pick up, via the UNC path, and read the path to the source file.
Stamps
JPEG or PNG image files are stored in this folder that are used with the ProjectDox Batch Stamp feature.
UserFilesSource
Original files uploaded to ProjectDox are copied, via UNC, to this directory and stored. Each project created will contain a subfolder within the UserFilesSource that identifies itself using the project ID number. This subfolder will contain a series of folders that will store the original file(s) and their versions by file name.
UserFilesPublish
Published files are deposited to UserFilesPublish, via UNC, allowing for the viewing of the file as thumbnail images in the folder view of a project and within the ActiveX Viewer. ActiveX Viewer is for Internet Explorer 32-bit viewing which is the richest viewer and should be used by primary reviewers for accuracy. Each project will contain a subfolder within UserFilesPublish identified by the project ID number. This subfolder will contain a series of folders that stores the published images of the file, associated markups, and associated versions of the document by file name.
DLCache
Equal amounts of disk space must be allotted to DLCache and UserFilesPublish. DLCache stores the published files to support HTML viewing for Chrome, Firefox, Edge, and Safari.
WFlowDLLCache
Stores the ProjectFlow instances for the life of the workflow. At this time, workflow files will remain even after they are completed. PDoxLogs stores the archived ProjectDox LogReports table entries preserving the information without impacting the working database by reducing the number of records. The size of the share is configurable via the ProjectDox user interface.
In addition to the shared folders, the services listed below were installed to assist in the management of the ProjectDox application. The location is recorded on the Customer Installation Information Sheet. The following list includes a description of the services. (Not all services will be installed on every site – the selection depends on your configuration.)
ProjectDoxUtility
Manages the sending of invitation emails to project groups (if a start date is present), and terminates permissions for project groups when the end date arrives. The Utility also governs cleanup of the files accumulated in the PdoxTemp folder, manages LDAP, PDoxLog and more.
Apache Tomcat and Java
Apache Tomcat and Java manage the Brava License Server and the Brava HTML Server. The license server manages the viewing of ActiveX and HTML published files; ProjectDox carries unlimited users. Once the ActiveX files are published, the Brava Server publishes the HTML files.ProjectDoxWorkflowServer
This service supports one of two possible workflow engines used in ProjectDox environments. The ProjectDox workflow engine service manages rules and activities of the previous Avolve generation of workflow.
ProjectDoxWCFService
A required service enabling the Lucene Search, used to implement a number of permitting integrations, and can be configured to allow for database calls managed by the Windows Communication Foundation, rather than direct calls from the Web Server.
ProjectDoxProcessIncomingService
An optional service that checks the DROP folder of INETPUB at scheduled intervals to pick-up and deliver emails sent to the specific projects within ProjectDox.
