Hybrid Deployment

Hybrid deployment allows you to run OData and SQL endpoints locally, without routing data through Skyvia. It works via the agent application.

The agent connects to Skyvia only to retrieve endpoint metadata. All data operations are performed directly between the agent and your data source, ensuring that your data never passes through Skyvia services.

To host an endpoint locally, specify an agent on the endpoint overview page and configure an IIS website with the Connect web service on the computer where the agent is installed.

Requirements

Hybrid deployment requires IIS to be installed on the machine where you host the endpoint. If IIS is not installed on your computer, perform the following steps:

  1. In Control Panel, select Programs and Features.

  2. Click Turn Windows features on or off.

  3. Expand Internet Information Services -> World Wide Web Services -> Application Development Features, and ensure the following are selected: .NET Extensibility 3.5, .NET Extensibility 4.8, ASP.NET 3.5, ASP.NET 4.8.

    IIS Installation

How to Set Up Endpoint

To mark the endpoint as local, perform the following steps:

  1. On the endpoint overview page, click Set up at the bottom.

    Endpoint overview with Hybrid deployment

    If the Set up button is not available, the endpoint either does not support hybrid deployment or your Connect plan does not include it. Currently, hybrid deployment is supported only for database endpoints using agent connections.

  2. Select the agent that will host the endpoint.

    Selecting agent for Hybrid deployment

    For endpoints using an agent connection, this must be the same agent as in the endpoint connection.

After this, the hybrid deployment is enabled for the endpoint. It is not available by the URL from https://connect.skyvia.com any more.

Endpoint overview with Hybrid deployment enabled

How to Disable Hybrid Deployment for Endpoint

To disable hybrid deployment, follow these steps:

  1. In the bottom of the endpoint overview page click Setup.
  2. Click Remove agent and then click Remove anyway.

After this, the endpoint is hosted on https://connect.skyvia.com again.

How to Set Up Web Service

After installing the agent, the Connect web service files are located in the in the Connect subfolder of the installation folder. By default, C:\Program Files (x86)\Skyvia Agent\Connect

Skyvia Agent installation folder

1. Check Settings in *.config Files

Make sure that the serviceAddress value in the Agent configuration file matches the value in the web.config file of the Connect web service. Depending on the agent version you use, the configuration file may be one of the following:

  • Skyvia.Agent.Client.exe.config
  • Skyvia.Agent.Client.UI.exe.config
  • Skyvia.Agent.Client.UI.x64.exe.config
  • Skyvia.Agent.Client.x64.exe.config

Skyvia Agent config files

If the serviceAddress value is different, update it so that it is the same in both:

  • the agent configuration file
  • the Connect web.config file

The default value is "localhost:9292", where:

  • localhost is the standard net domain name, reserved for the local computer
  • 9292 is the port used by the connection.

2. Set Up Connect as IIS Web Service

After this, set up Connect as an IIS web service. For example, you can do it in the following way:

  1. Add a new website.

    Adding website in IIS

  2. Specify the website settings:

    • Site name — any name (e.g., Skyvia Connect)
    • Physical path - the Connect folder from the agent installation directory
    • Port - the port by which the endpoint is available, for example, 8080.

    IIS website settings

  3. Make sure the Skyvia Agent application is running.

  4. Open the web site in the browser to verify it works. For example, you can open a test page http://localhost:8080/healthcheck/ping

Endpoint URL

Each endpoint has a unique token. To get it, copy the endpoint URL from the endpoint overview page on Skyvia.

For example, https://connect.skyvia.com/o0913b7q

The token is the part after the domain: o0913b7q

To access the endpoint, append the token to the address of your local Connect service. For example:

The result endpoint URL: http://localhost:8080/o0913b7q/