Originally posted by: jdavee

Using v8.204. We have WinXP and Win7 development systems that are producing output for a UDF to XML translation.

The XML output type tree was built from an XSD supplied by the customer that imported without incident. We have other XSD imports from the same customer for other data input and output that are working fine.

With this map working OK on Win development, we compile to run on HP-UX Itanium. We run dozens of maps this way (Win development / HP-UX execution) and haven't seen this problem: the map runs successfully on HP-UX but the output is incomplete and mostly empty XML tags. Not the same as the Win output at all.

We suspect that the XSD file has become a requirement for the map to execute. Since it is on the Win systems it is used and the output is good. Our other working XML output maps do not reference "metadata" in the card properties, but this problem map does.

We cannot determine if this is in fact the problem. We also can't confirm from the documentation where the XSD would be located on the Unix server. We're running the map in Launcher and have tried setting specific paths to the metadata in the Launcher settings for the output card, but it is not having any effect.

Questions:
1. Why the difference in XSD imports to type trees with some demanding metadata and others (the ones that work on Unix) do not?

2. Why are we not getting any error messages on Unix when the data is obviously faulty?

3. Where do we put XSD metadata on the Unix side to make is accessible (assuming this will solve our problem of malformed output data)?

Thanks,
Jim
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: TarunB

Jim

In your map, have a look at the output card settings for the XML structure. Do you see a section for Name Spaces? If so, try deleting these and re-building/running your map on HP-UX.

Alternatively have you tried using the XSD directly in the map, instead of generating a tree?

Good luck,

Tarun
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: jdavee

Tarun,

No sections for Name Spaces. I exported the type tree and did a full text search on it as well and couldn't find that value except that it wasn't used.

We've made several XML output maps and always built the type tree from the XSD without incident. Still can't tell why this one map fails on Unix while OK on Windows.

We've reimported the XSD several times, rebuilt the map many times, and still can't get the Unix side to work properly.

Any other ideas on where to look?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender