SOAP over HTTP Binding Details (Provider)

The following table describes the binding details that are displayed for the selected SOAP over HTTP binding, where the shared resource is acting as a provider.

Property Description
Binding Name Defines the name used to identify this binding. The default value is SoapOverHttp.
Style/Use Defines the style/use used by the SOAP binding. One of:
  • RPC/literal
  • Document/literal
Note: If a concrete WSDL document is being used to expose the service, the style/use used here should match the style/use defined in the WSDL document. If the two differ, at runtime the style/use defined in the WSDL document takes precedence and the style/use defined here will be ignored.
SOAP Version Defines the SOAP version used by this binding. SOAP versions 1.1 and 1.2 are supported.

The default value is 1.1.

Endpoint URI Path Defines the URI path component of the endpoint address that will be used to expose the service. The full endpoint address is defined as:

   protocol://host:port/path

The construction of the endpoint address depends upon whether a concrete or an abstract WSDL document is being used to expose the web service - see SOAP over JMS Binding Details (Provider) .

If you use multiple bindings to expose the same service (for example, one for SOAP 1.1 and one for SOAP 1.2, each binding must have a unique Endpoint URI path.

HTTP Connector Instance Logical name to identify the HTTP Connector resource instance in the BPM runtime that will be used to expose the service to client applications.

The default value is httpConnector, which is the name of the default resource instance used by the BPM runtime to expose any services to clients over an HTTP connection.

If you wish to use a different HTTP Connector resource instance, you can do so using either of the following methods:

  • Early binding: Replace the name here with the name of a suitable HTTP Connector resource instance that already exists on the BPM runtime. (The mapping to the HTTP Connector resource instance will then be done automatically when you deploy the application to the BPM runtime.)
  • Late binding: Change or create the HTTP Connector resource instance to be used when you deploy the application to the BPM runtime. You do this by changing the value assigned to the HttpInboundConnectionConfig property on the Property Configuration page of the DAA Deployment Wizard. See Using Pageflow Processes and Business Services for more information about how to do this.

    If you instead export the project to a Distributed Application Archive for subsequent upload to the BPM runtime, a BPM administrator will need to configure the HTTP Connector resource instance to be used. See the Administrator interface documentation for your BPM runtime environment for more information about this.