As far as I know, current Web Services specifications don't support
propagating a transactional context from the client to the service at the
moment. Your choices as far as I can see are to (1) not expose to your
ultimate client the individual components of a transaction as individual web
services but only have a "main" web service that invokes an EJB that handles
the transactionality, or (2) roll some kind of solution on your own with a
compensating backout transaction if one of the called complex COBOL programs
returns a bad error code so that you can rollback everything up to that
point. You might have to reengineer the COBOL programs to write their stuff
to a temporary place that you can then commit on your own if you make it all
the way through.

Gary

-----Original Message-----
From: Kiran Kumar [mailto:kkumar@xxxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 11:38 AM
To: Gary L Peskin
Cc: Java Programming on and around the iSeries / AS400
Subject: RE: Commitment control


We are planning to use Web Sphere as application server for Java
technology and currently we are confused as how to deal with
transactionality. A series of transactions are spread across multiple
slave COBOL programs exposed as web services. We would like call set of
COBOL web services and commit if all of them are successful.

Right now, we do not have any idea as how to proceed to handle this
problem.


-----Original Message-----
From: Gary L Peskin [mailto:garyp@xxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 2:24 PM
To: Kiran Kumar
Cc: 'Java Programming on and around the iSeries / AS400'
Subject: RE: Commitment control

Kiran --

You need to be careful about the job that you're talking about. If you
expose things as web services, what container are you using? That will
determine how to deal with transactionality. I was talking about a
straight
java application.

Gary



-----Original Message-----
From: Kiran Kumar [mailto:kkumar@xxxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 7:39 AM
To: Gary L Peskin
Cc: Java Programming on and around the iSeries / AS400
Subject: RE: Commitment control


Thanks, we can use this internally for building internal application.

We are also planning to expose slave COBOL programs as web services.
If
so, how the requestor using our slave web services should manage the
commitment control.

The requestor may be calling suite of various web services. How can
he
achieve the commitment boundary across web services?



Thanks
Kiran




=======================================================================
===============
Notice: This message is intended only for use by the person or entity
to which it is addressed. Because it may contain confidential
information intended solely for the addressee, you are notified that
any disclosing, copying, downloading, distributing, or retaining of
this message, and any attached files, is prohibited and may be a
violation of state or federal law. If you received this message in
error, please notify the sender by reply mail, and delete the message
and all attached files.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].