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.

Wednesday Nov 14, 2007

Glassfish Day @ Beijing

Participants flocked together to attend the Glassfish Day . I had the opportunity to talk about OpenPortal  at the Glassfish day held in Beijing. It was a wonderful bunch of participants. Do also check out Arun Gupta's blog and Carla King's blog on the same.

I talked about OpenPortal, its decoupled features, Web2.0 features, There were many questions asked about OpenPortal at the end of the talk and here is the excerpt about some of them:

  1. CMS Story
    • Check out Project Mirage. CMS  is available in the form of infrastructure APIs, Netbeans tooling and out of the box portlets(Article Management, Document Management and Custom Content Definition Portlets). CMS is being integrated with JSR170 repository e.g. Apache JackRabbit via the OCM mapping.
    • The project deliverables will be in terms of several individual smaller sub projects some of which may come in under some different projects. The deliverables from this project will be consumed by the OpenPortal project to provide CMS functionality to the portal product. The current plan is to provide in terms of deliverables :
      • CMS Infrastructure and Generic API based on the Apache Jackrabbit implementation of the JSR-170
      • CMS Tag Libraries which developers can use to create web applications/portlets that can leverage the features offerred by the content repositories.
      • Sample portlets which will be a part of the Portlet Repository. The sample portlets will showcase how to use CMS Infrastructure/API's to store/retrieve/update structured and unstructured content to the JCR.
      • Tooling Plugins for developer IDE's which empower the developer to use the Mirage API and Tag Libraries with the greatest of ease. These will be available under the Portal Pack Project.
  2. Comparison with other portals
    • Powerful CMS Story(independent of a JSR 170 compliant Repository)
    • Identity Based Content Delivery is also one of the powerful features of OpenPortal
    • Decoupled features viz. SAW, CMS , DesignView, Delegated Admin are some of the contrasting features
    • Secure Remote Access
  3. Difference between OpenPortal and OpenSource Portlet Container
    • OpenPortal and Open Source Portlet Container(OSPC) are two different projects and different consumables. OpenPortal consumes OSPC to cater to the lifecycle of a portlet(JSR 168 or JSR 286). OpenPortal is the entire Portal itself. A Portal in its entirety offers variety of different value added features viz. Security, Identity Based Content Delivery, CMS, Workflow, Collaboration, Communities etc. An OpenSource Portlet Container is a portlet container helping to render the life cycle of a portlet(JSR 168/JSR 286).
  4. Can OpenPortal work with different applications for enabling SSO
    • Yes, there is an SSOAdapter available which can be extended to enable SSO for different applications
  5. How can we contribute to OpenPortal.
    • Go to OpenPortal
    • Check out Community Wiki
    • To get involved check out GetInvolved Section
    • To subscribe to mailing lists, see the mailing lists or subscribe to the mailing list
  6. What are the various URLs specially portlet-repository
  7. Want to pitch for OpenPortal, but unable to download
    • Send Request to with exact problems faced
  8. Only available for Glassfish?? Not for Apache Geronimo
    • Currently only Glassfish
  9. How is OpenSource Portlet Container available?
  10. How to develop a simple login portlet.

And as time passed by , we came to the end of a wonderfully hosted Sun Tech Days(thanks to the organizers)






« June 2016