Before you can create a Java Message Services connector, you must plan it. You gather information about the system the connector sends messages to and determine the data to send in the messages. For example, determine where the connector gets the data for the message (from which properties in which classes), and how you'll identify the JMS resources, either using a JNDI server data object or resource references.
After you obtain the information about the destination of messages and the data to send, choose names for the rules and data objects that make up the connector.
First, determine how you will use identify the JMS resources (connection factories, destinations, and so on) the service connector interacts with:
- Through resource references that you insert in the Pega Platform™ deployment descriptor file (either
web.xml). For more information, see How to configure a JMS service or connector to find JMS resources through resource references.
- By direct JNDI name lookup through a JNDI server data object (instance of Data-Admin-Connect-JNDIServer).
Use the following table to organize the information you need about the JMS resources (the external system) the JMS connector communicates with.
Name or Value
JNDI initial context factory class
Provider URL of the JNDI server
User name and password for connecting to the JNDI server that identifies the JMS provider, if necessary
Messaging model: point-to-point, or publish/subscribe
JMS connection factory class
Queue or topic name
Request message type of the messages to be sent
Choose names for the rules and data objects in your JMS connector and use the following table in to keep track of the names.
Rule or Data Object
Class rule for connector
Properties for connector
Class rule for connector activity
Properties for connector activity
Connector rule (Service Name)
JMS producer model
You are now ready to create the JMS connector. Continue to Creating JMS connectors.