IBM DataPower Operations Dashboard v1.0.10.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Deprecated Extended Transactions
- Copy Page Tree
- Sara Weisz
- Former user (Deleted)
The intrusive Extended Transaction functionality will be deprecated in the near future
Extended Transactions are defined by the administrator over a web service proxy.
DPOD allows correlation between transactions across domains. This correlation is defined by means of a correlation id.
Examples of extended transactions include:
- A DMZ DataPower relays a request into the LAN internal DataPower. The request transcends two machines and would have consists of two separate transactions. With a DPOD Extended Transaction, you can treat this operation as a single one.
- An extended transaction may span domains inside a single DataPower machine or across several machines.
The following information is available for each extended transaction:
| Column | Description |
|---|---|
Service Name | The service this extended transaction ran on |
Operation | The operation’s name for this extended transaction |
Time | Timestamp for the extended transaction. This will be the timestamp for the last response within the extended transaction |
Status | The status for the extended transaction. The possible values are
|
Error Message | When the extended transaction completed in an error state, this column will hold the error message. |
Client IP | The client IP of the machine (or load balancer) where this transaction started. |
Elapsed (ms) | The number of milliseconds the extended transaction spanned. |
Click the 
icon to the left of an extended transaction to open a panel with the extended transaction’s correlation Id at the top, and extra information relating the single transactions comprising it:
| Column | Description |
|---|---|
Service Name | The service this transaction ran on. This may be the same service name listed for the extended transaction, or a different service name. |
Rule | The type of the transaction within the extended transaction. The possible values are:
|
Device Name | The device this transaction ran on |
Status | The status for this transaction. The possible values are:
|
Domain | The domain the transaction ran on |
Time | Timestamp for the transaction. |
Transaction Id | The Transaction id. Click on the transaction id to open a single transaction view for this transaction |
Error Message | If the transaction ended in an error state, this column will hold the error message received. If the error message is too long, it will be abbreviated, |
Elapsed (ms) | The number of milliseconds the transaction took. |