DSXchange

Never seen one.....is it in a standard format? ...like cwm or xmi or such? If so, it "might" work (depends on how close it is to the standard) with the Import/Export Manager......is there a chance that the Toad tooling exports in another tool's format, such as PowerDesigner or ERwin? Ernie

The most powerful way is via xml. Assign a couple of assets manually...then export via xml... look at the document. You will see that the assigned assets (whatever they are...columns, tables, etc.) appear in a grouping underneath each term within the xml structure. I'm working on a DataStage Job to ...

send the row into the xmlOutput Stage... for this tiny set of data, try using this in the Description properties of the three columns on the "input" link of the xmlOutput Stage... /myXML/col1/text() /myXML/col2/text() /myXML/myGroup/col3/text() select "aggregate" as your option. ...

That's a pretty ugly xml body. There's very little formal structure to it, except maybe the "order" of the elements. The easiest thing to do is to have the UI change it's requirement and conform to "your" WSDL from ISD....one that defines the first address uniquely from the secon...

Yes....but.........it's going to depend on what you are doing with the xml downstream.....if you run it in parallel, you could put "chunks" of xml on the output link, and then re-combine them later somehow...but you will then be responsible for the header, etc of the document.

Ernie

As noted above, I'd suggest experimenting with Actional Diagnostics or perhaps SOAP UI, and also test from other client "machines" in your network, in case there are network issues or other such blocks..... Also...how much data are you thinking about? The numbers we are talking about here ...

Hard to say. a) make sure that Folder is doing what you want it to. Are you using the default "builtIn" table defintion for the output link of the Folder Stage? b) send the columns from folder thru a transformer and then send the filename to a file. make sure it looks good. c) in the xmlIn...

a) the new xml stage lives and breathes on xsd's. So yes...but there are many considerations regarding a move to 8.5. This alone wouldn't be a good enough reason, especially if your ultimate goal is just reading. b) Not sure what you mean here. Are you autochecking only for individual nodes? You sti...

Try from other clients. I've never seen a situation where rows are dropped by ISD. I've had client tools blow up because there is no buffering in ISD (ie...it sends everything), but always sends all the data. I can't be sure what's happening in your environment, but I'd start to poke around elsewher...

Yeah..that would have been nice. You may just need to do what many pioneers have done over the years......parse the dsx itself.

Ernie

I haven't seen that creating an impact, but I'm not surprised. I had lots of issues in 8.0 and 8.1 with regular ds logs not showing up based on which way I had that setting...might be worth a support call.

Ernie

A couple of thoughts here... a) the importer prior to 8.5 understands a lot of xsd, but doesn't handle all of the constructs. b) independent mapping of the individual details of letterbody will likely be necessary... c) never use auto-check. It doesn't understand the hierarchy, which is very critica...

reading your first post again....what do you mean by "in the web page" ? are you using a mashup tool and the REST binding? If you are using the REST binding, then try running the service directly from the address line of your browser....something like: http://yourserver:9080/wisd-rest/your...

That's a pretty big payload for a SOAP envelope.

You mentioned SOAP and XML..... did you mean "SOAP over HTTP?"

What client tool are you using?

Ernie

There is more to do per my post above....

What happened when you design (and publish) a new Job that sends the data from the new target flat file, into ISDoutput ? [no oracle stages].

What client tool are you using to test? I suggest Actional Diagnostics or SOAPUI.

Ernie