DSXchange

An element that is "unbound" is going to help you define "one" of your output links..... So...you might have a document for a company (one single company) that has a node for "employees".... it is probably unbounded....nested in there, you might have a node for "jo...

Now, that's certainly strange. Is that also when you use our little 3 column example above with col1, col2 and col3?

Ernie

Do some searches...there are many entries that describe how this is done and entries that point to other resorources here and on the web.

Ernie

As Ray notes.....staying with MVS Edition and moving to v8 is a fully supported activity...... ...on the other hand, moving from MVS edition to an alternate platform version (such as moving MVS to Linux IIS v8) is another story --- though still conceptually do-able from a learning curve and graphica...

....the xml document is still the xml document, regardless of the xsd's (however many) needed to define it.

Define your metadata from a sample xml instance and don't look back. Your datatypes will all be varchar and 255 or similar, but so what? XML is all char anyway.

Ernie

PS....I saw this once a long time ago when I was building SOAP bodies for input into WSTransformer.... on a whim, also do a test where you add about 4 or 5 more columns (just create some dummies in a prior Transformer and give them the xpath that uses the same pattern as above). I can't remember the...

hmmm.... it looks like you have the xpath and everything correct, so it might just be an oddity in the values. There are still ways to skin this cat, but let's prove it first. What happens when the values coming in are 100% unique? (ie...where Name and City are each truly unique strings in each row)...

It's not clear at this point what the issue is. I'd first figure out why this service isn't working, fix it and then determine why perhaps the export/import has a problem. Re-deploy it (the QS job) from scratch...do you still have the problem? Deploy it instead with the SOAP binding....debugging it ...

I'm not sure I can be any more explicit than what I have up above... First, I am assuming that you have (in the example) two rows coming into the XMLOutput Stage....and you want "one row" going out. So...for example, a flat file with two rows, or a relational table with two rows and three ...

If I remember correctly, MDM server uses the EJB binding. Deploy also with SOAP over HTTP and test with a tool like SOAPscope. See if it fails in that unit test.

Ernie

Make sure you choose aggregate and not trigger, and be sure that you have a summary style node structure in your xpath.... Something like: for a link that has 3 columns: col1, col2, col3.... have xpath (the Description attribute) that has: /myRows/myRow/col1/text() /myRows/myRow/col2/text() /myRows/...

Could be an xpath issue.... Could also be an environment issue. To be sure, add an output link to the XMLOutput Stage and send the info to another I/O stage...like sequential. Put a single column on the output link, with varchar and some long length..put a single '/" in the Description property...

Can you be more explicit...it's not exactly clear what you are looking for.....

look thru the threads here...find the best practices document at Kim Duke's site..... there's a lot on creating and managing XML.....

Ernie

ISD has a project level export....

Is it pretty printing that you are looking for? ...or a truly single document? ...if it's pretty printing, follow the advice above...you shouldn't be needing to worry about it, as noted. ....but if it's a "single" xml doc, it might be an issue in the way you are specifying things.... ...fi...