WHINT AMQP Adapter (On-Premise)


This JCA Adapter for SAP PI / SAP Process Orchestration (PRO) 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 “http://whint.de/xi/AMQ” (Software Component WHINT_AMQ 2016.04 of whitepaper-id.com)
  • 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: http://whint.de/xi/AMQ
      • externalMessageID – Message Id received from broker
      • CreateDateTime – Timestamp of message creation
      • QueueExchangeID – Name of the Queue / Exchange Name
      • RoutingKey (only RabbitMQ)





WHINT InterfaceCatalog for SAP Process Orchestration / PI


This solution provides you with an overview about your Integration Landscape: All information from your configuration (Integration Directory) of your SAP Process Orchestration System. The tool downloads (e.g. periodically)

  • the Interface Catalog (based on all Integrated Configurations),
  • the Channel Catalog (based on all channels or on all channels used in the Integrated Configurations) and
  • the Interface Catalog Classic (optionally for PI only, based on Dual-Stack classic routings).

as an Excel Sheet.

All Routing information can be read as well as all communication channel attributes (e.g. host name) and all adapter modules including the corresponding parameters.

It answers questions like

  • what are the routing conditions for Partner X or IDoc Y ?
  • where do we use a specific FTP host?
  • where do we use Content Conversion (also via the MessageTransform Bean) ?

The solution is not invasive (no specific installation needed) and runs completely as interfaces using Standard PI/Process Orchestration technology. Only read access is required using the Integration Directory API.





  1. Import the TPZ file provided by Whitepaper InterfaceDesign into the ESR
  2. Configure the Process Integration Scenario using the Swing Client (Integration Builder: Directory) or Eclipse (SAP NetWeaver Developer Studio – NWDS) – see Configuration Guide below


Configuration Guide

  1. Create a user to access via the Integration Directory API (SOAP Receiver Lookup Channels) with the roles: SAP_XI_API_DISPLAY_J2EE and SAP_XI_APPL_SERV_USER
  2. Create two components according to your naming conventions, e.g. WHINT_IFC_Reader and <SID>_FILESYSTEM (in PI 7.11 it must be a Business System, for newer releases it can be either Business Component or Business System)
  3. Create all necessary SOAP Lookup Channels using the Channel Templates provided for the Objects
    • Communication Channel
    • Integrated Configuration
    • Configuration Scenario
    • Classic only: Receiver Determination
    • Classic only: Interface Determination
    • Classic only: Sender Agreement
    • Classic only: Receiver Agreement
  4. Start the wizard with the Process Integration Scenario WHINT_InterfaceCatalog, select the Component view matching your release and assign the systems to generate your iFlows/ICOs
  5. Assign the lookup channel parameters and select the correct NFS path where to write/read files
  6. Repeat this activity for Process Integration Scenario WHINT_InterfaceCatalog_Classic if you want to create the Dualstack InterfaceCatalog as well



Messages at Runtime