search
Ctrlk

Installing Gateway Agent

Tailent Gateway Engine is deployed as a self-hosted Windows service-grade application. The following prerequisites must be met:

  1. Tailent Gateway Agent installation kit (zip) - https://tailent-share.s3.eu-central-1.amazonaws.com/Orch/TailentGatewayAgent_1.3.3.0.ziparrow-up-right

  2. TAP Bundle (TAP Studio + TAP Assistant) builds with TGA functionality enabled

  3. Dedicated Windows User account belonging to the Administrators group (we'll assume it's called TGAUser for this exercise)

  4. Microsoft Terminal Services / Remote Desktop installed and configured for all target users

  5. Microsoft Visual C++ Redistributable 2013 (64 bit) must be installed on the Windows host environment. This can be obtained at https://www.microsoft.com/en-us/download/details.aspx?id=40784arrow-up-right

The following steps must be followed in order:

  1. The installation kit needs to be unzipped in a location where the user mentioned at #1 above has full read/write privileges (for reference, we'll assume that we'll be installing Tailent Gateway Agent to C:\Tailent\TGA for this exercise)

  2. Open a Command Prompt (as Administrator) and type the following command: sc create "TAP Gateway Agent" binPath= "C:\Tailent\TGA\TailentGatewayAgent.exe" The following message should be displayed, signaling the Windows service has been successfully created and is ready to be configured.

  3. Next, run services.msc from the Start Menu -> Run command and you should be able to see the recently created service listed:

  4. This service needs to be configured to run automatically:

  1. Aditionally, in order for TGA to be able to create Windows user session for unattended use, it also needs to be configured to run under the dedicated Windows user:

  1. Before starting this service, certain configuration parameters need to be set. This can be done by editing the configuration file found under the TGA folder, called appsettings.json. It should look something like this:

AllowedHosts - controls which addresses the TGA service will accept incoming requests. ListenPort - controls the port under which the TGA service will accept incoming requests. Token - represent a security token that must be used under all operational requests with TGA. Failure to provide this security token will lead to 403 Forbidden responses. This is a secret and should be changed to a randomly generated and secure string. For this setup exercise, we'll be leaving this token unaltered. Timeout - the timeout, in seconds, over which operational requests will fail. The default value of 120 seconds is a very safe setting and can usually be left unaltered.

  1. After reviewing all the above steps, start the service so incoming requests can be accepted.

Last updated