CSProxy Good or bad?

[TMC]

Does anyone have an opinion on whether CSProxy is useful or not?

I've had mixed experiences with this and would like to know what others think. I've been having trouble with a solution that uses them with warm standby, and I'm considering changing this to standalone or just linking into our main configservers.

I know they are useful when you experience network issues, however if you have problems starting up CSProxy or the wrong instance is Primary, our support team don't always know what to do.

Any comments?

[Jim]

CS proxy is something that Genesys needed to offer eight years ago when links between sites were expensive and bandwidth non existant. I do not see any reason to use them since not only do they complicate the overall system layout, but also add additional product to pay for.

[Sidney]

Well, I think you always run CSProxy as a primary. As long as you have the right license you can run different instances of CSProxy as primary.

CSProxy reads the configuration from the main config server or another csproxy and keep it memory, so you can have as many as you want, running and use any of them at any time. There are not limitations on that. The only real limitation is that you can't not have two different Configuration Servers against the same database.


For big implementations, with big configurations and several sites CSProxy makes sense because you can have one csproxy in each location and that shorten the time to start applications, and reduces network traffic.

For small implementations, for backup you can install a second instance of config server and have it ready to run if primary fails. Don't need HA for that, can be done manually.

Remember if config server dies, that doesn't affect the system unless you need to restart a process.

[TMC]

Is CSProxy a licensed product? I wasn't aware that it was.

[TMC]

What feature do you need in the license file? We are running several instances of CSProxy, yet I haven't seen a license for it.