Installation Mode

Select Required Features

Check the features you need to enable. Only the relevant installation steps will be shown.

Installation Steps

  1. Download and Extract

    Download the version that you would like from the releases page (use the "Service" download) (use the "Standalone" download), and extract the ZIP file. Copy the executable called TarasaGateway.WindowsService.exe TarasaGateway.Client.exe and the json file called client-settings.json to %programfiles%/TarasaGateway/, which is likely C:/Program Files/TarasaGateway. If this is your first time, you'll need to create this folder. Ensure the folder name is exactly TarasaGateway. a folder of your choice.

  2. Configure Settings

    In the TarasaGateway folder, open the file named client-settings.json in a text editor (Notepad works fine), and:

    1. Change the ServerUrl to the URL of the Tarasa application, including the /api/ suffix, for example https://www.example.com/api/
    2. Change the ApiKey to the API key of the user that should be used to connect to the gateway.
    3. Add the IntegrateUrl setting with the URL to your Flexpoint Integrate server, for example http://localhost:9995/integrate
  3. Install and Configure FlexpointFLEXPOINT

    To enable Flexpoint functionality, you need to install Flexpoint and ensure the Flexpoint Integrate server is running.

    1. Install Flexpoint on the machine running the Tarasa Gateway Client
    2. Start the Flexpoint Integrate service
    3. Verify it is accessible at the URL you configured in client-settings.json
  4. Install Ghostscript for PDF PrintingPDF PRINTING

    To enable PDF printing functionality, you'll need to manually install Ghostscript. Download the latest version of Ghostscript from https://www.ghostscript.com/download/gsdnld.html, and install it. Make sure it is installed in the "Program Files" folder, or that the "bin" directory is added to the PATH.

  5. Install Microsoft Word for Word to PDF ConversionWORD TO PDF

    To enable Word to PDF conversion functionality, you need to have Microsoft Word installed locally on the machine running the Tarasa Gateway Client. The gateway will use Word's COM automation to perform the conversion.

  6. Configure Firewall for WebRTCWEBRTC

    To enable local device connections via WebRTC, you need to allow outgoing connections in any firewall, including Windows Firewall.

  7. Create Windows Service

    Open a command prompt as administrator, and run these two commands:

    1. Basic installation (default settings):
      sc.exe create "Tarasa Gateway" binpath= "C:\Program Files\TarasaGateway\TarasaGateway.WindowsService.exe" start=auto
    2. With custom configuration and log paths (optional):
      sc.exe create "Tarasa Gateway" binpath= "C:\Program Files\TarasaGateway\TarasaGateway.WindowsService.exe --config my-settings.json --logs mylogs" start=auto
    3. Configure failure recovery:
      sc.exe failure "Tarasa Gateway" reset=0 actions=restart/60000/restart/60000/run/1000

    Note: Choose either option 1 (default) or option 2 (custom paths), not both. Then run option 3 to configure failure recovery.

  8. Start the Service
    1. Open the services control panel (use Windows-R and then type services.msc)
    2. Find the service named "Tarasa Gateway" and start it
  9. Run the Application

    Double-click TarasaGateway.Client.exe to run the gateway client. The application will run in the foreground and you can close it by closing the console window.

    Using Command-Line Parameters:

    To use custom configuration or log paths, open a command prompt in the gateway folder and run:

    TarasaGateway.Client.exe --config my-settings.json --logs mylogs
  10. Verify Installation

    If successful, a new logs folder will appear in the gateway installation folder (C:\Program Files\TarasaGateway\logs) (in the same folder as the executable), or in the custom location if you specified the --logs parameter. Inside, there should be a txt file with an entry like:

    2024-06-18 14:34:39.217 +02:00 [INF] Registered with server

    This confirms that the gateway has successfully connected to the Tarasa application.

Troubleshooting