How will modeling translate between enterprises with different architectures? Will a standards body evolve to resolve potential conflicts?
It's no secret that ESA is SAP's strategy foundation for the future of enterprise software—a market in which SAP's customers expect the company to provide the lingua franca. But it's also true that no one else has come forward with a language or a set of de facto standards for translating a vanilla SOA—a creation of IT, and only IT—into a tool that business users understand.
Erecting an SOA that's technically capable of integrating every one of your systems without involving your managers or your partners is like calling one of your suppliers in China from your cell phone without knowing how to speak Chinese. Cellular networks, undersea cables, and the protocols for transmitting your voice halfway around the world are minor miracles, but what good do they do you if you can't understand the voice on the other end?
SAP developed enterprise services to be the lingua franca spoken by any enterprise that has adopted an SOA. While SAP is leading the charge by virtue of its expertise in this arena, its goal isn't to jealously protect ESA as a proprietary set of standards, but rather to open the definition of services and the platform—the evolution of this language—to the broader community of developers and Independent Software Vendors (ISVs). We explore these issues in detail in Chapter 20.
This is a new position for SAP. Historically, the company has ...
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