The Transports tab is used to view
different processing status for a specific transport such
as whether or not the transport has been initialized and
the number of times the transport successfully delivered
data. The information is valuable during runtime especially
when deciphering transport processing problems.
To use the Transports tab, follow these
steps:
- From the Workbench left pane, expand the node whose transports you want to review.
- Expand Enterprise, and then
click Transports.
The Transports tab appears in the right pane.
The following describes each column on the Transports tab:Name
This is the unique name of the transport. Click the Name heading to list the transports in ascending or descending alphabetical order.
Type
The type of transport: For example, TCP, WMQ (for WebSphere MQ), DB (for relational database), and SAP.
State
The state of the transport can be:
- Up — indicates that the transport software is operational and that data can be sent. The transport could be either successfully sending transactions or having errors sending them.
- Down — indicates that the transport has not been initialized. The state will change when the first transaction is sent out through this transport. For more information, click Suspending a transport.
- Store and Forward — applies to all transports except for TCP. In this state, the transport has encountered an error sending transactions to a remote message queue or database table and is storing the transactions for a later delivery. The node will periodically attempt to retransmit the transactions. When all the transactions have been sent, the State column will change to Up.
- Suspended — indicates that the transport cannot deliver transactions to its final destination even if that destination is reachable and services are up and running on the destination host. A suspended transport will attempt to store the transactions in store and forward if store and forward is enabled for that transport. A transport that has been suspended can be returned to its normal state by using the Resume menu from the Transports tab. For more information, click Suspending a transport.
- Disabled — indicates an unrecoverable error occurred in the transport. Because of the seriousness of the problem, the system disabled the transport to prevent any further processing. Once the problem is corrected, a disabled transport can be enabled by using the Enable menu from the Transports tab.
- S&F Suspended — indicates that the transport cannot deliver transactions to its final destination. However, the transport has store and forward enabled so that transactions will be saved into a store and forward queue.
Successes
Tracks the number of times the transport successfully delivered payload. During normal operations, this column should have a non-zero value. A transport can be referenced by many transactions making the number a higher level of accumulation.
Failures
The number of failures due to application errors incurred by the transport. For example, SQL exception, TCP communication error, and so forth. During normal operations, this column should have a zero value.
S/F Queued
The number of transactions currently in the store and forward queue for the transport. As these transactions are processed, this number will be decremented by 1, and the Successes column or the Failures column will be incremented as appropriate. During normal operations, this column should have a zero value.
S/F Deleted
The number of transactions dropped while in the store and forward mode (lost data).This is due to TTL (time to live) parameter violation or Max Storage parameter violation. The TTL parameter is available on database or WebSphere MQ transports. During normal operations, this column should have a zero value. If this column has a non-zero value, it is an indication that the store and forward configuration values (TTL and Max Storage parameters) should be analyzed and possibly increased.
Pending
The number of transactions currently in the internal pending queue for the transport. During normal operation, this column should be zero (most of the time) or a very small number.
Pending Queue Overflow
The number of transactions dropped due to the pending
queue full condition (lost data). If this column is
non-zero, it is an indication of a serious condition, such
as a trigger executing too frequently, a network outage,
and so forth, and should be addressed quickly. During
normal operations, this column should have a zero
value.
There are other features available from the
Transports tab. You can display a pop-up
menu that lets you create a new transport, delete an
unwanted transport, and more. The pop-up menu provides
these options:
For information about Edit and
Delete, see Editing a
transport and Deleting a
transport.
For information about Suspend and
Resume, click Suspending a
transport.
Deleting a
transport
For information about Import and
Export, click Exporting a
single transport, Exporting
multiple transports, and Importing
one or more transports.
For information about the Purge Store/Forward
queue menu, click Purging
data from store and forward.
The Enable menu is not available unless
the transport encounters a serious problem. If that is the
case, the State column on the
Transports tab indicates
Disabled (and the Enable
menu becomes available). Once the problem is corrected, you
can enable the flow of transactions by using the
Enable menu.
The Clear counters menu allows you to
clear the all columns on the Transports
tab.