Before being able to define business transactions a corresponding application must have been defined which the business transaction should belong to. The page Defining Applications describes how to create application definitions.
...
When requests are evaluated to find the business transaction they should be assigned to, the business transaction definitions are processed in the same order as shown in the table. If the evaluation identifies a matching business transaction for a request, all subsequent business transaction definitions are not considered anymore for the corresponding request. This is not a problem if the matching rules of the differnet business transaction definitions are unabiguous. However, if this is not the case and the rules of one business transaction definition cover the rules of another business transaction definition, then the order of business transaction definitions is important.
| Info | ||
|---|---|---|
| ||
Position business transaction definitions with rather generic |
...
rules below |
...
business transaction definitions with rather specific rules! |
Lets assume we have two business transaction definitions in the following order and having following matching rules:
- Browse: GET HTTP request to /dvdstore/browse
- Search: POST HTTP request to /dvdstore/browse with HTTP parameter "SearchForm" having the value "SearchForm"
...