Transport Type
The transport configuration in the Advanced tab of an activity specifies the underlying communication characteristics for messages sent and received by the adapter services.
Normally, activities in the Adapter palette use the same transport configuration as the adapter service that they are communicating with; however, you can override the transport configuration of the adapter service by specifying different transport parameters.
You can select a transport type by which the incoming request is received. The transport is used by the adapter service. The following options are available in the Transport Type list: Adapter Service default, Tibrv Reliable, Tibrv Certified, Tibrv Certified Message Queue, JMS Queue and JMS Topic. The default transport is based on the associated adapter service. You do not have to specify any parameter.
The transport types are grouped into two categories:
- TIBCO Rendezvous Transport
The TIBCO Rendezvous transport includes Tibrv Reliable, Tibrv Certified, and Tibrv Certified Message Queue.
To use the TIBCO Rendezvous transport when configuring the adapter activities and running the TIBCO ActiveMatrix BusinessWorks™ process on a UNIX platform, you can set the LD_LIBRARY_PATH and RV_HOME environment variables with the TIBCO Rendezvous library path in the Run Configuration dialog.
For more information, see the TIBCO Rendezvous documentation.
- JMS Transport
The JMS transport includes JMS Queue and JMS topic.
Different types of EMS connectivity are not supported when using the JMS transport. For example, if SSL is used, all connectivity using JMS must be configured as SSL. The same applies if non-SSL is used.
For more information, see the TIBCO Enterprise Message Service documentation.
Tibrv Reliable
The Tibrv Reliable transport has the following fields:
Field | Module Property? | Description |
---|---|---|
RV Connection | Yes | The TIBCO Rendezvous connection.
For more information, see "Rendezvous Transport" in TIBCO ActiveMatrix BusinessWorks™ Bindings and Palette Reference. |
Message Format | No | The format of the message. The format is AE_message_format or AE_XML_format. |
Subject | Yes | The subject of the incoming request. |
Tibrv Certified
The Tibrv Certified transport has the following fields:
Field | Module Property? | Description |
---|---|---|
RV Connection | Yes | The TIBCO Rendezvous connection.
For more information, see "Rendezvous Transport" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference. |
Message Format | No | The format of the message. The format is AE_message_format or AE_XML_format. |
Subject | Yes | The subject of the incoming request. |
PreRegister Listeners | No | The CM names of the certified subscribers. With preRegisterListener, the publisher can preregister with any expected listeners. If multiple CM names are specified, separate each one with a comma. |
Tibrv Certified Message Queue
- Adapter Request-Response Server
- Adapter Subscriber
- Wait For Adapter Message
- Wait For Adapter Request
The Tibrv Certified Message Queue transport has the following fields:
Field | Module Property? | Description |
---|---|---|
RV Connection | Yes | The TIBCO Rendezvous connection.
For more information, see "Rendezvous Transport" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference. |
Message Format | No | The format of the message. The format is AE_message_format or AE_XML_format. |
Subject | Yes | The subject of the incoming request. |
JMS Queue
The JMS Queue transport has the following fields:
Field | Module Property? | Description |
---|---|---|
JMS Connection | Yes | The JMS connection.
For more information, see "JMS Connection" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference. |
Destination | Yes | The destination object from which an incoming request is received. |
Delivery Mode | No | The delivery mode of the published message. This can be
persistent or
nonpersistent.
This field is only available for the Publish to Adapter and Invoke an Adapter Request-Response Server activities. |
Time to Live | Yes | The expiration time (in milliseconds) for the message. The value
zero (0) means that the message never expires.
This field is only available for the Publish to Adapter and Invoke an Adapter Request-Response Server activities. |
Override Transaction | No | If this check box is selected, the JMS message does not participate in the transaction.
Select this check box to exclude the JMS message from the transaction. Clear this check box to include the JMS message in the transaction This check box is only available for the Publish to Adapter and Invoke an Adapter Request-Response Server activities. |
JMS Application Properties | No | The message properties specific to the JMS application. |
Auto-generate Client ID | Yes | Select this field to automatically generate the Client ID. If a Client ID is not specified, or if the specified ID is already in use. When the Auto-generate Client ID checkbox is selected and a value is specified in the Client ID field, you are prompted to use the specified Client ID. However, if the specified value is already in use, a new Client ID is generated. If the Client ID field is not selected, then the value specified in the field is used. If no value is specified in the Client ID field, then a Client ID is automatically generated. If the value specified in the Client ID field is already in use, an exception occurs. |
Client ID | Yes | Client ID for the connection. Typically JMS providers have a provider-specific format for client IDs. For more information about Client IDs, see the Java Message Service (JMS) provider’s documentation. Each connection must use a unique Client ID. If you do not specify a value in this field, TIBCO ActiveMatrix BusinessWorks ensures the uniqueness of the Client ID for each connection. |
JMS Topic
The JMS Topic transport has the following fields:
Field | Module Property? | Description |
---|---|---|
JMS Connection | Yes | The JMS connection.
For more information, see "JMS Connection" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference. |
Destination | Yes | The destination object from which an incoming request is received. |
Durable | No | Select or clear this check box to specify whether the request is a durable subscriber.
The check box is available only for the following activities: |
Durable Name | No | The name of the durable subscription that is registered with the JMS server in this field.
This field is only available when the Durable check box is selected. |
Delivery Mode | No | The delivery mode of the published message. This can be
persistent or
nonpersistent.
This field is only available for the Publish to Adapter and Invoke an Adapter Request-Response Server activities. |
Time To Live | Yes | The expiration time (in milliseconds) for the message. The value
zero (0) means that the message never expires.
This field is only available for the Publish to Adapter and Invoke an Adapter Request-Response Server activities. |
Override Transaction | No | If this check box is selected, the JMS message does not participate in the transaction.
Select this check box to exclude the JMS message from the transaction. Clear this check box to include the JMS message in the transaction. This check box is only available for the Publish to Adapter and Invoke an Adapter Request-Response Server activities. |
JMS Application Properties | No | Any application-specific message property that is part of the message. |
Auto-generate Client ID | Yes | Select this field to automatically generate the Client ID. If a Client ID is not specified, or if the specified ID is already in use. When the Auto-generate Client ID checkbox is selected and a value is specified in the Client ID field, you are prompted to use the specified Client ID. However, if the specified value is already in use, a new Client ID is generated. If the Client ID field is not selected, then the value specified in the field is used. If no value is specified in the Client ID field, then a Client ID is automatically generated. If the value specified in the Client ID field is already in use, an exception occurs. |
Client ID | Yes | Client ID for the connection. Typically JMS providers have a provider-specific format for client IDs. For more information about Client IDs, see the Java Message Service (JMS) provider’s documentation. Each connection must use a unique Client ID. If you do not specify a value in this field, TIBCO ActiveMatrix BusinessWorks ensures the uniqueness of the Client ID for each connection. |