topic Re: Scripting replication and synchronization workflow with ArcGIS Server and Geodata Services in Python Questions https://community.esri.com/t5/python-questions/scripting-replication-and-synchronization-workflow/m-p/162277#M12430 <HTML><HEAD></HEAD><BODY><P style="background-color: #ffffff; border: 0px;">I believe we resolved the issue.&nbsp; It turns out that we did not need a geodata service in order to create checkout replicas and synchronize back to the parent versions.&nbsp; The issue stemmed from the ArcSOC objects and the pooling instance specifications (we are using 10.5).&nbsp; This article helped us to resolve our problem:&nbsp;<A class="jivelink1" href="https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/" title="https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/">https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/</A></P></BODY></HTML> Fri, 28 Jun 2019 12:59:51 GMT AdamG 2019-06-28T12:59:51Z Scripting replication and synchronization workflow with ArcGIS Server and Geodata Services https://community.esri.com/t5/python-questions/scripting-replication-and-synchronization-workflow/m-p/162276#M12429 <HTML><HEAD></HEAD><BODY><P>Our organization is currently using one instance of ArcGIS Server, where we have published a Geodata service that references an SDE connection file.&nbsp; Via a python script we are&nbsp;able to create a check-out replica using the same SDE connection file, edit the features, and check the&nbsp;edits/changes back in to the SDE.Production version.&nbsp; Once the changes have been checked in and synchronized to SDE.Production via another python script, I am able to use ArcMap/Catalog to see that the changes are immediately posted to the SDE.Production version.&nbsp; However, if we attempt to re-create the checkout replica, it does not contain any of these edits that are showing in SDE.Production.&nbsp; It is as if the current state of SDE.Production was never updated and we are replicating it's prior state.</P><P></P><P>Is there a specific way to synchronize the replicas so that changes are reflecting immediately?&nbsp; Could there be a delay in the edits becoming available for replication?&nbsp; Could this be due to pooling or recycling parameters?&nbsp; Any help would be greatly appreciated.&nbsp; There is next to zero documentation on how to use the ArcGIS Server resources for check out replication.&nbsp;</P><P></P><P>Thanks!</P></BODY></HTML> Wed, 26 Jun 2019 16:54:09 GMT https://community.esri.com/t5/python-questions/scripting-replication-and-synchronization-workflow/m-p/162276#M12429 AdamG 2019-06-26T16:54:09Z Re: Scripting replication and synchronization workflow with ArcGIS Server and Geodata Services https://community.esri.com/t5/python-questions/scripting-replication-and-synchronization-workflow/m-p/162277#M12430 <HTML><HEAD></HEAD><BODY><P style="background-color: #ffffff; border: 0px;">I believe we resolved the issue.&nbsp; It turns out that we did not need a geodata service in order to create checkout replicas and synchronize back to the parent versions.&nbsp; The issue stemmed from the ArcSOC objects and the pooling instance specifications (we are using 10.5).&nbsp; This article helped us to resolve our problem:&nbsp;<A class="jivelink1" href="https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/" title="https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/">https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/</A></P></BODY></HTML> Fri, 28 Jun 2019 12:59:51 GMT https://community.esri.com/t5/python-questions/scripting-replication-and-synchronization-workflow/m-p/162277#M12430 AdamG 2019-06-28T12:59:51Z