1. www.oasis-open.org David Smiley SOA Technology Evangelist Software AG David.Smiley@softwareag.com Lead, follow or get out of the way Here Comes SOA

2. Today’s discussion n Here Comes SOA n Fundamentals l Background and concepts of a Service-Oriented Architecture l Standards that make SOA interoperability possible l Registry, Repository and Metadata l SOA Governance l Security n IT and Business Alignment n Implementation Challenges and Solutions n SOA Maturity Model

3. Here Comes SOA

5. Fundamentals Background and concepts of a Service-Oriented Architecture

6. What Is a Service-Oriented Architecture? n SOA provides a framework for creating loosely coupled business services that can communicate or interoperate without relying on a specific technology platform. n SOA defines the business services that support a business process and then enables those services by combining internal, external and web services to support the business requirements. n SOA provides the flexibility to reuse business services to produce multiple end-to-end business processes. Service-oriented architecture (SOA) is a Web-based, standards-driven, modular architecture that promises to deliver pervasive integration for real-time business agility … META Group – February 2005

7. Moving from the Past to SOA... Legacy Financials CRM Supply Chain Packaged Applications are componentized Legacy Applications are turned into Services Complex systems are broken into service pieces Modules are being connected according to business needs

8. Service Oriented Architecture Customer Data Customer InteractionOrder History Order Policy Shipment CRMERPCustomer DataOrdersLogistics Customer Information Order Management Order Compensation Retrieve Data Verify Details Order Entry Order Review Approve Order Initiate Shipment Order Management Business Service Orchestration Services Composite Apps Business Process Service Bus

9. The interesting thing about services is…

10. Fundamentals Standards that make SOA interoperability possible

11. Web Services Standards n SOAP l A protocol for exchanging XML-based messages over computer networks, normally using HTTP. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on.

12. Web Services Standards n HTTP l Both SMTP and HTTP are valid application layer protocols for SOAP, but HTTP has gained wider acceptance as it works well with today's Internet infrastructure; specifically, SOAP works well with network firewalls. This is a major advantage over other distributed protocols like GIOP/IIOP or DCOM which are normally filtered by firewalls.

13. Web Services Standards n WSDL l An XML-based service description on how to communicate using web services. The WSDL defines services as collections of network endpoints, or ports. WSDL specification provides an XML format for documents for this purpose.

14. Web Services Standards n WS-I Basic Profile l WS-I is an open industry organization chartered to promote Web services interoperability across platforms, operating systems and programming languages. The organization’s diverse community of Web services leaders helps customers to develop interoperable Web services by providing guidance, recommended practices and supporting resources. All companies interested in promoting Web services interoperability are encouraged to join the effort.

15. Web Services Standards n WS-I Basic Profile l Specifically, WS-I creates, promotes and supports generic protocols for the interoperable exchange of messages between Web services. In this context, “generic protocols” are protocols that are independent of any action indicated by a message, other than those actions necessary for its secure, reliable and efficient delivery, and “interoperable” means suitable for multiple operating systems and multiple programming languages.

16. Fundamentals Registry, Repository and Metadata

17. Registry l A neutral 3rd party for negotiating, publishing, discovering and utilizing objects (such as services). l Stores information and represents metadata objects about assets (such as WSDL, XML Schema or XPDL) and references them. l Does not store those assets itself.

18. Repository n Storage for Service Related Artifacts l Development XML Artifacts n XSLT l Non XML Development Artifacts n Documents n Forms

19. Repository n Storage of Service Components l Process Definitions n XPDL l Ontologies l Sequences l Services l More

20. Metadata “The use of integration products and features is expected to increase. However, challenges will accompany this growth, particularly regarding metadata management.“ Jess Thompson et al. (11/2005)

21. Registry and Repository Registry metadata belongs to owns provides contains implements uses Repository "Files" Products and Tools Store development artifacts Reporting and Analyses Define and extend data model Register services and other assets SearchNotification

22. Fundamentals SOA Governance

23. What is Governance? n The term governance deals with the processes and systems by which an organization or society operate

24. What is Governance? n Corporate governance is the set of processes, customs, policies, laws and institutions affecting the way a corporation is directed, administered or controlled. Corporate governance also includes the relationships among the many players involved (the stakeholders) and the goals for which the corporation is governed.

25. What is Governance? n IT Governance is about visibility, accountability and making IT decisions, which works in tandem with IT Management that is about implementing various IT decisions. IT Governance keeps together the IT strategies and Business strategies and converts IT maxims into strategic actions.

26. The Analyst's View “In 2006, lack of working governance mechanisms in midsize-to-large … SOA projects will be the most common reason for project failure.” -Yefim V. Natis, Gartner Group, 11/2005 Scott Adams, “Dilbert”, 2-15-07

27. Why Governance? Governance provides n Authorities and responsibilities n Clear rules and rule enforcement n Organizational and technical transparency