The system and hardware requirements for ArcGIS Mission Server are listed below.
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.
Verify that ports 20443, 20300, 20301, 20302, 20158, 20159, and 20160 are available on the ArcGIS Mission Server machine. Ports 20443, 20301, and 20300 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, 20301, and 20300 in the firewall. If ArcGIS Mission Server is configured to be highly available, ensure that communication between ArcGIS Mission Server machines is possible via ports 20158, 20159, and 20160.
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 an Enterprise portal.
Windows operating system requirements
Several internet host name specifications have designated the underscore character as nonstandard. Although Microsoft Windows allows the underscore in a machine name, it can still cause problems when you interact with other servers and platforms. For this reason, ArcGIS Mission Server will not install on servers that have an underscore in the host name.
The operating system of your ArcGIS Mission Server machines can be different from those of the other machines in your ArcGIS Enterprise deployment.
ArcGIS Mission Server is not supported on domain controllers. Installing ArcGIS Mission Server on a domain controller may adversely affect functionality.
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.
|Supported operating system||Latest update or service pack tested|
Windows Server 2019 Standard and Datacenter
Feb 2021 Update
Windows Server 2016 Standard and Datacenter
Feb 2021 Update
Windows Server 2012 R2 Standard and Datacenter
Feb 2021 Update
Windows Server 2012 Standard and Datacenter
Feb 2021 Update
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.
The Desktop Experience option is required on all versions of Windows Server.
ArcGIS Mission Server cloud implementation is currently supported by Amazon Web Services (AWS). For more information, see Enhanced Support for ArcGIS Server roles.
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.
Certificates created using IIS do not have the option to include a SAN. Use the script in Create a domain certificate, which includes a SAN, with the certificate created.
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.
ArcGIS Mission Server can be installed on its own or can be installed with other ArcGIS Enterprise 10.9 components.
Whether you are installing a new deployment or upgrading from an earlier version, ensure that all your software components—the ArcGIS Enterprise portal, an ArcGIS Server site, and ArcGIS Data Store—are installed and running ArcGIS Enterprise 10.9.
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.
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