Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home
home : products : HP web services transactions

HP web services transactions


HP middleware

» encore
» products
» HP web services platform
» HP web services registry
» HP web services transactions
» HP application server
» HP-AS resilient edition
» rich media
» HP message service
» core services framework
» HP mbuilder
» HPJmeter
» HP process manager
» total-e-transactions
» total-e-mobile
» total-e-syndication
» total-e-server
» download
» support
» maintenance packs
» documentation
» training
» HP middleware ISVs
» news
» events
» about HP middleware
» web site feedback
» help

Encore Program Overview

Thank you for your interest in HP Middleware. The Middleware product suite has been withdrawn from marketing, is now handled under the HP Software Services Encore Program and is no longer available for download from this location. These products are obsolete and any reference to J2EE compatibility, compliance, or relationship to Sun whatsoever is no longer applicable. If you have a Middleware requirement and need assistance, please feel free to contact your local HP sales representative or HP software business partner.

Today’s transaction servers operate behind corporate firewalls and have had almost total control over the resources that participate in a transaction. Every participant within a transaction either fully commits or fully rolls back in unison and dissenting participants aren’t tolerated. These ACID (atomic, consistent, isolated, and durable) transactions are tightly coupled and occur between trusted systems over very short durations of time. Although extremely reliable, classic ACID transactions are not suitable for loosely coupled environments such as Web services.

In a Web services environment, transactions will be complex, involve many parties, span multiple organizations, and potentially last for hours or days. Additionally, unlike atomic transactions, participants in a business-to-business transaction may be unwilling or unable to lock any underlying resources exclusively or indefinitely. Doing so could introduce possible issues such as denial of service attacks and the loss of business assoicated from such attacks. The culmination of these requirements rule out the use of traditional atomic transactions for Web services transactions.


This product is no longer available for download

More information

» spec sheet (87KB .pdf)
» implementing business transaction on teh web - white paper (88KB .pdf)
» listserv support
Encore Program Information

Giga report

Giga Information Group answers the question: What is a long-running transaction, and how does it relate to Web Services? Giga explains the need for Business Transaction Protocol (BTP) and the architecture and functionality required for Transactional Web services. This architecture maps closely to, and validates, HP Web Services Transactioning (HP WST) - the first commerical implementation of BTP.

» mission critical web services plan for long running transactions (160KB.pdf)
hp web services transactions 1.0, technology preview

HP Web Services Transactions (HP-WST) is the industry’s first implementation based on OASIS' Business Transaction Protocol (BTP) and delivers end-to-end transactional integrity over the Web that reflect real world business protocols. HP-WST enables Web services to reliably transact:

  • outside the firewall
  • among many parties, spanning many different organizations
  • in loosely-coupled environments
  • over long durations of time (from seconds to weeks)
  • without requiring that underlying resources be dedicated
Printable version
Privacy statement Using this site means you accept its terms
© 2005 Hewlett-Packard Development Company, L.P.