Abstract
Authentication, authorization, billing and monitoring are all common service delivery functions that are generally required to be added on to core business services in order for them to be delivered online commercially. Extending core services with these service delivery functions requires considerable effort if implemented ground-up and can be subject to limitations if outsourced to a service broker or a conventional middleware platform. Because of the ubiquitous nature of these service delivery functions, we see them as reusable patterns for service delivery. In this paper we have introduce an approach to implementing and applying these patterns in business to consumer e-commerce. We name the approach Service Packaging. Through the approach, generic implementations (or service packages) of the various service delivery patterns can be incrementally applied to core services, thus enabling flexible and systematic service delivery. A core service, regardless of its business domain does not require any structural or behavioral modifications in order to conform to a specific service delivery requirement and hence can be used out of the box. We also present a prototype middleware platform for the design-time modeling and implementation of service packages as well as their runtime execution.
Highlights
With the maturity of web service tools, creating and exposing backend functionality as web services has become relatively easy
The packaged service composite can recursively act as a concrete service composite that can be further packaged with additional service packages
In this paper we have introduced the concept of a service package which is a reusable implementation of a service delivery pattern
Summary
With the maturity of web service tools, creating and exposing backend functionality as web services has become relatively easy. Step1- Identify a service delivery pattern A service delivery pattern describes a specific recurrent functional or non-functional business requirement (e.g. pre-paid charging, authentication, authorization, monitoring, etc.) that service providers need to add-on to their core functional services While these patterns are common in today’s e-commerce, the challenge is to generalize their implementation so that it can be reused in multiple applications across various domains. The packaged service composite that comes out of the instantiation step is a concrete service composite that includes the structure and behavior of both the core service composite and the domain-independent service package This composition is deployed and enacted in a runtime execution engine (the section provides more details of the execution engine). The packaged service composite can recursively act as a concrete service composite that can be further packaged with additional service packages
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
