Platform Deployment Guide › Universal Extractor › XML Metadata Extractor › Extracted Events

Extracted Events

By default, the selection criteria specify that to be eligible for extraction, an event must:

• Match the RemoteID prefix requirement (the RemoteID is an identifier used to associate events stored on the CMS with their actual message data held in a third party archive).
• Have at least one associated trigger, issue or audit record. This ensures that only ‘significant’ events are extracted to the archive.
• Not have been previously extracted or, if it has been extracted previously:
  • It was not successfully committed (for example, because a problem prevented the XML files from being written), or
  • No acknowledgement was received from the target archive within the specified retry period, or
  • It has since been updated (for example, the expiry date has been changed), or
  • New issues have been created for that event, or its event history has been updated.

The database SP selects the events that are to be extracted. For Oracle CMSs, event selection is incorporated into the Wgn_V_UE_EventExport database view; for SQL Server CMSs, event selection is handled by a user-defined function, WgnUEExportEvents.

If you want to change the selection criteria (for example, to export all events regardless of triggers, issues and audit records), you can do this by modifying and reinstalling the UE stored procedures and database views. For guidance on reinstalling modified SPs and database views, please contact CA Technical Support.