HTTP Binding Wizard - HTTP Binding Configuration Page

Use to create an HTTP binding service.

At runtime, the concrete WSDL is generated with an HTTP binding and a SOAP binding; this is because the SOAP endpoint is used to provide HTTP support.

Notes: Note the following details about using HTTP binding in a SOA composite application:

The use of HTTP headers is not supported (that is, you cannot access HTTP headers in the composite and set them in the composite).
An outbound HTTP binding reference supports only XML as a response from an external HTTP endpoint. The response should contain the correct XML part name as per the outbound expectation.
You cannot change the httpBinding property for the HTTP binding component during runtime in Oracle Enterprise Manager Fusion Middleware Control.
If you want to enable basic authentication for inbound HTTP binding, you must attach a security policy. Inbound HTTP binding can also be used without enabling basic authentication.
1. Right-click the created HTTP binding service in the Exposed Services swimlane and select Configure WS Policies.
2. In the Configure SOA WS Policies dialog, click the Add icon in the Security section.
3. Select the oracle/wss_http_token_service_policy policy, and click OK.
4. In the Configure SOA WS Policies dialog, click OK.

Element	Description
Type	Configure an inbound or outbound HTTP binding service. Service: Creates an inbound HTTP binding service in the Exposed Services (left) swimlane that provides the outside world with an entry point to the SOA composite application. This direction is selected by default if you dragged the HTTP binding service into the Exposed Services swimlane. More Reference: Creates an outbound HTTP binding reference in the External References (right) swimlane that enables messages to be sent from the SOA composite application to external partners in the outside world. This direction is selected by default if you dragged the HTTP binding service into the External References swimlane. References support only the request-response pattern, and the external HTTP endpoint is expected to respond with XML. More
Operation Type	Select the type of operation to perform:
One-way	Select to create a one-way operation that sends or receives messages to and from an HTTP(S) endpoint.
Request-Response	Select to create a synchronous request-response operation that sends and receives input and output messages to and from an HTTP(S) endpoint.
Operation Name	Displays the operation name. If the operation type is one-way, the default name is Send. If the operation type is a request-response, the default name is Request-Response. You can override the default operation name by specifying a name.
Verb	Select the request method to be performed on the identified resource. GET: Retrieves data. POST: Submits data to be processed to the identified resource.
Payload Type	Select a payload type for HTTP POST request methods. For HTTP GET request methods, the payload type is URL-encoded and cannot be changed. url-encoded: Provides support for a URL-encoded payload (ampersand-separated name-value pairs) that uses the following format: <mime:context type="application/x-www-form-urlencoded"/> The provider converts the parameters to an XML format with the parameter name as the element tag and its content as the value. xml: Provides support for an XML payload that uses the following format: <mime:context type="text/xml"/>
Endpoint	Specify the endpoint URL. This field displays if you dragged the HTTP binding service into the External References swimlane and are configuring either an HTTP GET or POST request method.