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.
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.
This document is intended to be used by anyone deploying Greenway PrimeSUITE with a Kemp LoadMaster.
Kemp has developed a template containing our recommended settings for this workload. You can install this template to help create Virtual Services (VSs) because it automatically populates the settings. You can use the template to easily create the required VSs with the recommended settings. You can remove templates after use and this will not affect deployed services. If needed, you can make changes to any of the VS 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.
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.
Because this application can run at Layer 4, transparency is enforced. Transparency takes a higher priority than Subnet Originating Requests. Therefore, if transparency is enabled on the Virtual Service and Subnet Originating Requests is enabled globally, the Virtual Service still uses transparency. The Real Server sees traffic from this virtual service originating with the clientâs source IP address (transparency). See the Transparency document on the Kemp documentation page for more details.
In the diagram above, you can see the following details:
- Client: 10.0.0.100/24
- Virtual Service on eth0: 10.0.0.15/24
- Real Server on eth1: 10.20.20.25/24
With Subnet Originating Requests enabled, the Real Server sees traffic originating from 10.20.20.21 (LoadMaster eth1 address) and responds correctly.
With Subnet Originating Requests disabled, the Real Server sees traffic originating from 10.0.0.15 (LoadMaster Virtual Service address on eth0) and responds to eth0 causing asymmetric routing
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. Select the Subnet Originating Requests check box.
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.
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. Configure the settings as recommended in the following table:
|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.|
|Scheduling Method||round robin|
|Idle Connection Timeout||7200||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.|
|Advanced Properties||Add HTTP Headers||Legacy Operation (X-ClientSide)|
|Real Servers||Real Server Check Parameters||HTTP Protocol|
8. 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.
This document was last updated on 29 January 2019.