Tuesday Jun 09, 2009

Simplify Your Portal Deployment: Web Space Server 10 VM Template

If you're looking for an even easier way to deploy Webspace, look no further than the recently-released Sun GlassFish Web Space Server Virtual Machine (VM) Template.  This project pulls together many of Sun's open source components, and provides a simplified, pre-configured virtual image containing GlassFish Webspace Server, GlassFish Enterprise Server, MySQL, and OpenSolaris (Just Enough), in multiple virtual image formats. 

Ready, Set, (deploy) and Go!

Thursday May 14, 2009

Deep Dive: Sun GlassFish WebSpace Server

Deep Dive: Sun GlassFish WebSpace Server, An Interview With James Falkner

As part of the the WebSpace Server 10 release, Ed Ort (from java.sun.com) and I sat down to do a deep dive webcast for GlassFish WebSpace Server. Parts 1 and 2 were originally published a few weeks ago. Now, parts 3 and 4 are now available and cover development tooling, and end user social collaboration techniques.

Enjoy!

Monday Apr 27, 2009

Web Space Server 10.0 Downloads

Web Space LogoThe user-oriented site webspace.dev.java.net  has had download links for a while for our Community and Milestone builds.  Now available are CDDL-based downloads of the 10.0 Final Release, which means you can download without having to have an SDN account or accept the Sun License Agreement.  The binaries are licensed under CDDL.  So easy to use!

Wednesday Feb 18, 2009

WSRP 2.0 FCS binary

The WSRP 2.0 FCS binary is now available for download from the OpenPortal WSRP project download page and has implemented all the WSRP 2.0 mandatory and most of the optional features. This project binary is being shipped into the below release vehicles apart from the above standalone install which the project provides as a wsrp-configurator.jar

2. Liferay version 5.2 and higher.

The source code for the above is tagged as "liferay-5.2-snapshot" - In case you need the code for some debugging.

On the trunk work continues on the 2.1 release -- Which is a maintenance release. Please use the project mail list for any questions and comments.

Monday Feb 16, 2009

Content Management System in Glassfish Web Space Server 10.0

Glassfish Web Space Server comes with its own out of the box Content Management Sytem(CMS). The WebSpace CMS comprises of the following features :

1. Document Management.
2. Image Management.
3. Web Content Management.

To know more about CMS in Web Space Server, read the following article :

http://blogs.sun.com/prakashKLV/entry/content_management_system_in_glassfish

To start adding web content using CMS in Web Space Server, read the following articles :

http://blogs.sun.com/prakashKLV/entry/adding_content_to_portal_page

http://blogs.sun.com/prakashKLV/entry/structures_templates_and_web_content

Stay tuned and visit this blog for latest articles on CMS in glassfish Web Space Server.

Wednesday Feb 11, 2009

Web Space Server - Localization

Web Space Server has out-of-box localization for 22 languages , out of which Sun provides localization support for Japanese (ja) and Simplified Chinese (zh_CN). Remaining languages are community driven.Also it has been Internationalized which allow localization in new languages which does not shipped out of box.

For further details on Localization (L10n) , Refer my personal blog entry :  Web Space Server - Localization

Monday Feb 09, 2009

Sun GlassFish Web Space Server 10.0: Now Available!

Web Space LogoSun GlassFish Web Space Server 10.0 has been released today [download].  It is Sun's next-generation portal server platform. It enables businesses large and small to pull together applications and content from a variety of Web-based and internal sources and present them as a unified, customizable portal on Web browsers, kiosks, and mobile devices.  It is part of a larger Portfolio of software being released today as part of the GlassFish Portfolio.

Web Space Server started out about a year ago with a partnership with Liferay Portal to join forces to develop the core portal in the Liferay community. Web Space Server is Sun's first product based on this effort and common code base. You may still run across instances of the term Project WebSynergy - this was Sun's internal codename for the project before it was released.

Standards such as JSR 168, JSR 286, JSR 170, and WSRP 2.0 provide a solid foundation on which to build a modern web 2.0 enterprise application platform, using lightweight web-oriented architectures, and powerful developer tools to create a rich ecosystem for developers, integrators, administrators, and now users to collaborate and innovate with.

A new user-oriented site webspace.dev.java.net  has been established.  This site will house information most useful to administrators and end users of Web Space Server, including download and documentation links, community support forums, email lists, wiki content, and other useful information.

New community builds and milestones of Web Space Server will continue to be released to deliver new features and fix bugs.  This release is marked 10.0 to indicate it is a (r)evolutionary step from previous portal efforts, such as Portal Server 7.2.

The WebSyner--err--Web Space team is proud to bring you this first release, and hope you will like it as much as we do!

Monday Jan 26, 2009

Relocating WebSynergy Installations

Chris Reemts has found that relocating a WebSynergy-on-GlassFish installation is possible by following a few simple steps:

Moving a WebSynergy+GlassFish installation from one directory to another on OpenSolaris


The following are the actions I took to move an install of the MileStone 4 build of WebSynergy on OpenSolaris.
  • The installed location was: IL == /export/home/demo/Desktop/
  • The new location is: NL == /export/home/demo/
To move (NOTE: It is a good idea to save a copy of any files before editing):
  • Move the entire web\* folder from IL to NL – I used the file browser to do this
  • Modify NL/web\*/glass\*/bin/asadmin
    • 1.Open in a text editor
    • 2.Line 7 contains a path --- correct this path to the new location
    • 3.Save
  • Modify NL/web\*/glass\*/config/asenv.conf
    • 1.Almost every line has a path that you need to change to the new locations path
    • 2.Save
  • Modify NL/web\*/glass\*/domains/domain1/config/sun-acc.xml
    • 1.You may have a domain name different from domain1
    • 2.Line 26 value is a path --- correct this path to the new location
    • 3.Save
  • Modify NL/web\*/glass\*/domains/domain1/jbi/config/jbi-registry.xml
    • 1.You may have a domain name different from domain1
    • 2.Lines 19, 20, 25, 26, and 30 need the path corrected to the new location

This allows, for example, one to relocate a full install from one server to another (if using GlassFish V2, the destination machine must be the same OS/architecture). Nice work Chris!

Thursday Sep 18, 2008

How to do I18n and L10n in WebSynergy

Recently we have defined a common way to do I18n and L10n in WebSynergy. This process will be used for I18n/L10n during development of WebSynergy. It can also be used to develop new porlet with taking advantage of existing UI Tag lib and Language util class for I18n/L10n.

Details can be found on my personal blog entry .


Wednesday Aug 27, 2008

Project WebSynergy Stable Build 2: Now Available!

As you know, in May of this year, Sun and Liferay announced a partnership to jointly develop next generation enterprise portal technology.  The Sun portal team has since begun the rollout of Project WebSynergy, codename for the initiative to release a product based on this common technology.

The Project WebSynergy team is now proud to make its Stable Build 2 available for download!  This release represents a significant milestone for the project, incorporating a number of new features, improvements, and a general enhancements over the last stable build (which was made available in May @ JavaOne).

Some of the things to look for in SB2:

  • Release Stability and Cadence
  • The primary goal of this release was to establish regular builds (which you will start seeing regularly, not once every 2 months), get testing frameworks in place and automated (as soon as the public site, see below, is setup, automated test results will be posted as well), and establish basic hooks/frameworks in the Liferay community for future builds/releases to take advantage of.  As mentioned in my previous post, this is a Stable Build (as opposed to a Community Build or Commercial Release).

  • WSRP 2.0 Consumer Support & Admin Application

  • WSRP 2.0 Consumer support is now available.  In addition, a WSRP consumer administration application is available in WebSynergy that enables managing multiple WSRP Consumers. For more information, read the blog post.

  • Mirage/Journal

  • Liferay Portal has been modified to use the Mirage API. This API enables WebSynergy to use JCR-compliant repository.

  • Roller Blog Application

  • The Roller Blog app provides integration with Roller Weblogger version 4.0. Using this app, portal users can create and manage blogs on a Roller 4.0 server.

  • Simple API for Workflow

  • The Simple API for Workflow (SAW) feature is integrated into the Project WebSynergy SB 2 stable build. A sample Expense Report portlet provided with this feature showcases a typical enterprise Expense Report Application that involves human workflow. You can use SAW to connect to a business process engine such as the Java Composite Application Platform Suite provides the workflow functionality to the Expense Report portlet.

  • Presence

  • For more information on this feature, see this article on the Liferay wiki. In upcoming Project WebSynergy builds, new applications using this infrastructure will provide a more presence-aware Portal to end users.

  • Semantic

  • Core semantic processing libraries and utilities have been integrated into the portal. In the upcoming Project WebSynergy builds, the communities in the Liferay Portal Communities use this feature to provide a semantically rich experience to end users.

This build represents another in a series of binary releases of this project leading up to Sun's commercial release.  The product based on this project is also being renamed (Project WebSynergy is the internal codename), and we really don't want to have name confusion between the free-to-use, open source version and commercially supported version, so the external site presence (as described in my previous post) does not yet exist.  This should be resolved in the 14 days.

Note on GlassFish v3 - Project WebSynergy is available on GlassFish v2.  In the coming days, we expect to also make available a v3-based bundle based on GlassFish v3 TP2.


Sunday Aug 17, 2008

Liferay consumes OpenPortal WSRP project

The OpenPortal WSRP Project consumer is now integrated into Liferay Portal. The next stable release of Liferay Portal is expected to have both the OpenPortal WSRP producer and consumer integrated in it.

Checkout the following posts for detailed information on this integration.

  1. OpenPortal WSRP 2.0 Consumer in Liferay
  2. Testing WSRP 2.0 interoperability in Liferay

Stay tuned on the OpenPortal WSRP Project mailing list for more information w.r.t to this integration.  

Friday Aug 01, 2008

Project WebSynergy Update Part 1: Community and Roadmap

As you know, in May of this year, Sun and Liferay announced a partnership to jointly develop next generation enterprise portal technology.  The Sun portal team has since begun the rollout of Project WebSynergy, codename for the initiative to release a product based on this common technology.

Since May, we have been working on establishing the project in more concrete forms, establishing an online presence, producing regular builds, and releasing source code.  In the next month or so you should see the results of this groundwork.  In the meantime, I'll keep you updated on where we are at (in addition to making builds and source available, see below).  This "Part 1" will cover Community and Roadmap.  In future parts, we'll cover items such as architecture, build structure and distribution contents, feature deepdives, and other technical interests.

Most of the work to date has been over at the Sun Liferay community, integrating components (e.g. Portlet Container), and new features (e.g. Message Board improvements) needed for WebSynergy.  As the project evolves, additional features will be developed and used in WebSynergy proper and ultimately be part of a commercial offering.

Community

OpenPortal consists of a number of projects.  Each of these projects delivers a certain set of functionality, and Sun (as well as anyone else who wishes) produces a commercial offering based off of the available source.

  1. portal.dev.java.net - Core portal software, from which Sun's commercial Portal Server 7.x vintage is derived.  In addition, patches to 7.x will be generated for 7.x from this project's source.  No changes planned.
  2. <name>.dev.java.net - Parent project of Project WebSynergy, from which Sun will derive a commercial offering.  Source and regular builds will appear here once the site is operational.  The name of this site is TBD.
  3. [mirage,saw,wsrp,ruon,swa,portlet-container,jsfportletbridge].dev.java.net -  Projects delivering major functionality, consumed by both Sun Portal Server 7.x and WebSynergy.  No changes planned.
  4. portalpack.netbeans.org - NetBeans & Eclipse plugins for developing portlets.  No changes planned.
In short, we are adding a new project to OpenPortal to represent the core of WebSynergy, since it is so very different from the 7.x vintage.  OpenPortal is also now a proper part of the larger GlassFish community (which means association with a vibrant and growing open source community).

Roadmap

For WebSynergy, we are going to take a different tact: make things available early and often.  Because project community members are now using the latest open source code to develop new features before Sun has released its latest commercial offerings, some consumers are finding that they would rather have features earlier, even if long-term support is not available. In response to this demand from both Sun Java System Portal Server customers, and the OpenPortal community, we will be producing builds with varying support options, much more frequently than in the past --as often as bi-weekly.  This will give customers a chance to get working code immediately, and pay only for the support they really need (or use the freely available builds with no support).  This kind of a model is being adopted in other projects (e.g. OpenSSO), so its function may already be familiar to you.

There are three types of builds that will be made available based on Project WebSynergy:
  1. Community Build: Lightly tested, new features likely to be incomplete or have issues. Entirely supported by Community. New community builds generally available approximately 2-3 times a month.
  2. Stable Build: Higher amount of testing. Complete documentation. Available roughly every 6-8 weeks.
  3. Commercial Release - Highest amount of testing, complete documentation, commercial support available. Suitable for long term enterprise deployments. Frequency varies.

The demo that was made available at JavaOne represented the first Stable Build (SB1). SB2's plan is to be available this  onth, with an expected date for the first Commercial Release in the first quarter of 2009. Before SB2, there may be a community build (I had implied it would be this week, but a few of the features going into Liferay are still under code review, and not ready yet).

As indicated in the original announcement, we are not maintaining a fork. Instead, various components will be developed in WebSynergy, some of which will be integrated upstream (e.g. in Liferay) as needed, and a commercial release (and associated sustaining tail) will be initiated for each Commercial Release.  This is depicted in the below illustration (click on the image to get a larger version!).

Project WebSynergy Release Model

What you should get out of this image:

  1. The names of the components and releases and dates are all subject to change :-)
  2. There is no fork.  Each release is based off of a specific point in time of all components, including Liferay.  For the next release(s), new snapshots are taken, and the old ones ignored.
  3. Bugfixes bi-directionally flow between WebSynergy and Liferay before and after each Commercial Release. 

Stay tuned for part 2 and for the new WebSynergy site and builds to go live soon!

Monday Jun 23, 2008

JSR286 (Portlet 2.0) spec has been released

JCPThe JSR 286 (Portlet 2.0) specification has been released. Congratulations to Stefan Hepper, the spec lead of JSR 286 and the rest of the expert group. It has been a pleasure working with all on this JSR.

The main features of this JSR include

OpenPortal Portlet Container 2.0, which is a fully compliant implementation of the Portlet 2.0 (JSR286) specification, has been released. Check my blog for more details.

Tuesday Jun 17, 2008

Leasing for Remote Portlets

WSRP 2.0 offers Leasing of Portlets as part  of the specification. Leasing is the process by which a Consumer registers with a Producer for a specified time period, after which the Consumer Registration is rendered invalid. Lifetime is an optional parameter in the Registration offered by V2 producers. The OpenPortal WSRP project (Sun's open source implementation of WSRP ) has implemented this feature using the Open Source Portlet Container 2.0 . Check this wiki page for more information on portlet leasing.

Here's a primer on using the Leasing feature.. 


About

atul

Search

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