Troubleshoot migration

 

+

Search Tips   |   Advanced Search

 

  1. Portlet parameters may be lost if doing a Portlet Update or a migration
  2. Problems occurring with encoding of xml results of import and export results
  3. Migration not removing access control of user or group
  4. The export task finished with BUILD FAILED
  5. The import task finished with BUILD SUCCESSFUL
  6. The import task finished with BUILD FAILED
  7. Migration limitation for default encoding of markup languages
  8. After migration, only the Welcome and Getting Started pages are available
  9. Receive out of memory error
  10. During portal migration, XmlAccess reports an AuthorizationModelException with error code EJPSB0125E
  11. The export task finishes with BUILD SUCCESSFUL but also logs warnings

 

Problem: Portlet parameters may be lost if doing a Portlet Update or a migration

If you have made changes to existing portlet parameters through the Portal 'Manage Portlet' utility, these changes will be lost after a Portlet Update is done through the 'Portlet Application' utility or through a migration to another version of WebSphere Portal that does a silent update of the portlet.

Solution:

Make note of any modifications that you made through the 'Manage Portlet' utility and reapply the changes after the portlet update is complete.

For example, we can change the Notes View portlet parameters to point to a particular...

After the portlet is updated, these changes will be lost and reset to the default placeholder values. For future additions of this portlet to a page, the portlet would not be configured. If you have made many copies of the portlet, each configured separately, you would lose those changes. Therefore, it is important to note any modifications that are made to portlet parameters.

 

Problem: Problems occurring with encoding of xml results of import and export results

Sending migration export and import requests through an HTTP server may cause issues with the encoding of the xml results. You may encounter the following error: 

    org.xml.sax.SAXParseException: Content is not allowed in prolog

Solution:

If possible, use the direct connection to Portal server as opposed to going through the HTTP server when migrating.

 

Problem: Migration not removing access control of user or group

Migration will add access controls to a virtual resource but will not remove access control of a user or group.

Solution:

This is working as it was intended. Removal of access control will need to be accomplished using the new portals administration portlets.

 

Problem: The export task finished with BUILD FAILED

The migration export tasked failed and logged one of the following error messages:

EJPXB0016E: An error occurred on the client: Connection refused

Solution:

The migration export task failed. This error usually means that the previous version is not available on the network. Verify that the previous version is available and rerun the task.

EJPXB0019E: Server response indicates an error. For status and details of the xmlaccess error look at file

Solution:

The migration export task failed. Review the contents at the bottom of...

portal_server_root/migration/work/default/XML_file_name

Use the message number to determine the cause of the failure. After fixing the cause of the failure, rerun the task.

 

Problem: The import task finished with BUILD SUCCESSFUL

The import task was successful but logged the following warning message:

EJPXB0022W: The request was processed successfully on the server but warnings were encountered during processing. For details of the xmlaccess warnings look at file...

portal_server_root/migration/work/default/XML_file_name

Solution:

The import task was successful but with warnings. Review the contents at the bottom of...

portal_server_root/migration/work/default/XML_file_name

...to determine the cause of the warnings. After fixing the cause of the warning, rerun the task.

 

Problem: The import task finished with BUILD FAILED

The migration export tasked failed...

EJPXB0016E: An error occurred on the client: Connection refused

Solution:

The migration import task failed. This error usually means that the current version is not available on the network. Verify that the current version is available and rerun the task.

Missing war files have been detected. Verify the missing WAR files have been copied to the...

portal_server_root/installableApps

Solution:

The migration task failed because WAR files that existed in the previous version do not exist on the current version. Review the contents of...

portal_server_root/log/MigrationTrace.log

...and look for all occurrences of...

"portal_server_root/installableApps/WAR_file_name not found"

For each WAR file not found determine if there are any changes needed for the current version. Then copy the WAR file from the previous version to the current version and rerun the task.

EJPXB0019E: Server response indicates an error. For status and details of the xmlaccess error look at file...

portal_server_root/migration/work/default/XML_file_name

Solution:

The migration import task failed. Review the contents at the bottom of...

portal_server_root/migration/work/default/XML_file_name

Use the message number to determine the cause of the failure. After fixing the cause of the failure, rerun the task.

 

Problem: Migration limitation for default encoding of markup languages

The default encoding of markup languages is migrated from the previous version to the current version, which will cause problems if the language is East Asian, Japanese, Korean, Simplified Chinese, or Traditional Chinese.

Solution:

After migration, change the default encoding to UTF-8; see Change the character set for a language for information.

 

Problem: After migration, only the Welcome and Getting Started pages are available

There are ordinal values that determine the hierarchy of how pages display. If the ordinals of the migrated pages match the ordinals of the Out-of-box pages, the hierarchy is ambiguous and upon login, the user is directed to the incorrect page.

Solution:

Go to the Manage pages portlet and move the wps.My Portal label above the Home label using the Move up or Move down actions. We can also explicitly set the ordinals using the XML configuration interface.

 

Problem: Receive out of memory error

You may receive the Corba.NO_MEMORY error while performing various migration tasks, such as, but not limited to, exporting/importing users and/or groups or migrating documents larger than 20 M.

Solution:

Increase the JVM heap size according to the system requirements.

You may also need to stop all extra Java processes that are currently running on the machine.

If you receive the out of memory error while performing the export task, increase the JVM heap size on the previous WebSphere Portal. If you receive the out of memory error while performing the import task, increase the JVM heap size on the current WebSphere Portal.

 

Problem: During portal migration, XmlAccess reports an AuthorizationModelException with error code EJPSB0125E

This exception indicates that the previous version contains invalid role assignments that cannot be created within the current version. The following role assignments for the Anonymous Portal User are considered invalid in the current version:

  • Privilieged User@somepage
  • Editor@somepage
  • Manager@somepage
  • Administrator@somepage

All those role assignments would allow the anonymous user to modify existing portal content which is not supported by the portal runtime.

Solution:

In the previous version, change all of the above role assignments into User roles; see Roles for information.

 

Problem: The export task finishes with BUILD SUCCESSFUL but also logs warnings

The export task runs successfully, but also logs the following warning messages: 

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.

EJPXA0185W: The URL file://localhost/$server_root$/installableApps/pznruleportlet.war  does not point to a directory as required by predeployed portlets. 
 You will need to adjust the URL.

Solution:

These warnings indicate that the applications are pre-deployed ears and are not true Portlet WAR files. They are normal and can be addressed by Personalization migration steps. If Personalization is not required, these warnings can be ignored.