Versions Compared

Old Version 14

changes.mady.by.user CXDev

Saved on

compared with

New Version Current

changes.mady.by.user CXDev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following diagram shows the links of communication between the application and the CCX server.


Drawio
borderfalse
viewerToolbartrue
fitWindowfalse
diagramNameSupervisor-tools-Direct-CCX-Integration
simpleViewerfalse
linksauto
tbstylehidden
lboxtrue
diagramWidth994


Integration with UCCX


The direct integration approach saves all changes made through the application configuration interface to the CCX server directly. However, it doesn’t store the changes in the following scenarios:

...

The script handles client-side failover of Supervisor Tools and automatically requests to the secondary application server when the primary instance in inaccessible.

Note
iconfalse
title

Note

In a future release, all the changes made to UCCX through the Supervisor Tools interface will first be stored in the local database and asynchronously be written to CCX if/when CCX is available.

This will help to handle the scenarios where CCX server is down and it becomes impossible to make any modification through the Supervisor Tools unless the primary CCX is up again.

...

To detect failover, it continuously monitors the API Server state. In the event of connection failure to the primary UCCX API server, it connects to the secondary API Server to read data from UCCX.


title
Note
iconfalse

Note

  • UCCX subscriber becomes read-only and kept locked for any changes during failover by Cisco. So any changes made to UCCX data via the application would not be written to CCX during connection failure and might lead to data inconsistency issues.

  • Also, note that the application could not handle the failover of CCX to Secondary when the CCX primary node is completely shut down and needs a restart.