Скачать презентацию Sun ONE Developer Model Anne Thomas Manes Director Скачать презентацию Sun ONE Developer Model Anne Thomas Manes Director

2a099fcc6a5c9942dd46156fdf2ab87a.ppt

  • Количество слайдов: 37

Sun ONE Developer Model Anne Thomas Manes Director Market Innovation atm@sun. com Sun ONE Developer Model Anne Thomas Manes Director Market Innovation [email protected] com

Agenda • • Web Services Sun ONE Overview ONE Architecture ONE Developer Model Agenda • • Web Services Sun ONE Overview ONE Architecture ONE Developer Model

Web Services Definition Web Services Definition "Web services are loosely coupled software components delivered over Internet standard technologies. " Daryl Plummer, Gartner June 15, 2001

Web Services • Next phase in the continuum – Next generation Web applications – Web Services • Next phase in the continuum – Next generation Web applications – Web-accessible XML-based services – Internet, Intranet, Extranet – B 2 B, B 2 C, P 2 P • Evolutionary in terms of technology, revolutionary in terms of business impact

Web Services • Application Services – email, scheduling, gift registry, buy a car, stock Web Services • Application Services – email, scheduling, gift registry, buy a car, stock quotes, credit card clearance, mortgage prequalification, billing, payroll, provisioning, logistics, procurement… • System Services – storage, database, transactions, directory, security, content management, messaging, streaming media, collaboration… • May be provided by someone else … somewhere else

Web Services Characteristics • Programmatic interface • Using standard Web protocols • Loosely-coupled connections Web Services Characteristics • Programmatic interface • Using standard Web protocols • Loosely-coupled connections i. e. , XML Messaging

Web Services The Service Grid Service Registry Service discovery Service registration Service Descriptio ns Web Services The Service Grid Service Registry Service discovery Service registration Service Descriptio ns Service invocation and delivery

Web Services (current state) The Service Grid UDDI Service discovery Service registration WSDL XML Web Services (current state) The Service Grid UDDI Service discovery Service registration WSDL XML Messaging (SOAP/eb. XM L)

Web Services Emerging Standards Web Services Emerging Standards

XML Messaging Systems • • SOAP V 1. 1 SOAP V 1. 2 (W XML Messaging Systems • • SOAP V 1. 1 SOAP V 1. 2 (W 3 C XMLP) SOAP with Attachments eb. XML Message Service

SOAP Request Example <? xml version=“ 1. 0” encoding=“UTF-8”? > <SOAP-ENV: Envelope xmlns: SOAP-ENV=http: SOAP Request Example SUNW

SOAP Response Example <? xml version=“ 1. 0” encoding=“UTF-8”? > <SOAP-ENV: Envelope xmlns: SOAP-ENV=http: SOAP Response Example 16. 23

SOAP Implementations • See http: //www. soapware. org/ – 19 Java implementations • Examples: SOAP Implementations • See http: //www. soapware. org/ – 19 Java implementations • Examples: – Apache: SOAP – Idoox: WASP (plug-ins for Forte and j. Builder) – The Mind Electric: GLUE – j. Boss: ZOAP – Enhydra: k. SOAP

WSDL • • • Definitions Schema types Message formats Port types Bindings Service ports WSDL • • • Definitions Schema types Message formats Port types Bindings Service ports

WSDL Example <? xml version=“ 1. 0” encoding=“UTF-8”? > <definitions name=“my. Stock. Quote WSDL Example

<message name=“Get. Last. Trade. Price”> <part name=“request” element=“xsd: symbol”/> </message> <message name=“Return. Last. Trade.

My Stock Quote Service My Stock Quote Service My Stock Quote Service

4. 1. SW companies, standards bodies, and programmers populate the registry with descriptions of 4. 1. SW companies, standards bodies, and programmers populate the registry with descriptions of different types of services 2. Businesses populate the registry with descriptions of the services they support Marketplaces, search engines, and business apps query the registry to discover services at other companies UDDI Business Registry Business Registrations 3. Service Type Registrations Assigns a unique identifier to each service and business registration 5. Business uses this data to facilitate easier integration with each other over the Web

Request eb. XML specifications 1 eb. XML specifications detail 2 Register scenarios and implementation Request eb. XML specifications 1 eb. XML specifications detail 2 Register scenarios and implementation 4 Register company business profile eb. XML BO Library 3 eb. XML BP Model 12 DO BUSINESS! Confirm profile and scenarios Build local system implementation 9 Accept CPA 8 Submit CPA 5 y. X pan 7 m a ery bo o ut C le rio rofi ena P Sc ’s 6 y. X X’s an any 11 mp o mp C Co st io que nar e R ce ’s S X 10 any p Com Qu eb. XML BO Library eb. XML BP Model Specifications Profiles Scenarios INDUSTRY INPUT

Sun's Web Services Strategy Sun Open Net Environment (Sun ONE) • • Smart web Sun's Web Services Strategy Sun Open Net Environment (Sun ONE) • • Smart web services vision Open architecture Products Third party/ASP efforts

ONE Architecture Freedom of Choice • Platform for Web services – Future smart services ONE Architecture Freedom of Choice • Platform for Web services – Future smart services • • Open, vendor-neutral Industry standards Guidelines and recommendations Build your system your way

ONE Architecture Product Agnostic ONE Architecture Product Agnostic

ONE Architecture Standards Backplane ONE Architecture Standards Backplane

Sun ONE Integratable Stack Our Product Implementations Sun ONE Integratable Stack Our Product Implementations

Integratable Stack Build it Your Way Integratable Stack Build it Your Way

ONE Developer Model: Overview Interface Logic Business Logic Integration Logic Process XML Messages Implement ONE Developer Model: Overview Interface Logic Business Logic Integration Logic Process XML Messages Implement the Service Access data, applications, and services

ONE Developer Model: Based on Proven Platform: J 2 EE Interface Logic Business Logic ONE Developer Model: Based on Proven Platform: J 2 EE Interface Logic Business Logic Integration Logic JSP & Servlets and/or EJB JDBC, JMS, JCA & Web services

ONE Developer Model Anatomy of a Web Service ONE Developer Model Anatomy of a Web Service

JAX Pack Java APIs for XML • JAXP: Java API for XML Processing – JAX Pack Java APIs for XML • JAXP: Java API for XML Processing – (SAX, DOM, XSLT) • JAXB: Java Architecture for XML Binding • JAXM: Java API for XML Messaging – SOAP, eb. XML (document style • JAX/RPC: Java API for XML based RPC – SOAP (RPC style) • JAXR: Java API for XML Registries – UDDI, eb. XML reg/rep • JWSDL: Java API for WSDL

Inside the Interface Servlet XML Message SOAP eb. XML etc XML Message Receive XML Inside the Interface Servlet XML Message SOAP eb. XML etc XML Message Receive XML Message Extract Payload Determine Contents Determine Action Convert XML to Java Invoke Action Processor JAXM or JAX/RPC (eb. XML or SOAP) JAXP Get results Personalize data Convert Java to XML Transform XML to suit client requirements Package Payload Return XML Message RMI JAXB or JAXP (XSLT) JAXM or JAX/RPC (eb. XML or SOAP) EJBs

JSR 109 – Enterprise Web Services • Web Services Invocation Framework – Extends J JSR 109 – Enterprise Web Services • Web Services Invocation Framework – Extends J 2 EE container model – See www. ibm. com/alphaworks • Generate portable client stub from WSDL – Makes use of WSIF • WSIF automates – Payload extraction – XML to object binding – Service invocation

Summary: ONE Architecture • Guidelines for Web services – Create – Assemble – Deploy Summary: ONE Architecture • Guidelines for Web services – Create – Assemble – Deploy • Based on Java, XML, and pervasive industry standards • Fully interoperable with. Net • Sun ONE = Sun’s implementation

ONE = Freedom of Choice • Open, vendor-neutral • Your business should drive your ONE = Freedom of Choice • Open, vendor-neutral • Your business should drive your technology decisions • Don’t let your technology drive your business decisions

ONE versus. Net ONE . Net • Choice • Based on proven, existing platform, ONE versus. Net ONE . Net • Choice • Based on proven, existing platform, available today • Supports existing applications • Supports integration with through standard XML • No choice • Based on new, unproven platform, not available today • Requires re-write of existing applications • Customers are saying that Biz. Talk doesn’t

How Much is Vapour? • You can build Web services today – Build with How Much is Vapour? • You can build Web services today – Build with Java and XML • Additional tools and services are in development by Sun and partners – Tools: Forte, Cape Clear, Idoox, Tradia, IBM, The Mind Electric, Bind Systems, . . . – Services: eb. XML, UDDI, WSDL, SOAP, etc. • Future (vision) = smart services – Depends on new standards