You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc
+11-8
Original file line number
Diff line number
Diff line change
@@ -27,20 +27,23 @@ ifdef::backend-pdf[]
27
27
endif::[]
28
28
29
29
== Introduction to Entity Synchronization
30
+
WARNING: After https://issues.apache.org/jira/browse/OFBIZ-12212[OFBIZ-12212] "Comment out the SOAP and HTTP engines" this feature is no longer available OOTB. You need first to re allow the HTTP engine
31
+
32
+
30
33
31
34
The general idea behind the Entity Sync stuff is to re-create transactions from a central database into one or
32
35
more other databases, each represented by a set of records in the EntitySync and related entities.
33
36
34
-
Though the Entity Sync mechanism can be used without the now deprecated POS, it was mostly destined to it.
37
+
Though the Entity Sync mechanism can be used without the now deprecated POS, it was mostly destined to it.
35
38
It works well on a reliable network (LAN), it's a bit harder on Internet (WAN) but nothing impossible...
36
39
37
-
The four fields (lastUpdatedStamp, lastUpdatedTxStamp, createdStamp, createdTxStamp) are added to each entity and
38
-
automatically populated so that queries can be done on each entity to get all records created, updated,
39
-
or removed in a certain transaction, and so that in time order those transactions can be reproduced remotely
40
+
The four fields (lastUpdatedStamp, lastUpdatedTxStamp, createdStamp, createdTxStamp) are added to each entity and
41
+
automatically populated so that queries can be done on each entity to get all records created, updated,
42
+
or removed in a certain transaction, and so that in time order those transactions can be reproduced remotely
40
43
to get the data into the remote database in the proper order.
41
44
42
-
The no-auto-stamp attribute is used to tell the Entity Engine not to automatically add these stamp fields,
43
-
and not to automatically set the stamps when creating and updating the entities. It's false by default.
44
-
So by default these values will be automatically set, and when records are removed the primary key will be saved
45
-
in the EntitySyncRemove entity's table so that the record can be removed in the remote database.
45
+
The no-auto-stamp attribute is used to tell the Entity Engine not to automatically add these stamp fields,
46
+
and not to automatically set the stamps when creating and updating the entities. It's false by default.
47
+
So by default these values will be automatically set, and when records are removed the primary key will be saved
48
+
in the EntitySyncRemove entity's table so that the record can be removed in the remote database.
0 commit comments