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
  • Configuring the Quality of Service Properties
  • Configuring and Using Message Throttling
  • Configuring and Using Redelivery
• 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

Quality of Service (QOS) Features

---

Quality of Service (QOS) features are configured from the CASA Editor, and include properties used to configure Retry (Redelivery) and Throttling.

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 ellipsis button to open the QName Editor. Select a pre-existing Namespace URL or enter a new Namespace URL and prefix.	{http://j2ee.netbeans.org/wsdl/SoapBasicAuth}SoapBasicAuthServices
Endpoint Name	Specifies the consumer endpoint name. Click the ellipsis button to open an edit window.	SoapBasicAuthPortWssToken
Provider Settings
Service Name	Specifies the provider service name. Click the ellipsis button to open the QName Editor. Select a pre-existing Namespace URL or enter a new Namespace URL and prefix.	{http://enterprise.netbeans.org/bpel/BasicAuthBP/SoapBasicAuthAM}AMPartnerLink
Endpoint Name	Specifies the Provider endpoint name. Click the ellipsis button to open an edit window.	SoapBasicAuthAMPortTypeRole_myRole
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

Configuring and Using Message Throttling

Use throttling to set the maximum number of concurrent messages that are processed by a particular endpoint. Increased message load and large message payloads can cause memory usage spikes that can decrease performance. Throttling limits resource consumption so that consistent performance is maintained.

The HTTP Binding Component, using functionality provided by the Grizzly HTTP Web Server, manages the flow of messages by evaluating endpoints to determine when it is necessary to suspend requests and when to resume processing as usual.

For more information in regard to HTTP BC and Throttling, see HTT BC Throttling.

To Configure Throttling for an HTTP/SOAP WSDL Port:

1. From the NetBeans IDE Projects window, right-click the Service Assembly node under your composite application, and choose Edit from the pop-up menu.
   The CASA Editor opens containing your composite application.
   
   
2. Click the QOS icon located on the link between your JBI Module and the WSDL port you want to configure.
   The QOS Properties Editor appears.
   
3. Click the property field for maximumConcurrencyLimit under ThrottlingExtension, and type an integer for the maximum number of concurrent messages allowed for this endpoint.
   
   
4. Click Close.
   The appropriate throttling configuration for the connection is generated in the project's jbi.xml file, when the service assembly is built.

Configuring and Using Redelivery

Redelivery is a Quality of Service mechanism that handles message delivery when first-time delivery fails. Redelivery allows you to define the number of attempts that the system makes to deliver a message, the time between attempts, and the final result for an undeliverable message or non-responsive endpoint.
Redelivery is configured for a specific connection from the Composite Application Service Assembly (CASA) Editor, by clicking the QoS icon for that connection. This opens the Config QoS Properties for that connection. From the RedeliveryExtension section of the editor, configure the Redelivery properties.

The Redelivery configuration parameters are:

• maxAttempts: Specifies the number of times that the project attempts to re-deliver a message. An error status is returned to the JBI component for each failed attempt.
  

• waitTime: Specifies the time, in milliseconds, that the project waits between redelivery attempts.
  

• on-failure: Specifiy the actions taken and the message destination when the specified redelivery attempts have been exhausted. This parameter has four options:
  • delete: QoS utility deletes the message and returns a Done status to the JBI component, at which time the component proceeds to its next process. The delete option only supports In-Only message exchanges.
    
  • redirect: QoS utility redirects the message to a user-defined endpoint, such as a “dead-message” folder. Upon successful delivery to the redirect endpoint, the QoS utility returns a Done status to the JBI component, at which time the component proceeds to its next process. The redirect option only supports In-Only message exchanges.
    
  • suspend: 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.
    
  • error: The error option specifies that when the final attempt to redeliver the message is exhausted, the JBI component throws an exception. 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.
    

Note: The on-failure options, delete and redirect, cannot be applied to In-Out message exchanges because and the return value for these options does not suffice. A specific response is required from the process instance to proceed further.
For more information regarding Redelivery, see Redelivery.

Previous Next

This page (revision-14) was last changed on 05-Dec-08 10:48 AM, -0800 by rjacobus.
This page was created on 11-Sep-08 11:25 AM, -0700 by rjacobus.

More info...