Grid-based interoperability of workflow systemsMoustafa Ghanem, InforSense Ltd
Nabeel Azam Mike BonifaceInforSense Ltd IT Innovation
Background: SIMDAT Developing and applying Grid technology to support Distributed, Cross-organizational, product and process development www.simdat.org
Example Auto design workflows
Example Aero design workflows
SOA and Workflows: A programmers viewServicesServicesServices
Key challenge for workflow in SIMDATThere are 26 partners in SIMDAT
At least 3 workflow systems in use InforSense KDETaverna/FreefluoLMS OptimusOther approaches includeVarious hard-coded wf applicationsBPEL
Agreeing/Using a common workflow system (or language) is difficultMigration may require huge re-investmentsContinued debate on open source vs. proprietary
In general, virtual organizations are dynamicWhat happens when we add new partners?SIMDAT partners
Workflow Systems: Are they really similar?
Workflow systems quick comparisonSimilaritiesAll have drag-drop GUIsAll use XML-based languagesSimilar conceptual model
DifferencesDifferent language paradigms/semanticsPure Data Flow vs. Control FlowIterations (not available, implicit, explicit ?)Data types and operators supportedVarying degrees of abstractionNode granularityService call vs. abstract taskDifferent systems specialized to particular applicationsSpecialized viewersSpecialized helper nodes for data manipulation
Grid-based interoperability of workflow systems
Calling Grid Services vs Web Services
Example: Using of GRIA servicesGRIA uses a fully decentralized management approach, with minimal dependency between sites.
Each site offering GRIA services makes its own business decisions about which users to trust and on what terms, and is responsible for enforcing its own access policies and deciding which applications to support.
Sites can interact with each other, but this is driven by their common consumers, and those consumers are responsible for managing the resulting dependencies.
There are no global agreements to set up, and no virtual organizations need be established, though users can interact according to virtual organization models if they want.
Example: Pharma applicationFive basic Sub-workflow nodesAllocate ResourcesUpload InputsExecuteRetrieve ResultFinish Conversation
Grid-based workflows and interoperability
Run-time interoperability Workflow-based applications as servicesWorkflow enactment as services
Method 1: Workflow-based application as service
Example: Aero application
Method 2: Workflow enactment engine as service
Interoperability interaction patterns
Next Steps: Moving from abstract to heterogeneous executable workflows
User specifies high-level steps
Steps iteratively instantiated using services and workflow templates
Use service registries and workflow warehouses
Use existing run-time interoperability mechanisms
Heterogeneous workflow warehouseInforSense Workflow warehouse
Service RegistriesNEC Semantic Broker
Authoring advisor: high-level steps for application domains
Authoring assistant: map from abstract tasks to workflow fragments and services
Workflow warehousing and mining
SummaryUsing industrial strength workflow systems for cross-organization product design
Run-time interoperability mechanisms
Supporting the design of heterogeneous workflows