Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Sequence transactions in DC RUM 2017

Applies to DC RUM 2017

You can manage the sequence transactions (operation sequences) that are defined on an individual AMD or manage each transaction that is monitored by a group of AMDs.

Viewing all defined sequence transactions

To view all transactions, open the Sequence transactions screen.

  • In the RUM Console, select Configuration ► Sequence Transactions
  • In the CAS, select Reporting and alerting ► Sequence transactions

In the Sequence transactions screen:

  • Click in the Sequence Transactions list and then type the first letters of a sequenced transaction name to find a sequenced transaction whose name matches what you have typed.
  • Click the magnifying glass icon or press [CTRL+F] to open a search box to limit the table view to only those rows that contain a match (in any column) to the search string.

For each transaction, the following information is shown:

  • Sequence Transaction Name
    The name of a transaction.
  • Application
    The application that includes the listed transaction.
  • Type
    The protocol used to define the listed transaction: ASYNC-HTTP, HTTP, OF, SAP GUI, SQL or XML.

Viewing sequence transaction details

On the Sequence Transactions screen, select Actions ► Edit for a transaction to open the Edit Transaction window and examine the steps that make up the transaction. The listed details are as follow:

  • Application - address
  • Name - name
  • Description - text description
  • Timeout - seconds after which the transaction is designated as timed out
  • Slow after - milliseconds after which the transaction is designated as slow
  • Priority - 1, 2, or 3
  • URL - the URL identifying the transaction
  • Timeout
  • Repetition

Managing existing sequence transactions

To manage all of the defined transactions, use the Sequence Transactions screen.

  • To create new transactions, click Add Sequence Transaction. The Create Sequence Transaction screen appears, where you can select the AMD devices that will monitor this new transaction.
  • To edit a transaction, select Actions ► Edit for that transaction.
  • To copy a transaction to another device, select Actions ► Copy for that transaction.
  • To delete a transaction, select Actions ► Delete for that transaction.
    If the transaction you are deleting is monitored by more than one AMD, a new draft configuration must be published to all of the affected AMDs.

Viewing sequence transactions defined on an individual AMD

To view the defined transactions monitored by a single AMD:

  1. In the RUM Console, select Devices and Connections ► Manage Devices.
  2. Select Open configuration from the context menu for the AMD to access the AMD Configuration screen.
  3. Select Configuration ► Sequenced Transactions.

The main Sequenced Transactions table lists all of the currently defined transactions and their details:

Sequenced Transaction Name
The name of a transaction.

Application Name
The application that includes the listed transaction.

The protocol used to define the listed transaction.

The number of individual operations involved in the listed transaction.

The priority of the transaction. Possible values are 1 (highest priority), 2, and 3.

The maximum time for the transaction to complete.

Packaged Applications
Identifies whether the listed transaction is a packaged application whose transactions are recognized by the report server automatically.

Creating a sequenced transaction

Applies to DC RUM 2017

Transactions can be added to a number of AMDs at the same time.

To add a transaction to several AMDs:

  1. In the RUM Console, select Reporting Configuration ► Sequence Transactions.

  2. Click Add Sequence Transaction.

  3. Enter the transaction name and application names.

  4. From the Type list, select the analyzer type for the transaction.

  5. Select the check boxes for the AMDs to monitor this transaction and click OK to proceed to the transaction editor.

  6. Change the transaction and application names as needed.

  7. Provide the timing and priority values:

    • Timeout [s]
      The maximum time for the transaction to complete. Transaction execution time must stay within this time for the transaction to be logged as successful.

    • Slow after [ms]
      If the transaction execution time exceeds this value, the transaction is classified as slow. Specify this threshold in milliseconds. For example: 500 is half a second.

    • Priority
      Determines which transaction is recorded if two or more transaction definitions match the transaction detected in the monitored traffic. The valid priority values are 1 (highest priority), 2, and 3.

      You can use this feature to increase the priority of specific customized transaction definitions that should take precedence over more generic transaction templates.

      A multiple transaction match can happen if, for example, you first create a generic transaction definition that can match a number of more specific transactions and then you create another transaction definition that matches a particular sub-type of that generic transaction type. If an observed transaction is found to match the latter definition, it also matches the first (more generic) definition, and the system will need to determine under which transaction name to record the observed transaction instance. By increasing the priority of the second, more specific definition, you can count the occurrences of this particular transaction sub-type, which are then not counted in the statistics for the generic transaction type.

  8. Specify the operations that comprise the transaction steps.
    Depending on the transaction type, enter the following items to define the transaction steps:

    • HTTP Transaction
      URL - The URL can contain a contain optional wild-card character * or a regular expression.
    • XML Transaction
      XML Action - The XML action can contain a can contain a contain optional wild-card character *.
    • SAP GUI Transaction
      SAP GUI operation
    • Oracle Forms Transaction
      Oracle Forms operation - The Oracle Forms operation can contain an optional wildcard character *.
    • SQL Transaction (timer)
      SQL operation (command) and query type.

    Both SQL operation and query type can contain an optional wild-card character * to signify any number of any characters or a regular expression. You can use either of the two methods in one line. For example, you can use the regular expression based pattern for the query type, regex:rp[abc]$ and simple search pattern for the SQL operation, set*.

    To maintain the sequence of these operations, use the navigation buttons on the right.

    When using the regular expression in defining the HTTP, Oracle Forms and SQL transaction steps, you have to start the search string with the phrase regex: and follow it with a valid regular expression which is applied to the URL, Oracle Forms, SQL operation, or query type. Example: regex:http://monitored.server.corp:5000/of_html/abc?a=[123]&&a%20b.

    Using the wildcard character *, you can signify any number of any characters.

    You can Add, Delete, Move Up, Move Down, or Copy the defined steps by selecting the step and clicking one of these actions.

    You can also make changes in the table itself: click in any of the column cells to edit the values. Using the table, you can determine whether the selected operation is a request or a response and whether this particular operation may be repeated within this transaction.

  9. Click OK to add your transaction definition to a draft configuration.

  10. Return to the Sequence Transactions screen and click Publish Configuration.
    The configuration is sent to all of the selected devices.