Upgrade an existing single machine base ArcGIS Enterprise deployment

In this workflow, you will use the ArcGIS Chef Cookbooks to upgrade an existing ArcGIS Enterprise deployment that was originally deployed using ArcGIS Chef Cookbooks.

Prerequisites

Supported Platforms:

• Windows
  • Windows Server 2016 Standard and Datacenter
  • Windows Server 2019 Standard and Datacenter
• Linux
  • Ubuntu Server 18.04 LTS
  • Ubuntu Server 20.04 LTS
  • Red Hat Enterprise Linux Server 7
  • Red Hat Enterprise Linux Server 8
  • CentOS Linux 7
  • CentOS Linux 8

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

• Latest ArcGIS Enterprise Setups from My Esri:
  • Portal for ArcGIS
    • Portal for ArcGIS WebStyles (optional: starting at 10.7.1 and above)
  • ArcGIS Server
  • ArcGIS Data Store
  • ArcGIS Web Adaptor
• ArcGIS Enterprise authorization files. Make sure to use the correct authorization file for different products.
• It is recommended to create a backup using the ArcGIS Enterprise WebGISDR tool.
• An existing ArcGIS Enterprise base deployment that was originally deployed using ArcGIS Chef Cookbooks.

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

Windows or Linux

1. Download and install Chef Infra Client. To see the supported versions of Chef Client check out the Esri cookbooks and Chef Infra client version compatibility resource.

2. Download the latest ArcGIS Chef Cookbook Release, that corresponds with the ArcGIS Enterprise version you are upgrading to.

3. Extract the contents of the cookbook.

   • If using Windows, extract the contents of the cookbook zip file to C:\chef. The final folder structure should be c:\chef\cookbooks\arcgis-enterprise; c:\chef\cookbooks\arcgis-repository; etc.
   • If using Linux, unzip and untar the gz file to the /var/chef folder. The final folder structure should be /var/chef/cookbooks/arcgis-enterprise; /var/chef/cookbooks/arcgis-repository; etc.

4. Using a text editor, open the role JSON file that was used to originally deploy ArcGIS Enterprise, and save with a new name.

   • Windows: C:\chef\roles\arcgis-enterprise-upgr.json
   • Linux: /var/chef/roles/arcgis-enterprise-upgr.json

5. Using a text editor, open the arcgis-enterprise-upgr.json file created in step 4.

   • Update the node['arcgis']['version'] attribute to the latest version you are upgrading to.
   • Update the ['setup'], or ['setup_archive'], paths to point to the latest setups you are upgrading to for each Enterprise component.
   • Update the node['arcgis']['portal']['authorization_file'] and node['arcgis']['server']['authorization_file'] to point to the latest version of authorization files you are upgrading to.
   • Add the node['arcgis']['portal']['user_license_type_id'] attribute. For example:
     • "user_license_type_id":"creatorUT"
   • If you will be installing Portal for ArcGIS WebStyles, then add node['arcgis']['webstyles']['setup'] or node['arcgis']['webstyles']['setup_archive']and point to path of the Portal for ArcGIS WebStyles setup.

6. In the arcgis-enterprise-upgr.json file, ensure the recipe "run-list" is in the following order:

   • "recipe[arcgis-enterprise::portal]",
   • "recipe[arcgis-enterprise::portal_wa]",
   • "recipe[arcgis-enterprise::server]",
   • "recipe[arcgis-enterprise::server_wa]",
   • "recipe[arcgis-enterprise::datastore]"

Note: If you will be installing Portal for ArcGIS WebStyles, then add "recipe[arcgis-enterprise::webstyles]" recipe to the run-list. Place it after "recipe[arcgis-enterprise::portal]" recipe.

7. Use chef-client and the arcgis-enterprise-upgr.json role file to perform the upgrade.

   • Windows: Start a command prompt window as an administrator and run:

     • chef-client -z -j C:\chef\roles\arcgis-enterprise-upgr.json

   • Linux: As the super user, run:

     • chef-client -z -j /var/chef/roles/arcgis-enterprise-upgr.json

After the chef-client run completes, your ArcGIS Enterprise portal and hosting server will be available at the https://hostname.domain.com/portal and https://hostname.domain.com/server URLs, respectively.