WDK for Portlets/Documentum Portlets Product Overview Jeff Spitulnik Sr. Product Manager – Portal...
-
Upload
dylan-gregory -
Category
Documents
-
view
218 -
download
0
Transcript of WDK for Portlets/Documentum Portlets Product Overview Jeff Spitulnik Sr. Product Manager – Portal...
WDK for Portlets/Documentum Portlets Product Overview
Jeff SpitulnikSr. Product Manager –Portal Integration & Search Products
20 May 2004 - MWDUG
Agenda
Very Brief Portal Technology Overview WDK for Portlets/Documentum Portlets Product Functionality Overview Demo! Product Roadmap Additional Resources
Optional areas… Product Architecture Overview In-depth Product Architecture Troubleshooting and Debugging Customization
Very Brief Portal Technology Background
Portal Architecture
Portal
A “specialized” web application that provides value-added services such as
Personalization Single Sign-On Content aggregation from various sources Secure search facilities Localization of content
A Portal “page” represents a complete HTML document consisting of several Portlet components
Key Portal Functions
Provides security and user management Single sign-on/Authentication Authorization and entitlements
Provides information aggregation and integration
Filtering Indexing Classification Automation Syndication Unified enterprise search
Enables customization of pages by users
Enables personalization (based on roles, profiles, context)
Provides application integration Single look and feel Application interoperability Process integration
Administrators can either lock or open up areas of the page for end users to customize
Unifies (or interconnects) enterprise infrastructure
Multiple repositories Multiple communities Single source collaboration,
authoring, & communication Multiple enterprise applications
Portlet Principle
Each Portlet is a separate application Developed independently Aggregated on a portal page Can be placed anywhere on the
page Portlets have modes and window
states Portlets can support multiple devices
Phones, Organizers, Voice Unique views for each device Business logic can be shared
Portlets are portal context aware Per-portlet instance data stored by
portal Per-portlet settings managed by
portal Can contain portal info, e.g. user
profile information, look and feel
Unified Infrastructure
.com site Support sitePartner site Corporate site
CustomersPartners Employees
Enterprise ApplicationsEnterprise Applications
Marketing Content & Order Management Call Tracking SystemPartner
content ERP Systems
Content
Managem
entC
ontent M
anagement
Portal FrameworkPortal Framework
Ana
lyticsA
nalytics
Kno
wled
geM
anagement
Kno
wled
geM
anagement
Com
merce
Managem
entC
omm
erceM
anagement
XR
MX
RM
Sou
rcing/
Procurem
ent
Sou
rcing/
Procurem
ent
Collaboratio
nC
ollaboration
Sup
ply Chain
Sup
ply Chain
Security
Security
Unified Content InfrastructureUnified Content Infrastructure
Documentum ECM for Portals: A Unified Content Infrastructure
1. Facilitates the content lifecycle2. Enables content access3. Contextualizes content management application functionality
Examples of Documentum CM Functionality Available through the Portal
Template-based content publishing Taxonomy-based content categorization and access Enterprise search, federated search – full-text and content
attribute criteria Contribution, check-in, check-out, lifecycle management, version
control, etc of content objects The ability to act on workflow tasks, view notification messages,
and check the status of active workflow processes A convenient location where the content most critical to daily
activities can be accessed or tracked on a subscription basis
Product Overview
Web Publisher Portlet Submit Content Portlet Published Content
Documentum Portlets & Web Publisher Portlets
Search Inbox Cabinets Home Cabinet Subscriptions Workflows Browse Categories Recent Files
Support for: Login, Saved Credentials, User
Preferences Single Sign On Branding/Theme
These portlets can be deployed to any portal server implementing the JSR 168 portlet API specification.
These portlets can be deployed to any portal server implementing the JSR 168 portlet API specification.Developer/Administrators can use the full WDK framework for configuration and customization.
Developer/Administrators can use the full WDK framework for configuration and customization.
Any currently available or custom built WDK component can easily be deployed as a portlet.
Any currently available or custom built WDK component can easily be deployed as a portlet.
WDK for Portlets Overview – Components
Main common components advsearchcontainer categorydrilldown drilldown homecabinet_drilldown Inboxdrilldown myobjects_drilldown subscriptions_drilldown workflowstatusdrilldown
New portlet specific components, for example: accessibleactions general_preferences, component_preference, portal_preferences saved_credentials portal_login
WDK for Portlets Overview
The Web Development Kit for Portlets installer installs DFC, WDK components and configuration files, portlet definition files, portlet configuration files, portlet help files, custom classes, jar files, and tag libraries in a JSR-168 compliant portal server
The WDK runtime for WDK for Portlets differs somewhat from the runtime for standalone Web applications, but these differences are not exposed to customizations
The overall guidelines for configuration and customization for portal and standalone environments are the same. (I.e. Application, Controls…Many components that are called by portlets are configured in the same way as their counterparts in WDK)
JSR 168 helps standardize some integration variables. However, each portal server/app server combination is different:
• Different directory structure and install requirements
• Different preferences stores
• Variability in portlet state and session management
• Other issues…
WDK for Portlets contains an extendable environment layer to accommodate this variability.
JSR 168 helps standardize some integration variables. However, each portal server/app server combination is different:
• Different directory structure and install requirements
• Different preferences stores
• Variability in portlet state and session management
• Other issues…
WDK for Portlets contains an extendable environment layer to accommodate this variability.
WDK for Portlets Environment Class
Encapsulates an environment’s specific behavior and functionality. WDK instantiates and uses the registered environment class whenever it requires information from its environment.
You can write a single class that will run on many environments.
The environment layer is a set of classes in the com.documentum.web.env package that comprise base implementations, hooks, and interfaces.
Demo
Product Roadmap
Available Certifications
Portal Server / Application Server
BEA WebLogic Portal Server 8.1 SP2
BEA WLS 8.1 SP2
Windows 2000 / 2003Solaris 8 & 9HP UX 11iRH Linux
IBM WebSphere Portal Server 5.0.2 (with JSR 168 support)
IBM WAS 5.0.2
Windows 2000 / 2003Solaris 8 & 9AIX 5.1 & 5.2RH Linux
Sun Java System Portal 6.2
Sun JES AS 7.0 MU1
Solaris 8 & 9
Browsers Windows 2000 IE 5.5 SP2 IE 6.0 SP1 Netscape 7.0.2 & 7.1
Windows XP IE 6.0 SP1Netscape 7.0.2 & 7.1
Windows 2003 IE 6.0 SP1
Content Server Content Server 5.x Content Server 4.x (Safe Harbor)
Additional ports under consideration or being developed:
• Plumtree
• SAP
• Oracle
• Pluto
• Vignette
• PeopleSoft
• Tibco
• Others…
Additional ports under consideration or being developed:
• Plumtree
• SAP
• Oracle
• Pluto
• Vignette
• PeopleSoft
• Tibco
• Others…
Known 5.2.5 product limitations (relative to other clients)
HTTP Content Transfer Limited workflow capability, for example no Workflow Manager and limited
Workflow Reporting in the UI No treeview drill-down experience or multi-item select, as per Desktop and the
Classic view of Webtop No DRL or direct web link No Macintosh support — because of the content transfer mechanism used No checked out file location tracking No desktop authoring application integration, for example MS Office Limited end-user preferences No processing of XML during import although XML files can be imported Limited Virtual Document management functions FIGSJK language packs available in July
What’s Coming
5.2.5 SP2 – July 2004: certifications, bug fixes, performance improvements… 5.2.5 SP3 – October 2004: certifications, bug fixes
5.3 – December 2004 Usability improvements Packaging and deployability improvements Documentum Portal Solutions (e.g. CM for Process Portals, forms integration) Search Broker / Content Integration Infrastructure (askOnce) Integrated team-based collaboration functionality Multi-docbase support Improved content transfer experience WSRP implementation Improved/Additional end-user preferences controls
Also in the works… eRoom portlets askOnce portlets SharePoint integrations
Note: Availability dates may change without notice.
Resources
Documentation
Release Notes Hardware/Software requirements Known bugs (not comprehensive) Limitations Technical Notes
Install guide with content for each supported portal server BEA WLP 8.1 SP2, IBM WPS 5.0.2, Sun Java System Portal 6.2
WDK and WDK Client Development Guide Portlet-specific content throughout (e.g. authentication, branding) Many areas apply to portlets as well (e.g. NLS, actionlist) Part 3: WDK for Portlets
What is a Portlet/Portlet Architecture Environment Layer Creating Portlets Portlet Examples
Part 5: Portlet Reference Portlet Controls Portlet Components
Java docs Portlet End-User Guide and Online Help
Additional Resources
July 2004: Environment Layer Development and Extendibility Developer Guide
TBD: Portlet and Environment Layer Testing Guide Documentum Developer Site
Sample code Simple Search Portlet Documentum EDM Dashboard Adding Dynamic Data to a Portlet Logout Portlet
Component exchange Community forums Product Advisory Forum – eRoom and live events Portal vendor sites and contacts