DSXchange

Well, abnormal termination is different than zero rows. See if you have another service. I just did one and it worked fine. WSClient to a Transformer (just because) to a Sequential. Entirely void input for the WSDL. Did you import the WSDL successfully? Any errors when you chose the Operation? You m...

You aren't using the Trace I discussed up above. When you run the job, see if you have a Trace tab in the run dialog. You noted that this is a Server Job, so it should be there. Highlight the Stage on the left and all four boxes on the right. Review the tracing in the ds director log in detail...at ...

Not sure... a void input message for the Operation would certainly seem legitimate, and I recall doing some like this many years ago, but not in recent releases. Do you get "0" rows on the link, or just don't see anything in your target sequential file? You might want to try some things to...

Ok, then...as expected. You have a strategy then (above). If someone wants to move it back to the regular forum, that would make sense too...

Ernie

Are we talking about ISD Jobs being deployed as Web Services? (if so, then placement here in this forum makes sense)...or are we talking about Jobs that use the Web Services Pack (WSClient and/or WSTransformer Stages)? ...it "sounds" like the latter, but please confirm..... It sounds like ...

Thanks everyone! Great feedback....

Ernie

Thanks Ray...anyone else?

Ernie

Sounds like the "entire string" containing xml is null? I suspect that the Stage will see that as invalid, because it will attempt to apply xpath to "that string" that is coming in. Probably best to go to a transformer if you can, upstream, and split out the rows that have NULL x...

Hi Everyone... I'm in the midst of a research project and could use your help. How often do you use Job Parameters such as #DSHostName#, #DSProjectName#, #DSJobName#, and how? Typically I see it for defining things like flat files and datasets, which is particularly important for this line of resear...

The documentation describes this nicely, but in brief, it allows you to have a Job whose source and target are a real-time application....perhaps a user who is entering a name, and needs to have that name parsed and standardized and its address checked for validity. It's a one row, request/response ...

I've done the "naughty" thing and create services directly against xmeta to read the primary Term table and send me RSS notifications (using ISD :) )......but another way might be to have a REST API polling application looking at Term details, periodically walking thru the glossary. Ernie

I haven't tried exactly this, Ray, but in 8.7 you can limit access to Categories by user, and then establish Workflow and simply never approve or authorize new categories that an Author might accidentally create (ie...they'll stay in draft). ...then remove them from Draft.

Ernie

Not sure. You might try passing the entire payload as a single string (just put one column on the output link, make it a large varchar and put a single / in the description) and then pass that into an xmlInput Stage, where you can put the detailed metadata that is "currently" on your Web S...

As Ray notes, check the design...what is specific and interesting about that particular column? What is returned or provided by it? It is a strange datatype? Is it ever null, etc....

Ernie

It's not that you can't use the Join --- the issue is that you can't expect the data used in the Join Stage to be refreshed.... The Join is designed for best performance in a batch operation...it will pull all the rows into memory. It doesn't go "back" to the database again for the entire ...