From tabs where you specify a message (e.g., Request, Response, Payload), you can use the Views or Input Mode drop-down list to specify how you want to enter the message.
You can choose from the following options:
- Form Input View Options
- Form XML View Options
- Form JSON View Options
- Literal View Options
- Scripted View Options
- MapMessage Input Options
- Table Input Options
- Form ISO 8583 View Options
- Multiple Responses View Options
Views and Input Modes Overview
Form Input
Use this option to enter parameters in UI form fields. The form input enables a simpler way to view and work with an existing message (e.g., a sample from developers, traced from the server,etc.). Once a message is copied into the Literal view, the Form Input view is populated in a schema-aware and schema-constrained manner. This makes it much simpler to edit, manage, and parameterize.
See Form Input View Options for details.
Form XML
Use this option to configure XML messages via a tree view of the XML requests and responses. The form XML input helps you visualize the XML loosely without schema constraints and therefore gain the ultimate flexibility in constructing the message (but without the service-specific power of Form Input).
See Form XML View Options for details.
Form JSON
Use this option to configure JSON messages via a tree view.
See Form JSON View Options for details.
Literal
Use this option to work directly with the message. The literal view provides a simpler way to view and work with an existing message (e.g., a sample from developers, traced from the server, etc.). Once a message is copied into the Literal view, the Form Input view is populated in a schema-aware and schema-constrained manner. This makes it much simpler to edit, manage, and parameterize.
See Literal View Options for details.
Scripted
Use this option to dynamically generate the message from a script.
See Scripted View Options for details.
MapMessage Input
Use this option to specify input in a Messaging Client tool when JMS is selected as the Transport type, and javax.jms.MapMessage is chosen as the MessageType. See MapMessage Input Options for details.
Table
Use this option to post form parameters in the REST Client and Messaging client Request/Payload tab.
See Table Input Options for details.
