Name of the binder.

Endpoint address associated with this web service, that is, the network address at which the web service can be invoked.

For a consumer web service descriptor, this value is determined by the location attribute in the soap:address element (which is contained within the soap:port element of the service element).

For a WSDL first provider web service descriptor, the Port address is empty.

For a service first web service descriptor, you can edit the Port address for a binder that uses HTTP or HTTPS as the Transport.

For a web service descriptor that uses the JMS transport, the Port address displays the initial part of the JMS URI, specifically “jms”:<lookup var>:<dest>?targetService. Integration Server displays additional information that is part of the JMS URI in the JMS Settings and JMS Message Details properties.

The Port address value is display-only when Transport is JMS, the binder is in a consumer web service descriptor, or the binder is in a WSDL first provider web service descriptor.

Endpoint alias name associated with this web service. The endpoint alias name will be used for this binder when generating a WSDL for a provider or when executing a web service connector for a consumer. The actual endpoint value is looked up at run time in both cases. New aliases can be defined from the Integration Server, using Settings > Web Services.

Name of the port associated with the web service, as defined by the WSDL; an aggregate of a binding and a network address.

The SOAP processor for which the web service will be a target. The drop-down menu lists all registered SOAP processors on the Integration Server to which you are currently connected.

Name of the WSDL binding element.

Name of the portType associated with the WSDL binding element.

Type of binding. This will be one of the following:

Binding type is display-only. The Transport value determines the Binding type value.

Transport mechanism used to invoke the web service, specify:

The transport you select must match the type of requests accepted by the port you selected.

Version of the SOAP message protocol to be used; either SOAP 1.1 or SOAP 1.2.

The style of the SOAP binding and its operations; either Document or RPC (Remote Procedure Call).

The usage attribute of the SOAP binding and its operations; either literal or encoded

The transport protocol used by this SOAP Binding.

SOAP action associated with the operations in the binder.

Click in the Value column to display the SOAP action string associated with each operation in the binder.

For a service first provider web service descriptor, you can modify the SOAP action for an operation in a binder. The SOAP action value must be unique within the web service descriptor.

The SOAP action cannot be edited for a WSDL first provider web service descriptor or a consumer web service descriptor.

The address template that you can use as ReplyTo or FaultTo address to make the consumer web service descriptor process responses asynchronously. This property displays the following address format:

Where, wsdName is the web service descriptor name and portName is the name of the port associated with the web service, as defined by the WSDL; an aggregate of a binding and a network address.

You must specify this address as the value for ReplyTo and/or FaultTo address in the messageAddressingProperties parameter of the corresponding web service connector to use this consumer web service descriptor to process responses asynchronously by invoking the callback response services. You must replace the placeholders <server> and <port> or <topic/queue/jndi> and <destinationName> with appropriate values depending on the transport mechanism used to invoke the web service.

Indicates whether Integration Server places the request message in the client side queue if the JMS provider is not available at the time the message is sent.

Specify that Integration Server writes messages to the client side queue if the JMS provider is not available at the time the request message is sent by the web service connector.

Specify that Integration Server throws an ISRuntimeException if the JMS provider is not available at the time the web service connector executes. This is the default.

For more information about using the client side queue when sending web service requests using SOAP over JMS, seeConfiguring Use of the Client Side Queue.