Lesson 4. An survey of the impact on and use of Web Services in the industry today. Industry 4.1. Industry SkillBuilders, Inc. V1.

Transcription

1 Industry 4.1 Lesson 4 Industry An survey of the impact on and use of Web Services in the industry today. SKILLBUILDERS

2 Industry Lesson Objectives What companies are using it? Popular SOAP Implementations.NET Architecture Introducing Web Services to the enterprise Adoption ebxml and RosettaNet Related Standards Conclusions

3 Industry Who's Using Web Services Siebel SAP UPS Google Amazon.com Dun & Bradstreet E.piphany SAS GE GXS and Sterling Commerce Commerce One Thompson Financial Fidelity Investments So, who has announced that they ll incorporate Web Services into projects. A sampling: Siebel UAN (Universal Application Network) provides industry specific processes and customized versions of integration software from SeeBeyond Technology Corp SAP R/3 interfaces will be exposed as Web Services in mysap UPS shipment tracking service Google is exposing API to their search engine using SOAP and WSDL Amazon.com is allowing data to be received in XML format using REST and SOAP Dun & Bradstreet GlobalAccess is an address verification service E.piphany s CRM - real time personalization, call center, market data analysis SAS - will be Web Services enabled in version 9.1 GE GXS and Sterling Commerce added Web Services to their EDI offerings Commerce One Source topay application suite to be Web Services enabled Thompson Financial supplying consensus estimates financial data Fidelity Investments internally replaced multiple protocols with SOAP

4 Industry SOAP Implementations Apache SOAP / Apache AXIS Sun s JWSDP Microsoft.NET The Mind Electric s GLUE Systinet s WASP Iona s XMLBus Cape Clear Many others Many vendors are supporting SOAP in their developer products. We ve listed some popular ones here.

5 Industry NET Architecture... Web Services enable Microsoft s entire product line Delivered in pieces or embedded in new versions Foundation of.net architecture is called.net Framework Consists of Microsoft Intermediate Language (MSIL) Common Language Runtime (CLR) What is Microsoft doing with respect to Web Services? Let s take a look. Microsoft s.net architecture consists of a set of technologies designed to Web Services enable Microsoft s entire product line. These technologies are being delivered in pieces or embedded in new versions of Microsoft s products as they are upgraded. The foundation of.net architecture is called.net Framework which consists of the Microsoft Intermediate Language (MSIL) and the Common Language Runtime (CLR). Turn to the next page for a discussion of MSIL and CLR

6 Industry NET Architecture... MSIL Analogous to Java byte code Intermediate language interpreted by a virtual machine High level languages such as Visual Basic and C# are compiled to MSIL CLR Virtual machine that runs MSIL Equivalent to the Java JRE MSIL is analogous to the Java byte code. It is an intermediate language that is interpreted by a virtual machine. High level languages such as Visual Basic and C# are compiled to MSIL. The CLR is the virtual machine that runs MSIL. It is equivalent to the Java JRE.

7 Industry NET Architecture 4.7 Also includes Web Services container equivalent to J2EE MSIL code running inside this container serves a similar purpose as Java EJBs Called managed components Visual Studio.NET Development tool to code for the.net Framework Future Windows platform will include UDDI registry and XML object store Designed to replace the Windows file system The.NET Framework also includes a Web Services container that is equivalent to J2EE. MSIL code running inside this container serves a similar purpose as Java EJBs and are called managed components. Visual Studio.NET is Microsoft s development tool that allows one to code for the.net Framework. Future versions of the Windows platform will include a UDDI registry and Longhorn a XML object store designed to replace the Windows file system.

8 Industry NET My Services... A.K.A. Hailstorm Core set of personal Web Services Gives third parties controlled access to an individual s data Grantor has full control of: What information to make accessible For how long In original Microsoft plan everyone s data would be hosted by Microsoft Controversy has caused rethink of this plan.net My Services are a core set of personal Web Services that gives third parties controlled access to an individual s data. The individual granting this access have full control of what information he/she wants to make accessible to other parties and for how long. In the original Microsoft s plan everyone s data would be hosted by Microsoft. Due to the ensuing controversy Microsoft is now rethinking this approach.

9 Industry NET My Services... Data is centralized with someone Let s say someone is Microsoft Microsoft act as the trust authority Provide single sign on capability to any other site Must be compatible with.net Passport Visited sites do not have to store data No need to register on each site Since all of the individual s data is centralized say, with Microsoft, the latter can act as the trust authority for authenticating this user, effectively providing him/her single sign on capability to any other site (as long as that site is compatible with.net Passport). That site do not have to store any of the individual s data and the individual do not need to register on each site (again, as long as the site is Passport compatible).

10 Industry NET My Services Microsoft can also act as a broker Permit or prevent s or alerts If site requires credit card Can make a Web Service request to the individual s Profile service Microsoft can also act as a broker between that site and the individual, allowing or disallowing say, the sending of mail or alerts from the site to the individual. If a site needs the individual s credit card number it will make a Web Service request to the individual s Profile service and, if the individual so allowed, retrieve this information.

11 Industry My Services Core Services 14 core services Alerts Inbox Wallet Calendar Contacts Profile FavoriteWebSites Application Settings Lists Location Services Documents Presence Categories Fourteen core services are currently included in.net My Services, including: Alerts, Inbox, Wallet, Calendar, Contacts, Profile, FavoriteWebSites, Application Settings, Lists, Location, Services, Documents, Presence and Categories.

12 Industry Adoption of Web Services... Technologies still maturing should not deter organizations to start benefiting EAI will be first? Security can be more easily controlled Can start as simple point-to-point SOAP services Offered over HTTP or HTTPS Other transports permitted MQSeries Add flexibility with WSDL and UDDI registry As we have seen, many of the technologies in Web Services are still maturing, but this should not deter an organization to start benefiting from this architecture. Most likely, Web Services will start showing in Intranet applications such as EAI where security can be more easily controlled Web Services can start as simple as point-to-point SOAP services being offered over HTTP or HTTPS (SSL). One should not forget that other transports are also permitted such as MQSeries where messages can be protected albeit using a proprietary technology. Additional flexibility can be achieved using WSDL and an internal UDDI registry.

13 Industry Adoption of Web Services Adoption may be driven from vendors Packages such as ERP and CRM expose their APIs Need to subscribe will force companies Example: a stock quote service Microsoft shops will be forced to adopt by Microsoft product updates For many companies, adoption of Web Services may be driven from vendors as more and more packages such as ERP and CRM expose their APIs in the form of Web Services. The need to subscribe to an outside Web Service, say, a stock quote service may also force companies to introduce the technology. Microsoft shops will have their timetables dictated by that company as upgrades to their products increasingly include the technology. BizTalk is just one example of a package that makes use of Web Services.

14 Industry ebxml... Specification to provide EDI using Web Services Defines: business processes work flows and associated messages Uses SOAP as a protocol Does not rely on WSDL or UDDI Defines their own equivalents ebxml and RosettaNet are two initiatives that address higher levels of abstractions for B2B exchanges. ebxml is a specification to provide EDI using Web Services. It was created by a United Nations agency and OASIS to provide a complete framework for electronic transactions. Similarly to BPEL4WS it define business processes, work flows (ebxml BPS) and their associated messages. It uses SOAP as a protocol but does not rely on WSDL or UDDI preferring to define their own equivalents.

15 Industry ebXML Rely mostly on document centric data exchanges SOAP with attachments Addresses the same problem space of SOAP/WSDL/UDDI Difference is top down approach Start with business processes and then working downwards SOAP/WSDL/UDDI s approach was bottom up ebxml rely mostly on document centric data exchanges rather than parametric. It therefore makes use of SOAP with attachments rather than basic SOAP. ebxml addresses the same problem space of SOAP/WSDL/UDDI but their approach was top down starting with the business processes and then working downwards. SOAP/WSDL/UDDI s approach, on the other hand, was bottom up in that they first defined the low level protocols and are now defining work flow and transactions.

16 Industry RosettaNet RosettaNet is a similar initiative more narrow in scope than ebxml being used mostly in the electronics industry RosettaNet is a similar initiative more narrow in scope than ebxml. It is being used mostly in the electronics industry.

17 Industry Consequences of Adopting Lower of the cost of integrating Simpler access to vendor s proprietary APIs Data access enhanced to legacy and proprietary systems Systems more flexible and resistant to failures Ease of development Should accelerate development An immediate impact will be the lowering of the cost of integrating systems since both the technology and the skill sets needed for integration with Web Services is considerably cheaper than what systems integrators currently charge. Access to third party vendor s proprietary APIs will be simpler. So will the access to any external subscription services. Data access should be greatly facilitated both from legacy and proprietary systems. The need for data conversion should also be lessened as most of the data will be in XML format. Systems development should accelerate as Web Services reach a critical mass. Since each individual service serves as a building block to build higher level ones, as the number of services available increases it should be increasingly easier to build new systems.

18 Industry State of Web Services Today Basic foundation of Web Services available SOAP, WSDL, UDDI Can build relatively complex systems Deployment held back by lack of finalized standards Because security standards are not finalized: initial adoption will be inside the firewall But number of vendors provide proprietary solutions Next phase will expand to involve close business partners Final phase of adoption see the expansion to Internet The basic foundation of Web Services (SOAP, WSDL and UDDI) are currently available and can be used to build relatively complex systems. What is holding back the deployment of more sophisticated systems is not technology but the fact that not all standards (security, work flow, etc) are yet finalized. Because security standards are not yet finalized, initial adoption will be inside the firewall however, there is a number of vendors that provide proprietary solutions that can be used while a more standard solution becomes available. The next phase of Web Services adoption will then expand the circle to involve close business partners such as supply chain partners where a common security framework can be agreed upon. In the final phase of adoption, we will see the expansion to the Internet once the security, work flow and transaction standards and products are available.

19 Industry Other related standards BTP - Business Transaction Protocol BEEP - Blocks Extensible Exchange Protocol WS-Referral WS-Routing WS-Inspection WS-Transaction WS-Coordination The standards named WS-* are being proposed by Microsoft and IBM. In addition to the above, they also introduced: WS-Addressing, WS-AtomicTransaction, WS- Attachments, WS-Context, WS-Eventing, WS-Federation, WS-Reliability, WS- ReliableMessaging, WS-SecureConversation, WS-Security, WS-SecurityPolicy, WS-Discovery and WS-Trust. Some of the security related standards by W3C, OASIS and others are: XML- Encryption, XML-DSig, XKMS, SAML and XACML.

20 Industry Conclusions... A fundamentally new way of building systems? Yes, according to Microsoft No, according to the others Web Services enhances system interaction Dynamic Flexible Adaptable Required in environments like the Internet Is Web Services a fundamentally new way of building systems? Yes, according to Microsoft, no according to the rest of the industry. Web Services changes how systems interact with each other making them more dynamic, flexible and adaptable. This is a requirement in an decentralized environment like the Internet where systems come and go at will.

21 Industry Conclusions... Affects the interfaces of systems How services are discovered Decisions made at runtime Developing services on existing platforms With existing programming languages Web Services fundamentally affects the interfaces of systems and how these services are discovered. A system developed using Web Services makes many decisions at runtime as opposed to traditional systems where the developer knows already at design time the flow of the application. Developing individual services however, will continue to be done the traditional way using existing platforms and programming languages.

22 Industry Conclusions 4.22 Existing systems and application servers do not need a radical change An ideal technology for EAI Legacy systems can be wrapped Without radical change Fully realized, Web Services will blur distinction between System Module Components All viewed as XML producers or consumers Existing systems and application servers do not need a radical change to adapt to Web Services therefore Web Services are an ideal technology for EAI. Legacy systems can be wrapped as a Web Service without radically changing their inner workings. When fully realized, Web Services will blur the distinction between a system, a module and its components. They will all be viewed as XML producers or XML consumers.