The reverse proxy is quite mysterious. Is it difficult to deploy it? This article explains the reverse proxy from a simple perspective and tells you that it is actually very simple.
Environment:
Machine A: ArcGIS Server 10.1, IP: 192.168.112.209
Machine B: as a pure web server, IIS 7, IP: 192.168.112.214 IP: Internet IP is installed.
The rest address exposed by machine A is: http: // 192.168.112.209: 6080/ArcGIS/rest/services. In fact, machine A is represented by the ArcGIS Server built internally for the cluster. There are many servers, or even the serve cluster deployed in the cloud environment. We don't care about this. The addresses exposed by clusters composed of all ArcGIS servers are http: // 192.168.112.209: 6080/ArcGIS/rest/services.
What we want to do is to shield a's service address. All GIS requests are first forwarded to machine A through machine B and then to machine A through machine B, machine A does not accept requests from the Internet.
Deployment steps:
1. Download Microsoft applications for IIS 7 from the official websiteProgramRequest route Version 2
Http://www.microsoft.com/zh-cn/download/confirmation.aspx? Id = 16239
2. The installation prompt includes the URL rewriting module and application Request Routing module.
3. The most significant indication after successful installation is: server farm or serverfarms
4. the URL exposed by machine ArcGIS Server A is as follows:
5. Set reverse proxy on machine B
6. After the successful operation, see:
If we replace 192.168.112.214 with an Internet IP address, we also implement reverse proxy for 209.
You need to set detailed rules.