Testing of Alfresco SHARE Labs 3d version

I'm currently testing the latest community version of Share (Labs 3d).

It has been really improved compared to previous version...one example is that now the Calendar is fully working. Also site members management has been significantly improved. This version seems really more stable and finalized.

I think this version is user-friendly enough to be opened to end-users and let them create their site (team space) without any help.

Main features are:
- User Dashboard,
- Document library (based on Alfresco Document Management repository),
- Blog,
- Forum,
- Wiki (quite simple for the moment),
- Calendar,
- Links (bookmarks management),

New site creation is very easy and quick.

So my global feeling about this new version is very good.
I'm now waiting for Enterprise version 3.1 (based on Community 3d version) to be able to test it in our company (scheduled for february 2009).....

IBM Licenses Ephox EditLive! for IBM WCM EOM agreement

IBM has signed an OEM agreement with Ephox to license EditLive! for IBM WCM. This agreement means all
IBM Lotus Web Content Management customers will now have access to the
best HTML editor on the market, fully integrated into their WCM platform.

Source: http://blog.ephox.com/weblog/2009/01/announcement-ibm-licenses-editlive-for-ibm-lotus-web-content-management.html

I think this is a good news for all WCM users. We did evaluate Ephox RTE a few month ago and it provides a lot of very really usefuls features...but the cost was quite important at the time.

So now I think we will consider using this RTE in our project asap.

New JSR-286 rendering portlets for Lotus Web Content Management

FYI, the JSR 286 version of the WCM Rendering Portlet is now available for download from the Portlet Catalog.

====================
IBM annoucement:
The IBM® Lotus® Web Content Management Rendering Portlet provided with this package is a solution which updates and improves how the rendering of Web content is performed in IBM WebSphere® Portal. While the existing Web Content Viewer portlet (referred to in the WebSphere Portal documentation as a "rendering portlet") has evolved throughout several versions to implement sophisticated Web content rendering functions, it is still based on the deprecated IBM Portlet API. By contrast, the new JSR 286 Web Content Viewer has been entirely redeveloped based on the Java™ Portlet Specification 2.0 (JSR 286). In addition to the benefits afforded by JSR 286, the JSR 286 Web Content Viewer in this package also enables other features for Web content management, such as a new Web content portal page type and support for the standard search seedlist 1.0 format.

====================

For more information:IBM Lotus Web Content Management Rendering Portlet JSR 286

I did not test this Portlet so far, so I cannot give you any feedback for the moment...but if some of you already tested it your results and feedback are of interest for me...

I think we will test it asap, because I would like to get the following info:
- This new release means that the WCM Portlet delivered with 6.1.x WPS version is still based on the deprecated IBM Portlet API...So will this new release update the current existing Portlet clones we have created so far...(I don't think so, but would like to make sure).
- What about the WCM remote rendering Portlet (is it included in the same package) ?
- Does this new release support the CSA (Client Side Aggregation)...? (I know that previous 6.x release of the WCM Portlet does not support CSA, so this would be a major improvement).


Will let you know about our tests...

WebSphere Portal configuration : where are config and log files in v6.x ?

A lot's of things have changed in WebSphere Portal v6.0 and even more in 6.1.
Sometimes I spend a few minutes looking for a configuration file that has been moved to another folder and/or renamed....For those like me who are a little bit lost, here is a list of common v6.x config. files you need to work with frequently, and their correspondancy with v5.x


Basically, all the Portal and WCM config. files are now moved to : "/portal/WebSphere/wp_profile".

v6 logs file for WPS + WCM:
Now you will find most of the traces in:
/portal/WebSphere/wp_profile/logs/WebSphere_Portal/SystemOut.log

In v5, the corresponding files are :
[PortalServer root]/log/SystemOut.log
+
[PortalServer root]/log/wps_yyyy.mm.dd-hh.mm.ss.log
+
[PortalServer root]/wcm/shared/app/config/aptrixjpe.properties and connect.cfg
)


Please note that by default there are no more specific WCM log (like connect.log). Now WCM log traces output is located in SystemOut.log. (However, it is probably possible to configure the trace management system in WAS console to clearly separate WPS and WCM logs, as it was before in v5).


---------

WCM v6.x Config file (replace previous v5 aptrixjpe.properties and connect.cfg):
/portal/WebSphere/wp_profile/PortalServer/wcm/shared/app/config/
wcmservices/WCMConfigService.properties


---------

See the current fix level of the WPS application:
/portal/WebSphere/wp_profile/PortalServer/log/VersionInfo.log


---------

VMM LDAP configuration and mapping (if security is enabled):
/portal/WebSphere/wp_profile/ConfigEngine/properties/wkplc.properties

(equivalent to v5 file : [PortalServer root]/wmm/wmmLDAPServerAttributes.xml)


---------

v6.x PORTAL DATABASES configuration:
/portal/WebSphere/wp_profile/ConfigEngine/
properties/wkplc_comp.properties


---------

Hope this will help you....