Skip to main content

Configuring Live Guard

Preparation

To get started, you need two things at the ready:

  1. Your Live Guard dashboard
  2. Your Watchtower device

Dashboard

Your dashboard is deployed along your EVA environment and accessible easily accessible by replacing api in your endpoint with sentinel, e.g.:

https://api.environment.on-eva.io -> https://sentinel.environment.on-eva.io

Credentials

In the future, the Live Guard dashboard will be accessible with your regular EVA credentials.

Device

Our Watchtowers are custom-built by OnLogic. The product number is NEWBLACK-CL210G-11. They cannot be publicly ordered, you need to contact our dedicated account manager at OnLogic, your Strategic Lead can provide you with their contact information.

These devices can be sent to your stores or HQ directly, as they ship with the right firmware pre-installed.

Configuration

First off, we set up our device, then we onboard it into our dashboard. Finally, we configure EVA to make use of Live Guard.

Set up device

To set up your device, make sure you unbox it first. In the box you'll find the following items:

  • Your Watchtower device
  • A power cable
  • Power cable adapters

Setting up your service is as easy as plugging two cables into Watchtower and turning it on.


  1. Use the power cable and your desired adapter to plug the Watchtower device into a power outlet.
  2. Connect the Watchtower device to your local network using an ethernet cable (use the correct ethernet port as pictured).
  3. Use the power button to turn on Watchtower. When turned on, a white light will show.

Onboard device

To onboard your device, head to your dashboard. You will be greeted by the login screen.


If this is your first time logging in, you will have to set up credentials first. Make sure to save these credentials properly, we don't support password resets here yet.

If this is not your first time logging in, you will probably skip the initial configuration screen.

Initial configuration

When logging in for the first time, you have to set up a Backend first. If you only have one EVA environment, you will probably only need one backend.

To configure your backend, you need to give it a descriptive name, provide your endpoint and provide an API key.

You can fetch your API key using LiveGuardGenerateApiKey in DORA.


New Black role required

The LiveGuardGenerateApiKey service needs to be called from a NewBlack role. Since this is a role that is (or will become) unavailable to you, we are working on a solution that won't require it anymore. For the time being however, you will have to ask our Support department to generate the key for you.

As for the service itself, it will need to be called on root OU to configure on the fallback device - and per OU if a Watchtower is placed inside your store for offline functionalities.

Then, under Add your first device, simply provide your Watchtower device's serial number and find the device.

Serial number

Your Watchtower's serial number can be found on the box and on a sticker on the device itself. The serial number consists of one letter followed by six numbers.

After looking up your device, indicate in which OU the device will be used (this can be changed later on) and board the device.

After boarding your device, you will be redirected to your Live Guard dashboard.


Configure EVA

After having set everything up in your Live Guard dashboard, we need to configure EVA.

SettingDescription
Devices:Watchtower:EndpointYour Live Guard endpoint. Example:

https://sentinel.xxxxxx.on-eva.io/
Devices:Watchtower:AccessTokenYour Live Guard backend access token (Explained below)
Sentinel:Availabletrue
Sentinel:BaseUrlhttp://sentinel.local:8080
Note

Please note that the Printr settings might affect above settings when you're working on a test environment.

Backend Access token

In order to be able to communicate with your Live Guard backend, an access token is required. This access token can be found in your Live Guard dashboard by clicking the backend we have just configured. This shows a menu where a primary and a secondary access token are shown. Either of these are okay to be used in the setting mentioned above.

Patience

After having configured Live Guard in its entirety, you'll have to exercise a little patience. It takes about a day for all of the relevant settings to be replicated to the Watchtower and thus, before it becomes usable.