Feedback Event Configuration

The data is transferred by initiating an event in or from either of the systems. Depending on the lifecycle of an event, a feedback event containing information from the original event is triggered. There are two types of feedback events: Local and Remote.

To activate feedback events, you have to declare the feedback events in the event-config.xml file of the Gateways.

An event is:

  • Successful: When all its processing finishes successfully.
  • Unsuccessful: When one or all of its processing finishes with an error. After an event is unsuccessful, it can be retried or removed.
  • Aborted: When it is removed or purged using the admin console or purged monitoring services.

Local Feedback Event Remote Feedback Event
Feedback event is automatically triggered

When the processing on local site is

  • unsuccessful or the communication with the remote site is unsuccessful.
  • aborted.

When the processing on remote site is

  • successful
  • unsuccessful
  • aborted

Feedback Event Naming

[ORIGINAL_EVENT_NAME]_LocalFeedback

[ORIGINAL_EVENT_NAME]_RemoteFeedback
Feedback Event Parameters

  • Result: The value can be ERROR or ABORT.

    Note: In case of ERROR it is possible that several feedback events are sent for the same original event. OK and ABORT feedback events are definitive results.

  • OriginalEventID: The value should be the EventID of the original event.

  • OriginalEventState: The value should be the last state of the original event.

  • Result: The value can be OK, ERROR or ABORT.

    Note: In case of ERROR it is possible that several feedback events are sent for the same original event. OK and ABORT feedback events are definitive results.

  • OriginalEventID: the value should be the EventID of the original event.

  • OriginalEventState: the value should be the last state of the original event.

Activating and Configuring Feedback Events

Add the following entry for PRODUCTMirror_LocalFeedback on the X-PDM Gateway side:

Note: There is no need to declare the local feedback events on 3DEXPERIENCE platform side.
<Event Name=" PRODUCTMirror_LocalFeedback" IsSynchronous="False" 
Priority="Normal" Type="PRODUCT" ProcessingLocations="LocalOnly" 
HasMetaData="False" HasBulkData="False" />

where,

  • Processing location: It must be declared as LocalOnly.
  • HasMeta and HasBulk: It must be set to False

Add the following entry for PRODUCTMirror_RemoteFeedback on 3DEXPERIENCE platform Gateway side:

Note: Feedback event must be declared on 3DEXPERIENCE platform side, even if there is no processing of feedback events.
<Event Name="PRODUCTMirror_RemoteFeedback" Type="PRODUCT" IsSynchronous="False" 
Priority="Normal"  ProcessingLocations="RemoteOnly" 
HasMetaData="False" HasBulkData="False">
<RemoteProcessing>
<EventHandler>
  <Name>com.ds.enovia.XPG.EventHandlers.Generic</Name> 
  <EntryPoint>null</EntryPoint> 
  </EventHandler>
  <PreProcessing /> 
  <PostProcessing />
  </RemoteProcessing>
  </Event>

Add the following entry for PRODUCTMirror_RemoteFeedback on the X-PDM Gateway side:

<Event Name=" PRODUCTMirror_RemoteFeedback" IsSynchronous="False" 
Priority="Normal" Type="PRODUCT"  ProcessingLocations="RemoteOnly" 
HasMetaData="False" HasBulkData="False" />

where,

  • Processing location: it must be declared as RemoteOnly.
  • HasMeta and HasBulk: it must be set to False.

The event-directory is deleted, when a SUCCESS or ABORT feedback event is:

  • Canceled for local to remote communication error on remote gateway of the original event.
  • Completed successfully on the local gateway of the original event.
  • Removed in any state on the local gateway of the original event.
Note: The event-directory is deleted only after the lifecycle of the original event and feedback event are completed.