Press "Enter" to skip to content

WHINT AMQP Adapter (On-Premise)


Please note that our AMQP adapter has been deprecated and replaced by


This JCA Adapter for SAP Process Orchestration supports the Advanced Message Queuing Protocol (AMQP), a reliable way to establish a properly decoupled application integration using message queues and topics. AMQP defines both the network protocol and the server-side services through a defined set of message capabilities called AMQ model, which consist of a set of components that route and store messages within the broker service and a network wire-level protocol, that lets client applications talk to the server and interact with the AMQ model it implements.

It connects asynchronously to the followings Brokers by sending and receiving messages in a reliable way:

  • Microsoft Azure Service Bus (Cloud)
  • RabbitMQ (On-Premise/Cloud)


  • Works with SAP PI 7.1 and higher (incl. SAP Process Orchestration 7.50)
  • Deploy the SCA file provided by Whitepaper InterfaceDesign using NWDS/JSPM/SUM/Telnet
  • Import the TPZ file provided by Whitepaper InterfaceDesign into the ESR


  • Create a new sender or receiver communication channel and select the adapter “AMQP” from namespace “” (Software Component WHINT_AMQ 2016.04 of
  • Transport Protocol
    • Select one of the following transport protocols
      • MS Azure – to connect with a Microsoft Azure Service Bus
      • RabbitMQ – to connect with a RabbitMQ Broker
  • Message Protocol
    • The message procotcol is preselected based on the transport protocol. The following are available so far:
      • AMQP 1.0 – This is the message protocol for MS Azure
      • AMQP 0-9-1 – This is the message protocol for RabbitMQ
  • Other Options
    • Host & Port
    • Virtual Host (RabbitMQ)
    • SSL/TLS enabled
    • Queue / Exchange Name
    • Topic Support
      • Subscription ID (MS Azure)
      • Exchange Type: direct/headers/fanout/topic (RabbitMQ)
      • Routing Key (RabbitMQ)
    • Consuming Interval (secs/msecs)
    • Authentication based on User/Password
    • Quality of Service (EO/EOIO with queue name)
    • Set/Use Adapter-specific Message Attributes (ASMA)
      • Namespace:
      • externalMessageID – Message Id received from broker
      • CreateDateTime – Timestamp of message creation
      • QueueExchangeID – Name of the Queue / Exchange Name
      • RoutingKey (only RabbitMQ)
      • Custom Attributes
        • Receiver: can be set in Receiver Channel statically or dynamically
          • Each attribute must be listed (will be ignored otherwise) – when the value of an attribute is empty, the corresponding value is expected in the ASMA
        • Sender: all attributes will be set as an ASMA into DynamicConfiguration
    • Correlations
      • Receiver: when selected, the AMQP correlation will be set from
        • ASMA CorrelationId ( – if provided
        • PI MessageId
      • Sender: when selected, the PI Message will be filled with the AMQP correlation
        • In addition, the ASMA CorrelationId ( is set


Print Friendly, PDF & Email