Federation Gateway Developer Guide

Building and Packaging


The build machine needs the following:

  1. Java version 1.8
  2. Maven version 3
  3. Connectivity to Maven Central (for most jars)
  4. Connectivity to Linux Foundation Nexus (for CDS jar)

Use below maven command to build and package the gateway service into a single jar:

mvn clean package

Development and Local Testing

This section provides information for developing and testing the federaton gateway locally. We will run two instances of the gateway to depict two instance of Acumos federated to each other. In below scenario, we are going to run Acumos A and Acumos B for testing locally.


Start two microservice instances for development and testing as follows, with the appropriate version numbers:

java -Djavax.net.ssl.trustStore=src/test/resources/acumosTrustStore.jks \
     -Djavax.net.ssl.trustStorePassword=acumos \
     -jar target/gateway-1.x.y-SNAPSHOT.jar \

java -Djavax.net.ssl.trustStore=src/test/resources/acumosTrustStore.jks \
     -Djavax.net.ssl.trustStorePassword=acumos \
     -jar target/gateway-1.x.y-SNAPSHOT.jar \

REST Interface

The federation interface allows access via the federation gateway to information available in an Acumos system. The main category of information that is exposed via the gateway is solution information: solution/revision/artifact and artifact content. The federation gateway allows access from pre-registered peers via a REST interface running over HTTPS/SSL/TLS. The gateway requires mutual authentication; i.e., the client will be required to present a certificate. The gateway identifies a client as a pre-registered peer based on the certificates’ subjectName (which implies that the subjectName must be communicated to the Acumos system administrator when the peer is provisioned).


All APIs encode the response in JSON. There is a top level envelope containing error information, and under the entry ‘responseBody’ it contains the actual content. All identifiers are UUIDs. The following endpoints are defined:

  • /solutions

    List all public solutions. Accepts a query parameter, ‘selector’, which contains a JSON object with selection criteria, base64 encoded. Acceptable selection criteria are the solution object attributes. The entries are ANDed.

  • /solutions/{solutionId}

    Retrieve one solution details.

  • /solutions/{solutionId}/revisions

    List all revisions for a given solution.

  • /solutions/{solutionId}/revisions/{revisionId}

    Retrieve one revision details

  • /solutions/{solutionId}/revisions/{revisionId}/artifacts

    List all artifacts attached to a particular revision

  • /artifacts/{artifactId}

    Retrieve one artifact details

  • /artifacts/{artifactId}/download

    Download the artifact content.

Example of solutions selector: The following will select all CLassifiers:

{ "modelTypeCode":"CL" }

Multiple values for a solution attribute are allowed and ORed. The following will select all CLassifiers and PRedictors:

{ "modelTypeCode":["CL","PR"] }