Pega is in AWS cloud which is hosted by tomcat server. I installed amazon MQ in AWS cloud and integrated with Pega. All connections are successful while running connect-jms system throwing destination must be specified even though destination exists.
JMS destination.docx (1.64 MB)
@yerubandi ganesh The error happens because the Connect-JMS method is not picking up a destination at runtime, so it treats it as blank even if the connector rule shows one.
In your activity, set the destination directly on the step page you pass to Connect-JMS (ReqPage) before the Connect-JMS step.
Set ReqPage.pyDestination to the exact JNDI name of your queue (for example java:comp/env/jms/queue/first_queue).
Save, clear the requestor/session, and run the activity again so the updated page value is used.
Once pyDestination is present on the request page at execution time, the connector will send without the Destination must be specified error.