Studio dell'approccio SOA realizzato mediante REST service su IBM WebSphere Commerce

Come WebSphere Commerce implementa l'architettura SOA

SOAP vs. REST in un contesto di Informatica Gestionale

Il web è cambiato! In questi ultimi anni internet ha subito grandi cambiamenti, è passato da un web formato da sole pagine ad un web fornitore di servizi. Questi servizi chiamati ‘Web Service’ vengono utilizzati ampiamente per sviluppare la maggior parte delle applicazioni web. A questo proposito, viene presentata brevemente la tecnologia dei Web Service, per passare successivamente ad analizzare due tipi di standard: quelli basati su SOAP con disegni strettamente accoppiati simili a chiamate di procedura e quelli basati su REST con disegni debolmente accoppiati, simili alla navigazione di link. Questa tesi si pone l’obiettivo di fornire informazioni sulle caratteristiche, l’interoperabilità, le differenze e l’implementazione dei due standard, descrivendo l’utilizzo di queste architetture in un contesto di informatica gestionale, nello specifico, lo scenario di Infor ERP LN.

REST SERVER IN JOLIE - Practical Case

The aim of this thesis is to merge two of the emerging paradigms about web programming: RESTful Web Development and Service-Oriented Programming. REST is the main architectural paradigm about web applications, they are characterised by procedural structure which avoid the use of handshaking mechanisms. Even though REST has a standard structure to access the resources of the web applications, the backend side is usually not very modular if not complicated. Service-Oriented Programming, instead, has as one of the fundamental principles, the modularisation of the components. Service-Oriented Applications are characterised by separate modules that allow to simplify the devel- opment of the web applications. There are very few example of integration between these two technologies: it seems therefore reasonable to merge them. In this thesis the methodologies studied to reach this results are explored through an application that helps to handle documents and notes among several users, called MergeFly. The MergeFly practical case, once that all the specifics had been set, will be utilised in order to develop and handle HTTP requests through SOAP. In this document will be first defined the 1) characteristics of the application, 2) SOAP technology, partially introduced the 3) Jolie Language, 4) REST and finally a 5) Jolie-REST implementation will be offered through the MergeFly case. It is indeed implemented a token mechanism for authentication: it has been first discarded sessions and cookies algorithm of authentication in so far not into the pure RESTness theory, even if often used). In the final part the functionality and effectiveness of the results will be evaluated, judging the Jolie-REST duo.