sis 17(12): e3

Research Article

QoS-Based Architecture for Discovery and Selection of suitable Web Services Using Non-functional properties

Download977 downloads
  • @ARTICLE{10.4108/eai.18-1-2017.152102,
        author={Sarathkumar Rangarajan and Ravindra Krishna Chandar},
        title={QoS-Based Architecture for Discovery and Selection of suitable Web Services Using Non-functional properties},
        journal={EAI Endorsed Transactions on Scalable Information Systems},
        volume={4},
        number={12},
        publisher={EAI},
        journal_a={SIS},
        year={2017},
        month={1},
        keywords={Web service, SOA, Discovery \& selection, UDDI, QoS},
        doi={10.4108/eai.18-1-2017.152102}
    }
    
  • Sarathkumar Rangarajan
    Ravindra Krishna Chandar
    Year: 2017
    QoS-Based Architecture for Discovery and Selection of suitable Web Services Using Non-functional properties
    SIS
    EAI
    DOI: 10.4108/eai.18-1-2017.152102
Sarathkumar Rangarajan1,*, Ravindra Krishna Chandar2
  • 1: Centre for Applied Informatics, College of Engineering and Science, Victoria University, Melbourne
  • 2: Paavai Engineering College, India
*Contact email: sarathkumar.rangarajan@live.vu.edu.au

Abstract

Web Services are the most emerging distributed applications published in the public registries. Web service are can be discovered by both functional properties and non functional properties. Due to the rapid Web development, there are number of functionally similar Web Services published by different vendors. The functional property based web service discovery is cannot be done with accuracy. So client can find the best Web Services by taking the non-functional criteria such as Quality of Service (QoS). However, most of clients are not experienced enough to acquire the best selection of Web Service based on its described QoS properties. In this paper we are proposing a client request message structure and broker architecture to find the best Web Service. First the broker will get Web Service client's requirement message along with QoS criteria, and then it will retrieve the functionally similar web service. The broker will use an efficient mechanism to rank the Web Services based on the client’s message as well as the QoS properties which being confirmed by the broker architecture, If any tie situation happens in the ranking of the web service we will use the previous usage history of the web service to select the best web service which is matching with the client’s request message.