Skip to main content

ArcGIS Enterprise 12.1 system requirements

ArcGIS Enterprise provides a system for mapping, visualization, data management, and analytics, as well as a flexible deployment model allowing for use on-premises, in the cloud, and on virtual machines.

A base ArcGIS Enterprise deployment includes several components that are designed to work together. In addition to these components, you can add one or more servers to your deployment to meet specific workflow requirements in your organization.

It is recommended to use the same software version across all components in your deployment.

This page lists support information that is common to most parts of an ArcGIS Enterprise deployment and provides subsections for each component of a base deployment to help you understand additional requirements as relevant. This information is important for the physical design considerations for your deployment.

Before you install or upgrade ArcGIS Enterprise, review What's new in ArcGIS Enterprise including the retirement and deprecation notices to determine whether your hardware and software components are still compatible with the current release.

Note:

ArcGIS License Manager is no longer required to enable named user licensing for ArcGIS Pro, ArcGIS Pro extensions, ArcGIS Drone2Map, and ArcGIS AllSource.

A diagnostics tool runs during the setup to help you determine if your machine meets the minimum system requirements.

Operating system requirements

The following Linux operating systems are supported for ArcGIS Enterprise deployments. At present, the exception to this is ArcGIS Video Server.

Supported operating system

Latest update or service pack tested

Red Hat Enterprise Linux Server 8

Update 10

Red Hat Enterprise Linux Server 9

Update 7

AlmaLinux 8

Update 10

AlmaLinux 9

Update 7

SUSE Linux Enterprise Server 15

Service Pack 7

Ubuntu Server 24.04 LTS

24.04.4

Ubuntu Server 22.04 LTS

22.04.5

Oracle Linux 8

Update 10

Oracle Linux 9

Update 7

Rocky Linux 8

Update 10

Rocky Linux 9

Update 7

  • Prior and future updates or service packs for these operating system versions are supported unless otherwise stated. The operating system version and updates must also be supported by the operating system provider.

  • Do not install the software on an operating system (binary) that has been modified. Esri does not provide support for products installed on a developer's release of an operating system.

  • Machines with an underscore (_) in the name are not supported. The setup does 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.

Temp space requirements

By default, ArcGIS Enterprise uses the /tmp directory for temporary storage. If this directory does not have enough space, set the following environment variables to specify alternate locations:

  • IATEMPDIR—The directory where installation resources are extracted during setup.

  • TMPDIR—The directory that stores temporary files created when publishing from a service definition (SD) file and automatic backup files created during an upgrade.

Temporary storage directories must have read, write, and execute permissions enabled.

Package groups

The X Window System package group is required on the installation machines to run the following using the operating system graphical user interface (GUI):

  • Installation wizards

  • ArcGIS Authorization Wizard

  • Check for Updates tool

The following package groups are required.

Operating system

Package group

Red Hat Enterprise Linux Server and Oracle Linux

gettext

SUSE Linux Enterprise Server

gettext-runtime

Ubuntu Server LTS

gettext-base

The following 64-bit Windows operating systems are supported for most ArcGIS Enterprise components and sites. At present, the exceptions to this are ArcGIS Notebook Server and ArcGIS Video Server.

Production environments:

Supported operating system

Latest update or service pack tested

Windows Server 2025 Standard and Datacenter

April 2026 update

Windows Server 2022 Standard and Datacenter

April 2026 update

Windows Server 2019 Standard and Datacenter

April 2026 update

Basic testing and application development environments:

Supported operating system

Latest update or service pack tested

Windows 11 Pro and Enterprise

April 2026 update

  • Prior and future updates or service packs for these operating system versions are supported unless otherwise stated. The operating system version and updates must also be supported by the operating system provider.

  • The Desktop Experience option is required on all versions of Windows Server.

  • ArcGIS software is developed and certified to support file system path names with a maximum path length of 260 characters.

  • Microsoft recommends that you do not disable the IPv6 protocol on any of the currently supported operating system versions, as it is a required component of the operating system. If you do disable the IPV6 protocol on any machine where ArcGIS Enterprise components are installed, follow the instructions provided by Microsoft.

  • You cannot install on domain controllers. Installing on a domain controller may adversely affect functionality.

  • Windows 11 is supported for basic testing and application development use only.

  • Machines with an underscore (_) in their names are not supported. Several widely used internet host name specifications have designated the underscore character as nonstandard. Although Microsoft Windows allows you to use the underscore in a machine name, it can cause problems when you interact with other servers and platforms. For this reason, the installation will not proceed on servers that have an underscore in the host name.

ArcGIS Enterprise components require the Microsoft Visual C++ 2015–2022 Redistributable (x64) minimum version 14.44.35211. Obtain the Microsoft Visual C++ Redistributable for Visual Studio 2015–2022 file from the Microsoft site.

If the required Visual C++ 2015 - 2022 Redistributable is not installed, running the ArcGIS Enterprise setups (setup.exe) will install it for you. However, running the setup.msi directly will not install the redistributable. If the Microsoft Visual C++ 2015 - 2022 Redistributable (x64) is not already installed, running the setup.msi will fail to run ArcGIS Enterprise setups.

ArcGIS Server

ArcGIS Server is typically used as a federated or hosting server. It can also be used as a stand-alone server. It powers mapping and analysis in your GIS and scales dynamically to support traffic. See servers and extensions for all ArcGIS Server-based servers and extensions that follow this set of requirements.

Hardware requirements

  • ArcGIS Server requires a minimum of 10 GB of available disk space.

  • The minimum available memory (RAM) required to install any ArcGIS Server-based component is 8 GB per machine.

Hardware requirements are not listed for production environments because the user and business needs of the software may vary. These requirements must be considered in determining hardware needs to meet performance and scalability expectations.

  • Approximately 1.5 GB of the required disk space is used during the installation of this product. This temporary disk use is removed at the end of the installation.

  • You cannot install ArcGIS Server on a shared network directory (NFS mounted folder). The directory must be local on the target system.

.NET Extension Support

The .NET Extension Support feature, supporting .NET-based server object extensions (SOEs) and server object interceptors (SOIs), requires .NET 10. If .NET 10 is not found, the .NET Extension Support feature will not be available for installation.

If you use .NET-based SOEs or SOIs, you must install either .NET Desktop Runtime 10 (x64) or .NET SDK 10 (x64) prior to installing ArcGIS Server.

Page file size requirements

Ensure that a sufficient page file size is configured for the ArcGIS Server machine. You should consult with your IT administrator or follow best practices from Microsoft.

Geoprocessing requirements

If you use the ArcGIS Pro-based geoprocessing tools that are installed with ArcGIS Server, see ArcGIS Server and ArcPy for where to find the Python 3 files.

Default file permissions

For security reasons, all permission types (read, write, and run) for group and all users are turned off by default.

File handles and processes limits

ArcGIS Server is a data-intensive server product, and many of its data formats consist of hundreds of thousands of files. In heavily used systems, thousands or tens of thousands of files may be in use at any given time. If there are insufficient file handles and processes, requests may start failing randomly, leading to system downtime. The actual number of file handles and processes needed varies based on the data and the number of instances (threads/processes) running. Setting a file handle limit of 65,535 and a process limit of 25,059 will allow you to ensure that the system remains running.

There are soft and hard limits for file handles and processes on Linux. To determine the hard limits, use the ulimit -Hn -Hu (or limit -h descriptors if you're using csh) command. To determine the soft limits, use the ulimit -Sn -Su (or limit descriptors if you're using csh) command.

To increase the soft and hard limits, you must edit the /etc/security/limits.conf file with superuser access. For example, you can add four lines in the file as follows and change the values for the limits:

<ArcGIS Server installation user> soft nofile <file limit>
<ArcGIS Server installation user> hard nofile <file limit>
<ArcGIS Server installation user> soft nproc <process limit>
<ArcGIS Server installation user> hard nproc <process limit>

After making this change, you must sign out and sign back in with the particular user for the new values to take effect. To verify that the limits have been modified appropriately, use the ulimit -Hn -Hu and ulimit -Sn -Su commands as described above.

If you use SystemD to bootstrap starting and stopping the ArcGIS Server service, verify that DefaultLimitNOFILE and DefaultLimitNPROC limits in the /etc/systemd/system.conf file are set to 65536 and 25059, respectively.

SELinux support

The Security-Enhanced Linux (SELinux) module is supported on machines running ArcGIS Server. Because the default policy of SELinux may prevent ArcGIS Server from reaching internal components such as the configuration store, administrators may need to modify the SELinux policy. To do so, temporarily set the SELinux policy mode to permissive. This will record the violations of policy, such as actions taken by ArcGIS Server to access internal directories, but will allow them to occur. Administrators can note these violations by ArcGIS Server and modify the SELinux policy configuration to allow them before resetting the policy mode to enforced.

Portal for ArcGIS

Portal for ArcGIS has a central role in organizing and sharing information in your organization. It is the central hub of ArcGIS Enterprise where members access their organization to create maps, apps, and spatial data and share them with collaborators.

Hardware requirements

The following are the minimum hardware requirements to install Portal for ArcGIS:

  • Processor—2 cores minimum for development and testing, 4 cores minimum highly recommended for production systems

  • Memory/RAM—8 GB

  • Disk space—30 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. Optionally, you can change the location of where the portal stores its content after installing the software.

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 the following command to confirm: btrfs filesystem df /

File handle limits

For the portal to run properly, the file handle limits for the installation user are required to be set to a minimum of 65,535. An installation diagnostics tool will check 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, edit the /etc/security/limits.conf file with superuser access. For example, add two lines in the file as follows:

<Portal for ArcGIS installation user> soft nofile <file handle limit>
<Portal for ArcGIS installation user> hard nofile <file handle limit>

After making this change, sign out and sign back in with the user for the new values to take effect. To verify that the limits have been modified appropriately, use the ulimit -Sn and ulimit -Hn commands as described above.

If you use SystemD to bootstrap starting and stopping the Portal for ArcGIS service, verify that DefaultLimitNOFILE and DefaultLimitNPROC limits in the /etc/systemd/system.conf file are set to 65536 and 25059 respectively.

ArcGIS Data Store

Each type of ArcGIS Data Store requires different amounts of memory, disk space, and other resources, and each type can use either relatively little or significant amounts of resources depending on the number of users and workloads that it supports in the system. It is imperative to ensure that the machines have sufficient resources for all software, data, and network traffic that they are expected to consume; otherwise, resource issues could result in inoperable data stores.

The relational store uses the locale of the operating system of the machine where you install. Only locales that use ASCII characters are supported for the relational store.

Disk space requirements

  • ArcGIS Data Store requires a minimum of 13 GB of available disk space on the system drive.

This is the minimum disk space requirement for a machine with one empty data store type; it does not take into account all the data you will store in the data store or backup files that might be stored on the machine. Given this requirement, plan to install ArcGIS Data Store on machines with large quantities of available disk space.

To determine the amount of disk space needed on a dedicated ArcGIS Data Store machine, take all of the following into consideration:

  • The software installation uses 4.8 GB of disk space.
  • The software installation uses 5.2 GB of disk space.

  • Each data store uses an additional amount of space when created and still empty:

    • Spatiotemporal big data store = 200 MB

    • Graph store = 100 MB

    • Object store = 500 MB

    • Relational store = 2.5 GB*

    *An empty relational store uses up to 2.5 GB of disk space over time, to support high availability and a reliable backup policy. Upon configuration of the relational store, approximately 200 MB of disk space is used. The amount of disk space used by the empty relational store will grow by about 200 MB per hour over the course of 11 hours until settling at 2.5 GB at that time. Data stored in the system during use is in addition to this baseline storage requirement.

  • A minimum of 20 percent of the disk space on each machine must be available for temporary files when configuring or upgrading a spatiotemporal big data store.

  • You must estimate the amount of disk space needed for the data stored in the data stores. The numbers above are the minimum for empty data stores. That amount of free disk space allows you to create the data store. Additional space is needed to use it.

  • Backup files stored on the data store machine also consume disk space. If you do not configure backups to be written to a shared location or cloud storage, you must plan for this additional use of disk space.

Monitor ArcGIS Data Store logs so you are aware when a machine begins to run out of disk space. When a relational store, spatiotemporal big data store, object store, or graph store machine contains less than 10 GB of free disk space, ArcGIS Data Store begins logging warnings that you are running out of disk space. If you configure email notifications for the portal, the administrative contacts in that list will receive an email when the machines get close to running out of disk space. Once the disk drive contains less than 5 GB of free space, the relational, object, and spatiotemporal big data stores are placed in read-only mode, and the graph store shuts down. At this point, administrative contacts will receive another email indicating the data store is in read-only mode or shut down.

Memory requirements

The minimum memory required to configure a single, empty ArcGIS Data Store on a machine varies by type. Meeting the minimum free memory requirements ensures the data store will start. Once in use, additional memory is required.

The following minimum memory requirements assume you install each type of ArcGIS Data Store on its own machine; no other data store type or ArcGIS Enterprise component is installed on the machine. Amounts listed reflect the amount of free memory that must be available on the machine before installing ArcGIS Data Store and configuring a data store.

  • Relational store = 8 GB

  • Object store = 16 GB

    Note:

    For better performance, the object store requires a minimum of 32 GB of free memory.

  • Spatiotemporal big data store = 16 GB

  • Graph store = 32 GB

File handle and process limits

ArcGIS Data Store is a data-intensive product, and many of its data formats consist of hundreds of thousands of files. In heavily used systems, thousands or tens of thousands of files may be in use at any given time. If there are insufficient file handles and processes, the data store cannot start. Even if there are sufficient processes and file handles to start, requests may start failing randomly once data is loaded and people start accessing services, leading to system downtime. The actual number of file handles and processes needed varies based on the data and the number of instances (threads or processes) running.

There are soft and hard limits for file handles, file sizes, and processes on Linux. To determine the hard limits, use the ulimit -Hn -Hu (or limit -h descriptors if you're using csh) command. To determine the soft limits, use the ulimit -Sn -Su (or limit descriptors if you're using csh) command.

The minimum file handle limit is 65,535 for the relational store and 65,536 for the spatiotemporal big data store. The minimum process limit for relational and spatiotemporal big data store types is 25,059. These minimum settings only ensure ArcGIS Data Store can start. It is recommended that you set higher limits to help ensure that the system remains running.

For graph stores, set the file handle and process limits to unlimited.

Standard Linux file handle limits are sufficient for the object store.

To increase the soft and hard limits, edit the /etc/security/limits.conf file with superuser access. Which lines and settings you add to the file vary depending on the type of data store you configure.

See the next section for /etc/security/limits.conf file settings for spatiotemporal big data store machines.

The following example is for a relational store machine. Replace limits with numbers appropriate to your uses.

<ArcGIS Data Store installation user> soft nofile <file limit>
<ArcGIS Data Store installation user> hard nofile <file limit>
<ArcGIS Data Store installation user> soft nproc <process limit>
<ArcGIS Data Store installation user> hard nproc <process limit>

<ArcGIS Data Store installation user> is the name of the login you use to install ArcGIS Data Store.

Log back in with the user you specified for <ArcGIS Data Store installation user> for the file handle and process limit values to take effect. To verify that the limits have been modified appropriately, use the ulimit -Hn -Hu and ulimit -Sn -Su commands as described above.

If you use SystemD to bootstrap starting and stopping the ArcGIS Data Store service, verify that DefaultLimitNOFILE and DefaultLimitNPROC limits in the /etc/systemd/system.conf file are set to 65536 and 25059, respectively

After changing process and file handle limits, you must restart ArcGIS Data Store.

Environment settings for spatiotemporal big data stores

Spatiotemporal big data stores store and access large amounts of feature data. To accommodate this, additional environment settings are required for these types of data stores.

As mentioned in the previous section, the minimum file handle and process settings for spatiotemporal big data stores are 65,536 and 25,059, respectively. In addition, you must set file size and virtual memory to unlimited.

Set all of these limits in the /etc/security/limits.conf file. The following is an example of file limit, file size, process, and virtual memory settings in the /etc/security/limits.conf file on spatiotemporal big data store machines:

<ArcGIS Data Store installation user> soft nofile <file limit>
<ArcGIS Data Store installation user> hard nofile <file limit>
<ArcGIS Data Store installation user> soft fsize unlimited
<ArcGIS Data Store installation user> hard fsize unlimited
<ArcGIS Data Store installation user> soft nproc <process limit>
<ArcGIS Data Store installation user> hard nproc <process limit>
<ArcGIS Data Store installation user> soft as unlimited
<ArcGIS Data Store installation user> hard as unlimited

<ArcGIS Data Store installation user> is the name of the login you use to install ArcGIS Data Store.

Log back in with the user you specified for <ArcGIS Data Store installation user> for the file handle and process limit values to take effect. To verify that the limits have been modified appropriately, use the ulimit -Hn -Hu and ulimit -Sn -Su commands as described above.

Next, change the following system virtual memory settings:

  • vm.max_map_count must be set to at least 262144. If you do not set this, you may receive out-of-memory exceptions.

  • vm.swappiness must be set to 1; otherwise, it will negatively affect the performance of the spatiotemporal big data store.

Virtual memory settings apply to the whole system rather than the ArcGIS Data Store installation user. To configure your virtual memory settings, you must update the /etc/sysctl.conf file with the following virtual memory values. Replace the map count with a number appropriate for your use.

vm.max_map_count = <map count>
vm.swappiness = 1

After changing process, file, and virtual memory limits, you must restart ArcGIS Data Store.

Minimum CPU architecture requirements for graph stores

The processors in the machines where you install the graph store must use the Advanced Vector Extension 2 (AVX2) instruction set architecture.

ArcGIS Web Adaptor

ArcGIS Web Adaptor is an optional component of ArcGIS Enterprise that allows you to integrate components with your existing web server and organization's security mechanisms. ArcGIS Web Adaptor is required when configuring web-tier authentication, such as Integrated Windows Authentication (IWA), basic authentication with Lightweight Directory Access Protocol (LDAP), or client certificate authentication. ArcGIS Web Adaptor can also be integrated within a network path that includes other reverse proxy or load balancer appliances.

For more information about ArcGIS Web Adaptor, how it affects the ArcGIS Enterprise organization URL, and the use of third-party solutions, see the following topics:

ArcGIS Web Adaptor (Java Platform)

ArcGIS Web Adaptor (Java Platform) can be installed on a Windows or Linux machine and integrated with Apache Tomcat 10.1.x.

ArcGIS Web Adaptor (Java Platform) can support Java 11 or later based on the Java compliance level for Apache Tomcat 10.1.x where the web adaptor is deployed.

  • When running a localized setup of ArcGIS Web Adaptor on Linux, follow your operating system instructions to ensure you have the corresponding language fonts installed.

ArcGIS Web Adaptor (IIS)

ArcGIS Web Adaptor (IIS) can be installed on a Microsoft Windows machine and integrated with an Internet Information Server (IIS) web server. You will need to enable IIS components before you install ArcGIS Web Adaptor.

The following prerequisites must be installed on the machine where ArcGIS Web Adaptor (IIS) will be installed:

You must install the ASP.NET Core Runtime - Windows Hosting Bundle, which includes the .NET Runtime and IIS support.

If you installed the ASP.NET Core Runtime - Windows Hosting Bundle before enabling IIS and the required components, you must repair the bundle installation using the bundle installer.

Supported web servers

The IIS web server versions available on supported Windows operating systems are supported for use with ArcGIS Web Adaptor (IIS).

  • Updates on these operating systems and web servers are supported unless otherwise stated. The operating system version and updates must also be supported by the application or web server provider.

Hardware requirements

  • ArcGIS Web Adaptor (IIS) requires a minimum of 8 GB of memory, with more potentially required depending on the number of ArcGIS Web Adaptor instances installed and the number and size of the requests received.

  • For hardware considerations when upgrading ArcGIS Web Adaptor, see Upgrade ArcGIS Web Adaptor.

Maximum installation instances

  • The maximum number of instances of ArcGIS Web Adaptor (IIS) you can install on a single machine depends on how you install the first ArcGIS Web Adaptor instance. If you install the first instance using the ArcGIS Web Adaptor setup program, you can install a maximum of 51 instances of the same version of ArcGIS Web Adaptor on a single machine. However, if you install the first instance using ArcGIS Enterprise Builder, you can install a maximum of 50 instances of the same version or ArcGIS Web Adaptor on a single machine. If more instances are required, install them on a separate machine.

  • If you have earlier versions installed on the machine, you are not required to uninstall them. For example, you can have 5 instances of ArcGIS Web Adaptor at an earlier release and 51 instances of ArcGIS Web Adaptor 12.1 installed on the same machine. The maximum value only applies to instances of the same software version.

ArcGIS Enterprise Builder

ArcGIS Enterprise Builder deploys a base ArcGIS Enterprise deployment on a single machine in on-premises environments. The requirements to run ArcGIS Enterprise Builder are listed below.

Prerequisite

You must follow prerequisites to install ArcGIS Web Adaptor. before installing ArcGIS Enterprise Builder.

Disk space requirements

ArcGIS Enterprise Builder (Linux) requires a minimum of 52 GB of free disk space. The location you provide as your installation drive during setup must have a minimum of 50 GB of free disk space for installation to proceed, and you need an additional 2 GB of space on the system's /tmp directory to allow for extraction of the setup.

  • To accommodate data added after installation, a production system should have 80 GB or more of free disk space on each machine in the deployment. Also refer to the documentation for the application server that you use for integration with ArcGIS Web Adaptor (Java Platform) to determine the recommended disk space for the application server.

  • ArcGIS Enterprise Builder (Windows) requires 20 GB of free disk space on the system drive (often the C: drive), where setup files are staged and log files are written.

  • Additionally, the builder requires a minimum of 50 GB of free disk space on the installation drive, which you will specify during setup. This disk space is necessary for completing the initial installation of components and for the storage of data, logs, and configuration files as your base deployment expands.

  • Most users need more than 50 GB of space on their installation drive. A production system should have 90 GB or more of free disk space on each machine in the deployment.

Memory requirements

  • A minimum of 52 GB of free disk space is required for installation. The location you provide as your installation drive during setup must have a minimum of 50 GB of free disk space for installation to proceed, and you need an additional 2 GB of space on the system's /tmp directory to allow for extraction of the setup.

  • To accommodate data added after installation, a production system should have 80 GB or more of free disk space on each machine in the deployment. Also refer to the documentation for the application server that you use for integration with ArcGIS Web Adaptor (Java Platform) to determine the recommended disk space for the application server.

  • A minimum of at least 32 GB of available RAM is recommended for installation.

  • If you will publish hosted scene layers and hosted 3D tiles layers, a minimum of 48 GB of available RAM is recommended. You must run the changedbproperties utility to increase the heap size for the object store to at least 16000 MB.

Firewall settings

Each component in an ArcGIS Enterprise deployment communicates over a specific set of ports and requires certain ports to be available on each machine. See Required ports for links to information.

Trusted certificates

ArcGIS Enterprise deployments require HTTPS to be enabled on the machine where the base deployment is installed. For details, review steps to enable HTTPS on your web server.

If your deployment's web server is IIS, learn how to use a sample script to create a domain certificate.

Portal for ArcGIS and ArcGIS Server components are configured with a self-signed certificate, which allows you to do initial testing and helps you quickly verify that your installation was successful. It is recommended that you obtain a certificate from a trusted certificate authority (CA) and configure these components to use it. The certificate can be signed by a corporate (internal) or commercial CA.

For any of the components of the ArcGIS deployment that interact with clients over the network—such as ArcGIS Web Adaptor, a load balancer, or a reverse proxy server—it is important to configure them to use a certificate from a trusted corporate or commercial CA. If you plan to federate a server site, the external URL for the server site must use a CA-signed certificate.

For more information, see Security best practices.

Supported web browsers

Most ArcGIS Enterprise components include interfaces that you access through a web browser. The following browsers are supported for most components:

  • Google Chrome version 142 and later

  • Microsoft Edge version 142 and later

  • Mozilla Firefox version 146 and later

  • Mozilla Firefox version 140 (ESR)

  • Safari version 18 and later

Scene Viewer and scene-based apps have their own browser requirements. Some of the ArcGIS apps also have their own requirements. See each app's documentation for details.

For best performance and full functionality, use the latest version of a browser listed above. Only WebGL2-enabled, 64-bit browsers are supported. The website uses the local storage capabilities (similar to cookies) of the browser. If this storage is disabled, the site will not function properly. To learn how to enable local storage, consult the browser's documentation.

DNS and FQDN requirements

Your organization's domain name service (DNS) must include an entry of the fully qualified domain name (FQDN) of the machine hosting Portal for ArcGIS. Similarly, if you’re federating server sites with ArcGIS Enterprise, it's recommended that you include FQDN entries for each server site you intend to federate.

Note:

Portal for ArcGIS only supports a single organization URL.

Optionally, you can configure your DNS to use a friendly name for the portal (for example, friendly.example.com instead of portal.example.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 organization. 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 that 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 to use them again.

Supported databases and data warehouses

See the requirements for Supported databases and data warehouses that can be registered with ArcGIS Server sites.

Most databases require you to install and configure an ODBC client on the ArcGIS Server machines to connect. For that reason, you must consider the operating systems supported for the ODBC drivers when deciding which operating system to use for your ArcGIS Server machines; the operating system must be supported for both ArcGIS Server and the ODBC driver.

See Requirements for using ArcGIS with databases in the cloud for information about support for database services and databases deployed in the cloud.

Memory requirements

  • It is recommended that you have at least 32 GB of available RAM to install ArcGIS Enterprise Builder.

  • If you will publish hosted scene layers and hosted 3D tiles layers, a minimum of 48 GB of available RAM is recommended. You must run the changedbproperties utility to increase the heap size for the object store to at least 16000 MB.

Also refer to the documentation for the application server that you use for integration with ArcGIS Web Adaptor (Java Platform) to determine the recommended memory requirements for the application server.

External access

If you'll be using services provided by Esri, such as basemaps, ArcGIS Living Atlas of the World content, and data from ArcGIS Online, or participating in distributed collaboration with an ArcGIS Online organization, the machine hosting Portal for ArcGIS must have access to the internet. If your deployment will not have access to the internet, you'll need to perform some additional configuration steps to ensure that your environment is pointing to local resources. For instructions, see Configure a disconnected deployment.

Cloud support

See Requirements for using ArcGIS with databases in the cloud for information about support for database services and databases deployed in the cloud.

Additional system requirements

Each ArcGIS Enterprise component, server, app, and tool has specific requirements unique to it. When planning your system architecture, read the system requirements pages for all relevant areas you plan to deploy and use.