...
Message Responders can receive and respond with any content over one of the supported virtual asset protocol/API deployment options—namely, HTTP, JMS and WebSphere MQ, or through a protocol/API that is handled by a custom extension (see Using Custom Transports, Message Formats, and Tools_Virt). By customizing Message Responder options, you can customize the behavior of the virtual assets—with different request/response use cases specified manually or via data sources, error conditions, delays, and so forth.
...
- Form Input
- Form XML View Options
- Literal View Options
- Scripted View Options
- Form JSON View Options
- 2021-09-02_10-58-50_Form ISO 8583 View Options
- Sequence Responses
Notes
- The form-based views allow you to build the response and parameterize values from a data source.
- If an operation selector is enabled in the Form Input or Form JSON view, you can use it to select the operation for your response. When you select an operation, the Form Input/JSON view will be populated with appropriate values and UI controls (e.g., radio buttons for booleans, different controls for numbers vs. integers, etc.).
- In Form Input mode, the operation selector will show all operations for which the associated service definition 1) defines the response as XML and 2) specifies an XML schema.
- In Form JSON mode, the operation selector will show all operations for which the associated service definition 1) defines the response as JSON and 2) specifies a JSON schema.
- In Multiple Responses mode, each possible response has its own correlation to the incoming request, static response message, and performance (time) options.
...
- Transport: Allows you to specify HTTP Headers, JMS message properties, or MQ message fields within the message that will determine whether or not the message is processed by this particular responder. See Transport Correlation for details.
- Request Body: Allows you to specify XPaths within the message that will determine whether or not the message is processed. See Request Body Correlation for details.
- HTTP URL Parameters (for RESTful services): Allows you to specify URL parameters that will determine whether or not the message is processed. You can configure the correlation to match all messages that include specific parameters (no matter what value they are set to), or only match messages where specific parameters are set to specific values). URL parameters can be repeated (you can have the same parameter set to different values). See URL Parameter Correlation for details.
- HTTP URL Path: Allows you to specify URL paths that will determine whether or not the message is processed. See URL Path Correlation for details.
- HTTP Methods: Allows you to specify HTTP methods that will determine whether or not the message is processed. See HTTP Method Correlation for details.
- Custom: Allows you to specify a custom responder correlation that is based on the return value of a custom method written using Java or scripting languages. See Custom Correlation for details.
- ISO 8583 Correlations: Allows you to specify correlations for ISO 8583 messages. See 2021-09-02_10-58-35_ Using ISO 8583 for details. These options are designed specifically for SOAP, Plain XML, and Literal Message Responders.
...
Allows you to configure packager files for ISO 8583. See Configure an ISO 8583 Message Packager for details. This option is designed specifically for SOAP and Plain XML Message Responders
...