WebSphere Portal: Export Page error

I am very surprised to see that more people have not run into this issue in WebSphere 6.0.1.6:

Scenario: You go to export a page from the Portal Console, and you receive a 403 Forbidden page, instead of the exported file. I then went through the logs and discovered the error:

[10/7/09 14:04:53:935 CDT] 00000062 WebCollaborat A SECJ0129E: Authorization failed for scconlo while invoking GET on default_host:/wps/PA_1_NO2UF4I1186E1026H4BLVI00L6/exportServlet, Authorization failed, Not granted any of the required roles: exportPortalPagesRole
[10/7/09 14:05:27:796 CDT] 00000062 WebCollaborat A SECJ0129E: Authorization failed for scconlo while invoking GET on default_host:/wps/PA_1_NO2UF4I1186E1026H4BLVI00L6/exportServlet, Authorization failed, Not granted any of the required roles: exportPortalPagesRole

However, I do a Google Search for “websphere portal 403 exportPortalPagesRole” (http://lmgtfy.com/?q=websphere+portal+403+exportPortalPagesRole), and there is 1 result returned: http://dev.binarysoul.net/2009/08/11/2-bugs-in-websphere-portal-6-0-1-6-fix-pack/

This is a great post by “Jonathan”, which details the problem and the solution.

Check it out if you have the aforementioned issue.

WebSphere Portal: log4j to SystemOut.log

A requirement came across my desk to make the log4j output be directed to the SystemOut.log file instead of the logfile of choice configured within log4j. (See my previous post on WebSphere Portal & Log4j) I am still pretty knew to WebSphere and where output goes and what is considered the “console” log file, but I thought I would just start by configuring my log4j.xml file to output all data to the console instead of the log file I originally configured.

Luckily this update worked like a charm. That is the first time something worked as expected with Portal, and will probably be the last.