Installing the Self-Checkout Connector – Common Flow

Before You Begin

Before starting the installation, ensure that:

All system prerequisites are met. See Prerequisites for the Self-Checkout Connector (SCO) (supported operating system, IIS, network connectivity, authentication, and Hardware Station availability).
Business Central is configured according to the Business Central Configuration Requirements for SCO.
The correct SCO installer version matching the LS Central major version has been downloaded from the User Portal. See Getting the SCO Installer.

Starting the Installer

Log on to the target machine using an account with local administrator privileges.
Run the SCO installer.

The installer welcome screen is displayed.

Selecting Installation Components

During installation, you are prompted to select which components to install.

Self-Checkout Connector – Required for all installations.
NCR Connector – Optional. Required only for NCR self-checkout devices.

If you are installing SCO for non-NCR devices, select only the Self-Checkout Connector option.

Checking Prerequisites

When the Self-Checkout Connector component is selected, the installer shows a Prerequisites page that checks for the components the connector needs before it can run:

Internet Information Services (IIS)
.NET Runtime 8 (x64)
ASP.NET Core Runtime 8 (x64)
ASP.NET Core Module V2 (.NET Hosting Bundle)

Each component is marked [ OK ] when it is already installed. If anything is missing, keep Install the missing components before installing the connector selected (the default) and Setup installs them before it copies the connector files:

Missing IIS components are enabled with DISM.
The .NET Hosting Bundle is taken from a Prerequisites folder next to the setup file when one is present; otherwise Setup downloads it from Microsoft.
Either step can require a restart, and Setup tells you when it finishes.

If you clear the option, or continue while components are still missing, Setup asks you to confirm. Installation can finish, but the connector does not start until the missing components are installed. You can also install them manually beforehand. See Automatic Prerequisite Checks by the Installer.

Entering Common SCO Settings

The installer prompts for the common configuration values required for SCO to communicate with Business Central and Hardware Station.

Store ID - Store identifier matching the store configured in Business Central.
Service Token - Token generated in the Self-Checkout Connector card.
Hardware Station Base URL - Base URL of the Hardware Station used for payments and printing.
LS Central Base Endpoint - Base Endpoint of the LS Central Business Central instance.
Site Port - TCP port of the IIS site that hosts the connector and its Administration Portal. The default is 8077; enter a value between 1 and 65535. If the port is already used by another application, Setup warns you and lets you choose a different port, because the connector site cannot start on a port that is already taken.
Manufacturer - Device manufacturer (Diebold Nixdorf, NCR, or Custom).
Deployment Type - On-Premises or SaaS.

Manufacturer-Specific Options

If Custom is selected as the manufacturer, the installer prompts for a system folder where custom plugin assemblies are located.

Deployment-Specific Authentication

After entering the common settings, the installer prompts for authentication details based on the selected deployment type.

On-Premises – Username and password for Basic HTTP authentication.
SaaS – OAuth (S2S) authentication values.

Telemetry Settings

Starting with SCO version 29, the installer includes a Telemetry Settings page with a single Enable Telemetry checkbox, which forwards logs, traces, and metrics to the LS Retail Application Insights portal. Telemetry is optional and this checkbox is the only telemetry setting available during installation.

Additional telemetry options - a Retailer ID, which data categories to share with LS Retail, and optionally forwarding a full, unfiltered copy of telemetry to your own Application Insights resource - are configured after installation, in the connector's Administration Portal. See Telemetry in the Administration Portal topic.

Completing the Installation

After all required information is provided, the installer performs the following actions:

Copies SCO application files to the destination folder (IIS).
Updates the SCO settings database with the provided configuration values.
Configures the IIS site for the SCO application.

SCO Management Portal

When installation is complete, the installer attempts to open the SCO Management Portal.

From the portal, partners can:

Review and update SCO configuration
View connector and terminal status
Access logs
Start or stop the SCO Connector

Next Steps

Installing SCO for On-Premises Deployments
Installing SCO for SaaS Deployments
NCR Connector Installation (NCR devices only)