DSXchange

You have to "write" your own java class that reads from the JMS queue. The JavaPack doesn't just let you call "any" class/jar ....it is a bit more complex than that --- but ultimately, more powerful. Instead, it lets you directly interact with the DataStage "machinery"....

Ya got me. It "is" the same question, albeit not worded exactly the same way. You have a particular chunk of xml and are interested in knowing how to read it. It is a repeating element.... it will produce repeating rows. If you need something different, just say so. The patience of many is...

Well...the advice in my last post is "the" answer for multiple repeating nodes, regardless of whether additional searching in the forum was done or not.

Ernie

I think you asked this already in another entry...

Information Services Director "dictates" the WSDL that will be used --- the input and output message definitions in the WSDL are driven by the links that are part of the ISDinput and ISDoutput Stage... The easiest way to handle this is by having a single large varchar column on your link c...

hard to say...been too long since I've played around in a ds 7.5 environment....

You might try installing the client on another machine as a test, to see if it's something wrong with the client install.

Ernie

Spend some time reviewing many of the xml threads here in the forum. The key here is to have a separate link for each repeating "path" for which you want rows.... Create an independent table definition from the xml importer for each of those nodes. Include their common parent info. Make th...

It would be nice if it did, but on the other hand, the abstraction is important, and ultimately, you want the same Job to point (at different times) to different physical systems. DataStage only knows about "Server" (abstract string), Schema and Tablename... but WB knows about "real&q...

Did you configure your Database Alias settings? (assignment of DataStage's abstract "server" string to the host-database combination for your imported Database (Shared) Tables)....

Ernie

By the way....in the xml metadata importer, avoid the temptation to use the "auto-check" button. Instead, open up the ENTIRE tree....then traverse each straight path you have of nested repeating nodes (a separate sibling sub-node can be included on the same link with another if it doesn't ...

Hi Greg.... Good to hear from you! The individual nodes do not have to be "chunked"...(they can be, if you have reasons, as the syntax of the Stage supports it, but it is not a requirement).....each link will simply deliver the individual values, as though the elements and attributes came ...

Hi gsbrown... The key is in "what do you want to do with it"...... DataStage, like most ETL tools, can very easily tear this xml document apart, no matter how many sub-nodes, into its relational pieces. "If" you are trying to read such a document, what is the target? 99 times out...

That's up to you as the developer. In xmlOutput Stage, the xsd is an optional tool if you want to perform formal xsd validation, and optional as a way to import the metadata of an xml structure.....but the processing is your choice. If you don't want an element to appear at the lowest repeating node...

...it's the default behavior. If the field is null (using xmlOutput or 8.5 xml), the element simply does not appear.... you can optionally force it to blanks if you want, and can have blanks treated as nulls.

Ernie

No problem. Glad to be of help..... ..for anyone reading this, keep in mind that it's not just the syntax that will impact what your resulting document looks like. In this case there were "two" records at the higher level, so it had no choice but to cut another parent group. Know your data...