Using the HTTP Binding Component

Contents

• Using the HTTP Binding Component
• About the HTTP Binding Component
• HTTP/SOAP Binding Architecture
• HTTP Binding Component Features
• HTTP Binding Component Example Scenario
• SOAP Processing
• HTTP Processing
• HTTP GET and POST Processing
• HTTP Binding Component Runtime Properties
• HTTP Binding Component Client Endpoint Properties
• Using Normalized Message Properties to Propagate Binding Context Information
• Configuring Quality of Service (QOS) Features
• Using the Tango Web Service Attributes with the HTTP Binding Component
• Configuring Web Service Attributes
• HTTP Binding Component Security
• Using Application Variables to Define Name/Value Pairs
• Using Application Configuration to Configure Connectivity Parameters
• Logging and Statistics Monitoring
• Using WS-Atomic Transaction
  • The SoapWSATCompositeApp Sample Composite Application
• Clustering Support for the HTTP Binding Component
• Common User Scenarios

Using WS-Transaction

The HTTP Binding Component is integrated with WS-Transaction, an implementation of WS-Atomic Transaction available through Tango (WSIT). WS-AtomicTransaction is a specification that defines a two phase protocol to ensure that transactions are fully completed or fully rolled back, also known as all or nothing. Depending on the transactions success, the registered transaction participants arrive at a commit or abort decision, and both participants are informed of the final result.

The SoapWSATCompositeApp Sample Composite Application

For a sample composite application that demonstrates how to use WS-Transaction with the HTTP Binding Component and the BPEL Service Engine, see HTTP BC Automic Transactions.

The sample demonstrates the following:

• Using existing Java Transaction APIs (JTA) to initiate and complete the transaction.
  
• Invocations of transacted web service operations flow transactional context from client to web service.
  
• Transactional context import from web service client to HTTP/SOAP Binding Component.
  
• Transaction propagation from the HTTP/SOAP Binding Component to the BPEL Service Engine and from the BPEL Service Engine to the HTTP/SOAP Binding Component.
  
• Transactional context flow resuming from the HTTP/SOAP Binding Component to the web service.
  
• Persistent resources updated with client-created transactions are all committed or rolled back as a single atomic transaction.
  
• After the client-side code commits or aborts the JTA transaction, the client confirms that all operations in the transaction succeeded or failed by using calls to verify methods on the transacted web service.
  

Previous
Next

This page (revision-10) was last changed on 08-May-09 15:50 PM, -0700 by rjacobus.
This page was created on 12-Sep-08 13:37 PM, -0700 by rjacobus.

More info...