A Managerial Community of Web Services
Nowadays, Web services are considered as new and attracting distributed approach of application/services integration over the Internet. As the number of Web Services is exponentially growing and expected to do so for the next decade, the need for categorizing and/or classifying Web Services is very crucial for their success and the success of the underlying SOA. Categorization aims at systematizing Web Services according to their functionalities and their Quality of Service attributes. Communities of Web Services have been used to gather Web Services based on their functionalities. In fact, Web Services in a community usually offer similar and/or complementary services. In this paper, we augment Web Services communities’ classification by adding a new support layer for Quality of Service classification. This is done through Quality of Services specification, monitoring, and certification of different Web Services. A Web Service might be admitted to a community thanks to its high Quality of Service or might be ejected from a community due to its low Quality of Service. We propose a managerial community of Web Services that is able to monitor and certify Quality of Web Services in other communities. This managerial community offers services to other communities, Web Services providers, and Web Services clients by monitoring and certifying Web Services. The focus of this paper is the use of the managerial community to select Web Services. Web Design Company Arudhra Innovations
The phenomenal growth of Internet technologies, largely impacted by the eXtensible Markup Language (XML) and its related technologies is extending the traditional role (client-to-business) of the World Wide Web to a better support of Business-to-Business interactions. The future perspective of the Internet is being driven by a new concept commonly known as Web Services technologies [1]. A Web Service can be defined as an application that exposes its functionality through an interface description and makes it available for use by other programs. Web Services allow computers and devices to automatically interact with each other using the Internet to exchange and gather data. Moreover, on one hand, a composite Web Service can further be created by aggregating a set of Web Services to produce a more complex Web Service with a wide range of functionalities. On the other hand, a set of Web Services can form and operate inside a community. In the Revised Webster dictionary, a community is defined as “a body of people having common rights, privileges, or interests, or living in the same place under the same laws and regulations. On a similar path, a community of Web Services can be composed by Web Services offering the same functionalities or sharing similar concerns. Even with a huge number of related works on Web Services and somehow a reasonable amount on communities of Web Services (e.g. [2], [3], [4]), there is a lack of mechanisms and approaches to establish inter-community and intra-community rules and to enforce them. The aim of this paper is, first, to define the rights of a community and participating Web Services, their duties toward peers and clients, and it proposes a novel certification and monitoring approach to enforce all of these to protect the community, its reputation, its interest, and those of each individual Web Services. Although other aspects are discussed, the focus in this paper is on Web Services Quality of Service (QoWS) mainly in selecting Web Services. Defining and enforcing terms and regulations of/within communities of Web Services raise a set of questions including: •How to represent a rule? •How to make sure a participating Web Service respects rules of the community? •When a Web Service might be authorized/invited to join a community? •When a Web Service must be ejected from a community? •How members of communities should distribute the load to fairly share benefits and to guarantee a certain QoWS How to define interactions with other communities? •When to interact with other communities? •As a member of a community, how to find and select a community to get services from whenever needed? Although this paper does not answer all of these questions, we propose a managerial community of Web Services for management of communities of Web Services. This managerial community is composed by Web Services instrumented with adequate functionalities and services to assess the QoWS of other Web Services. Such a Web Service is called Managerial Web Service (MWS). Assessment includes test and certification of a Web Service as a partial-requirement to join a community. Moreover, once Web Services are part of a community, the managerial community can monitor, periodically or on request, their behavior and interactions on the fly to detect any potential violation to the terms of their community, which might result in ejection from the community. Moreover, a participating Web Service can make use of the managerial community to show how much it is useful for the community and get some business credit or consideration. Finally, clients of Web Services can use the managerial community to select a community that suits their needs. In fact, many communities are likely to be competing by offering similar services with different conditions. The managerial community can advise a client which community to do business with according to its requirements and the status of the selected community (as known by the managerial community). The remaining sections of this paper are organized as follows: next section discusses related works. Section III presents our managerial community and terms and rules to be respected while operating within a community, while section IV discusses the list of services a member of the managerial communities should support. A proof of concept summarizing our experience in using the managerial community for selection of Web Services is presented. We conclude by conclusion and future work in section VI.
In general, management of Web Services as well as their QoWS (specification, publication, and discovery) are becoming more and more important as the number of similar, though competing, Web Services available in the Internet proliferates and the need for communities and composition of Web Services increases. Management of QoWS, as an integral part of Web Service management, will play an important role for the success of this paradigm. On one hand, providers of Web Services will have to specify and guarantee QoWS to remain competitive and achieve the highest possible returns on investment from their businesses. On the other hand, clients will have the possibility to look for appropriate Web Services according to their QoWS preferences (e.g., highly available, respond to client’s requests in reasonable time, etc.). As discussed before, works on communities of Web Services are mostly on establishing and building communities rather than managing communities and enforcing appropriate rules. However, there are some works on management of WebServices that are relevant to this topic. Hereafter is a short list of some works of interest to this paper. Managing QoWS of Web services as component of Web Service management has been addressed by several research initiatives. In [5] the work introduces sPAC (Web Services Performance Analysis Centre) and shows how customers can verify timeliness of their Web Services semi automatically from the description of workflow of Web Services to reports analysis and estimation results. In [6], the paper identifies a set of QoWS metrics in the context of Web Services workflows, and proposes a unified probabilistic model for describing QoWS values of a broader spectrum of atomic and composite Web services. In [7], the paper proposes a QoWS-aware binding approach based on Genetic Algorithms. The approach includes a feature for early run-time re-binding whenever the actual QoWS deviates from initial estimates, or when a service is not available. The approach has been implemented in a framework and empirically assessed through two different service compositions.https://arudhrainnovations.com/
Nowadays, Web services are considered as new and attracting distributed approach of application/services integration over the Internet. As the number of Web Services is exponentially growing and expected to do so for the next decade, the need for categorizing and/or classifying Web Services is very crucial for their success and the success of the underlying SOA. Categorization aims at systematizing Web Services according to their functionalities and their Quality of Service attributes. Communities of Web Services have been used to gather Web Services based on their functionalities. In fact, Web Services in a community usually offer similar and/or complementary services. In this paper, we augment Web Services communities’ classification by adding a new support layer for Quality of Service classification. This is done through Quality of Services specification, monitoring, and certification of different Web Services. A Web Service might be admitted to a community thanks to its high Quality of Service or might be ejected from a community due to its low Quality of Service. We propose a managerial community of Web Services that is able to monitor and certify Quality of Web Services in other communities. This managerial community offers services to other communities, Web Services providers, and Web Services clients by monitoring and certifying Web Services. The focus of this paper is the use of the managerial community to select Web Services. Web Design Company Arudhra Innovations
The phenomenal growth of Internet technologies, largely impacted by the eXtensible Markup Language (XML) and its related technologies is extending the traditional role (client-to-business) of the World Wide Web to a better support of Business-to-Business interactions. The future perspective of the Internet is being driven by a new concept commonly known as Web Services technologies [1]. A Web Service can be defined as an application that exposes its functionality through an interface description and makes it available for use by other programs. Web Services allow computers and devices to automatically interact with each other using the Internet to exchange and gather data. Moreover, on one hand, a composite Web Service can further be created by aggregating a set of Web Services to produce a more complex Web Service with a wide range of functionalities. On the other hand, a set of Web Services can form and operate inside a community. In the Revised Webster dictionary, a community is defined as “a body of people having common rights, privileges, or interests, or living in the same place under the same laws and regulations. On a similar path, a community of Web Services can be composed by Web Services offering the same functionalities or sharing similar concerns. Even with a huge number of related works on Web Services and somehow a reasonable amount on communities of Web Services (e.g. [2], [3], [4]), there is a lack of mechanisms and approaches to establish inter-community and intra-community rules and to enforce them. The aim of this paper is, first, to define the rights of a community and participating Web Services, their duties toward peers and clients, and it proposes a novel certification and monitoring approach to enforce all of these to protect the community, its reputation, its interest, and those of each individual Web Services. Although other aspects are discussed, the focus in this paper is on Web Services Quality of Service (QoWS) mainly in selecting Web Services. Defining and enforcing terms and regulations of/within communities of Web Services raise a set of questions including: •How to represent a rule? •How to make sure a participating Web Service respects rules of the community? •When a Web Service might be authorized/invited to join a community? •When a Web Service must be ejected from a community? •How members of communities should distribute the load to fairly share benefits and to guarantee a certain QoWS How to define interactions with other communities? •When to interact with other communities? •As a member of a community, how to find and select a community to get services from whenever needed? Although this paper does not answer all of these questions, we propose a managerial community of Web Services for management of communities of Web Services. This managerial community is composed by Web Services instrumented with adequate functionalities and services to assess the QoWS of other Web Services. Such a Web Service is called Managerial Web Service (MWS). Assessment includes test and certification of a Web Service as a partial-requirement to join a community. Moreover, once Web Services are part of a community, the managerial community can monitor, periodically or on request, their behavior and interactions on the fly to detect any potential violation to the terms of their community, which might result in ejection from the community. Moreover, a participating Web Service can make use of the managerial community to show how much it is useful for the community and get some business credit or consideration. Finally, clients of Web Services can use the managerial community to select a community that suits their needs. In fact, many communities are likely to be competing by offering similar services with different conditions. The managerial community can advise a client which community to do business with according to its requirements and the status of the selected community (as known by the managerial community). The remaining sections of this paper are organized as follows: next section discusses related works. Section III presents our managerial community and terms and rules to be respected while operating within a community, while section IV discusses the list of services a member of the managerial communities should support. A proof of concept summarizing our experience in using the managerial community for selection of Web Services is presented. We conclude by conclusion and future work in section VI.
Comments
Post a Comment