Activity
Module description/purpose
This module will provide user access to all fishing activity data in the system. User would be able to view/sort/filter all fishing activities. It will also enable user to go through all different types of fishing activities and view details in user friendly way.
Basic workflow:
Validated Fishing Activity reports will be received by Activity module over JMS.
Once reports are received, data would be extracted from XML document and will be mapped with database entities. Some post-processing will be done on the data before saving into database for example: enrichment of geometries,calculating fishing trip start and end date. Various front end screens are provided to illustrate the fishing activity data in use friendly format.
Nexus artifacts
Group ID | Artifact ID |
---|---|
eu.europa.ec.fisheries.uvms.activity | activity-module-postgres |
eu.europa.ec.fisheries.uvms.activity | activity-module-weblogic |
Maven (Activity model)
<!-- Integration dependency --> <dependency> |
Github App: https://github.com/UnionVMS/UVMS-ActivityModule-APP
Github activity model: https://github.com/UnionVMS/UVMS-ActivityModule-MODEL
QA Summary App: https://sonarcloud.io/dashboard?id=eu.europa.ec.fisheries.uvms.activity%3Aactivity
CI location App: https://jenkins.focus.fish/view/UVMS%20App/job/UVMS-Activity-APP/
Project Site reports App: https://jenkins.focus.fish/view/Site-Reports/job/UVMS-Activity-APP-Site-Reports/site/
Module dependencies
Name | Description | Documentation |
---|---|---|
Audit | Log all operations which have been executed in all UVMS-modules | Audit |
User | Authentication operations and access management | User |
Config | To configure various permissions on different featuree | Config |
Rules | To receive validated Fishing Activity reports | Rules |
Reporting | Reporting module requests activity data/fishing Trip data from activity module | Reporting |
Assets | To get vessel information from some of the activity | Asset |
Movements | To get movements of vessel received from assets | Movement |
MDR | To map codes from MDR to Asset query parameters. This is needed to query asset for vessels | MDR |
Spatial | To get restricted area for User where user is allowed to view activities | Spatial |
JMS-Queue dependencies
Name | Jndi name example | Description |
---|---|---|
UVMSActivityEvent | java:/jms/queue/UVMSActivityEvent | Request queue to Activity module |
UVMSAsset | Response queue to Asset module | |
UVMSUserEvent | Request queue to User service module | |
UVMSUser | Response queue to User module | |
UVMSMovementEvent | java:/jms/queue/UVMSMovementEvent | Request queue to Movement service module |
UVMSSpatialEvent | jms/queue/UVMSSpatialEvent | Request queue to Spatial service module |
UVMSMdrEvent | jms/queue/UVMSMdrEvent | Request queue to MDR service module |
JMS Services
There are several features available over Activity module JMS
- Get Filtered Fishing Trips : External module can provide some fishing activity filters and get filtered fishing trips with those activities in response.
- Get Catch summary report : External module can ask for summary of catches matching certain criterias
- Get Fishing activities for Fishing Trip : External module can request all fishing activities belonging to certain fishin trips
- Receive Fishing Activity reports : External module can send fishing activity reports to activity module and activity module will save that data in database.
Datasources
Name | Jndi name example |
---|---|
uvms_activity | java:jboss/datasources/uvms_activity |
Jenkins build
https://jenkins.focus.fish/job/UVMS-Activity-APP/
https://jenkins.focus.fish/job/UVMS-Activity-MODEL/
Liquibase scripts
https://github.com/UnionVMS/UVMS-ActivityModule-APP/tree/dev/LIQUIBASE