SAP integration · LessonBy Arjun, SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels
SOAP
SOAP integration connects systems to SAP using XML web services with formal WSDL contracts, the classic service-oriented style, still used in enterprise SOA and via middleware.
Quick answer
Use SOAP where a formal contract or WS-* capabilities are required, or to integrate with systems/middleware that mandate it.
Key takeaways
- SOAP integration exchanges XML messages defined by WSDL contracts, with SAP as provider (exposing services via SOAMANAGER) or…
- WSDL contracts defining the service.
- XML payloads and WS-* standards.
- Watch out: Wrong tool for the integration style.
What SOAP integration does
SOAP integration exchanges XML messages defined by WSDL contracts, with SAP as provider (exposing services via SOAMANAGER) or consumer. Middleware (PI/PO) heavily used SOAP for structured, contract-based integration between enterprise systems.
Key aspects
- WSDL contracts defining the service.
- XML payloads and WS-* standards.
- SOAMANAGER for configuration.
- WS-Security for message security.
When to use it
Use SOAP where a formal contract or WS-* capabilities are required, or to integrate with systems/middleware that mandate it. For new lightweight integrations, REST/OData is generally preferred.
Common pitfalls
- Wrong tool for the integration style.
- Ignoring monitoring/error handling.
- Point-to-point instead of governed integration.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of SOAP?
Frequently asked questions
What does SOAP stand for, and how is it used in SAP integration?
SOAP integration connects systems to SAP using XML web services with formal WSDL contracts, the classic service-oriented style, still used in enterprise SOA and via middleware.
What does SOAP exchange data with?
Use SOAP where a formal contract or WS-* capabilities are required, or to integrate with systems/middleware that mandate it.
What is the practical takeaway on SOAP?
SOAP integration exchanges XML messages defined by WSDL contracts, with SAP as provider (exposing services via SOAMANAGER) or consumer.
What tends to go wrong with SOAP in SAP integration?
Wrong tool for the integration style. Ignoring monitoring/error handling. Point-to-point instead of governed integration.