DSXchange

Maybe not, Craig....let's find out first.... What exactly are working on and trying to accomplish? ISD pre-supposes that you need/want a web service...and as such, would call that web service via the WSTransformer Stage..... ....but doing ETL with Web Services is not a particularly good use case ---...

array from what? Information Services Director? ...or something else?

Ernie

That's how it was designed...and probably because there isn't much need for it. An always on service is infinitely faster (milliseconds as opposed to seconds) than a simplistic Job that only has ISDOutput. Further, an "always on" job is shared by anyone and everyone that invokes it......an...

A very good possibility is that your xsd is telling DataStage that there is only one row. Look at the "list" for the node in question. Depending on how you created your xsd, it is possible that the xsd came out without a maxOccurs=unbounded. [each xsd generation tool works differently --- ...

play with setting minimum instances to zero and a fairly small timeout value....then it's theoretically always on, but starts with the first incoming request, and if never called again, will eventually shut down that instance.

Ernie

Could be a lot of things....there have been problems with the import process, so it might depend on your release and your environment. Here are some things to try... a) download a soap testing tool such as SOAP ui (there are many on the web...I like SOAPui and Actional's SOAP Tester the best)....see...

The best way to do this is to instead set this up as an "always on" job that uses ISD input Stage....and then group that into an array. The WSDL will reflect an array and ISD at run time will accept multiple rows being input.

Ernie

There are lots of resources to get you started.....Look thru the forum here, get a copy of the xml redbook, look on developerWorks..... try other xsd's also.

Ernie

hmm. If you aren't seeing the Connector, then it probably is because you need to set up an additional Metadata Interchange Server -- one with no port because it is just going to find it at your DataStage Engine machine (which it usually knows the location). Most linux/unix sites will have "two&...

While it may create other complications for you (not sure what you are doing in the rest of your job), it might be worth trying this in a Server Job with the MQ Plugin..... I haven't dug into the return codes that are made available to the link in years, but it's possible that the REJECTEDCODE at an...

...that capability is not available for Information Server in a Windows environment.

Ernie

The port address is visible at the advanced tab.... for future reference, make it a job parameter so that you can change the value at run time.

Ernie

On the contrary. RCP works fine with Meta Data Workbench, but you have to understand the rules for lineage and create objects for each of your sources and targets. All more detail than can be outlined in one thread. Of all things to consider for success with DataStage and Meta Data Workbench, the mo...

Craig is right..there probably aren't enough people exercising it heavily enough yet to have experiencde this. I've been using the WLM off and on since early beta of 9.1 and haven't seen any particular issues. I'd look for some patterns. Is it only when you enable it, and then it immediately causes ...

...and also doing a test with a class that merely does a simple transformation, such as raising a string column's value to upper case....then compare that.

Ernie