Service JMS form
|
If the JMS service uses the Point-to-Point
messaging
model and the request messages will have a queue or topic specified in
their JMSReplyTo
header fields, use the Response tab to specify how the service rule constructs
the response to be sent. You can set up more than one response, based on
conditions. (If the JMS service uses the Publish-Subscribe
messaging model, responses are not expected; leave this tab blank.)
The list of response conditions is evaluated in order, and the first
condition that evaluates to true
determines the response
data returned to the client. The system sends responses to the queue
specified in the JMSReplyTo
header value in the request
message.
Field |
Description |
Response Condition | |
Condition |
Specify conditions that determine the format and content of the response message.
|
When Key |
Optional. If the
Condition value is For example, your service activity can set a property value to 0 initially, and to a positive integer when it detects any application-related issues. The when condition rule can test whether the property has a non-zero value. TANDP 9/2/05 |
Message Type |
B-17206 Select the type of the response:
|
Requestor Options |
Indicate whether the system is to keep this requestor session open, or close it after it sends the response message for this condition. If the requestor session is left open, the client
application can reuse this requestor session by referencing
it in the |
Click the triangle to access these fields. If the response is to include JMS headers, complete the fields in this section.
Field |
Description |
Name |
Select the type of JMS message header:
|
Description |
Enter a short description of the header. |
Map From |
Specify the source or the type of source of the value in your application:
If more choices appear, they each identify a custom
function rule in a |
Map From Key |
Specify the key to locating the property or rule in the source specified in the Map From field:
|
Use the fields in this section to map data for any JMS properties defined by the application sending the request.
Process Commander provides four application-specific JMS properties that contain information for response messages. (See More about JMS Listeners for details on these properties.) Do not map the values of those properties — they are managed by the listener and are included only when necessary.
Field |
Description |
Data Type |
Select the data type
of the message property, one of the Java primitive data types
|
Description |
Enter a short description of the message property. |
Map From |
Specify the source or the type of source of the value in Process Commander. See the options described above for the Message Header section. |
Map From Key |
Specify the key to locating the property or rule in the source specified in the Map From field. See the options listed above for the Message Header section. |
Use the fields in this section to define the body of the response message. Note the following: B-20128 Wizard
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 |
Select the data type
of the item you are mapping, one of the Java primitive data
types |
Description |
Enter a short description of the item you are mapping. |
Map From |
Specify the source or the type of source of the value in Process Commander. See the options above for the Message Header section. |
Map From Key |
Specify the key to locating the property or rule in the source specified in the Map From field. See the options listed above for the Message Header section. If this is a |