DSXchange

Tell us more about the machine. How many CPUs? How much memory? It will be interesting also to know the speed of your CPUs. Thiry six parallel Jobs running concurrently? How complex are the jobs? As noted above, there are MANY variables, but this could potentially be a huge number of processes --- e...

There is nothing automatic here. If you have not-null in your unhandled data, then craft an error message and send that back in your SOAP envelope in another column, with your own custom text message. That "message" column will be in the WSDL, and the java client can check that along with ...

hmm... it's been a long time since they were added in by default. I can't remember exact which point release of 7 when that was done...but if they are there, but you don't get the client side gui, that's usually easier to rectify..... I haven't looked at the names in awhile, but you probably have to...

Your existing Jobs will work fine. Be mindful of the install of v8 --- there is an MQ prompt that is for Server Jobs using the MQ Plugin ...it asks if you want to install the plugin for MQ and also asks if you are using MQ Server or Client.... since you are coming from 7.x, we will assume that you a...

Not sure what your goal is. The java program can certainly look at the unhandled data and flag the address as bad on its own. Hard to say how it might correct it --- indeed that could require clerical review. Are you ultimately validating the address for actual location? Perhaps having QS perform a ...

You can get as creative as you want.... I suppose you could add such logic to the QS job....although "on the fly" fixing is not usually where I've seen standaridation and investigation being used. Exceptions are found, rules are tweaked, overrides created, and then one less exception resul...

Aren't you always sending back the response? Wouldn't your unhandled pattern appear in either a direct stan or possibly investigate result? ...regardless? (assuming the process flow is finally working).

Ernie

...missed your line about it working fine in the sample other job.... This sounds oddly like it could also be an end-of-wave problem. If it is still occuring, try this: Right before your WISDOutput put in a Transformer with two output links. Send the first output link to a flat file or Peek ....the ...

The "unable" to find jvm is 99% the env var issue as you noted, although the values of these are slightly different for every platform. Search around..there are a lot of entries in here on this topic, for both the WSTransformer as well as JavaPack. Assuming you get past that in your test j...

Tell us more. Does it abort on its own, after you have deployed it via the wisd console and before you ever invoke it? ....after a single invocation? Does the job ever get up and running? How many instances have you set inside of the WISD console......? Do you have other WISD jobs that still work? I...

You are prompted at install time whether you want "Server" or "Client" version of the MQStage...this refers to whether you will be getting a plugin that supports the MQServer API, or one that supports the MQ Client API ...it is only an issue for Server Jobs..for Server Jobs you m...

awesome post!

Could be limits on EE and/or limits on what the XMLOutput Stage can handle. Hard to say, but in this case it is probably XMLOutput, as the "collection" of rows is causing the issue, not one particular row. The XML Stages can handle somewhere between 300 and 500M, but it depends a lot on th...

Yes...7.5.2.x moved over to a more formal rdbms so that clustering could be supported......

With namespace issues it's sometimes hard to say what might be at issue. ..... first, I'd test by trying to remove the default namespace from the header [if one exists....probably is something like xmlns="http://....."] and also remove the ns1: from your xpath statements. This will at leas...