Setting up delivery manager resilience, How to set up a load balanced system, 8 setting up delivery manager resilience – Grass Valley iTX Delivery Manager v.2.6 User Manual
Page 61: Setting up delivery manager, Resilience, Summary

55
Setting Up Delivery Manager Resilience
Delivery Manager’s two resilience models are determined by the number of instances of
the Delivery Manager services are running, the number of framework servers the service is
installed on and how the endpoints are configured for each instance.
This chapter explains the best practices for setting each resilience model.
Summary
How to Set Up a Load Balanced System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
How to Set Up Endpoint Monitoring System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
How to Set Up a Load Balanced System
To load balance your Delivery Manager system, you need to have all of your required
endpoints shared between two or more instances of the Delivery Manager service, ideally
running on separate framework servers.
To set up a load balanced system on multiple servers
1 Install Delivery Manager on two or more framework servers, as described in
2 Create new configuration profiles on each server, as described in
3 Add and configure your required endpoints.
For information on the properties that are common to most of the endpoints, see
Generic Endpoint Configuration Settings
Specific instructions for each endpoint type can be found on the following pages:
•
•
•
•
•
•
•
•
•
Make sure each server has different endpoints configured on them.
4 Configure each framework server to run the required instance, as described in
Configuring Server Controller to run a named instance of Delivery Manager