- 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.
- From the DataHub server, access to the source/destination locations should be opened for normal traffic, including http and https.
- 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.
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.
- Login to DataHub server(s) with DataHub Service Account
- Go to Windows Settings, Proxy
- Enable 'Use a proxy server' setting
- Update the 'Address' and 'Port' with the applicable proxy values
DataHub Service Account
General account best practices when running a DataHub Platform clustered install.
- Create a service account (DataHub User) whose password does not expire
- Create a new Database “DataHub” and make the DataHub user a DB Owner.
- You have an Admin/Power User account who has full access to both side (Source and Destination).
- Make sure you are able to get to api.portalarchitects.com from the server.
- For Office 365/OneDrive for Business and Box, all users have to be provisioned.
- For Office 365/OneDrive for Business, the DataHub Transfer account(s) have to be added to Site Collection Administrator of each and every user.