...
See Form XML View Options_SOA for details.
Form JSON
Use this option to configure JSON messages via a tree view.
See Form JSON View Options_SOA 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_SOA for details.
Scripted
Use this option to dynamically generate the message from a script.
See Scripted View Options_SOA 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.