Enterprise Service Oriented Architecture (Soa)


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Service Consumer: merupakan entitas dalam SOA yang membutuhkan sebuah layanan untuk mengeksekusi sebuah fungsi yang dibutuhkan. Lokasi layanan dicari baik dalam registry, atau jika mengetahui pengguna dapat langsung berhubungan dengan penyedia layanan. Service Provider: Merupakan entitas dalam jaringan yang menerima dan mengeksekusi permintaan dari pengguna. entitas ini menyediakan deskripsi layanan dan implementasi layanan. Service Registry: Merupakan direktori yang dapat diakses melalui jaringan dan memuat layanan yang tersedia. Fungsi utamanya adalah menyimpan dan menyampaikan deskripsi layanan dari penyedia dan memberikannya kepada pengguna layanan yang membutuhkan Service Contract: Merupakan deskripsi yang menjelaskan bagaiman interaksi antara pengguna layanan dan penyedia layanan. Memuat informasi tentang formay pesan request-respond, kondisi dimana layanan dapat dieksekusi.Service Proxy: untuk membantu interaksi antara penyedia layanan dan pengguna dengan menyediakan antarmuka dalam "bahasa lokal" bagi pengguna. Juga digunakan untuk meningkatkan keandalan layanan dengan kemampuan fasilitas caching. Ini merupakan entitas tambahan (optional entity) dalam SOA. Service Lease: menyatakan jumlah waktu bagi sebuah kontrak layanan valid. Dikelola oleh registry dan menetapkan kerangka waktu untuk membatasi respon layanan.
  • Enterprise Service Oriented Architecture (Soa)

    1. 1. Short Brief Lecture<br />11/12/2007<br />KapitaSelekta - T. Informatika STT Telkom<br />1<br />Enterprise Service Oriented Architecture (SOA)<br />@ Anwar S<br />
    2. 2. Service Oriented Architecture<br />11/12/2007<br />KapitaSelekta - T. Informatika STT Telkom<br />2<br />Multiple approaches for the realization and deployment of an IT system that has been designed and built around its principles<br />Framework for integrating business processes and supporting IT infrastructure as secure, standardized components—services—that can be reused and combined to address changing business priorities.<br />
    3. 3. Enterprise IT Evolution <br />The long history of programming languages, distribution technology, and business computing has influenced the development of a new paradigm, called service-orientation.<br />3<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />
    4. 4. Programming Evolution<br />The development of programming languages had a strong impact on the interfacing techniques for distributed components and the implied access pattern to these components<br />4<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />
    5. 5. Evolution Result <br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />5<br />More productive development platforms but has also significantly contributed to the understanding of interfacing techniques and access patterns for services <br />
    6. 6. Service Oriented Architecture<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />6<br />Implement<br />
    7. 7. Enterprise SOA<br />Enterprise Layer : end-points that provide access<br />Process Layer : Activity, Facade, Technology Gateway, Adapter<br />Service Layer : Provide business logic and data<br />7<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />
    8. 8. Agony Vs Agility<br />People are getting used to this situation and are starting to think in terms of workarounds, not in terms of the "right" structures<br />8<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />
    9. 9. Architecture Direction<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />9<br />
    10. 10. Business Process Support<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />10<br />SOA<br />
    11. 11. Technology Implementation<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />11<br />UML Design Tool<br />Service Repository<br />XMI<br />MDA-based Code Generator<br />Platform Based<br />WSDL<br />CORBA IDL<br />EJB Technology<br />
    12. 12. Information Management Under SOA<br />A logical view or framework for categorizing information management services based on their value propositions: security, collaboration, availability, management, and information consumption<br />12<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />
    13. 13. SOA Guide<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />13<br />SOA requires CEO- and CIO-level commitment . <br />The business team and IT team work hand-in-hand . <br />Avoid the "big-bang" approach.<br />Fully embrace the use of standards.<br />Governance is critical for success.<br />Successful project management of SOA projects is key to leverage best practices and patterns experience.<br />Adopt innovative software engineering principles.<br />
    14. 14. Closing<br />11/12/2007<br />Kapita Selekta - T. Informatika STT Telkom<br />14<br /> “The Enterprise Services Architecture enables unprecedented flexibility in business process deployment, allowing companies to execute and innovate end-to-end processes across departments and companies, with minimum disruption to other systems and existing IT investments.” "<br />Dr. Peter Graf, SVP Product Marketing, SAP<br />