PK69890: COMPONENT REMOVED IF PORTLET FROM DERIVED PAGE DELETED VIA XMLAC CESS

6.1.0.1 Download: WebSphere Portal and Web Content Management V6.1, fix pack 1
6.1.0.2 Download: WebSphere Portal and Web Content Management V6.1, fix pack 2
6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack
6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1
6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5
6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6

APAR status

• Closed as program error.

Error description

• Component removed if portlet from derived page deleted via
  XMLAccess.
  

Local fix

Problem summary

• If a portlet instance on a derived page, that replaces a portlet
  instance on the parent page is removed using XMLAccess,   not
  only the portlet instance, but also the corresponding component
  is removed. This leads to an appearance of the parents page
  portlet instance on the derived page.
  
  The problem occurs if on a derived page a portlet's settings are
  first changed and it is later removed.
  
     Example:
  
     Derived page before XMLAccess script import:
  
     ..
  
             <content-node action="update" ...
  create-type="explicit" derivation-parentref=".." ..>
  
                 ..
  
                 <component action="update" ..  shadowref=".." ..>
  
                     <portletinstance action="update" domain="rel"
  objectid="5_3A7U7FH20GFD402RULG64710G1" ..>
  
                       ..
  
                     </portletinstance>
  
                 </component>
  
             </content-node>
  
     ..
  
     XMLAccess script imported:
  
     ..
  
             <content-node action="update" ..>
  
                 <component action="update" ..>
  
                     <portletinstance action="delete" domain="rel"
  objectid="5_3A7U7FH20GFD402RULG64710G1"/>
  
                 </component>
  
             </content-node>
  
     ..
  
     Page after XMLAccess script import with incorrect state
  (component is missing):
  
     ..
  
             <content-node action="update" ...
  create-type="explicit" derivation-parentref=".." ..>
  
                 ..
  
             </content-node>
  
     ..
  
     Page after XMLAccess script import as intended (component
  still exists, only portletinstance tag missing):
  
     ..
  
             <content-node action="update" ...
  create-type="explicit" derivation-parentref=".." ..>
  
                 ..
  
                 <component action="update" ..  shadowref=".." ..
  />
  
             </content-node>
  
     ..
  

Problem conclusion

• Deletion of portlet instance on a derived page will not
  automatically remove corresponding component.
  
  
  Failing Module(s):
     XML Access
  
  Affected Users:
     XML Acces Users
  
  Version Information:
      Portal Version(s): 6.0.1.1
       Pre-Requisite(s):
        Co-Requisite(s): ---
  
  Platform Specific:
     This fix applies to all platforms.
  
  A fix is available from Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PK69890&productid=WebSphere%20Portal&brandid=5
  
  You may need to type or paste the complete address into your Web
  browser.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R60A PSY

     UP

• R60E PSY

     UP

• R60G PSY

     UP

• R610 PSY

     UP