The HTTP Connection resource describes the characteristics of the connection used to receive incoming HTTP requests. This section provides a reference to the fields. For procedures see Adding a Shared Resource.The HTTP Connection resource can specify that the HTTPS (secure sockets layer or SSL) protocol must be used by clients. If this is enabled, you can configure the SSL parameters for the HTTP server using the Configure SSL Button. See Configure SSL for more information.
If you have multiple HTTP Connection resources specified by multiple HTTP Receiver process starters, the HTTP servers require that all of the connections must be valid to initialize all HTTP Receivers. Therefore, make certain that all HTTP Connection resources have valid configurations before testing or deploying the project.
Global Var? The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. Names must be unique within a folder. See Identifiers (Names).Unlike other resource identifiers, however, shared resource identifiers can have spaces in the name.This field appears on the New HTTP Connection Wizard. The name then appears in the title of the resource. Specifies the name of the host that accepts the incoming requests. For machines that have only one network card, the default value localhost specifies the current machine. For machines that have more than one network card, this field specifies the host name of the card that will be used to accept incoming HTTP requests.Note Only one HTTP server can be started on each port. Therefore, if you have a machine with multiple network cards, make certain that all HTTP Connection resources that use the same host name specify different port numbers.Note If there is more than one network card on the machine, and the serverType field is set to TOMCAT, and you specify localhost in this field, then all network cards on the machine will listen for incoming HTTP requests on the specified port. If the serverType field is set to BUILT-IN, then only the loopback address will be bound to the HTTP port. Specifies whether incoming requests must use the HTTPS (secure socket layer, or SSL) protocol. This protocol authenticates the server to the client, and optionally authenticates the client to the server.Enabling this field allows you to specify SSL parameters with the Configure SSL button (see Configure SSL).The SSL Configuration for HTTPS Connections dialog (accessed by configuring the Configure SSL button) allows you to specify the SSL parameters for the HTTP connection.
Checking this field requires clients to present their digital certificate before connecting to the HTTP server.When this field is checked, the Trusted Certificates Folder becomes enabled so that you can specify a location containing the list of trusted certificate authorities. This field is only applicable when the Requires Client Authentication field is checked.This field specifies a folder in the project containing one or more certificates from trusted certificate authorities. This folder is checked when a client connects to ensure that the client is trusted. This prevents connections from rogue clients. This is an Identity resource that contains the HTTP server’s digital certificate and private key. See Identity Resource for more information. When checked, this field specifies that the minimum strength of the cipher suites used can be specified with the bw.plugin.security.strongcipher.minstrength custom engine property. See TIBCO ActiveMatrix BusinessWorks Administration for more information about this property. The default value of the property disables cipher suites with an effective key length below 128 bits.When this field is unchecked, only cipher suites with an effective key length of up to 128 bits can be used.
Copyright © TIBCO Software Inc. All Rights Reserved.