The Delimited Text data protocol lets you parse delimited textual data into arguments and values. This protocol takes the body of the request or response, parses it, and then replaces the body with an XML representation of the parsed data. For example:
“name1=val1;name2=val2”
becomes:
<name1>val1</name1><name2>val2</name2>
Follow these steps:
Defines the delimiter between the name/value pairs and the delimiter between the name and value. For example, for the following data:
"name1=val1,name2=val2,name3=val3"
the delimiter between the pairs is a comma, and the delimiter between the name and value is an equal sign.
Defines the delimiter between the values.You can use two types of lists:
For example, for the following data:
"val1,val2,val3,val4"
the delimiter is a comma.The parameters are named positionally.
The parameters are named positionally.
Defines (as a whole number) the width of the data field. The parameters are named positionally.
Defines a regular expression that locates the values. For example, for the following data:
"xxxx123xxx456xx789"
a RegEx of \d\d\d finds “123”, “456”, and “789” as values and discard the rest.The parameters are named positionally.
Defines the location of a field names document, which is a line-delimited document that specifies an ordered list of the names of fields. By default, the fields are named value1, value2, value3, and so on. To specify different names for those XML elements, use a field names document.
Defines the delimiter type used to separate name/value pairs and lists of values. Text or hex delimiters are automatically selected based the specified delimiter.
Values: Any alphanumeric characters, and the following:
You can also use hexadecimal notation to specify delimiters.
Note: You can only use delimiters that are valid XML 1.0. Specifying non-printable control characters makes the service image unusable.
Specifies whether to add parameters and associated values to requests as arguments.
Values:
Note: This check box has no effect when the Delimited Text data protocol is used on the response side.
The name/value pairs are represented in XML. Here, you can double-click a transaction to show the contents of that transaction.
You can see the virtual service image and the payload that is converted to XML when the processing completes.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|