SDI Library

SDI Library is a java library designed to help developers interact with gCube SDI.It is part of the gCube-SDI-Suite, and it is the main entry point for developpers wanting to exploits client implementations towards the SDI subsystems (i.e. SDI-Service, GeoNetwork, GeoServer ). It offers static gCube-fw-clients that communicate with SDI-Service for the management of gCube SDI and common publication features. It also manages client implementation for third-parties SDI technologies, allowing for direct communication with these subsystems.

Design

Following diagram illustrate the relations between the various clients components in gcube-sdi-suite.

SDI Clients

To external users, the main component of interest is sdi-library, built on top of the sdi-interface which contains common classes definition. SDI Library exposes basic gCube clients towards SDI-Service REST interfaces. SDI Library also exposes means to dynamically load and instantiate client implementations for specific SDI subsystems (e.g. GeoServer, GeoNetwork).

Each client imeplementation exposes :

• Information on internal implementation
• Information on the target engine
• Range of supported version for the declared target engine.

Philosophy

The library has been designed to maximize isolation of dependencies : common complex logic is supported on services and client implementations are discovered at runtime.

The main library sdi-ibrary offers ways to obtain specific client implementation based on :

• Information System Configuration : accessible third-parties services, configuration and version
• Available implementations at runtime

Static Clients

Static clients are directly defined in sdi-library, so no dynamic loading is needed. They are implemented as gCube-fw-clients towards SDI Sevice REST interfaces and cover most common use cases such as :

• Manage SDI configuration (instances, credentials, IS Resources)
• Manage Application Profiles
• Instantiate Dynamic clients
• Common basic publish logic

SDI Management

SDI Management client communicates with SDI Service REST interface, and should be used for :

• Manage SDI Configuration
• Inspect SDI-Health
• Obtain specific client

Following sections describe common usage. Please, refere to SDI Service for further information.

Check current Scope Configuration

Following example snippet shows how to printout current context's configuration

import static org.gcube.spatial.data.sdi.plugins.SDIAbstractPlugin.management;
import org.gcube.spatial.data.sdi.interfaces.SDIManagement;
...
 
SDIManagement sdi=management().build();
System.out.println(sdi.getConfiguration());

Instantiate specific client

SDI Management should be used to dynamically instantiate client implementations against runtime configuration.

It automatically checks :

• IS Configuration : in order to assess accessible subsystem and their configuration
• CLASSPATH : in order to dynamically load available cients.
• Supported engine version : REST API can drastically change from version, so specific plugins may be distributed.

Following example snippet shows how to obtain a client by its engineID and printout its exposed information.

import static org.gcube.spatial.data.sdi.plugins.SDIAbstractPlugin.management;
import org.gcube.spatial.data.sdi.interfaces.SDIManagement;
...
 
String engineID=...
System.out.println(management().build().getClientByEngineId(engineID).getInfo());

Dynamic Clients

Dynamic Clients are java components aimed at communicating with SDI subsystems (e.g. GeoServer, GeoNetwork..). Available implementations are dynamically discovered through JAVA reflection, so beware that you have the wanted client in your CLASSPATH at runtime.

Each client exposes informations about :

• Their internal implementation
• Their Specific ID
• The supported target Engine, identified by :
  • Engine ID : String representing the engine technology (e.g. "geonetwork")
  • Engine description : String describing the target engine and its developers.
  • Supported Version Range : Range of supported engine versions

Through #SDI Management, Dynamic clients :

• Are discovered in classpath at runtime
• Their target engine is checked against current context configuration
• They are automatically instantiated.

Following sections described currently knows available implementations.

gCube GeoServer Client

gCube GeoServer Client is a java client over GeoServer REST API.

It is distributed as the following artifact :

<artifactId>gcube-geoserver-client</artifactId>
<groupId>org.gcube.spatial.data</groupId>

Following snippet illustrate how to instantiate the client and printout available workspaces:

import static org.gcube.spatial.data.sdi.plugins.SDIAbstractPlugin.management;
import org.gcube.spatial.data.sdi.interfaces.SDIManagement;
import org.gcube.spatial.data.clients.model.engine.Engine;
...
 
GSRESTClient gs=(GSRESTClient) management().build().getClientByEngineId(Engine.GS_ENGINE).getRESTClient();
System.out.println(gs.getWorkspaces());