Exposing DataStage Job as Web Service

anand_chandrashekar · Post by **anand_chandrashekar** » Wed Jul 16, 2008 8:45 am

Hi all,

Some questions when DataStage exposes a job as a web service.

(1) I understand that this is a synchronous web service. However, this means that if a job runs for hours there is every chance that a connection timeout occurs. What happens to the job when the timeout occurs? Does it terminate?

(2) Is there a way to invoke a DS job asynchronously (but via standard integration components such as web services/proxy services etc.)?

Thanks,
Anand.

eostic · Post by **eostic** » Wed Jul 16, 2008 11:28 am

...all correct...two possibilities immediately come to mind...

a) build a simple Server job that, in a Transformer, uses UtilityRunJob (can remember the exact name, but its one of the sdk utility functions that you'll find in the pull down list). Use this, or a customized version of it, to start your REAL job without the wait option. Publish this little "starter" job as the service and pass (or hard code) your jobname into it.

b) 8.1 will have support for JMS binding, which can kick off jobs also...JMS inherently supports async type functionality.

Ernie

eostic · Post by **eostic** » Wed Jul 16, 2008 11:29 am

...all correct...two possibilities immediately come to mind...

a) build a simple Server job that, in a Transformer, uses UtilityRunJob (can remember the exact name, but its one of the sdk utility functions that you'll find in the pull down list). Use this, or a customized version of it, to start your REAL job without the wait option. Publish this little "starter" job as the service and pass (or hard code) your jobname into it.

b) 8.1 will have support for JMS binding, which can kick off jobs also...JMS inherently supports async type functionality.

Ernie