The system and hardware requirements required to run Portal for ArcGIS are listed below. A diagnostics tool runs during the setup to help you determine if your machine meets the minimum system requirements. For information about earlier versions, see Esri Support. If your Portal for ArcGIS organization will use a premium app, such as ArcGIS Pro or Drone2Map for ArcGIS, you will also need ArcGIS License Manager 2018.0 to configure your premium app licenses to specify which members can use the software. See the Portal for ArcGIS Administrator Guide, License Manager Reference Guide, and the License Manager system requirements for more information.
It's recommended that you review the deprecation notice to determine if your hardware and software components are still compatible with version 10.6.1.
Operating system requirements
The following 64-bit operating systems satisfy the minimum operating system requirements. Support is not provided for 32-bit operating systems; the setup will only proceed if the operating system is 64 bit. Portal for ArcGIS is only supported on Linux x86_64, on CPUs that adhere to the x86_64 architecture (64 bit), with supported Linux releases.
Machines with an underscore (_) in the name are not supported. The setup will not proceed if an underscore is detected in the machine name.
You cannot install the software as a root user. If you attempt to do this, the installation will not proceed and a diagnostics tool will display an error message indicating that you cannot install as root.
| Supported operating systems | Latest update or service pack tested |
|---|---|
Red Hat Enterprise Linux Server 7 | Update 5 |
Red Hat Enterprise Linux Server 6 | Update 9 |
SUSE Linux Enterprise Server 12 | Service Pack 2 |
SUSE Linux Enterprise Server 11 | Service Pack 4 |
Ubuntu Server LTS | 16.04.3 |
CentOS Linux 7 | 7.5 |
CentOS Linux 6 | 6.9 |
Scientific Linux 7 | 7.5 |
Scientific Linux 6 | 6.9 |
Oracle Linux 7 | Update 5 |
Oracle Linux 6 | Update 9 |
Prior and future updates or service packs on these operating systems are supported unless otherwise stated. The operating system version and updates must also be supported by the operating system provider.
Note:
Esri Technical Support is available for CentOS, Scientific Linux, and Oracle Linux versions that provide full binary compatibility with an equivalent supported Red Hat version. As a prerequisite for logging a defect, any software issue on these operating systems will be attempted to be reproduced on Red Hat Enterprise Linux. For Oracle Linux, support is predicated on the use of the Red Hat compatible kernel.
Caution:
If you want to install the software, run the ArcGIS Software Authorization Wizard, or run the Check for Updates tool using the operating system graphical user interface (GUI), the X Window System package group is required.
The following package groups are required.
Red Hat Enterprise Linux Server requirements
Red Hat Enterprise Linux Server 6 and 7
- gettext
SUSE Linux Enterprise Server
SUSE Linux Enterprise Server 11 and 12
- gettext-runtime
Ubuntu Server LTS
Ubuntu Server 16.04 LTS
- gettext-base
Hardware requirements
- Processor: 4 cores for 100 concurrent users
- Memory/RAM: 8 GB
- Disk space: 10 GB
All content created by your users will also be stored on disk. Carefully consider how data will be uploaded and created by your users and allocate disk space accordingly. If desired, you can change the location of where the portal stores its content after installing the software.
Temp space requirements
By default, resources are extracted to the system /tmp directory. This directory must have read, write, and execute permissions enabled. If the required space is not available in the /tmp directory, the setup program will attempt to extract resources to the user's HOME directory. If the required space is not available in the user's HOME directory, the setup program will report an error indicating this problem. Optionally, you can specify an alternate temp location by setting the IATEMPDIR environment variable.
File system requirements
On Linux systems, the ext3 file system limits the number of item subfolders to less than 32,000; this means your portal is limited to having no more than 32,000 items. No new items can be added to Portal for ArcGIS when this limit is reached. It is recommended that you update or move the installation directory to an ext4 or xfs file system that does not have this limitation. The file system must also be supported by the operating system provider.
Note:
The btrfs file system is supported only if adequate disk space is allocated for the metadata used by btrfs. Run command “btrfs filesystem df /” to confirm.File handles limits
For the portal to run properly, the file handle limits for the installation user are required to be set to 65,535. An installation diagnostics tool will check to validate whether the limits are set properly in the /etc/security/limits.conf file. If the limits are set incorrectly, the diagnostics check will fail.
There are soft and hard limits for file handles on Linux. To determine the limits, use the following commands:
- Soft limit: ulimit -Sn
- Hard limit: ulimit -Hn
To increase the soft and hard limits, you'll need to edit the /etc/security/limits.conf file with superuser access. For example, add two lines in the file like this:
<Portal for ArcGIS installation user> soft nofile 65535
<Portal for ArcGIS installation user> hard nofile 65535
After making this change, you will need to log out and log back in with the particular user for the new values to take effect. To verify that the limits have been modified appropriately, you can use the ulimit -Sn and ulimit -Hn commands as described above.
Firewall settings
Portal for ArcGIS communicates on ports 7080, 7443, 7005, 7099, and 7654. You'll need to open these ports on your firewall before installing the software. For more information, see Ports used by Portal for ArcGIS.
Domain name service (DNS) and fully qualified domain name (FQDN) requirements
Your organization's domain name service (DNS) needs to include an entry of the fully qualified domain name (FQDN) of the machine hosting Portal for ArcGIS. Similarly, if you'll be using ArcGIS Server with your portal, it's recommended that you include FQDN entries for each site you intend to federate with Portal for ArcGIS.
If desired, you can configure your DNS to use a friendly name for the portal (for example, friendly.domain.com instead of portal.domain.com). When doing this, assign the name to the portal machine before you install the software. Then use the friendly name when setting up the portal. For example, setup activities that require use of the friendly name include the following:
- Configure ArcGIS Web Adaptor with your portal.
- Federate an ArcGIS Server site with your portal.
- Add Portal for ArcGIS to your organization's reverse proxy server. If you're not using a reverse proxy server, it's recommended you assign a friendly name to the machine hosting ArcGIS Web Adaptor.
Caution:
If you configure a friendly DNS name after setting up your portal, existing items in the portal may become unusable, as they will include the nonfriendly name. You'll need to manually re-create each item in order to use them again.
SSL certificates
Portal for ArcGIS comes preconfigured with a self-signed server certificate, which allows the portal to be initially tested and to help you quickly verify that your installation was successful. You must request a certificate from a trusted certificate authority (CA) and configure the portal to use it. The certificate can be signed by a corporate (internal) or commercial CA.
You should configure each applicable ArcGIS component in your organization with a certificate from a corporate or commercial CA. Common examples include ArcGIS Web Adaptor and ArcGIS Server. For example, ArcGIS Server also comes with a preconfigured self-signed certificate. If you'll be federating an ArcGIS Server site with your portal, it's very important that you request a CA-signed certificate and configure the server and Web Adaptor to use it.
For more information, see Security best practices.
ArcGIS Web Adaptor
ArcGIS Web Adaptor is a required component of Portal for ArcGIS, which allows you to integrate your portal with your existing web server and your organization's security mechanisms. You cannot deploy Portal for ArcGIS in your organization without the Web Adaptor.
You can only use the Web Adaptor with port 80 or 443. Using different ports is not supported. See About ArcGIS Web Adaptor for details.
Supported web browsers
For the best performance in the portal website, use the latest browser versions listed below. Scene Viewer has its own browser and hardware requirements. Some of the common clients of Portal for ArcGIS have different requirements. See their documentation for details.
- Internet Explorer 11. Active scripting must be enabled for the portal website to function correctly.
- Edge
- Firefox
- Chrome
- Safari
- Android Browser
- Chrome for Android
External access
If you'll be using Esri-provided services, such as basemaps and data from ArcGIS Online, the machine hosting Portal for ArcGIS will need access to the Internet. If your portal will not have access to the Internet, you'll need to perform some additional configuration steps to ensure your portal is pointing to local resources. For instructions, see Configuring a disconnected deployment.
ArcGIS Enterprise on cloud platforms
You can deploy ArcGIS Enterprise on many cloud platforms. Any cloud platform that provides virtual machines that meet the basic system requirements for operating system and system specifications is supported for use with ArcGIS Enterprise.
In addition to basic support, Esri provides deployment tooling and prebuilt virtual machine images on two popular cloud platforms: Amazon Web Services and Microsoft Azure. When deploying on these two cloud platforms, it's recommended that you use the specialized tooling and images to simplify deployment and technical support.
Esri does not provide technical support for provisioning and configuring cloud infrastructure beyond what ArcGIS Enterprise deployment tooling creates and manages as part of its normal operations. For cloud platforms where Esri does not provide specialized deployment tooling, support is limited to troubleshooting software-specific issues.
ArcGIS Enterprise also supports different cloud native functionality such as storage and databases on several cloud platforms. Examples include Amazon Simple Storage Service (S3) and Microsoft Azure SQL Database. See the documentation for each ArcGIS component for information on the native cloud functionality that's supported.
Supported virtualization environments
All components of ArcGIS Enterprise are fully supported on virtual environments as long as they run on supported platforms. When running third-party applications with ArcGIS Enterprise, such as relational databases, the application must also be supported in a virtual environment. Check the third-party vendor for its virtualization support.
The following virtualization environments are known to perform well with ArcGIS Enterprise:
- VMware vSphere 5.5, 6.0, and 6.5
- Microsoft Hyper-V
For additional information, see Virtualization and ArcGIS Server.