Greenway PrimeSUITE

1 Introduction

Greenway PrimeSUITE is a fully integrated Practice Management (PM) and Electronic Health Record (EHR) software package for hospitals and private practices. PrimeSUITE gives access to data from a single interface. This allows physicians and support staff to complete accurate documentation, schedule appointments, monitor revenue cycles, and generate reports all from one dashboard.

PrimeSUITE makes information available in real-time throughout the practice, giving staff on-demand access to the data they need. The KEMP LoadMaster delivers an exceptional, cost-effective and easy to use solution which, by employing Load Balancing, balances requests across PrimeSUITE servers.

When deployed as a pair, two LoadMasters give the security of High Availability (HA). HA allows two physical or virtual machines to become one logical device. Only one of these units is ever handling traffic at any particular moment. One unit is active and the other is a hot standby (passive). This provides redundancy and resiliency, meaning if one LoadMaster goes down for any reason, the hot standby can become active, therefore avoiding any downtime. For more information on HA please refer to: High Availability (HA), Feature Description.

1.1 Document Purpose

This document is intended to provide guidance on how to deploy Greenway PrimeSUITE with a KEMP LoadMaster. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined.

The KEMP support site can be found at:

1.2 Intended Audience

This document is intended to be used by anyone deploying Greenway PrimeSUITE with a KEMP LoadMaster.

2 Template

KEMP has developed a template containing our recommended settings for this workload. You can install this template to help when creating Virtual Services, as it automatically populates the settings. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template.

Download released templates from the Templates section on the KEMP documentation page:

For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description on the KEMP Documentation Page.

For steps on how to manually add and configure each of the Virtual Services using the recommended settings, refer to the steps in this document.

3 Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet not the Virtual Service address.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to System Configuration > Miscellaneous Options > Network Options.


2. Tick the Subnet Originating Requests check box.

4 Configure the Greenway PrimeSUITE Virtual Services

The following are the steps involved and the values required to set up the Greenway PrimeSUITE Virtual Service:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Configure the Greenway PrimeSUITE.png

2. Enter a valid IP address in the Virtual Address text box.

3. Enter 80 in the Port text box.

4. Enter a recognizable Service Name, for example Greenway PrimeSuite.

5. Ensure tcp is selected as the Protocol.

6. Click Add this Virtual Service.

7. Expand the Standard Options section.

Configure the Greenway PrimeSUITE_1.png

8. Deselect the Transparency check box.

9. Select Server Cookie from the Mode drop-down list.

10. Select 2 Hours from the Timeout drop-down list.

The persistence mode in this deployment is set to two hours but can be set lower. It should be noted, however, that a longer persistence timeout can lead to ‘clumping’ (unbalanced load) while shorter timeouts typically result in more balanced traffic. The optimal persistence value is slightly longer than the servers' session timeout.

11. Enter a Cookie name, for example GreenwaySession.

12. Select round robin from the Scheduling Method drop-down list.

13. Set the Idle Connection Timeout to 7200 and click the Set Idle Timeout button.

The Idle Connection Timeout is also configurable in PrimeSUITE. The value in PrimeSUITE should match the value set here.

14. Expand the Advanced Properties section.


15. Select Legacy Operation (X-ClientSide) from the Add HTTP Headers drop-down list.

16. Expand the Real Servers section.

Configure the Greenway PrimeSUITE_3.png

17. Ensure the HTTP Protocol is selected.

18. Enter 80 as the Checked Port.

19. Ensure HEAD is selected from the HTTP Method drop down list.

Configure the Greenway PrimeSUITE_4.png

20. Add the Real Servers:

a) Click the Add New button.

b) Enter the Real Server Address.

This is the address of the backend server.

c) Enter 80 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. These can be changed by an administrator.

d) Click Add this Real Server. Click OK to the pop-up message.

e) Repeat the steps above to add more Real Servers as needed, based on the environment.


Unless otherwise specified, the following documents can be found at:

Virtual Services and Templates, Feature Description.

High Availability (HA), Feature Description

Document History




Reason for Change



Oct 2015

Initial Draft

First draft of document



Dec 2015

Release updates

Updated for 7.1-32



Jan 2016

Minor changes

Updated Copyright Notices



Mar 2016

Release updates

Updated for 7.1-34



July 2016

Release updates

Updated for 7.1.35



Jan 2017

Minor changes

Updated Copyright Notices



July 2017 Release updates Updated for 7.2.39 7.0 LB



Was this article helpful?

0 out of 0 found this helpful