|
10th International IEEE EDOC Conference "The Enterprise
Computing Conference" (http://www4.comp.polyu.edu.hk/~edoc06/) |
|
2006 Middleware for Web Services (MWS 2006) WorkshopSponsored by the National ICT Australia (NICTA, http://www.nicta.com.au) Held on October 16, 2006 at the Room B of the Regal Kowloon Hotel in Hong Kong |
|||||||||||||||
|
|
Proceedings of all EDOC 2006 workshops in the IEEE CS Digital Libarary (includes MWS 2006 Proceedings, log in for full papers) | |||||||||||||||
Workshop Program09:00 Session 1
10:30 Coffee break 11:00 Session 2
12:30 Lunch 14:00 Session 3
15:30 Coffee break 16:00 Session 4
|
||||||||||||||||
About the WorkshopDuring the past several years, Web services technologies have become very prominent in both the research community and the industry. Web services are distributed computing application components implementing the service-oriented architecture (SOA). They rely on Extensible Markup Language (XML) interface description languages, such as the standardized Web Services Description Language (WSDL), and communication protocols, such as the standardized SOAP protocol (previously known as the Simple Object Access Protocol). In addition, Web services can use a number of other standardized and/or proprietary XML-based formats, such as the standardized Web Services Business Process Execution Language (WSBPEL) for describing business processes implemented as Web service compositions. Implementation-independence of Web services technologies allows different businesses to collaborate and achieve common business goals despite the fact that the collaborating Web services can be distributed over the Internet, run on different platforms, and implemented in different programming languages. Web services technologies are already embedded in various products and services of all major computing companies and used for diverse purposes. An important application area is e-business process integration in business-to-business (B2B) and/or enterprise application integration (EAI) scenarios. Additionally, Web service technologies became the basis for several other recent distributed computing technologies, such as Grid services and Semantic Web services. Reusable Web services technologies are implemented
in middleware, so appropriate middleware is a prerequisite for the growing
acceptance of these technologies. For example, implementation independence of
Web services is achieved using middleware, such as application servers and/or
SOAP engines (software that analyzes, processes, and generates SOAP
messages). In addition, middleware solutions have been proposed to provide,
monitor, and manage quality of service (QoS) aspects, such as response time,
throughput, availability, reliability, security, and privacy. Quality of
service is important for Web services for several reasons. For example,
run-time management (monitoring and control) of QoS for a Web service helps
to ensure correct operation, attain or surpass QoS levels expected by
consumers, discover and fix (or, better, predict and prevent) problems,
accommodate change, balance price/performance ratios, and maximize profits.
QoS negotiation between consumer and provider Web services can help in providing
QoS levels appropriate for particular consumers. Also, description and
publication of QoS in addition to functionality can help in selection between
provider Web services with the same (or similar) functionality. One of the
major challenges that Web services middleware faces is to provide appropriate
reusable software building blocks for QoS management. Consequently,
middleware for Web services is a very important research and development
topic for advanced enterprise distributed computing and e-business process
integration and management. The previous version of this workshop, MWS 2005, was held at the EDOC 2005 conference. It gathered industrial, academic, and government researchers and developers interested in Web services and/or middleware technologies. Through an interesting and diverse program, containing a keynote speech, presentations of selected peer-reviewed papers, and a panel discussion, the MWS 2005 workshop contributed to the exchange of knowledge and ideas, dissemination of results about completed and on-going research projects, as well as identification and analysis of remaining open research issues and possible approaches towards their solution. The workshop proceedings were published by the IEEE Computer Society. MWS 2005 was followed by a special International Journal of Business Process Integration and Management (IJBPIM) journal issue on middleware for web services, for which papers were invited both from MWS 2005 authors and through an open call for papers. After an additional rigorous double-blind review process, four best submissions were selected. Two of them were papers from the open call for papers, while two were significantly improved versions of MWS 2005 papers. The goal of this year’s workshop, MWS 2006, is to further contribute to the research and development in this exciting area, using the workshop model of MWS 2005. We have again composed an interesting and diverse program, containing a keynote speech, presentations of selected long and short (work-in-progress) peer-reviewed papers, a book review, and a discussion session. Research papers were selected after a thorough and competitive peer-review by workshop Program Committee members. In most cases, there were 4 reviewers per long paper and 3 reviewers per short paper. The MWS 2006 program and proceedings contain the best 5 full papers and 3 short papers. |
||||||||||||||||
Open Forum “Requirements and Challenges for Middleware Supporting Reliability of Web Service Composition”This discussion session will be an open forum about middleware support for composed Web services, with particular focus on the resulting reliability. The challenges in achieving reliable composition of Web services are paramount. From assuring correct transactional properties of composite business processes to the role of standards and from the inherent reliability of supporting middleware (open source or not) to the semantic correctness of match making. In fact, the mere definition of the term reliability is an open issue. While some general issues related to reliability were debated at the MWS 2005 panel “Quality of Service (QoS) Middleware for Web Services: Achieved Results and Challenges for the Future”, many additional specific questions have to be explored. This forum discussion may address a number of questions, including (but not limited to) the following questions: What are the main reliability requirements in Web service composition? For instance in: - transactional properties, - matching semantics, - middleware reliability. Can middleware contribute to fulfilling these reliability requirements? Can we prioritize the main requirements? Can we identify the most challenging issues in middleware support for reliable Web service composition? Are there unsolvable reliability questions? Which middleware support does already exist? What is the role of standards in creating reliable service composition, and which are most promising? - WS Transaction - WS Composite Application Framework - WS Reliable Messaging - WS Management Can we define a roadmap to develop solutions for reliable Web services? |
||||||||||||||||
Workshop Chairs
Workshop Program Committee |
||||||||||||||||
|
|
|||||||||||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
||||||||||||||||
|
|
Sponsored by the National ICT Australia (NICTA). Website designed by Franky Lam, updated by Vladimir Tosic. |
|||||||||||||||