The OpenPortal WSRP v2 milestone 4  is now available for download, milestone 4 is the last feature preview binary from the OpenPortal WSRP v2 project. The OpenPortal WSRP is feature complete from the WSRP 2.0 spec perspective by implementing all the mandatory and most of the optional features.

This milestone previews the following optional WSRP v2 features

1. WSRP 2.0 CC/PP Capability
2. WSRP 2.0 Leasing
   1. Registration Leasing
3. Interoperability Fixes

 

Here are the links to the binary and documents associated with this milestone.

A. Binary download

1. WSRP version 2.0 milestone 4 binary  requires
2. Portlet Container 2.0  16 April 2008 binary
   

B. OpenPortal WSRP documents:

1. Whats new in Milestone 4
   
2. Glassfish Install Instructions
3. Tomcat Install Instructions
   
4. User Guide
5. WSRP v2 milestone 4 samples
6. Sample Portlets

 

The WSRP version 1.0 FCS is the latest stable binary from the WSRP v1 project. This is expected to be the last binary release from the WSRP v1 Project and this project will remain in maintenance mode, only serious issues reported will be fixed from now on. This same binary is integrated into the following releases.

1. Sun Java System Portal Server 7.2 release and
2. Java Application Platform SDK Update 5.

From now on all future developments and feature integration will happen only on the WSRP version 2.0 project. 

A. Binary download

1. WSRP version 1.0 FCS bits  requires
2. Portlet Container 2.0 RC2
   

B. WSRP documents:

1. Install Instructions
2. User Guide
3. FAQ

C. Portlet Container documents:

1. Install Instructions

D. See Also:

1. Portlet Repository binary

 

We just completed the WSRP version 2.0 interoperability test cases with OpenPortal WSRP Project Consumer and IBM Producer.  Here are some screenshots and details about this interoperability test cases.

A. WSRP 2.0 Eventing Interoperability:

IBM interoperability server exports the following 2 portlets that communicate with each other using events:

1. FlightBookingPortlet
2. HotelBookingPortlet
   

Using the FlightBookingPortlet and booking a flight results in an event that is caught by the HotelBookingPortlet and blocks a hotel in the same city. Here is a screenshot of these portlets on the OpenPortal WSRP driver.

 

 

B. WSRP 2.0 Shared Render Interoperability:

IBM interoperability server exports the following 3 portlets that communicate with each other using shared or public render paramters:

1. PublicParamCityInfo
2. PublicParamCitySelect
3. PublicParamCityWeather
   

Using the PublicParamCitySelect and selecting a city results in setting of a shared render parameter that is received by the PublicParamCityInfo and PublicParamCityWeather which display the city information and weather respectively. Here is a screenshot of these portlets on the OpenPortal WSRP driver.

 

 

C. WSRP 2.0 Resource Serving:

There is not special portlets for this, if you observe the above eventing and shared render parameter portlet, you could see the image that is being displayed by these portlets are fetched inband or using the getResource() method call on the portlet, which validates the getResource WSRP version 2.0 implementation on the OpenPortal WSRP Project

This interoperability tests all the major WSRP version 2.0 features, stay tuned for more information on the OpenPortal WSRP Project mailing lists.

 

Checkout the following announcements on the release of a new milestone binary from OpenPortal WSRP Project.

1. Project Announcement : OpenPortal WSRP version 2.0 milestone 3 now available   or
2. Blog on PortalPost .

 

This new milestone 3 supports the following feature set

1. WSRP 2.0 getResource
2. WSRP 2.0 Caching
   1. Markup Caching
   1. Expiration Markup Caching
   2. Validation Markup Caching
      
   2. Resource Caching
   1. Expiration Resource Caching
   2. Validation Resource Caching
      
3. Tomcat 5.5 support
4. Migrated code to the latest WSRP 2.0 schema

 

Pls note that the previous milestones have already provided the following WSRP  version 2.0  feature sets.

1. WSRP 2.0 Eventing.
2. Shared/Public render parameters.

 

The above links also provides sample portlets and configuration instructions to try out these features. If you have questions on how to use the OpenPortal WSRP Project and other comments/suggestions/requests, consider joining the users@wsrp.dev.java.net alias.

Just a repost of the information on Portal Post w.r.t to WSRP version 2.0 milestone 2 binary. Here is the actual post  

The OpenPortal WSRP version 2.0 milestone 2 binary is now available for download. The binary along with install instruction is available on the Open Portal WSRP download page.  This is the second milestone release from the OpenPortal WSRP Project that implements the OASIS WSRP version 2.0 specification. The main intent of this release is to preview the following optional features defined in the WSRP version 2.0 of OASIS specification.

1. WSRP Eventing
2. Shared/Public render parameters
   

Pls follow the instructions in coordination preview document on how to test and use these features that'll help you to understand the implementation.

Here are the links to the complete set of documents for this milestone.

1. Install Instructions
2. User Guide
3. WSRP v2 Coordination samples

Stay tuned for more optional feature implementation in the future milestones of the OpenPortal WSRP version 2.0 project. If you would like to keep track of future announcements and additions to the OpenPortal WSRP Project, please subscribe to the announce@wsrp.dev.java.net alias.

If you have questions on how to use the OpenPortal WSRP Project and other comments/suggestions/requests, we urge you to join the users@wsrp.dev.java.net alias.

Please report any issues that you encounter while trying OpenPortal WSRP version 2.0 milestone 2 to issues@wsrp.dev.java.net.

Check the following thread for the manual instructions of installing and configuring OpenPortal WSRP on Tomcat. The above instructions is validated against the following binaries.

1. Tomcat version 5.5.25
2. Metro version 1.1
3. Portlet Container version 2.0 Beta 2 (2 Jan  2008 build)
4. WSRP latest trunk binary.

Stay tuned to the OpenPortal WSRP aliases for more news related to automatic configuration soon. 

The OpenPortal WSRP version 2.0 milestone 1 binary is now available for download, checkout the following announcement on the OpenPortal WSRP project. 

 
Here are the links to install and user guide.

• Install Instructions
• User Guide

 The above WSRP binary works over the latest OpenPortal Portlet Container 2.0 beta 2 binary, checkout the  following announcement with respect to OpenPortal Portlet Container binary. Here are some links to the Portlet Container documents

• Release Notes
• Installation Instructions
• Article: Understanding the Portlet Container 2.0 beta
• Screencast: How to deploy and test portlets using the Portlet Container

Stay tuned for future announcements on OpenPortal WSRP Project on other WSRP version 2.0 feature implementation, Please subscribe to  announce@wsrp.dev.java.net

The implementation of the WSRP version 2.0 is in full swing in the OpenPortal WSRP Project community. Here is the link to the project wiki page that tracks this project.

• WSRP version 2.0 Project Wiki Page

Apart form this the following documents are also available for review

1. WSRP v2 FSD
2. WSRP Consumer Admin Usecases
3. Eventing Usecases
4. Architecture changes for WSRP v2
5. Project Plan
   

If you have comments or questions, pls join the project and post your queries or comments. Stay tuned for the milestone 1 drop which is expected in the next few weeks also for more features in the future drops.

Here is how you uninstall OpenPortal WSRP and OpenPortal PortletContainer projects after successful installation without having to uninstall the whole glassfish application server. Recently I came across this issue since someone asked about it and this information was not available or documented anywhere.

 

Uninstall OpenPortal WSRP :

Upon successful install of OpenPortal WSRP, The installer would have created a 'wsrp' directory as <glassfish_install>/domains/domain1/wsrp. There is a setup.xml under this directory, invoking the 'uninstall-wsrp' ant target does the job. Here is the example

# ant -f setup.xml uninstall-wsrp.

Make sure you restart the glassfish application server after this.

 

Uninstall OpenPortal PortletContainer :

Similar instructions apply the OpenPortal PortletContainer uninstall procedure. Upon successful install of OpenPortal PortletContainer, the installer would have created a 'portlet-container' directory as <glassfish_install>/domains/domain1/portlet-container. There is a setup.xml under this directory, invoking the 'uninstall-pc' ant target does the job. Here is the example

 

# ant -f setup.xml uninstall-pc.

 Make sure you restart the glassfish application server after this.

 

 

OpenPortal WSRP 1.0 beta is now integrated into the Java Application Platform SDK Update 3 Beta release. The WSRP implementation provided over the OpenPortal Portlet Container 2.0 beta which is also available in the same Java Application Platform SDK bundle.

 

Portlet Container 2.0 beta implements some of the JSR286 features based on the early access draft , its available as a preview in the above bundle.

 

Here is the location to get all the details about this bundle ( download, release notes, install instructions, articles and more).  

 

Here is some of the issues that we encountered during migration of the OpenPortal WSRP Project from JAX-RPC to JAX-WS. The following note does not go into details on why these changes are required and the concepts behind it, rather helps you to deal with migrating your application from the older webservice stack to new stack.

Consider leaving a note if you have faced a different issue and solved it, so that it would benefit other.

[Read More]

 

The OpenPortal WSRP project is consumed or integrated into the OpenPortal project, Here is a note on some of the integration that was done.

Java Persistence API based (JPA) based datastore :

Added a new datastore for storing WSRP Producer and WSRP Consumer related configurations The file based datastore that OpenPortal WSRP Project is unacceptable as the configurations stored in file would be local to specific portal server node. The JPA based WSRP datastore implementation by default uses derby as backend to store all the WSRP Producer and Consumer related configuration information.

 

Note : The source code for this resides in the OpenPortal WSRP Project as this can be used outside of the OpenPortal. Watch this space for more details on how to use it in OpenPortal WSRP Project.

User Management:

The OpenPortal project customizes the user datastore of the OpenPortal WSRP Project, its provides user store where WSRP users are created and managed on to the LDAP server that is used by the OpenPortal installation. OpenPortal project creates creates people container under organizational units for each consumer registration The people container is used for creating phantom users that are specific to a consumer registration.

 

Note : Pls see the other entries on WSRP User Identity Propagation to know more about phantom users and identity propagation techniques

Role Management :

OpenPortal uses roles in LDAP/Access Manager to store explicitly cloned portlets. Explicit clones are portlet clones that are created by consumers that needs to be shared by all the users. Hence the cloned portlet is stored on to the role and all users under that consumer registration are assigned to this role, which makes the portlet clone available to all the users under this consumer registration.

 

Here is a simple representation, the WSRP Producer and WSRP Consumer stores configuration onto a database. The WSRP Producer uses the AM /LDAP  server to create users and roles for the above mentioned functionalities.

 

Single SignOn Token(SSOToken) Identity Propagation:

OpenPortal uses AccessManager(AM) to authenticate users, authenticated users are represented by a Single SignOn Token(SSOToken) in AM. Since SSOToken is used only in OpenPortal, the SSO identity propagation is added as an extension by the OpenPortal Project to WSRP Project.

 

When this option is selected the SSOToken associated with the user is propagated as an UserContext extension by the WSRP Consumer to the WSRP Producer which represents a user. 

 

Note : This identity propagation mechanism assumes that both Consumer and Producer Portal are OpenPortal installations. Pls see this entry for more details

WSRP Mbeans :

The OpenPortal WSRP Project Mbeans are consumed by the OpenPortal and integrated into the OpenPortal Portal Administration Server (PAS) module, the WSRP Mbeans are deployed on to the Common Agent Container for APG and Orion/Common Agent Container (CACAO/CAC) management server. The OpenPortal administrative console (psconsole) provides a user interface for WSRP administrative purposes using the above Mbeans.

 

Note: Pls see the architecture here and the intent of this design.

WebService Single Sign On (WSSSO) Portlet :

The OpenPortal project provides a portlet/user-interface that allows users to add/provide Single SignOn information in the form of a username and password. This portlet stores the user credentials that is used by the WSRP Consumer to create a OASIS Username Token profile and propagate the user identity to the WSRP Producer portal.

 

Note : The WSSSO Portlet uses the SSOAdapter infrastructure to store user credentails, Pls see here for more information on SSO Adapter.

 

We have put together an article on the Open Portal WSRP Project titled "Open-Source Portal Initiative at Sun, Part 4: Web Services for Remote Portlets".  This article provides an overview about the Open Portal WSRP Project and some details about its architecture, deployment, build process and usage instructions.

Following are the links to all the article in this series

• Open-Source Portal Initiative at Sun, Part 1: Overview
• Open-Source Portal Initiative at Sun, Part 2: Portlet Repository
• Open-Source Portal Initiative at Sun, Part 3: Portlet Container
• Open-Source Portal Initiative at Sun, Part 4: Web Services for Remote Portlets
  

The Enterprise class Portal Server Project now has a new name, its called OpenPortal. It also has a brand new logo. All the subproject are now referred with OpenPortal prefixed to them. For e.g. the Enterprise-class WSRP Open Source Project is now called OpenPortal WSRP Project.

 

Apart from this, the Sun Java System Portal Server 7.1 source code is also available for download on the OpenPortal Project, check out the download page for more details.  Please keep a watch on the Portal Post for announcements related to the OpenPortal Project. 

Here is the list of features that WSRP 2.0  addresses or adds over WSRPv1 specification. We'll try to contrast and compare with the JSR286 specification in some places and see how these two specifications compliment each other. Here is the list of new stuffs that WSRP v2 brings to the table.

[Read More]