Note: The following deployment strategies are organized from official documents, primarily to facilitate later review of various deployment scenarios. 1, single-machine deployment and reverse proxy1.1. Reverse proxy
The reverse proxy can take the ArcGIS Web adaptor or a third-party reverse proxy server.
1.2. Deployment Architecture
1.3. Security architecture for public network
If the map service needs to be published for public networks, it is recommended that you use a reverse proxy to isolate ArcGIS for server to increase the security of your GIS server. Typically, an enterprise-class firewall is added between the access tiers, with the following architecture:
1.4, third-party reverse proxy configuration
In Apache, for example, the reverse proxy uses the mod_proxy and mod_proxy_http modules, which need to be configured with these two modules, which can be opened in httpd.conf:
LoadModule Proxy_module modules/mod_proxy.so
LoadModule Proxy_http_module modules/mod_proxy_http.so
Then add in the httpd.conf:
Proxypreservehost on
Proxypass/arcgis Http://gisserver.domain.com:6080/arcgis
Proxypassreverse/arcgis Http://gisserver.domain.com:6080/arcgis
If you need an open management feature, continue to add the appropriate configuration in HTTP.D.
If you change the default site name ArcGIS, you also need to make additional settings:
(1) Log in to the Server admin site;
(2) Open system->properties->update, enter the new configured site name in the properties:
{
"Webcontexturl": "Http://gisserver.domain.com/mygis"
}
(3) When the update is complete, restart the Server service.
2, single-machine deployment and master-Standby mode
ArcGIS for server supports the main standby mode, but requires third-party load balancer software or hardware.
2.1. Master-Standby Architecture
In primary and Standby mode, the two GIS servers need the exact same environment, including: A separate service directory, Configuration Storage, and so on. If you are using file-based data and do not recommend using a network share, it is recommended that you keep a separate copy of each GIS server, or use a database or storage device.
In master and Standby mode, you need to ensure that the services on both GIS servers are synchronized. The usual methods are:
(1) Use the Custom admin script to implement;
(2) Virtualization technology.
3, single-machine deployment and master-Master mode
ArcGIS for server supports primary master mode, but requires third-party load balancer software or hardware.
3.1. Master-Master Architecture
In primary master mode, the two GIS servers require the same environment, including: A separate service directory (cache, jobs, system), Configuration Storage, and so on. However, the output service directory must be shared with two GIS servers .
If you are using file-based data and do not recommend using a network share, it is recommended that you keep a separate copy of each GIS server, or use a database or storage device.
In primary master mode, you need to ensure that the services on both GIS servers are synchronized. The usual methods are:
(1) Use the Custom admin script to implement;
(2) Virtualization technology.
4. Cluster deployment and Web Adaptor
Use the Web adaptor to enable flexible cluster deployment. The general architecture is as follows:
Each node in a clustered deployment GIS server needs to use the same installation account, shared configuration store and service directory, shared data, or local data copy.
To prevent web adaptor single point of failure, you can also use a third party to implement a Web adaptor cluster.
To make reasonable use of resources, you can also set up different cluster groups in the server. If you publish a map service in cluster Group A, publish the GP service in cluster Group B.
5. Cluster deployment and third-party load Balancing
ArcGIS for server supports cluster deployment using third-party load balancer software or hardware.
ArcGIS 10.3 for Server deployment policy