Upload
buck-strickland
View
217
Download
0
Embed Size (px)
Citation preview
04/19/23 Dr.Withalm2 SOA Bratislava
Lectures at the University of Bratislava/Autumn 2008
29.09.2008 Lecture 1 Evolution Of Architectures- The long Way from OO to SOA
13.10.2008 Lecture 2 WEB-Services& Semantic WEB
20.10.2008 Lecture 3 SOA-Technological Basis
10.11.2008 Lecture 4 SOA-Basing on J2EE
24.11.2008 Lecture 5 SOA-Focus on Business Processes
01.12.2008 Lecture 6 B2B Frameworks and related Standards
15.12.2008 Lecture 7 WEB 2.0 & GRID
04/19/23 Dr.Withalm3 SOA Bratislava
Summary of lecture 6/1
Collaboration between organizations is primarily fostered by sharing of resources, competencies, and capacities.
Premises for collaborations among different organizations are common Business Strategies (BS), Business Models (BM), and Business
Processes (BP) Different coalition types (i.e. network, collaboration network)
correspond different integration levels (i.e. communication & integration exchange, joint goals & joint responsibilities)
Services may be distinguished in different kinds Horizontal versus Vertical ones Enterprise Collaborations versus Enterprise Interoperability Services Web Services versus Semantic Web Services
04/19/23 Dr.Withalm4 SOA Bratislava
Summary of lecture 6/2
Success of Semantic Web Services will be measured defining process areas which positively contribute to the common
business appropriate ontology, appropriate maturity level of organizations
will foster it specific goal could be
how many attempts you need to find the right web service Virtual Breeding Environment (VBE), Virtual Organizations (VO) and
typical examples Supply Chains (SC) and their actual challenges ARIS & BizTalk
BPEL, BPMN Steps from ARIS business services via BPEL/BPMN, Visual Studio
to executable BizTalk applications on respective BizTalk servers. Reference Project
04/19/23 Dr.Withalm5 SOA Bratislava
Summary of lecture 6/3
Electronic business is not an invention of the Web Already in the 80’s a standard for Electronic Data Interchange (EDI) was
established Mainly focusing on business data
Technological driver of B2B frameworks was XML United Nations bodies, OASIS (Organization for the Advancement of Structured
Information Standards) and vendors fostered the development of standards Partly standards are focusing on business data
Whereas the others tried to standardize business processes Between the involved companies of electronic business
To the first group belong: ebXML which focuses on CPP (Collaboration Partner Profile) and CPA
(Collaboration Partner Agreement) Are in some way a superset of WSDL
cXML defining structures of purchase orders or order acknoledgment UBI ended in a standard and is more or less successor of EDI
04/19/23 Dr.Withalm6 SOA Bratislava
Summary of lecture 6/4
To the second group belong: RosettaNet providing dictionaries, PIP (Partner Interface Processes), and
TPA’s (Trading Partners Agreement) -including 5 modules OBI entailing a buying organization Biztalk specifies message formats that encloses documents: provided on MS
servers Bolero.net is running on a server owned by an independent third party-
focusing on trading processes tpaML provides a special language to express agreements between business
partners Two of them are meta frameworks:
eCO architecture is an abstract architecture for B2B frameworks XCBL is a set of XML building blocks and a document framework
04/19/23 Dr.Withalm7 SOA Bratislava
Today’s Agenda
Web 2.0 Evolution Overview of ingredients SaaS
Major Trends Metaphor Ingredients Chances Premises Risks Measures
Conclusions Challenges
Grid Computing Concern Relations to other technologies Space based computing Standards Conclusions
04/19/23 Dr.Withalm11 SOA Bratislava
DNA of Web 2.0/1
RSSlinks of relevant information for the customer are visualized automatically
Tagging enables assignment/categorizing of specific areas of internet
Blogsdiaries of relevant information for different customers of all relevant information
Pod – Web Castingenables downloading of broadcastings
Social networkingenables customers to identify themselves and to get networked
WikisWikipedia information platform
04/19/23 Dr.Withalm12 SOA Bratislava
Web 2.0 /11Mash up/1
Applications use existing web-services
for assembling new services.
Web-services can only be integrated reasonable
if they provide appropriate interfaces.
As technical basis for communication
SOAP or REST based web-services are applied.
04/19/23 Dr.Withalm13 SOA Bratislava
SaaS (Software as a Service)/1Origins
Some ideas coming from the “Big Iron”
also some similar ideas as “Thin Clients” and “Application service providing” are going back to the late nineties
The primary idea of SaaS is the following
provide the user with application functionality via web clients
instead to force to install the whole application on his PC.
04/19/23 Dr.Withalm14 SOA Bratislava
SaaS (Software as a Service)/2Overview
Major Trends Metaphor Ingredients Chances Premises Risks Measures
04/19/23 Dr.Withalm15 SOA Bratislava
SaaS (Software as a Service)/3Four trends have been defined as top priorityand require immediate deep-dive actions
04/19/23 Dr.Withalm16 SOA Bratislava
SaaS (Software as a Service)/4Metaphor/Electricity
Infrastructure, i.e. cables (network, servers ...)
Different kinds of plug-ins (interfaces, no international standards)
Different adapters to appliances (integration of legacy systems)
Different utilities, i.e. high/low voltage
Different business models, i.e. business/private customers
04/19/23 Dr.Withalm17 SOA Bratislava
SaaS (Software as a Service)/5Metaphor/AMADEUS – IT Provider in Tourism
Infrastructure A dedicated network, which provides different booking
offers (flights, hotels, packages, events ...) TOMA interface is the connector to the utilities Utilities are different booking offers as
Flights, Packages: are provided by different organizations as airlines, tour operators, hotels ...
Business models consist of Access price, which is a fixed price for a period Booking fee, which is an amount of the whole booking
price
04/19/23 Dr.Withalm18 SOA Bratislava
SaaS (Software as a Service)/6Ingredients
Infrastructure containing Payment services Maintenance services Monitoring services Building of domain clusters / sub webs
Providing of domain specific services, which are separated in Basic, horizontal, vertical ones
Services are built on the four cornerstones Web2.0 Web services, SOA Semantic Web Ontology
which induces the separation in domains Interfaces to make services to be integrated with ERP and legacy
systems
04/19/23 Dr.Withalm19 SOA Bratislava
SaaS (Software as a Service)/7Premises
Technological Eclipse, IBM Websphere, Microsoft Team Foundation
Server Semantic Web languages (OWL, RDF, etc.)
Domain competency Especially in Automotive, Healthcare, Energy
Ontology Basic knowledge how ontology could be established,
which in turn also requires deep domain knowledge.
04/19/23 Dr.Withalm20 SOA Bratislava
SaaS (Software as a Service)/8Risks
Another hype? Ontology neither exists nor chance to agree on it.
Often on political reasons (i.e. Automotive sector – Odette) Services don’t meet the expectations of end users.
Neither value proposition nor relevant business models are met. Interfaces/connectors to ERP/legacy systems are too heavy to be
implemented. Are there enough technicians or business experts available? Confidential Analysis are available
04/19/23 Dr.Withalm21 SOA Bratislava
SaaS (Software as a Service)/10Challenges
Legal aspects must be solved
Above all liability issues
The crucial issue seems to be the Ontology.
Without Ontology UDDI will not work properly.
So no customer will really find the respective services!
It’s also very questionable, if Ontology will be standardized.
Some fears are concerning the quality of services.
Are they again “technical” services at the end of the day?
as we experienced with objects
SOA BratislavaSOA Bratislava
ITA ProjectCollaborative Capacity
Demand Planningas part of the
ITA Initiative
Collaborative Supply Network Excellence
München, 25.04.2008
Andreas Hametner
04/19/23 Dr.Withalm23 SOA Bratislava
Description
Refine existing capacity demand planning recommendations.
Adapt them to collaborative principles and
incorporate changes concerning the transformation from supply chains to supply networks.
04/19/23 Dr.Withalm24 SOA Bratislava
Objectives
Seamless integration of capacity management systems and principles of different OEMs and their interconnected supply networks.
Establish a protocol (data exchange) and/or a common framework for OEMs and Tiers.
Improve the planning process by having more reliable capacity information, increase transparency for all parties.
Develop an efficient capacity planning framework, improve the quality of data for demand capacity planning. Extend the existing escalation process by integrated system support to reduce response time.
04/19/23 Dr.Withalm25 SOA Bratislava
Key Actions
Project Setup (incorporate OEMs and Tiers)
06/2008 Define requirement
10/2008 Define protocol and standards for capacity planning
02/2009 POC, including a demo system
06/2009 Final Report and recommendation
10/2009
04/19/23 Dr.Withalm26 SOA Bratislava
Generische ELGA-Definition für ÖsterreichÜbersicht Basiskomponenten und Kernanwendungen
Dokumentation & Erfassung
Speicherung & Aufbewahrung
Wiedergabe & Kommunikation
Wissens-management
Verarbeitung & Datennutzung
Berichts-erstattung
& Monitoring
Unterstützung Bürger/Patienten
Unterstützung administrativer
Prozesse
Anamnese
MBDS
e-Medikation
e-ArztbriefBefund
autom.Datenübern.
Repository
Registry
e-EinweisungZuweisungÜberweis.
e-Medikation/ e-Rezept
e-Arztbrief / Entlassungs
-brief
Kataloge für Diagnosen
& Leistungen
qualitätsgesGesundheits-Informationen
Pseudony-misierung
Vorsorge-unters.
PortalAnwend-
ungen
-Prävention - Info
e-Aufnahme
e- Entlassung(Beh.-Kette)
Sicherer Online -Zugriff
ELGA-Basis-
komponenten
Voraus-Setzungenfür ELGA
LegistischeMaßnahmen
Akzeptanz-Management
Organisa-torische
Maßnahmen
Patienten- identifikation
Patienten-Index
ö-weit & EU komp.
Identi-fikation
&Authentifi-zierung
GDA
Rollen & Berechti-gungen
& Zugriffs-proto-
kollierung
Vernetzung
Portal
ELGA Kernanwendungen
Standards
e-card
e-card Netz(GIN)
MARC
IHE
Legende
Soarian Integrated Care
Security & Identity Management
e-card Erweiterungen
Semantische Technologien
e-cardPilot
NÖMED WAN
NÖMED WAN
e-cardGPA
Ergänzung um aktuelle Siemens Sicht - Quelle: ELGA-Machbarkeitsstudie, Stand Januar 2007
04/19/23 Dr.Withalm27 SOA Bratislava
SSttrruuccttuurreedd CCoonntteenntt wwii tthh ccooddeedd sseecctt iioonnss::
Reason for Referral Vital Signs
MMeeddiiccaattiioonn
Studies AAlllleerrggiieess
Social History PPrroobblleemmss
Care Plan
XDS-MS Medical Summary
Structured and Coded Header Patient, Author, Authenticator, Institution, Time of Service, etc.
Header always structured and coded
Title-coded sections with non-structured nor coded content (text, lists, tables). Simple Viewing (XML Style sheet)
Level 1Level 1
Level 2Level 2
Text StructureEntry
Text Structure Entry
Med, Problems and Allergies required as highly structured text. Text easy to import/parse
Text StructureEntry
Level 3Level 3
Med Problems and Allergies have a required fine-grain structure with optional coding. Coding Scheme not standardized, but explicitly identified.
Coded Section Entry
Coded Section Entry
Coded Section Entry
Level 3Level 3
XDS-MS enables both semantical XDS-MS enables both semantical interoperability and simple viewing !interoperability and simple viewing !
04/19/23 Dr.Withalm28 SOA Bratislava
SaaS (Software as a Service)/12SaaS business model for an Independent SW Vendor (ISV)
Key Attributes Key Components
Usage based pricing
One to many Web delivery
Modular components
Bus. functionality centric
Flexible, scalable infrastructure
Web centric applications
Remote application management
Multi-tenant and multi-instance
ISVs
Web native providers
Business service
providers
Web a Service integrators
Key Enablers
Software as a Service is the business of delivering software-powered services, not delivering software
“The ISV’s mission is no longer the creation of packaged software for the customer to install. Instead, they [ISV’s] create functional services and applications for customers to use: delivered to agreed performance levels throughout the life of the service contract.” ……Summit Strategies
04/19/23 Dr.Withalm29 SOA Bratislava
SaaS (Software as a Service)/13Distinguishing ASP from SaaS
Application Hosting Model Software as a Service Model
Customer pays on delivery of software Customer pays for delivery of functional
services
Customer responsible for software
performance
Provider responsible for software
performance
Customer responsible to customize
software to business requirements
Customer responsible to configure
software to business requirements
Customer pays maintenance to fix
software
Provider fixes software or pays penalty
for failure to meet service levels
Customer buys upgrades to keep current Provider ensures currency of solution
Source: Summit Strategies, Inc “Software Powered Services: Net-native SaaS Transforms the ISV Business Model” Feb, 2005
04/19/23 Dr.Withalm30 SOA Bratislava
SaaS (Software as a Service)/14Managed Hosting and Support for SaaS Solution
Internet connectivity & Operations
Data centre LAN infra & Operations
Server Hardware Infra & Operations
Storage & Tape HW Infra & Mgmt
OS Management
Application Operations
Cu
sto
mer
En
d-u
ser
Hel
pd
esk
(Lev
el 1
)
Ser
vice
Man
agem
ent
& R
epo
rtin
gO
S S
ecu
rity
Mg
mt
Application Management ServicesM
on
ito
rin
g
(ale
rtin
g, e
scal
atio
ns)
Hel
pd
esk
Lev
el 2
Governance & Project Management
IBM ISV
Tra
nsi
tio
n
04/19/23 Dr.Withalm31 SOA Bratislava
SaaS (Software as a Service)/15Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm32 SOA Bratislava
SaaS (Software as a Service)/16Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm33 SOA Bratislava
SaaS (Software as a Service)/17Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm34 SOA Bratislava
SaaS (Software as a Service)/18Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm35 SOA Bratislava
SaaS (Software as a Service)/19Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm36 SOA Bratislava
SaaS (Software as a Service)/20Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm37 SOA Bratislava
SaaS (Software as a Service)/21Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm38 SOA Bratislava
SaaS (Software as a Service)/21Lutz Heuser (SAP Research Director)
04/19/23 Dr.Withalm39 SOA Bratislava
Web 2.0 /31Conclusion/1
Web 2.0 provides both users and commercial interested ones crucial benefits.
Benefits of users are:
more interactivity,
more powerful user interfaces and applications,
more efficient access of any contents and their composition,
as well as the possibility to have influence on contents
building a new community of common interests.
04/19/23 Dr.Withalm40 SOA Bratislava
Web 2.0 /32Conclusion/2
For the commercial provider new instruments for marketing and selling are established as well as diverse business opportunities
and above all the evolution of the web to an efficient platform for hosting services and
applications. Certainly , there are many challenges - especially:
security and trust legal issues and technological issues.
04/19/23 Dr.Withalm41 SOA Bratislava
Web 2.0 /33Challenges/1
Security & trust:
Blog authors are engaged for writing specific opinions by organizations: i.e. Hotels
Phishing attacks Emergence of incorrect articles in Wikipedia.
Legal issues:
Clearing of Brands
Liability issues
If a provider assembles new services out of existing ones (mashups)
04/19/23 Dr.Withalm42 SOA Bratislava
Web 2.0 /34Challenges/2
Technological issues
For approaches as AJAX there are diverse options for implementation
there is not a systematic IDE-support.
On the other hand important technologies don’t exist at all or are changing permanently.
In spite of the SOA approach not all integration issues are solved.
And finally the question arises if the existing web technology is the appropriate and
stable platform.
04/19/23 Dr.Withalm43 SOA Bratislava
Grid Computing/1Overview/1
Opaque domain Is very novel and dynamic
Refining to a very new technology Commonly unknown Enjoys an increased popularity in a small but
nevertheless very dedicated circle of software experts Provides very interesting and novel solutions to
traditional problems.
04/19/23 Dr.Withalm45 SOA Bratislava
Grid Computing/3Concern of GC/1
High performance computing is prevailing technology GC is becoming more and more of high interest and of economic
relevance GC is related to
Infrastructure which enables a Coordinated common usage of any resources in
Dynamic, distributed IT systems An aggregation of multiple organizations to such an
infrastructure Is called a virtual organization (VO).
04/19/23 Dr.Withalm47 SOA Bratislava
Grid Computing/5Concern of GC/3
As VO’s generally have a large number of users and are strong distributed the following issues are of great importance Fault tolerance Load balancing Real time messaging Clustering
Which in best case are taken over by the underlying layers in a transparent way.
04/19/23 Dr.Withalm48 SOA Bratislava
Grid Computing/6 Concern of GC/4
IBM’s most important target is usage of Needless breached system resources The following figures are quoted for idle times
Mainframes 40% Servers in academic environment 90% Most PC 95%
For comparison only envisage An airline where 90% of its fleet are on ground A car manufacturer which 40% of time is not producing A hotel which is 95% vacant.
04/19/23 Dr.Withalm49 SOA Bratislava
Grid Computing/15Relations of GC to other technologies/1
All existing technologies don’t provide frameworks For the general mechanisms and services
Which are essential for the distributed usage of resources in VO’s.
Systems as CORBA or J2EE enable the realization of distributed systems Intend mainly in local resource management
Operations crosswise firewalls as well as real time and multimedia support Were not intended originally
04/19/23 Dr.Withalm50 SOA Bratislava
Grid Computing/16Relations of GC to other technologies/2
The fundamental nature of P2P- computing Server doesn’t exist
Instead a federation of engines work together Complies totally with the GC paradigm Real P2P applications are nowadays limited to vertical
domains For instance music online exchange server
Is not identified with middleware, general protocols, and functionality.
The project “JXTA” of SUN provides a set of general P2P interfaces and protocols Which are widely accepted and could be standardized.
04/19/23 Dr.Withalm51 SOA Bratislava
Grid Computing/17Relations of GC to other technologies/3
Web-Services (WS) provide dynamic discovery of services Crossways heterogeneous systems and the automatic generation of the
essential Proxies for the communication basing on defined interfaces
WS is a widely accepted industry standard and in that way Interoperability is guarantied.
WS are a central component on the road to a global GC WS don’t provide communication forms
Which raise the abstraction And in that way facilitate the development of distributed systems.
04/19/23 Dr.Withalm52 SOA Bratislava
Grid Computing/18Relations of GC to other technologies/4
That’s why technologies are requested Which provide additive essential components
Agent-based computing is one of these.
04/19/23 Dr.Withalm53 SOA Bratislava
Grid Computing/28Agents/SOA/3
Agents are working and communicating asynchronously and loosely coupled Providing a significant enlargement
In designing and implementing of systems Loosely coupling leads distributed systems to
More stability and performance Tasks must not executed synchronously
Starting with an initial action Instead they may follow the logical process
Of request and replay Batch process will be eliminated
Replaced by real time behavior In that way agents represent an equivalent architecture
For dynamic changing systems.
04/19/23 Dr.Withalm54 SOA Bratislava
Grid Computing/35Standards/1
In the context of the GLOBUS project IBM works on the Open Grid Services Architecture (OGSA)
Which strives for harmonization of Web Services and GC Main endeavor of these standardizations are common interfaces
Both for GC and Web Services.
04/19/23 Dr.Withalm56 SOA Bratislava
Grid Computing/38Conclusion/1
In the future we will encounter P2P-based virtual technologies i.e. agents and service oriented aspects
Enabling comprehensive services Difficulties and challenges are coming from paradigm shift
Similar to that of 80’s When introducing OO.
04/19/23 Dr.Withalm57 SOA Bratislava
Grid Computing/41Conclusion/4
A breakthrough will only come into sight If these utility tools are available
MS for instance facilitates the usage of software in providing Easy to handle user interfaces Easy attainable software tools for all areas
For example Visual Studio or the .Net framework.
04/19/23 Dr.Withalm58 SOA Bratislava
Summary of lecture 7/1
Web 2.0’s main focus is the different usage of the Web Social Networks, WIKI, Blogs, Active User, Personalized Web Portals
Technically there are different approaches On the server side SOA applications are prevailing
Search may take place either central or locally via P2P or Grid On the client side AJAX has been established
Important challenges which must be overcome Security and trust, legal issues and technological issues
i.e. is the existing Web technology appropriate and stable?
04/19/23 Dr.Withalm59 SOA Bratislava
Summary of lecture 7/2
SaaS origins go back on the one hand to Big Iron and on the other hand to “thin” clients of the late nineties.
Actually SaaS seems one of the mayor trends within the whole SW industry.
Specific premises, risks, and measures must be considered before SaaS will be successful
SaaS also requires specific (not only environment) ingredients An adequat business model has not really emerged
typical metephor is electricity distinguishment ASP from SaaS Vision of IBM respectively SAP
04/19/23 Dr.Withalm60 SOA Bratislava
Summary of lecture 7/3
Main concerns of Grid Computing are: Resource sharing
Personal Computer resources are only used up to 5 %
Operation of VO’s Relation GC to other technologies
Web Services, Agent based computing (P2P), CORBA, and J2EE
Web Service and Grid standards are converging Breakthrogh is dependent on the availability of easy
attainable tools.
04/19/23 Dr.Withalm62 SOA Bratislava
Farbpalette mit Farbcodes
Primäre Flächenfarbe:
R 215G 225B 225
R 130G 160B 165
R 170G 190B 195
R 220G 225B 230
R 145G 155B 165
R 185G 195B 205
R 255G 210B 078
R 229G 025B 055
R 245G 128B 039
R 000G 133B 062
R 000G 000B 000
R 000G 084B 159
R 255G 255B 255
Sekundäre Flächenfarben:
Akzentfarben:
R 255G 221B 122
R 236G 083B 105
R 248G 160B 093
R 064G 164B 110
R 064G 064B 064
R 064G 127B 183
R 255G 232B 166
R 242G 140B 155
R 250G 191B 147
R 127G 194B 158
R 127G 127B 127
R 127G 169B 207
R 255G 244B 211
R 248G 197B 205
R 252G 223B 201
R 191G 224B 207
R 191G 191B 191
R 191G 212B 231
R 255G 250B 237
R 252G 232B 235
R 254G 242B 233
R 229G 243B 235
R 229G 229B 229
R 229G 238B 245