DSXchange

Not in the current WSTransformer. It is designed to handle single row, single input/output request/response services without complex bodies (the body must be a relational set of identical rows and columns).

Ernie

Some questions for further detail and more discussion.... a) ISD application? b) Server or EE Jobs? c) Always on? How many of them? (Jobs with wISDInput Stages).. d) How complicated are the jobs...(average number of stages) That should help us get started with things to review and check out. Ernie

It's not particularly easy, but it can be done....try these steps: a) be sure that the service WORKS PERFECTLY with a single row. That will ensure that the "plumbing" is working as you expect and that the service behaves as you would expect, only needing an array of data for better efficie...

You have to do a formal install of the MQPlugin and when you do, select that you want to use the MQ Client method of connectivity. I'll see if I can find a document that describes an after-initial-install of the Plugin....your support provider should know also.

Ernie

In 8.x you should see two options for MQ...the MQ Plugin and the MQ Connector..... it sounds like you may be trying the Plugin? Not sure exactly what your issue is, but it will be important to find out what choices were made at install time. In 8.x there is a dialog during the install that asks if y...

not sure how one "moves" the thread, but in the meantime, if you are succesfully parsing out the attribute and element, it is unlikely that it's the XMLInput Stage that is causing your data to be on two lines. Generally, an attribute and element value like this will all be on the same row....

Yes. Please elaborate. There certainly are adjustments when going from 7.x to 8.x, but in most cases, 8.0.1 to 8.1 has been a relief.

Ernie

Hi Craig.......in examples I've seen over the years, CDATA treatment is "sloppy"...meaning sporadic and that people seem to interpret it's meaning differently.... I've seen all kinds of stuff in CDATA...binary characters, etc. ......although less often than several years ago. Seems more ap...

you might explore pure xslt and include it in the Stage.

For something like this, I'd do it in an upstream Derivation. Evaluate for isnull() and then create your string separately for this particular element. That way you have absolutely the most explicit control of the logic and the result. If necessary, use Data Element of "XML" in the input l...

In your existing result, the element "Test" is a child of the other.....that's a direct reflection of the xpath..... sounds like you have .../text/text() at the end of your xpath and you are using aggregate...... is that what you want? If not, don't have it nested in the xpath (in the Desc...

There's a bigger issue.

Who (or what application) cares? ...and if they do, teach them (or it) that they are wrong. Both ending tags are acceptable per the standard and any tool that can't read it with a fully closing tag needs to be updated (or shot).

Ernie

I thought it was already there at 7.5.1, but I can't remember back that far....there was a time when it was a separate install.....check again, but ultimately you may have to contact your support provider. It won't cost anything, but it's possible that 7.5.1 still required it as a separate install.

Can't be sure exactly, but can suggest some things to try: a) add Jour_ouverture as an actual column on the output link. Give it a unique value (such as a counter from a prior Transformer or such)...it may not make sense for your ultimate solution, but it may point to where the problem might be. b) ...

Keep in mind that you aren't just calling any java class --- you are effectively "integrating" that class into the row by row processing performed by the DataStage Job..... Use the Java Transformer when you want the opportunity to make a call or implement some bit of java code for each row...