IBM Support

Pre-deployed portlets or applications not found during Portal migration

Troubleshooting


Problem

After you run the IBM WebSphere Portal pre-upgrade task to export content from an earlier version, the allout.xml file may contain messages pertaining to pre-deployed portlets or applications for which you must adjust the URL.

Symptom

Messages with the ID, EJPXA0185W or EJPXA0186W, may be generated by the XML configuration interface when you migrate the Portal configuration.

Examples of these messages:

    <status element="[web-app _1_0G0ALN66VD0237T4_6O uid=pzn.author.1001]" result="warning">
    <message id="EJPXA0185W">com.ibm.wps.command.xml.XmlCommandException: EJPXA0185W: The URL file:
    // localhost/$server_root$/installableApps/pznauthorportlet.war does not point to a directory as required by predeployed portlets. You will need to adjust the URL. [web-app _1_0G0ALN66VD0237T4_6O uid=pzn.author.1001]</message></status>

    <status element="[web-app _1_0G0ALN66VD0237T4_FL uid=ilwwcm-pdmdoclist.war.webmod]" result="warning">
    <message id="EJPXA0186W">com.ibm.wps.command.xml.XmlCommandException: EJPXA0186W: The URL file:// localhost/$server_root$/install ableApps/ilwwcm-pdmdoclist.war does not point to a file. You will need to adjust the URL. [web-app _1_0G0ALN66VD0237T4_FL uid=ilwwcm-pdm doclist.war.webmod]</message></status>
Messages with the ID, EJPXA0185W, refer to pre-deployed portlets that are not located in the directory where WebSphere Portal expects to find them. You must resolve these messages (as described below) before you can continue migration.

Messages with the ID, EJPXA0186W, refer to deployed portlets and can be ignored because WebSphere Portal is able to extract the deployed portlet without the associated .war file being in the specified location.

Cause

WebSphere Portal generates messages similar to those shown above when you attempt to migrate pre-deployed portlets or applications that are not located in the default directory where WebSphere Portal expects to find them.

This can occur if in the earlier Portal server, you deployed portlets or applications directly in the WebSphere Application Server to a non-standard location (instead of using either the WebSphere Portal administrative portlets or XML Configuration Interface to deploy to the default location for the portal server).

Resolving The Problem

To ensure proper migration of pre-deployed portlets or applications that were deployed to a non-standard location in the earlier Portal server, complete the steps below before you run the portal-post-upgrade task to import information into the new Portal server.



1. Locate the predeployedWebAppBinaryMappings.properties file in the <backupDirectory>/profiles/<profiledir>/PortalServer
/migration/work/default/wp.migration.predeployed directory.

    If you are migrating from Version 5.1:
    Locate predeployedWebAppBinaryMappings.properties in the <backupDirectory>/PortalServer/migration/work/default/
    wp.migration.predeployed directory.

    If you are migrating from Version 6.0.1.1 or later:
    Locate predeployedWebAppBinaryMappings.properties in the
    <backupDirectory>/profiles/<profiledir>/PortalServer/
    migration/work/default/wp.migration.predeployed directory.

    The predeployedWebAppBinaryMappings.properties file identifies the portlet UID and directory for each predeployed portlet or application. WebSphere Portal writes these UIDs to the PreDeployedWebAppUIDS property, creating a property named after each UID and appending binaryPath to the property name.

    For example, if a predeployed portlet has the UID my.predeployed.portlet, WebSphere Portal creates a property named my.predeployed.portlet.binaryPath.

    The UID property in the predeployedWebAppBinaryMappings.properties file looks like this:
    PreDeployedWebAppUIDS=my.predeployed.portlet
    my.predeployed.portlet.binaryPath=file://localhost/$app_install_root$/installedApps/mynodename/mypredeployed.ear/mypredeployed.war



2. Modify the path that points to the binary files for the .ear file as follows:
    a) If you used the default options to install the pre-deployed portlet to the standard location, remove the installedApps directory from the path since it is not required. For example:
    PreDeployedWebAppUIDS=my.predeployed.portlet
    my.predeployed.portlet.binaryPath=file://localhost/$app_install_root$/mynodename/mypredeployed.ear/mypredeployed.war

    b) If you installed the pre-deployed portlets to a non-standard location, specify the fully qualified path (in file URL format) in the local file system. For example:
    PreDeployedWebAppUIDS=my.predeployed.portlet
    my.predeployed.portlet.binaryPath=file://localhost/
    <custom install path>/mynodename/mypredeployed.ear/mypredeployed.war



3. Save the updated file.

[{"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Migration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
03 December 2021

UID

swg21300236

Page Feedback