Overview

The eSpatial upload tool provides a method to automate the upload of data from your systems into eSpatial. This is a great way to keep your maps up to date with the latest data from your CRM, ERP, Databases and Spreadsheets. 

The eSpatial upload tool needs to be setup on your infrastructure. This can be installed on a server, laptop or desktop. The Upload Tool is a Java application that can be run on a wide variety of Operating Systems. 

System Requirements

Minimum recommended system requirements:

Installation and configuration

1. To request access to the upload tool, please contact your Customer Success Manager or use in-app chat. 

2. Unzip the esUploadTool Zip file onto the target machine.

3. To run the configuration wizard, double-click:

                  esUploadTool\run-wizard.bat

          or manually modify the configuration file:

                  esUploadTool\esUpload-config.json

4. To start the begin monitoring configured directory/directories, run or double click:

                  esUploadTool\run.bat
                  OR
                  double click on esUploadTool-1.4-jar-with-dependencies.jar to run in the background as a service

Maintenance & Notes

  • In the event of a server restart, run: 

                  esUploadTool\run.bat
                  OR
                  double click on esUploadTool-1.4-jar-with-dependencies.jar to run in the background as a service

For ease of maintenance, it is recommended that this is configured to run every time the server starts. See also: http://windows.microsoft.com/en-ie/windows/run-program-automatically-windows-starts

  • Logging from theUpload Tool can be configured:

                  esUploadTool\logging.properties

You can send the output to both the console and log file at a logging level of INFO, WARNING or SEVERE. 

  • On Windows Systems, applications cannot be run from a networked drive e.g.\\myNetworkDrive\esUploadTool. If the esUploadTool is installed on a server and shared directory you must log in or remotely connect to the machine to run it.
Did this answer your question?