Enterprise SOA Infrastructure
SAP NetWeaver is exposing business and IT managers to new concepts (for example, Web services, composite applications, and service-oriented architecture). While most of you have a general understanding of these key terms, “The Last Word” provides you with a deeper, more practical definition. It was adapted from Enterprise SOA: Designing IT for Business Innovation by Dan Woods and Thomas Mattern (O’Reilly Media, 2006).
The world of service consumers, service providers, and model-driven development and composition requires seven supporting infrastructure elements, each of which plays a crucial role.
• Model-driven, pattern-based development tools: Many different levels of Enterprise SOA use modeling. For example, SAP NetWeaver Visual Composer simplifies the task of creating UIs, so business analysts can configure or build their own apps. Modeling simplifies development, makes changing applications easier, and supports many platforms with less work. Patterns combine component assemblies in repeating, high-level structures, amplifying modeling power. They simplify things and give developers a huge headstart.
• Enterprise services infrastructure: This is the tools foundation for designing and building enterprise services that ensure optimized operations. Enterprise SOA determines what portion of a service’s work the calling application will do; how much an intermediate layer will do; and how much the providing application will do.
• Enterprise Services Repository (ESR): To reuse enterprise services, you must be able to find them, determine what they do, and incorporate them into development tools. The ESR is a directory of this information. To create something from reusable parts, you’d need a directory of all reusable parts (ESR), how they work, how to access them, and so on.
• Enterprise services inventory: This is a comprehensive set of business-level enterprise services identified by SAP. You can find these enterprise services through the enterprise services workplace on SDN (www.sdn.sap.com).
• Lifecycle management, operations, and security: Enterprise SOA changes what software vendors need to provide and what is available for reuse. Management needs model-driven configuration tools and support models. Operations and security practices must change to accommodate these new services.
• Industry and technology standards: Enterprise SOA uses technology standards, such as J2EE and Web Services (WS)-Policy, at all stack levels to improve interoperability and reduce implementation costs. It provides context and plumbing for standards, working with them to maximize the value of each, creating a synergy.
• Ecosystem: This consists of all of SAP’s and its partner’s capabilities to solve customer problems. The Enterprise Services Community allows partners and customers to work with SAP to design enterprise services to solve emerging technology and industry problems and gain more value from Enterprise SOA.
|Supporting Elements of Enterprise SOA