IBM Support

PM05353: CANNOT RECREATE URL MAPPINGS IN VIRTUAL PORTAL WITH HOST NAME CO NFIGURATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a virtual portal is created with a hostname but without an
    identifying url context, it is not possible to create new URL
    mappings and assign them to portal pages through the URL
    mapping admin portlet.
    
    The following error will be shown:
    EJPEC0622E: A resource of a virtual portal can only be mapped
    to a context of the same virtual portal.
    
    This APAR modifies the virtual portal creation process to always
    
    
    generate a URL mapping context, if no context name has been
    provided. So this APAR only addresses the issue for newly
    created virtual portals. Existing portals will have to be
    recreated to fix the issue (see workaround description).
    
    Detailed exception shown in URL Mapping portlet is:
    
    EJPAY0050E: Error occurred when assigning the mapping for
    context testvp2.
    com.ibm.portal.WpsException: EJPAY0050E: Error occurred when
    assigning the mapping for context testvp2.
    at
    com.ibm.wps.portlets.urlmapping.UrlMapping.setStatusMessage(UrlM
    
    apping.java:2216)
    ...
    EJPEC0622E: A resource of a virtual portal can only be mapped
    to a context of the same virtual portal.
    com.ibm.wps.command.mappingurl.MappingURLCommandException:
    EJPEC0622E: A resource of a virtual portal can only be mapped
    to a context of the same virtual portal.
    at
    com.ibm.wps.command.mappingurl.AbstractMappingURLCommand.throwMa
    
    ppingURLCommandException(AbstractMappingURLCommand.java:302)
    at
    com.ibm.wps.command.mappingurl.AssignPortalURLCommand.execute(As
    
    signPortalURLCommand.java:188)
    at
    com.ibm.wps.portlets.urlmapping.UrlMapping.actionEditMapping(Url
    
    Mapping.java:1205)
    

Local fix

  • export the vp through XMLAccess; delete the vp and run the Clean
    
    
    
    
    up Daemon Task; recreate vp with some VP context in addition to
    the hostname (use config engine task create-virtual-portal to cr
    
    
    
    eate an empty VP!) and reimport the contents
    

Problem summary

  • If a virtual portal is created with a hostname but without an
    identifying url context, it is not possible to create new URL
    mappings and assign them to portal pages through the URL Mapping
    admin portlet.
    
    The following error will be shown:
    EJPEC0622E: A resource of a virtual portal can only be mapped to
    a context of the same virtual portal.
    

Problem conclusion

  • This APAR modifies the virtual portal creation process to always
    generate a URL mapping context, if no context name has been
    provided. So this APAR only addresses the issue for newly
    created virtual portals. Existing portals will have to be
    recreated to fix the issue:
    
        - export the vp through XMLAccess;
        - delete the vp and run the Clean up Daemon Task;
        - recreate vp with some VP context in addition to the
    hostname (use config engine task create-virtual-portal to create
    an empty VP!)
        - reimport the contents
    
    Manual Steps:
       None
    
    Failing Module(s):
       Virtual portals
    
    Affected Users:
       All users
    
    Version Information:
        Portal Version(s): 6.1.0.2
         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=PM05353&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 number

    PM05353

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    61B

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-19

  • Closed date

    2010-02-04

  • Last modified date

    2010-02-04

  • 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

  • R61B PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 February 2010