Tuesday Sep 11, 2007

Screencast: Documentum Portlets

Documentum Portlets Documentum portlets are now available for Sun Java System Portal Server. These portlets from Documentum provide Documentum Content Management functionality, including tasks like creating, locating, viewing and managing all types of content. Documentum eRoom, Web Publisher and ECI Services portlets can now be integrated and deployed in Sun Java System Portal Server.

The following screencast demonstrates integration and deployment of these portlets in Sun Java System Portal Server -- Documentum Portlets Screencast .

Monday Jul 02, 2007

Sun Portal now supports EMC Documentum Portlets

Back in January 07, we started a project to support EMC Documentum Enterprise Content Management Portlets in Sun Java System Portal Server 7.1. The portlets in Content Management and Web Publisher categories are pre-packaged Web Development Kit (WDK) components that include Java server pages,  Java classes, and XML files. These portlets  provide core content management and content services for creating, viewing, submitting and publishing various types of content.

eRoom portlets provide a dashboard view into EMC Documentum eRoom and offer the ability to manage multiple project eRooms. 

ECI Services portlet is built using ECI Services framework with adapters to search various repositories, databases and and web sites.

All these portlets are  JSR 168 standard based and customizable. For further details, please visit this link Sun Java System Portal Server Documentum Portlets 

Thursday Jun 07, 2007

SPEAK OUT! Portlets and Web Services

When bringing an application into a portal, when is a Web service better than an old-school portlet? That's not a rhetorical question  - what do you think?

 The answer will probably vary, based on the type of application you want to expose. My work has been primarily with commercial ISV's (Citrix, Elluminate, Documentum, etc.), maintaining our Core Portal Ecosystem. Originally, every portlet project was 100% custom. Most ISV's had decent API's, but it was still a lot of manual work (not to mention constant business negotiations, measurement, etc.). The rapid adoption of the Java Portlet Specification (JSR 168) standard helped (by providing a container, consistent authentication mechanisms, etc.), as did WSRP's enabling of Web service consumption. Better still, many ISV's began publishing and supporting portlet sets of their own, taking over about 80% of the portlet development work.  However, even with these advances, code to support portal-specific features (e.g. single sign on and, in our portal's case, Secure Remote Access) was still done largely by hand.

This Google spellcheck portlet is actually a Web service.

This Google spellcheck portlet started with a Web Service. To learn how to build this yourself, visit the tutorial

Clearly, Web services are the future for commercial ISV portlets. Some are already phasing out portlets in favor of publishing Web services (Interwoven and Business Objects come to mind). SIDE NOTE: I've been advocating the creation of a core series of reusable infrastructure services (e.g. a single sign-on service, a secure remote access service) to glom\* together with the ISV services as our model for supporting commercial portlets going forward. Some of our gifted engineers are validating the concept as we  speak. What's your take? 

Also, almost half of the proposed features in the upcoming Portlet Specification 2.0 address WSRP alignment. So where does that leave the portlet as we once knew it? Is it strictly to be used for obscure, one-off tasks or ...?

Which method do you prefer in which circumstances? Please share your ideas and experiences.

Thanks-
Kim Buck

 

PS - If you're interested in portals, you're probably interested in SOA. For a glimpse into Sun's SOA ISV community, feel free to visit my SOA Solar System blog. Most of the content is business oriented vs. technical, but it's a good place to learn about  how SOA vendors - from established platform players to innovative startups - are shaking up that space.

 

\*glom - to mash, to moosh, to adjoin with reckless abandon (trademark pending) ; )

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