Author: Eric Vasbinder
Support Status: APPROVED
Integration Method: ODBC Direct Database
Connection Method: TLS Database Endpoint (TLS VPN) / Hosted Data Connector (LEGACY)
Hosted: NO (Current) / YES (Legacy)
Hosting Location: EXTERNALLY in vendor's or customer's environment, connected over a TLS Database Endpoint (TLS VPN)
Hosting in Viewpoint cloud allowed only for existing customers with GCPay already hosted in our cloud (LEGACY)
Additional Charge:
CURRENT: NO (VPN add-on included in every cloud contract by default - if not on your contract additional charge will be required to add VPNs)
LEGACY: Yes (1x Standard Server and 1x Management Fee)
Vendor URL: https://ww3.gcpay.com/
CRITICAL NOTE
For existing customers who are already hosted in our VEC RDP, TC1, and VP1 environments who ALREADY have GCPay's data connector hosted in our cloud:
You are allowed to continue hosting GCPay with us even if you upgrade from VEC RDP licensing to TC1. Please be aware that this exception does NOT apply to customers in VFC wishing to upgrade to TC1.
GCPay simplifies the application for payment processes between general contractors and subcontractors by automating the payment application process.
N/A
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) between our cloud and the customer or vendor environment where the data connector is housed.
As of this time, we no longer support hosting of this product in our cloud for new installations. As such, the customer must continue to host it in either their on-premise environment or in another cloud. As a result, since this product and Vista will be on separate networks, a TLS Database Endpoint (TLS VPN) is needed to bridge the gap between the two networks. This solution uses a data connector ("shim") between the Vista server and other third-party products.
Stand up remote connectivity to our cloud:
TLS Database Endpoint (TLS VPN) between hosting location of third party product and customer's Vista environment in our cloud.
NOTE: An IPSEC VPN will also work and may be preferrable if you have other needs for direct SMB file system access to Vista's server.
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?
Configure the third-party solution to talk to the DNS name of the new Vista server in our cloud.
tl;dr: Customers who need to integrate GCPay with Vista in our cloud need to host the physical bits in an external location, connected over the Internet via a TLS Database Endpoint (TLS VPN). Legacy VEC RDP, TC1, or VP1 customers may continue to host the bits for GCPay within our cloud, but ONLY if already doing so.
Monday, 14 November 2022 at 11:38AM:
Added Vendor URL
Tuesday, 30 August 2022 at 09:55AM:
Updated to show that legacy VEC RDP customers with GCPay's data connector already hosted can continue to keep it hosted in our environment, BUT that this hosting will eventually go away.
Post date: Feb 6, 2020 6:19:11 PM