Differences

This shows you the differences between two versions of the page.

--- gui:architecture [2026/02/05 11:25] – emcodem
+++ gui:architecture [2026/02/28 20:50] (current) – [Multiple Servers + NAS] emcodem
@@ Line 12: / Line 12: @@
 {{:gui:deployment_options.jpg?1000|}}
-==== Simple Deployment Single Server ====
+==== Local Machine ====
 You can run FFAStrans on a standalone PC without the need for further Hard- and Software. In this case the installation files and Media files are on the local drives of your PC.
@@ Line 19: / Line 19: @@
-==== Common Deployment Single Server ====
+==== PC + NAS ====
 If you have one or multiple NAS Servers where your Media files come from and go to but still only one Server that runs FFAStrans, make sure that:
@@ Line 27: / Line 27: @@
-==== Complex Deployment Farm ====
+==== Multiple Hosts (Farm) + NAS ====
-If you need more than one server/host to take care about your workflows, you can utilize FFAStrans farming abilities.
+If you need more than one server/host to take care about your jobs, you can utilize FFAStrans farming abilities.
 FFAStrans runs in an **Active-Active** Pattern. This means that there is no "Main Server" as it would be the case in a typical "Master-Slave" pattern which is the case for most other workflow managing software.
 How it works is that you just place the FFAStrans installation directory on the SMB Server - let us call it **Database Share** - with the highest availability possible.
+This means that the FFAStrans.exe App needs to be started from a UNC Path on every host (especially before installing the Service)
+  * In a Farm Environment, you should NEVER start FFAStrans.exe from a local path like C:\FFAStrans but instead always start it from the central share
+  * Example: \\FFASTRANSDB\FFAStrans\FFAStrans.exe
 === How to choose Database Share Location ===