Rule configuration options

There are several possible permutations to Data Parser rules. Values are returned in the order they are found in the buffer.

Setting	Description
`Action`	For all rules in DataParser, the Action must be set to `Search`. This setting avoids confusion with other types of actions allowed by other session agents.
`SearchType`	The search type can have one of two values: `Single Pass` uses normal text searching methods to collect strings from the buffer. `XML` uses a separate XSL transform to do all data manipulation. XSL transforms are powerful but very slow to execute. XSL usage is not recommended in high-traffic environments.
`DisplayName`	This setting is the name used in the name/value pair, if the pattern is found.
`SearchString`	This setting is the pattern for which you wish to search in the buffer. StartPattern can also be used.
`Regular expression`	Denotes the regular expression used, if the SearchString pattern is found. `regular expression=` and `regex=` are recognized in rules configuration. Look-behind expressions of unfixed length are not supported. If you need to use an expression like `(?<=start).*end`, then you must denote the number of chars you want to capture explicitly. Example: `(?<=start). {1,200} end` Note: If a regular expression is supplied and does not match the text found after the SearchString is found, no name/value pair appears in the REQ buffer.
`SearchURL`	The URL on which to fire for this action. If no SearchURL is specified, the action fires on all hits.
`EndTag`	Denotes an end tag character sequence that terminates the collection of characters. You can use an end tag and a regular expression to collect and then clean up a character string. EndPattern can also be used.
`MD5`	Set this value to `True` to apply MD5 to the final value, after the regular expressions and end tags are applied. Note: Only the value is MD5-encoded. The DisplayName is not.
`Section`	This setting denotes whether to search the REQ or RSP buffer. Only two case-sensitive values are accepted: `Response` or `Request`. If no value is provided, the RSP buffer is used by default.
`DelimMatches`	When set to `True`, Data Parser puts all the matches found under the Display Name delimited by comma by default. You can provide a different delimiter in the Delimiter setting.
`Delimiter`	The user-defined delimiter used when DelimMatches is set to `True`. If it is not specified, the delimiter is set to comma. Note: If multiple search patterns are found from the same rule, the DataParser numbers them and puts them in the REQ buffer in the order they are found. For example, if multiple `Title` searches returned results, the output looks like the following: `Title=firstfind Title2=secondfind Title3=thirdfind`
`RegGroup`	Optionally, you can specify the output and format of the regular expression matching based on groups in the regular expression. For example, if the regular expression is `(tom)(/sis)(/s.)(*)`, then specifying `RegGroup={g1}={g2`} returns the value `tom= is`. In this case, the second equals sign (`=`) is a literal and is passed through to the output.

Join the community

Academy

Session agent reference

Related articles

Join the community

Academy