Building a Customizable Business-Process-as-a-Service Application with Current State-of-Practice

Gey, Fatih; Walraven, Stefan; Landuyt, Dimitri Van; Joosen, Wouter

doi:10.1007/978-3-642-39614-4_8

Cited by 10 publications

(13 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the other hand, multi-tenant applications are often limited in terms of customizability since one application should fit the needs of all customers. In [9], Gey et al focus on the customizability due to the different tenant-specific requirements. They argue that the workflow modelling language should offer support to describe these tenant-level variabilities explicitly.…”

Section: Related Workmentioning

confidence: 99%

jBPM4S: A Multi-tenant Extension of jBPM to Support BPaaS

Zhu

Guo

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. BPaaS, or Business Process as a Service, is an advanced model of SaaS in which the Business Process Management system is deployed as a hosted service and accessed over the Internet without the need for the user to deploy and maintain additional on-premise IT infrastructure. In this paper, we present an architectural design and implementation of a BPaaS system, called jBPM4S. jBPM4S is an extension of jBPM, and further provides process-related services to be invoked by multiple tenants on their demands over the Internet. It leverages Spring Framework to manage transactions of process instance execution and expose its universal process services that are unrelated to the specific business through the means of Web services. The case study based on jBPM4S demonstrates the effectiveness and efficiency of such service based process management facility.

show abstract

Section: Related Workmentioning

confidence: 99%

jBPM4S: A Multi-tenant Extension of jBPM to Support BPaaS

Zhu

Guo

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…In order to allow the implementation of multi-tenancy in different SCE implementations, we abstract away from the specifics of SCE solutions like Apache ODE 3 , WSO2 Business Process Server 4 , OW2 Orchestra 5 or the YAWL Workflow Engine 6 , and we compose logical components standing for specific SCE functionalities (e.g. navigation through the process model) in a unified architecture model.…”

Section: B Multi-tenant Scementioning

confidence: 99%

“…They do not however describe an architecture or realization approach how multi-tenancy can be supported. Looking specifically at the SaaS model, the work in [6] discusses how a BPMN-based business process execution engine can be made multi-tenant to allow for tenantbased configuration of the application-supporting processes. The discussion however focuses on the modeling aspect of processes and does not provide any architectural insights into how to implement a multi-tenant aware execution engine.…”

Section: As In the Original Esbmentioning

confidence: 99%

“…This sharing manifests both in terms of multiple tenants using the same engine in an isolated manner, but also as different combinations of tenants and/or tenant users sharing the same process model, potentially with different configuration options per tenant as discussed e.g. in [6]. Previous work [7] demonstrated that the concept of SCE as a Service is both feasible and efficient, however by delegating the problem of multi-tenant awareness on the level of the messaging middleware used.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

SCE^MT: A Multi-tenant Service Composition Engine

Hahn

Sáez

Andrikopoulos

et al. 2014

2014 IEEE 7th International Conference on Service-Oriented Computing and Applications

View full text Add to dashboard Cite

Abstract-The support of multi-tenancy is an essential requirement for leveraging the full capacity of Cloud computing. Multi-tenancy enables service providers to maximize the utilization of their infrastructure and to reduce the servicing costs per customer, thus indirectly benefiting also the customers. In addition, it allows both providers and consumers to reap the advantages of Cloud-based applications configurable for the needs of different tenants. Nowadays, new applications or services are typically compositions of multiple existing services. Service Composition Engines (SCEs) provide the required functionality to enable the definition and execution of such compositions. Multitenancy on the level of SCEs allows for both process model, as well as underlying infrastructure sharing. Towards the goal of enabling multi-tenancy of SCEs, in this paper, we investigate the requirements and define a general architecture for the realization of a multi-tenant SCE solution. This architecture is prototypically realized based on an open-source SCE implementation and integrated into an existing multi-tenant aware Enterprise Service Bus (ESB). The performance evaluation of our prototype shows promising results in terms of the degradation introduced due to processing and communication overhead.

show abstract

“…One example is a document processing service [4], [7], a B2B SaaS application that generates, distributes, signs, and archives different kinds of documents (e.g. paychecks, invoices) on behalf of tenant organizations.…”

Section: Introductionmentioning

confidence: 99%

Continuous Evolution of Multi-tenant SaaS Applications: A Customizable Dynamic Adaptation Approach

Gey

Landuyt

Joosen

et al. 2015

2015 IEEE/ACM 7th International Workshop on Principles of Engineering Service-Oriented and Cloud Systems

Self Cite

View full text Add to dashboard Cite

Applying application-level multi-tenancy in Software-as-a-Service (SaaS) offerings yields a number of compelling benefits: sharing a single instance of the application between large numbers of customer organizations increases cost efficiency and allows the SaaS provider to attain true economies-of-scale benefits. There is however a main downside to this: increased sharing of resources causes the SaaS application to be very difficult to modify after initial development and deployment without affecting service continuity: any change potentially affects the service levels promised to all enrolled tenant organizations and their end users.This rigidity is a key impediment as now the SaaS provider must evolve and maintain the SaaS offering at run time, on a gradual, per-tenant basis. This in turn causes a reality of multiple co-existing versions of individual components and as such introduces substantial management complexity.To address these challenges, this paper motivates and defines key requirements that allows per-tenant, SLA-aware and gradual upgrades in the context of multi-tenant SaaS applications. In addition, we define an approach that allows the involved stakeholders (tenants, SaaS operators, SaaS developers, etc.) to customize the dynamic enactment of upgrades, and provide a number of alternative software upgrade strategies that represent different service quality trade-offs.

show abstract

Building a Customizable Business-Process-as-a-Service Application with Current State-of-Practice

Cited by 10 publications

References 12 publications

jBPM4S: A Multi-tenant Extension of jBPM to Support BPaaS

jBPM4S: A Multi-tenant Extension of jBPM to Support BPaaS

SCE^MT: A Multi-tenant Service Composition Engine

Continuous Evolution of Multi-tenant SaaS Applications: A Customizable Dynamic Adaptation Approach

Contact Info

Product

Resources

About