ArcGIS for Server is software that makes your geographic information available to others in your organization and optionally anyone with an Internet connection. This is accomplished through web services, which allow a powerful server computer to receive and process requests for information sent by other devices. ArcGIS for Server opens your GIS to tablets, smartphones, laptops, desktop workstations, and any other devices that can connect to web services.
To get started with ArcGIS for Server, you’ll need to prepare your hardware, software, and data, then you can set up GIS web services. Finally, you can use various types of applications to consume your services.
Preparing hardware, software, and data
The hardware you use for your server is typically more powerful than your other desktop computers. ArcGIS for Server requires a machine capable of running a 64-bit operating system. The ArcGIS for Server architecture is scalable, meaning you can add multiple machines if extra processing power is needed.
Depending on organizational requirements, you may need the help of your IT staff to allow your server to be accessed over the Internet. When planning your hardware and environment, remember that ArcGIS for Server can also be deployed on virtual machines or commercial cloud platforms such as Amazon EC2.
Once you install ArcGIS for Server, you can start using it right away or you can integrate it with your organization’s existing web server by installing the ArcGIS Web Adaptor. You also need to have ArcGIS for Desktop on at least one computer in your organization in order to publish GIS web services. This computer does not have to be the server.
Publishing GIS web services
If you’ve worked with ArcGIS for Desktop, then you know how to use applications like ArcMap and ArcGlobe to view and analyze GIS data. You use these same applications when publishing web services to ArcGIS for Server. You can author maps, geoprocessing models, mosaic datasets, and other GIS resources in ArcGIS for Desktop and use a simple wizard to share them as web services.
As part of the sharing process, ArcGIS alerts you to potential performance issues in the resource you are publishing. It also checks its list of registered data locations to understand whether it needs to fix any paths after your resource is moved to the server.
Below are the types of resources you can publish to ArcGIS for Server:
| GIS resource | What it can do in ArcGIS for Server | Which ArcGIS for Desktop application creates it |
|---|---|---|
Map document | Mapping, network analysis, Web Coverage Service (WCS) publishing, Web Feature Service (WFS) publishing, Web Map Service (WMS) publishing, Web Map Tile Service (WMTS) publishing, mobile data publishing, KML publishing, Geodatabase data extraction and replication, feature access publishing, schematics publishing | ArcMap |
Address locator | Geocoding | ArcCatalog or the Catalog window in ArcMap |
Geodatabase | Geodatabase query, extraction, and replication; WCS publishing; WFS publishing | ArcCatalog or the Catalog window in ArcMap |
Geoprocessing model or tool | Geoprocessing, Web Processing Service (WPS) publishing | ArcMap (geoprocessing result from the Results window) |
ArcGlobe document | 3D mapping | ArcGlobe |
Raster dataset or mosaic dataset or layer file referencing a raster dataset or mosaic dataset | Image publishing, WCS or WMS publishing | ArcCatalog or the Catalog window in ArcMap |
Folders and geodatabases of GIS content | Create a searchable index of your organization's GIS content | ArcMap |
If you don’t want to publish right away (for example, if you don’t have immediate access to the server machine) you can save a service definition file instead and publish it later. The service definition includes all the data paths and properties necessary to publish the service at another time. You can even choose to include all the source data, allowing you to truly package the service into one transferrable file.
During the publishing process, you'll enable capabilities that define the various ways your audience can use the service. For example, Feature Access is a popular capability that allows web users to edit vector features in a map service. Another example of a capability is WMS, which exposes your service through the Open Geospatial Consortium (OGC) Web Map Service (WMS) specifications.
See What types of services can you publish for greater detail on the services and capabilities available to you.
If you find that your web service does not offer the precise functionality or business logic that you need, you can expand it through server object extensions (SOEs). An SOE extends the base functionality of a web service using ArcObjects, the vast suite of components on which the Esri family of products is built. SOEs are an advanced option requiring custom development, but once written they are easy to deploy to your server or share it with others. No special software other than ArcGIS for Server is required to run an SOE.
Using GIS web services
Once you have web services running, you can use them in any application, device, or API that can communicate through HTTP (Hyper Text Transfer Protocol).
- ArcGIS.com and Portal for ArcGIS let you make and save maps that display your services. You can optionally overlay your service with other services.
- The ArcGIS APIs for JavaScript, iOS, Android, and Windows Phone allow you to develop custom applications that use the full breadth of your web services within an interface you design yourself.
- ArcGIS for Desktop applications, such as ArcMap, ArcGIS Pro, and ArcGlobe, are designed to use web services published by ArcGIS for Server. Using a service in these applications is often as easy as clicking the Add Data button.
- Any other application that can make a SOAP or REST web service request can connect to ArcGIS for Server. Supported clients range from smartphone and tablet apps that find the nearest grocery store to enterprise desktop applications for customer management or resource planning.
Maintaining your server
As you work with your server over time, you’ll need to adjust settings, add and remove services, and set up security rules. ArcGIS Server Manager is a web application included with every installation of ArcGIS for Server that provides an intuitive point-and-click interface for administering the server. You can use Manager to view the server logs, stop and start services, publish service definitions, define users and roles for security, and perform other similar tasks.
As easy as it is to use Manager, there are times when you may want to administer your server automatically through scripting. ArcGIS for Server has a REST-ful administrator API that allows you to automate server management tasks using the scripting language of your choice. For example, you can write a Python script that checks the health of your services periodically and sends you an e-mail if a service is detected to be down. This help system contains various examples of how to script your server administration.
Summary
ArcGIS for Server opens your GIS to many types of devices through web services. You can take the resources you’re familiar with through ArcGIS, such as map documents and geoprocessing models, and publish them to your server to create GIS web services. The services can be consumed in any application or device that can make a web service call using HTTP.
ArcGIS for Server includes an administrative Manager application and an API which you can use to maintain your server and set rules for security, logging, and other behavior.
The help system you are reading contains more detail on all of the subjects above.
Note:
To improve readability throughout this help system, the term “ArcGIS for Server” is used to refer to the product name, while “ArcGIS Server” is used to refer to the technology itself (in other words, the software running on your computer). In introductory topics like this one, you will more often see “ArcGIS for Server”, whereas the lower-level technical topics favor “ArcGIS Server”.