Monday, October 3, 2011

Mobile Portal Accelerator

Just got a chance to evaluate Mobile Portal Accelerator a accelerator provided by IBM to ease development of portlets for mobile devices. It sits on top of WebSphere Portal Server with a toolkit for RAD or RSA to develop mobile portlets. It extends the capabilities of WebSPhere Portal Server to limitless of mobile devices.
Some unique points of MPA are listed below:


  • Supports 9000 mobile devices. include Android, Apple iPhone, Apple iPad, RIM BlackBerry, Microsoft Windows Mobile and Nokia Symbian-based devices.

  • Supports almost all the browsers supported by WebSphere Portal. Support for IE 6.0 +, Mozilla Firefox 3.0+, Apple Safari and many more.

  • Support for JSR 168 and 286 portlet specification.

  • A uniquly provided subscription of MPA update will provide support for all the new devices introduced in the market.

So if anyone interesed ot looking for a tool to develop mobile portlets using WebSphere Portal environment can surely go for this accelerator. It requires WebSphere Portal, WAS and RAD or RSA. Evaluation versions are already out for MPA 6.0 and 7.0. So you can download then and start evaluating the software. Sample portlets are alredy provided. I have the toolkit evaluation version with me will try to attach them for the benefit.













Friday, May 21, 2010

How to enable WCM on local development environment!!!

To enable WCM on local development environment below are the steps:

1) Stop portal server
2) From command prompt go to Portal_Home/config.
In my system Portal_Home is C:\Program Files\IBM\WebSphere\PortalServer
3) Run Command WPSconfig.bat configure-wcm-authoring -DPortalAdminPwd=password.

Sunday, April 25, 2010

Test LOT-959: IBM WebSphere Portal 6.1 Application Development

Objectives

Architecting a Portal Solution

1. Demonstrate familiarity WebSphere Portal Web 2.0 features

2. Demonstrate knowledge of WebSphere Portal Platform features

3. Identify portal dependencies on existing software

4. Identify supported portlet frameworks

5. Identifying scope for custom portlets

6. Know the authentication levels provided by WebSphere Portal

7. Understand how portal features and portlets use user identity to personalize

8. Understand patterns and methods for application integration with WebSphere Portal

9. Understand portal page aggregation modes

10. Use out-of-the-box portlets

Install, Setup and Configuration of a Developer Environment

1. Compile, packaging, and deploying portal artifacts using Rational Application Developer

2. Configuring Rational Application Developer for remote testing and debugging with WebSphere Portal

3. Create portlets in Rational Application Developer and WebSphere Portlet Factory

4. Creating Portal projects in Rational Application Developer

5. Diagnose problems with development environment installation

6. Identify Software Requirements

7. Optimize development environment

8. Understand software prerequisites (including compatibility questions)

Portlet Development

1. Create cooperative portlets using Click-2-Action and Property Broker

2. Demonstrate knowledge of core Java Portlet Objects

3. Demonstrate the differences between, events, render parameters, public render parameter, and scoped attributes; request, session, shared session, and application scope.

4. Describe the portlet life cycle for JSR-168 and JSR-286

5. Effectively use JSP and JSTL to render portlet markup

6. Have knowledge of WSRP for JSR-168 and JSR-286 portlets

7. Identify supported portlet modes and custom portlet modes

8. Implement portlet actions and events with Java 5 annotations

9. Understand portlet descriptor files for each portlet type and utilize WebSphere Portal extend features

10. Understand WebSphere Portal client side portlet API

11. Use AJAX to update state and trigger actions with JSR-286 portlets

12. Use Remember Me API to provide anonymous portlet content personalization

13. Utilize client profile information (JSR-188)

14. Utilize of standard portlet cascading style-sheet classes

Theme Development

1. Demonstrate understanding of Theme Extensions

2. Develop custom themes, skins and screens

3. Identify Portal and Drag-and-Drop JSP tags

4. Implement Client Side Aggregation

5. Implementing Portal Navigation

6. Portal Cascading Style-sheet classes

7. Using Theme Customizer Portlet to modify a theme

8. Using theme policies and custom page settings

Portal Frameworks and Portlet Services

1. Creating a custom Portlet Service

2. Develop Login, Logout, and Session validation filters

3. Parsing ATOM Feeds

4. Understand key Service Providers (SPI) and Application Programing Interfaces (API)

1. Login Service SPI

2. Portal User Management SPI

3. Portal Write Model SPI

4. Property Broker SPI

5. Resource Addressability Framework (SPI)

6. Step Up Authentication SPI

5. Use REST protocol to access SPI's

Testing, Debugging and Performance Monitoring of Portlets

1. Debug a portlet on a local server

2. Debug a portlet using WebSphere Portal remote

3. Effective use of logging

4. Running code profiling in Rational Application Developer

5. Troubleshoot portlet applications

6. Using portlet PMI statics

Additional Development Concepts

1. Assembling Composite Application Templates

2. Collaboration API

3. Creating custom portal search interfaces

4. Developing Personalization Resources

5. Have knowledge of Portlet Bridge Frameworks; Struts, JavaServer Faces, etc.

6. Search the Business Solutions catalog

7. Using and extending the Credential Vault

8. Using Web Content Management API's

9. Writing Personalization and Visibility Rules

Tuesday, March 16, 2010

Working with Locks in IBM Lotus Web Content Management !!!

As authors contribute content, they might find items that are locked by other
users, because either they are being edited by another user or a draft item has been created.

When a user is editing an item, the item is locked to other users. This means other users
are unable to edit the item until the current user closes the item that they are editing. A
lock symbol is displayed against items that are currently locked.
Administrators can lock and unlock items by selecting them and clicking either the Lock
or Unlock button.
The locking of sites, site areas, taxonomies, and categories is configurable and
is not enabled by default. When locking is enabled, authors cannot create any children
under the locked site or site area. This only applies to items that are located one level
below a locked parent.
When a new draft of a published item is created, a check mark is displayed next to the
published item indicating that no other user can create a draft until the current draft
progresses through a workflow and its state changes to published.

Library Versioning in IBM Lotus Web Content Management!!!!

With library versioning, administrators can group the items within a library by label or
date and time.
If something goes wrong, the administrators can go back to a previous version,
selected by date or label.
A library cannot be restored while any items are currently locked or checked out
by users. Before restoring a library, you must view all published items in a library and
unlock any items marked as checked out or locked.