Should we consider SOA?
Posted: Wed Mar 22, 2006 2:20 pm
I've just come back from a discussion regarding a new project in which business users would like to execute DataStage jobs "on-demand". Although the jobs will likely be batch-oriented in their configuration (i.e. reading large volumes of data from static tables, transforming the data, then writing out to sequential files), the users may wish to run them at any time without having to contact the administrator.
One option that was raised was that of using the SOA edition of DataStage and executing the jobs via a web interface. Is this an appropriate use of the tool, or is the SOA edition intended for more of a message-based data stream? If the latter is the case, I'd appreciate any suggestions about alternative approaches!
Thanks in advance,
Peter
One option that was raised was that of using the SOA edition of DataStage and executing the jobs via a web interface. Is this an appropriate use of the tool, or is the SOA edition intended for more of a message-based data stream? If the latter is the case, I'd appreciate any suggestions about alternative approaches!
Thanks in advance,
Peter