Fetching contributors…
Cannot retrieve contributors at this time
99 lines (69 sloc) 3.5 KB

Exonum Java Binding App Tutorial

This document describes how to configure and run an Exonum node with a Java service using Java Binding App.


Build an application following the instructions in “How to Build” section of the Contribution Guide.

You also need a ready-to-use Exonum Java service. You can use cryptocurrency-demo as an example, and find information about implementing your own Exonum service in the user guide.

How to Run an Exonum Node

Step 1. Configure Environment

EJB_ROOT used in examples of this section corresponds to the Java Binding root directory.


LD_LIBRARY_PATH is required to locate native libraries used by Java Binding. You need to provide paths to:

  • JVM library (e.g., on Linux).
  • Rust standard library that is used to build the application.
  • Application libraries used by Java Binding.

You can use the following script for this purpose:

JAVA_HOME="${JAVA_HOME:-$(java -XshowSettings:properties -version 2>&1 > /dev/null | grep 'java.home' | awk '{print $3}')}"
LIBJVM_PATH="$(find ${JAVA_HOME} -type f -name libjvm.* | xargs -n1 dirname)"

RUST_LIB_PATH="$(rustup run 1.27.2 rustc --print sysroot)/lib"

export EJB_LIBPATH="${EJB_ROOT}/exonum-java-binding-core/rust/target/debug"



Classpath is used to locate Java classes of your service and its dependencies, including the Exonum Java Binding.

You may package your service in an Uber JAR using the Maven Shade Plugin and pass a path to the service artefact during application configuration as --ejb-classpath parameter. Alternatively, you may assemble a classpath that includes the service and all of its dependencies and pass it instead.

Step 2. Generate Node Configuration

EJB App configuration is pretty similar to configuration of any other Exonum service, with a few additional parameters.

Note: using cargo run command requires working from the ejb-app directory. This would be fixed in the future EJB versions.

Generate Template Config

$ cargo run -- generate-template testnet/common.toml

Generate Node Private and Public Configs

  • --ejb-classpath for a classpath of your service.
  • --ejb-libpath for a path to Java bindings native libraries.
$ cargo run -- generate-config testnet/common.toml testnet/pub.toml testnet/sec.toml \
    --ejb-classpath $EJB_CLASSPATH \
    --ejb-libpath $EJB_LIBPATH \

Finalize Configuration

There are two specific parameters here:

  • --ejb-module-name for fully qualified name of your ServiceModule.
  • --ejb-port for port that your service will use for communication. Java Binding does not use Exonum Core ports directly.
$ cargo run -- finalize testnet/sec.toml testnet/node.toml \
    --ejb-module-name 'com.<company-name>.<project-name>.ServiceModule' \
    --ejb-port 6000 \
    --public-configs testnet/pub.toml

Step 3. Run Configured Node

$ cargo run -- run -d testnet/db -c testnet/node.toml --public-api-address