IBM Distinguished Engineer Member, IBM Academy Of
Managing Business Processes via Workflow Technology - LeymannTutorial at VLDB 2001(Rome, Italy, September 11-14, 2001)Managing Business ProcessesViaWorkflow TechnologyFrank LeymannIBM Distinguished EngineerMember, IBM Academy Of TechnologyIBM Software GroupSchoenaicherstr. 22071032 BoeblingenGermanyPhoneFaxCellulare-mail 49-7031-16 3998 49-7031-16 4890 49-172-731 5858ley1@de.ibm.comCopyright Notice:All of the material is copyrighted.With a few exceptions, the copyrightis help by IBM or Prentice Hall, Inc. IBMFrank Leymann297
Managing Business Processes via Workflow Technology - LeymannAgenda1. History2. Workflow Basics3. Some Plumbing4. WFMS Architecture5. Transactional Workflows6. Application Structures7. Web Services IBMFrank LeymannAgenda1. History2. Workflow Basics3. Some Plumbing4. WFMS Architecture5. Transactional Workflows6. Application Structures7. Web Services IBMFrank Leymann298
Managing Business Processes via Workflow Technology - LeymannWhy Do Care About Workflow Technology?Companies use computers to support their business,most frequentlyThe way to do business is prescribed via a business process,very oftenApplications support business processes and have to ensurecompliance with business processes Application Business Process Business FunctionsChanges in how to perform business must be reflected as soonas possible in applicationsA workflow is a business process in execution (an instance ofa process model) in a computing environment IBMFrank LeymannProcesses And WorkflowsReal WorldComputerProcess ModelWorkflow s identifiedProcessWorkflowNot all parts of a process are runin a computing environment some processes are not run on a computer at all! IBMFrank Leymann299
Managing Business Processes via Workflow Technology - Leymann"The Business You Are In DeterminesWhat Your Business Processes Are!"ManufacturingAssembly lines of cars, PCs, cloths,.InsuranceHandling of claims, policies,.FinanceStock brokering, settlement, clearing,.BankingThere is nothinglike a "typicalbusiness process"!!!Loans, savings, current accounts,.Database administrationBackup & recovery, reorganization, tuning,.Software developmentWaterfall model, spiral model,.Telecommunications, administration, government, datawarehousing. IBMFrank LeymannPeople Workflow Evolution:1st GenerationElectronic document and folder routing (late 80s)Document image, folder,.Routing through enterprise's organizational structureUser associated electronic basket is keyContainer for documents a certain user has to work on to contribute to a casePotential flow of documents prescribed in advanceRouting conditions in terms of document content or document propertiesActual routing based on actual content or properties of subject documentIn "paper factories" (administration, insurance, banking,.) workmainly equates to processing documents, thus the termworkflowhas been used for routing documents between people IBMFrank Leymann300
Managing Business Processes via Workflow Technology - LeymannPeople Workflow Evolution:2nd GenerationFunctions performed by users in 1st generation WFMS aremainly retrieval, browsing, editing, archiving,.But cases represented by documents were recognized to beonly part of larger business processesNot only performance of document management functions required butalso usage of other functions provided by application systems supportingthe operation of an enterpriseWFMS extensions needed to invoke any kind of executableIn-/Out-Basket grew towards worklistsLaunch-pad for executablesWorkitem managementPrioritization, duration management, life-cycle,. IBMFrank LeymannPeople Workflow Evolution:2nd Generation (cont.)Launching executables requires parameter passingThus, data flow features complemented available control flowsIn turn, control flows can now be expressed in terms of thesenew parameters ("business rules")Data flow is used for integrating applications with longtemporal delays between their initiationsParameters managed by data flow must be persistentData flow must be allowed to be different from control flowData produced by application A might be used by application B to be startedafter a couple of intermediate applications run IBMFrank Leymann301
Managing Business Processes via Workflow Technology - LeymannPeople Workflow Evolution:2nd Generation (cont.)Being able to support large spectrum of business processes incomputing environments made WFMS of strong interest forBusiness Process Reengineering (BPR) projects - early 90sGoal of BPR is to speedup business processes and reduce theircosts. Resulting requirements:Parallelism in workflows (- speedup)Deadline processing (- speedup)Monitor actual workflow status (- speedup)Auditing of significant events, i.e. processing history (- cost reduction)Maintain execution history for analysis (- cost reduction)Process activities without human intervention (- speedup cost reduction)So-called automatic activitiesConsequence: (parts of) business processes can be automated ("macro-scripts") IBMFrank LeymannPeople Workflow Evolution:3rd GenerationWorkflow-based applications become state-of-the-art (mid 90s)Strict separation of business process logic and business functionsBusiness processes implemented via workflow systemBusiness functions implemented "traditionally" (TP-monitor, ORB,.)Enterprises become dependent on WFMSSimilar to TP-Monitors and DBMS beforeThe term production workflow has been coined to indicate that WFMS isdriving operational aspects of an enterpriseConsequences:WFMS had to provide quality of services known before from "productionsystems" like DBMS and TPMHigh/continuous availabilityScalabilityRobustness IBMFrank Leymann302
Managing Business Processes via Workflow Technology - LeymannPeople Workflow Evolution:Latest MovesApplication integration is of fundamental importanceIntegrate diversity of application functionslegacy applications, newly written applications (e.g. component based),.new invocation paradigms (e.g. message queuing, pubsub)workflows as granules to be integratedautomatic workflowsOrganizational integration becomes more and more importantWorkflow expand across business units of enterprise ("intra-enterprise")Workflows across enterprises become key for B2B ("inter-enterprise")Creation and enactment of workflows in virtual enterprisesStimulated by mergers and acquisitions, outsourcing, supply chains, e-marekt places,.New technologies like Web Services, UDDI, SOAP,. stimulate thisWorkflows understood as business oriented "logical units of work"Advanced transaction management functions requiredForward recovery of workflows as well as workflow-based applicationsBackward recovery (global transactions and compensation-based recovery) IBMFrank LeymannEncapsulated WorkflowsCompany BoundaryCompany's personnel "translate" requests/responses with theoutside into actions performed within workflowsInquiries about status usually via phone callsCall center agents receive requested informationLimited service to customers & suppliers (e.g. restricted service hours,.) IBMFrank Leymann303
Managing Business Processes via Workflow Technology - LeymannOpening Up WorkflowsserBrow"Web-Up"(B2C)Internal Workflow"Business-To-Business"(B2B)"End-To-End" (E2E)Customers invoke company's applications to perform certain steps of the busines processE.g. place on order, inquire status,.Company's applications must get a browser-based front-end for that purpose ("web-up")Workflow activities may directly communicate with the outsideSend e-mail, faxes, messages,.Workflow activities may trigger actions in another companySimple invokation of program or start of another workflow ("subprocess" from invokers point-of-view)Such "business-to-business" scenarios are the base for realizing sophisticated "supply chains" IBMFrank LeymannTransactional Workflow EvolutionSuccess of TP Monitors and concept of (classical) transactionshave been overwhelmingHidden assumption behind classical transactions:Short duration (fractions of a second to a few seconds)Technical underpinnings based on this assumption2-phase-locking, log based recovery,.Early 80s started to extend transaction technology towardslonger durationsTechnical underpinnings have to be adoptedMost famous "transaction models"Nested transactions (closed & open)SagasMultilevel transactions IBMFrank Leymann304
Managing Business Processes via Workflow Technology - LeymannTransactional Workflow Evolution:Nested TransactionsStructure transaction into a tree of subtransactionsAllow intra-transaction parallelism to speedup processing:siblings may run concurrentlyOverall nested transaction has ACID propertiesDurability of subtransactions are given up (ACI remain)RootOverall nested transaction isolated from othernested transactions ("closed")ResultPossible speedup of a single closed nested transactionModerate throughput increase of environmentSiblingsChildParentLeaf IBMFrank LeymannTransactional Workflow Evolution:Open Nested TransactionsOpen nested transactions give up isolation and to acertain degree atomicitySubtransactions commit their changes to the outside assoon as they commitConsequence:Recovery via restoring before-images does not work anymoreAlready performed subtransactions of an aborting rootmust be undone by running application specific logic("compensation action") IBMFrank Leymann305
Managing Business Processes via Workflow Technology - LeymannTransactional Workflow Evolution:SagasOpen nested transactions assumed that compensationactions are scheduled manuallySagas require to specify compensation actions in advance andrun them automatically on abortDefinition:A Saga is a sequence [(T1,C1),., (Tn,Cn)] having the following properties:1. T1,.,Tn and C1,.,Cn are two sets of transactions, such that Ci isthe compensation function for Ti,2. [(T1,C1),., (Tn,Cn)] is executed as one of the following sequences:i.[T1,.,Tn], if all Ti committed, orii. [T1,.,Ti, Ci-1,., C1] if Ti aborts and T1,.,Ti-1 committed before. IBMFrank LeymannTransactional Workflow Evolution:StructuresStructures of transactions have been extended fromsequences and trees to directed acyclic graphsDependencies between transactions are describedBackward recovery based on ACID semantics as well ascompensation has been folded inE.g. "ConTracts"Late 80s, early 90s:The term "transactional workflow" has been coined forprescribing control flow dependencies between transactionsand their joint backward recovery IBMFrank Leymann306
Managing Business Processes via Workflow Technology - LeymannTransactional Features of Production Workflows:Merging People Workflow & Transactional WorkflowProduction workflow have the following characteristics:Many executables invoked areclassical transactionsrun automatic (i.e. launched as soon as detected to be performedrun unattended (i.e. no interactions with human beings)Thus, today's workflow systems impose directed graphstructures on set of transactions as discussed for"transactional workflows"It is only natural that users now require "transactionalworkflow features" within production workflow systems IBMFrank LeymannTransactional Features of Production WF (cont.)Production workflows invoke a lot of non-transactional programstoo (i.e. programs that cannot be simply undone)Thus, supporting compensation based recovery in productionworkflow systems is only naturalEspecially, a "unit of work" must allow to includetransactional as well as non-transactional programslong running programsprograms that demand human interactionsAbility to involve people in recovery:Not focus oftransactionalworkflow areaIn exceptional situations people can be notifiedas part of recovery processingHuman beings might "repair" the exceptional situationallowing to continue processing IBMFrank Leymann307
Managing Business Processes via Workflow Technology - LeymannWorkflow-Based Application: StructureBusiness Process Models EXEDLLCMDPIFCICSIMSEJBMQBusiness Functions IBMFrank LeymannWorkflow-Based Application: ExecutionWFMS.workitem.Worklist IBMFrank Leymann308
Managing Business Processes via Workflow Technology - LeymannWF-Based Apps:The Role Of Business ProcessesVery important to understand: Product Processfrom an internal company point of view in many industriesE.g. finance (settlement, credit,.), insurance (policy, claim,.),.Consequence: Time to create/modify business processesequates time to market for new/modified productsThus: Competitiveness of company depends on this timeBusiness process represents rules of procedureOften optimized wrt time & costsThus: Process participants must precisely follow specificationsWorkflow-based applicationflexibility: Creation and modification of business functions independentfrom specification of business processesenforcement: Workitems scheduled exactly as defined by process model IBMFrank LeymannWF-Based Appls: Industry AcceptanceLarge companies adopted this paradigm in the early 90sBuilt their own workflow systems at that timeNo real production workflow system was availableBenefits: Time to market for new/modified productsStandard application vendors adopted this paradigm mid 90sMost vendors built their own workflow system because no systemdominated the marketBenefits: Customization and internationalizationStandardization started mid 90sWorkflow Management Coalition (WfMC) since 95The standard consortium for workflow standards since 99OMG's Workflow Management Facility Objectification of WfMC I/FsSince 2000: ebXML, BPMI.org, OMG process modeling,.Vendors role out production workflow systems since late 90sIBM MQSeries Workflow, HP ChangEngine, MS Orchesterator,. IBMFrank Leymann309
Managing Business Processes via Workflow Technology - LeymannWorkflow TechnicaldocumentationcreationClaims handlingLoan handlingAccountingBrand MgmtAd HocAdministrativeReview/approvalFYI routinglowlowTravel expense reportsPurchase approvalshigh IBMRepetitionhighFrank LeymannAgenda1. History2. Workflow Basics3. Some Plumbing4. WFMS Architecture5. Transactional Workflows6. Application Structures7. Web Services IBMFrank Leymann310
Managing Business Processes via Workflow Technology - LeymannWhat Are Workflows? IBMFrank LeymannWorkflows: N-Dimensional „Things“WhatWhoWith IBMFrank Leymann311
Managing Business Processes via Workflow Technology - Leymann„What Dimension“: Activity SpecificationWhatWhoWithAInput ContainerOutput Container IBMFrank Leymann„What Dimension“: Control 35A4BlockE4p45A5E4E5ooo IBMoooFrank Leymann312
Managing Business Processes via Workflow Technology - LeymannControl Flow A4BlockE4p45A5E4E5oooooo IBMFrank LeymannControl Flow ConstructsFork ActivityActivityCollectCreditInformationTransition ConditionJoin ConditionAcceptCreditAssessRiskRisk 'low'RequestApprovalRejectCreditExit ConditionControl ConnectorJoin Activity IBMFrank Leymann313
Managing Business Processes via Workflow Technology - Leymann„What Dimension“: Data FlowWhatWhoWithA1Output ContainerOutput ContainerA3Data MapsInput ContainerData ConnectorA2 IBMFrank LeymannData Flow SpecificationAInput ContainerOutput ContainerPContainer MapB IBMFrank Leymann314
Managing Business Processes via Workflow Technology - LeymannContainers And Their InstancesXNamePersonSalarystringfloat instantiate AddressCityXHobbies[]15Countrystring stringHobbystring(Frank, 4000, (Berlin, Germany), [jogging, reading])(Dieter, 5000, (Munich, Germany), [biking, cooking, wine]) IBMFrank LeymannData MapsA1Output ContainerOutput ContainerA3Data MapsInput ContainerData ConnectorA2 IBMFrank Leymann315
Managing Business Processes via Workflow Technology - LeymannData Flow ConstructsInput ContainerNameOutput ContainerContainer CreditRisk tRequestApprovalData Connector IBMFrank LeymannOther Approaches To Flow Modelling Graph-/PTN-based modeling .realized in a bunch of products.standardized by WfMC (see later)Many other possible approaches State-Transition DiagramsCalculus-based.realized on some products .standard proposals . IBMFrank Leymann316
Managing Business Processes via Workflow Technology - Leymann„Who“ Dimension: Organizational AspectsDepartBossntsmeDivision 1 Division 2Dept A1Area 21Lab ALab BDept A2Dept ion 3Area 22Agentsh i nesWhatWhoWith IBMFrank LeymannStaff ResolutionDepartntsmeDivision 1Dept A1Division 2Area 21Division 3Area 22Lab ALab BDept A2Dept gentshi ne s IBMFrank Leymann317
Managing Business Processes via Workflow Technology - LeymannStaff CreditRequestApprovalRejectCreditStaff query associates with each activity the resources that have the ability (skill, duty,power, knowledge,.) to perform the activity successfully."Resources" are people or computing devices collectively called agents or simply staff. IBMFrank Leymann„With“ Dimension: IT LinkageWhatWhoWithActivityInput ContainerOutput ContainerOutput ParmsInput ParmsProgram IBMFrank Leymann318
Managing Business Processes via Workflow Technology - LeymannFlows As Implementations Of ActivitiesP2AB P1kick offand forgetP3chained(special case)kick offA & waitP6returnP5 IBMFrank LeymannHow To Work With Workflows? IBMFrank Leymann319
Managing Business Processes via Workflow Technology - LeymannPutting Things TogetherWhatWorkitemWhoWith IBMFrank s( , )( , )( , )ProgramProgramProgramAlso subject to Notification Expiry Escalation . IBMFrank Leymann320
Managing Business Processes via Workflow Technology - LeymannWorklists. a launchpad for business functionsFiltered list of workitems per agentAutomatic prioritization of workAssociates tools to pieces of workAutomatic data provision.User gains focus onbusiness aspects of workinstead ofcomputer aspects IBMFrank LeymannWFMS: End-User ExperienceWorklist.Workitem.1ActivityOutput ContainerInput Container253Pgm4 IBMFrank Leymann321
Managing Business Processes via Workflow Technology - LeymannActivity And Workitem Lifecyclemanual startactivityRestart/ ForceRestart automatic startactivityautomatic andexit.cond. falsemanual exitForceRestartand eckInCheckOutexit cond. falseCheckinmanual exitimm.cleanup/keep finished kInexit cond.trueautomatic andexit.cond. trueForceFinishDelete/keep etedinstance suspend/resumeterm.onerrorTerminate/term.on rminate/term.on errorTerminate/term.on errorForceFinishSuspendedDelete/keep finishedexceededimm.cleanup/keep finished tomatic matic startprocess activitystart IBMFrank LeymannAutomatic Workflow, MicroflowsWhatWhoWith Regular processing of automatic workflows andmicroflows don‘t involve human beings Microflows run often „local“, are „method“ bodies etc IBMFrank Leymann322
Managing Business Processes via Workflow Technology - LeymannBusiness Process Reengineering IBMFrank LeymannWhat Is BPR?Business Reengineering The fundamental rethinking andradical redesign of business processesto achieve dramatic improvementsin critical, contemporary measures of performance,such as cost, quality, service, and speed.M.Hammer and J.Champy, Reengineering the corporation, HarperCollins Pub.Inc. IBMFrank Leymann323
Managing Business Processes via Workflow Technology - LeymannBPR OutputAt the heart of business (re-)engineering.Business rganizationStructures IBMFrank LeymannOptimizing Business ProcessesDynamic analysis.takes into account quantitative aspectsnumber of processes per time unit, probabilities that certain paths are taken,.produces quantitative aspectsresources consumed to perform certain activities, to carry out business process,.Simulation generates information about.human resources needed to execute business processimpact on hiring strategyskills needed to handle business processimpact on skill planningtime and cost for performing business processindicator for outsourcingUsed to compare and select from alternative models of a givenbusiness process the "optimal" oneoptimal in terms of metrics like cost, duration,. IBMFrank Leymann324
Managing Business Processes via Workflow Technology - LeymannPurpose Of SimulationVerify capability of organization to support expected workloadPerformed based on metrical information ("instrumentation")Instrumentation requires to specifyNumber of processes started per time intervall, i.e. distribution patterns ofstarts - for example:constant: same number for each time intervallexponential: smaller numbers more frequent than large numbersuniform: numbers random within lower and upper boundcustomer defined: 57 between 9AM and 11AM, 341 between 11AM and noon,.Probability of transition conditions (likelihood of different branches taken)Probability of activation-, join- and exit conditions (likelihood of repetitions)Average duration of activities (work time, idle time,.),i.e. their distribution patternsProcessing power of resources, availability (based on calendar, shifts,.) IBMFrank LeymannMonitoring And AuditingProcessStateBusiness modeling based on assumptionsabout cardinalities, duration, etc.Based on these assumption processcharacteristics are derived (costs,.)which trigger riggerAPIThus, incorrect assumptions result innon-optimal process modelsWorkflowSystemWFMS allows to access actual state(monitoring) as well as history (auditing)of each workflowAnalyzing audit trail ("vanilla" SQL, OLAP,mining) derives "real data" for optimizingprocess models (re-engineering)Monitoring (manually or automatically)individual processes or instances of thesame model allows to detect out-of-linesituations and to react accordingly(re-assignment of work,.)AuditTrail IBMFrank Leymann325
Managing Business Processes via Workflow Technology - LeymannMonitoring And AnalyzingOooh, this is just goingfine!!! Good that Ihave chose this serviceprovider!VWXYPOPQABZKCP2 DRLMP3NP4STFUE IBMP1 HFrank LeymannContinuous ReengineeringBusinessModelingWorkflowBuild TimeVisualWorkflowBuildingRun Time IBMProcessMonitoringFrank Leymann326
Managing Business Processes via Workflow Technology - LeymannAgenda1. History2. Workflow Basics3. Some Plumbing4. WFMS Architecture5. Transactional Workflows6. Application Structures7. Web Services IBMFrank LeymannMessagesMessageHeaderMessageMessage BodyRequestDataReply-to queue, message lifetime,.Request component may be omitted [or minor aspect](e.g. in information brokering)Data is often a significant amount of informatione.g. a complete business object(opposed to "simple parameters" in method invocations)Emphasize is reliable data/information exchangeas well as exactly once invocation IBMFrank Leymann327
Managing Business Processes via Workflow Technology - LeymannMessage QueuingMachine XPGM APut Q1Machine YPGM BPGM CGet Q3Put Q2Get Q2MQIQ1Put Q3Put Q3MQIQ2Q3 IBMFrank LeymannHiding Plumbing ComplexityProgram P2Program P1PUT into Q1GET from Q7MQI queue directory queue directory .Q1 (MQM2, Q7).Q7 (local, Q7). target queue transmission queue MQM1MoverChannelMoverMQM2Network IBMFrank Leymann328
Managing Business Processes via Workflow Technology - LeymannAvailabilityMTTRMTBFSystem up and running,producing correct results versMTBFMTBF MTTRMTBFMTTR8GiveUP!Fault detection1 0 1 IBMDo It!Frank LeymannFault DetectionN?queue ocess2?Watchdoglock acquisitionProcesspulseProcessNProcess1 IBMProcess2ProcessNWatchdog detectsfailed processRecreate failed processesimmediately for HAFrank Leymann329
Managing Business Processes via Workflow Technology - LeymannApplication Server Hot PoolingPoolInputQueueGETPUTClientServerWatchdogHot pool isgeneralizationof warm backups transaction Hot Pool IBMFrank LeymannMessage IntegrityGETPUTClienttransaction 1ServerDead-Letter Queuetransaction 2transaction 3PUT IBMGETClientFrank Leymann330
Managing Business Processes via Workflow Technology - LeymannAvailability Of Hot PoolsNkDowntimekH(1 H) N k2001003457253768331.6.Assume very bad hot application server:MTBF 24h, MTTR 6h - thus,availability 0.8.But with 8 members, hot pool of such membersfails about 1.5 min/year !!!9999.65059N02Hhot pool 1 - (1 Hmember )00iH(1 H) N i 00i 1150Ni4Hhot pool P 1 6Hi (1 H) N i38N8.Pi 66i ki kNi16N[min / year]P k N192Pk 05678Hot Pool Cardinality IBMFrank LeymannHot Pool Take OverHot pool provides connection handling at client side:Automatic switching to available hot pool when current hot pool failsAlternative: Messaging system switchesClientMessaging SystemHot Pool NHot Pool 1 IBMFrank Leymann331
Managing Business Processes via Workflow Technology - LeymannClustering Hot PoolsHotPoolServer MachineHotPoolApplicationServerServer usterServer MachineApplication ClientApplication IBMFrank LeymannLoad Balancing Via Cluster QueuesPhysical QueueHotPoolPhysical QueueServer MachineHotPoolApplicationServerServer usterServer MachinePhysical QueueLoadBalancingLogical QueueApplication ClientApplication IBMFrank Leymann332
Managing Business Processes via Workflow Technology - 08.9010821521110802.9670273840411This is Mathonly!!! But COTScluster get a lot ofattention !9080.1097393698Same formulas as before apply!Assume very bad environment(i.e. HW, OS, DB and MOM):MTBF 24h, MTTR 12h- thus, availability 0.6!But with 12 server machines,application cluster with such abad environment isonly about 1min/yearunavailable!Cluster Downtime [min/y]Availability Of Application Clusters111208910Cluster Cardinality IBMFrank LeymannSummary: HA In Application ClustersServers are statelessServers use transactions to process client callsC/S communication is based on recoverable queuesEnsured message integrityServer hot poolingAutomatic recreation of hot pool membersTake-over between cluster machines IBMPlus plattformspecifics:(HACMP, ARM,Paralles Sysplex,.)Frank Leymann333
Managing Business Processes via Workflow Technology - LeymannSummary: Scale In Application ClustersHot pool allows scaling on each machine(increase cardinality of hot pool until CPU bound is reached)Application Cluster allows scaling via hot plug-in of machines(attach additional machines hosting server [hot pool]until DBMS server becomes bound [CPU, I/O])Domain (see below) allows scaling via attaching system groups(for organizational reasons or DBMS bounds)Using messaging as software bus allows scaling bydistributing app components on different machines(dedication of CPUs for particular logical tasks)Plus plattform specifics:(WLM, Enclaves,.) IBMFrank LeymannAgenda1. History2. Workflow Basics3. Some Plumbing4. WFMS Architecture5. Transactional Workflows6. Application Structures7. Web Services IBMFrank Leymann334
Managing Business Processes via Workflow Technology - LeymannThe WfMC Reference ModelBusiness Process ModelWFMS interoperabilityWorkflow Enactment ServiceWorkflowEnactmentServiceWFMS ApplicationPlugable activity implementationsInvokedApplication IBMFrank LeymannRelation Of BPR Tools And delingServerWorkflowSystemRuntimeInformation about process modelcollected in BPR tool often notsufficient for execution in WFMS(but sometimes it is!)Refinement via WFMS buildtimeFuzzy boundary between BPR andworkflow specification (similar toworkflow specification ystemInterchangeFile IBMExchange of data between BPR tooland WFMS looses information:Metamodels typically differentFrank Leymann335
Managing Business Processes via Workflow Technology - LeymannThree-Tier-ArchitectureMQ Workflow ClientMQ Workflow ServerMQ WorkflowServer HotpoolDBMS ClientDBMS ServerStored ProcedureProcess Control Data IBMFrank LeymannSystem rogramExecutionServerRun TimeClientAll systems of aparticular systemgroup share thesame databaseProgramExecutionServerRun TimeClientBuildTimeClient IBMFrank Leymann336
Managing Business Processes via Workflow Technology - LeymannMultiple System GroupsDatabaseServerDatabaseServerSystemSystemRun TimeClientSystemSystemRun TimeClientSystemGroupRun un TimeClientRun TimeClientBuildTimeClient IBMFrank LeymannDistributed ystemSystemRun TimeClientRun TimeClientSystemGroupSystemGroupRun TimeClient IBMFrank Leymann337
Managing Business Processes via Workflow Technology - LeymannInvoking Activity kationPEA-InfoExtractionStateDataMappingPgmData FormatLogon,. IBMFrank Leymann
Tutorial at VLDB 2001 (Rome, Italy, September 11-14, 2001) IBM Frank Leymann . , the copyright is help by IBM or Prentice Hall, Inc. Managing Business Processes via Workflow Technology - Leymann 297 IBM Frank Leymann 1. History 2. Workflow Basics 3. Some Plumbing 4. WFMS Architecture 5. Transactional
Chief Engineer Bhopal Zone, Bhopal Chief Engineer, Leh Chief Engineer (AF) Udhampur Chief Engineer Chennai Zone Chief Engineer (AF) Banglore, Chief Engineer (Navy) Visakhapatnam Chief Engineer A & N Zone, Port Blair Chief Engineer Chandigarh Zone Chief Engineer Bareilly Zone, Chief Engineer Pathankot Zone CWE Bhopal, PIN-900 236, c/o 56 APO
The Impact of and Journey to Experience Management, Powered by Qualtrics Michael Ryan, IBM Distinguished Engineer, IBM Jose R. Paredes Hernandez, IBM Global SAP Retail Leader, IBM Session ID 94223. About the Speakers Michael Ryan IBM Distinguished Engineer, IBM
Modi ed IBM IBM Informix Client SDK 4.10 03/2019 Modi ed IBM KVM for IBM z Systems 1.1 03/2019 Modi ed IBM IBM Tivoli Application Dependency Discovery Manager 7.3 03/2019 New added IBM IBM Workspace Analyzer for Banking 6.0 03/2019 New added IBM IBM StoredIQ Suite 7.6 03/2019 New added IBM IBM Rational Performance Test Server 9.5 03/2019 New .
IBM 360 IBM 370IBM 3033 IBM ES9000 Fujitsu VP2000 IBM 3090S NTT Fujitsu M-780 IBM 3090 CDC Cyber 205 IBM 4381 IBM 3081 Fujitsu M380 IBM RY5 IBM GP IBM RY6 Apache Pulsar Merced IBM RY7
Product Analysis for IBM Lotus Domino, IBM Lotus Notes, IBM Lotus iNotes, IBM Lotus Foundations, IBM Lotus Quickr, IBM Lotus Sametime, IBM Lotus Connections, and IBM LotusLive. This report is intended for Organizations, Vendors, and Investors who need to make informed decisions about the Email and Collaboration market. Figure 1: Worldwide IBM .
IBM Developer Kit per Java IBM Developer Kit per Java è ottimizzato per l'utilizzo nell'ambiente IBM i. Esso utilizza la compatibilità della programmazione Java e delle interfacce utente consentendo così di sviluppare applicazioni IBM i. IBM Developer Kit per Java consente di creare ed eseguire programmi Java sul server IBM i. IBM
IBM Spectrum Protect Snapshot (formerly IBM Tivoli Storage FlashCopy Manager) For more details about IBM Spectrum Copy Data Management, refer to IT Modernization . A9000R snapshots, see IBM Hyper-Scale Manager for IBM Spectrum Accelerate Family: IBM XIV, IBM FlashSystem A9000 and A9000R, and IBM Spectrum Accelerate, SG24-8376.
2.3 Baseline Financial Inclusion Data from Exuma In the Summer of 2019, the Central Bank also conducted a targeted baseline survey on financial inclusion and access for Exuma, alongside new data for the rest of The Bahamas, which provides a context for consumer education and awareness and tracking financial inclusion measures as
