Originally posted by: jvanboga
I did see the two elements defined in your type tree
<AccountId>WSAPI</AccountId>
<ObjId>77777777</ObjId>
The trace file indicates that the map could not find your data error message "INPUT 1 exists (322 bytes) but has no content." Looks like the data does not match the type tree definition so the map doesn't recognise your data. Below is the trace file related to the input:
Level 0: Offset 0, len 0, comp 1 of 0, #1, DI 00000001:)
Data at offset 0 ('<?xml version="1...') does not match INITIATOR '<OWSP><<IGNORE...><NULL>SearchRequest'
of TYPE X'0004' (ElemDecl SearchRequest Element XSD).
INPUT 1 exists (322 bytes) but has no content.
End of Validation messages for INPUT CARD 1.
It looks like your xml based tree is looking for '<optional white space><<IGNORE...><NULL>SearchRequest' but it finds '<?xml version=...'. I did not see where the tree had accounted for "<?xml version="1.0" encoding="UTF-8"?>". I could have just missed it. As a matter of presonal preference, I generally stay away from using 8.2 and above when I can. So someone that is more used to navigating the Eclypse version of the tool may see it when I didn't.
#IBMSterlingTransformationExtender#DataExchange#IBM-Websphere-Transformation-Extender