![KaTe AMQP Adapter - Basics
.. JSON „JSON centric“ example!
JSON XML
[
"1",
"2„,
3
]
<?xml version="1.0" encoding="UTF-8"?>
<a class="array">
<e type="string">1</e>
<e type="string">2</e>
<e type="number">3</e>
</a>
This is forth & backward compatible!](https://image.slidesharecdn.com/amqpintegrationadapteroverview1-141112004411-conversion-gate02/85/KaTe-AMQP-Adapter-for-SAP-Process-Orchestration-SAP-Process-Integration-14-320.jpg)
KaTe AMQP Adapter for SAP Process Orchestration / SAP Process Integration
- 1. KaTe AMQP Adapter for SAP Process Integration Introduction & Overview
- 2. KaTe AMQP Adapter - Overview What can the KaTe AMQP adapter do for you?
- 3. KaTe AMQP Adapter - Overview The KaTe AMQP adapter bridges your SAP systems to AMQP enabled devices, cloud & applications via SAP PI/PO AMQP – „Bus“ ~ transport SAP ERP SAP PI SAP CRM 3rd Party AppCloud Apps MobileIoT Devices AMQP Integration Adapter ~ connect SAP PI ~ route / transform
- 4. KaTe AMQP Adapter - Overview This enables you to : Publish & Subscribe AMQP Messages to any AMQP compliant broker from SAP PI/PO in secure & reliable manor Send and receive any payloads straight forward in JSON & XML formats 100% connects MOM oriented interactions with SAP PI message & error handling and standard monitoring & tooling Develop and operate AMQP messagin scenarios quickly with our full fleshed error handling / administration options.
- 5. KaTe AMQP Adapter – At glance So how does it work?
- 6. KaTe AMQP Adapter – At glance So how does it work? AMQP messages are translated into PI messages while entering the adapter PI messages are translated into AMQP messages while leaving the adapter AMQP message (binary) PI message (XI-SOAP)receive AMQP message (binary) PI message (XI-SOAP) sent
- 7. KaTe AMQP Adapter – At glance AMQP Payloads are translated to PI message XML payloads AMQP Headers are translated to PI dynamic configurations AMQP Properties are translated to PI dynamic configurations Any Header or Property can be set statically (in the channel configuration) or dynamically (via dynamic configuration) AMQP message PI message • Header A • Header B • ReplyTo PAYLOAD (e.g. XML) PAYLOAD (e.g. XML) • amqpReply • Header A • Header B Dynamic Configurations XML Payload (defined in ESR) AMQP standard properties AMQP headers AMQP payload (XML, JSON, etc) Translation JSON 2 XML If necessary
- 8. KaTe AMQP Adapter – At glance AMQP standards support: AMQP versions: 0-8-0, 0-9-0, 0-9-1 and 1.0 Broker Level Server wiring (0-9-1): Binding Queues to AMQP Exchanges via Routing keys or directly interact with Queues* Security: Use SSL and User/Password authentication *) e.g. Take a look at the „classic“ RabbitMQ tutorial examples, all these scenarios are supported:
- 9. KaTe AMQP Adapter – How it works ... and how about JSON payloads?
- 10. KaTe AMQP Adapter – How it works ... and how about JSON payloads? The adapter uses content negotiation features (via AMQP property content-type to „autodetect“ how to treat the content Contents with no content type set or XML as content type get automatically treated as XML / regular PI payload Contents with content type JSON are „autotranslated“ to XML via conventions (you can always turn this off if needed)
- 11. KaTe AMQP Adapter – How it works ... and how do the JSON / XML conventions look like?
- 12. KaTe AMQP Adapter – How it works ... and how do the JSON / XML conventions look like? The conventions allow a 100% forth and backward compatible conversion between XML and JSON No intensive configuration for JSON needed (modules etc...), only choose between 2 different flavors for JSON constructs XML „centric“ JSON „centric“ (for special constructs like JSON arrays)
- 13. KaTe AMQP Adapter - Basics .. JSON „XML centric“ example! JSON XML { "tns:company": { "@xmlns:tns": “urn:my:comp", "name": "My Company", "address": { "city": "München", "zipCode": "83503", "houseNumber": "93a", "country": “DE" } } } <?xml version="1.0" encoding="UTF-8"?> <tns:company xmlns:tns=“urn:my:comp"> <name>My Company</name> <address> <city>München</city> <zipCode>83503</zipCode> <houseNumber>93a</houseNumber> <country>DE</country> </address> </tns:company> This is forth & backward compatible!
- 14. KaTe AMQP Adapter - Basics .. JSON „JSON centric“ example! JSON XML [ "1", "2„, 3 ] <?xml version="1.0" encoding="UTF-8"?> <a class="array"> <e type="string">1</e> <e type="string">2</e> <e type="number">3</e> </a> This is forth & backward compatible!
- 15. KaTe AMQP Adapter - Features ...and how about request/reply messaging and errorhandling?
- 16. KaTe AMQP Adapter - Features ...and how about request/reply messaging and errorhandling? We included request/reply as first class citizen without need to: Use Any „artifical“ bridges like BPM or complicated adaptermodules (sync/async or async/sync) bridge Simply by setting qoS to „best effort“ in your sender channel or invoking a receiver channel with best effort Advanced errorhandling & timeout support comes along
- 17. KaTe AMQP Adapter - Features Errorhandling ...or life not always runs the „happy path“
- 18. KaTe AMQP Adapter - Features Errorhandling ...or life not always runs the „happy path“ Why is it necessary? SAP PI defines a WSDL oriented error pipelines (defined WSDL faults or system exceptions aka undefined faults) MOM oriented systems like AMQP mostly signal errors via message headers (e.g. Status of an operation + error payload) Therefore you need control to bridge this behaviour
- 19. KaTe AMQP Adapter - Features Errorhandling ...or life not always runs the „happy path“ How do we solve this? The adapter supports adding additional header fields for defined faults or system exceptions (e.g. Status) The adapter supports evaluating AMQP header fields for incoming messages to „detect“ treatment as faults or system exceptions
- 20. KaTe AMQP Adapter - Operations and how about operations & monitoring?
- 21. KaTe AMQP Adapter - Operations and how about operations & monitoring? You can use all the PI standard monitoring tools (msg/channel monitor) On top we augment these by: Allow you to increase auditLog output for tracing AMQP properties, headers + payloads as „on wire“ into the auditlog. Providing a Web UI to see an overview of all connected destinations for your PI interfaces Test JSON/XML transformation
- 22. KaTe AMQP Adapter - Operations Example auditlog output (only for debugging purposes) AMQP Payload AMQP headers AMQP properties Adjust Watch
- 23. KaTe AMQP Adapter Interested in our offer? We are pleased to hear your feedback 30 Day trial of the adapter available!
- 24. AMQP Integration Adapter Interested in our offer? http://en.kate-group.de/sap-beratung-services- projektmanagment/ampq-integration-adapter/ Contact us at : WWW: http:www//kate-group.com/ T +49 711 90 79 64 65 F +49 711 90 79 64 66 E [email protected]