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: Click in 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: Click in the
JMS Connection Name field to display details about the JMS connector resource.
|
Acknowledge Mode
|
None
|
The acknowledge mode for service request messages.
- Auto: The SOAP Service Binding acknowledges the message upon receipt.
- Client: The SOAP Service Binding does not acknowledge the message upon receipt. Use
Confirm activity in the
TIBCO BusinessWorks™ Container Edition to confirm the message. If the
Confirm activity is not used, SOAP Service Binding automatically acknowledges the message while sending the service reply.
Note: One-way operations with fault, if the service uses the
Catch block to handle the exception, the message is acknowledged.
To retain a message in a queue, do not create a catch block handler.
Set max retry attempts at queue level to avoid infinite number of deliveries of JMS messages to a SOAP service.
- Dups OK:The SOAP Service Binding acknowledges the message upon receipt. JMS provides this mode for lazy acknowledgment, but
TIBCO BusinessWorks Container Edition acknowledges messages upon receipt.
- Tibco EMS Explicit: (only available for TIBCO Enterprise Message Service)
SOAP service binding does not acknowledge the message. Use
Confirm activity in the
TIBCO BusinessWorks Container Edition to confirm the message.
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.
Note: For One way operations with fault, if the service handles the exception using the
Catch block, message gets acknowledged.
If you want to retain a message in a queue , do not create a catch block handler.
It is recommended to set max retry attempts at queue level to avoid infinite number of deliveries for JMS message to a SOAP service.
- 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
TIBCO 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.
|
Delivery Mode (Response)
|
None
|
The message delivery mode.
- Persistent Messages - stored and forwarded.
- Non-Persistent Messages - not stored and can be lost due to failure.
The default mode is
Persistent.
|
JMS 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.
|
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 acknowledgement is not done at process level then it is automatically acknowledged when the SOAP Service Binding sends a service reply.
After reaching the maximum number of sessions, no new incoming messages can be processed. After any of the messages are processed, the total number of active sessions decreases and 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 the
Durable Subscription value is set to
true.
|