DSXchange

Hi All,

Could you'll please explain regarding the Web Services Client/Transformer, at what would be the purpose of using it.

I have a current requiremnt, were there would be a set of WSDL's used to notify Data Stage of change and then if some thing has changed then would need to use Query which is again a WSDL function to retrive the data.

Could someone give a brief overview of how this could be achieved ?

Any suggestion are welcome !!!

Regards
M

Hi KeepTrying...

To answer your first question, the Web Services Stages (WSClient and WSTransformer) are used to allow DataStage to be a SOAP client. This means that DataStage will be able to, during a job, call out to a Web Service (somewhere) that is performing an action. The WSTransformer, like a regular transformer, works on a row by row basis. The WSClient Stages are more "one timers", as a source or target.

However, your second question sounds like it might be the other way around --- that some other application or function wants to invoke a WSDL to notify DataStage of something? That would be more like WISD/RTI, where DataStage becomes the Web Service.

Then again, in your Query example, that could be a perfect situation for WSClient Stage, where DS would invoke that service to retrieve data.

In your example, who is the caller and who is the callee?

Ernie

Hi Ernie ,

Thank you for the details, We are supposed to design a Integration Middleware using Data Stage i.e., There are two applications which could be the Source and Target Systems or Vice Versa.

An example is : When there is a Change in one of the applications this would notify Data Stage using a wsdl function which would be exposed by Data Stage and then the Application would notify Data Stage and then we would need to use the Query fucntion (wsdl function) to retireve the rows that have been changed and do the necessary transformation to be updated in the other Application.

Could you or anyone please advice on the above.

With Regards
M

Sorry to not post anything helpful here, but Ernie - do these components now ship with the 8.x product or are they still a separate purchase?

M - do you actually have these components (and thus the accompanying documentation) or are you just asking about them to see if they would help?

chulett wrote:Sorry to not post anything helpful here, but Ernie - do these components now ship with the 8.x product or are they still a separate purchase?

M - do you actually have these components (and thus the accompanying documentation) or are you just asking about them to see if they would help?

Hi Craig,
These two stages are integrated with datastage 8.0.1 for Unix
under real time category.

don't know much about 8.0

regards

...the Web Services Stages are now included by default with 8.x.... but to "expose" DataStage Jobs as a Service (and have a WSDL that defines it) requires RTI/WISD....

The two are "related" technologies, but vastly different in what they represent and perform for you. WSPack lets DS access other Web Services, and consume a WSDL that you provide ...while RTI/WISD lets DataStage "be" the Web Service and it generates WSDL for you.

Ernie

Thanks again to all,

Craig - Yes, the customer has currently installed Information Server v8.0.1 on a Windows 2003 box and they have Web Service Client/Transformer in their palatte.

Erine - Could you please explain how and what needs to done to enable a RTI/WISD scenario? This would be important for me as both the Source and Target have WSDLs which I need to use to extarct and pass for either an update or insert when a transactional data is changed (cs would be vice versa).

Any inputs would be helpful.

Regards
M

When he said RTI/WISD was required to expose an ETL job as a service, he means you'll need to purchase that optional component. If all you are doing is calling a service, then you've got what you need.

Indeed. WISD is a chargeable item.... it is a rich infrastructure that allows you not only to publish DataStage and QualityStage functionality as a "Service" but fully supporting Web Services and EJB (java based) mechanisms for invocation, and a workload balancing and failover architecture....that sounds like "marketing-speak," but the technology has been GA for four years and is providing some sites with some very cool benefits, enabling re-use of their DataStage assets as well as allowing DS developers to get right into the mix of SOA and portal application development.

Ernie