Quick Start Guide
Table Of Contents
- 1 Electronic Shelf Labeling – A brief introduction
- 2 Label Family Introduction
- 3 Get the latest software and documentation
- 4 Core Appliance
- 5 Core Appliance initial setup
- 6 Start SES-imagotag Core Service and SES-imagotag Control Center
- 7 ESL Access Point Configuration
- 8 Selecting channels
- 9 Setup Security
- 10 Register labels
- 11 Start tagging
- 12 Templates
- 13 Integration
- 14 Troubleshooting
- 14.1 SES-imagotag Core Service Dashboard
- 14.2 Running the SES-imagotag Core Service as a background service
- 14.3 Where can get a demo/development license key?
- 14.4 Deleting the demo articles
- 14.5 Establish a network configuration when no DHCP is available – Step by step
- 14.6 Access point discovering with Bonjour Services
- 14.7 What can I do if the Status LED of the AP-2010 access point doesn’t turn blue?
- 14.8 Labels don’t come online
- 14.9 The encryption does not work
- 14.10 Unlocking labels
- 14.11 Starting Java applications
- 14.12 Encoding problems
- 14.13 Reserve RAM for Java heap space
- 14.14 Further documentation
- 15 Declaration
Core Service Quick Start Guide
Page 9 of 42
4 Core Appliance
The Core Appliance is a compact network device which can be used to run the SES-imagotag Core
Service in the store, instead of using an additional dedicated server. The SES-imagotag Core Service
is always needed in the store locally, also when cloud-based/centralized middleware systems like
Jeegy S3 Centralized/Jeegy Cloud or Bison ESL Manager is used.
4.1 Why is it needed in the Store?
l Continuous communication with access points and labels is required (even without tasks)
l Limited bandwidth between store and headquarters
l Disconnected VPN connection will prevent proper operation
l Load (image rendering…) is distributed to stores
4.2 Key Features
l Core Appliance is optimized to run up to 30 000 labels and 7 access points
l Easier and faster shop installations (“Plug and Play”)
l Is not recognized as an additional server
l Low maintenance
l Easy replace/restore when hardware crashes
l Limited deployment variabilities
l Lower development costs
l Lower support costs
l Better brand recognition
l Easier to sell as a “solution in a box”
l Less overall risk for system integrators