Transport Tab
Transports specify the underlying communication characteristics for messages sent and received by adapter services. Normally, the activities of the ActiveEnterprise Adapter palette use the same transport configuration as the adapter service with which they are communicating. However, in some situations, you may want to override the transport configuration of the adapter service and use different transport parameters.
The Transport tab is available in activities in the ActiveEnterprise Adapter palette. This tab allows you to override the transport configuration of the adapter service. The Transport tab has different fields depending upon which transport is selected in the Transport Type field. The Transport tab describes the fields of the transport tab.
Field |
Global Var? |
Description |
||||||||||||||||||
Transport Type |
No |
The transport receives the incoming request. This is normally the transport used by the adapter service, but you can override this by specifying different transport parameters. The possible values for this field are:
The sub-sections of this table describe the fields that appear when each of these options is selected as the transport type. |
||||||||||||||||||
Tibrv Reliable TransportFor more information about these fields, see TIBCO Rendezvous documentation. |
||||||||||||||||||||
Subject |
Yes |
The subject of the incoming request. |
||||||||||||||||||
Service |
Yes |
The service parameter of the transport of the incoming request. |
||||||||||||||||||
Network |
Yes |
The network parameter of the transport of the incoming request. |
||||||||||||||||||
Daemon |
Yes |
The daemon parameter of the transport of the incoming request. |
||||||||||||||||||
SSL |
No |
Specifies that SSL should be used when connecting to the TIBCO Rendezvous daemon. For more information about configuring SSL parameters, see Configure SSL Button. |
||||||||||||||||||
Message Format |
Yes |
Specifies the message format for the message. This can be either AE message format or AE XML format. This field is only available on the Transport tab of the following activities:
|
||||||||||||||||||
Tibrv Certified TransportFor more information about these fields, see TIBCO Rendezvous documentation. |
||||||||||||||||||||
Subject |
Yes |
The subject of the incoming request. |
||||||||||||||||||
Service |
Yes |
The service parameter of the transport of the incoming request. |
||||||||||||||||||
Network |
Yes |
The network parameter of the transport of the incoming request. |
||||||||||||||||||
Daemon |
Yes |
The daemon parameter of the transport of the incoming request. |
||||||||||||||||||
SSL |
No |
Specifies that SSL should be used when connecting to the TIBCO Rendezvous daemon. For more information about configuring SSL parameters, see Configure SSL Button. |
||||||||||||||||||
CM Name |
Yes |
The CM name of the incoming request. |
||||||||||||||||||
PreRegister Listeners |
Yes |
This field is only available on activities that publish messages (for example, Invoke an Adapter Request Response Service or Publish to Adapter). This field specifies the cmname(s) of the certified subscriber(s). This allows the publisher to pre-register with any expected listeners. If multiple cmnames are specified, separate each cmname with a comma. |
||||||||||||||||||
Relay Agent |
Yes |
Name of the relay agent, if one is used. |
||||||||||||||||||
Ledger File |
Yes |
Name and location of the ledger file. Warning: ActiveMatrix BusinessWorks constructs the default value of this field from global variables and the Adapter Service configuration. The value of this field must result in a valid path on the filesystem where the process is run. You may need to modify the default value in this field or modify the global variables used in this field to make sure the field results in a valid filesystem path.
|
||||||||||||||||||
Sync Ledger |
Yes |
When checked, this specifies the ledger file should be kept synchronous (asynchronous ledger updates are performed, if this field is unchecked). |
||||||||||||||||||
Default Time Limit |
Yes |
The default message time limit for certified messages specified in milliseconds. |
||||||||||||||||||
Require Old Messages |
Yes |
Specifies that unconfirmed messages should be kept in the ledger file. |
||||||||||||||||||
Message Format |
Yes |
Specifies the message format for the message. This can be either AERV or XML. This field is only available on the Transport tab of the following activities:
|
||||||||||||||||||
Tibrv Certified Message Queue TransportFor more information about these fields, see TIBCO Rendezvous documentation. |
||||||||||||||||||||
Subject |
Yes |
The subject of the incoming request. |
||||||||||||||||||
Service |
Yes |
The service parameter of the transport of the incoming request. |
||||||||||||||||||
Network |
Yes |
The network parameter of the transport of the incoming request. |
||||||||||||||||||
Daemon |
Yes |
The daemon parameter of the transport of the incoming request. |
||||||||||||||||||
SSL |
No |
Specifies that SSL should be used when connecting to the TIBCO Rendezvous daemon. For more information about configuring SSL parameters, see Configure SSL Button. |
||||||||||||||||||
CMQ Name |
Yes |
The CMQ name of the incoming request. |
||||||||||||||||||
Complete Time |
Yes |
The amount of time (in seconds) the scheduler waits for a worker process to complete. If the worker process does not complete in the specified period, the scheduler reassigns the message to another worker. |
||||||||||||||||||
Scheduler Weight |
Yes |
The scheduler weight for the process engine. |
||||||||||||||||||
Scheduler Heartbeat |
Yes |
The scheduler heartbeat interval (in milliseconds). |
||||||||||||||||||
Scheduler Activation |
Yes |
The scheduler activation interval (in milliseconds). |
||||||||||||||||||
Worker Weight |
Yes |
The worker weight for the process engine. |
||||||||||||||||||
Worker Tasks |
Yes |
The maximum number of incoming adapter requests this process engine can accept. |
||||||||||||||||||
Message Format |
Yes |
Specifies the message format for the message. This can be either AERV or XML. This field is only available on the Transport tab of the following activities:
|
||||||||||||||||||
JMS Topic TransportFor more information about these fields, see TIBCO Enterprise Message Service documentation. |
||||||||||||||||||||
Topic |
Yes |
The topic name of the incoming request. |
||||||||||||||||||
Auto Confirm |
No |
Specifies whether the incoming request should be automatically confirmed. This field is only available for activities that receive messages (for example, Adapter Subscriber). If check box is not selected then the message gets acknowledged at a later point by using the Confirm activity. If the message is not confirmed before the process instance ends, the message is redelivered and a new process instance is created to handle the new incoming message. Ensure that your process definition confirms the message. |
||||||||||||||||||
Transactional |
No |
This field is only available for activities that receive messages (for example, Adapter Subscriber). Check this field when a transaction that can process JMS messages is included in the process definition and you want the incoming message to be a part of the transaction. Any reply or exception message associated with the incoming message is also part of the transaction. The message is acknowledged when the transaction commits. Checking this field disables the Auto Confirm field. For more information about creating transactions, see TIBCO ActiveMatrix BusinessWorks™ Process Design. |
||||||||||||||||||
Override Transaction |
No |
This field is only available for activities that publish messages (such as Publish to Adapter or Invoke an Adapter Request-Response Service). By default, ActiveEnterprise Adapter activities that are included in the appropriate transaction group are included in the transaction. Check this field if you want to exclude the activity from the transaction. |
||||||||||||||||||
Durable |
No |
Specifies whether the client making the request is a durable subscriber. The durable subscription name is a concatenation of the process definition name and the name of the activity. This field is only available on the Transport tab of the following activities:
|
||||||||||||||||||
Durable Name |
No |
When the Durable field is checked, you can specify the name of the durable subscription that is registered with the JMS server in this field. This field is only available when the Durable field is checked. |
||||||||||||||||||
Delivery Mode |
No |
This field is only available on the Transport tab of the Publish to Adapter or Invoke an Adapter Request-Response Service activities. This field specifies the delivery mode of the published message. This can be either persistent or non-persistent. |
||||||||||||||||||
Time To Live |
Yes |
This field is only available on the Transport tab of the Publish to Adapter or Invoke an Adapter Request-Response Service activities. This field specifies the expiration time (in milliseconds) for the message. Specifying zero signifies the message should never expire. |
||||||||||||||||||
JNDI Lookups |
No |
Specifies that references to the JMS objects (ConnectionFactory, Topic, and so on) should be obtained from a JNDI server. |
||||||||||||||||||
SSL |
No |
Specifies that SSL should be used when connecting to the JMS server. For more information about configuring SSL parameters, see Configure SSL Button. |
||||||||||||||||||
Topic Connection Factory Name |
Yes |
Specifies the Topic ConnectionFactory object. |
||||||||||||||||||
Connection User Name |
Yes |
The user name to use when connecting to the JMS server. |
||||||||||||||||||
Password |
Yes |
The password to use when connecting to the JMS server. |
||||||||||||||||||
Provider URL |
Yes |
The URL for the JMS server. |
||||||||||||||||||
JMS Application Properties |
No |
Any application-specific message properties that is part of the message. This is specified by the JMS Application Properties shared configuration resource. Once specified, these properties appear on the Input or Output tab as "OtherProperties". |
||||||||||||||||||
Transacted Session |
Yes |
Specifies if the AE Event Source is a part of a transaction. When selected, this field disables Transactional and Auto Confirm. The fields Precreate Transactions and XA Transaction Manager is not visible. |
||||||||||||||||||
Precreate Transactions |
Yes |
When selected this field specifies that the transaction is created before a message arrives at the JMS receiver. This field is available when Transactional field is selected. Note: The Precreate Transactions feature should be used only with IBM MQ Websphere.
|
||||||||||||||||||
XA Transaction Manager |
Yes |
Specifies the XA Transaction Manager Configuration used to create the XA transaction. This field is available when Precreate Transactions field is selected. |
||||||||||||||||||
JMS Queue TransportFor more information about these fields, see TIBCO Enterprise Message Service documentation. |
||||||||||||||||||||
Queue |
Yes |
The queue name of the incoming request. |
||||||||||||||||||
Delivery Mode |
No |
This field is only available on the Transport tab of the Publish to Adapter or Invoke an Adapter Request-Response Service activities. This field specifies the delivery mode of the published message. This can be either persistent or non-persistent. |
||||||||||||||||||
Time To Live |
Yes |
This field is only available on the Transport tab of the Publish to Adapter or Invoke an Adapter Request-Response Service activities. This field specifies the expiration time (in milliseconds) for the message. Specifying zero signifies the message should never expire. |
||||||||||||||||||
Transactional |
No |
This field is only available for activities that receive messages (for example, Adapter Subscriber). Check this field when a transaction that can process JMS messages is included in the process definition and you want the incoming message to be a part of the transaction. Any reply or exception message associated with the incoming message is also part of the transaction. The message is acknowledged when the transaction commits. Checking this field disables the Auto Confirm field. For more information about creating transactions. see TIBCO ActiveMatrix BusinessWorks™ Process Design. |
||||||||||||||||||
Override Transaction |
No |
This field is only available for activities that publish messages (such as Publish to Adapter or Invoke an Adapter Request-Response Service). By default, ActiveEnterprise Adapter activities that are included in the appropriate transaction group are included in the transaction. Check this field if you want to exclude the activity from the transaction. |
||||||||||||||||||
JNDI Lookups |
No |
Specifies that references to the JMS objects (ConnectionFactory, Queue, and so on) should be obtained from a JNDI server. |
||||||||||||||||||
SSL |
No |
Specifies that SSL should be used when connecting to the JMS server. For more information about configuring SSL parameters, see Configure SSL Button. |
||||||||||||||||||
Queue Connection Factory Name |
Yes |
Specifies the Queue ConnectionFactory object. |
||||||||||||||||||
Connection User Name |
Yes |
The user name to use when connecting to the JMS server. |
||||||||||||||||||
Password |
Yes |
The password to use when connecting to the JMS server. |
||||||||||||||||||
Provider URL |
Yes |
The URL for the JMS server. |
||||||||||||||||||
JMS Application Properties |
No |
Any application-specific message properties that will be part of the message. This is specified by the JMS Application Properties shared configuration resource. Once specified, these properties appear on the Input or Output tab as "OtherProperties". |
||||||||||||||||||
Transacted Session |
No |
Specifies if the AE Event Source is a part of a transaction. When checked, this field disables the Precreate Transactions at the receiver and the fields Precreate Transactions and XA Transaction Manager Reference are not visible. |
||||||||||||||||||
Precreate Transactions |
Yes |
When checked, this field specifies that the transaction is created before a message arrives at the JMS receiver. This field is available when Transactional field is selected. Note: The Precreate Transactions feature should be used only with IBM MQ Websphere.
|
||||||||||||||||||
XA Transaction Manager Reference |
Yes |
Specifies the XA Transaction Manager Configuration used to create the XA transaction. This field is available when Precreate Transactions field is selected. |