1. An introduction to SOA fundamentals By : Abhishek Chatterjee

3. Mainframes: The first applications ran on one central computer. Users connected through dumb terminals or teletype machines. no messaging systems, no GUIs, no shared data, and no interaction between applications . Workstations : As desktop computers, personal applications; each user ran a locally installed copy and quit it after its use. No data was shared Networking : Networks connected workstations to each other . This enabled e-mail capability within an enterprise and sharing files on a file server. Client/server : application no longer ran completely on a central computer or on a workstation, but was split across the two. business logic that ran on the server and local clients. central business logic running in application servers . N-tier : Database server runs on a different host computer from the application server, that's a three-tier architecture . Internet : The Internet is networking on a global network . enabled communications and information sharing between users anywhere in the world. World Wide Web : Web made the Internet graphical , using HTML, hyperlinks to other document . Browser GUIs : Web introduced HTML browsers for viewing static HTML documents. provide interactive GUIs for accessing remote applications. This was a return to the centralized computing model. none of the application ran on the client except for HTML rendering and some simple scripting

4. Enterprise architecture: architect is responsible for an enterprise's full range of software-intensive systems, including the relationship between multiple applications, data shared between applications, integration of the applications, and the infrastructure to run applications Application architecture : focuses on the design of applications to automate business processes and provide functionality that helps users perform business tasks. Focus of functional and quality of service requirements including performance, availability, scalability, security, and integrity. Information architecture: focus on structure, integrity, security, and accessibility of that data Infrastructure architecture : focuses on the design of hardware and server software including server computers, storage, workstations, middleware, non-application software, networks, and the physical facilities that support the applications and business processes required by the enterprise Integration architecture: focuses on the design of solutions that enable existing applications, packaged software offerings, networks, and systems to work together within an enterprise or among enterprises Operations architecture : focuses on the design of solutions to manage the infrastructure and applications used by the enterprise

5. Before we define SOA, Lets find what is Web services and Web 2.0 . Web services: Internet was created to connect applications, but the Web connected people to static content and to server applications. Web services use the Web to connect applications so that one application can invoke behaviour in another application through a Web connection . Web 2.0: This is the application of Web services to Web sites. The user of a Web site is no longer a person, it's another application. SOA: It is an architecture for building business application as a set of loosely coupled black box components orchestrated to deliver a well defined level of service by linking together business processes. Applications have tended to be monolithic, applications at best interacted as peers . SOA divides an application into a service coordinator . that represents user functionality and service providers that implement the functionality , a service can be reused and shared by multiple composite applications .

9. Enterprise service Bus (ESB): Different pieces of software talk to each other by sending messages. ESB is used to transport messages quickly and reliably between software components. Work flow engine: Designed to connect a whole business process from end-to-end, flowing work from one individual/process to another until entire BP is carried out. SOA registry: Its an electronic catalogue where you store information describing what each component does. (publish web sevrices) Acts as a reference that helps them select components and connect them together to create composite applications and build process Also store How each components connects to other Service broker: Acts like a needle threading one component to the next in a business process. Uses the information in SOA registry and threads components together for the workflow engine. SOA supervisor Guarantee service: 99.999% Define and measure the service levels for the end-to-end business process. SOA supervisor plays pivotal role. ESB

10. XML: the definition language that can accompany information ( XSD : defines the template of the information.) SOAP: standard that uses XML to describe messages that are sent from program to program. A program uses SOAP to request a service from another program & then pass the related data. (consists of Envelop, Header, Body and fault) WSDL: A standard based on XML programmers use WSDL to create XML document that describes a Web service and how to access it. (consist of Definition of Post, message(input & Output, data types, program binding) UDDI: It is a framework for describing, discovering and integrating business services via internet. (a public registry)

16. It pulls of the trick of providing a single identity for user that can be used throughout a computer network, or even across networks. Old days: Portal accesses the IM software and IM in turn provides all the passwords & access to individual application based on users role. SOA scenario: Connect to business services not applications. So IM software creates a encrypted token containing identity of user, details of the access rights of the user . Service broker delivers this token to all component and each component decrypts and executes it based on the access.

17. Weak authentication: password etc Strong authentication : computer readable cards, biometric reader. Software fingerprint: Antivirus software have a signature of bad software(Trojan, worms). These signatures are software fingerprints. If these concept is extended for ever good software. Each software component of business services are fingerprinted & stored in signature file. Service Broker passes the address of each component of the services to authentication software, which then tests it and pass/reject it & service broker then execute the components. Audit trail is kept using ESB of all messages that are passed Sometimes we use digital certificates to deal with trusted sources. Its guarantee of authenticity from issue authority, it says the named person and company has this public encryption keys (PKI – public key infrastructure) Certificates are kept in public registry.

18. Modelling tools: Rational software modeller Programming tools: Rational software developer Application servers: Websphere application servers DBMS: DB2 CM tools: rational clear case Testing tools: Rational clear quest

19. Lifecycle tool: Iterative model actually involves people from business & technologies but still has a weakness and that is you are still developing the application not a business process. Getting software developer to think in terms of business process need to follow a new software development lifecycle. Use BPM tool to develop business process.

20. BPM tool: Generate the linking code by referring to interfaces published in the SOA registry Used to build new business functions & publishes their interfaces in the SOA registry Create instruction to direct a workflow engine. Store business process map in repository

22. SOA – The final picture

23. Thank you