ArcGIS Engine Developer Guide

BUILDING A COMMAND-LINE JAVA APPLICATION
• ANT_HOME=%ARCENGINEHOME\DeveloperKit\tools\ant
Setting up environment variables on Solaris and Linux
To configure your environment on Solaris and Linux you should source two setup
scripts. The init_engine script in the ArcGIS installation directory sets the
ARCENGINEHOME environment variable as well as several required paths.
The setenv_ant script in arcgis/developerkit/tools sets the ANT_HOME variable
to point to arcgisant and includes arcgisant’s bin directory in your PATH.
• If you use C-shell:
To compile and run applications using the ArcGIS
Engine Developer Kit, the PATH environment
variable should include paths to ArcGIS/bin and
J2SE JRE/bin. In addition, ArcGIS Engine Developer
Kit ships with an extended version of Ant
called arcgisant. The path to this tool should
also be included.
Folder and file structure required for the build
scripts to work as desired
source .../arcgis/init_engine.csh
source .../arcgis/developerkit/tools/setenv_ant.csh
• If you use bash or bourne shell:
source .../arcgis/init_engine.sh
source .../arcgis/developerkit/tools/setenv_ant.sh
You should also set the JAVA_HOME environment variable to point to the
install location of your J2SE SDK.
• Using C-shell:
setenv JAVA_HOME [J2SE SDK install directory]
• Using bash or bourne shell:
JAVA_HOME=[J2SE SDK install directory]
Build scripts
Before proceeding with building the application itself, you need to prepare the
build scripts. It is vital to set up the build structure as illustrated to the left for
the scripts to work correctly.
• TintoPoint folder—root folder for the project
• src folder—subfolder containing all of the application’s source code
• build.xml—Ant build script file
• properties.xml—external Ant properties file, which extends the build environment
• sample.properties—external Java properties file with command-line parameters
The three files—build.xml, properties.xml, and sample.properties—must be
created before you can build and run the scenario.
Creating the sample.properties file
Begin by creating the sample.properties file. This file provides the build script
with necessary command-line arguments to successfully execute the application
created in this exercise. This file will use the variable=argument pattern.
1. Create a text file named sample.properties and add the following lines of code
to it. Revise the arguments for the variables input.tin.path and
output.shape.path to match the paths to your TIN dataset and output
shapefile dataset.
# TinToPoint
unit.name=TintoPoint
Chapter 6 • Developer scenarios • 411