Arsitektur Teknologi Informasi Services Oriented Architectures Antonius Rachmat C, S.Kom, M.Cs
Tes Kecil I • Bagaimana hasilnya?
Business factors for Services SOA eBusiness Processes over WWW System Integration Business to Customer Internet Based Delivery WAN’s Local Networks Protocols / Standards Computers
Business Interaction B to C Disintermediation B to B
Collaboration
Perkembangan SOA Internet
LAN
Web
1980
XML
1990
WS 2000
SOA
2012
Office Workflow EAI BPM B2B
Business Integration
EDI WS Mainframe Client / Server Web/Portal
J2EE .NET
?
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
Service Oriented Architecture • SOA adalah sebuah konsep software architecture yang mendefinisikan penggunaan layanan untuk 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
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 mengabstraksikan fungsi dan dapat menunjukkan bentuk hubungan yang bermakna antara 2 pihak yang berkomunikasi (requester dan provider)
SOA seperti puzzle
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
– Outward memanfaatkannya sebagai perluasan sistem yang ada (external network, peluang bisnis, dsb) • Contoh: layanan pembuatan file PDF secara online
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 integration of applications by discovering and orchestrating network-available services
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 publik dapat diakses oleh siapapun, berupa deskripsi tentang layanan yang ditawarkan • Bagian privat hanya bisa diakses oleh pemilik/penyedia layanan
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.
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
Reusability
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 multiple instances 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
Scalability
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.
Implementation of SOA • Services have platform independent, self describing interfaces (XML) Composable • Messages are formally defined (WSDL) Re Re--Usable • Services can be discovered (UDDI) Interoperable SOA • Services have quality of service characteristics defined in Loosely policies (SOAP) Coupled • Services can be provided on any platform (HTTP) • Services can be secured (WSSecurity)
Komponen SOA • • • • •
Layanan / Service Penyedia layanan / Provider Pemakai layanan / Consumer / Requester Tempat penyimpanan / Registry Pesan / query / call
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.
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.
Beberapa Istilah dalam SOA • Provider: bagian dalam SOA yang menyediakan services – Terdiri dari >= 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
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
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.
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.
Non-SOA (Integration)
SOA – Integration
Changing SOA (Integration)
Shift From Application To A Service-Oriented Architecture
From • • •
Function oriented Build to last Prolonged development cycles
Application based solution Tightly coupled Function / Object oriented Known implementation
To • • •
Coordination oriented Build to change Incrementally built and deployed
Enterprise solutions Loosely coupled Message oriented Abstraction
Enterprise View
Br ow s e r S tudent
A dm iss ions Offic e
Online S elf - S e r vice RW egis ation orktrpla ce
V is ibility S e rv ic es
A dm is sions & R ec ruitm ent
R e gistra tion A pplic a tion
E m a il
P hone P D A U niv e rs ity S ta ff
P a rtne r
P roc es s S er vice s
For m s
Te x t M e s sa ge
S tudent S e rv ic es S uite
Fina ncial P roc es s ing
D ocum e nt M ana ge m e nt (Folde rw a v e )
S c hedule M a nage m ent (S che dule 25 )
Blac k boa rd
A ca dem ic Audit
S tude nt Fina nc ia ls
S tudents Age nt Infor m a tion WOnline ork pla ce
Optim ization S e rv ic es
S tudent R e cor ds
Cours e E m ploy ee Inform a tion W Online ork pla ce
Le a rning U nit M a na ge m e nt
S uppor t S er vice s
PPar tner r a rtne WWor k plac e ork pla ce
Folde r M anage m ent
Infor m ation S e rv ic es Oper l Ope ationa ra tional DDa a tata
C r ea te S tudent
R e gula tor
Ex ter
P r os pe c t
Pa ck ag e
Busine ss Se rv ic e s Applic a nts W ork plac e
na l
Ente rp rise Info rm atio n Syste ms
Se rv ic e s
ga cy
C hanne ls
Le
Busine ss Partic ip ants
Ar chiv e S tude nt D a ta
EEle c trtronic lec onic BBusine us iness ss Gate y Ga tewwaay
AAna ly tic ss nalytic
Inte gratio n (ESB)
S e c ur ity S e rv ic e s
S ys te m s M gm t S er v ic es
V e ndor / P ar tne r S y stem s S e curity
S ys te m s M anage m ent
Te c hnic al Se rv ic e s Infra struc ture & Te c hno lo gy
V ir tualization S e rv ic e s
P olic ie s
Ontology
D ata S e rv ic e s
Indus tr y Fa bric
IT Systems View I nternal Proxy
Internal U ser Access
E nterprise Inform ation System ( O racle F inancial , H R et c. ) S ervice C o n su m er Servi ce Pro vid er
External U ser Access
Ext ernal P roxy
Port al Process Services
W eb Applicat ion Server
net
( C horeography
) Applications (S I S , B lackboard , et c .)
ESB
Protocol F irew all
Service C o n su m er
D omain F irew all
Servi ce Pro vid er
Services G at ew ay Security Services
Business Partners (U niversities , F ed . Govt. etc .)
Service R egist ry
Inform ation Services
S ervice C o n su m er Servi ce Pro vid er
S M anagem ent Security
&
F irew all Security Policy
D atabases
Servi ce Pro vi d er
D at a W arehouse / Business I ntelligence S ervi ce Pro vid er
SOA at application layer of OSI
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
NEXT • Web Services (SOAP)
