One way to do this is to create a portlet service that accesses the Domino database (or any other back-end application/data store for that matter) so that the specifics of accessing Domino applications are not embedded in the portlet code. Portlet services are shared by all portlets and are, therefore, a great place to implement logic (and caching) that is shared by multiple portlets.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
I just finished editing an article for the premier edition of The Sphere (WebSphere version of the highly respected The View magazine), which describes exactly how to implement a portlet service that accesses a Domino database.
Dig Deeper on IBM WebSphere
Related Q&A from Tony Higham
Can I install WPS 5.1 on an existing WAS 6 Notes/Domino system? I have a server that already has WAS6 Notes/Domino running. I also want to install ... Continue Reading
For a WebSphere Portal 5.1 installation, are there any caveats to using RAD 6 and WAS 6 versus WSAD 5 and WAS 5? Continue Reading
What is the recommended logical drive configuration for a WebSphere Portal installation on a Windows machine (i.e., C: OS, D: WPS and WAS)? Also, ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.