nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Advantages of using the export acknowledgement message?

rawansaleh1

Could anyone tell me what is the advantages of using the “export acknowledgement message” in replica?

I couldn’t figure out what is the real meaning of using this tool. What is the effect of it if we don’t use it after replica in disconnected environment?

Best,

Rawan

Trouver plus de publications taguées avec

Accepted answers

Asrujit_SenGupta

When replicating in this type of environment, it is important for the data receiver to send an acknowledgment message after receiving data changes as often as possible. If no acknowledgment messages are received, the data sender resends changes and maintains the information needed to resend changes until those changes are acknowledged. As a result, the data sender's geodatabase can become large and new data change messages can also become large.

As the above statement mentions, the Data sender will resend the changes till those changes are acknowledged.

As a result, the data sender's geodatabase can become large and new data change messages can also become large.

This part is not because of the previous statement. This is just indicating that as and when the data in the Data Sender geodatabase keeps on increasing with time, the new data change messages will also keep becoming larger, because the previously sent change messages have not been acknowledged yet and the data sender gdb is sending all changes.

All comments

Asrujit_SenGupta

Great! Please mark the thread as answered and close it, if you have no more doubts on this one!

rawansaleh1

Thank you Asrujit for your feedback.

This is clear now.

Best,

Rawan

Asrujit_SenGupta

When replicating in this type of environment, it is important for the data receiver to send an acknowledgment message after receiving data changes as often as possible. If no acknowledgment messages are received, the data sender resends changes and maintains the information needed to resend changes until those changes are acknowledged. As a result, the data sender's geodatabase can become large and new data change messages can also become large.

As the above statement mentions, the Data sender will resend the changes till those changes are acknowledged.

As a result, the data sender's geodatabase can become large and new data change messages can also become large.

rawansaleh1

Thank you Asrujit for your feedback, as I can see from the topics that if we don’t export the acknowledgment message that will make the sender to resend changes until those changes are acknowledged. As a result, the data sender's geodatabase can become large and new data change messages can also become large. I can’t understand exactly how that will enlarge the data sender geodatabase?

Best,

Rawan

Asrujit_SenGupta

A quick tour of synchronizing disconnected replicas

Exporting an acknowledgment message

Go through the above links, to understand what it actually does during the complete synchronization cycle...

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.