Configuring Thin POS Client
| Configuration files |
|
POS Thin Client does not have its own business logic, master data or other persistence. The Thin Client operates in the store contacting the POS Service for each function call. The POS Service is a central application that provides the POS business logic to all POS Thin Clients in the store via remote interface. The POS Service also provides access to master data from central master data repository and stores the finished POS transactions in the Central Transaction Pool.
The following configurations are required for the use of a Thin Client:
- Connection to the POS Service
- POS Service configuration
Setting up POS Thin Client
To set up the POS Thin Client, proceed as follows:
- Configure the connection to the POS Service in the file clientSystem.properties:
ServiceConfigs.Default.masterUrl=http://localhost:8080/pos-service/tenants/${SystemConfig.tenantId}/stores/${SystemConfig.retailStoreId}/services SystemConfig.smartPosEnabled=false - Configure the connection to the POS Service in the file services.properties:
SmartPOSServiceConfig.enabled=false
Configuring connection to the Command Channel
- Configure the connection to the Command Channel in the file command-channel.properties:
gkr.command-channel.client.baseUrl=https://localhost:50443/swee-sdc/tenants/${SystemConfig.tenantId}/stores/${SystemConfig.retailStoreId}/rest/services/command-channel - Enable the Command Channel scheduler in file scheduler_command-channel.properties:
scheduler.enabled=true - Set the remote URL for the Command Channel data service in file data-store.properties:
remote-object-factory.serviceUrlPrefix=https://localhost:50443/swee-sdc/tenants/${SystemConfig.tenantId}/stores/${SystemConfig.retailStoreId}/remoting