Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fix typo

...

  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                                                                                                                                      to Exchange without knowing/extracting whats inside it.

...

  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 "UVMSMdrluginEventUVMSMdrPluginEvent" queue.
  3. Once the message is in the "UVMSMdrluginEventUVMSMdrPluginEvent" queue MDR Plugin picks it up and transports (without reading it) the message to Exchange (always through JMS communication).

...


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



...

  • DF Value : Currently DF value configured on FLUX node for MDR Plugin is 'urn:un:unece:uncefact:fisheries:FLUX:FAMDM:EU:2'
  • JMS Queue to send messages : Mdr request messages will be forwarded to 'UVMSPluginBridge' queue.
  • JMS Queue to receive messages : Mdr response messages will be forwarded to 'UVMSMdrluginEventUVMSMdrPluginEvent' queue.