Deploy a base ArcGIS Enterprise deployment on a single machine

In this workflow, the arcgis-enterprise Chef cookbooks will:

1. Install ArcGIS Server, authorize it, create a site and enable HTTPS in Server Admin.
2. Install IIS on Windows or Tomcat and Java on Linux if not installed.
3. Import the CA-certificate if it's defined, or generate a self-signed certificate for the web server.
4. Install and configure WA for ArcGIS Server.
5. Install Portal for ArcGIS and authorize it. Create Initial Administrative Account.
6. Install and configure WA for Portal for ArcGIS.
7. Install ArcGIS Data Store and register it with ArcGIS Server.
8. Federate ArcGIS Server with Portal. Set it as the hosting Server.

Prerequisites:

Before setting up the deployment, you'll need to have obtained:

• Setups for Esri software
• Esri authorization files. Make sure to use the correct authorization file for different products.
• A domain name for your web site
• SSL certificate issued by certification authority for the domain (Note: If you don't define a CA-cert, this tool will generate and use a self-signed certificate for testing purposes. Self-signed certificates are not supported by Portal for ArcGIS.)

If you are running Linux, your machine needs to allow running sudo to execute commands without a password.

On some Linux distributions, sudo is configured to require a tty as a default configuration. This is usually set in /etc/sudoers with the entry of "Defaults requiretty".

You can either change the entry to "Defaults !requiretty" in the /etc/sudoers file or change this configuration for certain users, groups or commands.

RedHat will remove this default setting, as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1020147.

On Windows

1. Install Windows Chef Client. ArcGIS Chef cookbooks support Chef-Client versions 13 and 14.
2. Download the arcgis cookbook to your machine.
3. Extract the content of the cookbook zip file to C:\chef. The final folder structure should be c:\chef\cookbooks\arcgis; c:\chef\cookbooks\windows; etc.
4. Edit c:\chef\roles\arcgis-enterprise-windows.json file.
   • If an attribute value is not specified in the *.json file, chef uses the default value for the attribute.
   • If SSL certificate for IIS is not specified by node['arcgis']['iis']['keystore_file'] attribute, chef generates and uses a self-signed certificate.
   • If node['arcgis']['server']['domain_name'] or node['arcgis']['portal']['domain_name'] attributes are not specified, the FQDN of the machine is used.
   • If the repository variable is defined, you do not need to also specify the path to your setup file.
   • If you are specifying the path to your setup file, examine your file. Setup files named "Setup.exe" should be defined in the JSON using the setup variable; setup files named in a format such as "ArcGIS_Server_1061_163983.exe" are self-extracting and should be defined using the setup_archive variable.
5. Start a command prompt window as administrator and run "chef-solo -j C:\chef\roles\arcgis-enterprise-windows.json"
6. After the chef-solo run is completed, Portal for ArcGIS and ArcGIS Server will be available at https://hostname/portal and https://hostname/server URLs respectively.

Note: To complete the installation of IIS on Windows 8 and Windows Server 2012, the machine needs to be rebooted after the first chef run, and chef needs to be run again after the reboot.

On Red Hat Enterprise Linux

1. Install Linux Chef Client. ArcGIS Chef cookbooks support Chef-Client versions 13 and 14.
2. Download the arcgis cookbook to your machine.
3. Unzip and untar the gz file to the /var/chef folder. The final folder structure should be /var/chef/cookbooks/arcgis; /var/chef/cookbooks/tomcat; etc.
4. Edit /var/chef/roles/arcgis-enterprise-rhel.json file.
   • If an attribute value is not specified in the *.json file, chef uses the default value for the attribute.
   • If SSL certificate for Tomcat is not specified, chef generates and uses a self-signed certificate.
   • If node['arcgis']['server']['domain_name'] or node['arcgis']['portal']['domain_name'] attributes are not specified, the FQDN of the machine is used.
   • For the 'install_dir' attribute, specify the installation directory without the subfolder. For example, use "/data/work" instead of "/data/work/arcgis/server".
5. As the super user, run "chef-solo -j /var/chef/arcgis-enterprise-rhel.json"
6. After the chef-solo run is completed, Portal for ArcGIS and ArcGIS Server will be available at https://hostname/portal and https://hostname/server URLs respectively.

Supported Platforms

• Windows: Windows 7, Windows 8 and 8.1, Windows 10, Windows Server 2008 and 2008 R2, Windows Server 2012 and 2012 R2, Windows Server 2016, Windows Server 2019
• Linux: Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, RHEL 6.5, RHEL 7
• Support Non-English OS.

Note:

• For a disconnected environment, make sure you have access to the component resources, e.g. for Tomcat, .NET Framework, etc.

Copyright © Esri 2018