EasySOA business case and real world use case 20130220
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

EasySOA business case and real world use case 20130220

  • 316 views
Uploaded on

Nuxeo EasySOA Webinar slides : EasySOA pitch and offering, retelling of the story of the AXXX use case from start to finish using screenshots takend from the latest EasySOA release, Nuxeo's......

Nuxeo EasySOA Webinar slides : EasySOA pitch and offering, retelling of the story of the AXXX use case from start to finish using screenshots takend from the latest EasySOA release, Nuxeo's contributions

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
316
On Slideshare
316
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SOA Governance A new approach with EasySOA Marc Dutoo, R&D leader – Open Wide Thierry Delprat, CTO - Nuxeo
  • 2. Overview Overview Why What Use Case Nuxeo for EasySOA Open Wide Technologies l Janvier 2013 2
  • 3. CONCEPTS OF SOA Information systems structure Business processes A middleware architecture pushing forward a model of applications interactions Keywords : loose coupling, modularity, dependencies, service level orchestrate Operational requirements Applications require made of Policies compliant with governed by constrained by Services share manage States exchange Contracts Service components Messages refer to executed on diffusés via Services registries contain Operational systems describe Protocols Schemas Open Wide Technologies l Janvier 2013 3
  • 4. SOA – STATE OF THE ART Information Systems, getting open and interconnected… Growing awareness in Information Systems Democratization of message and data exchanges Acknowledgement of architectural best practices …however… SOA projects are complex ► ► ► ► Different actors with different concerns & profiles (Business vs Technical) Technology heterogeneity (risk management) Different partners (internal vs external services) Not much knowledge sharing on how things are done Exigences SOA needs are not always well understood ► ► A lot of services have been forgotten and are waiting to be woken up New needs : Cloud, Mobility Besoins Métier d’exploitatio n Contraintes de réalisation Open Wide Technologies l Janvier 2013 4
  • 5. EASYSOA An SOA governance administration solution A critical tool for Information System Architects… …to keep in check business process consistency… …all along service lifecycle management… … from specification to development and up to service operation Developer Completion management Business User Documentation management Consistency management Information System Architect IT Staff Open Wide Technologies l Janvier 2013 5
  • 6. EASYSOA – MAIN FEATURES Developer Automated service discovery (parsing) Rapid development of services (scripting) Business User IT Staff Core Registry Cloud Platform Information System Architect Open Wide Technologies l Janvier 2013 6
  • 7. EASYSOA – TOOLS • • • • • Developer EasyWSDL Qdox SoapUI Apache CXF Node.js • • SCA / OSGi FraSCAti Studio Business User IT Staff Core • • Nuxeo DM PostgreSQL • • • • • Apache Tomcat Apache HTTP Client Nuxeo (IHM) FraSCAti Scarbo Information System Architect Open Wide Technologies l Janvier 2013 7
  • 8. EASYSOA – GOALS To ease up SOA governance… Add a lighter, non-intrusive layer over « traditional » SOA in order to provide governance overview Minimal changes on existing services and applications to maximize extracted value (documentation, practices, uses) Service quality analysis for SOA sanitization Agile approach through extracted as well as collaborative documentation and prototyping Fosters emergence and evaluation of best and most urgent needs to be implemented next using existing « traditional » SOA Version management and impact analysis of service changes (internal or external) on business processes …to secure and optimize exchanges between services of the entreprise and its partners Open Wide Technologies l Janvier 2013 8
  • 9. THE EASYSOA PLATFORM A light, non-intrusive solution An additional, non-intrusive layer over the entreprise’s SOA allowing for Web tools that ease up gathering and analysis of existing services, as well as developing simple new services using scripting, RAD or Point-and-Click. Light Core Integration « Traditional » SOA Middleware architecture A consistent multimedia registry aggregating all information, coming from automated extraction as well as manual input by SOA actors, in a Document Management (DM) solution and its indexed database, for easy high volume information management through the Web. An ecosystem of solutions and extensions allowing for compatibility with a large range of « traditional » SOA architectures to further empower them : business process modeling and execution, monitoring… The entreprise’s SOA architecture, built on « traditional » and well-known solutions is not impacted by using EasySOA Open Wide Technologies l Janvier 2013 9
  • 10. EASYSOA – PARTNERS Partner list Open Wide – Global architecture, BPM (Eclipse JWT / OW2 Scarbo), EasySOA community leader Nuxeo – Collaborative document management platform (GED / ECM) for SOA models, documents and deliverables Talend – SOA and data connectors (ETL & ESB) with graphical configuration Bull – SOA Administration & Monitoring (OW2 Jasmine) EasiFab – SOA Model (Eclipse SOA), Business monitoring (Galaxy) INRIA Labs – Light service engine (OW2 FraSCAti) Open Wide Technologies l Janvier 2013 10
  • 11. EASYSOA – SERVICE OFFERING Discovery Sanitization Gather existing services through static (files and source code) and / or dynamic analysis (messages and data flows) Put availability and quality of registered services under control Business User Cartography Service modeling, design and documentation in a collaborative platform Developer 3 1 2 Development of newly specified services 4 Operator Core Registry Cloud Platform Governance Custom dashboard generation within continuous integration process Impact analysis on service signature change Information System Architect Open Wide Technologies l Janvier 2013 11
  • 12. USE CASE ANCV (National Agency for Holiday Vouchers) 2 differents businesses, done by separate entities, each with its own Information System (IS) ► ► Selling holiday vouchers, by the DCV entity Funding holidays for underpriviledged people, by the DPS entity DPS has now decided for its IS to go beyond spreadsheets ► This use case is the real story of DPS IT being built from the ground up, rewritten with EasySOA Registry, Talend ESB and OW2 Jasmine. Existing applications ► ► SI DCV – Pivotal : management of ANCV social partners. Customized MS .NET web CRM. Uniserv : online address checking service New applications : SI DPS – APV ► Management of « holiday projects ». Subcontracted Java web business application. Has to connect with Pivotal, using services. 2013 Open Wide Technologies l Janvier 12
  • 13. Focusing on Pivotal call to APV, with address checking
  • 14. Commercial AXXX UI We b SI DCV Uniserv Partenaires sociaux SI DPS checkA ddress Pivotal CRM ? APV Web How to provide checked information from Pivotal to APV ?? How to provide checked information from Pivotal to APV Simple : : some service plumbing between both and Uniserv ! Simple some service plumbing between both and Uniserv ! But how can separate ITs share (in)formal specifications ? ? Design them But how can separate ITs share (in)formal specifications Design them together without over-meeting ? ? Have each its own point of view ? together without over-meeting Have each its own point of view ? How to set them inin stone, and still handle (unavoidable) changes ? How to set them stone, and still handle (unavoidable) changes ? How to best share knowledge about what isis being developed, so one How to best share knowledge about what being developed, so one team can easily use what the other did ? ? team can easily use what the other did How to be sure that everything that should be developed and provided How to be sure that everything that should be developed and provided has been ? ? And nothing more ? has been And nothing more ? And how can Pivotal users be really sure it it went up to the other end ? And how can Pivotal users be really sure went up to the other end ? All without burdening teams with tasks or tools they won’t use ? ? All without burdening teams with tasks or tools they won’t use
  • 15. Commercial Uniserv SI DPS OLA Pivotal CRM Cré_Pr écpte SLA WS DL Métrique business précompte BAM_ Pré_ Cpte Orchestrati on _DCV UI We b SI DCV checkA ddress WS DL OLA TdrWe bServic e WS DL 1. Specifications phase How can separate ITs share specifications ? => Nuxeo collaborative platform ! ► ► ► ► Partenaires sociaux Business concepts as well as office documents and images Tree navigation, search Document comments, preview & publishing Social features : like, follow, wall APV Web
  • 16. Commercial UI We b SI DCV Uniserv SI DPS Partenaires sociaux Pivotal CRM SLA Métrique business précompte BAM_ Pré_ Cpte 1. Specifications phase ► Business layer : Business Service, Actor, Service Level Agreement…
  • 17. Commercial UI We b SI DCV Pivotal CRM SLA Uniserv Cré_Pr écpte WS DL Métrique business précompte BAM_ Pré_ Cpte SI DPS Partenaires sociaux checkA ddress WS DL TdrWe bServic e WS DL 1. Specifications phase ► Information layer: services, by actor, full WSDL support (type extraction, preview), REST (JAXRS)-capable…
  • 18. Commercial Uniserv SI DPS OLA Pivotal CRM SLA Cré_Pr écpte WS DL Métrique business précompte BAM_ Pré_ Cpte Orchestrati on _DCV UI We b SI DCV Partenaires sociaux checkA ddress WS DL OLA TdrWe bServic e APV Web WS DL 1. Specifications phase ► Technical layer: technical constraints (« Platforms ») on Components to be developed, Operational Level Agreements… Components Platforms
  • 19. Commercial Uniserv SI DPS OLA Pivotal CRM SLA Métrique business précompte Cré_Pr écpte BAM_ Pré_ Cpte Orchestrati on _DCV UI We b SI DCV 1. Specifications phase How to set specifications in stone ? => approval & locking How to handle (unavoidable) changes ? => versioning & diff comparison Partenaires sociaux checkA ddress OLA TdrWe bServic e WS DL APV Web
  • 20. Commercial Uniserv SI DPS OLA Pivotal CRM SLA Métrique business précompte Cré_Pr écpte WS DL BAM_ Pré_ Cpte Orchestrati on _DCV UI We b SI DCV Partenaires sociaux checkA ddress OLA WS DL TdrWe bServic e WS DL 2. Development phase How to best share knowledge about what’s being developed, so one team can easily know and use what the other did ? => source code discovery, automatically at build time Registry APV Web
  • 21. 2. Development phase Service implementations and their extracted documentation Artifact dependencies Service consumptions
  • 22. Commercial Uniserv SI DPS OLA Pivotal CRM SLA Métrique business précompte Cré_Pr écpte WS DL BAM_ Pré_ Cpte Orchestrati on _DCV UI We b SI DCV Partenaires sociaux checkA ddress WS DL OLA TdrWe bServic e WS DL 2. Development phase How to be sure that all that should be developed has been ? And nothing more ? => matching dashboard and guides APV Web APV Web
  • 23. Commercial Uniserv SI DPS OLA Pivotal CRM SLA Métrique business précompte Cré_Pr écpte WS DL BAM_ Pré_ Cpte @ http://url Orchestrati on _DCV UI We b SI DCV Partenaires sociaux checkA ddress WS DL OLA @ http://url TdrWe bServic e APV Web WS DL @ http://url 3. Deployment phase : discovery of endpoints by web browsing, using HTTP Proxy or bookmarklet or directly from integrated runtimes (Talend ESB, FraSCAti / CXF)
  • 24. Commercial Uniserv SI DPS OLA Pivotal CRM SLA Métrique business précompte Cré_Pr écpte WS DL BAM_ Pré_ Cpte @ http://url SAM Agent Orchestrati on _DCV UI We b SI DCV Partenaires sociaux checkA ddress OLA WS DL @ http://url TdrWe bServic e APV Web WS DL @ http://url 3. Deployment phase SAM Agent And how can Pivotal users be really sure it went up to the other end ? => end to end business service level indicators monitoring Business service level indicators Bull OW2 Jasmine Talend Service Activity Monitoring DB Technical Monitoring console Probe Adapter Business Rules REST Registry
  • 25. All without burdening teams with tools they won’t use ? => integrate EasySOA within their own, a few ideas : Business design tool, such as Eclipse JWT Rapid online service prototyping in the Cloud, such as FraSCAti Studio up to full BPM solution, such as OW2 Scarbo 2
  • 26. EASYSOA – GOALS Store SOA model inside Nuxeo Content Repository Design specifications Implementation info Deployment architecture Nuxeo Content Repository Open Wide Technologies l Janvier 2013 26
  • 27. EASYSOA – GOALS Store SOA model inside Nuxeo Content Repository Manage configurations of the content tree ► tree snapshotting nuxeo-tree-snapshot Multi-dimensional content tree ► ► proxies and publishing faceted search custom classifications nuxeo-platform-classification Work on complex content ► ► quick preview diff between versions of SOA definitions nuxeo-diff Open Wide Technologies l Janvier 2013 27
  • 28. EASYSOA – GOALS Improve Automation Java Bean binding (5.7) simplify data structures for easy mapping playground Open Wide Technologies l Janvier 2013 28
  • 29. EASYSOA – GOALS Connect Nuxeo to ESB expose Automation Operations to the service bus ► expose high level / business custom services bridge Nuxeo event bus with the global service bus Open Wide Technologies l Janvier 2013 29
  • 30. Registry Contacts 23-27 rue Daviel 75013 Paris Tél. : 01 42 68 28 00 97, Rue Racine 69100 Villeurbanne Tel : 04 26 68 95 00 technologies@openwide.fr http://technologies.openwide.fr http://www.easysoa.org http://www.improve-foundations.com Open Wide Technologies l Juin 2012 30
  • 31. BONUS
  • 32. Even more Light tools EasySOA Proxy (“HTTP Mining”) : listen to service exchanges to ► ► ► ► ► discover and register them record and replay them play alternative exchanges suggested through correlation generate simulations or assertions trigger other services SOAPUI integration (service testing) : ► generate SOAPUI configurations filled with all EasySOA known WSDLs and endpoints (“no more URL copy / paste”)
  • 33. Even more - UIs Indicators on the SOA model ► ► ► ► ► Amount of services without documentation, Without any implementation Or consumption Or endpoint Amount of unkown (« placeholder ») implementations Service Browsing UI ► ► Service doc UI Tag them and browse by tags