ArcGIS Server 10.7.1 offers new enhancements, tools, and bug fixes. For a list of issues that were fixed at 10.7.1, see the Issues Addressed List.
It is no longer possible to configure multiple server clusters in ArcGIS Server, and sites with multiple clusters will be reconfigured to a single-cluster architecture when upgraded to 10.7 or later versions. If you plan to upgrade an ArcGIS Server site that still has multiple server clusters configured, see Upgrade a multiple-cluster site for complete information and available options.
It's recommended that you review the deprecation notice to determine if your hardware and software components are still compatible with version 10.7.1, and to see a list of functionality that has been deprecated. To review which earlier ArcGIS product versions are compatible with ArcGIS Server 10.7.1, see Compatibility of ArcGIS Server with earlier versions.
This topic describes new features and developments in both 10.7 and 10.7.1, and indicates the version at which each item was introduced.
The ArcGIS Server documentation was improved at 10.7.
As with other ArcGIS Enterprise software components, the installed help has a new format: a local installation of all the content available on the ArcGIS Enterprise website. This allows you to access all parts of the ArcGIS Enterprise documentation from within ArcGIS Server Manager.
The ArcGIS Server help has also been reorganized. Content for administrators relating to site planning and configuration can now be found in the Deploy section; information and workflows on data in ArcGIS Server is now in the Manage Data section; and the Administer section has been restructured to improve the browsing experience.
Introducing ArcGIS Notebook Server
A new ArcGIS Server role has been introduced at 10.7. ArcGIS Notebook Server is a powerful server role specialized to host ArcGIS Notebooks. This places a comprehensive data science platform into your ArcGIS Enterprise deployment, integrated with the portal.
ArcGIS Notebook Server has a unique architecture. To provide each notebook author with an isolated workspace, the server role uses containers, which are virtualized operating systems configured with hundreds of Python libraries.
Because of this, ArcGIS Notebook Server has a different installation process than that of other ArcGIS Server roles. See the ArcGIS Notebook Server installation guide for complete steps.
At 10.7.1, ArcGIS Notebook Server now supports multiple-machine sites. Refer to the topic Join additional machines to an ArcGIS Notebook Server site for more information and complete steps.
ArcGIS Server 10.7 introduces shared instances, a configuration in which some or all of the map services published to your site from ArcGIS Pro use a pool of service processes (ArcSOC.exe processes) rather than having their own reserved instances. This conserves memory usage on your server machines by reducing the number of processes running when there is no need for them, and does so without detracting from service performance. To learn more, see Configure service instance settings.
At 10.7, administrators can now specify a maximum heap size setting for an individual service using the ArcGIS Server Administrator Directory. The service property javaHeapSize overrides the machine's socMaxHeapSize setting without affecting the settings of other services in the site. Increasing the value of this property is a possible solution to performance issues—for example, if the heap size limit is preventing the service from processing a very large file.
A legacy server architecture component has been removed from ArcGIS Server 10.7. This grants ArcGIS Server some noticeable performance improvements.
ArcGIS Server 10.7.1 includes several fixes and enhancements that improve the security of the software. It's recommended that you upgrade to 10.7.1 to help protect your ArcGIS Server infrastructure.
At 10.7, ArcGIS Server now sends a no-sniff web header with all web traffic by default. This header prevents the user's web browser from "sniffing" the content-type of requests away from the content-type declared by ArcGIS Server. This is a defense against cross-site scripting (XSS) attacks. There is an option to disable the no-sniff header, which should be used with caution.
As of 10.7, only communication over HTTPS is enabled in ArcGIS Server by default. Previously, communication over both HTTP and HTTPS was enabled by the default setting. The default TLS protocol settings have also changed: now, only TLS version 1.2 is enabled by default on ArcGIS Server, though you can modify the settings to enable TLS versions 1.0 and 1.1. For more information about these settings, see Secure ArcGIS Server communication.
Two new properties to improve efficiency in multinode sites are available starting at 10.7 in the Server Properties resource of the ArcGIS Server Administrator Directory. The first, machineSuspendThreshold, defines a time period of inactivity (where the machine does not register an active status) after which the site stops assigning administrative and publishing requests to the inactive machine. By default, this property is set to 60 minutes. The second, suspendedMachineUnregisterThreshold, defines a time period of inactivity after which the machine will be automatically unregistered from the site. It is disabled by default, given that unregistration is irreversible.
A new property, Under Maintenance, can be used to flag a machine participating in an ArcGIS Server site. When the property is set to true in the ArcGIS Server Administrator Directory, the machine will "fail" its regular health check operation. At 10.7.1, ArcGIS Web Adaptor will avoid passing service requests to any machine that has failed its most recent health check. You can also program your third-party load balancer or reverse proxy server to avoid passing service requests to such machines. Using this flag allows administrators to perform maintenance, such as an OS upgrade, on a machine without causing service requests to sit idle. You can set this property in the Edit Machine resource.
A new page, Jobs, is available in ArcGIS Server Manager under the Site tab at 10.7. On this page, you can query for current jobs for any of your site's published services, view information about each job, and intervene to cancel or delete jobs.
All requests made to ArcGIS Server services, such as to draw a map or locate an address, are now assigned a unique Request ID starting at 10.7. This ID is included in all logs involving the request, and is created for all services, including hosted services. Queries to the server logs can be filtered for a specific Request ID, allowing you to view a comprehensive timeline of how the request was processed. Doing so can aid your monitoring, troubleshooting, and server optimization efforts.
Starting at 10.7.1, print services will automatically adjust legends to only display patches for features that are visible in the current extent. This applies to map services published from ArcGIS Pro to ArcGIS Enterprise 10.7.1 and does not require any additional configuration.
Starting at ArcGIS Pro 2.4, you can now publish services directly from ArcGIS Pro to a stand-alone ArcGIS Server site at version 10.7 or later. See Introduction to arcpy.sharing in the ArcGIS Pro documentation for complete information.
To publish a geoprocessing service from ArcGIS Pro to a stand-alone ArcGIS Server using ArcPy, see Publish a geoprocessing service to a standalone ArcGIS Server.
You can now publish OGC-compliant services, such as WMS and WFS, from ArcGIS Pro to the ArcGIS Enterprise portal.
When you add the same feature class to a map multiple times and publish a feature layer that references an enterprise geodatabase, you can now enable the sync capability on the feature layer if the layer is read-only (only the query and sync capabilities are enabled).
The following are new at 10.7:
Inputs and outputs
You can move the jobs directory for one or more geoprocessing services from its local machine location to a Microsoft Azure cloud storage location. This can allay the storage impact of a geoprocessing service that receives a high volume of job requests.
You can now deploy custom script tools that were written using third-party Python libraries or the R-ArcGIS Bridge as geoprocessing services. To do so requires extra steps, which are detailed in the ArcGIS Pro documentation:
ArcGIS Server licensing roles
Many updates have been made across the ArcGIS Enterprise platform at 10.7 and 10.7.1:
ArcGIS GeoAnalytics Server
New tools and enhancements are available in the ArcGIS Enterprise portal. See What's new in the portal for details.
ArcGIS GeoAnalytics Server can now support writing results to big data file shares.
New in other ArcGIS Enterprise components
See the following topics to find out what's new in Portal for ArcGIS, ArcGIS Data Store, and the ArcGIS REST API Services Directory:
Geodatabases and databases
The following changes in functionality and support for databases occurred for 10.7.1:
- Log file tables for geodatabases in Oracle now use Oracle temp tables. Starting with 10.7.1, the Configure Geodatabase Log File Tables geoprocessing tool and ArcPy function no longer alter the log file configuration for geodatabases in Oracle.
- PostgreSQL 11 has been certified for 10.7.1. Therefore, new versions of the st_geometry library are available to allow you to create a geodatabase in PostgreSQL 11 or install the ST_Geometry type in a PostgreSQL 11 database. The new st_geometry library is available from My Esri and installed with ArcGIS Desktop and ArcGIS Server 10.7.1.
- PostgreSQL 9.5.x and PostGIS 2.2 are not supported for 10.7.1 and subsequent release geodatabases in PostgreSQL. Upgrade your database to a supported version.
- You can use operating system authenticated connections from ArcGIS 10.7.1 clients on Microsoft Windows to Microsoft SQL Server 2017 on Linux.
In 10.7, the following changes were implemented:
- ArcGIS 10.7 supports Oracle 18c.
- You can no longer create user-schema geodatabases in Oracle. You can continue to use and upgrade existing user-schema geodatabases at this release, but you should begin moving your data to stand-alone geodatabases.
- The use of Altibase databases with ArcGIS has been deprecated.
- You cannot create a geodatabase in Microsoft SQL Server 2012 or upgrade an existing geodatabase if it resides in a SQL Server 2012 database. Upgrade SQL Server to a supported release before you upgrade your geodatabase.