HTTP Binding Component User Guide

Contents

• HTTP Binding Component User Guide
• 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
• Configuring Quality of Service (QOS) Features
• Using the Tango Web Service Features with the HTTP Binding Component
• Configuring Web Service Attributes
• Configuring Security Mechanisms
• Using Basic Authentication with the HTTP Binding Component
• Using Application Variables to Define Name/Value Pairs
• Using Application Configuration to Configure Connectivity Parameters
• Enhanced Logging
• Statistics Monitoring
• Using WS-Transaction
• Clustering Support for the HTTP Binding Component
• Common User Scenarios

The HTTP/SOAP Binding Architecture

The HTTP Binding Component's SOAP binding enables external components to invoke web services hosted by the JBI platform using SOAP messages over the HTTP protocol. It also allows JBI engines to expose its services. The web service can be unsecured or secured, using HTTP over SSL, TLS, or some other technology.

The SOAP binding resides in the JBI framework. It leverages the services offered by the web container to receive incoming web service requests. The Binding components are based on standards and do not use any proprietary API to promote reusability across different J2EE based JBI platforms. The binding does not use any web container services for outbound web services requests.

The HTTP Binding Component is B.P.1.1 compliant. The binding addresses Basic Profile 1.1 requirements for messaging:

• XML representation of SOAP messages, including fault messages
• SOAP processing model
• Use of SOAP in HTTP
• Transport level security.

The following diagram illustrates relationship between the HTTP Binding Component and the other components within the runtime environment.

The Application Server contains the ESB/JBI container, as well as the Metro container that incorporates JAX-WS, JAX-RPC, JAXB, and Tango (WSIT), and the HTTP (Grizzly) container that adds Asynchronous Processing and NIO. The ESB/JBI container incorporates the HTTP Binding Component, the BPEL Service Engine, and the Java EE Service Engine, as well as other JBI Components. The HTTP/SOAP Binding Component provides interaction between the various containers and JBI components within the Application Server.

Previous Next

This page (revision-11) was last changed on 22-Sep-08 10:40 AM, -0700 by rjacobus.
This page was created on 10-Sep-08 15:05 PM, -0700 by rjacobus.

More info...