Search Results

SOAP Reference Binding

Using SOAP reference binding you can create a service consumer using SOAP protocol.


This section has the following fields.

Field Description
Name The name of the reference binding.
Description A short description of the HTTP reference binding.
WSDL Service Specifies the service name and its target namespace.
WSDL Port Specifies the binding implemented by the service. If more than one implementation is available in concrete WSDL, select an appropriate implementation.
SOAP Version The version of the SOAP specification: 1.1 or 1.2.
Attachment Style The attachment style for the incoming and outgoing messages. The following attachment styles are available:
  • SwA
  • MTOM

The MTOM attachment style is available if SOAP 1.1, or SOAP 1.2 specification is used.

Transport Configuration

This section has the following fields.

Field Literal Value/Module Property Description
Transport Type None The transport over which the SOAP message is sent. HTTP and JMS transports are supported.
Application for HTTP Transport
Default Host/Port None Specifies the default host and port configuration available in the concrete WSDL.
HTTP Client Name None Name of the HTTP Client resource.
Endpoint URI Yes The endpoint of the service through which SOAP clients can access the service.
Application for JMS Transport
JMS Connection Name None Name of the JMS Connector resource
Tip: Click on the JMS Connection Name field to display details about the JMS Connector resource.
JMS Destination Yes Specifies the name of the destination for the incoming JMS messages. The syntax of the destination name is specific to the JMS provider you are using.
Messaging Style None Specifies the style of the incoming messages on the specified destination. It can be Generic, Queue, or Topic.
Message Type None Specifies the type of the incoming messages on the specified destination. It can be either Text Message or Bytes Message.
Delivery Mode No The delivery mode of messages.
  • Persistent Messages are stored and forwarded.
  • Non-Persistent Messages are not stored and can be lost due to failure.

The default is Persistent.

Expiration Yes The length of time a message can remain active. 0 means that the message does not expire.
Priority Yes The priority of the message. Priority is a value from 0-9. Higher numbers signify a higher priority (that is, 9 is a higher priority than 8).

The default is 4.

JMS Application Properties None The user-defined JMS Properties required to be available in the incoming message.
JMS Application Properties(Response) None The user-defined JMS Properties required to be sent in the outgoing message.