Arsitektur Teknologi Informasi. Services Oriented Architectures Antonius Rachmat C, S.Kom, M.Cs

Transkripsi

1 Arsitektur Teknologi Informasi Services Oriented Architectures Antonius Rachmat C, S.Kom, M.Cs

2 Bagaimana hasilnya? Tes Kecil I

3 Business factors for Services Internet Based Delivery SOA ebusiness Processes over WWW System Integration Business to Customer WAN s Local Networks Protocols / Standards Computers

4 Business Interaction B to C Disintermediation B to B Collaboration

5 Perkembangan SOA Internet LAN Web XML WS SOA Office Workflow EAI EDI BPM B2B WS Business Integration? Mainframe Client / Server Web/Portal J2EE.NET

6 Service Model expanded What if the two classes are not on the same machine? Network! How can one class find another? Service Description How can a class send its information to the other class? XML Do the two classes have to be on the same network? TCP/IP + HTTP + XML

7 Service Oriented Architecture SOA adalah sebuah konsep software architecture yang mendefinisikan penggunaan layananuntuk mendukung kebutuhan pengguna software. Dari sisi prespektif bisnis: A service-oriented architecture is a framework for integrating business processes and supporting IT infrastructure, standardized components services that can be reused and combined to address changing business priorities

8 Bentuk SOA SOA adalah sebuah arsitektur yang merepresentasikan fungsi dalam bentuk layanan Mengapa fungsi? Karena fungsi menunjukkan abstraksi aktivitas sesuatu yang secara alami dilakukan oleh aplikasi/program, individu, dan organisasi Mengapa layanan? Karena layanan mengabstraksikanfungsi dan dapat menunjukkan bentuk hubungan yang bermakna antara 2 pihak yang berkomunikasi (requester dan provider)

9 SOA seperti puzzle

10 SOA dan Aplikasinya Ada dua arah pengembangan: Inward ke dalam institusi sendiri integrasi sistemsistem yang ada untuk membangun fungsionalitas yang lebih luas Misal : untuk Supply Chain Management Outwardmemanfaatkannya sebagai perluasan sistem yang ada (external network, peluang bisnis, dsb) Contoh: layanan pembuatan file PDF secara online

11 Penyebab SOA dan Tujuan SOA Pendorong berkembangnya SOA dari sisi bisnis: Large scale Enterprise systems Internet scale provisioning of services Want to reduce the cost of doing business Tujuan Just-in-time integrationof applications by discoveringand orchestratingnetwork-available services

12 SOA dan Integrasi Aplikasi/Sistem SOA berfungsi sebagai platform integrasi: SOA memisahkan antara pesan/query/call dengan pemrosesan Pesan/query/call distandardisasi dan tidak dikaitkan dengan sebuah produk teknologi tertentu, sehingga bisa dikirimkan/diterima oleh siapapun SOA memisahkan antara bagian publik dan bagian privat Bagian publikdapat diakses oleh siapapun, berupa deskripsi tentang layanan yang ditawarkan Bagian privat hanya bisa diakses oleh pemilik/penyedia layanan

13 Sifat SOA SOA bersifat behind the scence, SOA tidak terlihat secara langsung oleh client, SOA dihadapkan pada client melalui client UI Digunakan untuk berkomunikasi antar aplikasi SOA merupakan suatu service yang hanya menunggu (listen) secara terus-menerus untuk digunakan.

14 Benefits of SOA Better reuse of services Build new client functionality on top of existing Business Services Well defined interfaces Make changes without affecting clients Easier to maintain Changes/Versions are ok! Platform Independence An enterprise can leverage its existing legacy applications that reside on different types of servers

15 Reusability

16 Benefits of SOA (2) Code Reuse the services can be reused in multiple applications Location Transparency Web services are often published to a directory where consumers can look them up Better scalability there can be multipleinstances of the service running on different servers. This increases scalability Higher availability Since the location of a service does not matter and you can have multiple instances of a service, it is possible to ensure high availability

17 Scalability

18 Prinsip-prinsip utama SOA Standardized service contract by one or more service-description documents. Service Loose Coupling Service Abstraction Beyond descriptions in the service contract, services hide logic from the outside world. Service reusability Service autonomy Services have control over the logic they encapsulate. Service statelessness - Services minimize resource consumption by deferring the management of state information when necessary Service discoverability Services are supplemented with communicative meta data by which they can be effectively discovered and interpreted. Service composability Services are effective composition participants.

19 Implementation of SOA Services have platform independent, self describing interfaces (XML) Messages are formally defined (WSDL) Services can be discovered (UDDI) Services have quality of service characteristics defined in policies (SOAP) Services can be provided on any platform (HTTP) Services can be secured (WS- Security) Interoperable Composable SOA Loosely Coupled Re-Usable

20 Komponen SOA Layanan / Service Penyedia layanan / Provider Pemakai layanan / Consumer / Requester Tempat penyimpanan / Registry Pesan / query / call

21 Beberapa Istilah dalam SOA Service: suatu fungsi yang menerima satu atau lebih request dan mengembalikan satu atau lebih response yang terdefinisi dengan baik dengan menggunakan interface yang standar. Service is self-contained. That is, the service maintains its own state Interface contract to the service is platform-independent Service can be dynamically located and invoked Pengguna service dapat menentukan service yang diperoleh untuk digunakan dalam application logic mereka.

22 Elements of a service Header Name Version Owner Type: presentation/process/business/data/intergration Functional Service operation : method Invocation: how to invoke (SOAP/REST) Non functional Security constraints Quality of service, etc.

23 Beberapa Istilah dalam SOA Provider: bagian dalam SOA yang menyediakan services Terdiridari >= 1 service Harus dapat ditemukan oleh requester Mendaftarkan dulu ke registry Requester: bagian dalam SOA yang mencari dan menggunakan services Dapat menggunakan lebih dari 1 service Harus dapat mencari provider Mungkin mencari di registry

24 Beberapa Istilah dalam SOA Registry: tempat penyimpan informasi provider-provider yang menyediakan berbagai services Berupa layanan yang listen terus menerus Bisa berbayar atau gratis Query: mekanisme invocation service Berupa permintaan service yang bersifat standar Menggunakan format khusus agar dapat dibaca oleh service

25 Build an SOA in 8 Steps (1) What problem are we trying to solve? (2) What aspects can be implemented as services? Old services? New services? Legacy wrappers? (3) Track services with registries and repositories (4) We need to monitor behavior, enforce policies & assess user satisfaction. (5) Secure the services. Using established standards, we need privacy, authentication, and authorization.

26 Build an SOA in 8 Steps (6) Manage the services. Are messages arriving on time? Is everything operating properly? (7) Virtualization through mediation. Are we free to move and change the services? (8) Design for interoperability through the adoption of standards.

27 Non-SOA (Integration)

28 SOA Integration

29 Changing SOA (Integration)

30 Shift From Application To A Service-Oriented Architecture From To Function oriented Build to last Prolonged development cycles Coordination oriented Build to change Incrementally built and deployed Application based solution Tightly coupled Function / Object oriented Known implementation Enterprise solutions Loosely coupled Message oriented Abstraction

31 Enterprise View Busine ss Partic ip ants Channels Services Enterprise Information Systems P r ospec t For ms Applica nts W orkplace Business Services P rocess S er vices V isibility S e rv ic es Package Legacy External S tudent Admissions Office Univ ersity S ta ff Brow ser E mail P hone P D A S elf Online - Service Registr W orkpla ation ce S tudents Age nt Infor ma tion W Online orkpla ce Course Informa E mploy tion ee W Online orkpla ce Admissions & R ec ruitment S tude nt Financials S tudent R ecor ds Learning Unit M anage ment Registra tion A pplica tion Optimization S e rv ic es Folde r M anage ment S tudent S e rv ic es S uite Fina ncial P rocess ing Docume nt Sc hedule M ana ge ment Management (Folderw ave ) (S chedule25) Blackboard Academic Audit P artner Te xt M e ssage P P ar artne tner r W or orkpla k plac ce e S uppor t S er vices Infor mation S e rv ic es Create S tudent Oper Ope ationa ra tional l Da Data ta R egulator E Electronic lectronic Business Business Gatew Gatew ay ay Ar chiv e S tudent Data A Analytics na ly tic s Inte gratio n (ESB) V endor / P ar tner S ystems Technical Services Security S ervices S ystems M gmt S ervices V irtualization S ervices Data S ervices S ecurity S yste ms M anage ment Infrastructure & Technology P olicies Ontology Industr y Fa bric

32 IT Systems View Internal User Access Internal Proxy Enterprise Information System ( Oracle Financial, H R etc.) Service C onsum er Service Provider External User Access net Protocol Firewall External Proxy Domain Firewall Portal W eb Application Server Process Services ( C horeography ) ESB Applications (SIS, Blackboard, etc.) Service C onsum er Service Provider Business Partners (Universities, Fed. Govt. etc.) Services Gatew ay Security Services Service R egistry Inform ation Services Service C onsum er Service Provider S Managem ent Security & Security Policy Firewall D atabases D ata W arehouse / Business Intelligence Service Pro vid er S ervice Pro vid er

33 SOA at application layer of OSI

34

35 SOA challenges Trust Data from a large number of services from different partners Test All services work as designed? Security Is the level of security is adequate? Continuous updating, refinement and expansion

36 Web Services (SOAP) NEXT