Meta

July – EasySOA in the press

21 August, 2014 (18:59) | Checkpoint, News | By: Marc Dutoo

Summer holidays may have been relaxing, but EasySOA has found its way in the French online press a couple of times in July nonetheless :

Le Monde Informatique on Julyt the 17th says EasySOA enables REST-based light SOA (“EasySOA d’Open Wide : pour de la SOA légère basé sur REST”).

Silicon.fr on July the 23rd talks about EasySOA as a management tool for service-oriented information systems (“EasySOA, un outil de gestion des systèmes d’information orientés service“).

My thanks go to Stéfane Fermigier of the System@tic French competitivity cluster for spreading the word !

REST APIs for SOA ?

3 February, 2014 (16:19) | Blog | By: Marc Dutoo

There is an interesting discussion in the LinkedIn Service Oriented Architecture Special Interest Group, following top contributor Alex Yakimovitch’s question whether REST API service definition frameworks getting more traction means that they are going to be “recognized as one of the SOA implementation models”. My opinion is that such frameworks and other developments in the REST API field are going to make SOA options in the fields of platforms and tools more flexible, and here is my full answer.

In the entreprise, the ability to specify first, and then develop client and server separately according to a specified contract (such as a WSDL service definition) is paramount.

Now, it’s a little bit far-fetched to say that REST APIs don’t have service interfaces. They have some, but sometimes it’s defined in informal documentation rather than in a formal definition, or hardcoded in the server’s way of checking the format of PUT/POSTed Resources.

Actually, WSDL mixes up a lot of different features, as Eric said in first post :

  • helping check service messages, for server or client side
  • helping generate servers, skeleton or test mocks
  • helping generate clients, for testing or for client developers
  • protocol and non-functional configuration
  • possibly even documentation

WSDL is practical because it provides all-in-one, though coupled support for all these features. But this support is limited, and once the limit has been reached, said coupling prevents any further level of support. For instance, WSDL can check that a field is a string or among a list of values, but not that it should conform to a given regular expression, though it could be a valuable check to single out invalid business messages.

The solution is to decouple all these features. Provide WSDL, but if in your business domain you encounter often message validation problems, think about providing additional validation tools.

In the case of REST API, such tools are precisely decoupled. Sorry to have taken up so many lines to get there, but it’s my main point. it’s up to the API developer to choose which feature and how to use and offer to its clients. For instance,

  • Swagger provides web playground, documentation and client generation
  • RAML provides documentation, API designer and web playground, server framework, testing using SOAPUI
  • SPoRE provides portable client generation when you don’t own the API
  • JSON-Schema or RxSchema provide validation, with Schematron being more useful for sparse definitions

Indeed, providing the API is only the start, helping its users use it and get added value out of it now and in the future is the difference between a forgotten and a successful, well-liked API.

Now, obviously, there are other differences between SOAP / WSDL services and REST APIs (such as WSDL being business operation-, transition-oriented, or “RPC”-like as Eric said ; versus REST being state-oriented), but going back to the original question : until there is a REST way to do contract-based SOA development that is as easy as SOAP / WSDL (one-stop format checking, client & server generation, documentation), which is not happening tomorrow because as we’ve seen there’s no single answer, WSDL in not going anywhere. But “traditional” SOA platform and tools will learn from REST flexibility.

December – patch & community

30 January, 2014 (20:05) | Checkpoint, News | By: Marc Dutoo

First of all : let me wish a happy new year to all EasySOA enthusiasts on behalf of the EasySOA core team. May 2014 mean a lot of well defined, well supported, collaborative service architectures bringing a lot of value to their users – all of that fully automated !

Now about what happened here in December. Well, we mainly followed on promoting the EasySOA release here and there. For instance, relieve the whole EasySOA story in the latest Nuxeo newsletter (by the way, thanks, partner !). In addition, we’ve improved a few things in the Web Discovery by Browsing server (such as added company proxy support and patched a start script).

November : packaging

12 December, 2013 (18:27) | Checkpoint, News | By: Marc Dutoo

In November, our focus has obviously been on releasing EasySOA Registry 2.0. But this has entailed a wide array of things, comprising obviously packaging it, testing it and updating documentation, but also cleaning up its web UI and improving samples on one side, and on another side updating website pages, explaining features in the new eponym Blog category, and finally promoting it through a (French) press release, various social networks and our related communities.

We’ve even done a big translation effort on the side – now almost all pages are available in English as show screenshots – which will probably be worthy of a new minor release, stay tuned !

EasySOA Registry 2.0 at Nuxeo Blog

10 December, 2013 (15:13) | News | By: Marc Dutoo

Together with our colleagues at Nuxeo, we’ve worked on a new article on the Nuxeo Blog. It focuses on why and how the Nuxeo document management platform is used in EasySOA. It also provides a good depiction of our motivations in creating EasySOA Registry, and of the current state of things now that the 2.0 release is out.

EasySOA 2.0 – Téléchargement

28 November, 2013 (13:45) | News | By: Marc Dutoo

Télécharger EasySOA Registry 2.0  (installation, usage, sources)

La solution EasySOA Registry 2.0 comprend le registre coeur SOA – métier, avec ses quatre catégories fonctionnelles : Cartographie, Conformité, Monitoring et Gouvernance. Cela inclut les interfaces utilisateur pour

  • la navigation dans les services, dont la Fiche Service, portail de la documentation et des outils des définitions / implémentations / déploiements de services,
  • la réconciliation des services implémentés et déployés avec leur définition attendue,
  • le monitoring du niveau de service métier,
  • les indicateurs (dont les indicateurs agrégés de complétion et gouvernance),
  • la documentation et l’édition collaborative du modèle SOA,
  • l’aide et les liens vers les autres fonctionnalités : API REST, outil SOAPUI, ainsi que ceux listés ci-dessous, mais aussi ceux mis à disposition indépendamment comme OW2 FraSCAti Studio et OW2 Jasmine.

Cela inclut aussi

les autres composants d’EasySOA sont mis à disposition indépendamment :

  • EasySOA Light – FraSCAti Studio (scripting et déploiement d’orchestrations de services entièrement dans le Cloud), dans OW2 FraSCAti (site web, source)
  • EasySOA Light – les fonctionnalités d’enregistrement, rejeu et simulation HTTP du composant EasySOA Proxy, dans la démo 0.4
  • EasySOA Integration – l’export de Eclipse JWT vers EasySOA (et le framework d’export EMF vers CMIS), dans Eclipse JWT (site web, documentation, source) et la future solution Scarbo 2 de gestion de processus métier (BPM) cohérents avec la SOA
  • EasySOA Integration – Talend ESB et notamment le composant Talend Service Activity Monitoring (SAM)
  • EasySOA Integration – La solution de monitoring OW2 Jasmine (et l’adapteur Jasmine pour EasySOA pour le cas d’usage AXXX)
  • exemples – cas d’usage AXXX  (source)
  • exemples – PureAirFlowers, SmartTravel, Airport et EventPAFGlue, dans la démo 0.4

Captures d’écran

Ayant remplacé les captures d’écran de la release EasySOA 2.0 par des version anglaises, j’ai déplacé les captures originales en Français ici :

Accueil

Accueil

Graphe d'avancement du Projet SOA et indicateurs agrégés
Graphe d’avancement du Projet SOA et indicateurs agrégés
Analyse d'impact SOA
Analyse d’impact SOA
Fiche Service - documentation agrégée
Fiche Service – documentation agrégée
Fiche Service - outils des services déployés
Fiche Service – outils des services déployés
Monitoring de la qualité métier d'un service
Monitoring de la qualité métier d’un service
Découverte à l'exécution - interface de gestion du proxy HTTP
Découverte à l’exécution – interface de gestion du proxy HTTP
Interface de découverte de services par navigation
Interface de découverte de services par navigation
Interface d'édition collaborative du modèle SOA
Interface d’édition collaborative du modèle SOA
Mise en correspondance - encore quelques services déployés à relier
Mise en correspondance – encore quelques services déployés à relier

Matching Dashboard tunable suggestions

28 November, 2013 (12:07) | Blog, Feature | By: Marc Dutoo

The Matching Dashboard allows EasySOA users to reconcile newly discovered service implementations (for instance, extracted from source) or deployments (for instance, scraped on the web or monitored) with already known service definitions, when the automated matching algorithm has not enough information to decide on itself. But did you know it provides tunable suggestions thanks to the same matching algorithm ?

Choosing the implementation of a service deployment (endpoint)

Choosing the implementation of a service deployment (endpoint)

Indeed, the matching algorithm even ensures that any match chosen by the user will be consistent, meaning the service definition type (in SOAP, the Port type) and platform constraints (ex. developed in Java) will match. For instance, when you want to select for your AccountService among integration deployments (endpoints) the production one, it will only list deployments of AccountService.

But what if you’re fronting the deployment of the actual implementation with a Proxy implementation of it to inject it with additional logging or data check features ? There will be two matching deployments of the AccountService ! So how to choose the front one among them ? Well, you first have to define in the Specification phase which Information System components hosts which service. Then in the Matching Dashboard, you can explicitly say that it should belong to the AccountService ESB component and not the AccountService application, which will tell the matching algorithm to also match platform constraints, that is that the implementation should be done on top of an ESB and not in Java.

Telling which Information System component hosts the front service

Telling which Information System component hosts the front service

So a single suggestion will be listed, without any risk of mixing it up.

October : offering

25 November, 2013 (15:00) | Checkpoint, News | By: Marc Dutoo

In October, here at Open Wide we’ve worked on our brand new EasySOA offering, and finally came at a point where we’ve been able to publish it on Open Wide’s website. Note that is is only available in French for now, but to get the gist of it you can have a look at the What is EasySOA page, or let Google translate it. As always, feedback welcome !

HTTP Proxy for runtime monitoring discovery

22 November, 2013 (11:54) | Blog, Feature | By: Marc Dutoo

In EasySOA Registry 2.0, the HTTP Proxy is now part of the release. But did you know its management web interface prevents users from stepping on each other’s feet by forbidding to use it at the same time to discover services in different projects  ?

Runtime discovery - HTTP proxy management UI

Runtime discovery - HTTP proxy management UI

This web page displays all configuration properties of the service discovery probe within the EasySOA Proxy. For instance, it says on which port on which host service exchanges are listened to. But it especially displays properties defining where discovered services are registered : in which context (SOA Project and Phase, here respectively Intégration DPS – DCV and Deploiement) and in which environment (here, Production).

These properties are filled when the user (here, Administrator) clicks on “Service Discovery by Runtime monitoring” buttons in EasySOA Registry. For instance, when the user clicks on it in the Service Browsing UI of a service deployment (endpoint), it is filled by this service deployment’s Project and Phase, and from now the Proxy can only be asked to discover services from the same User, Project and Phase, at least until the Proxy configuration is explicitly reset.

At the end, what’s actually interesting to users is obviously that all those Probe configuration properties make it in the registry (save User which is soon upcoming) and appear there on discovered service deployments and service consumptions that the Proxy registers when it sees a message exchange corresponding to a service call from a consumption host to a deployment url, along service- and exchange- specific information extracted from this monitored flow.

Note that there is a single instance of the Proxy, though allowing to create new ones on demand is in the works. Technically, this is being done by making out of the Proxy an OW2 FraSCAti Studio generated template application.

EasySOA 2.0 – Captures d’écran en français

20 November, 2013 (02:13) | News | By: Marc Dutoo

Ayant remplacé les captures d’écran de la release EasySOA 2.0 par des version anglaises, j’ai déplacé les captures originales en Français ici :

Accueil

Accueil

Graphe d'avancement du Projet SOA et indicateurs agrégés

Graphe d'avancement du Projet SOA et indicateurs agrégés

Analyse d'impact SOA

Analyse d'impact SOA

Fiche Service - documentation agrégée

Fiche Service - documentation agrégée

Fiche Service - outils des services déployés

Fiche Service - outils des services déployés

Monitoring de la qualité métier d'un service

Monitoring de la qualité métier d'un service

Découverte à l'exécution - interface de gestion du proxy HTTP

Découverte à l'exécution - interface de gestion du proxy HTTP

Interface de découverte de services par navigation

Interface de découverte de services par navigation

Interface d'édition collaborative du modèle SOA

Interface d'édition collaborative du modèle SOA

Mise en correspondance - encore quelques services déployés à relier

Mise en correspondance - encore quelques services déployés à relier

EasySOA

Copyright © 2010-2012,
EasySOA Consortium

Powered by Wordpress

RSS/Atom | Contact

Sitemap

Who is behind EasySOA?