A set of dockers for ESRI Arcgis Enterprise

Make sure you check the wiki, https://github.com/Geo-CEG/docker-arcgis-enterprise/wiki

There were 4 separate github repos for this project, they have been combined into one repo for all four dockers.

Each of these folders contains files to build a separate Docker image:

• arcgis-server/
• portal-for-arcgis/
• web-adaptor/
• datastore/

To connect the separate dockers together and enable the use of hostnames requires creating a custom network.

Use this command:

docker network create wildsong.lan

Each of the provided scripts in this repo assumes you use "wildsong.lan" as the network name.

You only have to do this once, it hangs around in your docker engine.

When I am building and testing everything on my Mac, I just append the addresses to my /etc/hosts file so that name lookups work. For example,

cat >> /etc/hosts
127.0.0.1 portal portal.wildsong.lan 
127.0.0.1 server server.wildsong.lan
127.0.0.1 web-adaptor web-adaptor.wildsong.lan
127.0.0.1 datastore datastore.wildsong.lan

You don't have to use "wildsong.lan", but if you change that then change AGS_DOMAIN too, see below.

• Download archives from ESRI. Put each tar.gz file in the appropriate folder.
• Create provisioning files for ArcGIS Server and Portal for ArcGIS and put them in their folders.

(For testing only, it is also possible to build these containers without the propietary ESRI files, and that's what will happen on hub.docker.com once I get things sorted out.)

  docker-compose build

When you are done you should be able to see each image with the command "docker images"; on my machine I see this:

REPOSITORY TAG IMAGE ID CREATED SIZE geoceg/datastore latest 2b61b9429659 2 minutes ago 2.835 GB geoceg/web-adaptor latest ab34fd0cdea5 4 minutes ago 1.156 GB geoceg/portal-for-arcgis latest e2e69bac2ca6 5 minutes ago 9.252 GB geoceg/arcgis-server latest eae45e398fac 16 minutes ago 12.39 GB

You have to define three things somewhere in your environment. I put them in .bash_profile on a Mac, and it gets used in each startup script. Remember to refresh your environment before going on so the .bash_profile takes effect. (Normally this means starting a new shell.)

export AGS_USER="siteadmin"
export AGS_PASSWORD="yourpasswordhere"
export AGS_DOMAIN="wildsong.lan"

My intention is to start them all at once. For the moment, you will need to cd into each folder and issue the run command there. Each folder has a script. The run* script runs in interactive mode, the start* script in detached mode. So far I have been starting each component in interactive mode in a separate window so that I can watch what happens and can start and stop them independently.

So, in

• window #1, cd arcgis-server && ./runags
• window #2, cd portal-for-arcgis && ./runportal
• window #3, cd web-adaptor && ./runwa
• window #4, cd datastore && ./runds

As you run each component, you will get instructions on what to do and a command prompt. For example, to start arcgis-server from the command prompt you will be instructed to run the start script, ./start.sh The session would look something like this:

$ cd arcgis-server
$ ./runags 
Docker is starting in interactive mode.
Management URL is http://laysan:6080/arcgis/manager
Start AGS and configure it with  ./start.sh
ArcGIS Server$ ./start.sh 
My hostname is server.wildsong.lan
Removing previous site configuration files.
Starting ArcGIS Server
Attempting to start ArcGIS Server... Hostname change detected, updating properties...


Waiting for ArcGIS Server to start...
Yes; configuring default site.
Error: HTTPSConnectionPool(host='server', port=6443): Read timed out. (read timeout=30)
A timeout here might not mean anything. Try accessing your server.

At this point you should be able to bring up the server in a browser (use the URL printed by the script) and log into it. Default username is 'siteadmin' and the password is 'changeit'. As stated above you can override these by defining AGS_USER and AGS_PASSWORD in the environment before you run the start.sh script. (Note, start.sh calls the script "create_new_site.py".)

Then continue to open additional (shell terminal) windows and start the other components in this order: portal-for-arcgis, web-adaptor, datastore.

You can learn a lot about how ESRI thinks provisioning should be done by reading the source code from their Github Chef repository. For example, here is the code that creates a site by using REST. This is ruby code from arcgis-cookbook/cookbooks/arcgis-enterprise/libraries/server_admin_client.rb that is pretty easy to read, basically it's filling in a form and sending it.

  log_settings = {
    'logLevel' => log_level,
    'logDir' => log_dir,
    'maxErrorReportsCount' => 10,
    'maxLogFileAge' => max_log_file_age }

  request = Net::HTTP::Post.new(URI.parse(
    @server_url + '/admin/createNewSite').request_uri)

  request.set_form_data('username' => @admin_username,
                        'password' => @admin_password,
                        'configStoreConnection' => config_store_connection.to_json,
                        'directories' => directories.to_json,
                        'settings' => log_settings.to_json,
                        'cluster' => '',
                        'f' => 'json')

  response = send_request(request, @server_url)

  validate_response(response)

You should be able to see the form by going to https://yourserver:6443/admin/createNewSite