Agave API

Author: Eric Vasbinder

Support Status:  APPROVED

Integration Method:  Direct ODBC and Import / Export Files

Connection Method:  IPSEC VPN

• TLS Database Endpoint (TLS VPN) possible IF specific external integration does NOT require automated imports into Vista

Hosted:  NO

Hosting Location:  EXTERNALLY in vendor’s cloud, connected over IPSEC VPN or TLS Database Endpoint (TLS VPN)

Additional Charge:  NO (VPN add-on included in every cloud contract by default - if not on your contract additional charge will be required to add VPNs)

Product Use Case:

This product is a solution that creates a single, documented API for access to and from Vista data.

Similar Products:

This product is similar to and competes with Ryvit.

ERP Connection Overview: 

As per many other server-side integrations to third-party products, this product is designed to talk to Vista's database using Import and export files.  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 server to server IPSEC VPN between our cloud and the vendor's multi-tenant cloud.

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.  This solution uses a data connector ("shim") between the Vista server and other third-party products.

Detailed Instructions:

• 1.  Stand up remote connectivity to our cloud:

     1.   TLS Database Endpoint (TLS VPN) set up if no imports to external third-party product is needed:  TLS Database Endpoint 

     2.  IPSEC VPN between hosting location of third party product and customer's Vista environment in our cloud: How do I set up an IPSEC VPN to access my Vista database directly?

  2.  Create a cloud Workspace account (LEGACY Method) to allow for mapping of drive over SMB:  See "Setting up Automatic Imports".

  3.  Map the Vista autoimport pickup directory using SMB file sharing:  Setting up Automatic Imports 

tl;dr:   All programmatic components of this solution must be hosted externally to Viewpoint's cloud environment. Customers who need to integrate this solution with Vista in our cloud need to use a TLS Database Endpoint (TLS VPN) or an IPSEC VPN.  Once the endpoint or VPN is configured and in place, we stand up a CloudWorkspace account to allow mapping of the import folder.  The customer and/or partner then configures their solution to map that drive.