DSXchange

It looks like we can attach a DS job as the information provider, but can we attach a Job sequence? If a web service when called, needs to run 2 jobs in a row with some notification activity as well (for exception handling) need a sequence and cannot be accomplished with one job.

Reading the manual, not sure if we CANNOT call a job sequence or is there a work around ?


thanks in advance

A job is a job is a job, be it a Server, PX or Sequence job so I would think this should be feasible as long as it is Multi-Instance. Can't say I've ever tried it myself, however... can they be "ISD enabled" or whatever it is called nowadays?

That's exactly my thought Craig and that is why i am surprised why a sequence cannot be called. However the 'ISD enabled' option seems to be available only in the jobs (job properties) and not sequences. Strange - but i wondered if there are work arounds ..

I'd be very surprised if a sequence could be ISD enabled. Any job that can be ISD enabled needs to able to listen (e.g. ISD Input stage) and send. There's nothing in a sequence that fulfils this requirement.

A regular Job, even without ISD Stages, can be published as a Service, but that support is not extended to Job Sequences....

So....... create a tiny little Server Job that has ISDInput---Transformer----ISDOutput (play with this technique first using Sequential---Transformer---Sequential until you get it right). Inside the Transformer, use the UtilityRunJob function to invoke your Job Sequence.

If you aren't doing this very often, you could just publish the Sequential---Transformer----Sequential Job as the Service and it will work fine.

Ernie

Yah, thought I recalled from my RTI days that the 'Input' stage isn't a requirement, so made a leap of faith to hoping that a Sequence could in fact be exposed. Ah well. Nice workaround, though.

It would be nice....but the alternate solution is very easy to set up. RTI had a web services implementation of the Job Control API also, but it was deprecated in ISD, probably because it wasn't used much.

Ernie

Probalby because RTI is not free product prior to 8.x; back then everbody is using DSStage Job Control API.

It's still not (in its new evolved format of ISD) free......... ; )