Connect JMS form
Completing the Service tab

Field

Description

To use resource references to identify the JMS resources, select Resource Reference. Otherwise, select Direct JNDI Lookup. See the Pega Developer Network article PRKB-25070 How to configure a JMS service or connector to find JMS resources through resource references for information about this choice.

If you selected Direct JNDI Lookup in the Resource Name Resolution field, select the name of a JNDI server data object (instance of Data-Admin-Connect-JNDIServer) that contains environment settings for the JNDI server. The JNDI server looks up the JMS provider through its Environment Naming Context (ENC).

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyJNDIServer. For more information, see Using the Global Resource Settings feature.

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 pyConnectionFactory. For more information, see Using the Global Resource Settings feature.

Select a JMS Producer Model data instance that defines message characteristics.

Field

Description

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 pyDestination. For more information, see Using the Global Resource Settings feature.

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.

Select the message type, one of the five choices in the JMS API standard:

• Text — A Java String, a java.language.String object.
• Map — A list of names and corresponding values. The names are Java String objects and the values are Java String objects or Java primitive data types.
• Byte — A stream of bytes with no explicit structure.
• Stream — Contents of a Java I/O stream, a stream of primitive values, filled and read sequentially.
• Object — A serialized Java object.

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.

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 Point-to-Point.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyDestinationResponse. For more information, see Using the Global Resource Settings feature.

Optional. Enter a positive number of seconds after which the Connect-JMS method returns even when no response is received.

Field

Description

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.

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.

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.

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. The 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.

Click to create a simulator for this connect rule. See Creating connect simulators.