Developing Portlets using JSR 168 and WebSphere Portal V5.1, a Best Practice Approach

[This article is sponsored by Peningo Systems, Inc., a provider of WebSphere Consulting and Staffing Services on a nationwide basis. For more information on Peningo Systems, please go to the Peningo WebSphere Consultants page ]

IBM has release an article “Best practices for developing portlets using JSR 168 and WebSphere Portal V5.1”. As more and more firms are employing the JRS 168 Portlets standards, this article is an invaluable resource for the WebSphere Portal Developer. This article will provide the developer with a Best Practices approach to portlets development to conform to the JRS 168 standards while utilizing the WebSphere Portlet infrastructure. The best use of this article is as a checklist during design and code reviews to help promote consistent and quality Portlet implementations.

To view the article, please click the link below:

To learn more regarding JSR 168, please go to the following link:

If you are an “End Client” looking for a WebSphere Portal developer provider to support your Portal Applications, Peningo Systems provides Consultants with expertise in many areas including:

WebSphere Portal

WebSphere Commerce

WebSphere Eclipse Development

WebSphere MQ

Tivoli Identity Manager

Tivoli Access Manager

System Security Architecture

DB2 – UDB,



Peregrine / HP Openview AssetCenter and ServiceCenter

J2EE based systems architecture and development.

To see Peningo Systems areas of expertise, please go to the Peningo Technical Areas page or go to the Peningo WebSphere Consultants page.

To see Peningo’s other Blogs please go to

Peningo’s Blog

The Peningo Opinion Blog

[Slashdot] [Digg] [Reddit] [] [Facebook] [Technorati] [Google] [StumbleUpon]

About Edward Pellon

About Peningo Systems ( ) Peningo Systems and it founders have been involved in IT Consulting for over 30 years. Our goal is to support the individual IT Consultant by providing an avenue for them to be in contact directly to the end client. By doing this we reduce the many layers and tiers of organizations that are involved with placement of an IT Consultant. By reducing these layers and tiers, cost can be significantly reduced to the end client, while still providing the room for the Consultant to increase their revenues. Peningo is a for profit organization. We have decided to earn our “keep” by advocating, establishing and supporting a “market place” where the IT consultant and the “end client” may function without the interference of tiers of “prestigious” companies that bring to the consulting assignment excessive Markups and very little else. At Peningo we feel that the IT Consultant should be paid adequate rates commensurate with their skills and the personal sacrifice inherent in the life of an IT consultant. These allows us to field capable, motivated consultants that will contribute successfully to the “end client’s” systems development and implementation, while attracting to the IT industry new talent that otherwise would go to more lucrative pursuits. With the elimination of the “prestigious ones” there will be costs savings that will allow for the consultant to be paid a higher rate and for the client to reduce its costs. Both objectives represents Peningo’s Mission.
This entry was posted in IT Outsourcing, Offshoring, Tivoli, Tivoli Consulting, WebSphere, WebSphere Commerce, WebSphere Consulting, WebSphere Portal. Bookmark the permalink.

Comments are closed.