Hardware requirements

The minimum RAM requirement for ArcGIS Mission Server is 8 GB per machine.

For a production environment, minimum 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

Verify that ports 20443, 20301, and 20160 are available on the ArcGIS Mission Server machine. Ports 20443 and 20301 must be reachable by the ArcGIS Web Adaptor (if used) or external clients. If a firewall is in place between ArcGIS Web Adaptor or external clients, open ports 20443 and 20301 in the firewall. If ArcGIS Mission Server is configured to be highly available, ensure that communication between ArcGIS Mission Server machines is possible via port 20160.

Temporary 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 temporary location by setting the IATEMPDIR environment variable.

Linux operating system requirements

The 64-bit operating systems described below 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. Machines with an underscore in the name are not supported. The setup will not proceed if an underscore is detected in the machine name.

The operating system of your ArcGIS Mission Server machines can be different from those of the other machines in your ArcGIS Enterprise deployment. The most common scenario for this is to deploy ArcGIS Mission Server on Linux machines while the rest of the ArcGIS Enterprise deployment is on Microsoft Windows machines.

You cannot install the software as a root user. If you attempt to do so, the installation will not proceed, and a software diagnostics tool will display an error message indicating that you cannot install as root.

The software should not be installed on an OS (binary) that has been modified. Esri does not provide support for products installed on a developer's release of an operating system.

Prior and future updates or service packs on 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 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'll need to 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'll 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, use the ulimit -Hn -Hu and ulimit -Sn -Su commands as described above.

Cloud implementation

ArcGIS Mission Server cloud implementation is currently supported by Amazon Web Services (AWS). For more information, see Enhanced Support for ArcGIS Server roles.

SSL certificates

ArcGIS Mission 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 Mission 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 Mission Server will not work properly.

Portal for ArcGIS also includes a preconfigured self-signed certificate. Because you'll federate an ArcGIS Mission Server site with your portal, request a certificate from a trusted CA and configure the portal to use it.

Software prerequisites

ArcGIS Mission Server can be installed on its own or can be installed with other ArcGIS Enterprise 10.9.1 components.

As part of the base deployment, an ArcGIS Data Store is required. The spatiotemporal big data store is the default data store when creating a mission with ArcGIS Mission. A message appears when creating a mission if the spatiotemporal big data store is not detected, configured, or available. A relational data store will instead be used by default. Because missions can contain large quantities of data and span an extended period of time, it is highly recommended that you use a spatiotemporal big data store. The spatiotemporal big data store allows you to store data more efficiently due to its archive of high-volume data and the support for high-velocity write throughput.

During ArcGIS Mission Server set up, you will federate your new ArcGIS Mission Server site with your Enterprise portal 10.9.1.

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 Mission Server site. The ArcGIS Enterprise portal will request the FQDN of your server site when you federate it.

Supported web browsers

The ArcGIS Mission Server installation wizard is supported by all web browsers including but not limited to the following:

• Google Chrome
• Microsoft Edge
• Mozilla Firefox
• Safari