WHINT AWS SQS Adapter (On-Premise)


This JCA Adapter for SAP PI / SAP Process Orchestration (PO) connects to Amazon Web Service´s (AWS) Simple Queue Service (SQS) as well as Simple Notification Service (SNS) in a reliable way. It enables businesses to establish a properly decoupled application integration using message queues and topics like known queue-based protocols as JMS or AMQP.

“Amazon SQS is a distributed queue system that enables web service applications to quickly and reliably queue messages that one component in the application generates to be consumed by another component. A queue is a temporary repository for messages that are awaiting processing.” (Source: Amazon)

Our AWS SQS Adapter enables SAP Process Orchestration/SAP PI to act as a publisher and/or consumer of SQS messages.

The current release uses the version 1.11.143 of the aws-java-sdk.


  • Consume Messages from Amazon SQS
  • Send Messages to Amazon SQS Queue
  • Publish Messages to Amazon SNS Topic
  • Dead Letter Queue Support
  • Adapter-specific Message Attributes, also custom attributes
  • Internet Proxy Support
  • Quality of Service: EO/EOIO


  • 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 “AWS_SQS” from namespace “http://whint.de/xi/ASQ” (Software Component WHINT_ASQ 2016.10 of whitepaper-id.com)
  • Transport Protocol: AWS SQS
  • Message Protocol: HTTP
  • Other Options
    • SQS Queue Name
    • AWS Region (select from Drop-Down)
    • Authentication based on Access/Secret Key
    • Internet Proxy (Host, Port, User, Password)
    • Sender Only:
      • Consuming Interval (secs)
      • Quality of Service (EO/EOIO with queue name)
    • Receiver Only:
      • SNS Topic ARN (Receiver only) as alternative to SQS Queue Name
      • Default Visibility Timeout (secs)
      • Message Retention Period (secs)
      • Maximum Message Size (1-256 KB)
      • Delivery delay (secs)
      • Receive Message Wait Time (secs)
      • SQS Dead Letter
        • Use Redrive Policy
        • Dead Letter Queue Name
        • Maximum Receives (1-1000)
    • Set/Use Adapter-specific Message Attributes (ASMA)
      • Namespace: http://whint.de/xi/ASQ
      • externalMessageID – Message Id received from broker
      • createDateTime – Timestamp of message creation
      • SqsQueueName – Name of the SQS Queue
      • SqsTopicName – Name of the SNS Topic ARN
      • Custom Message Attributes (up to 10, free defined)

Example Configuration





How to expose a CSV file as a Service with SAP PI/PRO

Imagine you need to read a file content from a remote application and you do not want to set up a replication?
This scenario explains how to expose a CSV file (here a product list) as a WebService using the standard SOAP Adapter and the WHINT FileReader Adapter.


CSV File:

Design (ESR):

  • Create Service Interfaces (Sender and Receiver side)
  • For the receiver side you can also use the synchronous Inbound Service Interface FileReaderQueryResponse_In which is shipped with the Adapter
  • Optional: Create a Mapping if you do not want to expose the result of the CSV-to-XML conversion of the MessageTransformBean




Configuration (Eclipse/NWDS):


Receiver Channel (FileReader):

SFTP Connectivity (of course you can read the file from NFS or FTP as well):

Module Configuration (MessageTransformBean: CSV->XML):

Upload File to SFTP Server:

Test from SOAP UI:

Update: I think it is obvious that the Files can be also queried with other sender channels, not only from SOAP (like e.g. REST providing the response in JSON format):


How to use the results of WHINT InterfaceCatalog

The WHINT InterfaceCatalog for SAP PRO/PI generates two Excel Documents to bring more transparency to your interface landscape. Here is how you can better understand the results:

Channel Catalog

  • a list with all communication channels
  • contains all adapter attributes
  • contains all adapter modules
  • contains all parameters within each adapter module
  • You can filter and/or search for specific values as host names, user names, modules used, etc. across all channels



Interface Catalog

  • a list of all sender/receiver interface combinations
  • contains operation mappings used
  • contains routing (receiver determination and interface determination)
  • contains an assignment to configuration scenario(s)

Example iFlow / Integrated Configuration




is shown in the InterfaceCatalog as follows:


WHINT now Registered Trademark in Germany

Since October 2016 WHINT® is a registered trademark in Germany and represents our software product line whint://Solutions. Each product name of Whitepaper InterfaceDesign contains the term WHINT®.


whint://Solutions now in SAP HCI Content Catalog

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


Bitcoin Currency Rates now available from Blockchain

We have enhanced our cloud edition of WHINT CurrencyRates with a new provider: Blockchain.info.

The API provides bitcoin exchange rates for the major currencies and integrates automatically into SAP (e.g. ECC/ERP/CRM).

WHINT PaymentReporting Ingenico (Cloud Edition)

This Integration Package for SAP HANA Cloud Integration (HCI) is a turn-key solution which seamlessly integrates Ingenico ePayment reporting data into SAP FI (Ingenico ePayments was formerly known as GlobalCollect).
It enables the automatic processing of the Ingenico Collection Appendix Report as SAP FI documents with state-of-the-art integration technology. No changes or developments are required on SAP ERP side, only a few configuration steps are needed (ALE IDoc inbound processing).The accounting documents will be created automatically via a standard IDoc. Other Reports (Financial Statements) can be picked up automatically as well and e.g. sent via E-Mail.

It enables the merchant to process and reconcile payment processing data and match it with his transactional order-related data in SAP Finance.



  • Turn-key Solution: Pre-Packaged Integration Content for SAP HANA Cloud Integration (HCI)
  • Mapping, Connectivity and Interface Processing just needs to be activated with a few steps
  • Data provider for Payment Reporting 
    • Ingenico ePayments is the online and mobile commerce division of Ingenico Group – connecting merchants and consumers, enabling businesses everywhere to go further beyond today’s boundaries, creating the future of global commerce
  • How it works
    • The regular sales transactions (e-commerce, retail, …) are posted into SAP Finance using the transaction id of Ingenico against credit card/payment type specific G/L accounts (Debit)
    • The payment reporting data is also posted into SAP Finance against the same G/L accounts using the same allocation number (Credit). Like this, the postings can be reconciled easily. The total balance is posted on a receivables G/L account (Debit) which can be reconciled against the financial statement coming from the electronic bank statement.
    • The solution handles the creation of the SAP FI accounting document by picking up the Ingenico Collection Appendix Report and converting (mapping) it automatically.


  • SAP HANA Cloud Platform, integration service (SAP HCI)

Configuration Guide: SAP Cloud Platform Integration (CPI aka HCI)

  1. Import Integration Package into your HCI tenant
  2. Configure Integration Package
  • Select the scheduling according to your needs, e.g. daily at 10 PM or every hour.
  • Check the SFTP Address and provide your credentials
  • Add User Credentials under Monitoring -> Security Artefacts
  • Add the SFTP Public Key into the known_hosts file and deploy it under Monitoring -> Security Artefacts
  • Configure the SAP Business System Connectivity
  • Maintain the Value Mappings for Account Determination, … tbd.

Configuration Guide: SAP Business Suite 

  1. Check if IDoc-XML Messages can be received
  2. Create ALE Logical System
  3. Create partner profile for IDoc

Transaction SALE: Add your logical system name which represents the data provider (e.g. INGENICO)


Transaction WE20: Maintain Message Type ACC_DOCUMENT for partner (LS) INGENICO with process code BAPI.

Monitoring the Message Flow

Transaction BD87 shows the processed IDoc

Transaction FB03 finally shows the accounting document in SAP. 

WHINT On-Premise Adapter Bundle

Version: 2015.08 released in November 2015

ICC_cert_pbnw    sap-store-lr

This SAP certified solution bundle consists of 3 components:

Please visit our product landing page!