Export; Import - IBM BS029ML - WebSphere Portal Server Self Help Manual

The MigrationTrace.log file contains a running list of each sub-task that the migration has run
along with the time stamp that it occurred. This is helpful when mapping an error in either the
WebSphere Portal Server log (systemout.log) or the MigrationMessages.log to a particular
migration task. Search this file for the last BUILD FAILED to see at what point the latest
migration ended.
Other files of interest can be found in the <wp_root>/work directory. This is were the migration
stores the temporary files that are generated during the migration. These files can be helpful
in showing what the tasks are trying to import into the V6 system. Unless stated in a
TechNote or by IBM support, we do not recommend making changes to these files.
Problems with migration can be put into three broad categories: Export, Import, and Post
Migration. We list some techniques to help locate the root cause of the errors encountered
during each category in the following sections.

Export

Xmlaccess export failure
The migration export involved the migration code performing a full xmlaccess export on
the source server. If there is an error during this export, the files to review are the
MigrationMessages.log and the wps_<time>.log file from the source server. Often, errors
with the export indicate that there may be some missing prerequisite fixes missing from
the source/target servers.
Export of user groups failure
Another task that is performed during the export phase is the export of the groups. This is
a very common point of failure that can have several causes. In this task, the WebSphere
Portal Server exports the groups from the V5.1 system to create an XML file that will then
be used to import the groups and the ACLs put on the groups into the target server. This
step is only needed when you have assigned a manager role to a group to manage
another group. This is not a very common set-p for most WebSphere Portal Servers. It is
often best that if the migration fails on this task to skip it if it is not required.
Common exceptions that occur during the export of the groups are
SizeLimitExceededException or an error from the LDAP itself stating that it cannot export
the number of records that is being requested. A TechNote that explains how to fix this
issue, if it caused by the WMM size limit, can be found at:
http://www-1.ibm.com/support/docview.wss?uid=swg21259963

Import

Missing WAR files
One of the manual steps in the migration of the portal is to move a copy of all the WAR
files that exist in the source portal into the sharedApp directory on the target portal (the
exception to this is pre-deployed apps). If this has not been done, the migration will fail
when it tries to install the portlets into the target server. If you have PK48603 or your
WebSphere Portal version is 6.0.1.1 or higher, the logs will provide a list of all WAR files
that are missing. If you are not at this level of the portlet, the migration will fail at each
missing WAR file, one at a time, with a nullpointer until the all of the WAR files are found.
Anonymous user ACLs
It is possible in IBM WebSphere Portal V5.1 to assign the anonymous virtual user a role
on an item greater than USER. If this is done, the migration import will fail, because this is
222
IBM WebSphere Portal V6 Self Help Guide