JavaPOS Demo Application: Getting Started
28
BEETLE /moPOS "Getting Started"
•
Whenever an NFC Tag is presented on the tablet, it will always ask the user if he
wants to connect to the first POS Device HUB configured under “UDMConnec-
tionHandler.servers”.
•
Whenever you ask the Admin Server to retrieve the list of all POS Device HUBs:
It will return the list of POS Device HUB’s retrieved from the configuration file
demo1.properties under “
UDMConnectionHandler.servers
” and automatically jumps to the
UDM POS Device HUB Usage panel. For odd server’s indexes (first, third, fifth, etc…) in the
list, the Dummy Admin Server will mark these as
free
(=with DISCONNECTED status), while
for even server’s indexes (second, fourth, sixth…), it will mark these as
claimed
(=with CON-
NECTED status).
Note: this is only for demonstration purpose and does not represent the real state of each
individual POS device HUB.
5.4
The difference in using the moPOS Admin Server and a
dummy Admin Server
The dummy admin server is only a feature for the Demo application when using just the Uni-
fied POS Interface of the POS Device HUB without usage of the moPOS Admin Server.
Usually when using a moPOS Admin Server which is running on
one
designated POS Device
HUB the demo application will query the admin server via a defined interface which POS
device HUB’s are really free and not already “claimed” by one connected tablet. Then the
admin server responses to the demo application with a list of all HUB’s indicating which are
free and which are already in use (or “claimed”) by another tablet. When not having a run-
ning Admin Server the list of all possible HUBs has to be named in the
demo1.properties
file
in the parameter
UDMConnectionHandler.servers.
When not having the Admin Server the automatic notification when docking a tablet into
one POS Device HUB also does not occur. However, simultaneous connections from multiple
tablets are then avoided alone by the Unified Device Manager of a POS Device HUB.