Applies to:

Installing Winshuttle Server 10.6.1—Overview

The following is a high-level overview of the installation process for Winshuttle Server.

There are numerous possible server configurations for the installation of RabbitMQ, Winshuttle Server Manager, and Winshuttle Worker.

See Winshuttle Server Installation and Configuration Options (below) for more information about server architecture and deployment considerations.

Please read before you begin

In a test environment (only), Winshuttle Server can be installed and run on the same machine as Winshuttle Central and Winshuttle Workflow.
In a production environment, Winshuttle Server must be installed and run on a separate machine from Winshuttle Central and Winshuttle Workflow.

Winshuttle Server installation and configuration options

There are multiple possible configurations for the installation of Erlang OTP, RabbitMQ, Winshuttle Server Manager, and Winshuttle Worker.

Note: Basic 1 and 2-server configurations are generally best used for development environments only.

More complex and robust server configurations with 3 and more servers are described below. Generally speaking, for optimal performance 6-server configurations are recommended.

Minimum Server Deployment

This is the minimum recommended configuration for a development environment.

Notes:

Single Manager – Recommended for Dev/QA environments
SQL Server as a DB on the same/different machine

Additional Configurations

Below are additional possible server configurations for 4, 5, and 6 servers.

5 servers configuration

This configuration allows high availability for both the Managers and the Workers. The Queue will share a server node with one of the Managers. SQL Server will share a server node with another manager.

Pros

High availability for the Managers
High availability for the Workers

Cons

Cost is higher (five servers)
Administrative overhead

6 servers

This is a recommended architecture. This configuration requires 6 server nodes to ensure that each process has its own server on which no resources will be shared.

This configuration requires three additional server nodes beyond those that are currently provisioned.

Pros

Highly Available Managers
Highly Available Workers
Queue on its own dedicated server
Scales as necessary

Cons

Highest amount of servers/cost
Administrative overhead

Highly Available Server Deployment

For a Highly Available environment, a configuration with Multiple Managers behind a Load Balancer is recommended

Note:

SQL Server is on a different Machine
All the components (Manager, DB, Rabbit MQ and Worker) need to be on different machines.
Having multiple managers behind a load balancer ensures that when one of the managers is not available, the other one is available to take the responsibility. Having multiple workers with same set of capabilities ensure redundancy.