When you click a transaction’s id in the transactions widget, DPOD loads the full details of the transaction into the information window.
...
This information is identical to the information displayed for the transaction in the DataPower Transactions table.
Previous/Next
...
buttons
If you navigate to this page from a transactions list that contains more than one transaction in the transactions list widget only). If a previous and next transaction exist -, previous/next buttons will appear to quickly move to the next and previous transactions (might be only forward or only backward of course at the beginning or end of the list)or previous transaction on that list.
The Size size of next/previous transaction transactions results can be defined in the System Parameters list.
Transaction Analysis Widget
...
Displays the request and response size.
This data is only available since IDG firmware 7.6.0.8 and 7.7.1.2 for transactions of traditional IDG services.
Memory
Memory consumption graphs for the request and response parts of the transaction, across the transaction lifetime and state changes.
...
The memory graph displays the differences in memory usage values in KB.
Raw Messages Tab
This widget lists the raw messages that make up the single transaction viewed (up to 2000 messages).
...
| Column | Description |
|---|---|
Category | The message’s category |
Severity | The message’s severity |
Time | The message’s timestamp |
Direction | The message’s direction. This may be:
|
Object Type | The object type associated with this message |
Object Name | The object name associated with this message |
Client IP | The Client IP this message originated from. This may be the actual client, or a load balancer. |
Message Code | The message’s code |
Message | The actual message logged. |
Payload Tab
When WS-M recording is switched on, the Payload pane of the table will contain payload information for the messages displayed.
The payload is shown for both the front end and the back end, for both the request and response phases.
Extended Latency Tab
...
. |
...
Side Calls Tab
The side calls tab shows calls made by the DataPower to external resources during the transaction, such as SQL calls, LDAP, HTTP requests, SOAP requests, FTP calls, MQ calls, etc.
...
| Column | Description |
|---|---|
| Type | The call type - such as SQL, LDAP, etc. |
| Direction | request or response |
| Time | When the call was made |
| Elapsed (ms.) | Elapsed time of the call in milliseconds |
| Status | Whether the call was successful or not |
| Details | Additional details about the call, such as the SQL statement, HTTP request URL, etc |
Correlated Transactions Tab
The Correlated Transactions Tab (Appears only if the user has appropriate permissions), shows all the transactions with the same Global Transaction ID, both Gateway transactions and API-C transactions are shown.
The transactions are sorted by their start time, where the first transaction that run appears on top..
...
Clicking on the Raw Errors links (appears only if the transaction did have any errors, and only if the user has appropriate permissions) will open a window with the all the transactions' error messages, note that the existence of error messages doesn't necessarily mean that the transaction failed.
Side Calls Tab
The side calls tab shows calls made by the DataPower to external resources during the transaction, such as SQL calls, LDAP, HTTP requests, SOAP requests, FTP calls, MQ calls, etc.
| Column | Description |
|---|---|
| Type | The call type - such as SQL, LDAP, etc. |
| Direction | request or response |
| Time | When the call was made |
| Elapsed (ms.) | Elapsed time of the call in milliseconds |
| Status | Whether the call was successful or not |
| Details | Additional details about the call, such as the SQL statement, HTTP request URL, etc |
Payload Tab
When payload is captured for this transaction, the Payload pane of the table will contain payload information for the messages displayed.
The payload is shown for both the front end and the back end (when applicable), for both the request and response.
A link to Payload Capture will appear if payload does not exist.
Extended Latency Tab
Detailed latency information for both the request and response phases.