Thanks for the followup, James; I appreciate it.
But I think I’m still missing something . . .
Duplicating, renaming and reconfiguring the outbound protocol threads and adding them all as destinations in a single route detail on a local test site took me about 90 seconds. Deleting those threads when done also removed the destinations from the route detail, so that was even faster than setting it up in the first place. It seemed pretty straightforward for either a temporary or permanent solution.
Perhaps the issue is that there are multiple inbound threads whose output needs to be replicated? My suggestion gets a bit more complex in that scenario, but in a linear fashion 🙂
Or maybe I’m just misunderstanding the terminology, given that I’m new here and an eGate refugee. My attempt didn’t involve creating additional routes, it simply added destinations to an existing route’s detail. If that’s bad form, it would be helpful to me to understand why.
Thanks!
PS. If the issue boils down to licensing, I guess I need to understand that better. It seems you’d need multiple protocol threads regardless.