Transport Details

The Transport Details tab allows you to specify additional configuration information based on the type of transport used for the SOAP request. For more information about SOAP over the JMS transport, see SOAP Messages Over the JMS Transport.

The Transport Details tab contains the following fields:

Field

Global Var?

Description

HTTP Transport

Use Basic Authentication

No

When checked, this field specifies that incoming SOAP requests must supply a valid username and password.

The user name and password specified in the incoming request must exist in the domain (users are created and managed in the domain using TIBCO Administrator).

Endpoint URI

No

Specify endpoint URI here. This is optional.

JMS Transport

JMS Destination

No

Name of the JMS destination for incoming requests.

The syntax of the destination name is specific to the JMS provider you are using. For more information about destination names, see your JMS provider documentation.

Note: If you are using TIBCO Enterprise Message Service as your JMS provider, you can use the Browse button next to this field after specifying a valid connection in the JMS Connection field and a destination type in the JMS Destination Type field. The Browse button displays a list of configured destinations in the JMS server that are of the specified type.

JMS Destination Type

No

Specify either Queue or Topic as the destination type.

Durable Subscription

No

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

This field specifies a durable subscription.

You must specify a name in the Subscription name field that is registered with the JMS application as the durable subscription name.

Subscription Name

No

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

This field specifies the subscription name registered with the JMS application for durable subscriptions. This field is only available when the Durable subscription field is checked.

Once a durable subscription is created, it can only be removed by accessing the administration tool of the JMS provider. For more information about managing durable subscriptions, see the documentation of your JMS provider.

JMS Message Type

Yes

The type of the message. This can be one of the following:

  • Bytes Message — A stream of bytes.

  • Text Message — The message is a java.lang.String.

Acknowledge Mode

Yes

This field is available when a JMS transport is selected.

This field specifies the acknowledgement mode to be used for incoming messages. It can be one of the following:

  • Auto : the message is automatically acknowledged when it is received.

  • Client: the message is acknowledged when the process implementing the operation ends successfully.

  • Dups OK : the message is acknowledged automatically when it is received. JMS provides this mode for lazy acknowledgement, but ActiveMatrix BusinessWorks acknowledges messages upon receipt.

  • TIBCO EMS Explicit : (only available for TIBCO Enterprise Message Service) a message which is not acknowledged using the Confirm activity before the process instance ends, are redelivered instead of all messages in the session. The session is not blocked and one session handles all incoming messages for each process instance.

  • Note: In the ActiveMatrix BusinessWorks 5.10 release, a change occurs in the behavior of this feature. Now only the messages that are not confirmed, are redelivered.
  • TIBCO EMS Explicit Dups OK : (only available for TIBCO Enterprise Message Service) a message which is not acknowledged using the Confirm activity before the process instance ends, are redelivered instead of all messages in the session. The session is not blocked and one session handles all the incoming messages for each process instance. The messages however, would be lazily acknowledged.

Max Sessions

No

This field is available when Client is selected as the Acknowledge Mode. If the JMS Destination Type is Topic, this field is read-only. If the JMS Destination Type is Queue, the value of this field can be altered.

This field specifies the maximum number of JMS sessions to create for incoming queue messages.

When a JMS queue message is received, the session is blocked until the message is acknowledged. Because the acknowledgement can comes at a later time when the process ends, this field allows you to specify a maximum number of new sessions to create to handle incoming messages.

Once the maximum number of sessions is reached, no new incoming messages can be processed. Once an incoming message is confirmed, the total number of active sessions is decreased and another incoming message can be processed.

JMS Application Properties

 

Any application-specific message properties that are part of the message. This is specified by the JMS Application Properties shared configuration object.

Enable W3C SOAP JMS 1.0 Compliance

No

Select the check box to enable the W3C SOAP Over JMS 1.0 specification.

By default, the check box is not selected and the service complies with the TIBCO specifications.

Target Service

No

This field is available only when the check box Enable W3C SOAP JMS 1.0 Compliance is selected.

Specify the target service value, if any.

Note: If Target Service is configured, it’s value is reflected in the WSDL as a query parameter.