1 / 12

Architecting a Service-Oriented Collaborative Web

Architecting a Service-Oriented Collaborative Web. 邱俊銘 M9590236. Proceedings of the Advanced International Conference on Telecommunications and International Conference on Internet and Web Applications and Services (AICT/ICIW 2006). Outline. Abstract Introduction

kisha
Download Presentation

Architecting a Service-Oriented Collaborative Web

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecting a Service-Oriented Collaborative Web 邱俊銘 M9590236 Proceedings of the Advanced International Conference on Telecommunications and International Conference on Internet and Web Applications and Services (AICT/ICIW 2006)

  2. Outline • Abstract • Introduction • Architecture for service-oriented collaboration • Implementation • Conclusions

  3. Abstract • Web Service movement has the potential to realize a universal collaboration environment. • creating their own services • combining services from others to solve their own problems • we propose a service-oriented architecturein which two important entities, called service containers and workbenches, are made explicit and protocols for them are defined.

  4. Introduction • Web Services is an ongoing movement • using open, standardized protocols. • targets primarily on system integration and business processes. • people may also collaborate by creating and sharing services. • user needs to solve a problem,he/she can look for suitable services over the Internet, customize and combine them.

  5. Architecture for service-oriented collaboration(1/4)

  6. Architecture for service-oriented collaboration(2/4) • containers can be long running at server side accepting requests, or transient at client side interacting with users. • A container may offer different levels of service management capabilities to different classes of users (e.g. normal users or administrators).

  7. Architecture for service-oriented collaboration(3/4)

  8. Architecture for service-oriented collaboration(4/4) • Templates are container and technology dependent, and can be quite complicated. Different containers can offer different. • workbenches can help users create and compose services by interacting with containers via standard protocols. • Moreover, workbenches may provide sophisticated collaboration mechanisms among GUI services, such as desktopwise drag and dropping.

  9. Implementation(1/3) • Channel types and Container : • Channel types : SOAP • Container : Axis Web service container

  10. Implementation(2/3) • Service instantiation and composition

  11. Implementation(3/3) • Service templates • Service templates are blueprints inside containers for clients to instance services.

  12. Conclusions • we have proposed an abstract service-oriented architecture with core entities including agents, services, workbenches, and containers, with an aim of enabling a global and open service-oriented collaboration environment. • Our model differentiates from current architectures in that client side and server side are unified, and GUI services are explicitly modeled.

More Related