Page History

...

The localisation is done dynamically using the platform default. But it needs a 1st launch to be set (it dynamically changes the XUI's xpos.properties file). It also takes care of possible font issues. But for now only for Chinese (see posstyles_zh.xml).
You may override this behavior (for instance to test) using

1. the The languageSuffix parameter in the framework/guiapp/config/xui.properties file. This has an influence on the labels from XuiLabels.properties files.
2. forcing Forcing the JVM language using "-Duser.language=zh -Duser.country=CN" from the command line. This has an influence on the labels from PosUiLabels.xml file.

There are example synchronization settings in the data/PosSyncSettings.xml file, which is just an Entity Engine seed data file that gets loaded into the database. This example is for 3 tiers: a Main Central Server (MCS), a Per-Store Server (PSS) and the Point-Of-Sale client (POS). There are example sync settings to do 4 data moves including MCS -> PSS, PSS -> POS, POS -> PSS, and PSS -> MCS. This uses the Entity Synchronization service in the Entity Engine and the XML import file for this has pretty good comments about what does what. Note that the services shown in the example are configured to use the location "entity-sync-rmi" which is a pre-defined location specified in the serviceengine.xml file. Note that to help avoid duplication of sequenced IDs in the data that is synchronized up the chain from the POS terminals a unique prefix should be setup for the Entity Engine using the sequenced-id-prefix attribute of the delegator element in the entityengine.xml file.

...