2022.2

Table Of Contents
l
The Connect Workflow module requires less RAM but fast hard drive access. It also benefits from
fast multi-core CPUs, in order to run processes in parallel.
l
The Connect Server module requires more RAM and benefits from fast multi-core CPUs. Disk
access speed is less of a concern.
l
The Connect Designer module requires more RAM and fast disk access to provide a responsive
user-experience.
l
The back-end database (MySQL by default) benefits from more RAM, speedy disk access and
fast networking as it will be solicited by all modules simultaneously.
Environment considerations
This page provides technical information about the environment in which PReS Workflow is intended to
run.
Terminal Services
PReS Workflow does not support Remote Desktop (Terminal) Services because Workflow runs on
single server and only one user can log on at once.
Terminal Services may also be referred to as Terminal Server or Remote Administration Mode (Win-
dows Server 2003 and 2008).
Single-User Remote Desktop Protocol (RDP) (where only one person can use RDP at a time) is sup-
ported for PReS Workflow version 6.2 and higher, however it is only supported in Windows XP or Win-
dows 2003. While later versions of Windows may not cause issues when accessing PReS Workflow
through RDP, these combinations are no longer tested and may not be functional.
Virtual environments
PReS Workflow supports the following virtual environments:
l
VMWare Environments. This includes VMWare Player, VMWare Workstation as well as VMWare
ESX Server.
l
VMWare VMotion. This means the virtual machine hosting PReS Workflow can be automatically
moved from one ESX server to another in a clustered installation.
l
Microsoft Hyper-V/Azure infrastructure environments.
l
Amazon Web Services (AWS)
PReS Workflow is not officially supported on any other virtual machines such as Virtual PC, Parallels,
Bochs, Xen, etc. While running PReS Workflow on these virtual machines may work finewe have not
tested them and cannot offer support for them.
Page 18