The system and hardware requirements for ArcGIS Data Pipelines Server are listed below.
To learn more about installing ArcGIS Data Pipelines Server, see Install ArcGIS Data Pipelines Server using the installation guide.
To learn more about the capabilities of ArcGIS Data Pipelines, see Introduction to ArcGIS Data Pipelines.
Note:
At ArcGIS Enterprise 12.0, ArcGIS Data Pipelines is a beta feature. While in beta, this capability may not be feature complete and, as such, may have known performance or quality issues and will not be supported by Esri Technical Support. Feedback on this feature can be provided in the ArcGIS Enterprise 12.0 Beta Features Early Adopter Community.Hardware requirements
The minimum RAM requirement for ArcGIS Data Pipelines Server is 16 GB per machine.
For a production environment, hardware requirements are not listed 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.
Port availability
ArcGIS Data Pipelines Server communicates with ArcGIS Enterprise on port HTTPS 14443. Verify that HTTPS port 14443 is available on the ArcGIS Data Pipelines Server machine and is opened to your firewall before installing the software.
Additionally, ArcGIS Data Pipelines Server communicates internally on random ephemeral ports that are chosen by the OS. These ports are internal only and do not require firewall settings. They are required to connect to the ArcGIS Data Pipelines editor and run data pipelines.
To communicate with the ArcGIS Enterprise with which it's federated, ArcGIS Data Pipelines Server needs access to ArcGIS Server and Portal for ArcGIS on HTTPS ports 6443 and 7443 respectively.
Note:
This component is only one part of an ArcGIS Enterprise deployment. See ArcGIS Enterprise system requirements for a diagram and links to information about the ports needed to communicate with other components in ArcGIS Enterprise.Temp space requirements
By default, resources are extracted to the system /tmp directory. This directory must have read, write, and run 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.
Linux operating system requirements
Several internet host name specifications have designated the underscore character as nonstandard. Host names with underscores can cause problems when you interact with other servers and platforms. For this reason, ArcGIS Data Pipelines Server will not install on servers that have an underscore in the host name.
The operating system of your ArcGIS Data Pipelines Server machines can be different from those of the other machines in your ArcGIS Enterprise deployment.
The following 64-bit operating systems satisfy the minimum operating system requirements.
ArcGIS Data Pipelines Server is only supported on Linux x86_64, on CPUs that adhere to the x86_64 architecture (64 bit), with supported Linux releases.
You cannot install the software as a root user. If you attempt to do this, the installation will not proceed and a software diagnostics tool will display an error message indicating that you cannot install as root.
The following 64-bit operating systems satisfy the minimum operating system requirements.
| Supported operating system | Latest update or service pack tested |
|---|---|
Red Hat Enterprise Linux Server 9 | Update 6 |
AlmaLinux 9 | Update 6 |
SUSE Linux Enterprise Server 15 | Service Pack 7 |
Ubuntu Server 24.04 LTS | 24.04.2 |
Ubuntu Server 22.04 LTS | 22.04.5 |
Oracle Linux 9 | Update 6 |
Rocky Linux 9 | Update 6 |
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.
File handles and processes limits
ArcGIS Data Pipelines 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 Data Pipelines Server installation user> soft nofile <file limit>
<ArcGIS Data Pipelines Server installation user> hard nofile <file limit>
<ArcGIS Data Pipelines Server installation user> soft nproc <process limit>
<ArcGIS Data Pipelines 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 Data Pipelines Server service, verify that DefaultLimitNOFILE and DefaultLimitNPROC limits in the /etc/systemd/system.conf file are set to 65536 and 25059, respectively.
Cloud implementation
ArcGIS Data Pipelines Server cloud implementation is currently supported on Amazon Web Services (AWS) and Microsoft Azure.
SSL certificates
ArcGIS Data Pipelines Server is preconfigured with a self-signed certificate that allows the server 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 ArcGIS Data Pipelines Server to use it. This can be a domain certificate issued by your organization or a CA-signed certificate. The certificate must have a Subject Alternative Name (SAN) configured or ArcGIS Data Pipelines Server will not work properly.
Portal for ArcGIS also includes a preconfigured self-signed certificate. Because you'll federate an ArcGIS Data Pipelines Server site with your portal, request a certificate from a trusted CA and configure the portal to use it.
Software prerequisites
ArcGIS Data Pipelines Server requires an ArcGIS Enterprise base deployment licensed with ArcGIS Enterprise. The ArcGIS Data Pipelines Server site must be federated with ArcGIS Enterprise to function; you cannot have a stand-alone ArcGIS Data Pipelines Server site.
The ArcGIS Data Pipelines Server site is required to be installed on a separate machine from other ArcGIS Enterprise components. All software components must use the same software version whether you're installing for the first time or upgrading from an earlier version.
As per the requirements of the base deployment, the ArcGIS Data Store configured as a relational store is required. ArcGIS Data Pipelines creates and updates hosted feature layers that are stored in the relational store.
Domain name system and fully qualified domain name recommendations
It's recommended that you configure your organization's Domain Name System (DNS) to include Fully Qualified Domain Name (FQDN) entries for the ArcGIS Data Pipelines Server site. The ArcGIS Enterprise portal will request the FQDN of your server site when you federate it.
Supported web browsers
The ArcGIS Data Pipelines Server installation wizard is supported by all web browsers including but not limited to the following:
- Google Chrome version 138 and later
- Microsoft Edge version 138 and later
- Mozilla Firefox version 142 and later
- Mozilla Firefox version 140 (ESR)
- Safari version 18 and later