DSXchange

Try it. Using this technique, it will work without append mode. When you have (say) 300 xml files in a single directory, a single Job run will read thru all of them, delivering parsed rows to your DataSet .....as though it was one big xml document.

Ernie

The questions are answered in the prior post.....but here are some further instructions.... Open your xml in the xml metadata importer (under imports...table definitions). Expand the ENTIRE tree so that you can look at all of it. For your Parent-Child node section, check ONLY the inner-most boxes fo...

This is one of those strange ones....best I can tell from searching thru various xsd sites is that the actual targetnamespace needs to exist as the initial part of a URL pair inside of the value for schemaLocation... that suggests that yours might be something like: xsd:schemaLocation="http://w...

Looking at this more closely, another issue might be the use of trigger --- are you expecting to create multiple documents? Generally speaking you will want to use the "Aggregate" option, and then specify the lowest level repeating unit (just pick one of the elements at that level) as a ke...

1) via the xmlInput Stage, you only need to describe the columns that you want to actually parse out of the xml document. Just describe the 25 that you need. ...Note that "per link", they need to be on the same nested node path...meaning parent-child-grandchild, etc. If you have another co...

...it's worth noting that (if you want to get really fancy) ISD supports some very complex constructs here --- you can ask ISD to apply xslt to the output payload, and you can also do things like capture only the HTTP header information. These are all the assignment settings that you will see for th...

I dug up an old example that illustrates the concept.... Job is this: ISDinput --- Transformer ----- ISDOutput There is one column coming from ISDinput. Call it "payload". There is one column coming from the Transformer. Call it "output". The incoming payload column is 10 charact...

I'm not surprised. I have never looked at the exact format of an xml REST response to an http GET (what your browser issues). There is likely some additional detail needed. When I do this technique with a custom SOAP payload, I often use an http or tcp trace facility to capture a whole payload with ...

? I just outlined the details.....start with database stage to xmlOutput to isdoutput --- and then use the text over http binding .....

It can be done, but not "out of the box". ETL tools are inherently based on a relational engine --- rows and columns --- so the "automated" functions generate fairly simple "flat" json and xml. So I'll say it again --- the value of using DataStage here is the use of you...

Don't allow a non ctitical requirement dictate your development. Encourage (or just tell) the receivers of the payload that they should accept the "flat" xml or json that is delivered directly by the binding --- the job and its binding will be far simpler and you will have done the team, t...

To get it to be an "always on" Job instead of a regular batch Job with only ISDoutput, send your input parameters up thru an ISDinput Stage instead of (what I am guessing you are doing at the moment) as Job Parameters. ...and then perform a lookup with a multi-row return to bring back as m...

My point here is to allow ISD to dictate the structure ....it will be in perfect JSON format, or XML if that is what you choose....and in the Job, REMOVE the xmlOutput Stage.... ...send the link DIRECTLY to the ISDOutput. You will get a simple hierarchy, albeit a nearly flat one. ...the receiver of ...

Then as noted, try publishing a simple server Job as a service......after you have fully worked out all the techniques, return code and recovery issues about invoking a Sequence from a regular batch Server Job using the DSUtilityRunJob function inside of a transformer.

Ernie

Best practice for your success: a) build the Job and publish it as REST binding with either JSON or XML format. ...both are VERY different formats, albeit similar from a tagging perspective. b) share the xsd, or share the JSON output with the callers. c) THAT becomes the standard. Don't fall into th...