Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

One important thing to understand about the movement module are movements, segments and tracks.


...

Code Block
languagexml
themeConfluence
titleMaven
<!-- Integration dependency -->
<dependency>
  <groupId>eu.europa.ec.fisheries.uvms.movement</groupId>
  <artifactId>movement-model</artifactId>
  <version>2.1.1</version>
  <classifier>date</classifier>
</dependency>

Module dependencies

All movements are calculated to be a part of a segment and a track. Calculations can then be made to control the reported speeds and courses to the actual speed and courses that are calculated. More of this can be read on the Javadoc.

Image Removed

The movement module can also store searches that a user makes on positions for later retrieval so the user don´t have to fill all fields again when making a search.

The movement module has functionality for storing temporary ( manual ) positions. These positions can be created saved and retrieved for later processing. When the user wants to he or she can execute the movement. When the movement is executed it is sent to the exchange module who in turn processes the position report.

Nexus artifacts and dependencies


Main moduleDatabase module
SnapshotSnapshot
ReleaseRelease
Code Block
languagexml
themeConfluence
titleMaven
<!-- Integration dependency -->
<dependency>
  <groupId>eu.europa.ec.fisheries.uvms.movement</groupId>
  <artifactId>movement-model</artifactId>
  <version>2.1.1</version>
  <classifier>date</classifier>
</dependency>


Module dependencies


Name

Description

Documentation

Spatial

Retrieve Spatial enrichment data regarding areas for a movement. This is due to pre calculation of spatial data that is stored in the movement database

Spatial

Exchange

When sending a temporary movement that movement is sent to exchange who in turn processes the movement like a movement retrieved from any system o plugin

Exchange

Audit

Audit logs are sent to the audit module. Audit logs are created when actions that changes data in the database are made.

Audit

User

All requests to the REST api is authenticated via the user module. If the user module is undeployed the rest api for the movement module will not work

User


Calculations - Flow

All movements are calculated to be a part of a segment and a track. Calculations can then be made to control the reported speeds and courses to the actual speed and courses that are calculated. More of this can be read on the Javadoc.


Image Added



JMS-Queue dependencies


The jndi name example is taken from wildfly8.2 application server

...

The jndi name example is taken from wildfly8.2 application server


Name

Jndi name example

 

Name

Purpose

Compabilities

uvms_movement

java:jboss/datasources/uvms_movement

 

 

 

Tested compatabilities

Applicationserver

  • Wildfly 8.1
  • Wildfly 8.2

Database

  • Postgres 9.4.4 with PostGis extension

JMS provider

  • ActiveMq 5.0

Availabale database modules

All database modules can be found under the DB folder

movement-dbaccess

Middlehand between movement module and database

Postgres 9.4.4 with PostGis extension

Available proxy modules

All proxy modules can be found under the PROXY folder

Name

Purpose

N/A

N/A

Avaliable plugin modules

All plugin modules can be found under the PLUGIN folder

Name

Purpose

N/A

N/A

Liquibase – database compability

All Liquibase scripts can be found under the LIQUIBASE folder

Database

version

Postgres

9.4.4 with PostGis extension