Use command line scripts - WebSphere Portal Migration
Use the command line scripts
The WebSphere Portal migration package provides the WPmigrate.sh script file to invoke the migration tasks. In the directory in which the current WebSphere Portal version is installed...cd portal_server_root/migration
WPmigrate.sh task_name -Dproperty=value...where task_name indicates the migration task that you want to run.
export-portal-content task
The export-portal-content task exports the WebSphere Portal content from the previous version.
- Stop the current WebSphere Portal server.
- Start the server for the previous version of WebSphere Portal and ensure it is accessible to the network.
Execute...
WPmigrate.sh export-portal-content -DPrevPortalAdminId=portaladminid -DPrevPortalAdminPwd=password
...where...
PrevPortalAdminId Portal admin id from the previous version of WebSphere Portal PrevPortalAdminPwd Password for the above Portal admin id To export virtual portal content...
- Stop the current WebSphere Portal server.
- Ensure the server for the previous version of WebSphere Portal is running and accessible to the network.
- Execute...
WPmigrate.sh export-portal-content -DPrevPortalAdminId=portaladminid -DPrevPortalAdminPwd=password -DVirtualPortal=URL context
...where URL context is the context extension for the virtual portal URL.
import-portal-content task
The import-portal-content task imports the content from the previous version of WebSphere Portal into the current version of WebSphere Portal.
- Stop the previous WebSphere Portal server.
- Start the server for the current version of WebSphere Portal and ensure it is accessible to the network.
- Specify the WasUserid and WasPassword in the wpconfig.properties file.
- Execute...
WPmigrate.sh import-portal-content -DPortalAdminId=portaladminid -DPortalAdminPwd=password
...where...
PortalAdminId Portal admin id from the current version of WebSphere Portal PortalAdminPwd Password from the above Portal admin id
- If running the import-portal-content task multiple times, Restart the servers before rerunning the task.
To import virtual portal content
- Stop the previous WebSphere Portal server.
- Ensure the server for the current version of WebSphere Portal is running and accessible to the network.
- Before importing each Virtual Portal, backup the database.
- Invoke the migration task...
WPmigrate.sh import-portal-content -DPortalAdminId=portaladminid -DPortalAdminPwd=password -DVirtualPortal=URL context
where:
PortalAdminId Portal admin id from the current version of WebSphere Portal PortalAdminPwd Password from the above Portal admin id URL context Context extension for the virtual portal URL.
- If running the import-portal-content task multiple times, Restart the servers before rerunning the task.
Optional: Migrating the FileServer portlet
If you cloned the FileServer portlet in previous versions and supplied HTML files in the...wp_old_root/installedApps/FileServer.war/FileServerPortlet/html...directory, copy those files to the...
portal_server_root/installedApps/FileServer.war/FileServerPortlet/html...directory, after running the import task and before restarting the server, to make the files accessible in the current version.
For i5/OS, the directories are wp_user_old_root and portal_server_root, respectively.
Restart the servers
After completing the import-portal-content task, restart the following server on the current version only:
- Open a command prompt and change to the following directory:
was_profile_root/bin
- Enter the following command:
./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password
- Enter the following command:
./startServer.sh WebSphere_Portal
Next steps
- Migrate additional components
- Migrate the remaining access control configuration
- Verify the migration tasks
Related information
Parent topic:
Migrating WebSphere Portal Configurations