Using an XQuery endpoint to filter messages - 7.3

Messaging Endpoint (Mediation)

Version
7.3
Language
English (United States)
Product
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Routing components (Mediation) > Messaging Endpoint components (Mediation)
Data Quality and Preparation > Third-party systems > Routing components (Mediation) > Messaging Endpoint components (Mediation)
Design and Development > Third-party systems > Routing components (Mediation) > Messaging Endpoint components (Mediation)

This scenario applies only to Talend Open Studio for ESB, Talend ESB, Talend Data Services Platform, Talend MDM Platform, Talend Real Time Big Data Platform, and Talend Data Fabric.

For more technologies supported by Talend, see Talend Mediation Components.

In this scenario, we will use a cMessagingEndpoint component to call a Route Resource as an XQuery parser to extract messages from the local file system.

The following sample XML file is used in this scenario:

<people>
  <person id="8">
    <firstName>Ellen</firstName>
    <lastName>Ripley</lastName>
    <city>Washington</city>
  </person>  
  <person id="9">
    <firstName>Peter</firstName>
    <lastName>Green</lastName>
    <city>London</city>
  </person>
</people>