Self-Scanning Service
The Self Scanning Service communicates with other applications to retrieve master data, to calculate prices, promotions and taxes and to suspend the resulting transaction. Those services are normally included deployed within SDC or the POS Service app. The base URLs are configured in self-scanning-service.properties:
| Property | Description |
|---|---|
| remote-services.master-data.appUrl | The base URL to retrieve the item master data; running by default within an SDC. |
| remote-services.tax-service.appUrl | The base URL for Tax Service; running by default within a POS Service. |
| remote-services.cps.appUrl | The base URL for the Customer Profile Service |
| remote-services.price-calculation.appUrl | The base URL for Price Calculation Service |
| remote-services.mca-promotion-checkout.appUrl | The base URL for MCA Promotion Checkout |
| remote-services.basket-service.appUrl | The application URL for the Basket Service. |
| remote-services.tx-pool.appUrl | The application URL where the TX Pool is running (mostly SDC) |
Please note that the Self Scanning Service user has to be configured on the specific endpoint system as well in security.properties to set up the connection correctly.
Landscape Support
Remote services with landscape support have the default configured URL containing the system-landscape.id property placeholder, e.g. http://localhost:8080/service-name/sl/${system-landscape.id}. This placeholder is resolved automatically by the platform. The resolved value is the current landscape identifier; therefore, the called remote service is within the same landscape as the calling SSS. If the landscapes are disabled, then a default value is filled and the called remote service ignores it.
If a custom project needs landscapes to be handled differently (e.g. the landscape identifier is in the hostname or port number), the URL format can be customized directly in the project using the ${system-landscape.id} placeholder in the appropriate place.
Optional Connections: Sales Restrictions / Event Service
Several items, such as alcohol, are restricted to customers of a certain age. This has to be approved by store staff. GK Self Scanning provides the option to send an authorization request to a store assistant, who can then meet and approve the request. This reduces waiting time at the Self Checkout stations or re-enables frictionless checkout for BYOD devices.
In addition to a Store Assistant app, this functionality requires an Apache Kafka infrastructure to be available on the retailer's network. These Kafka servers are configured in self-scanning-service.properties:
| Property | Description |
|---|---|
| remote-services.event-service.kafkaBootstrapServers | A list of host/port pairs used to establish the initial connection to the Kafka cluster (no need to name the full set of servers).Value format: host1:port1,host2:port2,... |
More configuration properties with the prefix remote-services.event-service can be changed to fine-tune the behavior.
Optional Connections: Loyalty Service
GK Self Scanning supports the use of loyalty accounts. To login and show loyalty program information, the connection to GK Loyalty Service has to be configured in self-scanning-service.properties:
| Property | Description |
|---|---|
| remote-services.loyalty-service.appUrl | The base URL for the Loyalty Service |