Infrastructure and hardware considerations

Firewall

1. If a firewall is used, port 9090 is required to be opened to the primary DataHub server for communications to be enabled for the engine. 
2. From the DataHub server, access to the source/destination locations should be opened for normal traffic, including http and https. 
3. For best results for data migrations that reside on premise, DataHub servers should be installed or co-located in the same data center to reduce latency of source data access. 

Proxy Server

DataHub supports proxy server environments and utilizes the proxy settings from the underlying host Operating System; however, additional prerequisites may be necessary for a fully functional implementation. Note, proxy servers may introduce some latency within the transfer process. If a proxy is utilized, ensure that the DataHub servers have the manual proxy setup configured correctly. Note that proxy server environments add a layer of complexity and additional management that may impact troubleshooting, rate limiting, and overall performance.

1. Login to DataHub server(s) with DataHub Service Account
2. Go to Windows Settings, Proxy
3. Enable 'Use a proxy server' setting
4. Update the 'Address' and 'Port' with the applicable proxy values

DataHub Service Account

General account best practices when running a DataHub Platform clustered install.

1. Create a service account (DataHub User) whose password does not expire
2. Create a new Database “DataHub” and make the DataHub user a DB Owner.
3. You have an Admin/Power User account who has full access to both side (Source and Destination).
4. Make sure you are able to get to api.portalarchitects.com from the server.
5. For Office 365/OneDrive for Business and Box, all users have to be provisioned.
6. For Office 365/OneDrive for Business, the DataHub Transfer account(s) have to be added to Site Collection Administrator of each and every user.