Revision as of 08:02, February 4, 2017 by Priyam (talk | contribs)
Jump to: navigation, search

CME Synchronization

Raw Content; Working title
[PRIYA] Is CME the application name?
Feature Server synchronizes the following CME objects whenever there are updated, SIP Switch related objects for the SIP Server, which is assigned to Feature Server:

  • CFGDN
  • CFGAgentLogin

Tenant related objects:

  • CFGAgentGroup
  • CFGPerson
  • CFGPlace

In general SIP FS synchronization with Configuration Server consists of three functional facilities:

  • Initial Import
  • Real-time Synchronization
  • History Log Synchronization

Initial Import

  • Master Feature Server imports Switch related objects and tenant related objects when it starts for the first time.
  • To avoid repeating import procedure, Feature Server saves/retains initial import flags in Cassandra Database.
  • After the check, Feature Server imports when required.
Important
  • Master and Conf-Sync FS nodes perform the initial import of Switch related objects.
  • Master Feature Server performs the initial import of Tenant related objects.

Real-time Synchronization

  • Configuration Server provides ‘subscription for notifications’ mechanism for real-time synchronization.
  • Each Feature Server will be subscribing for the notifications, therefore real-time synchronization with CS may be redundant.
Important
  • All FS nodes perform the real-time sync of Switch related objects.
  • Only Master and Conf-Sync Feature Server perform real-time sync of Tenant related objects.

History Log Synchronization

History log retrieval is a way Configuration Server allows to synchronize with Feature Server with all the changes in the CME during the time the FS has been disconnected from the Configuration Server. If the history log is lost owing to a Feature Server outage, reimport mechanism will be triggered automatically. For configuring Reimport procedure, please refer the link: https://docs.genesys.com/Documentation/FS/latest/Admin/reimpcassdb

Important
  • Feature server instances perform the historical Synchronization.
  • Non-master/confsync The FS nodes perform Historical Synchronization of Switch related objects.
  • The Master and Conf-Sync Feature Server perform Historical Synchronization of Tenant related objects.
Comments or questions about this documentation? Contact us for support!