2.3. Connector Windows Service

2.3.1. Entering ApiKey into appsettings.json

Manually entering of the ApiKey into services/connector_host/appsettings.json is required before the Unity connector service installation.
The ApiKey must be copied from the DW administration application and encrypted with AesDataEncryptor using AesKey and RsaContainerName specified in appsettings.json. For instructions, please see Chapter 3.9 Connectors Installation in the DW Administration Tool Guide.

2.3.2. Installation

After the connector installation is done, a Windows service for the Unity connector must be installed.

This install script will install connector as Windows service which will be running under virtual Windows account NT Service\2Ring [instanceName] [connectorName].
Script will also assign this account all required rights and permission needed for this service to run.

Navigate to the {DW deploy folder}/services/connector_host directory and run install.ps1 as Administrator.

Use a non-core version of the Powershell (e.g Powershell 5.1).

  • Enter the name of the connector when prompted. Name must match with installed connector and is case sensitive.

  • Enter the instance name when prompted or use default [dw_8_3].

  • Choose whether a connector is custom or use default when prompted. Default [N] -> No for 2Ring connectors

Once the install.ps1 script finishes running, a Unity Connector Windows service will be installed from the connector folder. This service connects to the Unity Contact Center, collects data and sends it to the DW application to display. The service will automatically start running once installed with the configuration supplied during the installation.

Figure 8: Unity Connector Windows Service

../../_images/connector-installation-windows-service.png

2.3.3. Running connector via command prompt

The connector can also run via the command line. To run the connector in the command line, open it and navigate to the {DW deploy folder}/services/connector_host directory.
Run the following command:

ConnectorHost.exe --connector=Unity

Never run more than one instance of the same connector simultaneously, or the data may get corrupted. It is recommended to use the Windows service in a production environment and only use the command line mode for troubleshooting purposes. Do not forget to stop the service before running the command line mode.