What does the future hold for creating enterprise services?
Web services, although simple and standardized, are not by themselves enough for building a robust, reliable SOA that meets enterprise-level needs. The problem is exacerbated by the fact that the staff who administer enterprise applications and the developers maintaining the corporate web site and creating web services are typically in two different groups.
What is needed is a cohesive blueprint for an SOA that provides integration with enterprise applications and is adaptable to constantly changing market conditions. To be service oriented really means to be process oriented. That's what ESA is all about. It's an architectural blueprint for an SOA that is fully standards based and provides business value, with services modeled from key business processes.
This section briefly explores the future of creating enterprise services. We'll start by digging into the conceptual details of SAP's architectural vision for ESA, concepts that are foundational to creating your own ESA adoption roadmap.
What are business objects?
ESA is built on business objects, described in Chapter 5. Business objects are unique, identifiable business entities. Examples of business objects include a sales order, a purchase order, and a business partner. A business object is a logical building block, composed of numerous data elements, some of which are, in turn, based on the UN/CEFACT standard for global data types, ensuring wide interoperability with ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access