Portlet

Log files are redirected if the display name is null. (#6319289)

Description:

In case the display name is null in web.xml, the logs from portlet web application will be directed to the default logger for portlet web application.

Templates loaded by shared events and tasks not accessible from psconsole. (#6350620)

Description:

SSOAdapterTemplates added using amadmin do not appear in psconsole.

Solution:

Stop and restart the CACAO server using the following command:

/opt/SUNWcacao/bin/cacaoadm stop; /opt/SUNWcacao/bin/cacaoadm start

Portal desktop does not close the Proxylet console. (#6241355)

Description:

Even after you log out of the portal console, the Proxylet continues to run.

Extend Session attribute in Netlet does not work. (#6252410)

Description:

The portal desktop session times out even though the Netlet session is active.

Solution:

You need to log out of the portal desktop and log in again for the updated value of the Extend Session attribute to be reflected in the session.

Netlet is not loaded when portal is launched through Proxylet. (#6296829)

Description:

Initiate a portal session through Proxylet. The URL of the browser from where the Proxylet is launched is rewritten with portal desktop URL and the portal desktop is launched. When you launch the Netlet, the browser displays “Netlet is loading” message but fails to launch.

Custom portlets do not deploy in WebSphere from psconsole. (#6341228)

Description:

When you deploy a portlet from psconsole, you see a successfully deployed message. But, in the WebSphere administration console the portlet war file is not deployed. In the portal desktop, the Portlet Samples tab displays an error message.

Solution:

To deploy portlets in WebSphere, perform the following steps:

1. Run deploy portlet command from psconsole or psadmin.

2. Go to WebSphere administration console http://<machine>:7090/admin and start the deployed portlet.