Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS HTTP Binding Component User's Guide Java CAPS Documentation |
Using the HTTP Binding Component
HTTP/SOAP Binding Architecture
HTTP Binding Component Features
HTTP Binding Component Example Scenario
SOAP 1.1 WSDL Extensibility Elements
SOAP 1.1 header and headerfault Elements
SOAP 1.2 WSDL Extensibility Elements
SOAP 1.2 header and headerfault Elements
HTTP WSDL Extensibility Elements
Configuring the HTTP Binding Component for HTTP Get Interactions
Using the HTTP Binding Component with the HTTP POST Method
Configuring the HTTP Binding Component for HTTP Get Interactions
HTTP POST Treatment of http:urlEncoded and http:urlReplacement
HTTP Binding Component Runtime Properties
HTTP Binding Component Client Endpoint Properties
Accessing the HTTP Binding Component Client Endpoint Properties
HTTP BC Client Endpoint Configuration Properties
Using Normalized Message Properties to Propagate Binding Context Information
Using Normalized Message Properties in a BPEL Process
Using Predefined Normalized Message Properties in a BPEL Process
To use predefined normalized message properties in a BPEL process
Adding Additional Normalized Message Properties to a BPEL Process
To add a Normalized Message Property Shortcut to a BPEL process
To edit an NM Property Shortcut
To delete an NM Property Shortcut
To add a Normalized Message Property to a BPEL process
BPEL Code Generation Using NM Properties
SOAP HTTP Binding Component Specific Normalized Message Properties
Quality of Service (QOS) Features
Configuring the Quality of Service Properties
Message Throttling: Configuring and Using
Configuring the HTTP Binding Component Endpoint for Throttling
Redelivery: Configuring and Using
Using the Tango Web Service Features with the HTTP Binding Component
Configuring Reliable Message Delivery
Installing the Synchronous BPEL Process sample
Configuring Web Services for a Project from the CASA Editor
Configuring the Tango Web Services Attributes exposed by the HTTP Binding Component
Accessing the Tango (WSIT) Web Service Attribute Configuration
Accessing the WS-Policy Attachment Editor for a Specific Endpoint
Server Configuration--Web Service Attributes
Client Configuration -- Web Service Attributes
HTTP Binding Component Security
Using Basic Authentication with the HTTP Binding Component
Basic Authentication Supported Features
Authentication Mechanisms for Consumer Endpoints
WssTokenCompare Username/Password Authentication
Using the Access Manager for Authentication and Authorization
Installing the Access Manager Add-on
Installing Access Manager with Java Application Platform SDK
Configure the HTTP Binding Component to use Access Manager
Using the OpenSSO Web Services Security (WSS) Agent for Authentication and Authorization
Install OpenSSO Enterprise Server
Configure the HTTP Binding Component to use OpenSSO Web Service Security
Using the GlassFish Realm Security to Authenticate the HTTP Client Credentials
Configuring Security Mechanisms
Username Authentication with Symmetric Key
Message Authentication over SSL
SAML Sender Vouches with Certificates
STS Issued Token with Service Certificate
Using Application Variables to Define Name/Value Pairs
Using Application Variables for password protection
Creating a password Application Variable
Using Application Configuration to Configure Connectivity Parameters
To apply a named Config Extension to the Application Configuration
Clustering Support for the HTTP Binding Component
Configuring the HTTP Binding Component for Clustering
Understanding the ${HttpDefaultPort} Token
Validating HTTP Extensibility Elements from the WSDL Editor
Adding a SOAP Template to a WSDL Document
Adding an HTTP Template to a WSDL Document
Web Service Client Calling an Operation Using HTTP Basic Authentication
Web Service Implementing an Operation Protected by HTTP Basic Authentication
Web Service Client Calling an Operation Using SSL Authentication
Web Service Implements an Operation Protected by SSL Authentication
The HTTP Binding Component provides connectivity for SOAP over HTTP in a JBI 1.0 compliant environment. The HTTP Binding Component is used as both a provider proxy to support connectivity to services in the JBI environment, and as a consumer proxy to invoke services.
The JBI platform enables software vendors to provide services that can be invoked by external components using different protocols. These services are represented as JBI service engines and implement the business logic of the service. JBI binding components implement the protocol transformations between abstract messages handled by the JBI Service Engines and concrete messages of the protocol.
The HTTP Binding Component enables external components to invoke services, hosted by the JBI platform, using SOAP messages over the HTTP/HTTPS protocol. It also allows JBI components to invoke external web services using the same SOAP over the HTTP/HTTPS protocol.
The transformation of abstract messages to SOAP messages occurs in the HTTP Binding Component. WSDL extensibility elements, as defined in the WSDL 1.1, SOAP 1.1, SOAP 1.2 specifications, and Basic Profile 1.1, are used to properly configure this transformation. These WSDL extensibility elements are part of the binding and service sections of WSDL documents. These WSDL documents are the major artifacts included in a Service Unit, the JBI deployable unit into a Binding Component. Both the binding and service sections of a WSDL document must be properly filled out to determine how the message is transformed and the destination of that message.