The purpose of this paper is to describe ideas for combining Web Services and workflow engines (here AristaFlow1), where they might fit and where they might provide the enterprise with advantages in terms of integration, dynamic processing and interoperability.
This paper also showcases guidelines for designing component descriptors using WSDL and other XML Standards and guidelines for developing flexible application accessing methods in AristaFlow. More understanding of how to use these techniques are explained by our sample scenarios on the basis of the Java™ Adventure Builder Reference application.
Table of Contents
I. INTRODUCTION
1. Standards & Technologies - Web Service
2. Standards & Technologies – Workflow Management System
II. ARISTAFLOW
1. About
2. AristaFlow Component Descriptor
2.1 AFD - Component
2.1.1 Component Types
2.1.2 Activities
2.1.3 Taxonomies
2.1.4 Workflow Elements
2.2 Defining the component
2.2.1 Example 1: Credit Card Service
2.2.1.1 An empty component definition
2.2.1.2 Adding an activity
2.2.1.3 Completing the credit card component
2.2.2 Example 2: Activity Supplier
2.2.3 Example 3: Weather Forecasts
III. ADVENTURE BUILDER
1. About
2. Overview of Adventure Builder
2.1 Architecture and Design
2.1 Communication Architecture
3. Advanced Workflow with AristaFlow
4. Sample Scenarios
4.1 Scenario 1: Choose Products
4.2 Scenario 2:Make Order
4.3 Scenario 3:Customer Support
5. Conclusion & Outlook
Objectives & Core Topics
The paper explores the synergy between Web Services and workflow engines, specifically using AristaFlow to enhance enterprise integration, dynamic process flexibility, and interoperability. It establishes design guidelines for component descriptors and demonstrates these concepts through the Java Adventure Builder reference application.
- Integration of Web Services within workflow management systems.
- Technical design and implementation of AristaFlow Component Descriptors (AFD).
- Adaptive process management and handling of ad-hoc changes.
- Practical application scenarios including credit card services and adventure package booking.
- Benefits of moving from static management to automated process engines.
Excerpt from the Book
2.1 AFD - Component
Let us introduce AristaFlow Component Descriptor with its root element component. The component element is the representative of the software component of the real world. It consists of component type specific data, activities, metadata, taxonomies and other optional elements. And it has attributes like id, name, version etc.
Summary of Chapters
I. INTRODUCTION: Covers the fundamental concepts of Web Services and the general challenges facing modern Workflow Management Systems.
II. ARISTAFLOW: Details the AristaFlow architecture, focusing on the component descriptor schema and practical examples for defining and integrating various software components.
III. ADVENTURE BUILDER: Applies the theoretical AristaFlow concepts to a complex, multi-partner enterprise scenario to demonstrate improvements in flexibility and usability.
Keywords
Web Services, AristaFlow, Workflow engine, Adventure Builder, Component Descriptor, AFD, Service Oriented Architecture, SOA, Process Management, Enterprise Application, Interoperability, XML, J2EE, Business Process, ADEPT
Frequently Asked Questions
What is the primary focus of this paper?
The paper examines how to integrate Web Services with workflow engines like AristaFlow to improve enterprise-level integration, dynamic process handling, and overall system interoperability.
What are the central thematic areas?
The work centers on workflow management systems, the AristaFlow Component Descriptor (AFD) schema, SOA-based architecture, and the practical application of these technologies in the travel industry.
What is the research goal?
The primary goal is to provide a conceptual framework and practical guidelines for designing flexible, reusable software components that can be dynamically managed within an adaptive workflow engine.
Which methodology is employed?
The author uses a descriptive and constructive approach, utilizing the Java Adventure Builder reference application to model and test the implementation of Web services within the AristaFlow environment.
What is covered in the main section?
The main section describes the AristaFlow Component Descriptor (AFD), how to define components using XML, and how to execute workflow scenarios involving multiple external partners and human activities.
How are the key terms defined?
Key terms are identified by the technologies used for service-oriented architecture (SOA), such as WSDL, XML, JNDI, and the specific AristaFlow process management framework.
How does AristaFlow handle ad-hoc changes?
AristaFlow allows for ad-hoc changes to process instances and process types during run-time, enabling efficient migration to new schema versions without requiring a full redesign or redeployment of the application.
Why is the "Component Descriptor" significant?
It provides a standardized schema (AFD) that enables the workflow engine to interpret disparate software components—whether they are Web Services, EJBs, or standard applications—in a unified way.
What benefit does this system provide for an enterprise?
It offers greater flexibility, reduced time-to-market for process changes, improved error handling through automated recovery mechanisms, and the ability to integrate diverse partner services seamlessly.
- Quote paper
- Ke Zhang (Author), 2006, Implementation of Webservices in AristaFlow, Munich, GRIN Verlag, https://www.grin.com/document/68973
