Deployment Example: Deploying and Customizing the Documentum Portlet

ProcedureKnown Issue for Web Publisher Portlet

It has been observed that single-sign-on does not work for non Documentum admin users once Web Publisher Portlet is deployed on the Sun Java System Portal Server. In addition to authentication changes described in Configuring Portlet Authentication and User Principal Authentication, perform the following steps.

  1. Download the WPPortlets_BUG.zip file and unzip it.


    Note –

    Please open a Sun Support case or ticket to obtain the WPPortlets_BUG.zip file.


  2. In the machine where you have deployed your WPP portlets, make a backup copy of your current web.xml file in the /var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/wpportlets/WEB-INF/ directory and replace it with the web.xml from the WPPortlets_BUG.zip file.


    Note –

    If you made changes to the web.xml file in the /var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/wpportlets/WEB-INF/ directory, you have to re-do it after copying the web.xml from the WPPortlets_BUG.zip file.


  3. In the machine where you have deployed your WPP portelets, make a backup copy of TicketedRedirect.class in the /var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/wpportlets/WEB-INF/classes/com/documentum/wpportlets/library/ticketedredirect directory and replace it with TicketedRedirect.class file from the WPPortlets_BUG.zip file.

  4. Restart the Sun Java System Application Server.

  5. Test WPP portlets by logging as an user who is not the DCTM Admin user.