Update Get Started With ArcGIS Cookbook

[pbobov]

After reading the Get Started With ArcGIS Cookbook on github there were a few things that were not clear to me:

1. The port redirection (port forwarding) through the firewall a. It is not immediately obvious that iptables is configured for redirecting requests. This feature is documented on the README.md and the arcgis‐enterprise-Cookbook-Recipes Page. However I was specifically looking for this. Initially it was not obvious this was happening. b. Also, it is not clear whether iptables needs to be running prior to starting the chef-solo command. Does the cookbook enable ‘ufw’ (Ubuntu) or start the service (RedHat) when it runs? c. Can Prerequisite section on the Get Started With ArcGIS Cookbook page be updated to state the dependency of the firewall and how it will be used?
2. Using valid and correctly populated license files a. The cookbook uses some ArcGIS products that require a valid license. While I made sure to use the valid authorization files, a mistake I made was to just grab license from metro and point webgis-ubuntu.json at this location on my file system. From the point of view of an Esri employee, this step was not enough because the cookbook will fail unless the Email field in the license file is set to a valid address. While some users may already have this info in their file, I did not (since I copied it straight from metro) and the install process failed (at ArcGIS Server and Portal). b. I only knew the lack of the Email address was the issue because I have authorized ArcGIS Server before. There error message only says the license file is not valid c. Is it possible to also warn the user on what specifically is wrong with the license file?
3. The /etc/hosts file a. The /etc/hosts file is a simple resource but one that can interfere with a deployment if configured a certain way b. The default /etc/hosts file in Ubuntu takes the machine name given from the installer and assigns that to 127.0.1.1. It is theorized that this was might be a reason why the datastore could register on localhost but not with his FQDN. c. I don’t think it is a good idea that from the server itself, the FQDN resolves to 127.0.1.1…this should be resolved by DNS. Is it possible to have the cookbook check the entries in /etc/hosts and warn the user accordingly?
4. Chef Client feedback when complete a. The cookbook ran for an hour on my machine and completed with “Chef Client finished”. This is good to see but it was not clear what to do after that. I could tell Portal was running successfully on port 7443 and ArcGIS Server was running successfully on port 6443 but pointing to Tomcat on https://MYHOSTNAME.DOMAIN/arcgis/rest just gave me a blank page. I had to search the file system, find the Tomcat directory, then look in the webapps folder to see that there were two apps installed as portal and server. This was not obvious. b. Can the Chef client print feedback to the screen telling the user that they can now validate the deployment by point their browser to: https://MYHOSTNAME.DOMAIN/portal and https://MYHOSTNAME.DOMAIN/server