PK65674: COMPOSITE APPLICATION SERIALIZATION AND INSTANTIATION FAILS WHEN PLACES GET TOO BIG OR HAVE TOO MANY INITPARAMETERS(POVS)

6.0.1.7 Download: WebSphere Portal and Web Content Manager V6.0.1, fix pack 7
6.0.1.5 Download: WebSphere Portal and Web Content Management V6.0.1 fix pack 5

APAR status

• Closed as program error.

Error description

• When creating a Lotus Quickr place, the creation process
  generates a failure message; however, the place appears in the
  place catalog.
  The resulting place, which appears to function properly for
  users, will fail to allow administrators to save the place as a
  template.
  The problem is due to the size of the original place from which
  the template was created.  Normally, the procedure for inducing
  this issue is to create a place from a default Quickr template.
  The newly created place will be referred to as "Parent Place".
  "Parent Place" is then populated with various content in the
  form of 30 components.  For example, it may be populated with
  30
  Wikis or with 15 Wikis and 15 Blogs.  Generally speaking, the
  upper limit is 30 components.  An administrator creates "Parent
  Template" from "Parent Place".  A place "Child Place" created
  from "Parent Template" will display a place creation failure
  message on initial creation; however, "Child Place" will be
  populated in the place catalog.  Furthermore, administrators
  will be unable to create templates from "Child Place".
  

Local fix

Problem summary

• When creating a Lotus Quickr place, the creation process
  generates a failure message, however, the place appears in the
  place catalog.
  The resulting place, which appears to function properly for
  users, will fail to allow administrators to save the place as a
  template.
  The problem is due to the size of the original place from which
  the template was created. Normally, the procedure for inducing
  this issue is to create a place from a default Quickr template.
  The newly created place will be referred to as "Parent Place".
  "Parent Place" is then populated with various content in the
  form of 30 components. For example, it may be populated with 30
  Wikis or with 15 Wikis and 15 Blogs. Generally speaking, the
  upper limit is 30 components. An administrator creates "Parent
  Template" from "Parent Place". A place "Child Place" created
  from "Parent Template" will display a place creation failure
  message on initial creation; however, "Child Place" will be
  populated in the place catalog. Furthermore, administrators will
  be unable to create templates from "Child Place".
  

Problem conclusion

• The iFix is preventing the broken places from being displayed
  in the catalog and thereby preventing the customer from using
  broken places. Please see also technote #1304266 which describes
  a way to enable the customer to store applications with more
  components.
  
  Failing Module(s):
     Composite Applications
  
  Affected Users:
     All users
  
  Version Information:
      Portal Version(s): 6.0.1.1
       Pre-Requisite(s):
        Co-Requisite(s): ---
  
      Portal Version(s): 6.0.1.3
       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=PK65674&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

• R60E PSY

     UP

• R60G PSY

     UP