You can configure Workflow and ServiceDesk to support configurations where one server provides all of the product capabilities. They can also support the configurations that use load balancing technologies.
If your plans involve only a lab environment or a very small environment, load balancing probably does not apply to you. However, if you plan to set up a medium or a large environment or anticipate aggressive growth in the next three to five years, you should consider configuring load balancing from the outset.
In a large environment, load balancing is recommended to let more users access the Process Manager portal, to relieve pressure on a single-server computer, and to allow for scalability and still maintain a single data source.
The benefits of load balancing are as follows:
Front-end servers can be added to scale with the needs or your organization
Additional front-end nodes can be added easily as requirements change
Front-end servers can be stopped, started, and restarted as needed since there are other nodes to handle service requests when one server is unavailable
Things you should be aware of before you attempt load balancing:
Load balancing only affects front-end client access. One server is required to handle background processing. This means that any interruptions to the server that handles background processing may cause service interruptions.
Front-end client access is only one component of system performance. If you have multiple, heavily-used, front-end servers and an under-powered SQL environment, performance is still affected. You should consider all aspects of your environment to ensure optimal performance. You cannot use load balancing to make up for other performance deficiencies.
This document only includes the basics of installing load balancing. Before attempting to set up load balancing you should contact your vendor for instructions and for support.