On the workspace, double click tXMLMap to open its editor.
At this moment, the editor should look like:
In the main row table of the input flow side (left), right-click the column name
payload and from the contextual menu, select Import from
Repository. Then the Metadatas wizard is
opened.
Expand the File XML node in this wizard, select the schema
of the request side and click OK to validate this selection.
In this example, the schema is getAirportInformationByISOCountryCode.
Do the same to import the hierarchical schema for the response side (right). In
this example, this schema is
getAirportInformationByISOCountryCodeResponse.
Then to create the join to the lookup data, click the CountryAbbrviation
node in the main row of the input side (left), hold and drop it onto the
Exp.key column of the lookup flow, corresponding to the
id row.
On the table representing the lookup flow, click the wrench icon on the up-right
corner to open the setting panel.
Set Lookup Model as Reload at each
row, Match Model as All
matches and Join Model as Inner
join.
Do the same to open the setting panel on the output side (right) and set the
All in one option as true. This
ensures that only one response is returned every time when one request is sent, as,
otherwise, the airport data from the given database may provide several airports,
thus several responses, to each country code that you send as one request.
Click the name row in the lookup flow (left), hold and drop it onto the
Expression column corresponding to the
tns:getAirportInformationByISOCountryCodeResult node in the XML tree view
of the output flow (airport_response in this example).
Then your tXMLMap editor should look like:
Information noteNote:
In the real-world practice, you can as well add hierarchical data for lookup.
Click OK to close the editor and validate this
configuration.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!