DSXchange

Here are some things to try.... Increase the APT_DEFAULT_TRANSPORT_BLOCK_SIZE. I have had success with that when needing a larger size to support XML stages, albeit not with the MQ Connector.... Try a Server Job. It may not be what you need, but it might offer clues as to the issue, as Server someti...

It can be edited manually after import...I've done it many times...but I'm not sure if it can be parameterized....perhaps it gets compiled into the job......

Ernie

....using JavaPack means more than just writing a stand alone class....sorry I wasn't more explicit. You write your class according to the api as defined for JavaPack (it's not hard to adapt an existing one). Search thru the forum here...there are a ton of threads on it...I also have a sample at my ...

The method I use is to make row number a formal element inside the xml ....give it xpath and everything. Have it be one of the sub-elements in the lower node. Then.....it depends on what your xml is for.....if it must match a valid xsd, then push the xml to a transformer as noted above and get rid o...

I should have been more explicit..... if you are sending xml content "out" of xmlOutput Stage to a downstream stage, place just ONE single giant column on your output link, with a single "/" in the Description property. Your entire content will then proceed for further transforma...

I've seen this before, and it seems to occur whenever all the other columns are duplicate. One easy way I've resolved it is to create a unique counter as you have done and then remove it in a follow-up Transformer right after XMLOutput.

Ernie

I'll need a few more details, such as the types of Stages you are using, etc.... ...but first a few questions... a) what release are you on? 8.0? 8.1? 8.1.1? b) from where are you invoking lineage? (from within Cognos? from within the Metadata Workbench? What object are you "sitting on" wh...

...hmm.. Hard to say...you'd need to know exactly how the author of the service interprets nulls..... one "formal" way to do it is to put in the accepted standard null attribute, and see if the service accepts it. What test tool are you using? Many of them will let you manually play with t...

Wow. Nice to have an open "box" of tools to work with...... Lots of things you could start adding to your solutions..... ...get yourself up onto 8.1 of Information Server, which includes DataStage, QualityStage, Information Analyzer, Business Glossary, Metadata Workbench and FastTrack, and...

...it is still a chargeable item....not exactly sure, but typically it is licensed today as ISD (Information Services Director), but you would receive RTI if you are on an old release. ...you have to INSTALL DataStage with the RTI license code. If DS is already installed without it, you will need to...

If the queue technology is not WebSphere MQ, then you will need to use JMS via your own class with JavaPack. ...not difficult, but you will need to have some java expertise, especially that knows the ins and outs of JMS because of your interest in transaction logic.... With the MQ Connector, you can...

JavaPack is there....we don't call it "JavaPack" so much anymore because it is no longer a chargeable item. Look for the Java Transformer and Java Client Stages in your palette... Doc is in lots of places also, and with lots of entries here in this forum, and I have some samples at my blog...

Ah yes....it was a fun time in the early web-bubble days. The sessionizer was the most interesting.......thought it was going to make a comeback, but alas, not enough demand...into the bin with other cool stuff from the past like the Job Edit API.... ; )

Ernie

I've seen it done with JavaPack and long ago with the old Perl Stage.

Today, write a java class that can get the document via HTTP and then you can parse it as appropriate and send the rows down an output link.

Ernie

The overall subject of migration is quite complex, although more specifically, moving OMD (Operational Metadata) is fairly straightforward.... ...the key is being sure that you have also moved all of the artifacts that are mentioned or named in that OMD. OMD is stored in an xml document in the ASBNo...