Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Description

MDR plugin acts as mediator between FLUX node and Exchange module.

  1. REQUEST    :  MDR plugin receives messages from Exchange and propagates them to FLUX Node.
  2. RESPONSE :  MDR plugin receives messages from FLUX Node and propagates them to the Exchange module. It is Important to note that MDR plugin just propagates the message to Exchange without knowing/extracting whats inside it.

Communication between FLUX node / Exchange and MDR 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 MDR Plugin plugin.

This application will act as bridge between FLUX Node and fishing MDR Plugin.

Basically the following happens during a whole cycle of request/response :

  1. MDR Plugin puts the requests in the "UVMSPluginBridge" queue which is being listened by the bridge application which picks the message and transports it to the next Flux Node (Ex. AHR:VMS Node);
  2. The bridge application listens to the remote FLUX bridge queue (queue residing in the FLUX Node) for responses and once it has it it transports it to "UVMSMdrluginEvent" queue.
  3. Once the message is in the "UVMSMdrluginEvent" queue MDR Plugin picks it up and transports (without reading it) the message to Exchange (always through JMS communication).

JMS Queues

Queue Name
Purpose
java:/jms/queue/UVMSMdrluginEvent
FLUX messages will be received on this queue
jms/queue/UVMSPluginBridge
FLUX response messages will be sent to FLUX node on this queue


Github Repository

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

Focus Nexus Build

https://jenkins.focus.fish/job/UVMS-MDR-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'






  • No labels