Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Documented: Comment out the SOAP and HTTP engines (OFBIZ-12212)
Documents that the EntitySync feature is no longer available OOTB.
You need first to re allow the HTTP engine
  • Loading branch information
JacquesLeRoux committed Mar 30, 2021
1 parent 1bc8a20 commit 62e657f
Showing 1 changed file with 11 additions and 8 deletions.
19 changes: 11 additions & 8 deletions framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc
Expand Up @@ -27,20 +27,23 @@ ifdef::backend-pdf[]
endif::[]

== Introduction to Entity Synchronization
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



The general idea behind the Entity Sync stuff is to re-create transactions from a central database into one or
more other databases, each represented by a set of records in the EntitySync and related entities.

Though the Entity Sync mechanism can be used without the now deprecated POS, it was mostly destined to it.
Though the Entity Sync mechanism can be used without the now deprecated POS, it was mostly destined to it.
It works well on a reliable network (LAN), it's a bit harder on Internet (WAN) but nothing impossible...

The four fields (lastUpdatedStamp, lastUpdatedTxStamp, createdStamp, createdTxStamp) are added to each entity and
automatically populated so that queries can be done on each entity to get all records created, updated,
or removed in a certain transaction, and so that in time order those transactions can be reproduced remotely
The four fields (lastUpdatedStamp, lastUpdatedTxStamp, createdStamp, createdTxStamp) are added to each entity and
automatically populated so that queries can be done on each entity to get all records created, updated,
or removed in a certain transaction, and so that in time order those transactions can be reproduced remotely
to get the data into the remote database in the proper order.

The no-auto-stamp attribute is used to tell the Entity Engine not to automatically add these stamp fields,
and not to automatically set the stamps when creating and updating the entities. It's false by default.
So by default these values will be automatically set, and when records are removed the primary key will be saved
in the EntitySyncRemove entity's table so that the record can be removed in the remote database.
The no-auto-stamp attribute is used to tell the Entity Engine not to automatically add these stamp fields,
and not to automatically set the stamps when creating and updating the entities. It's false by default.
So by default these values will be automatically set, and when records are removed the primary key will be saved
in the EntitySyncRemove entity's table so that the record can be removed in the remote database.

0 comments on commit 62e657f

Please sign in to comment.