A JSP - Quicker tool for debugging your WebSphere Portal issues
Deepak Gupta_ISL 060001TG9W Visits (992)
When debugging the IBM WebSphere Portal issues server logs, browsers traces and other ways are certainly helpful to find out the cause. A must gather for each and every component in IBM WebSphere Portal is available to dig through the traces. But sometimes you want specific information because :
Many time you modifies the applications to include "SYSTEM OUTs." but you need to bear hassle of creating the portlet, deployment, re-deployment and server start and stop.
A quicker solution to overcome all of these challenges is to place the 'required code' in a JSP file and then run the jsp file in your Portal. This approach offers the benefits of testing and debugging your module quickly and works on all supported versions of IBM WebSphere Portal.
Now, question comes, where is to place this JSP file and execute the code. There are following two possible places where you can place and run your debugging module.
Open Picker portlet is not avaible OOTB, you can deploy it using war file available at location : Port
Once you deploy the portlet, you will get a file named index.jsp at location : wp_p
You can either append your content to this jsp file or replace with your file named index.jsp.
Now create a page under HOME label and call it 'JSP TestPage' and add either 'Open Picker portlet' - approach #1 or 'Information portlet' - approach #2.
For approach #2, i.e. for Information portlet you need to perform following additional steps:
i)Click portlet menu drop down arrow in the top-right corner and then click 'Edit Shared Settings'.
Let's take some modules which can be debugged using JSP if is there any issue in them.
1)User & Groups and their attributes: User/Group is mostly consumed by every application in IBM WebSphere Portal and many times we face issue where either valid users/groups or their attributes do not exists in system and fails your module. In this case we can write code for retrieving user/group and corresponding attributes on JSP and can confirm the issue.
<%@ page impo
2) Person Card: Person card in WebSphere Portal is used to get the detail of any live name. It is widely integrated into IBM WebSphere Portal and various ways exists to integrate it. The Person card consumes PUMA REST APIs for getting the information from LDAP configured with IBM WebSphere Portal. If this card doesn't work then following code can be used to confirm whether
<%@ taglib uri=
If you observe the page, you will either get the working card or cause of failure.
Similarly you can add your code to JSP and debug the issue more easily and quickly as compared to standard approach.