Before running the export process, you must complete the tasks in Preparing the source environment. For the export process to work, the source Lotus Quickr 8.1.1.1 portal server must be started before running the WPmigrate export command.

To run the export process, perform the following steps:

If you are running the export process after having previously run it, either delete or rename the previous backup directory created by the export process. Reusing the same directory can cause problems with the place export process.

Run the command to set up the command line from the <WAS Extras CD>/migration/bin directory.

For Windows®, enter:

setupCmdLine.bat

For UNIX®, enter:

./setupCmdLine.sh

On the command line change the directory to <WAS Extras CD>/migration/portal_migration.

Launch the process.

The command syntax is:

WPmigrate.bat|sh portal-pre-upgrade

-DbackupDirectory=<source_backup_dir>

-DcurrentPortalDirectory=<source_quickr811x_dir>/PortalServer

-DcurrentPortalAdminId=<source_portal_id>

-DcurrentPortalAdminPwd=<source_portal_password>

-DDbPassword=<source_db_admin_password>

-DDoNotCopySkinsThemesScreens=true

-DPrevWpFamilyName=PortalExpress

-DPrevPortalAdminId=<source_portal_id>

where:

<source_backup_dir> is the directory where data from the source WebSphere Portal server will be stored for subsequent use with the portal post-upgrade task. If this directory does not exist, the portal-preupgrade task creates it. The migration task stores the data under the <source_backup_dir> directory. Specify the full path of the <source_backup_dir> directory, for example, C:\\mybackup.

<source_portal_id> is the current 8.1.1.1 administrator userid for WebSphere Portal.

<db admin password> is the administrator password for your database. If you have split out the database domains to separate databases, this password matches the one used for the release domain.

If prompted to accept an SSL certificate, enter Y to accept and continue with the export process.

The migration log is stored on the source server in the system temp directory. It could be deleted unintentionally later. Copy <system temp>/MigrationTrace.log to <source_backup_dir>.

Before you continue to the import steps, make sure that the export steps completed successfully.

Check the MigrationTrace.log file for errors. For a remote migration, the file will be in the <system temp> directory. Otherwise, the file will be in the <target_dir>/wp_profile/PortalServer/log directory.

Confirm that the <source_backup_dir> directory contains the following folders:

profiles

wp.migrate.ai

Look in the <source_backup_dir>/wp.migrate.ai/application folder and verify there is one subfolder containing multiple subfolders. These subfolders represent your source system places so there should be many.

If you have backup places that will migrate, also look in the folder <source_backup_dir>.wp.migrate.ai/backups for subfolders.

Verify that the <source_backup_dir>/profiles/wp_profile/PortalServer/migration/work/default/allout.xml file exists.

Restore static log settings in the administrative console back to their original values.

Log into the WebSphere Administrative Console as the WebSphere Application administrator.

On the Configuration tab which changes the static setting for the trace.log file, restore the Maximum File Size to your previous value (default is 20 MB) and the Maximum Number of Historical Files to your initial value (default is 3).

Click OK to save.

Click Troubleshooting->Logs and Trace >WebSphere_Portal->JVM Logs.

On the Configuration tab which changes the static setting for the SystemOut.log file, restore the Maximum Size to your previous value (default is 5 MB) and the Maximum Number of Historical Files to your previous value (default is 3).