Dynamic Web Services Personalization

Abstract

International audienceIn order to fulfill current customers requirements, companies and services providers need to supply a large panel of their products and services. This situation has led recently to the Mass Customizing Paradigm, meaning that products and services should be designed in such a way that makes it possible to deliver and adapt different configurations. The increasing number of services available on the Web, together with the heterogeneity of Web audiences, are among the main reasons that motivate the adoption of this paradigm to Web services technology.In this paper we describe a solution that allows automatic customization of Web services: a supplier configuration, published in a services repository, is automatically translated into another configuration better suited for fulfilling customers' needs

An integrated personalization framework for SaaS-based cloud services

“…To provide a mechanism to satisfy the personalized service requirements automatically, Sam, Boucelma and Hacid [46] adapt a paradigm for web services which enables service providers to avoid the weighty task of building a configuration for each user. The role of this Automatic Configuration Component is to automatically transform services published in a service directory in order to generate suitable configurations to fulfil client's needs [46].…”

“…The Automatic Configuration Component consists of the defining service parameters from the service directory and confirming the constraint rules by comparing the requests and constraint requirements of the selected services in a Constraint Module [46]. To provide a mechanism to satisfy the personalized service requirements automatically, Sam, Boucelma and Hacid [46] adapt a paradigm for web services which enables service providers to avoid the weighty task of building a configuration for each user.…”

“…The S-context information stored in the Context Repository is invoked to set up the constraint. Service providers publish only one explicit configuration for a given service; the others are dynamically and automatically inferred from the service directory [46]. The structural module and constraint module work together to build each personalized configuration for specified services.…”

“…The automatic configuration component is made up of two modules: a structural module and a constraint module [46]. The structural module is defined by the service directory and recommended patterns.…”