<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

[GUIDE] FlowWright Process Automation On-premise

Posted by Dileepa WIjayanayake on Apr 20, 2020 7:45:00 AM

FlowWright supports many infrastructure configurations, including distributed processing.  For security reasons, FlowWright customers often choose to install on-premise - either on their in-house servers or in dedicated servers within a data center.

FlowWright's architecture can be (over)simplified as being comprised of 3 basic parts:

  1. Web application (User interface)
  2. Engines (Windows services)
  3. Database (Microsoft SQL server)

These can all be installed on a single server, although we recommend running an application and a database server separately:  a web application performs better when the database server is separate, except in the case of the 2 servers are in 2 different networks.

FlowWright basic configuration

But you may choose to set up a distributed configuration.  There are many reasons why you might want to do this.  For example, you may wish to separate UI processing from workflow processing because when workflows are often processing-intensive, separating the UI from the engines results in better performance and user experience.

And, in some cases, many users have to interact with workflows (e.g., completing tasks), and the UI must perform well for these users.  In a high UI request environment, workflow performance might be hindered if engines rely on the same processing power.  You might want to separate process engines onto a separate server.  In this scenario, you would need at least 3 servers, one for the application, one for engines and the database server.

In some environments, there may be a heavy load of workflow instances to be processed.  We have customers that process more than 300,000 workflows each day.  It is possible that 2 servers - one application server plus one database server - might not able to handle a massive processing load.  In this case, you might want to include multiple application servers to distribute the load and process.  A similar configuration is displayed below:

Multiple FlowWright servers processing the load - distributed configuration

Another scenario is the need to process multiple databases with a single application server (in other words, a multi-tenant configuration scenario!)  FlowWright engines are designed for processing multi-tenant configurations, and FlowWright version v9.7 provides many new multi-tenant features, including enhancements to the user interface as well as a tenant manager.

FlowWright is flexible when it comes to accommodating your needed infrastructure configuration.  FlowWright is readily adaptable to your existing hardware infrastructure and FlowWright uses the standard, advanced Microsoft stack of technologies.

Learn more today about FlowWright and set-up a customized demo with our team. Schedule here. 

Start Software Trial


Topics: workflow process software