Product Line: | Microsiga Protheus | ||||||||||
Segment: | Framework | ||||||||||
Module: | Configurator | ||||||||||
Routine: |
| ||||||||||
Initial Registers: | You must first register the Adapters (APCFG020) in Protheus to use this feature. | ||||||||||
Parameter(s): | MV_EAIURL2 | ||||||||||
| Requisite (ISSUE): | PCREQ-1483 | ||||||||||
Country(ies): | ALL | ||||||||||
Database(s): | ALL | ||||||||||
Tables: | XX4 - Adapters Register XB6 - Initial Synchronization Queue | ||||||||||
Operating System(s): | Windows / Linux | ||||||||||
Version/Release: | 12.1.7 |
EAI Protheus features a synchronizer of initial loads for the registers that transit via EAI. You can, from among the adapters registered, choose one with which to start the synchronization, sending the affected records through the adapter at issue via EAI to another system.
This synchronizer only affects the first load between a populated Protheus database and another database. There is no control, whether the record already exists or not, upon the other system. In the ideal synchronization scenario, the data exist in Protheus but not in the other integrated system. Once the synchronizer starts, it sends all records via EAI to the other system, in accordance with the rules of the adapter selected.
This is an implantation aid for you to send, from Protheus, the records of a given register through the EAI. It is not responsible for saving From-To records, internalId (given that a TOTVS Single Message is at issue) or for processing the business rule involved in the integrations.
For details on how to use this feature, refer to the EAI article in TDN, by accessing The EAI Protheus Synchronizer of Initial Loads.
