Connect JMS form
|
Contents |
Use the Service tab to identify the JMS provider, the destination system, and characteristics of the messages between Process Commander and the JMS provider.
Synchronous versus asynchronous operation
JMS connectors can either wait for a response (operate synchronously)
or post a message and end the connection without waiting for a response
(operate asynchronously). If you either select the Dynamic
Destination
option or select a value in the Destination
Name field and configure data mappings on the Response tab, the connector waits for a response message.
If the Response tab does not have data
mappings configured, the connector does not wait for a response, even if
you specify a response destination.
Field |
Description |
Service Properties | |
Resource Name Resolution |
To use resource references to identify the JMS resources,
select |
JNDI Server |
If you selected
This field supports the Global Resource Settings syntax
(=.PageName.PropertyName). The default property name for
this field is |
Connection Factory |
Select the appropriate JMS connection factory from the list. This field supports the Global Resource Settings syntax
(=.PageName.PropertyName). The default property name for
this field is |
Factory Username | If the connector needs to connect to the queue as an authenticated user, specify the username. PROJ-912 task 2813 |
Factory Password | If the connector needs to connect to the queue as an authenticated user, specify the password for the user you specified in the Factory Username field. PROJ-912 task 2813 |
JMS Producer Model |
Select a JMS Producer Model data instance that defines message characteristics. |
Field |
Description |
Request | |
Destination Name |
Identify the name of the destination — a JMS topic object or a JMS queue — to which the messages are to be addressed. This field supports the Global Resource Settings syntax
(=.PageName.PropertyName). The default property name for
this field is Click the pencil button () to inspect the queue. A window appears, listing any items in the queue. Click a message position number to display detailed information about that item. |
Request Message Type |
Select the message type, one of the five choices in the JMS API standard:
|
Response | |
Dynamic destination? |
8/4/05 B-13105 HITZM Select to specify that a temporary queue is to be created to hold the response message. When selected, leave the Destination Name field blank. When cleared, Process Commander uses the queue specified in the Destination Name field if there are data mappings configured on the Response tab. The connector obtains the Correlation ID from the message ID, unless the Correlation ID is mapped on the Request tab. Click the magnifying glass button () to inspect the queue. A window appears, listing any items in the queue. Click a message position number to display detailed information about that item. Proj-195 |
Destination Name |
8/4/05 B-13105 HITZM Optional. If your connector is to wait for a response and you are not using a dynamic destination, select the name of a queue or topic managed by the JMS provider identified by the Connection Factory field.
The JMS producer model
specified in the JMS Producer Model field must
be configured to use This field supports the Global Resource Settings syntax
(=.PageName.PropertyName). The default property name for
this field is |
Response Timeout (seconds) |
Optional. Enter a positive number of seconds after which the Connect-JMS method returns even when no response is received. B-16587 |
Field |
Description |
Error Handling | |
Status Value Property |
Optional. Select a property to hold the status of the remote service request. If the property is on the step page, start the property reference with a period. B-17161 validation |
Status Message Property |
Optional. Identify a property for providing more information about errors that occur when processing the remote service request. If the property is on the step page, start the property reference with a period. B-17161 validation |
Error Handler Flow |
C-1075 Optional. Identify a flow rule that is to be started when this connector rule is started by a flow rule but fails. The default flow rule Work-.ConnectionProblem provides one approach for handling such problems. See Handling connector exceptions. |
Test Connectivity |
After you complete at least the Service tab and Request tab, save the rule form and click Test Connectivity . Process Commander accesses the JNDI server and the producer model to connect to the JMS producer. C-1704The system presents test results in a separate window, identifying the parameters used in the test, the steps attempted, and the outcome of each step. It does not call the service. |
Simulations |
Click to create a simulator for this connect rule. See Creating connect simulators. |