PM83434: Parameter WpsPersonalizedHome and WpsDefaultHome not honored when creating new server configuration

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to use parameters WpsPersonalizedHome and
    WpsDefaultHome are not honored when creating new WebSphere
    Portal server configuration.
    
    Problem:
    
    1) Use Rational Application Developer 7.5.5.5 Interim Fix 001
    and WebSphere Portal 6.1.5
    
    2) Change the parameter Portal Context Root, Default Portal Home
    and Personalized Portal Home as described in the Portal
    infocenter:
    
    http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?to
    pic=/com.ibm.wp.ent.doc_v615/config/cfg_intr.html
    
    For example,
    Portal Context Root set from wps to portal
    Default Portal Home set from portal to public
    Personalized Portal Home set from myportal to personal
    
    3) Start a new workspace
    
    Actual Result:
    Correct Portal Context Root portal is recognized
    Old Default Portal Home portal and Personalized Portal Home
    myportal are recognized
    
    Expected Result:
    Correct Portal Context Root wps, Default Portal Home public and
    Personalized Portal Home personal are recognized
    
    Local fix:
    
    Adjust the parameter Default Portal Home and Personalized Portal
    Home after creating a new Server configuration
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is happening because wkplc.properties file is
    not the right file to look for the WpsDefaultHome and
    WpsPersonalizedHome properties. The right properties file
    for these properties is "wkplc_comp.properties" typical
    location of this file in portal installation is
    ?wp_profile?\ConfigEngine\properties.
    

Problem conclusion

  • WpsDefaultHome and WpsPersonalizedHome properties values
    will be read from the wkplc_comp.properties file.
    
    The fix for this APAR is included in Rational Application
    Developer v9.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83434

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    755

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-22

  • Closed date

    2013-06-25

  • Last modified date

    2013-06-25

  • 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

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R755 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Application Developer for WebSphere Software

Software version:

7.5.5

Reference #:

PM83434

Modified date:

2013-06-25

Translate my page

Machine Translation

Content navigation