JMS MDB Listener form – Completing the JMS Properties tab
Use the JMS Properties tab to set up the JMS configuration options for the listener, including the topic or queue and which messaging domain to use.
| Field | Description |
|---|---|
| Messaging Model | Specify which messaging model to use: Publish-and-Subscribe
or Point-to-Point. |
MDB Destination Properties
| Field | Description |
|---|---|
| Destination JDNI Name | Select or enter the name of the destination JNDI, which is used by the message-driven bean to look up the JMS destination. |
| Message selector | Optional. To filter messages, enter a JMS selection expression. A message
selector is a string whose syntax is based on a subset of the SQL 92 conditional
expression syntax. For details and examples, see the Javadoc documentation for the
Java class named javax.jms.Message. |
| Durable subscriber | If the messaging model is set to Publish and Subscribe,
select this check box to specify that the listener is a durable subscriber. |
Reply To Connection
Configure the fields in this section only if the messages delivered by this listener will
have a queue or topic specified in their JMSReplyTo header fields. In that
case, use these fields to specify the server to which to send the reply.
| Field | Description |
|---|---|
| Preference | Determines whether this listener, or the incoming messages, provide the
identity of the response destination:
|
| Resource name resolution | To use resource references to identify the Reply To
queue or topic, select Resource Reference. Otherwise, select
Direct JNDI Lookup. See the Pega Community article How to configure a JMS service or connector to find JMS resources through resource references for more information. |
| JNDI server | If you selected Direct JNDI Lookup in the Resource
name resolution field, select the JNDI server data instance (
Data-Admin-Connect-JNDIServer ) that will create a reply
connection if the JMSReplyTo header of the received message has a
value. This field supports the Global Resource Settings syntax (=
PageName.PropertyName ). The default property name for this
field is |
| Connection factory name | Select or enter the name of the JMS Connection Factory for the reply
connection. For example: This field supports the Global Resource Settings syntax (=
PageName.PropertyName ). The default property name for this
field is |
| Factory username | Optional. If the Connection Factory is to connect to the topic or queue
specified below as an authenticated user, enter the name of a valid user. This
field supports the Global Resource Settings syntax (=
PageName.PropertyName ). The default property name for this
field is |
| Factory password | Optional, but required if a user name is specified in the Factory
username field. Enter the password for the user that you identified in
the Factory username field. This field supports the
Global Resource Settings syntax (= PageName.PropertyName ). The
default property name for this field is |
| Response destination name | If the Preference field is set to
Listener and this listener is to send responses, specify the
destination of the response. If the messaging domain is
Publish-and-Subscribe, select the JMS Topic object from which
messages are to be received. If the messaging domain is
Point-to-Point, select the JMS Queue object from which messages
are to be received. This field supports the Global Resource Settings syntax (=
PageName.PropertyName ). The default property name for this
field is Click Message explorer to display a list of JMS messages, add a message, or remove a message. |
| Test connectivity | After you save the listener, click Test connectivity to
test whether Pega Platform can connect to the server identified
by the JNDI Server data instance selected in the JNDI server
field above. 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. |
MDB Generation
| Field | Description |
|---|---|
| Generate MDB | Click to generate an MDB component archive file that contains the descriptor
fragment for this listener.
After you generate the archive file, click the link and save the archive file in the file system. Next, follow the instructions in the Pega Community article Deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener in Pega 7. |
Previous topic JMS MDB Listener form – Completing the Listener Properties tab Next topic More about JMS MDB Listener data instances