@Pankaj_C   this is our standard OOTB documentation about Messaging service overview  

Advanced Message Queuing Protocol (AMQP) is an open Internet Protocol for Business Messaging.     There is no OOTB way instead of using REST connectors.  The only mentioned methods are with Azure Service Bus using a JMS service.

You would use any Azure Service Bus with a connection string in the servicebus.properties file (connectionfactory).  The shared username and key is set in the factory username and password in the JMS properties tab of the Listener. The JAR files also need to be imported into the Pega application.

The request is to use the OASIS Advanced Message Queuing Protocol (AMQP) standard so PRPC can communicate with ESBs and MQ brokers that use AMQP in both JEE (etier) and tomcat (web tier) environments ie to add "AMQP Provider" as another choice of JMS provider for both connect and service JMS and create documentation on how to setup PRPC with both Qpid and RabbitMQ

Two major implementations of AMQP are RabbitMQ and ApacheQPid.  Of these two, RabbitMQ seems to be more popular, but does not have Java JMS Client implementation so in future there may be the use stand-alone Apache QPid JMS Client to test compatibility with RabbitMQ broker.

RabbitMQ (AMQP provider) has come up a couple of times with customers but details on installation techniques etc would need to be discussed with our Pega Consulting teams.  Technically it's possible to achieve a JMS integration.  We have OOTB support for RabbitMQ using RabbitMQ JMS Client but  there is a fair amount of configuration required.  (See forum posts here , here   ,  here  and here

Pega does not provide  support for integration to listen to Azure topics with any  out of the box methods

You may be able to find discussions on the forum from users who used either AMQP, REST protocol or Webhooks  (implemented using Data flow rule ) or you may wish to enlist the help of consultancy services if there is no further help on this archived post.