Upgrade ArcGIS Enterprise
Upgrading ArcGIS Enterprise requires upgrading each component. The sections of this page provide an overview of the process and links to specific instructions for upgrading each component.
Before proceeding with an upgrade, take a backup of your ArcGIS Enterprise deployment in case you need to recover the content, services, and data that existed prior to the upgrade.
Versions supported for direct upgrade
Recent versions of ArcGIS Enterprise support a direct upgrade to the latest version. Older versions may require multiple upgrades to reach the latest version of ArcGIS Enterprise. The table below indicates the latest version supported for direct upgrade for each version of ArcGIS Enterprise.
Caution:
Even if a software version supports direct upgrade, you may still need to perform multiple upgrades to access tools for migrating deprecated services, apps, data, or other items. Carefully review the considerations for upgrades before upgrading any ArcGIS Enterprise components.
|
Source version |
Latest target version supported for direct upgrade |
|---|---|
|
12.0 |
12.1 |
|
11.0 - 11.5 |
|
|
10.8 - 10.9.1 |
11.5 |
|
10.7 - 10.7.1 |
11.3 |
|
10.5 - 10.6.1 |
10.9.1 |
If your source version supports direct upgrades to your target version, the setup files for the target version of each component will automatically upgrade the component. There is no need to obtain and install each previously released version in sequence or uninstall your current version. For example, if your current version is 11.3, you can directly upgrade to version 12.1.
If your source version does not support direct upgrades to your target version, you will need to perform one or more upgrades to an interim version. For example, if your current version is 10.7.1, you cannot directly upgrade to 12.1. You must perform an upgrade to at least version 11.0, because this is the lowest version that does support direct upgrades to 11.5. The interim version can be no higher than 11.3, because that is the highest version supported for direct upgrades from 10.7.1. From an interim version within this range, you can perform a second upgrade directly to 11.5
ArcGIS Enterprise upgrade order
The recommended order to upgrade the components in your ArcGIS Enterprise deployment is as follows:
Upgrade ArcGIS Web Adaptor (for Portal for ArcGIS).
Upgrade ArcGIS Web Adaptor (for Portal for ArcGIS) for IIS or Java (Windows).
Upgrade the ArcGIS Server site serving as the hosting server.
Upgrade ArcGIS Web Adaptor (for ArcGIS Server).
Upgrade ArcGIS Web Adaptor (for ArcGIS Server) for IIS or Java (Windows).
If your ArcGIS Enterprise deployment includes them, upgrade any other federated server sites.
Federated server sites should match the version of the base ArcGIS Enterprise deployment.
See the upgrade information for any additional federated ArcGIS Enterprise servers you need to upgrade.
Install the Web Styles setup if you want to use a complete set of 3D symbology from Scene Viewer. For additional information, see Scene Viewer requirements.
Upgrade considerations
To ensure the success of your upgrade, there are a variety of considerations that you should take into account. Carefully review these considerations before proceeding with the upgrade process.
Take a backup of ArcGIS Enterprise before upgrading any components. If the upgrade process fails, you may need to use the backup to restore the previous state of your deployment.
Review What's new in ArcGIS Enterprise for information about changes in support and functionality.
The version of all base ArcGIS Enterprise components must be the same.
The system requirements may have changed in later versions. Make sure that you are able to meet the requirements of the version you are upgrading to for each component of ArcGIS Enterprise.
Make sure that the required ports are open for each machine involved in the upgrade.
Supported geodatabase versions may be different in later versions. You may need to upgrade your geodatabase as part of your ArcGIS Enterprise upgrade.
You don't need to upgrade ArcGIS Pro at the same time as ArcGIS Enterprise.
During an upgrade, if more space is needed for installed resources than is available in the default
/tmpdirectory, you can specify an alternate setup temp location by setting theIATEMPDIRenvironment variable to a larger directory.During upgrades, if the system temp directory does not have enough space to backup your files and folders, you can either run the
export TMPDIR=/path/to/new/tmpcommand to set a larger alternative temp directory, or expand the size of the system temp directory.You can upgrade a base deployment using ArcGIS Enterprise Builder if you used that builder to create the base deployment.
You can use ArcGIS Enterprise Cloud Builder for AWS, or ArcGIS Enterprise Cloud Builder for Microsoft Azure to upgrade your deployment if you used that builder to create the deployment.
You can use an identical, isolated standby environment to avoid downtime during an upgrade. As an administrator, you can upgrade your standby environment while your production environment remains accessible. To learn more about this upgrade strategy and about how to upgrade your highly available or replicated environment, see Upgrade highly available and replicated environments.
After the upgrade is complete, it is recommended that you run the
portalScan.pyandserverScan.pyscripts to check for security best practices with your upgraded organization.
Retired features
The following features were retired at version 12.0. If you make use of any of these features, upgrade to 11.5 and migrate away from them before performing any additional upgrades. See the ArcGIS Blog article Dive into ArcGIS Enterprise 11.5 before you delve into 12 for more information.
ArcGIS GeoAnalytics Server was retired at version 11.4. If you have a GeoAnalytics Server site federated with ArcGIS Enterprise, you must delete all your Big Data Fire Share items and remove or unfederate the site before upgrading ArcGIS Enterprise to 11.4 or later.
The following features were retired at version 11.0. If you make use of any of these features, upgrade to 10.9.1 and migrate away from them before performing any additional upgrades.