Friday Feb 13, 2009

Sun GlassFish WebSpace Server consumes SAW API

GlassFish Portfolio

Sun GlassFish WebSpace Server 10.0(henceforth referred as "WebSpace" was released as part of GlassFish Portfolio launch.

Traditionally, performing tasks on multiple portals is tedious and inefficient as enterprises adopt back-end business processes and must then continually manage them. Hence, demand has steadily mounted for the capability to perform tasks on just the portal itself instead of on multiple sites with a single-point solution; that is, a solution that not only handles the process interactions but also enables end users to seamlessly perform tasks as "hooks" in the process. Bear in mind that automation of business integrations requires human steps on portals, often accomplished through proprietary applications. By integrating human workflow into portals, you ensure that all the tasks, whether performed by humans or by software, occur in one place.

WebSpace consumes the SAW API to provide this functionality. The Simple API for Workflow(SAW) is intended to offer a generic workflow api to perform human workflow interaction with various workflow engines. SAW API is an API for performing task management(update(e.g. approve/reject), delete, reassign, escalate etc.) created in a human oriented workflow. The Workflow can be defined in various languages supported by the workflow engines. With SAW API, portlet developers can manage tasks created via various instances of workflow definitions defined in languages specific to Workflow engines.

Currently the SAW API has implementations for Sun Java Composite Application Platform Suite, jBPM, OpenSymphony OSWorkflow.

These implementations are showcased by means of:

  1. Workflow Portlet available in Portlet Repository(works with saw-impl-jcaps).
  2. Workflow Portlet available as part of Liferay Plugins(works with saw-impl-jbpm)
  3. Expense Report Portlet(available as part of eval bundle, works with OpenSymphony os-workflow)

Details about '1' are available here. Stay tuned for details around '2' and '3'.

Watch out saw site for screencasts, user guides, docs and other details.

Friday Aug 24, 2007

SAW is Ready

SAW Binaries ReleaseIn an effort to enable workflow functionality within products, SAW was conceived. However, a value added feature that has emerged out of it is that it abstracts the interaction with different workflow engines. As the diagram in Understanding SAW guide depicts, the intent of SAW is to be able to integrate with different workflow engines, thereby keeping the product using SAW pretty oblivious to changes.
Currently, SAW comes with a default integration with Java CAPS. For folks having Java CAPS(5.1.3) installation, it should be a matter of minutes to get the client stubs required to perform workflow. After having defined  a simple workflow as indicated in my article Incorporating Workflow into Portals with Sun Java CAPS, they should be able to play around with SAW. Ofcourse, alternatively, SAW User Guide offers a typical way of using SAW.
I am sure many of the developer friends will be interested in knowing more about SAW's details. And this is precisely why, the Java Docs are there too.
I invite/request you all to go through all this exhaustive material that we have around SAW and explore/give feedback at users@saw.dev.java.net , join SAW and help enrich it.

About

vihangpathak

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today