SOAP Service Binding

Using SOAP service binding you can create a service provider through the SOAP protocol.

Binding

This section has the following fields.

Field Description
Name The name of the service binding.
Description A short description of the service getting exposed.
Target Namespace The Target Namespace of the service.

Generate Concrete WSDL

The SOAP service binding helps you to create the concrete WSDL using Concrete WSDL Generation Wizard. See Generating Concrete WSDL for more details.

SOAP Default Configuration

This section has the following fields.

Field Description
SOAP Version The version of the SOAP specification: 1.1 or 1.2. The default is 1.1.
Style The default SOAP binding style for all operations. Specify either Document or RPC style.
Encoding Encoding is literal.
Attachment Style Select the default attachment style for all the binding operations. Can be overidden at the operations level for each operation.

The following attachment styles are available:

  • SwA - Supports both, Bound and Unbound Attachments
  • MTOM

The MTOM attachment style is available only if 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 SOAP message is sent. The HTTP and JMS transports are supported.
Connector Name None The name of the shared resource. This points to either the HTTP or JMS shared transport configuration.
Configuration for HTTP Transport
HTTP Connector Name None Name of the HTTP Connector resource.
Tip: Tip: Click on the HTTP Connector Name field to display details about the HTTP Connector resource.
Endpoint URI Yes The endpoint URI for the service.
Configuration for JMS Transport
JMS Connection Name None The name of the JMS Connector resource.
Tip: Tip: Click on the JMS Connection Name field to display details about the JMS connector resource.
Acknowledge Mode None The acknowledge mode for service request messages. It can be one of the following:
  • Auto: The message is acknowledged when it is received by a SOAP Service Binding.
  • Client: The message is not acknowledged when it is received by the SOAP Service Binding. You can confirm the message by using the Confirm activity in the BusinessWorks process that is configured as an operation implementation. If the Confirm activity is not used, the message is automatically acknowledged by the SOAP Service Binding while sending the service reply.
  • Dups OK:The message is acknowledged automatically when it is received by a SOAP Service Binding. JMS provides this mode for lazy acknowledgment , but BusinessWorks Container Edition acknowledges messages upon receipt.
  • Tibco EMS Explicit: (only available for TIBCO Enterprise Message Service™)

    The message is not acknowledged when it is received by a SOAP service binding. You can confirm the message by using the Confirm activity in the BusinessWorks Container Edition process that is configured as the operation implementation.

    If the Confirm activity is not used, then the message is automatically acknowledged by the SOAP Service Binding while sending the service reply.

    The session is not blocked and one session handles all incoming messages for each process instance.
  • Tibco EMS Explicit Dups OK: (only available for TIBCO Enterprise Message Service)

    The message is not acknowledged when it is received by a SOAP service binding. You can confirm the message by using the Confirm activity in the BusinessWorks Container Edition process that is configured as the operation implementation.

    If the Confirm activity is not used, the message is automatically acknowledged by SOAP Service Binding while sending the service reply.

    The session is not blocked and one session handles all the incoming messages for each process instance. The messages however, are lazily acknowledged.
Message Type None Specifies the type of the service request messages. It can be either Text message or Bytes message.
Messaging Style None Specifies the style of the service request messages. It can be Generic, Queue, or Topic.
JMS Destination Yes Specifies the name of the destination for the service request messages. The syntax of the destination name is specific to the JMS provider you are using.
JMS Application Properties None User-defined JMS Properties expected to be available in the service request messages.

NOTE: JMS Application properties should be defined in a schema only through a complex type. Also, all JMS Application properties should be direct child of this complex type.

JMS Application Properties (Response) None User-defined JMS Properties expected to be sent in the the service response messages.

NOTE: JMS Application properties should be defined in a schema only through a complex type. Also all JMS Application properties should be direct child of this complex type.

Max Sessions None When the Acknowledge Mode field is set to Client, this field configures the maximum number of JMS sessions that is created for the service request messages.

When a message is received, the session is blocked until the message is acknowledged in the process. If acknoledgement is not done at process level then it is automatically acknowleged when the SOAP Service Binding sends a service reply.

After reaching the maximum number of sessions, no new incoming messages can be processed. Once any one of the messages is processed ,the total number of active sessions decreases and then another incoming message can be processed.

Operations None

This field is available only when Topic is selected in the JMS Destination Type field.

Operation Name - Specifies the operation name.

Durable Subscription - Set to true if the client is a durable subscriber.

Subscription Name - Specify the Subscription Name if Durable Subscription is set to true.

Persistence Configuration

This section has the following fields.

Field Literal Value/Module Property Description
Persistence Type None Select any one from the available Persistence configuration types. They are NONE and File.

Selecting the File option displays the Directory, Create Directories, and Threshold Size fields.

Directory Yes The directory where attachments will be serialized.
Create Directories Yes Creates new directories if not present on the disk.
Threshold Size Yes The maximum size of the attachment that can be kept in memory. Attachments larger than the specified size will be written to the disk.The file name generated for serialization is random except when the Content-disposition header is available for the attachment. Here, the name is the same as the content-disposition header value.

You can configure the size to Bytes, KB or MB.

Threading Policy Details

The following are the details for the SOAP Service Binding threading policy.

Activity Type Multi-Threaded? Default Thread Count Thread Count Configuration
Transport: HTTP
ProcessStarter Yes
  • Minimum thread pool threads = 10
  • Maximum thread pool threads = 75
It can be configured on the HTTP Connector shared resource using the following fields:
  • Minimum QTP threads
  • Maximum QTP threads

Add Binding

You can add a binding. Click the Add Binding icon to add a binding.

Delete Binding

You can delete a binding. Click the Delete Binding icon to delete a binding.