|
|
Use the Request tab to map the incoming data to properties on the clipboard.
Field |
Description |
Message Type |
Specify the message type of the messages to be processed by this service rule:
|
Use the fields in this section to map any data of interest from the header fields of the JMS message.
Field |
Description |
Name |
|
Map To |
In unusual cases, select |
Map To Key |
You can map the data to the parameter page of the activity rather than the primary page by using the |
Use the fields in this section to map data from any JMS properties defined by the application sending the request.
PRPC provides four application-specific JMS properties that the sender can use to provide information about the messages consumed by JMS services. (See More about JMS Listeners for details on these properties.) You do not need to map the values of those properties — they are processed automatically.
Use this section to map message properties defined by the external application, not by PRPC.
Field |
Description |
Data Type |
|
Description |
Enter a short text description of the message property. |
Map To |
If more choices appear, they identify a custom function rule in a |
Map To Key |
|
Use the fields in this section to map the data from the body of the message. Note the following:
Empty Message
, do not create any rows in this section.Text Message
, include one row only in this section. The data type of the mapping must be set to String.Object Message
, include one row only in this section. The data type of the mapping must be set to Object.Stream Message
, create data mappings for each of the items in the stream in the order in which they will be received.
Field |
Description |
Data Type |
|
Message Key |
Applies only when the Message Type is set to |
Description |
Enter a short description of the item you are mapping. |
Map To |
|
Map To Key |
|