Enterprise Collaboration & Web Services Summary

1. SOA Part1 Lecture 5 Dr. Withalm 6-Jan-20

2. Lectures at the University of Bratislava/Autumn 2017 03.10.2017 Lecture 1 The long Way from OO to SOA & WEB- Services 17.10.2017 Lecture 2 Semantic WEB & SOA-Technological Basis 14.11.2017 Lecture 3 SOA-Basing on J2EE & SOA-Focus on Business Processes 21.11.2017 Lecture 4 B2B Frameworks and related Standards 28.11.2017 Lecture 5 WEB 2.0 & GRID & Cloud Computing Dr.Withalm

3. Summary of lecture 4/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 Dr.Withalm

4. Summary of lecture 4/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 Dr.Withalm

5. Summary of lecture 4/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 acknowledgment • UBI ended in a standard and is more or less successor of EDI Dr.Withalm

6. 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 Dr.Withalm

7. Today’s Agenda • SaaS • Origin • Major Trends • Back Ground & Context • Business Strategies • Business Models • Metaphor • Ingredients • Premises • IBM’s View • Methodology • Grid Computing • Concern • Relations to other technologies • Space based computing • Standards • Conclusions • Web 2.0 • Evolution • Overview of ingredients • Mash Up • Challenges • Conclusion • Cloud Computing • Definition • Service Delivery Levels • Deployment Models • Architecture • Standards Dr.Withalm

8. Evolution of the Web/1 Dr.Withalm

9. DNA of Web 2.0/1 Dr.Withalm

10. 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 • Liabilityissues • If a provider assembles new services out of existing ones (mashups) Dr.Withalm

11. Web 2.0 /34Challenges/2 • Technological issues • For approaches as AJAX there are diverse options for implementation • there is not a systematic IDE (Integrated Development Environment) -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. Dr.Withalm

12. 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. Dr.Withalm

13. 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. Dr.Withalm

14. Cloud Computing/Definition • The notion of what exactly is cloud computing is ... cloudy -- numerous definitions exist. A rather well-founded definition is provided by the US National Institute for Standards and Technology (NIST) • Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources • e.g., networks, servers, storage, applications, and services • that can be rapidly provisioned and released • with minimal management effort or service provider interaction. • As most other definitions, NIST's definition describes three service-delivery models for cloud computing Dr.Withalm

15. Cloud Computing/Service Delivery Levels • Cloud Software as a Service (SaaS) • The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure and accessible from various client devices through a thin client interface such as a Web browser (e.g., web-based email). • Cloud Platform as a Service (PaaS) • The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created applications using programming languages and tools supported by the provider (e.g., java, python, .Net). • Cloud Infrastructure as a Service (IaaS) • The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. Dr.Withalm

16. Cloud Computing/SaaS Layer • The SaaS layer is regarded as the application layer, delivering applications over the browser or composite high-level services. • It's important to mention that cloud computing is not stuck to thin-clients. • The smart phone shows that the smart client is used in practice. Therefore, new client technology, running as plug-in in the browsers, • for example Microsoft's Silverlight, Adobe's AIR, Flash, Java FX,Google Chrome, are required to deliver the required user experience. • Prominent examples are, Microsoft online (BPOS) and live, Goggle Apps, Salesforce CRM, • SuccessFactors, Apple's AppStore and many more. Dr.Withalm

17. Cloud Computing/PaaS Layer/1 • The PaaS layer consists of a platform technology and typical foundation infrastructure services. This could be split up in the platform and service. • The architectural platform aspect can be compared to a typical desktop operating system and infrastructure services to typical network services required in an enterprise environment. • The platform part covers the abstraction for resource management • computation, storage, network • The service part covers services for • directories, search, billing. Dr.Withalm

18. Cloud Computing/PaaS Layer/2 • Current examples are Windows Azure, Goggle App Engine, Force.com. All three offerings can be regarded as PaaS, but are very different. • Windows Azure is much like an .net operating system open for developing like for an on-premise OS • Google App Engine is intended to allow glue logic in Java and Python for Google Apps • Force.com is a fully proprietary platform with specific programming language and useful services in the CRM domain. • The common advantage of cloud platforms is their focus on scalability, reliability and low operating cost. • Existing applications cannot be transferred from on-premise to cloud platforms; • they typically have to be reengineered in order to gain the benefit of seamless Internet scale. Dr.Withalm

19. Cloud Computing/IaaS Layer • The IaaS layer covers all the current offerings in the virtualization domain. • The market leader is Amazon (Elastic Cloud) • typically offering hosted operating systems like Windows or Linux. • These virtualized offerings allow fast scale of virtualized hardware, but does not scale up applications, if they are not developed for scalability already. • But also the new types of services, called storage services are related to the infrastructure level. • Prominent offerings are: Amazon Simple Storage (S3), SimpleDB, Windows Azure Storage, Google Storage. • Furthermore, infrastructure services for synchronization are provided. Dr.Withalm

20. Cloud Computing/Deployment Models • Private cloud • The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise. • Community cloud • The cloud infrastructure is shared by several organizations (e.g. SC, CNO) and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise. • On-premises software is installed and run on computers on the premises (in the building) • off-premises software is commonly called "software as a service" or "computing in the cloud." • Public cloud • The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services. Dr.Withalm

21. Cloud Computing/Hybrid Cloud • These deployment models can be mixed as a "hybrid cloud": • the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique • entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting). Dr.Withalm

22. Service View vs. Architecture View • The big number of different definitions and the current buzz around cloud computing, leads to different interpretations of cloud computing. • Therefore, a cloud computing reference architecture model is introduced which allows • relating technological and architectural aspects to service view aspects. • Cloud computing novelty comes from the composition of existing technologies combined with new business models for software and service selling. It's not a single new technology. Dr.Withalm

23. Cloud Computing Architecture Dr.Withalm

24. Cloud Computing/Standards • Cloud computing heavily relies on Web standards (protocols, e.g. SOAP and REST, security, e.g. SAML (Security Assertion Markup Language ),OAuth (Open Authorization), etc.) • but there are no specific cloud computing standards for elements and processes • such as APIs, the storage, data import and export, and backup. • Furthermore, application portability is difficult, because the platform concepts differ in resource scheduling and resource access and control from current on-premise concepts. Dr.Withalm

25. Cloud Computing/Success Factors/1 • Generic cloud computing aspects • Low price • Flexible contractual models • Relevant factors in SaaS • Best-of-breed support for the company processes that are mapped • The provider’s economic reliability • Integration and migration interfaces • References and flexible price models Dr.Withalm

26. Cloud Computing/Success Factors/2 • Key aspects for PaaS providers • Size of the community entrusted with developing the technology in question • Simplicity of service deployment • Architecture frameworks that support automatic scaling • Key aspects for IaaS providers • Leveraging economies of scale • Advantages in price/performance ratio • Availability • Security • Network connection’s bandwidth Dr.Withalm

27. SaaS (Software as a Service)/2Overview • Origin • Major Trends • Back Ground & Context • Business Strategies • Business Models • Metaphor • Ingredients • Premises • IBM’s View • Methodology Dr.Withalm

28. SaaS (Software as a Service)/1Origins • Some ideas are 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. Dr.Withalm

29. Background and ContextDistinguishing ASP from SaaS Source: Summit Strategies, Inc “Software Powered Services: Net-native SaaS Transforms the ISV Business Model” Feb, 2005 Dr.Withalm

30. SaaS-U SaaS Subscription Value Driven (based on function commoditisation) Variable Usage (Metered) Hybrid (Fixed & Variable Usage) Simple Increments (modify CPU/ tiered models) Today’s Models (mostly fixed) Marginal cost > 0.0 Value based dynamic pricing Service infrastructure as utility Innovation focused Variable costs Shared resources Service oriented2463 2463 Fixed costs Dedicated resources Product oriented IT Plug IT Switch IT Tap Background and ContextA tentative Roadmap towards SaaS-U Dr.Withalm

31. Business Strategies • Intellectual property • Bundling • Standards • Open source • Long tail • “Free” • FUD (Fear, Uncertainty and Doubt) Dr.Withalm

32. Utility based business models: Issues & Questions Dr.Withalm

33. MetaphorElectricity • 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 Dr.Withalm

34. MetaphorAMADEUS – 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 Dr.Withalm

35. Ingredients • 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 Dr.Withalm

36. Premises • 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. Dr.Withalm

37. IBM’s ViewManaged Hosting and Support for SaaS Solution Governance & Project Management Application Management Services Application Operations OS Management Helpdesk Level 2 Service Management & Reporting CustomerEnd-user Helpdesk (Level 1) Storage & Tape HW Infra & Mgmt Transition OS Security Mgmt Monitoring (alerting, escalations) Server Hardware Infra & Operations Data centre LAN infra & Operations Internet connectivity & Operations IBM ISV Dr.Withalm

38. MethodologySaaS/1 • EI Services which are available on the GSP (Generic Service Platform) will be provided via the SaaS concept. • which is an emerging concept for current and future networked enterprises • SaaS is a model for SW deployment with the following characteristics: • application is hosted as a service provided to customers across the Internet. • application must neither be installed nor run on the customer's own computer • alleviates the customer's burden of software maintenance, ongoing operation, and support. • customers relinquish control over software versions or changing requirements. • conceivably reduce that up-front expense of software purchases • through less costly, on-demand pricing. Dr.Withalm

39. MethodologySaaS/2 • From the software vendor's standpoint following issues are from importance: • it has the attraction of providing stronger protection of its intellectual property • establishing an ongoing revenue stream • may host the application on its own web server • this function may also be handled by a third-party application service provider (ASP). • This way, end users may reduce their investment on server hardware too. Dr.Withalm

40. MethodologySaaS/3 • Many types of software are well suited to the SaaS model • where customers may have little interest or capability in software deployment, but do have substantial computing needs. • Such Application areasare for instance: • Customer relationship management (CRM) i.e. Salesforce • Video conferencing • Human resources • IT service management • Accounting • IT security • Web analytics • Web content management • e-mail are • These are the initial markets showing SaaS success Dr.Withalm

41. MethodologySaaS/4 • SaaS solutions were developed specifically to leverage web technologies • such as the browser, thereby making them web-native. • Both data design as well as architecture of SaaS applications are specifically built with a 'multi-tenant' backend • Multi-tenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). • thus enabling multiple customers or users to access a shared data model. • This further differentiates SaaS from client/server or 'ASP' (Application Service Provider) solutions • because SaaS providers are leveraging enormous economies of scale • in the deployment, management, support and through the Software Development Lifecycle. Dr.Withalm

42. MethodologySaaS/5 • A new implementation of the SaaS vision is expected • supporting the various collaborative business forms, from supply chains to business ecosystems • and becoming for them like a utility, a commodity, the so-called Interoperability Service Utility (ISU) • ISU will not just create a service platform • but mainly a new business concept – the Software-as-a-Service Utility (SaaS-U) model. Dr.Withalm

43. MethodologySaaS-U/1 • can be seen as a software application delivery model • where a software vendor develops Web-native software services • hosting and operating them for use by its customers over the Internet. • Customers do not pay for owning the software itself any longer but rather for using it on-demand. • They use it through an API accessible over the Web and often written using Web services. • fits also well with modern SOA architectures • aiming to promote software development in a way that leverages the construction of dynamic software systems • which can easily adapt to volatile user environments and be easily maintained as well. Dr.Withalm

44. MethodologySaaS-U/2 • SOA enables flexible connectivity of applications by representing every application as a service with a standardized interface. • enabling to exchange structured information quickly and flexibly. • This flexibility enables new and existing applications to be easily and quickly combined • to address changing business needs, and the ability to easily combine and choreograph applications • allowing IT services to more readily reflect business processes Dr.Withalm

45. MethodologySaaS-U/3Open Issues/1 • Are there success stories/lessons learned in specific domains concerning experience of ISU/SaaS-U? • SaaS-U will undergo further transformation • In business models for SaaS-U the providing of platforms should be taken into account • What’s the borderline between value added services and utility services: concretely is payment an utility service? • Do utility services belong to horizontal services? • Consider the differentiation between horizontal and vertical services. • Assessment respectively certification authorities could be another type of stake holder: especially in the crucial issues as QoS (Quality of Service), liability, reliability, SLA (Service Level Agreement). • There are doubts that ISU will bring intelligence in the network. • Discussions about the different types of metaphors especially concerning the tab: is mixture of cold and warm water really a metaphor for ISU? • Distinguish among cost based and market based prices • IPR (and patents) also for SW solutions are encouraged by CMMI assessments : could this fact increase prices for ISU Dr.Withalm

46. MethodologySaaS-U/3Open Issues/2 • 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 Dr.Withalm

47. MethodologySaaS-U/3Open Issues/3 • 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? Dr.Withalm

48. 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. Dr.Withalm

49. 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). Dr.Withalm

50. 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. Dr.Withalm