Scenario 1: In the DMZIn this scenario, the Mobility servers are located in the DMZ. The primary and standby warehouses are located inside the corporate network. For Mobility XE version 8.5 and higher, the machine(s) hosting the Reporting server and Reporting database (SQL server) are located inside the corporate network. Remote access to the Mobility console will only be available if TCP port 8080 is open for each Mobility server. If open only through the corporate firewall but not the external firewall, the console can only be accessed from within the corporate network. If access is desired from both the external and internal networks, port 8080 needs to be open through both firewalls for all Mobility server addresses. The Mobility servers must have access through the corporate firewall to the Reporting server and the Reporting database (SQL server), on TCP ports 1433 and 61616 respectively. The Mobility servers must be available on UDP port 5008 (Mobility's default port) to Mobility clients. If clients exist on the corporate network as well as externally, UDP port 5008 to each Mobility server must be available through both firewalls. If you are running a pool of Mobility servers, TCP port 5009 and UDP port 5009 must be accessible between the servers to allow for inter-server communication. The Mobility console uses TCP 5009, and the load balancing functionality uses UDP 5009. All Mobility servers must have TCP port 389 available for communicating with the Mobility warehouse. In this scenario the warehouse is collocated with the Mobility server(s) in the DMZ, so no firewall holes need be opened. If you choose to put the Mobility warehouse behind the corporate firewall, TCP port 389 must be open for each Mobility server for warehouse access. If you are running a standby warehouse in addition to the primary, access must be available for both. If you configured non-default ports for the Mobility server or warehouse, add your custom ports to the firewall exceptions list instead of the default ones listed above. No other ports beyond those listed above are required for NetMotion Mobility to function in this environment.
|
Scenario 2: Inside the Corporate NetworkIn this scenario, all the components of the Mobility XE system: Mobility server(s), warehouse(s), Reporting server and Reporting database (SQL server), are located behind the corporate firewall. If clients exist outside the corporate firewall, UDP 5008 access must be available to each Mobility server. If remote access to the Mobility console is desired, TCP port 8080 access must be available to each Mobility server. The Mobility servers must have access to the Reporting server and Reporting database (SQL server), on TCP ports 1433 and 61616 respectively. If you are running a pool of Mobility servers, TCP port 5009 and UDP port 5009 must be accessible between the servers to allow for inter-server communication. The Mobility console uses TCP 5009, and the load balancing functionality uses UDP 5009. All Mobility servers must have TCP port 389 available for communicating with the Mobility warehouse. If you are running a standby warehouse in addition to the primary, access must be available for both. If you configured non-default ports for the Mobility server or warehouse, add your custom ports to the firewall exceptions list instead of the default ones listed above. No other ports beyond those listed above are required for Mobility to function in this environment.
|