Load-balanced call to executable on web server

Ah ok - I'll address your points in turn:

Do requests from the Quartz scheduler flow through the BIG-IP to get back to the same web server? Not currently. Quartz runs directly on our web server which is behind BIG-IP.

How often is the scheduler set to run? 3 times daily, (during downtime/non-business hours for different geographic regions)

What would you want to happen if the scheduler ran more than once? With the current implementation of the process called by the scheduler, we would get undefined results, or business entities in incorrect states. We don't want this to happen obviously, so the process is called on the single server only.

Do you need each scheduler request to go to a specific web server (ie. itself), or load balanced across the multitude of web servers? Nope, it doesn't have to go to a specific web server. What I'm trying to achieve is: Enable both web servers behind BIG-IP Have the executable process active on both web servers Then have some scheduler process (Quartz/SQL Agent/Something else) call the executable process via BIG-IP This will route the call to one of the web servers - doesn't matter which one, as long as it's one and one only per call.

I'm not clear as to whether this is achievable - i.e. can a scheduler process call an executable via BIG-IP? Will we need to build in some http/https hook to allow BIG-IP to route the request to the executable process?

Thanks fiveeuros