웹서비스 주요 동향과 전망

1. 웹서비스 주요 동향과 전망 ㈜ 아이티올로지 조원석

2. 목차 • 웹서비스의 개념 • 웹서비스의 기반기술 • 주요 웹서비스 트렌드 • 웹서비스 주요벤더 및 전략 • Comparison of Approach • 웹서비스의 Limitation • 웹서비스 시장 전망

3. 웹 서비스의 개념 – General Description Within a broad context, a Web Service is any component that: • Is network-based, modular, self-contained, self-describing, • Offers platform and implementation neutral services, • Conforms to a set of open standards and specifications, and • Leverages a common infrastructure for description, discovery and invocation. Web services (sometimes called application services) are services (usually including some combination of programming and data, but possibly including human resources as well) that are made available from a business's Web servers for Web users or other Web-connected programs.

4. 웹서비스의 개념 - SOA • SOA (Service-Oriented Architecture) A service provider can publish the availability of its service(s) and respond to requests to use, or, alternatively it can bind to its service(s). Service Provider A service requester uses service brokers to find the services needed to construct a solution, or part of a solution, and then invokes (binds to) those services offered by service providers. Publish Bind Service Broker Service Requester Find A service broker allows service providers to publish (register and categorize) themselves and their services; a service broker also offers find mechanisms for business entities attempting to locate appropriate services for use in a solution.

5. 웹서비스의 개념 – Technical Aspect • Embed functionality seamlessly • Remove duplication of functionality from otherwise discrete applications • Centralize functionality to teams or locations with competitive and financial advantages • Gain access to functionality or services that we need but can’t perform • Broaden our choice of functionality publishers • Consider outsourcing functionality requirements

6. 웹서비스의 개념 – Business Aspect • Concentrate development efforts on computing assets that drive revenue. • Outsource services that provide no business Value-add. • Evolve business models and relationships as necessary • Reduce costs of internal integration and of testing emerging market opportunities. • Establish interactions with marketplaces more efficiently • Deliver business functions to a broader set of customers and partners, if appropriate.

7. 웹서비스의 개념 - Flow Dynamic e-businesses can maximize their reach to customers, partners, suppliers, and market places, and minimize their costs and time to market. Business can leverage flexible and dynamic business models, through just-in-time integration. These solutions can change the target and even the nature of interactions based on changing business conditions. Quick composition and deployment of solutions based on reusable components from the lowest cost provider. Web services decouple applications and infrastructures.

8. 웹 서비스의 기반기술 - XML • XML (eXtensible Markup Language) • XML is a flexible way to create common information formats and share both the format and the data on the World Wide Web, intranets, and elsewhere. • ebXML (e-Business XML) • XAML (Transaction Authority Markup Language)

9. 웹서비스의 기반기술 - SOAP • SOAP (Simple Object Access Protocol) defines a standard XML-based layout of messages to be exchanged from one system to another. • SOAP spells out the format of a message Header and Body. • SOAP defines rules for encoding data into messages and decoding data from messages.

10. 웹서비스의 기반기술 - UDDI • UDDI (Universal Discovery, Description and Integration) • UDDI is a standard that provides an information model used to describe a business and its services. • UDDI defines a standard SOAP-based API used to interact with UDDI registry. • There are three public registries in operation today. • WSIL (Web Service Inspection Language) • IBM and Microsoft • WSIL allows applications to browse Web Servers for XML Web Services. • WSIL will make it easier to discover available services on Web sites not listed in the UDDI registries.

11. 웹서비스의 기반기술 - WSDL WSDL (Web Service Definition Language) • WSDL is an XML-based language which can be used to formally specify the interface of a Web service. • The Interface consists of all the operations supported by the Web service along with information about the input and output arguments for each operation. • Most application servers and tools support WSDL.

12. 주요 웹서비스 트렌드 • Web Services industry doesn’t have any benchmark industry to learn from. • Rather than considering the overall architecture of a Web Services business model, the present trend seems to be for companies to produce development tools in a market that is still maturing.

13. 웹서비스 주요 벤더 및 전략(1) • IBM • WebSphere Application Server • Sun • SunONE Strategy • Hewlett-Packard • e-Speak & Netaction • Microsoft • .NET platform

14. 웹서비스 주요 벤더 및 전략(2) - IBM • IBM is one of the big supporters Web services. • IBM embedded the open standards that Web services are built on (SOAP, UDDI, WSDL) into its WebSphere application server, its MQ Series middleware, its database server DB2, as well as in its Domino and Tivoli.

15. 웹서비스 주요 벤더 및 전략(3) - Sun • Sun announced its ONE (Open Net Environment) on the 2001/2. • Scott McNealry described Sun’s Smart Services as “an intergratable stack of software that allows you to create smart network services”. • Sun ONE supports XML and SOAP. • The Liberty Alliance Project • Sponsored by Sun, IBM, Nokia, Phillips, Vodafone, Verisign, RSA and others against Passport online authentication service. • Java has most of the requirements already in place for creating Web services and there is an extensive knowledge

16. 웹서비스 주요 벤더 및 전략(4) – HP • HP pioneered the Web Services idea, creating the Java-based e-speak in early 1999. • A service available via the Internet that completes tasks, solves problems or conducts transactions. • Netaction is the new marketing name for HP’s Web Service product line, the core of HP’s e-service technology remains e-Speak. • e-Speak Service Engine • e-Speak Framework Specification. • e-Speak architecture supports XML for defining and registering Web services, Microsoft’s BizTalk vocabularies, SOAN and the UDDI project.

17. 웹서비스 주요 벤더 및 전략(5) – Microsoft • 2000/6 Microsoft announced “Microsoft .NET” • The most ambitious project Microsoft has undertaken. • By founding the development of SOAP as well as adopting XML into its .NET server architecture, Microsoft clearly shows the importance of Web Services in the company. • .NET programming model, including a ASPNG for SOAP-based service delivery, will help Web Services supplant the COM family architecture of Microsoft’s heritage.

18. Comparison of Approach Service Description: • J2EE • J2EE-enabled Web Services exchange information using WSDL to come to an agreement on the proper format for each transferred XML document. • 3rd parties who want to transact business with a J2EE-enabled Web Service company can lookup information about the company’s Web Services in a registry. • .NET • A .NET Web Services uses a WSDL document to describe itself. • XML namespace is used within a WSDL document to uniquely identify the Web Service’s endpoints.

19. Comparison of Approach Service Implementation: • J2EE • Existing Java classes and applications can be wrapped using the JAX-RPC and exposed to as Web Services. • .NET • All programs will be compiled to an MSIL (Microsoft Intermediate Language). • This portable, binary code is then executed in a CLR (Common Language Runtime)

20. Comparison of Approach Service Publishing, Discovery, and Binding: • J2EE • JAXR (Java API for XML Registries) is used as a single general purpose API for interoperating with multiple registry types. • JAXR allows its clients to access the Web Services provided by a Web Services implementer exposing Web Services built upon an implementation of the JAXR specification. • .NET • XML-based DISCO (Discovery) file is used to determine what services are available. • Clients can access a specific DISCO file or browse for DISCO files starting at the root of the Web Server.

21. Comparison of Approach Service Invocation and Execution: • J2EE • JAX-RPC is used to send SOAP method calls to remote parties and receive the result. • .NET • Gain access to a Web Services by implementing a Web Service listener. • To implement this, a system needs to understand SOAP messages, generate SOAP responses, provide a WSDL contract for the Web Services, and advertise the Service via UDDI.

22. 웹서비스의 Limitation • Limits of in-house skills • Matching suitable services • Generic vs. Custom • Granularity of service exposure • Ensuring continuity of Web Services supply

23. 웹서비스 시장 전망 – Benefits Summary • Web Services promote interoperability • Interaction between a service provider and a service requester is designed to be completely platform and language independent • Web services enable just-in-time integration • As service requesters use service brokers to find service providers, the discovery takes place dynamically. • Web services reduce complexity through encapsulation • Service requesters and providers concern themselves with the interfaces necessary to interact with each other. • Web services give new life to legacy application • It is relatively straightforward to take an application, generates a SOAP wrapper, then generate a “WSDL” document to cast the application as a Web service.

24. 웹서비스 시장 전망 • 75 percent of all corporations with more than $100 million in yearly revenue to use Web services by mid-2002. But perhaps because of its dubious experience with other industry trends, the research group is tempering expectations for the market's maturation. • Don't expect it to have mainstream impact until 2004 • It's a fact of nature that it takes a couple of years for technology to thrive. (Gartner Group)