DSXchange

Hi Satish... What is it that you are trying to do? Using MQ to receive XML is a perfect pattern for using DataStage. MQ receives a payload that contains an entire XML document, and then sends it to an XMLInput Stage so that it can be parsed out into individual tables (each "link" getting a...

Yes...that's probably the one. I may hav made minor changes to it, but it's pretty much the same.

Drop me an email (eostic@us.ibm.com) and I can send you a .dsx with some sample jobs in it that illustrate most of the "basic" patterns that are used for DataStage Jobs published as web services.

Ernie

I like Ray's thoughts --- it's certainly a good possibility --- and I also seem to remember something like this coming up a long time ago, and it had something to do with either the axis engine underneath WSPack, or the JVM... Some googling of "axis SOAP daylight savings" shows some intere...

Thx. Flattery will get you everywhere. :) Trust me I'll be coming your way for deep "down and dirty" pure DataStage things... On your xml application, congrats that it's going to production. Sounds like a cool solution. How complex was the hierarchy? Did you resort to multiple XMLOutput St...

Now that's a new acronym that I like :) ...thanks for the warm welcome, Craig..... which level of the forum should we talk about XML? Also...there are some other good tools out that act as dynamic SOAP clients, or help generate code, and I've heard that even a lot of the BI tools are (finally) suppo...

Old topic, but interesting subject. RTI has several tools for achieving scalability and failover. As Ray notes, you can set up "n" instances of a job/Operation at one particular DS Server, thus having a set of "always on" jobs waiting to handle incoming requests. Secondly, you ca...

This is a very old entry, but this question comes up all the time, so I figured it was worth addressing. The MQ Series stage "listens" for new messages on a message queue, which means that the job (by default) will run forever, "waiting" for new messages to arrive. There are, of ...

Did you ever come up with a solution here? From your description, it sounds less like a problem for RTI to solve and more like a task for something simple like FTP...can you be more descriptive (if it's still an issue).

Ernie

Just about any tool on the market that can handle WSDL 1.1 documents will be able to handle an RTI based Service. A really good one for test purposes is SOAPscope from a company called Mindreef (www.mindreef.com). In .NET, the tooling is pretty much ready out-of-the-box for importing WSDL, while in ...