With message and communication protocols evolving quickly, SAP invested a lot in integration technologies and kept on adding new components and products to its integration suite.Īt this time, SAP’s Integration Suite covers all integration use cases applications, devices, users, people and so on. REST was developed as an alternative to web service implementation and its flexibility and speed made it very popular during the mobile adoption era.
#Sap ecc architecture diagram software#
SAP enables the integration of SOAP web services through its Exchange Infrastructure/ Process Integration software SAP XI/PI.Īlthough SOAP proved very successful, a new lightweight architectural style called Representational State Transfer (REST) emerged to simplify the communications between software applications in a service-oriented architecture. Later, as service-oriented architecture started gaining popularity during the early 2000s, SAP re-invented its interfaces and started exposing business functions in the form of web services.įor a long time, the Simple Object Access Protocol (SOAP) was the go-to messaging protocol that almost every web service used. This included IDoc and BAPI’s as the standard SAP interfaces which played an important role in the technical integration and exchange of business data.
In the past, Application Link Enabling (ALE) was the means to exchange data within an enterprise between SAP and non-SAP systems. The early days of integration to now – a brief history
0 kommentar(er)
