HTTP Binding Component User Guide

Contents

• HTTP Binding Component User Guide
• About the HTTP Binding Component
• The 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
  • Configuring the Quality of Service Properties
• Using the Tango Web Service Features with the HTTP Binding Component
• Using Basic Authentication with the HTTP Binding Component
• Using Application Variables to Define Name/Value Pairs
• Using Application Configuration to Configure Connectivity Parameters
• Statistics Monitoring
• Clustering Support for the HTTP Binding Component
• Common User Scenarios

Quality of Service (QOS) Features

Quality of Service features are configured from the CASA Editor, and include properties used to configure Retry (Redelivery) and Throttling. This section contains the following topics:

• Configuring the Quality of Service Properties
• Message Throttling: Configuring and Using
• Redelivery: Configuring and Using

Configuring the Quality of Service Properties

The QOS attributes are configured from the Config QoS Properties Editor, accessed from the Composite Application Service Assembly (CASA) Editor. For an example of how to access the Config QOS Properties Editor, see Configuring the HTTP Binding Component Endpoint for Throttling

Attribute	Description	Value/Example
Consumer Settings
Service Name	Specifies the consumer service name. Click the ellipses button to open the QName Editor.	Check box Selected indicates enabled.
Endpoint Name	Specifies the consumer endpoint name. Click the ellipses button to open an edit window.	Check box Selected indicates enabled.
Provider Settings
Service Name	Specifies the provider service name. Click the ellipses button to open the QName Editor.	Check box Selected indicates enabled.
Endpoint Name	Specifies the Provider endpoint name. Click the ellipses button to open an edit window.	Configure the Keystore from the Keystore Configuration Editor.
RedeliveryExtension Settings
maxAttempts	Specifies the number of retries to attempt before using the on-failure option.	20
waitTime	Specifies time (in milliseconds) to wait between redelivery attempts.	300
on-failure	Specifies the type of action to be taken when message exchange (ME) re-delivery attempts have been exhausted. The on-failure options are: * delete: When the final defined delivery attempt has failed, the QoS utility abandons the message exchanges (ME) and returns a Done status to the JBI component, which proceeds to its next process instance. This option is only supported for In-Only message exchanges. * error: When the final defined delivery attempt has failed, the QoS utility returns an Error status to the JBI component, and the JBI component throws an Exception. This is the default option, and is supported for both In-Only and In-Out message exchanges. * redirect: Similar to the delete option, except that the QoS utility re-routes the ME to the configured redirect endpoint when the maxAttempts count has been exhausted. If the QoS utility is successful in routing the message to the redirect endpoint, a Done status is returned to the JBI component; otherwise, an Error status is returned. This option is supported for In-Only message exchanges only. * suspend: The QoS utility returns an Error status to the JBI component if it is not able to deliver the ME to the actual provisioning endpoint. After the re-delivery attempts have been exhausted, the JBI Component suspends the process instance. This option is only supported if monitoring is enabled in the JBI Component, since the user must use the monitoring tool to resume a suspended instance. This option is supported for both In-Only and In-Out message exchanges.	delete
ThrottlingExtension Settings
maximum-ConcurrencyLimit	Specifies the maximum number of concurrent messages that can be processed on a specific connection. This number is used to set up the maximum number of concurrent messages that the internal endpoint sends to the the provider endpoint.	10

Previous Next

This page (revision-3) was last changed on 11-Sep-08 11:40 AM, -0700 by rjacobus.
This page was created on 11-Sep-08 11:25 AM, -0700 by rjacobus.

More info...