IBM Web Experience Factory wiki
WebSphere Portlet Factory
Best Practices for WebSphere Dashboard Framework
> WebSphere Dashboard Framework - Best practices for WebSphere Application Server applications
About the Original Author
Articles authored: 24
Articles edited: 57
Recent articles by this author
Security bulletins to supplement product documentation
Developing multi-channel and hybrid mobile web sites
You can create multi-channel and hybrid mobile web sites using IBM WebSphere Portal, IBM Web Experience Factory, and IBM Worklight.
Resources for mobile and multi-channel application development
Use the links below to learn more about using IBM Web Experience Factory to rapidly develop custom portlets and web applications that are optimized for mobile and desktop devices.
WebSphere Dashboard Framework - Announcing releases 6.1.5 and 184.108.40.206
WebSphere Dashboard Framework 6.1.5 and the 220.127.116.11 fixpack are now available
WebSphere Dashboard Framework - Creating custom maps
You can create custom maps for WebSphere Dashboard Framework 6.1.5 with the IBM ILOG JViews Map Builder.
WebSphere Dashboard Framework - Best practices for WebSphere Application Server applications
| Edited by
January 5, 2010
No abstract provided.
The WebSphere Application Server sample application provided with WebSphere Dashboard Framework demonstrates best practices for developing dashboards for any platform. It also incorporates these techniques for developing dashboards specifically for WebSphere Application Server.
Use the Model Container builder to simulate a portlet.
Use Model Container builder to wrap a single portlet model to a special "portlet" model for WebSphere Application Server.
Use Model Container builders to position "portlets" at a specified page location.
Use templates for design elements.
Create a portlet HTML template for all the portlets' user interfaces and extract styles to a CSS file.
Create a page HTML template for a page's design and reserve locations for portlet insertion.
Add security to pages.
Add security constraints to basic units, WAS portlets, pages, which are the ingredients of a Portal-like application. This prevents non-admnistrators from accessing a portlet or page directly.
Add All-role-level security constrains to the entry page (model), which imports several basic pages.
Leverage profiling technology to implement access control on pages and contents customization.
Set up a login model.
Create your own login model or page instead of using the pre-defined one from Portlet Factory, in order to customize the login page and implement globalization.
Leverage WebSphere Application Server pre-defined login and logout actions, managing sessions with the help of WebSphere Application Server security mechanisms.
Use WebSphere Application Server user and group registries.
Leverage WebSphere Application Server user registries to manage user and group information.
Customize AccessDelegate implementation for different customization of user registries to read user and group information.
Edit the article to add or modify attachments.
Compare selected versions
Summary of changes
This version (7)
Jan 5, 2010 10:40:29 AM
Oct 30, 2008 4:44:05 PM
Copy and paste this wiki markup to link to this article from another article in this wiki.
IBM Collaboration Solutions wikis
IBM Software support
IBMSocialBizUX on Twitter
IBMSocialBizUX on Facebook
Lotus product forums
IBM Social Business UX blog
The Social Lounge
Forgot user name/password
Wiki design feedback
About the wiki