1. Muhammad Ghifary, M.T.
Gede Karya, M.T.

2. Latar Belakang & Masalah
• Kebutuhan layanan machine-to-machine antara SI Unpar
dengan sistem lainnya
– akademik, umum, lainnya ?
• Mengapa machine-to-machine ?
– Interoperability
– HTTP browser capability
– Service reusability
• Penyediaan layanan oleh SI Unpar berupa API dengan Web
Services
– Layanan apa saja ?
– Teknologi yang digunakan ?
– Model / arsitektur sistem ?
– Isu keamanan ?

3. Model Hipotesis

4. Batasan
• Hanya SI Akademik bagian studentportal
– Fokus : operasi read
• Web Services Server menggunakan Java EE

5. Tahap Penelitian
1. Kajian Pustaka (v)
2. Pemahaman sistem kini (v)
3. Analisis (3/4)
– Spesifikasi kebutuhan (v)
– Desain model (1/2)
4. Implementasi web services server (x)
5. Implementasi web services test client (x)

6. 1. Kajian Pustaka
• Traditional Web Services
– HTTP
– XML
– SOAP
– UDDI
• RESTful Web Services
– HTTP GET/POST, SOAP, JSON
• Security in Web Services / HTTP
– HTTPS, SSL/TSL, WSS, OAuth
• Distributed System
– cluster

7. Traditional Web Services
• Web Services :
– layanan apapun yang tersedia dan dapat diakses melalui
jaringan Internet dengan menggunakan sistem XML
messaging
– Tidak bergantung pada Sistem Operasi atau Bahasa
Pemrograman

8. Traditional Web Services (2)
Service-Oriented Architecture (SOA)
• Format pesan : XML (SOAP atau XML-RPC)
• Service Description : WSDL (Publish) & UDDI (Find)
• Transport network : HTTP

9. RESTful Web Services
• RESTful bukan standard, hanya sebuah gaya arsitektur
• Universal Interface : GET, POST, PUT, DELETE (HTTP verbs)

10. RESTful Web Services (2)
• Example

11. Security in Web Services
• Traditional network security (firewall, IDS) is not
enough !
• HTTPS
– User authentication assurance
• SSL/TSL
• WSS (Web Services Security)
– SOAP extention
– Integrity & confidentiality
– XML Signature & Encryption
• Separated authorization
– OAuth

12. 2. Sistem Kini
Login Home IP
Nilai Tagihan

13. 2. Sistem Kini (2)

14. 3. Analisis
• Spesifikasi kebutuhan services untuk studentportal :
1. Info jadwal kuliah
2. Info jadwal UTS/UAS
3. Info nilai mata kuliah per semester
4. Info indeks prestasi
5. Info total tagihan
• Rancangan skema API

15. 3. Analisis (2) – Perbandingan Teknologi
• Arsitektur : Traditional (SOA) vs RESTful
SOA / WS-* RESTful
SOA Middleware Architectural style for the
Interoperability Standard web
The Web is the universal The Web is the universal of
(tunneling) transport for globally accessible
message information
Enterprise computing (not Web application (only via
only via HTTP) HTTP)
Complexity Simplicity
More secure Less secure

16. 3. Analisis (2) – Perbandingan Teknologi
• Message format : XML vs JSON
XML (SOAP) JSON
Richness Simplicity
Problem domain Message domain
Document-based Data-based
Slower read/written Faster read/written

17. 3. Analisis (3)
• Kondisi sistem
– Server type : Web Server
– Protocol : HTTP
– Future client apps : Web and Mobile Apps
• maka, pilihan teknologi utama :
RESTful Web Services + JSON

18. 3. Analisis (3) – Model Usulan
REST-based UNPAR Web Services Model

19. Selanjutnya …
• Implementasi Web Services Server
• Implementasi Desktop/Mobile Client (Testing)

20. Daftar Referensi
1. Alonso, G., Casati F., Kuno H., Machiraju V., Web Services:
Concepts, Architectures, and Applications, Springer, 2003.
2. Oracle Sun Developer Network (Oracle SDN), The Java™ Web
Services Tutorial for Java Web Services Developer’s Pack
v1.6,
http://download.oracle.com/docs/cd/E17802_01/webservic
es/webservices/docs/1.6/tutorial/doc/index.html, Juni
2005.
3. Newcomer, E., Understanding Web Services: XML, WSDL,
SOAP, and UDDI, Independent Technology Guide, 2002.
4. Adams P., Easton P., Mehta B., Merrick R., SOAP over Java
Message Service 1.0, http://www.w3.org/TR/2009/CR-
soapjms-20090604/ , Juni 2009.
5. Chappel D. A., Jewell T., Java Web Services, O’Reilly Media,
2002.
6. Cerami E., Web Services Essentials, O’Reilly Media, 2002.

21. Daftar Referensi (2)
7. R.T. FIelding, R. N. Taylor. Principled Design of the
Modern Web Architecture, in the Proceedings of the 22nd
International Conference on Software Engineering,
Ireland, June 2000 (ICSE 2000), 407 - 416.
8. C. Pautasso, O. Zimmermann, F. Leymann. RESTful Web
Services vs. Big Web Services: Making the Right
Architectural Decision. in the Proceedings of the 17th
International WWW Conference, April 2008, 805-814