Portal Server Logging - Part 1
If you deploy a portlet and the deployment fails, how to debug?
If
the deployment is successful, but the content does not show up on
portal desktop, how to debug?
The
Sun Java System Portal Server 7.x has powerful logging features. It
uses JSR 47 logging. In this section(Part 1) i will explain how to
debug the above two scenarios. In the next part(Part 2) i will explain more powerful
features of portal server logging.
A. If the portlet
deployment fails, you need to check the logs from PAS(Portal
Administration Server). These logs are in
/var/opt/SUNWportal/logs/admin/portal.0.0.log
By default the log
level is SEVERE. For debugging purposes you need to decrease the log
level. This can be done by using the CLI command
<portal-install-dir>/bin/psadmin set-logger -u amadmin -f
<password-file> -m pas -O debug.com.sun.portal -L FINEST
The
changes are applied dynamically. No need to start the cacao server.
After this change the content from the PAS will be logged at FINEST
level.
B. After the successful deployment of portlet,
if the content does not show up on Portal Desktop, you need to check
the portal logs. These logs are in
/var/opt/SUNWportal/portals/<portal-id>/logs/<instance-id>/portal.0.0.log
By
default the log
level is SEVERE. For debugging purposes you need to decrease the log
level. This can be done either by using the CLI command(psadmin) or
using Portal Server console(psconsole). The changes are applied
dynamically, no need to start the webcontainer.
Using CLI:
<portal-install-dir>/bin/psadmin
set-logger -u amadmin -f <password-file> -m portal -p
<portal-id> -i <instance-id> -O debug.com.sun.portal -L
FINEST
Using psconsole:
After login, select Logger Settings under Common Tasks
After selecting Logger Settings, select the portal, this will bring up the Common Logger Settings page
Change the log level and click "Apply".
After the change the content from the portal will be logged at level selected.
