Enterworks - ETT 124 - How to Process Large Volumes of Record Changes for the Change Notification CN_Log

Enterworks - ETT 124 - How to Process Large Volumes of Record Changes for the Change Notification CN_Log

Business Rules, Vaidation

rate limit

Code not recognized.

About this course

One of the many features of Change Notification is to be able to log the changes made to attributes in repository records to the CN_Log repository.  These changes are normally queued to the ChangeNotificationQueue table, then retrieved by the Change Notification Process workflow and inserted into the CN_Log repository, one record at a time using API calls.  Since a separate record is created for each attribute that was changed, there can be a very high-volume of CN_Log records that need to be created.  In some environments, the rate in which the CN_Log records can be created is surpassed by the rate in which new changes are queued to be logged.  This not only places a significant processing burden on EPX, it results in significant latency between when a change is made, and when details about that change are available.
 This logging process can be sped up significantly by replacing the Change Notification Process workflow with a combination of a Scheduled Export that transfers the data from the ChangeNotificationQueue table to a file and a Scheduled Import to load that file into the CN_Log repository.  This session provides the details on how to configure EnterWorks in this manner to vastly improve the data throughput rate for the CN_Log repository.

Prerequisites - ETT 052

About this course

One of the many features of Change Notification is to be able to log the changes made to attributes in repository records to the CN_Log repository.  These changes are normally queued to the ChangeNotificationQueue table, then retrieved by the Change Notification Process workflow and inserted into the CN_Log repository, one record at a time using API calls.  Since a separate record is created for each attribute that was changed, there can be a very high-volume of CN_Log records that need to be created.  In some environments, the rate in which the CN_Log records can be created is surpassed by the rate in which new changes are queued to be logged.  This not only places a significant processing burden on EPX, it results in significant latency between when a change is made, and when details about that change are available.
 This logging process can be sped up significantly by replacing the Change Notification Process workflow with a combination of a Scheduled Export that transfers the data from the ChangeNotificationQueue table to a file and a Scheduled Import to load that file into the CN_Log repository.  This session provides the details on how to configure EnterWorks in this manner to vastly improve the data throughput rate for the CN_Log repository.

Prerequisites - ETT 052