22.2. Installing GeoMesa Lambda¶
22.2.1. Installing from the Binary Distribution¶
GeoMesa Lambda artifacts are available for download or can be built from source. The easiest way to get started is to download the most recent binary version (3.2.2) from GitHub.
Extract it somewhere convenient:
# download and unpackage the most recent distribution: $ wget "https://github.com/locationtech/geomesa/releases/download/geomesa_2.11-$VERSION/geomesa-lambda_2.11-$VERSION-bin.tar.gz" $ tar xvf geomesa-lambda_2.11-$VERSION-bin.tar.gz $ cd geomesa-lambda_2.11-$VERSION $ ls bin/ conf/ dist/ docs/ examples/ lib/ LICENSE.txt logs/
22.2.2. Building from Source¶
GeoMesa Lambda may also be built from source. For more information refer to Building from Source
in the developer manual, or to the
README.md file in the the source distribution.
The remainder of the instructions in this chapter assume the use of the binary GeoMesa Lambda
distribution. If you have built from source, the distribution is created in the
target directory of
More information about developing with GeoMesa may be found in the Developer Manual.
22.2.3. Installing the Accumulo Distributed Runtime Library¶
The Lambda data store requires the Accumulo data store distributed runtime to be installed. See Installing the Accumulo Distributed Runtime Library.
22.2.4. Setting up the Lambda Command Line Tools¶
GeoMesa comes with a set of command line tools located in
geomesa-lambda_2.11-$VERSION/bin/ of the binary distribution.
18.104.22.168. Configuring the Classpath¶
GeoMesa needs Accumulo, Hadoop and Kafka JARs on the classpath. These are not bundled by default, as they should match the versions installed on the target system.
If the environment variables
KAFKA_HOME are set, then GeoMesa will load
the appropriate JARs and configuration files from those locations and no further configuration is required. Otherwise,
you will be prompted to download the appropriate JARs the first time you invoke the tools. Environment variables can be
conf/*-env.sh and dependency versions can be specified in
In order to run map/reduce jobs, the Hadoop
*-site.xml configuration files from your Hadoop installation
must be on the classpath. If
HADOOP_HOME is not set, then copy them into
GeoMesa also provides the ability to add additional JARs to the classpath using the environmental variable
$GEOMESA_EXTRA_CLASSPATHS. GeoMesa will prepend the contents of this environmental variable to the computed
classpath, giving it highest precedence in the classpath. Users can provide directories of jar files or individual
files using a colon (
:) as a delimiter. These entries will also be added the the map-reduce libjars variable.
See Logging Configuration for information about configuring the SLF4J implementation.
Due to licensing restrictions, dependencies for shape file support must be separately installed. Do this with the following command:
Test the command that invokes the GeoMesa Tools:
$ geomesa-lambda Usage: geomesa-lambda [command] [command options] Commands: ...
GeoMesa Accumulo command-line tools can be used against features which have been persisted to Accumulo. See Setting up the Accumulo Command Line Tools for details on the Accumulo command-line tools.
22.2.5. Installing GeoMesa Lambda in GeoServer¶
See GeoServer Versions to ensure that GeoServer is compatible with your GeoMesa version.
22.214.171.124. Installing GeoServer¶
As described in section GeoMesa and GeoServer, GeoMesa implements a GeoTools-compatible data store. This makes it possible to use GeoMesa as a data store in GeoServer. GeoServer’s web site includes installation instructions for GeoServer.
After GeoServer is installed, you may install the WPS plugin if you plan to use GeoMesa processes. The GeoServer WPS Plugin must match the version of the GeoServer instance. The GeoServer website includes instructions for downloading and installing the WPS plugin.
If using Tomcat as a web server, it will most likely be necessary to pass some custom options:
export CATALINA_OPTS="-Xmx8g -XX:MaxPermSize=512M -Duser.timezone=UTC \ -server -Djava.awt.headless=true"
The value of
-Xmx should be as large as your system will permit. Be sure to restart
Tomcat for changes to take place.
126.96.36.199. Installing the GeoMesa Lambda Data Store¶
To install the GeoMesa data store, extract the contents of the
geomesa-lambda-gs-plugin_2.11-$VERSION-install.tar.gz file in
in the binary distribution or
geomesa-lambda/geomesa-lambda-gs-plugin/target/ in the source
distribution into your GeoServer’s
$ tar -xzvf \ geomesa-lambda_2.11-$VERSION/dist/gs-plugins/geomesa-lambda-gs-plugin_2.11-$VERSION-install.tar.gz \ -C /path/to/geoserver/webapps/geoserver/WEB-INF/lib
Next, install the JARs for Accumulo, Hadoop and Kafka. By default, JARs will be downloaded from Maven central. You may
override this by setting the environment variable
GEOMESA_MAVEN_URL. If you do no have an internet connection
you can download the JARs manually via http://search.maven.org/.
Edit the file
geomesa-lambda_2.11-$VERSION/conf/dependencies.sh to set the versions of Accumulo, Hadoop and Kafka
to match the target environment, and then run the script:
$ ./bin/install-dependencies.sh /path/to/geoserver/webapps/geoserver/WEB-INF/lib
Due to a classpath conflict with GeoServer, the version of Accumulo client JARs installed must be 1.9.2 or later. Note that newer Accumulo clients can talk to older Accumulo instances, so it is only necessary to upgrade the client JARs in GeoServer, but not the entire Accumulo cluster.
GeoServer ships with an older version of commons-text, 1.4. The
install-dependencies.sh script will
remove it, but if you don’t use the script you will need to delete it manually.
The specific JARs needed for some common configurations are listed below:
Hadoop 2.4-2.7 (adjust versions as needed)
Restart GeoServer after the JARs are installed.
To upgrade between minor releases of GeoMesa, the versions of all GeoMesa components
must match. This means that the version of the
JAR installed on Accumulo tablet servers must match the version of the
geomesa-plugin JARs installed in the
WEB-INF/lib directory of GeoServer.
See Upgrade Guide for more details on upgrading between versions.