Cisco Cisco Process Orchestrator 3.0 Installation Guide

To set up Microsoft Network Load Balancing Manager for Process Orchestrator requires at least three 
to five machines and three static IP addresses:

One machine acts as the cluster host (with a static IP).

Two machines act as Process Orchestrator servers and Web Consoles. Alternatively, the Web 
Console could be installed on a separate highly-available IIS (with a static IP).

One machine hosts a High Availability database for Process Orchestrator (for testing purposes this 
could be the same machine as the cluster host).

One machine performs client testing (for testing purposes this could also be the same as the cluster 
host).

In the example in the following sections, the cluster/load-balancer is not monitoring specific Process 
Orchestrator ports to verify that the application is healthy, but instead is tested using the Load Balancing 
Manager software (by stopping incoming connections to a specific host) or by shutting down the server 
or disabling network access on one of the Process Orchestrator servers to ensure that load-balancing is 
occurring. In production, the load balancer should be configured to monitor the health of the Process 
Orchestrator server, northbound web service, or IIS ports to determine if the server, northbound web 
service, or web console are running or down.

In this example, sjc-msnlb.tidalsoft.local is the cluster host and the Process Orchestrator servers and web 
consoles are installed at sjc-ms-w2k864-1.tidalsoft.local and sjc-ms-w2k864-2.tidalsoft.local.