Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2024.1

...

The path to the element is given starting at the root, down to the subjectFirstName element. The text value will then be used for the correlation. The XML-converted request can be viewed using the Event Details view to better help with constructing of XPaths.  See Gaining Visibility into Server Events for more information.

Defining Responses

There are several ways to configure Message Responders with the desired Equifax response messages. To ensure that the Equifax parser can successfully convert the XML formatted response to an Equifax-standard response, you will need to use XML format in the sample XML response file for all segments and fields.

  • If you have an existing Equifax response message (obtained from your application logs or other sources), you can take advantage of Virtualize's ability to convert to/from XML. This lets you copy an existing Equifax response into the Literal view and convert it to XML by switching to the Form XML view and back again. This enables scripting or parameterization of a desired Equifax response with a data source.
    • Note that this Equifax parser implementation uses the deprecated ICustomMessageConverter interface of the extension framework in order to enable conversion to/from XML. See the Extensibility API documentation for details.
  • If you have multiple existing response messages with an understanding of how to correlate them to request messages, then use the Multiple Responses option in the responder and paste each response message into the Message tab area of each response. Each response matching criteria needs to be set (as described in Defining Correlations). See Multiple Responses View Options for general information about entering multiple responses.

  • If you do not have existing Equifax messages or you prefer to model them from scratch (for example, the application does not yet exist, is not ready, or you cannot obtain samples), then use the schema available in the examples/listeners folder to construct a Form Input, then configure the fields. This approach provides awareness to the available (valid) fields, and it allows for advanced capabilities such as the use of array data sourcessources (as described in Parameterizing Tools with Data Source Values, Variables, and Extracted Values).