SelectView Gemini Web Portal

Author: Eric Vasbinder

Support Status: Supported

Integration Methods:

• ODBC Direct Database

• Automated File Imports

Connection Methods:

• PREFERRED: TLS Database Endpoint (TLS VPN)

  • NOTE: for TLS Database Endpoint (TLS VPN) to work, customer MUST be willing to forgo AUTOMATED imports of CSV files from SelectView's Gemini portal.

• IPSEC VPN

Hosted: NO

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:

Web portals used to provide a web UI for reporting on and editing data in Vista Payroll and Time Entry

Similar Products:

This product is similar in operation and feature set to Viewpoint's HR Portal and Field Management tools, as well as mJobTime and others.

IMPORTANT NOTE

RHUMBIX IS NOT DIRECTLY APPROVED AS AN INTEGRATION PARTNER INTO VISTA

However, this connector, supplied by SelectView is approved to connect to Rhumbix. For direct connection from Rhumbix to Vista, without involving the Gemini Portal, a separate approval process will be necessary.

ERP Connection Overview:

As per many other server-side integrations to third-party products, this product is designed to talk to Vista's database directly using ODBC to pull information from Vista. Time and other data can then be pushed into Vista using an automated or manual CSV file import process.

The ODBC and import connections require that the Vista server be "visible" to the third party system. To ensure that the two systems can communicate, we set up either the TLS Database Endpoint (TLS VPN) 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. This solution uses a data connector ("shim") between the Vista server and other components.

Detailed Instructions:

• 1. Stand up either a TLS Database Endpoint (TLS VPN) or an 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 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: 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 purchase an IPSEC VPN. Once the VPN is configured and in place, we stand up a SQL account to allow communication with Vista. The customer and/or partner then configures this solution to point to the new IP address of Vista in the cloud.