Configuring the tXMLMap components in the input flow - 7.0

ESB SOAP

author
Talend Documentation Team
EnrichVersion
7.0
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance > Third-party systems > ESB components > ESB SOAP components
Data Quality and Preparation > Third-party systems > ESB components > ESB SOAP components
Design and Development > Third-party systems > ESB components > ESB SOAP components
EnrichPlatform
Talend Studio

About this task

Talend data integration uses schemas based on rows and columns since it has roots in relational data warehouse integration. But SOAP messages uses the XML format. XML is hierarchical and supports richer structure than rows or columns. So we need the tXMLMap to convert from the relational row/column structure to the schema expected by the SOAP service.

Procedure

  1. In the design workspace, double-click the first tXMLMap component to open the Map Editor.
  2. In the output table, right-click the root node and select Rename from the contextual menu. Enter IsValidEmail in the dialog box that appears.
  3. Right-click the IsValidEmail node and select Set A Namespace from the contextual menu. Enter http://www.webservicex.net in the dialog box that appears.
  4. Right-click the IsValidEmail node again and select Create Sub-Element from the contextual menu. Enter Email in the dialog box that appears.
  5. Right-click the Email node and select As loop element from the contextual menu.
  6. Click the Email node in the input table and drop it to the Expression column in the row of the Email node in the output table.
  7. Click OK to validate the mapping and close the Map Editor.
  8. Configure the other tXMLMap in the same way. Add a row of Document type to the output table and name it header. Create two sub-elements to it, id and company. Map the id and the company nodes in the input table to the corresponding nodes in the output table.