McDewey

C H A P T E R 7 Finesse High Availability Availability of a Finesse server is determined by the following information (and in this order): 1. The status of the server as provided by the SystemInfo object: The status of the server indicates whether the server is in service and available to accept requests. 2. The status and availability of a XMPP connection to the Cisco Finesse Notification Service: In a Unified CCX deployment, this service is called the Unified CCX Notification Service. Note An active XMPP connection to the Cisco Finesse Notification Service is required to receive notifications. Loss of this connection may mean that the server itself is unavailable or that the client cannot reach the server. 3. The presence of the 'finesse' XMPP user: Presence indicates whether Finesse has an active connection to the Cisco Finesse Notification Service (Unified CCE) or the Cisco Unified CCX Notification Service (Unified CCX) . An UNAVAILABLE presence for the 'finesse' XMPP user may mean that the connection is lost or that the Finesse web app crashed. A Finesse server must meet the following criteria to be fully available for client use: 1. The status of the server must be IN_SERVICE. 2. A successful XMPP connection is made. 3. The presence of the 'finesse' XMPP user is AVAILABLE. Ensure that the preceding conditions are checked in the order listed, as failure of the criteria at the top of the list means the rest of the criteria will also fail or will not be relevant. For example the presence of the 'finesse' XMPP user cannot be checked without a XMPP connection. An XMPP connection is not useful if the server is OUT_OF_SERVICE. • Failure Scenarios , on page 378 • Desktop Presence and Forced Logout, on page 378 • Failure Handling for Task Routing Clients, on page 380 Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 377