HTTP Binding Component Runtime Properties

The HTTP Binding Component's runtime properties can be configured from the NetBeans IDE, or from a command prompt (command line interface) during installation.

The HTTP Binding Component properties apply to the binding component as a whole, including all provider and consumer endpoints.

To display or edit the properties in the NetBeans IDE, do the following:

From the Services tab of the NetBeans IDE, expand the Servers node.
Start your application server. To do this, right-click your application server and select Start from the shortcut menu.
Under the application server, expand the JBI -> Binding Components nodes and select the HTTP Binding Component (com.sun.httpsoapbc). The current HTTP Binding Component properties are displayed at the right side of the NetBeans IDE. You can also double-click the HTTP Binding Component to open a properties window.
Edit the properties as needed. To apply any changes you make to the runtime HTTP Binding Component properties, stop and restart the HTTP Binding Component.

Figure 2 HTTP Binding Component Runtime Properties

image:Graphic shows the HTTP Binding Component Runtime Properties Editor dialog box. The dialog box displays the properties and their current values.

The HTTP Binding Component properties specify clustering and proxy settings, and reference the Binding Component's description, name, type, and state.

Table 18 HTTP Binding Component Runtime Properties

Property	Description	Required or Optional	Example
General Properties
Description	Indicates the purpose of the HTTP Binding Component. This property is displayed for reference purposes.	Automatic	HTTP Soap Binding to send SOAP messages, for example, to and from BPEL service engine.
Name	Indicates the name of the HTTP Binding Component. This property is displayed for reference purposes.	Automatic	com.sun.httpsoapbc-1.0-2
State	Indicates the state of the HTTP Binding Component as "Started" or "Stopped." This property is displayed for reference purposes.	Automatic	Started
Type	Indicates the type of component. This property is displayed for reference purposes.	Automatic	binding-component
Identification Properties
Version	Indicates the component specification version.	Static	1.0
Build Number	Indicates the component build number.	Static	080311_4
Configuration Properties
Number of Outbound Threads	Specifies the maximum number of threads to process outbound HTTP/SOAP invocations concurrently. The value can be any integer from 1 to 2147483647.	Required	10
Default HTTP Port Number	Specifies the default HTTP port number for the HTTP Binding Component instance. This property is required for clustering and allows each HTTP Binding Component to be differentiated by its unique default port number. A default port number is calculated and preassigned when the binding component is initially installed in the application server instance. A file containing the persisted configuration is stored for each component. This is used to assign a unique default port number for each HTTP Binding Component instance on a computer.	Required	8180
Default HTTPS Port Number	Specifies the default HTTP Secure port number for the HTTP Binding Component instance. This property is required for clustering and allows each HTTP Binding Component to be differentiated by its unique default port number. A default port number is calculated and preassigned when the binding component is initially installed in the application server instance. A file containing the persisted configuration is stored for each component. This is used to assign a unique default port number for each HTTP Binding Component instance on a computer.	Required	8280
(SSL) Client authentication enabled	Specifies if client authentication 2-way (mutual) SSL on the default HTTPS port is enabled. Restart the binding component to effect changes for this property.	Optional	Select the checkbox to enable
Sun Access Manager Configuration Directory	Specifies the location of the Sun Access Manager configuration directory, which contains the Access Manager properties file. If you are using the OpenSSO Web Service Security Agent (WSS), use this property to specify the directory that contains the `AMConfig.properties` file. For more information see Authentication Mechanisms for Consumer Endpoints	Optional	C:\JavaCAPS\appserver\ addons\accessmanager
Sun Access Manager Classpath	Specifies the client SDK JAR and WS provider JAR files to be added to the classpath. The files you specify depend on whether you are using Access Manager or OpenSSO Web Service Security Agent (WSS) For more information see Authentication Mechanisms for Consumer Endpoints	Optional	C:\JavaCAPS\appserver\ addons\accessmanager\ amclientsdk.jar, C:\GlassFishESBv21\ glassfish\addons\ accessmanager\ amWebServicesProvider.jar Note: Files are comma separated.
Proxy Type	Specifies the proxy type as SOCKS, HTTP, or DIRECT. Enter one of the following String values: SOCKS The proxy server is a SOCKS (version 4 or version 5) server. HTTP The proxy is an HTTP proxy server. DIRECT The connection does not go through any proxy.	Required	SOCKS
Proxy Host	Specifies the proxy host name or IP address.	Optional	polaris.sun.com
Proxy Port	Specifies the proxy port number.	Required	2080
Non-proxy Hosts	Specifies the list of hosts that you do not want to go through the proxy. Each host is separated with a pipe "\|".	Optional	localhost\|127.0.0.4
Proxy User Name	Specifies the user name used to the proxy server. For SOCKS-v4, no authentication is required. For SOCKS-v5, the binding component supports no authentication, and Username/Password authentication. For HTTP Proxy, the binding component supports Basic Authentication, Digest Access, and NTLM. Basic Authentication requires a specified username and password. Digest Access and NTLM require a dedicated proxy server for support.	Required in some cases
Proxy User Password	Specifies the password used in conjunction with the ProxyUserName to access the proxy server. For SOCKS-v4, no authentication is required. For SOCKS-v5, the binding component supports no authentication, and Username/Password authentication. For HTTP Proxy, the binding component supports Basic Authentication, Digest Access, and NTLM. Basic Authentication requires a specified username and password. Digest Access and NTLM require a dedicated proxy server for support.	Required in some cases
Use Default JVM Proxy Settings	Indicates whether the HTTP Binding Component's proxy settings are specified by the existing JVM settings or by the HTTP Binding Component properties. The options indicate the following: true The proxy is controlled by the existing JVM system settings. The settings are outside of this binding component, so all additional proxy settings are ignored. false The proxy is controlled by the binding component proxy settings.	Required	false
Allowed hostname aliases for localhost	Specifies a comma-separated list of alias names that the HTTP BC uses to validate the host name in a service URL when it deploys an application. The HTTP BC does not perform any general validation of the aliases in the list, so they must only be valid as resolvable host names on the host system. Use this property when a given host supports multiple interfaces that have different FQDNs (fully qualified domain names) for the host.	Optional	None
Application Configuration	Specifies the values for a Composite Application's endpoint connectivity parameters (normally defined in the WSDL service extensibility elements), and 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.	Optional	The user-defined name of the Config Extension you want and define, and the values for the connection parameters.
Application Variables	Specifies a list of name:value pairs for a given stated type. The application variable name can be used as a token for a WSDL extensibility element attribute in a corresponding binding. The Application Variables configuration property offers four variable types: String: Specifies a string value, such as a path or directory. Number: Specifies a number value. Boolean: Specifies a Boolean value. Password: Specifies a password value.	Optional	Enter the name value, such as PASSWORD, and enter the variable Value, such as SECRET. For Boolean values, the Value field provides a checkbox (checked = true). For Password values, the Value entered is masked as asterisks.
Statistics Properties
Includes 19 different component activities including exchanges, errors, requests, replies, and so forth.	Lists component statistics that are collected for actions such as endpoints activated, average response time, completed exchanges, and so forth. Running statistics are automatically collected and displayed.	Automatic	240
Loggers Properties
Includes over 30 different component activities that can be recorded by the server.log.	Specifies the level of logging for each event. There are eight levels of logging, FINEST (most detailed), FINER, FINE, CONFIG, INFO, WARNING, SEVERE (failure messages only), and OFF.	Optional	WARNING

Skip Navigation Links
Exit Print View
	Oracle Java CAPS HTTP Binding Component User's Guide Java CAPS Documentation