Tools

Kiosk Administrator works in the background to gather information on kiosk applications and report it to Command & Control

OVERVIEW:

Kiosk Administrator is an application that runs locally (but invisibly) on each remote unit. It provides data to Command & Control.
Kiosk Administrator(KA) polls configured applications and devices on each system in order to ensure that everything’s operational. If it detects an exception, it can take local action - such as restarting an application, or rebooting the system - and will also forward a real-time alert to C&C. KA’s API can also provide third-party applications resident on each device with system status, peripheral status, and logging mechanisms (usage tracking, for example).


Kiosk Administrator works with Command & Control to give customers a complete view of their kiosk.

COMPONENTS:

User Interface – KA’s user interface shows the current status and recent event history. It allows local configuration changes (overrides configuration received from C&C, where applicable) and for the scheduler to be stopped/started. Under normal function KA runs minimized and is available from the Windows system tray.

KA Remote – The core of the KioskAdmin application is a .NET Remoting object that serves as an entry point for communication events from Command & Control as well as an API for other applications, local or remote.

KA Downloader – Technically a separate application, the Downloader asynchronously manages any download requests that come through the KA Remote API.

Database – A local SQL Express database stores transient data (such as usage logs awaiting upload to C&C) as well as permanent configuration information.

Kiosk Administrator provides customers with many remote control options for their kiosks.

Links:

Command & Control – KioskAdmin’s main job is to act as a liaison between one or more customer-facing applications and C&C. KA uploads usage data, order summaries, wellness alerts, and other data based on requests from local applications (or its own scheduled events) to CCService through HTTP. It also downloads content/software updates and reacts to events received on its Remoting interface - for example, a reboot request, file upload request, or check device request.

Device Components – KA has a generic interface that allows separate components (typically DLLs) to be attached. These components are responsible for polling and operating peripheral devices such as card dispensers and printers. In this way KA can be extended to support different devices without customizing the application itself, and in many cases these extensions don’t need to be performed by St. Clair. Once a device is configured within KioskAdmin it can be monitored and operated through the API.

UI Applications – Similar to peripheral devices, KioskAdmin can monitor and operate one or more separate applications. Typically these are kiosk applications which are started by KioskAdmin when it is loaded. KA monitors the performance of these applications, can restart them in response to issues, and generally ensures that they’re running properly at all times.
Multiple levels of application integration are possible, ranging from no integration (KA will terminate that application when needed and not manage any logging or device operation) to fully integrated (KA will request the application close itself, write log events requested by the application, and operate devices based on application requests).

Software pre-requisites

  • SQL Express Server
  • .NET Framework 3.5/4.0