Though the Entity Sync mechanism can be used without the POS, it was mostly destined to it. It works well on a reliable network, it's harder on Internet...
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
With The last released version with the POS available was R12.04.06. It's though still available in the R14.12 and 15.12 non released branches. It'll not be availble with the R16 release. All the documentation below is reliable and usable before revision 1754402 |
| Table of Contents |
|---|
Sync Setup Notes and Example
...
- Setup POS terminal with clean checkout from trunk
- In startofbiz.sh/bat set RMIIF to localhost (uncomment the line.)
- Create empty ofbiz database and populate with seed data (ant run-install-seed).
Note that for testing/learning you can load demo data as well.
For a production environment you will need to only load seed, then do all of your organization specific setup such as accounting, facilities, stores, etc. - framework/service/config/serviceengine.xml - enity-sync-rmi set to MCS.
- Start POS instance(s) (the OFBiz instance(s) which runs the POS, aka POS terminal(s)) in standard mode (web interface)
- Load EntitySync record for PULL on MCS instance (the OFBiz instance which runs the MCS)
- Load XML data you want to setup on POS instance to trigger PULL sync
- Load EntitySync PUSH on POS instance(s).
- When pull is finished, load XML data you want to setup to trigger PUSH
- Shutdown POS instance(s)
- pos-containers.xml on POS instance(s) - set xui session id = <facilityId-pos terminal number> ex. 10020-1.
- pos-containers.xml on POS instance(s) - set faclility ID = <facilityId) ex. 10020.
Don't forget to change entityengine.xml on all POS instance(s) to include a prefix for record id's.
Otherwise you will get record id conflicts when instance(s) push records to the MCS.
This is done by adding the "sequenced-id-prefix" attribute to the default delegator. For example:Code Block <delegator name="default" entity-model-reader="main" entity-group-reader="main" entity-eca-reader="main" distributed-cache-clear-enabled="false" sequenced-id-prefix="10020-1"> <group-map group-name="org.ofbiz" datasource-name="localpostgres"/> <group-map group-name="org.ofbiz.olap" datasource-name="localpostgres"/> </delegator>- Add PosTerminal record to MCS database.
You must create a PosTerminal record for each POS instance you need to synchronize with MCS.
Once this record is added you can start your POS instance and attempt a synchronization. - Start your POS instance in rich client mode. (add -pos after ofbiz.jar in startup file.)
...
- Initiate your PULL with a recurrence of about 5 minutes (do not setup any PUSH processes yet).
- Locate a record known to not PULL correctly and verify that it did not pull this time.
- Update the timestamp on the MCS for that record. Have the xml ready to load thru web tools before starting the PULL process. The key here is to just make sure the date and time is set to something later than when the job ran.
- Let the PULL run again and check the record on the POS client to see if it updated properly this time.
Finally since you went so far, you might be interested by this article There is No Now - Problems with simultaneity in distributed systems