(IJCSIS) International Journal of Computer Science and Information Security,Vol. 8, No. 5, August 2010
2. Related Work
With the widespread use of Web Services the QoS havebecame the significant factor in selecting a best serviceamong the providers and it constitutes the differentiatingpoint for a group of services. QoS generally refers tononfunctional properties of Web services such as price,performance, reliability, integrity, availability, accessibility,interoperability, security, etc. [1]. Certain traditionalapproaches [2] make use of QoS policies and a weighingsystem to judge through the attributes. This approach isapplicable only when there is a relatively small set of services and attributes. Since all the services cannot beweighed through a common attribute thereby limiting thisapproach to a smaller set of services. Also rule based modelproposed by Patel et.al [3] is too restrictive and provide acondensed set of alternatives for service execution. Menasce[4] in his research has highlighted the need for QoSdefinition, specification and evaluation in WS from theperspective of both service provider and service user. W3C[5] has summarized the key requirements of QoS for Webservices. Recently, several research works have dealt withthe definition of QoS languages for WS-based applications.Ludwig [6] in his work have discussed about the QoSlanguages and the service level agreements(SLA) that are tobe initiated between the service consumer and serviceproviders for proper operation of the system after satisfyingthe QoS requirements. Hewlett-Packard (HP) has proposed aWeb Services Management Language (WSML) andframework and IBM have developed a Web Service LevelAgreement (WSLA) language.In a SOA environment the QoS data of the serviceproviders continuously change during the lifetime of aservice. There is no mechanism that periodically updates theQoS data into the registries. Al-Masri et al.[7] have statedthat about 53% URL’s of the Universal BusinessRegistries(UBR) are invalid and they cannot be validatedwith a valid WSDL document. This means that the metadatainformation collected at the time of registration of a servicein the registry, has been modified and not yet been reportedto the registry for proper updation. Since the informationcontained in the UBR are not accurate, it utilized moreresources when performing the binding of web services andwasted a considerable time in trying to communicate witheither non functional or poorly functioning web services.The clients should know the revised QoS information tochoose the appropriate service accordingly.Various query based and monitoring basedmethods exist [8-10] for obtaining the QoS values of theservices. The former periodically queries the service andactively request for the QoS information whereas the laterutilizes a monitoring engine that runs on the serviceprovider side as a middleware or acts as a central proxy. Linet.al.[11] have formalized the service selection for a Webservice composition as a fuzzy constraint satisfactionproblem. Each QoS criteria has five fuzzy sets describing itsconstraint levels: Poorly Acceptable (PA), AlmostAcceptable (AA), Acceptable (A), Very Acceptable (VA),and Extremely Acceptable (EA). The overall QoSpreference of a user is then represented by a fuzzyexpression which is composed of a group of fuzzy setsconnected by the and logical operator. They have introducednecessary definitions for mapping a Web service dynamiccomposition to a fuzzy constraint satisfaction problem(FCSP) and finding its solution through NP-hard [12].Xiong et.al. [13] modeled QoS based service selection as afuzzy multiple criteria decision making problem (FMCDM).QoS criteria are evaluated by a set of linguistic expressionsL1 = {Very Poor (VP), Medium Poor (MP), Poor (P),Medium (M), Good (G), Medium Good (MG), Very Good(VG)}. Similarly, the weights of QoS criteria are expressedby a set of linguistic expression L2 = {Very Low (VL), Low(L), Medium (M), High (H), Very High (VH)}. Theselinguistic expressions are mapped to fuzzy set membershipfunctions to yield the results. Agarwal et.al [14] suggestedthat user preferences can be defined as a set of fuzzy If-Then rules. The If part contains membership functions of various QoS criteria of a Web service and the Then part isone of the membership functions of a special conceptrepresenting the rank of the Web service. In each rule, fuzzyconcepts like fast, medium, slow or cheap, medium,expensive are used to express imprecise values of QoSproperties and these fuzzy concepts are modeled asmembership functions.
3. Proposed Framework
In this paper we propose to create a reliablearchitectural framework that can manage faults and canadapt itself to provide a reliable service. This frameworkdecouples the clients from the service providers and takescare of the service execution after due consideration of allQOS issues. Presently the web service clients are typicallyhardwired with the service providers and does not adaptdynamically in case of service failures. Unavailability of aservice is handled only with a manual intervention duringfailures and fixing them accordingly. This involves servicestoppage which directly hinders the performance of thesystem. The proposed framework addresses this issue byacting as a layer in between the web service clients and theweb service providers and dynamically reconfigures itself torespond to the faults so that the business processes cancontinue in the event of service failures. By virtue of usingSOA and XML based web services, this framework ismultiplatform enabled along with multi protocol supportthat can bridge various interfaces, thereby removing thedifficulty of integrating mobile and wireless sensor networkclients with this framework. The clients submit theirrequests to the framework and during runtime the
227http://sites.google.com/site/ijcsis/ISSN 1947-5500