Welcome to the Ambassador Web 2.0 SEPIA-Kenai Project Wiki

- 1 Welcome to the Ambassador Web 2.0 SEPIA-Kenai Project Wiki
- 1.1 SVN
- 1.2 Visualization of Composite Document using OpenSSO
- 1.3 AjaxPush
- 1.4 TroubleTicket
- 1.4.1 TroubleTicket GlassFishESB BPEL
- 1.4.2 TroubleTicket screenshot
- 1.4.3 TroubleTicket deliverables
- 1.5 JavaFX portlet
- 1.6 Sun Web Space Server Best Practices
- 1.7 Portlet - JavaFX - REST full Service demo
- 1.8 Web2.0 Portlets catalog and classification
In the Sepia Kenai project we publish the following documentation & materials :
- architecture guides
- best practices guides
- developer guides for AjaxPush demo
- configuration guides for Auctionmanager & TroubleTicket (business) demo
- samples-demos(NetBeans projects)
- AjaxPush demo : counter, chat & AuctionManager
- TroubleTicket demo : WebSpace/GlassFishESB/OpenSSO
- JavaFX portlet
- Visualisation of Composite Document (SSO/Federation)
- Amphibious Portlet
- WebSpace Server Best Practices
- Web2.0 Portlets catalog and classification
regarding AjaxPush applications developed with netbeans 6.5.* / 6.7.* to be deployed on a Glassfish v2, GlassFish v3 or WebSpace Server 10.x (aka Liferay)
This project is part of the Ambassador Web 2.0 program.
SVN
- The SVN repos URL is https://svn.kenai.com/svn/sepia~sepia-svn-repository
- To view the content of the SVN repos : http://kenai.com/projects/sepia/sources/sepia-svn-repository/show
Basic commands for SVN
svn list https://svn.kenai.com/svn/sepia~sepia-svn-repository/trunk/ svn delete -m "purge" https://svn.kenai.com/svn/sepia~sepia-svn-repository/trunk/... svn import -m "1st Import" myProject
https://svn.kenai.com/svn/sepia~sepia-svn-repository/trunk/.../myProject
Visualization of Composite Document using OpenSSO
Alain and Christophe working on this subject...
This demonstration is based on visualization of composite documents. A composite document is composed of several documents coming from different sources. The purpose of this demo is to visually demonstrate the power of web service security in a federated environment. We use the concept of virtual enterprise to match to a real use case and simply understandable by anyone. We use the concept of document because :
- documents are generally tagged with security token which have a direct impact on visualization.
- documents can have different sources from different security domains
So we can provide a visual cross domain security demonstration using the concept of virtual enterprise. Firstly we will provide a demo with a company and a partner using Sun's technologies but this demo can be extended to other technologies to show interoperability and respect of standards.
User interaction must be intuitive, simple and use web 2.0 technologies. Documentation concerning this demo will be provided to describe :
- Goals, Technology and business impact
- General Presentation of the demonstration
- Installation of the demo and presentation guide for presenter
- Specifications
AjaxPush
AjaxPush samples already available
The samples source code can be downloaded from the SVN repos or the Download area (zip format). The samples have been tested successfully on the following configuration under Windows XP, Mac OS X, OpenSolaris & Linux. The samples source code are available as WebApp application or Portlet 2.0.
| Glassfish v2 | Glassfish v3 | WebSpace Server 10.* |
|---|---|---|
| chat | chat | chatPortlet |
| counter | counter | counterPortlet |
| AuctionManager | AuctionManager | AuctionManagerPortlet |
AjaxPush documentation
| Documentation | Description | Comment |
|---|---|---|
| Presentation (.pdf) | Available here | Presentation about the Ajax Push technology ... |
| Architecture Guide | AjaxPush Web2.0 Mechanism Architecture Guide | This guide describes the architecture style to achieve push mechanism with ICEfaces and Glassfish. |
| Development Guide for the session/application counter | AjaxPush Web2.0 Mechanism Dev Guide | This guide describes the Development steps and prerequisites to build a push mechanism sample application (counterApp) with ICEfaces and Glassfish / WSS |
| chat Deployment/User Guide/Screencast | Push Mechanism screencast | Screencast showing the functional demos |
| AuctionManager Deployment/User Guide/Screencast | Push Mechanism screencast | Screencast showing the functional demos |
TroubleTicket
Business application to transform opened TroubleTicket to WorkOrder with the support of an BPEL orchestration service.
- A web application or a portlet is used to monitor TrouleTicket and WorkOrders. These user interface are connecting to a BPEL process.
- The business process would initiate the creation of a Work Order following an operator's interaction with an existing Trouble Ticketing system and would interact with the mediation framework to retrieve site data information from the Configuration Management system (e.g. CMDBf) based on the distinguished name of the underlying network elements which were at fault.
TroubleTicket GlassFishESB BPEL
Here is a screenshot of the GlassFish BPEL process. One of the partner link is a ServiceMix service.
- The 1st part of the BPEL consists in collecting information from various sources/services (PartnetLink) required to create a WorkOrder.
- The second part is a simulation of the WorkOrder lifecycle and updates to the WO database table are performed following timers activation to reflect the WorkOrder status and activities done :
- work order "Not Started"
- work order "Started"
- work order "Engineer on site"
- work order "Resolved"
TroubleTicket screenshot
TroubleTicket deliverables
| Deliverables | Status | Comment |
|---|---|---|
| Draft D0.2 for review | |
| Draft D0.2 for review | |
| 1st version without voice comment | Start withTroubleTicketv2-portlet-11052009.html |
| 1st version without voice comment | Start withTroubleTicketv2-web-11042009.html |
| NetBeans projects Available in the SVN | The full distribution is about 219MB |
JavaFX portlet
The JavaFX platform is designed to enable easy creation and deployment of rich internet applications (RIA) with immersive media and content. The JavaFX platform ensures that RIAs look and behave consistently across diverse form factors and devices.
The tutorial uses the JavaFX platform to demonstrate how easy it is to integrate a JavaFX application into WebSpace Server.
The tutorial steps through the development process to the WebSpace Server configuration of the JavaFX portlet. Some JavaFX samples form http://javafx.com/samples/ have been reused. It is completely out-of the scope of this tutorial to cover the development of JavaFX apps.
| Deliverables | Status | Comment |
|---|---|---|
| JavaFX sample | Imported into SVN | |
| JavaFX portlet samples | Imported into SVN | |
| 2nd draft with codebase fixed for WXP | Review tin progress |
As another sample, we have integrated into a portlet the ShiFuMi machine developed by Christophe Vaille on the following WebSpace Server : http://freeze.france.sun.com:8080 Express login as admin for the base Sample Users Tab JavaFX
Sun Web Space Server Best Practices
Following there are documents related with Portlets and the Sun Web Space Server:
- Creating the environment to develop for Web Space Server (JEE 5, WSS 10.0 and NetBeans 6.5) - v1.1: Get PDF
- Creating the environment to develop for Web Space Server (JEE 6, WSS 10.0 and NetBeans 6.8) - v1.0: (coming soon)
- Portlets by Example (I) Greetings: Get PDF
- Portlets by Example (II) Profile: Get PDF
- JSF Best Practices (English): (coming soon)
- JSF Best Practices (Spanish): Get PDF
Portlet - JavaFX - REST full Service demo
REST stands for Representational State Transfer. REST uses HTTP for all four CRUD (Create/Read/Update/Delete) operations. REST is a lightweight alternative to mechanisms like RPC (Remote Procedure Calls) and Web Services (SOAP, WSDL, et al.). REST becomes more and more popular and the adoption is growing very fast. A lot of services provide by Yahoo, Google, Amazon are already exposed and can be used to developed WEB2.0 applications. This demo shows a JavaFX portlet having access to a service exposed as a REST service. The REST service is based mainly on a TOPLink interface retrieving from a JavaDB database some information to be displayed in the portlet.
| Deliverables | Status | Comment |
|---|---|---|
| REST | 1st Draft | |
| REST JavaFX portlet samples | Imported into SVN |
Web2.0 Portlets catalog and classification
In Progress. To be done by a leader, but completed by the whole team ... Another idea would be to put a generic portal demo online (swan) to show all of them... We need a server available on the swan ??






