DSXchange

...this discussion has a history that is as old as ETL and EAI tools, which is upwards of twenty years. "EAI vs ETL" used to be a big debate and discussion, and if you can find old papers, even the analysts always concluded...."the typical customer needs both." The area between t...

Now you've lost me. Request ID? Is that a column? You should have just one big column in your sequential stage that reads this file...nothing else...just one large varchar column as you suggest. Be sure you can read that file and write that file exactly "as is", and get the correct number ...

Making sure my prior entry was clear......."Nope" refers to the fact that moving to real time does not necessarily dictate a reason to use WTX instead of DataStage. You are on track with DataStage if you need regular ETL functionality (RTI and SOA issues are a whole other topic).

Ernie

Nope. Same issue there. Both tools can do "real time". ...and in a data warehousing case, it's usually "real time feeding"....not the purpose of RTI..... simply the need for sourcing data from a real time source such as MQ series, a named pipe, JMS queue, etc. As noted above, the...

You are on the right track.....but what you have successfully done here is to put the other generated values into "separate columns".....what you have to do is get the other value into "multiple rows". Create a brand new job. Create a flat file in notepad...put three rows in it: ...

Is that a file with sequential rows of xml content? ...or a tiny bit of an xml document that you are trying to read? If you have the former, then it isn't an xml source per se....it's a sequential file that has xml "content" in each row, or in a particular column. In this case, use the Seq...

I haven't been using it (istool) recently with DataStage Jobs (.dsx's have been fine for my current requirements), but like the other assets (I've been using it mostly with the new common metadata support for things like Shared Tables), I believe that there is an asset type that you have to apply in...

Not sure what you are looking for...the architecture for xmlOutput is that it takes multiple rows and turns them into multiple elements. That's how it works. There are lots of ways to tweak it, but this is the simplest, "by design" way to generate multiple repeating elements. In a lot of n...

As noted earlier, if you need/want three repeating elements, then you need to feed in three repeating "rows". You need to have three rows...one for your Service type, one for your "subtype" and one for your bundled ID...... try it with a simple little flat file first....put each ...

That's the first time I've heard that comment. Interesting. I have not found that to be true in my usage of it, but perhaps there are things I didn't review during several projects in the past several years using MapStage in combination with WTX or using WTX with RTI, which was supported in release ...

Another thing to consider is that repeating elements at the lower level are a direct reflection of "repeating rows".....so, if you have repeating rows (3 of them in this case it appears) for each of the ServiceCh elements, you will get the repeats that you are looking for. So....sometimes ...

They are both there. If you have a license for EE, Server is "in the box."

Ernie

Vincent is right.....they complement each other. While both can do basic transformations, they are designed for different purposes. WTX (WebSphere TX as it is called now) excells at moving complex hierarchical structures to "other" complex hierarchical structures. There are other things it...

One possibility is the port number. I always fully quality the domain (-dom) with the portnumber, such as mydomain:9080

Ernie

You won't be able to formally control the file "name" (it will be a fixed name with an appended numeric value), but you can certainly control the content and "when" each document will be "snapped"...... Play more with the trigger column....it is your solution.......it i...