separating execution and data management a key to
play

Separating Execution and Data Management: A key to - PowerPoint PPT Presentation

Separating Execution and Data Management: A key to Business-Process-as-a-Service (BPaaS) Yutian Sun Jianwen Su Jian Yang UC Santa Barbara Macquarie U Outline of the Talk The technical problem for supporting BPaaS


  1. Separating Execution and Data Management: A key to Business-Process-as-a-Service (BPaaS) Yutian Sun Jianwen Su Jian Yang UC Santa Barbara Macquarie U

  2. Outline of the Talk � The technical problem for supporting BPaaS � Self-guided artifacts � The SeGA Framework (support for BPaaS) � Conclusions BPM '14 2014/9/9 2

  3. Business Processes & Workflow Management � A BP is an assembly of tasks to accomplish an objective � Eg: Obtaining a Permit Certificate Application Delivery Review Fee Init rev Approval BP workflow Workflow Management (WfM) System � Each workflow model matches a BP model � Each workflow activity is a software program ( ) that interfaces one task in BP � WfM system manages executions, resources, documents, etc. BPM '14 2014/9/9 3

  4. Application Example: Property Management � A Housing Management Bureau (HMB ) manages titles , licenses , permits , … for a region � Each HMB runs its own workflow system for its business � 30 provinces in China, each province has 10-50 HMBs � Those hundreds HMB workflow systems are individually maintained—very costly! Service Provider HMB 1 � Can one workflow system Workflow HMB 2 System support multiple HMBs? . . . � Note: (1) BPs are similar but not identical (provincal/local policies); data sets are mostly disjoint (e.g., data for buildings) (2) BPs change often (e.g., low income housing added in 2013) BPM '14 2014/9/9 4

  5. Workflow Systems and Local Data � A workflow system typically maintains execution states , control flow related data , correlations , etc. in a local data store Workflow System Includes all Execution data required Local for control engine data store flow decisions, correlations, . . . … Task Task Task wrapper wrapper wrapper Enterprise database [van der Aalst-van Hee 2004] BPM '14 2014/9/9 5

  6. Workflow Mgmt as Services? Not Effective � With straight-forward approach, the service provider has to run one WfM system for each client HMB due to disparate local data for each HMB’s workflow instances Hangzhou HMB Service Provider Enterprise Data Store 1 WfM system 1 Local 1 Yiwu HMB WfM system 2 Local 2 Enterprise Data Store 2 . . . . . . � Arguments for keeping data at local sites: � Analytics with local enterprise data + WF control data � Heterogeneity of data across different local sites � HMB’s want to hold their own data BPM '14 2014/9/9 6

  7. Our Goal: Separate processing from data Hangzhou HMB Service Provider Ent DS 1 & Local 1 Virtual Yiwu HMB WfM System Ent. DS 2 & Local 2 . . . � Only one WfM system that maintains no data � Keep each HMB’s data separated � Independent decision where/how Hangzhou, Yiwu maintain their data � A key enabling idea: � For each WF step, ship relevant data to WfM System � How to know which data is relevant? � Use BP model with holistic notion of data + process BPM '14 2014/9/9 7

  8. Self-Guided Artifacts (sga) A self-guided artifact contains everything an engine needs � A traditional business artifact (model): ( Entity information model , Entity lifecycle model ) � A self-guided artifact: (BP specification, Entity , States, Dependencies, L ) A document with the specification of ID of the entity lifecycle modeling model language actual business current correlations data states resources BPM '14 2014/9/9 8

  9. The SeGA Framework � Key idea: a process wrapper to supply all data (i.e., self-guided artifact) when the engine needs to run 4. decompose sga and 3. send the sga to put them into the right places the mediator and send the incoming event 1. incoming event Barcelona SeGA SeGA Dispatcher Engine Mediator 2. fetch the self-guided artifact (sga) 5. engine performs 6. fetch all data and a step and SeGA assemble into an sga possibly sending Repository outgoing event 7. store sga back into the repository � Both Barcelona and EZ-Flow are integrated with SeGA BPM '14 2014/9/9 9

  10. Supporting BPaaS WfM System (Service Provider) 4. decompose sga and 3. send the sga to 1. incoming put them into the right places the mediator event and send the incoming event Barcelona SeGA SeGA Dispatcher Engine Mediator 2. fetch the sga 5. engine performs 6. fetch all data and a step and Hangzhou assemble into an sga SeGA possibly sending Repository HMB 7. store sga back outgoing event into the repository SeGA Dispatcher � WfM system maintains no local 2. fetch the sga data* YiWu � SeGA repository can be merged SeGA Repository HMB into enterprise db [Sun-Su-Wu-Yang ICDE 2014] * in current prototype some data stored in Server due to ID mgmt issue BPM '14 2014/9/9 10

  11. SeGA Prototype and Current State � A prototype developed that works with Barcelona and EZ-Flow � Two operational test examples: Hangzhou HMB’s (cooperative) BPs: � Early-sell permit approval (Barcelona via SeGA) � Maintenance space check (EZ-Flow via SeGA) � A new project funded by Ministry of Sci. & Tech (China), Zhejiang Province, and Hangzhou City (> 1.2m RMB): � To implement an operational prototype with a small number of HMBs BPM '14 2014/9/9 11

  12. Summary � Main difficulty of providing BPaaS lies in data management � Workflow systems need to have a holistic approach to managing all of its data � Self-guided artifact is one such approach � SeGA elevates existing systems to support: Independence of Data and Execution Management � With the principle, BPaaS is actually easy to support � Basis for moving workflow services to cloud while enabling local sites to maintain their data BPM '14 2014/9/9 12

  13. Some research challenges � Conceptual data modeling for BPs beneficial, but SeGA raises many technical questions to be addressed: � Inefficient to ship large sega instance due to large data sets � Identify subset of artifact data needed for a given WF step? � Parallelism/txn consistency – what if 2 WfM steps require overlapping sets of artifact instances? � Use locking, and also subsets of artifact data � Auto-ID issue: current BP systems typically use DBMS to perform ID mgmt � Current SeGA prototype: retains some data in WfM server � For general solution the virtual WfMS server needs to explicitly manage artifact IDs � Re-thinking WfMS arch. to include the above will enable robust support for the data independence principle BPM '14 2014/9/9 13

Recommend


More recommend