Connect JMS form
|
Use the Request tab to specify the contents of the outgoing request message. At runtime, Process Commander maps the data from the clipboard (or other sources) to fields of the message header, message body, and parameter values.
Field |
Description |
Field |
Optional. Select a message header field
( |
Description |
Enter a text description. |
Map From |
Select how the system creates the selected request header value:
If more choices appear, they identify a custom function rule
in a |
Map From Key |
If the Map From value
is If the Map From value is
|
Complete this section to define how Process Commander is to assemble property values and literal values to form the request message.
Field |
Description |
||||||||||
Data Type |
Select the external Java data type of
the parameter value: |
||||||||||
Name |
Enter a property reference that is the source of the value. |
||||||||||
Description |
Optional. Enter a short text description of this row of the array. |
||||||||||
Map From |
Select how the system creates request parameter values. The choice you make for this field depends on what you selected for Data Type:
If more choices appear, they each identify a custom function
rule in a |
||||||||||
Map From Key |
Enter additional details that complete the Map From mapping:
|
Complete this section to identify the sources and
mappings for the JMS request parameters. Working in the same way as the
Message Properties section, this section provides two
additional data types: Bytes
and JavaObject
.
VAGUE what's diff between Byte and Bytes