Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Agila Wiki" for change notification.
The following page has been changed by MatthieuRiou:
http://wiki.apache.org/agila/FrontPage
------------------------------------------------------------------------------
#format wiki
#language en
#pragma section-numbers off
- = WikiName Wiki =
+ = Welcome to Apache Agila Wiki =
- What is this wiki about?
+ Agila is centered around Business Process Management, Workflow and Web Service Orchestration.
It's composed of two specialized modules: Agila BPM and Agila BPEL.
- Interesting starting points:
- * RecentChanges: see where people are currently working
- * WikiSandBox: feel free to change this page and experiment with editing
- * FindPage: search or browse the database in various ways
- * SyntaxReference: quick access to wiki syntax
- * SiteNavigation: get an overview over this site and what it contains
+ '''Agila BPM''' is basically handling tasks and users who have to complete these tasks.
It's a very flexible and lightweight workflow component.
+
+ '''Agila BPEL''' is a BPEL-compliant Web Services Orchestration solution. Here is a short
description of what BPEL is good and bad for (from http://wiki.java.net/bin/view/Main/WhatIsBPEL
)
+
+ * BPEL is not workflow: there are no explicit abstractions for people, roles, work items,
or inboxes in BPEL (among other things).
+ * BPEL is also not BPM: no specified data model for measurement, reporting, or management.
+ * BPEL is not integration: there is no explicit support for transformation, semantic interpolation,
or specific protocols.
+ * BPEL is not all-encompassing: there are some patterns that are difficult to model with
BPEL.
+ * BPEL (i.e., an implementation) abstracts the common, non-process-level concerns of business
process execution.
+ * As a service-tier composition language, BPEL is a key ingredient in a service-oriented
architecture.
+ * BPEL provides a deployment-level interface for higher-level tools (e.g., modeling).
+ * "Low-hanging" innovation does not create sustainable competitive advantage.
+ * Complexity will remain an unavoidable part of the enterprise technology landscape. Managing
and minimizing that complexity will create leaders.
+ * Defining the organizational processes around BPEL, i.e., who uses BPEL and how, is of
paramount importance to the role and success of service oriented architecture.
+
+ The available resources in this Wiki are:
- == How to use this site ==
-
- A Wiki is a collaborative site, anyone can contribute and share:
- * Edit any page by pressing '''[[GetText(Edit)]]''' at the top or the bottom of the page
- * Create a link to another page with joined capitalized words (like WikiSandBox) or with
{{{["quoted words in brackets"]}}}
- * Search for page titles or text within pages using the search box at the top of any page
- * See HelpForBeginners to get you going, HelpContents for all help pages.
-
- To learn more about what a WikiWikiWeb is, read about MoinMoin:WhyWikiWorks and the MoinMoin:WikiNature.
Also, consult the MoinMoin:WikiWikiWebFaq.
This wiki is powered by MoinMoin.
|