Greenlight Compliance Solutions

Author: Eric Vasbinder

Support Status: Supported

Integration Method: ODBC Direct Database

Connection Methods:

• TLS Database Endpoint (TLS VPN) (PREFERRED)

• IPSEC VPN

Hosted: NO

Additional Charge:

• TLS Database Endpoint (TLS VPN) - NO

• IPSEC VPN - YES

Description:

As per many other server-side integrations to third-party products, this product is designed to talk to Vista's database directly using ODBC. This connection requires that the Vista server be "visible" to the third party system. To ensure that the two systems can communicate, we set up a TLS Database Endpoint (TLS VPN) (PREFERRED) or a server to server IPSEC VPN between our cloud and the customer environment.

Deployment Methodology:

We do not support hosting of this product in our cloud. As such, the customer must continue to host the actual program (i.e. "bits") in either their on-premise environment or in another cloud. As a result, since this product and Vista will be on separate networks, a VPN is needed to bridge the gap between the two networks.

Detailed Instructions:

• 1. Stand up a remote connection channel (either TLS Database Endpoint (TLS VPN) or IPSEC VPN) between the hosting location of the third party product and the customer's Vista environment in our cloud:

     1. TLS Database Endpoint (TLS VPN): TLS Database Endpoint

     2. IPSEC VPN: How do I set up an IPSEC VPN to access my Vista database directly?

  2. Create SQL account to allow third-party to authenticate to Vista: I need a dedicated SQL account for my integration to Vista in your cloud. How do I set that up?

  3. Configure the third-party solution to talk to the IP address of the new Vista server in our cloud.

tl;dr: Customers who need to integrate Greenlight Compliance's solution with Vista in our cloud need to purchase an IPSEC VPN. Once configured and in place, we stand up a SQL account to allow Insight to communicate to Vista. The partner then configures it to point to the new IP address of Vista in the cloud.