Analyzing different protocols for E-business

1. Supervisors Analyzing different protocols for E-business • Prof. Dr. Ezzatabd El TawabKorany • Dr. Saleh Abdel ShachourEl Shehaby FatmaSayed Gad Elrab

2. Main topics • What is the E-business • E-business technology Phases • E-business process properties • E-business process technology (WS) • Web Service transaction protocols • Disadvantage WS transaction protocols • Transaction properties ACID • Disadvantage ACID • Problems • Literature review • Contributions

3. What is the E-business • E-business is electronically business processes like electronic purchasing ,supply chain management, processing orders electronically, handling customer service, and cooperating with business partners.

4. E-business technology phases

5. E-business process properties • Loosely coupled • long-running processes • components that do not share data ,location, or administration

6. E-business process technology (WS) • A Web service (WS) is mechanism that expose any process that can be integrated into external systems through valid XML documents over Internet protocols. • Organization strive to make by WS their IT resources more effective (performance issue) • Web services environment does not have full control over all the resources. (performance issue) • Web services can compose other Web services in a transactional manner. • Composite Web services require Transactional Properties (TP) so that the overall consistency is ensured. • Invalid Web services is a critical issue . (performance issue)

7. E-business process technology (WS) Count

8. Web Service transaction protocols • WS-T(web service transaction (coordination ,Business activity). • THP(tentative-hold protocol ). • BTP(Business transaction protocol).

9. Disadvantage WS transaction protocols • Mainly based on the database transaction models such as ACID properties and extended advanced transaction models. • They use the Two-Phase Commit (2PC) protocol as underlying protocol to coordinate activities. This lead to lock recourses to protected and ensure data • They do roll back everything even if the first transaction is failing after a lengthy timeout

10. Transaction properties ACID • Atomicity :transaction must either appear to execute in its entirety or not at all (ok all or not all ) • Consistency :-demands that a transaction must transform a data from one consistent state to another consistent state. and guarantees integrity. • Isolation:- requires that an active transaction cannot expose its intermediate results to other concurrently running ,not make its updates visible to other transactions until it is committed.Durability: Once a transaction commits, the committed changes must never be lost in the event of any failure.

11. Disadvantage ACID • ACID properties are implemented using various commit protocols such as two-phase commit (2PC) and its variants presumed abort (PA), and presumed commit (PC) protocols. • These are useful in ensuring data consistency and correctness of transactions they result in serious performance problems. • ACID properties are based on the strict atomicity and isolation policywhich requires that transactions can not share its data with other concurrently running transactions until it is completed this lead transaction to poor performance, as transactions have to wait for each other until they are completed.

12. Problems • consistent outcome and correct execution:- Most business-to-business applications require transactional support in order to guarantee consistent outcome and correct execution (censuses problem ). • loosely-coupled and don`t (ACID)loosely-coupled systems, and components that do not share data, location, or administration. It is therefore difficult to incorporate atomic transactions(ACID)within such architectures (lock resources problem ). • long-running systems and lock recourse :With long-running systems where exclusively locking resources is impossible or impractical. (lock resources problem ).

13. Literature review • Muhammad Younas (2006)et.al,” An Efficient Transaction Commit Protocol for Composite Web Services” describe new transaction properties (Semantic Atomicity, Consistency, Resiliency, Durability)and develop a protocol TCP4CWS (Transaction Commit Protocol for Composite Web Services).for implementing this properties in the composite web services(performance issue in case of failure). • An Liu(2009)et,al.” FACTS: A Framework for Fault Tolerant Composition of Transactional Web Services”. Ignore, Notify, Skip, Retry, RetryUntil, Alternate, Replicate, Wait (censuses aoutcome issue in some cases)

14. Contribution

15. Results

16. Description • Build frame work in UDDI server to handle transaction between consumer and provider • New solution ensure atomicity this lead to consuse outcome of composite web service like travel agent. • New solution try to Reduce time of lock resource in case of failure participant . • New solution don`t supposed coordinator failure or crash so it built in UDDI server . • New solution let composite web service to decide second step in case of failure participants (Compensation, abort…etc) • New solution let composite web service , participants to recover them self In their own way.

17. Not include in new solution • New solution not cover work flow long running process that wait for days to approve (lock resources ).

18. New Web service structure

20. New WS structure Steps.