Connectors
      Back to home
      1. Knowledge Base
      2. Connectors

      How does Bridge Facilitate the Connectivity with Connectors?

      The OvalEdge Bridge component allows seamless connectivity between any cloud-hosted server and on-premise or public cloud data sources.

      By installing the client component of the bridge within their own infrastructure, the customer only needs to whitelist the IP address of the data sources and respective ports within the bridge client for secure connectivity. This enables the OvalEdge platform to handle metadata-related activities, while the Bridge Component acts as a secure VPN connection between OvalEdge and the data sources.


      Bridge

      The bridge component (also called site-to-site communication) is used as a tunnel to transfer data from the client-hosted cloud/client-on-prem data center, with a handshake between the bridge server and the client.

      The Security Tool Kit is a combination of the required keystores, truststore, and relevant configuration files to establish the secured connection between the Bridge Server and Client.

      The OvalEdge Bridge has two components.

      1. Bridge Server: The Server in the SaaS cloud 
      2. Bridge Client: The Client is installed on a VM where client data sources are hosted (Cloud or On-Prem). 

      The Bridge Client installed requires the outbound ports to be opened on the Client Side Firewall (9443) and Whitelisted for the public IP provided by OvalEdge.

      The relationship of a Customer’s Cloud-based sources, the bridge, and OvalEdge:

      • The Bridge Server is hosted on the OvalEdge SaaS AWS server. 
      • The Bridge Client will be hosted/installed on any public cloud where the data Sources are hosted, and the OvalEdge platform needs to communicate. 
      • The Bridge Client VM only needs to be whitelisted in the client firewall, establishing secured communication with the OvalEdge application through the Bridge Server hosted on the SaaS VM.

      The relationship of a Customer’s On-Prem sources, the bridge, and OvalEdge:

      • The Bridge Server will be hosted on the OvalEdge SaaS AWS server.
      • The Bridge Client will be hosted/Installed on the On-Prem (on a VM provided by the Customer), where the data sources are hosted, and the OvalEdge platform needs to communicate.
      • The Bridge Client VM must be Whitelisted in the client Firewall, establishing secured communication with the OvalEdge application through the Bridge Server hosted on the SaaS VM.

      The Bridge operates using a Pull Model, where the Bridge client periodically checks for commands stored at the Bridge Server, which are issued from the OvalEdge Platform (such as establishing a connection to the dataSource). The client waits in the queue, which is essentially a Flow File containing data to be transmitted through the Bridge, and it does this polling every 5 seconds. 

      The pull time can be configured. The Bridge client receives the commands pulled from the Bridge Server and transmits the metadata to the OvalEdge Platform for processing.

      OvalEdge provides and maintains the Bridge component. The Bridge Server is hosted along with the OvalEdge Platform and interacts with the platform. Users perform actions such as crawling and profiling data sources. The Bridge Client actively pools for commands and securely executes connections to client data sources using TLS1.2 (Transport Level Security) and SSL for enhanced security.

      The Bridge Component, included as part of the SaaS offering, is designed to alleviate communication challenges with client data sources.

      How to set up a SaaS Bridge Client

      The following are the prerequisites required for installing the Bridge Software:

      • OS: Windows 2019/2022 or Ubuntu 20.04 
      • SSD: 64 GB, RAM: 16 GB, vCPUs: 2  for Windows OS
      • SSD: 200GB, RAM:32 GB for Ubuntu 20.04
      • Java: 8.0 
      • Whitelist the bridge client IP in all the required connector data sources. 
      • Outbound Open Port (9443) for the bridge client to communicate with the bridge server.
      • Outbound Open Port (9443) in Windows firewall defender for the bridge client to communicate with the bridge server and to access the Bridge-Client UI.

      After the prerequisites are provided, please follow the installation instructions below for Windows and Linux. 

      For any support required for installing the Bridge Client, please contact the OvalEdge Customer Success Management (CSM) Team.

      Copyright © 2023, OvalEdge LLC, Peachtree Corners, GA USA