JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Java CAPS HTTP Binding Component User's Guide     Java CAPS Documentation
search filter icon
search icon

Document Information

Using the HTTP Binding Component

About the HTTP Binding Component

HTTP/SOAP Binding Architecture

HTTP Binding Component Features

Service Provider Features

Service Consumer Features

Security Features

HTTP Binding Component Example Scenario

Purchase Order Example

SOAP Processing

SOAP 1.1 WSDL Extensibility Elements

SOAP 1.1 Connectivity Element

SOAP 1.1 address Element

SOAP 1.1 Binding Elements

SOAP 1.1 binding Element

SOAP 1.1 operation Element

SOAP 1.1 body Element

SOAP 1.1 fault Element

SOAP 1.1 header and headerfault Elements

SOAP 1.2 WSDL Extensibility Elements

SOAP 1.2 Connectivity Element

SOAP 1.2 address Element

SOAP 1.2 Binding Elements

SOAP 1.2 binding Element

SOAP 1.2 operation Element

SOAP 1.2 body Element

SOAP 1.2 fault Element

SOAP 1.2 header and headerfault Elements

WS-I Basic Profile 1.1

HTTP Processing

HTTP WSDL Extensibility Elements

HTTP Connectivity Element

HTTP address Element

HTTP Binding Elements

HTTP binding Element

HTTP operation Element

HTTP urlEncoded Element

HTTP urlReplacement Element

HTTP GET and POST Processing

XML/HTTP GET Processing

Configuring the HTTP Binding Component for HTTP Get Interactions

Binding Details

http:binding Element

http:address Element

http:operation Element

http:urlEncoded Element

http:urlReplacement

Using the HTTP Binding Component with the HTTP POST Method

Configuring the HTTP Binding Component for HTTP Get Interactions

Binding Details

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

To delete an NM Property

BPEL Code Generation Using NM Properties

Normalized Message 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

Mutual Certificates Security

Transport Security (SSL)

Message Authentication over SSL

SAML Authorization over SSL

Endorsing Certificate

SAML Sender Vouches with Certificates

SAML Holder of Key

STS Issued Token

STS Issued Token with Service Certificate

STS Issued Endorsing Token

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

Enhanced Logging

Statistics Monitoring

Using WS-Transaction

Clustering Support for the HTTP Binding Component

HTTP Load Balancer

Configuring the HTTP Binding Component for Clustering

Understanding the ${HttpDefaultPort} Token

Common User Scenarios

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

Using Application Configuration to Configure Connectivity Parameters

The Application Configuration property allows you to configure the external connectivity parameters for an application that you have created, such as a service assembly, and without changing or rebuilding the application, deploy the same application into a different system. For example, you could take an application that is running in a test environment, and deploy it to a production environment without rebuilding the application.

From the Application Configuration property, you can specify values for a Composite Application's external connectivity parameters, which are normally defined in the WSDL service extensibility elements. You can then apply these values to a user-named endpoint Config Extension Property. The Application Configuration property editor includes fields for all of the connectivity parameters that apply to that component's binding protocol. When you enter the name of a saved Config Extension and define the connectivity parameters in the Application Configuration editor, these values override the WSDL defined connectivity attributes when your project is deployed. To change these connectivity parameters again, you simply change the values in the Application Configuration editor, then shutdown and start your Service Assembly to apply the new values.

The Application Configuration property editor allows you to create several application configurations referenced by their own user-defined names. Note that different binding component protocols will have different attributes. The HTTP binding attributes are not the same as the JMS binding attributes, and therefore, the Application Configuration property editors for each of these binding components will contain different attributes.

To change a property when the application is running, change your Application Configuration property value, then right-click your application in the Services window under Servers -> GlassFish -> JBI Service Assemblies, and click Stop in the popup menu. When you restart your project, your new settings will take effect.

The HTTP Binding Component's Application Configuration property contains one parameter only: HTTP URL Location.

To apply a named Config Extension to the Application Configuration

  1. In the CASA editor, specify a name for your endpoint Configuration Extension , from the endpoint's Configuration Extension property.
  2. In the Services window, go to the Binding Components directory under the JBI node, right-click the binding component used by your application, and select Properties.

    The Properties window appears.

  3. In the binding component's properties, click on the Application Configuration property ellipsis (...) button.

    The Application Configuration property editor appears.

  4. Enter the user-defined name of the Config Extension you want and define the values for the connection parameters.
  5. Once the Application Configuration values have been defined, deploy your application.