/mcpClusterConfig APIs apply only to Finesse deployments with Unified CCE. Because you need not configure cluster settings for Unified CCX deployments, these APIs are not supported for Finesse with Unified CCX. Note This feature also reports replication status. Replication status determines whether a user is allowed to or restricted from changing the value of the secondary node. The Finesse server interacts with the VOS database to get and set information about the secondary node. The ClusterConfig object is structured as follows: <ClusterConfig> <uri>/finesse/api/ClusterConfig</uri> <secondaryNode> <host></host> </secondaryNode> </ClusterConfig> Any changes made to the settings through the ClusterConfig API will require a Cisco Finesse Tomcat restart. Note ClusterConfig APIs ClusterConfig—Get This API allows an administrator to get a copy of the ClusterConfig object. https://<FQDN>/finesse/api/ClusterConfig URI: https://finesse1.xyz.com/finesse/api/ClusterConfig Example URI: Only administrators can use this API. Security Constraints: GET HTTP Method: — Content Type: XML Input/Output Format: — HTTP Request: 200: Success 401: Unauthorized 403: Forbidden 500: Internal Server Error HTTP Response: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 215 Cisco Finesse Configuration APIs ClusterConfig APIs
