What are the Hayylo Adaptor virtual machine and account requirements?

The Hayylo Adaptor is a Windows services that runs on a virtual machine (VM) within your network. The adaptor regularly retrieves data from your Care Management System (CMS) database and sends it to your account in the Hayylo platform. 

Detailed below are the VM and account permission requirements.

 

Remote access

Hayylo staff will require remote access into your network in order to install and configure the Hayylo adapter. This may be via Windows RDP or a service such as LogMeIn or TeamViewer. This may also include VPN connection.

For additional security it suggested that remote access be provided to a "jump box" that provides local RDP access to the VM. However this is not a requirement.

 

Virtual Machine

Recommended specifications:

  • 1 x vCPU
  • 8 GB RAM
  • 40 GB HDD
  • Windows server 2012 or newer

The VM should have SQL Server Management Studio installed so that Hayylo staff can test the adaptor filter queries before installing the adaptor.

For performance and stability reasons, it is recommended that the Hayylo adaptor does not reside on the same server as the CMS or the CMS database.

The VM requires internal network access to the SQL Server instance(s) where the CMS databases are hosted, and also requires external (internet) access to the following API endpoints:

  • import-receiver.hayylo.com
  • *.s3.ap-southeast-2.amazonaws.com

 

Accounts and access

Hayylo staff will require a Windows account with the following:

  • Access to connect to the VM where the adapter will run
  • Read-only access to the UAT CMS database in SQL Server (during the UAT period) for testing the adaptor filter queries before installing the adaptor
  • Read-only access to the production CMS database in SQL Server for testing the adaptor filter queries before installing the adaptor
  • Local administrator access to install the adaptor

The Hayylo Adaptor service requires a Windows service account to run under, this account will require the following:

  • Read-only access to the UAT CMS database in SQL Server (during the UAT period)
  • Read-only access to the production CMS database in SQL Server
  • "Logon as a service" permission
  • Member of the local groups: Performance Monitor Users, Performance Log Users
  • Local filesystem access to write logs files in the installation directory

 

Was this article helpful?
1 out of 1 found this helpful