HHAeXchange System Requirements

The following sections outline the baseline system requirements needed to run the HHAeXchange web application and Mobile App.

The HHAeXchange applications are compatible with the browsers listed below. Although the applications may run on additional browsers, some of the features may not be fully available when running in an unsupported browser.

  • Chrome

  • Edge

Must be latest public release of the browser, or one of the two previous releases.

Ensure the following when operating in the application:

  • Cookies are enabled.

  • JavaScript is enabled.

Component

Requirements

Operating System

Microsoft Windows 10

Microsoft Windows 11

Memory

Minimum 8GB

Processor

Intel® Core™ i5 @ 2.9GHz
Screen Resolution

1280 x 1024

1024 x 768

The HHAeXchange Mobile App can be run on the following:

  • Smartphones using the Android Operating System *6.0 (Marshmallow) or higher

  • Apple iPhones running iOS version *11.0 or higher

While HHAeXchange supports the listed mobile operating systems, we strongly recommend Mobile App users install the latest public mobile operating systems on their devices.

The following five Subnet IDs must be white-listed to facilitate proper communication between HHAeXchange and your network:

  • 70.36.25.160/28

  • 72.28.118.40/29

  • 70.36.27.192/26

  • 72.28.105.160/29

  • 198.35.49.128/26

HHAeXchange recommends using an internal DNS server to process DNS queries. An internal DNS server handles fewer requests from a smaller number of IP addresses related to your operations compared to a public DNS service, which can handle a much larger volume of requests from any business or public user on the world-wide-web.

HHAeXchange web application communicates with hhaexchange.com over secure HTTP protocol for exchanging information. You may see traffic from/to multiple subdomains within hhaexchange.com. For example:

All communication inbound and outbound is transmitted via https://*.hhaexchange.com to ensure that any additional subdomains that HHAeXchange introduces in the future can still work in your environment.

Internal Mail Servers must allow HHAeXchange domain to avoid denials categorization of HHAeXchange email as spam or junk and gray-listing. Also, ensure that your MX Records are not blacklisted and that your Mail Server’s SFP configuration permits authorized parties to send emails on your behalf.

HTTP/HTTPS communication to the following third-party domains (through port 80 and 443) must be enabled.

To configure connections per second for the firewall, determine the number of users connecting to the HHAeXchange application and multiply by 5. For example, if 100 users are to be connected to HHAeXchange, configure the firewall to allow for 500 connections per second to enable the HHAeXchange application to function at an optimal level.

If using the HHAeXchange Secure FTP environment for electronic data exchange, note that the following port must be opened for outbound connections:

  • For CoreFTP: Port 22

  • For JScape SFTP: Port 2222

The web application communicates with HHAeXchange servers over secure HTTP protocol through port 443. Port 443 must be enabled for outbound connections originating from your network to HHAeXchange. It is also recommended to leave the standard HTTP port 80 open for outbound communication.