Plugin - Fishing Activity

Description

Fishing Activity plugin acts as mediator between FLUX node and Exchange module. Fishing Activity plugin receives message from FLUX Node. Plugin will then extract envelope properties and create request for Exchange module with those properties. Flux Plugin will not try to read the message at this point. It will directly send the message to exchange without trying to extract it.

Communication between FLUX node and Fishing Activity plugin will happen over JMS. Flux Plugin needs to communicate to remote queues residing on FLUX node. To avoid configuring remote queue bridge into wildfly, another bridge application has been created. This application has to be deployed along with fishing activity plugin. This application will act as bridge between flux node and fishing activity plugin. Bridge application will receive messages from FLUX node and forward it to local queues defined for Activity plugin. Activity plugin will then communicate with only local queues without any knowledge of remote queues.

JMS Queues

java:/jms/queue/UVMSFAPluginEvent

jms/queue/UVMSPluginBridge

Github Repository

https://github.com/UnionVMS/UVMS-FLUXACTIVITY-PLUGIN

Focus Nexus Build

https://jenkins.focus.fish/job/UVMS-FLUXACTIVITY-PLUGIN/

Configuration on FLUX Node for the Plugin

• DF Value : Currently DF value configured on FLUX node for Fishing Activity plugin is 'urn:un:unece:uncefact:fisheries:FLUX:FA:EU:2'
• JMS Queue name : Fishing Activity report messages will be forwarded to 'jms/queue/FAPlugin' queue on FLUX node. Plugin should receive messages on this queue.
• JMS Queue to send messages :  FLUX node will receive response messages on  'jms/queue/bridge'