Fix (APAR): PK34915 Status: Fix Release: 6.1.0.7,6.1.0.5,6.1.0.3,6.1.0.2,6.1.0.1,6.1 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 20209 Date: 2007-06-01 Abstract: Portlets are deployed into the portlet container provided by the WebSphere Application Server. This deployment breaks a custom application installation that provides its own portle Description/symptom of problem: PK34915 resolves the following problem: ERROR DESCRIPTION: Customers might hit exceptions when running their portal applications, for example a pluto portal, in parallel to the default portlet container provided with WebSphere Application Server v6.1. A switch enables the customer to disable their applications from accessing the WebSphere portlet container. This fix will address the requirement to have such a switch. LOCAL FIX: NONE PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server version 6.1 application developers using a framework interferring with the default portlet deployment. PROBLEM DESCRIPTION: Portlets are deployed into the portlet container provided by the WebSphere Application Server. This deployment breaks a custom application installation that provides its own portletcontainer. RECOMMENDATION: None Portlet deployment must be disabled for enabling portlets to be deployed into a custom portlet container. PROBLEM CONCLUSION: To disable portlet deployment this APAR, PK34915 is required and the portlet application must set the context parameter "com.ibm.websphere.portletcontainer.PortletDeploymentEnabled" to "false" within the web.xml. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.7. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: With PK34915 installed a portlet application can disable portlet deployment by setting the context parameter "com.ibm.websphere.portletcontainer.PortletDeploymentEnabled" to "false" within the web.xml: This is to be seen as a workaround for WAS 6.1. With next release the solution is expected to change, as this fix is based on service stream limitations and com.ibm.websphere.portletcontainer.PortletDeploymentEnabled false The disable flag is subject to change with next release, as this way is a workaround for the WebSphere Application Server 6.1 service stream.