Skip navigation links

Package eu.europa.ec.sfc2014.frontoffice.jws.service.notification

The Event Notification Module web services interface.

See: Description

Package eu.europa.ec.sfc2014.frontoffice.jws.service.notification Description

The Event Notification Module web services interface.

The Notification service is a web service that will allow external systems to get notifications about the events occurred for any object in the SFC2014 application.
At first, the external systems will need to subscribe for events that they wish to track. Subscription can be requested by writing sfc2014-info@ec.europa.eu.
After that, the system can poll the Notification service with the desired interval of time between each call. We invite the external system to poll the Notification service not more than once each ten minutes.
Any system that didn't subscribe first can call the Notification service and will always get an SfcFaultException saying "System not found for acr: ".

The order in the notified events:
Whenever an action is performed (for example actions such Admit, Accept and Decision Taken on an Operational Programme) a message is generated to handle the notification for such actions. The JMS architecture is by design asynchronous: this explains why we cannot give any guarantee


We nevertheless guarantee
  • that all the actions are notified (if a subscription for the action is requested).

If a client still needs to process the events following the chronological order with which they have been generated, it could keep into account that:

  • the pair "OriginatorEventId" + "originator" is unique
  • the "OriginatorEventId" is provided by the "originator" issuing the event
  • consequently, we cannot guarantee that the "OriginatorEventId" are unique, nor that there is a chronological order for the "OriginatorEventId"
  • however, concerning the "originator" "SFC2014" only, we can guarantee that there is a chronological order for the "OriginatorEventId"
This means that (for the system "SFC2014" only!) the chronological order can be determined using "OriginatorEventId". This rule cannot be generalised for other systems.

Clients can also keep into account that:

  • the element "originatorTimestamp" contains the timestamp of the event the originator has given it.
Since:
1.0
Skip navigation links

Copyright © 2024. All rights reserved.