Meaningful SOA (Berlin SOA/Cloud Symposium 2010)

transcript

APRIL 8, 2023 | SLIDE 1

www.realdolmen.com

MEANINGful SOA

Achieving Dynamic Automation and Runtime Agility

AGENDA

Background Defining MEANINGful SOA Business Case for MEANINGful SOA Tools Clarifying the Theory Q&A

BACKGROUND

Many organisations adopt the Service Orientation Paradigm Enhance the efficiency, agility, and productivity of an enterprise

by positioning services representing solution logic Each service is assigned its own distinct functional context

comprised of a set of capabilities Automate business processes through service composition An application is now just another service composition

Intrinsic Interoperability as a strategic goal Contract standardization, scalability, behavioral predictability,

and reliability Establish native interoperability within services in order to

reduce the need for integration Integration as a concept begins to fade within service-

oriented enterprises

Syntactic interoperability Ability for multiple software components to interact regardless of

their implementation programming language or hardware platform

Interfaces must conform to standards that specify consistent syntax and format across all systems

XML, WSDL, SOAP are platform independent technologies to ensure syntactic interoperability

Reducing (“loosening”) dependencies between the service contract, its implementation, and its service consumers

DIFFERENT NOTIONS OF INTRINSIC INTEROPERABILITY

DIFFERENT NOTIONS OF INTRINSIC INTEROPERABILITY (2)

Semantic Interoperability Related to the "meaning" of the exchanged information The ability of software components to have the meaning of that

information accurately and automatically interpreted and "understood".

All data must be annotated with metadata using terminology and ontology identifiers

Syntactic interoperability is the primary motivation of Web Services. Automation of information use and dynamic interoperability are the primary objectives of Semantic Web Services

CAN WE GO FURTHER?

Yes... We are still integrating using SOA design patterns

(Intrinsic Interoperability?)

Contract standardization is hard to achieve in large organisations or between many business partners

Hard to put a canonical data model in place

... we face difficulties and ... Many mappings and transformations are needed Human intervention needed to build service compositions

... that’s why we need an extra dimension! Meaning! Exchanging MEANINGful information instead of just byte

streams

SEMANTICS TO THE RESCUE?

If services published their meaning and could interpret message meaning we would be able to ...

... avoid one-off mappings decreasing complexity and rigidity ... extend the service contract with the semantics of the operations ... not only discover services based on keywords but only using

their content ... find, invoke, compose and monitor services representing

specific solution logic of having specific peculiarities

... in a preferably automatic manner.

CAPTURING MEANING

Relationships among entities declared in classes Information about classes and their relationships are

captured in ontologies

An ontology is an explicit description of concepts. It defines a common vocabulary and a shared understanding.

Industry Standard Ontologies OASIS Quantities and Units of Measure Ontology Standard Dublin Core

Document ontology FOAF (from “friend of a friend)

Describe persons and their social network Open Biomedical (http://www.obofoundry.org) Finance Ontology (http:// fadyart.com)

MEANINGFUL SOA

Combination of Semantic Web and Service Orientation Principles

Adopting standard languages OWL : Web Ontology Language - Semantic markup language

enabling the creation of ontologies. (W3C Recommendation)

OWL-S: An ontology of service concepts for describing the properties and capabilities of (Web) services in a machine interpretable form. (W3C Submission)

Objective Automatic service discovery Automatic service invocation Automatic service composition

OWL-S SERVICE INTERACTION

(1) Advertise S

erviceProfile A(2

(4) Select Service

(5) Construct and issue request

(6) Execute Service, Generate and transmit response

(1) Publish Service Model A

(5) Construct and issue request

(6) Execute Service, Generate and transmit response

OWL-S MATCHMAKING

A provider publishes services using an advertisement defined by an OWL-S compliant ontology

A consumer queries the repository using a goal query described using the same ontology

Repository matches the goal and available services and returns services able to fulfill the consumer goal

SERVICE ONTOLOGY

OWL-S is organized in three modules

Source : OWL-S: Semantic Markup for Web Services - http://www.daml.org/services/owl-s/1.1/overview/

SERVICE PROFILE

SERVICE MODEL

SERVICE GROUNDING

BUSINESS CASE FOR MEANINGFUL SOA

Tactically Applied Data Integration Data Warehousing and Business Intelligence Portal Applications and Data Mashups Data Replication, Migration, Transformation

Strategically Applied Service Discovery Entity Services Decision Services Decision making applications (tracking/tracing patterns) Enterprise Information Management

Semantic solutions have been adopted by niche vendors Collibra (http://www.collibra.com) TopQuadrant (http://www.topquadrant.com/) Cambridge Semantics (http://www.cambridgesemantics.com/) Expert System (http://www.expertsystem.net/)

Addition to existing enterprise stack of major vendors Progress TIBCO SoftwareAG IBM Oracle

CLARIFYING THE THEORY

THANK YOUjohan.kumps@realdolmen.com

Meaningful SOA (Berlin SOA/Cloud Symposium 2010)

Technology