Finesse Custom Client High Availability Failover

[dev11]

Hi,

we are developing a 3rd party Finesse application using Cisco Finesse REST APIs.

Considering that this application will run on IIS with reverse proxy configured and probably a load balancer between the web clients and the two IIS servers which is the suggested way to guarantee high availability failover against the two Finesse servers?

What we are supposed to have is depicted in the following image:

Since there are two connections between Cisco Finesse clients and the Cisco Finesse server, a REST channel for requests and responses and an XMPP channel to send notifications from the server to the client, which workflow do you suggest to follow in case of recovery?

Any suggestion is welcome.

Many thanks,

John

[dekwan]

Hi John,

All of the users are automatically subscribed to the SystemInfo notifications via the XMPP channel. When the user gets a notification that the node they are connected to (lets say Node A) is OUT_OF_SERVICE, then your 3rd party application should check to see if NodeB is in service. If so, all of the agents should get switched to NodeB. If not, the application should continuously check the two nodes to see which one comes into service first. Whichever that one is, the agents should connect to it.

The agents should stay on whichever node it got connected to. There is no need to connect back to the original node. This is the logic used for the Finesse out of the box desktop.

Does that make sense?

Thanx,

Denise