Share via

3.3.1 Abstract Data Model

  • Article

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This specification does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this specification.

It is possible to implement the conceptual data defined in this section using a variety of techniques. An implementation is at liberty to implement such data in any way it pleases.

The Management Server MUST maintain all the data elements specified in section 3.1.1. The Management Server MUST also maintain the following data elements:

  • Management Server Name: A Name object identifying the Management Server with the underlying OleTx Transports Protocol [MS-CMPO] transport infrastructure.

  • Show Limit: An unsigned integer value specifying the minimum age a transaction MUST have to be reported to the Management Client. This is common to all connections in the Management Connection List.

  • Update Limit: An unsigned integer value specifying the Update Timer value. This is common to all connections in the Management Connection List.

  • Trace Limit: A field that MUST have one of the values in TRACE_LEVEL, and specifies what level a trace event MUST have to be reported to the Management Client. This is common to all connections in the Management Connection List.

  • Management Connection List: A list of CONNTYPE_TXUSER_DTCUIC connections.

  • Tracked Transaction List: A list of transaction objects.

  • Open Transactions: A 4-byte unsigned integer indicating the number of currently opened transactions.

  • Committed Transactions: A 4-byte unsigned integer indicating the current number of committed transactions.

  • Aborted Transactions: A 4-byte unsigned integer indicating the current number of aborted transactions.

  • In Doubt Transactions: A 4-byte unsigned integer indicating the current number of in-doubt transactions.

  • Heuristic: A 4-byte reserved field that MUST be set to 0x00000000.

  • Open Max Transactions: A 4-byte unsigned integer indicating the maximum value of the Open Transactions field since the transaction manager was started.

  • Committed Max Transactions: A 4-byte unsigned integer indicating the maximum value of the Committed Transactions field since the transaction manager was started.

  • Aborted Max Transactions: A 4-byte unsigned integer indicating the maximum value of the Aborted Transactions field since the transaction manager was started.

  • In Doubt Max Transactions: A 4-byte unsigned integer indicating the maximum value of the In Doubt Transactions field since the transaction manager was started.

  • Heuristic Max: A 4-byte reserved field that MUST be set to 0x00000000.

  • Forced Commit Transactions: A 4-byte unsigned integer indicating the current number of transactions that were in doubt and were forced to commit.

  • Forced Abort Transactions: A 4-byte unsigned integer indicating the current number of transactions that were in doubt and were forced to abort.

  • Avg Response Time: A 4-byte unsigned integer indicating the current average time in milliseconds for committing a transaction.

  • Min Response Time: A 4-byte unsigned integer indicating the current minimum time in milliseconds for committing a transaction.

  • Max Response Time: A 4-byte unsigned integer indicating the current maximum time in milliseconds for committing a transaction.

  • Time Transactions Up: This field SHOULD contain an unsigned 4-byte integer <6> that specifies the number of seconds that elapsed from a baseline time to when the service was started.

  • System Time Transactions Up: A SYSTEMTIME structure (as specified in [MS-DTYP] section 2.3.13) indicating the time the service was started.

  • Time Stamp: A 4-byte unsigned reserved field that MUST be set to 0x00000000.

  • Single Phase In Doubt: A 4-byte unsigned integer indicating the current number of transactions that have entered the single-phase in-doubt state.