...
The term "Message Responder" refers to all tools that send responses over HTTP, MQIBM MQ, JMS, or other/custom protocols. Custom Message Responders can support any message format that you are working with—for example, mainframe message formats, binary formats, or any other kind of proprietary custom message.
...
The Transport Header tab allows you to specify the HTTP, JMS, or MQ IBM MQ message header that will be returned with the response message. You can use table view or literal view.
...
Virtualize sets the outgoing (response) MQ IBM MQ message characterSet field to the same value as the incoming (request) IBM MQ message.
When sending responses with character data such as XML, CSV, fixed-length, or plain text, the "format", the MQ header type must be set to the value of the MQFMT_STRING constant, which is "MQSTR". This format header should be configured in the Message Responder’s Transport Header tab (in the MQ Headers table, add an entry with format set to MQSTR).
...
The response message will be encoded based on the MQ "characterSet" header field. By default, Virtualize automatically sets the characterSet field on the outgoing (response) IBM MQ message to the same value as the incoming (request) IBM MQ message. However, this character set can also be explicitly configured by adding a "characterSet" header in the Message Responder’s Transport Header tab.
...