Versions Compared

Old Version 86

changes.mady.by.user Sharan Foga

Saved on

compared with

New Version 87

changes.mady.by.user Sharan Foga

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: formatting, grammar and readability changes

...

  • In the parameters.properties file
    • By default the POS uses a virtual alphanum keyboard and a virtual numeric pad. If you prefer to use a real keyboard, change the ShowKeyboardInSaveSale parameter. (Note: You may even swap dynamically back and forth from the Admin Panel using "Virtual" button. But then the parameter will not persist.)
    • There is a related special parameter SwipWithCard which is, for now, used only to swipe card numbers using an MSR in the Client Profile dialog box (Promo Panel, Client Profile button). There are also sentinel parameters for setting MSR types.
    • If you use an external system for credit card payments then you may find it convenient to use the PosRefNum parameter which allows you makes entering payments references optional (i.e. so you dont have to enter them)
  • In pos-containers.xml and both-containers.xml (depending if you use one or the other)
    • xui-session-id : the POS terminal identifier (used during synchronisation for instance)
    • facility-id : related to the name you set for your facility on the ERP side
    • look-and-feel : see http://www.jgoodies.com/
  • In xui.properties (in framework/guiapp/config)
    • # isSameLogin : if equals "true" (false by default), a logged off user (blocked, time out, ...) can only log in with the same login/pwd couple.
  • There are also some technicals barcode scanning related parameters in jpos.properties

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). So in order to switch from a lanquage language to an other you have to load the POS 2 times. twice  It also takes care of possible font issues. But for now only for Chinese (it uses posstyles_zh.xml).
You may override this behavior (for instance to test) using

...

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.

Note that OOTB the login/pwd are 1/1 (or 2/2 for a non manager person) and you must open the register before being able to play with the POS.

To open the register click

  1. Click on the MGR button on the top and near the right

...

  2. and then on the "Open" button on the right side of the screen near the top.

If you need to do some JavaPOS settings you may find this page interesting

...