Skip to end of metadata
Go to start of metadata

Purpose:

There is quite a lot of change in the configuration, framework and functionality of the Web Page Composer application between WPC 1.0 and WPC 2.0. EP 7.30 upwards uses WPC 2.0 and when migrating the Enterprise Portal from a lower EP version to EP 7.30 or higher, issues with the migration of the WPC Content between the two WPC application versions may be encountered. While the freedom to customize and implement the WPC scenario in such a broad spectrum of options is one of the main attractions of the application, this possibility of issues arising during the migration process is also due to the resulting complexity and unpredictability of these solutions. Should a portal migration be encountering an issue due to the migration of the WPC content, this troubleshooting guide should hopefully provide some assistance.

Overview:

Primarily, if the portal migration stops due to an issue with the migration of WPC content, it tends to be interrupted at the 'Execute Final Online Migration' step of the process. The migration will generally stop with the following error message -

Could not execute migration controllers for action migrate.online.engine.data and scenario all executed in slot online.final. Error while processing migration list /usr/sap/<SID>/put/SUM/sdt/data/mig/MIGRATIONAUSF.LST. Could not migrate some archives from migration list. Possible reason is Database is down. Check if database running Error during migration of archive /usr/sap/<SID>/put/SUM/sdt/data/mig/DEPLOYARCHIVES/com.sap.nw.wpc.mgr_mc_sda.sda which has been extracted to directory usr/sap/<SID>/put/SUM/sdt/migtool/com.sap.nw.wpc.mgr_mc_sda. Possible reason is Database is down. Check if database running Could not execute MTI process.

This error is quite generic and as such gives no indication of the exact root cause of the issue. To investigate the cause further, it is vital to check both the default.trc file generated at the time of occurrence and the WPC_Migration_Report.log files. 

Below you will find a collection of possible WPC migration issues which may be encountered during this step of the migration. Any exception generated in the WPC_Migration_Report or default.trc should be cross-referenced with these and if encountered, the appropriate solution should be applied.

Known Issues:

As advised above, the best indication of the root cause of the issue can be found in the WPC_Migration_Report.log file and the default.trc file. The first step to resolving any WPC Migration issue should be to consult these. Check both for any of the following known issues -

  • javax.naming.NameNotFoundException: Child not found: layouts at portal_content/templates/pcc [Root exception is javax.naming.NameNotFoundException: Child not found: layouts at portal_content/templates/pcc]
    This exception is generally encountered due to the invalid configuration of one or more layout template objects. The issue should be resolved by applying the steps outlined in SAP Note 2069837 - WPC Migration to EP 7.30 or higher Failing.
  • com.sap.portal.pcc.exceptions.PccDesignTimeException: Could not find object:pcd:com.sap.portal.pcc/StagingAreaId/<AreaID>
    This exception indicates that there is a problem with the area/object referred to in the 'AreaID' section of the exception. In WPC 1.0, 'sites' are stored in wpccontent/Sites/<AreaID>. During the migration this content is transferred over to pcd:com.sap.portal.pcc/StagingAreaId/<AreaID>. You should check the object referred to in the exception but check the original content so look for it in wpccontent/Sites/ - it's important to verify that the object exists and is indeed a web site and not some other type of unsupported object in this location (a likely cause of such behaviour). If <AreaID> is some type of unsupported or problematic resource it should be backed up and then removed from wpccontent/Sites/. After this, the migration should be able to proceed.
  • Error encountered migrating resource: /wpccontent/Sites/<Web_Site_Name>/Site Content/<Object_ID>
    Error encountered during processing: com.sap.portal.pcc.exceptions.PccDesignTimeException: Could not find object: pcd:com.sap.portal.pcc/StagingAreaId/<Web_Site_Name>/Site Content/<Object_ID>
    These errors can often indicate that there is an issue with the referenced object located in /wpccontent/Sites/<Web_Site_Name>/Site Content/. The 'Site Content' folder should contain only Web Resources for use within a page, it should not contain for example, web pages themselves. If the Object referred to in the exception is indeed a Web Page, it should be moved to /wpccontent/Sites/<Web_Site_Name>/Web Pages/ instead. Alternatively (or if it some other problematic object type, it can be simply deleted and the migration should then be clear to proceed. See also SAP Note 2217454 - EP: WPC Migration failing due the error ‘Error encountered migrating resource’ referencing the Site Content folder.

  • WPC Migration of content failed; nested exception is: java.lang.Exception: Inconsistent configuration found! Cannot find Web Resource Type with resource type <resource_ID>. Migration must fail.
    This would indicate that there is an issue with the configuration of the resource type referred to by the 'resource_ID' object in the exception (Ie. the resource does not contain the required configurations to be migrated successfully). In this case, the following steps should be carried out -
    1. Navigate to System Administration > System Configuration > Knowledge Management > content Management > Global services > resource types > ResourceTypes
    2. Locate <resource_ID> (the problematic resource type) and delete it
    3. Navigate to System Administration -> System Configuration -> Knowledge Management -> Content Management -> (Show Advanced Options) -> Web Page Composer (Legacy) -> Web Content Types -> Web Resource Types
    4. Locate <resource_ID> once more and switch to Edit mode
    5. Remove the "Allowed RIDS" entry and save changes
    6. Delete the edited <resource_ID> object
    7. Ensure that any content created within existing Web Pages using this web resource are also deleted
    8. Resume the migration

  • Error encountered during processing: java.lang.NullPointerException: while trying to invoke the method java.util.List.add(java.lang.Object) of a null object loaded from local variable 'aclList'
    This generally occurs due to a null property being returned for the 'ACL List' which in the context of the WPC Migration would refer to the 'Authoring Permissions'. To resolve this issue, implement the steps outlined in SAP Note 2218762 - WPC Migration Fails - null object loaded from local variable 'aclList'

  • The external connector for the following pcd object is not correct portal_content/<Path To Role>: pcdPath or extConn has invalid value 
    This exception may also be seen in conjunction with Exception occured while trying to get an area from KM with the id: pcd:com.sap.portal.pcc/StagingAreaId/<Area_ID> [EXCEPTION] com.sap.portal.pcc.pccservices.PCCException: com.sapportals.wcm.WcmException: Page resource must have type wpc_page
    This issue may arise if the External Connector property of the role(s)  connected to the WPC sites is not correct. Check this by navigating to the role referenced in the 'portal_content/<Path To Role>' section of the exception (in the PCD) and opening the role for editing. Within the relevant subfolder in the Role, locate the 'External Connector' property. The structure of this property should be of type -  wpcnavigation:///wpccontent/Sites/<Site_Name>/Site Navigation/navigation.wpc (Note - there should be 3 'forward slashes before wpccontent', no more and no less). Once the External Connector property has been corrected, resume the migration.

  • java.lang.Exception: pcd:com.sap.portal.pcc/StagingAreaId/<AreaID>/<AreaID> is not a pcd area
    This is usually caused by a Web Page being located within another Web Page. This is not supported as Web Pages can only contain Web Resources, not other Web Pages.

  • Error encountered during processing: java.lang.Exception: /wpccontent/Sites/Asia/Site Navigation/navigation.wpc is not a page nor translated pages folder object 
    This error can be triggered due to an issue with the navigation.wpc file referenced in the error message. It should be resolved by deleting the problematic Navigation.wpc file and proceeding with the migration.

  • A StackOverflow is generated and the default.trc contains multiple calls of com.sap.portal.pcc.pccshortcut.PCCShortcutService.checkCyclicDependencies
    Coding Issue and SAP Note 1849433 - 'StackOverflowError while migrating wpc content' should be applied.
  • java.lang.NullPointerException: while trying to invoke the method com.sapportals.portal.pcd.gl.IAclHandle.removeAcl(java.lang.Object) of an object loaded from local variable 'aclHandle'
    Coding Issue and the following note should be applied - SAP Note 1853367 - WPC Migration fails during permissions migration stage
  • java.lang.Exception: <pcd location of object> does not have parent role at com.sap.nw.wpc.mgr.permissionsMigrators.PermissionsMigratorPhase4.getParentRole(PermissionsMigratorPhase4.java:147)
    Coding Issue, should be resolved by applying fix as outlined in SAP Note 1713976 - WPC migration fails during setting runtime permissions stage
  • java.lang.NullPointerException: while trying to invoke the method com.sapportals.portal.pcd.gl.IAclHandle.removeAcl(java.lang.Object) of an object loaded from local variable 'aclHandle' at com.sap.nw.wpc.mgr.permissionsMigrators.PermissionsMigratorPhase3.migratePermissions(PermissionsMigratorPhase3.java:101)
    Coding Issue, should be resolved by applying fix as outlined in SAP Note 1711785 - WPC migration fails during the permissions migration stage
  • java.lang.Exception:  Object ID = <path to object in pcd>  Object Name = <display name of the object> is not a pcd area, not a folder and not a regions folder
    Coding Issue, fix is provided as outlined in SAP Note 1703531 - Migration fails during processing of regionalized pages
  • In WPC_Migration_Report - Error encountered during processing: javax.naming.InvalidNameException: Character not allowed: 'special character' in 'name of a page with special character'
    In the default.trc - javax.naming.InvalidNameException: Character not allowed: 'í' in 'ClusterLogístico'
    This is also caused by a coding issue. Apply SAP Note 1703578 - WPC migration stops during connection creation

 Related Notes

 

SAP Note 1849433 - StackOverflowError while migrating wpc content

SAP Note 2217454 - EP: WPC Migration failing due the error ‘Error encountered migrating resource’ referencing the Site Content folder

SAP Note 1853367 - WPC Migration fails during permissions migration stage

SAP Note 2069837 - WPC Migration to EP 7.30 or higher Failing

SAP Note 2218762 - WPC Migration Fails - null object loaded from local variable 'aclList'

SAP Note 1668291 - WPC Content migration fails due to NullPointerException

SAP Note 1713976 - WPC migration fails during setting runtime permissions stage

SAP Note 1711785 - WPC migration fails during the permissions migration stage

SAP Note 1703531 - Migration fails during processing of regionalized pages

SAP Note 1703578 - WPC migration stops during connection creation

SAP Note 2049985 - WPC migration fails upon connection of Area to Portal Roles



 

 

  • No labels