DSXchange

MQ isn't the issue as much as "getting the file" into a single column. I'd probably use a Server Job and then just have a Folder Stage pick up the file "as is" and send as a single large column (check out the Folder "Built-in" table definition for the column called Reco...

I've started some preliminary research on this, building extensions to illustrate definitions within InfoSphere Warehouse, based on an xml export, but it is still in its infancy.

Ernie

...like everything, it depends. Many of the metadata imports to Information Server can be automated at the command line. If so, then a script can be written and that script can be triggered appropriately, for those circumstances where a background update to metadata is desired. The changes that ensu...

I'm not sure I understand the issue entirely, but it's possible that you have a CRLF in your data somewhere that the sequential stage is seeing. Follow some of the tips I have here: www.dsrealtime.com and try using the External Source Stage to read the location of the file, instead of using the Seq ...

The log is like any other DS job. Normal Job log. It's possible you many not see anything in it until you stop the operation, but it's the regular log. As for not seeing anything in your db target, some things to look for: a) make any links that branch to your isdOutput last in order, if you happen ...

There are MANY factors that go into this.....far too many than I could possibly list here. At a "very" general level, though, you should be encouraged to start using the new XML Stage --- ultimately, it is the direction for DataStage and QualityStage and XML. It does things that the xmlInp...

....share some more of your requirements... ......even without applying the patch, you have the included xmlInput and xmlOutput stages, for reading and writing xml respectively. There are significant enhancements in the 8.5 functionality that you might want to take advantage of, depending on your ne...

Absolutely. Sometimes it can get a bit tricky as to how the schema is specified, but yes, it can be done, with the new xml stage in 8.5 or with the prior xmlInput Stage in 8.5 or earlier.

Ernie

How is it not a dsXchange item? They are using ds to build xml..... isn't that a good thing? :) .....hard to say exactly what your issue is, but put the "key" on an element (column) that is on the lowest level repeating node. It's usually and incorrect position of the "key" [it d...

The best solution for "some data" (not xml) is to use JavaPack. Code your own HTTP retrieval and then parse it as you wish and write it to an output link.

Ernie

Yep.... agree with the all the points... Ultimately, you need all the pieces to "talk" to the JMS provider in question. So, at best, find someone who has already authored a connection to that system via Java..... getting it into DataStage is usually the easy part. The connection factory an...

look at the various functions in the BASIC transformer...... it's been awhile since I've done it, but probably multiple iterations of Field, using your element and it's start/end tags as a delimeter, should let you pull the required pieces surrounding the unwanted elemnent and then reconcatenate the...

Cool. Glad it worked...... ..and I wish we had a way to migrate those settings more directly, and a few more defaults....but once you get the hang of it...

Ernie

Ok.... you just need some additional processing after you parse the xml. First, from an xml perspective, this isn't really "two attributes with different values"....it's "two elements", each with an attribute that has a value. That's an important distinction, because the simplest...

...the other point I may have not made clear is that you have to use specific method names and use the javaApi that we provide with JavaPack...it contains the specific read() and write() methods that you will use to get or put data onto specific links within a DS Job.

Ernie