SAP Enterprise Services Architecture

From Wikipedia, the free encyclopedia

You have new messages (last change).

SAP Enterprise Services Architecture (ESA) has been defined by SAP as "an open architecture for adaptive business solutions". ESA is enabled by the SAP NetWeaver platform, and builds on the benefits of Web services. SAP has positioned ESA to deliver the benefits offered by service-oriented architecture, including enabling both flexibility and business efficiency. SAP state that ESA provides companies with a "cost-effective blueprint for composing innovative new applications by extending existing systems, while maintaining a level of flexibility that makes future process changes cost-effective"[1] .

Contents

[edit] Key principles of ESA

The five key principles of ESA are:

  1. Abstraction — hiding technical details that can be confusing
  2. Modularity — breaking down complexity and creation of "reusable pieces"
  3. Standardized connectivity — enabling flexible composition of services to form processes
  4. Loose coupling — allowing for separate evolution of the various components without breaking any points of integration
  5. Incremental design — enabling changes to composition and configuration without affecting the internals of components, and vice versa

[edit] SAP Solutions that currently use ESA

SAP have committed to "building new SAP applications purely in a service-oriented way".

[edit] Composition of ESA

ESA is not a product in itself. However, principles of ESA are being increasingly applied in SAP technology and software, such as:

  • SAP NetWeaver, which provides the technical foundation for implementing an Enterprise Services Architecture.
  • SAP xApps, the next generation of SAP applications, utilising multiple application components and built mainly by model-driven composition and configuration.
  • In new releases of the SAP Business Suite, where more principles of ESA will be applied.

[edit] How ESA is related to SAP NetWeaver

SAP NetWeaver is the open integration and application platform for all SAP applications and solutions. It provides a technical foundation for implementing an Enterprise Services Architecture by providing common:

  • Service descriptions based on Web services standards (e.g. WSDL)
  • Development process for all types of remote interfaces, including process integration, user interface, application-to-application (A2A), B2B, etc.
  • Web services-based runtime infrastructure
  • ESA service bus for communication, transaction handling, debugging, tracing, message integrity etc.

[edit] See also

[edit] External links

[edit] References

  1. ^ When Does a Web Service Become an Enterprise Service? Dr. Franz-Josef Fritz (SAP AG), SAP Insider, Apr May Jun 2004
Retrieved from "http://en.wikipedia.org../../../s/a/p/SAP_Enterprise_Services_Architecture_bfd7.html"
In other languages