Import configuration for migration to a remote machine

To import backed-up artifacts and content that were exported from WebSphere Portal v6.0.1.x, use the WPmigrate script to run the portal-post-upgrade task.

Before performing the import, complete these tasks:

• Update the following properties in the WP_PROFILE/ConfigEngine/properties/WmmVmmDBMigration.properties file on the new portal: PrevPortalAdminId, PrevPortalAdminGroupId, PrevWasUserid, PrevWasAdminGroupId. When specifying these values, keep the following conditions in mind:

  • Ensure that you specify the fully qualified distinguished name (DN) for these properties. Specifying the short name results in a failed migration. Verify the fully qualified DN by checking the configuration of directory server.

  • Ensure that there are no trailing spaces or tabs in the parameter values.

• For any other administrator and group properties (Prev*) for the previous portal in the WmmVmmDBMigration.properties file, specify the fully qualified DN for the values.

• The portal-post-upgrade task includes code that prompts for the IBM WAS administrator ID and password. If you plan to run this stage of the migration unattended, ensure that you add the WAS administrator ID and password to WP_PROFILE/properties/sas.client.props and set loginSource=properties; also set the administrator ID and password in the com.ibm.CORBA.loginUserid and com.ibm.CORBA.loginPassword properties.
  To run the portal-post-upgrade task remotely through a telnet session, set loginSource either to properties as described above, or to stdin.

• Increase the lifetime timeout value. For more details about how to do this refer to the WAS information center.

• If you are using DB2type 4 driver, ensure that you have copied and pasted db2jcc4.jarand db2jcc_license_cu.jar to the WAS_HOME/lib directory.
  Note: If you are using DB2 Version 9.1, use the db2jcc.jar file. You will need to replace references to db2jcc4.jar with db2jcc.jar in this topic. If you are not using this specific version of DB2, use the db2jcc4.jar file.

• If you are using DB2 type 2 driver, ensure that you have copied and pasted db2jcc4.jarto the WAS_HOME/lib directory.
  Note: If you are using DB2 Version 9.1, use the db2jcc.jar file. You will need to replace references to db2jcc4.jar with db2jcc.jar in this topic. If you are not using this specific version of DB2, use the db2jcc4.jar file.

Run WPmigrate with the portal-post-upgrade task from the WP_PROFILE/PortalServer/migration directory, where WP_PROFILE is the profile directory of the new WebSphere Portal version.

Run the script as follows:

Windows™: WPmigrate.bat portal-post-upgrade -Dproperty=value

UNIX™: ./WPmigrate.sh portal-post-upgrade -Dproperty=value

i: WPmigrate.sh portal-post-upgrade -Dproperty=value

where:

property is a specific property used by the task

value is the property value

Migration log output for the portal-post-upgrade task is stored in several different log files that you can view using a text editor. For more information, see the topic on WebSphere Portal logs.

1. Move the directory that contains the exported data to the remote machine where the new version of WebSphere Portal is installed.
   Use a compression utility to compress the directory contents, or map a drive to the remote machine, and then move the directory containing the exported data to the remote machine.

2. Stop the new WebSphere Portal server.

3. Before migrating exported content into a new portal installation on AIX®, Linux™, Solaris, or i, check the value that is set by the ulimit command, and then increase the value to 200000.
   The ulimit command determines the maximum number of open files that the OS supports. By increasing the value before you migrate exported content into the new portal installation, you can avoid problems that might be caused if the value were too low. After migration is complete, you can restore the earlier value. For more information on ulimit, see the reference documentation for OS.

4. Change to the WP_PROFILE/PortalServer/migration directory.

5. Run the portal-post-upgrade task as follows:

   • Windows:
     WPmigrate.bat portal-post-upgrade -DbackupDirectory=dirname -DPortalAdminId=adminid -DPortalAdminPwd=adminpassword -DWasUserid=wasid -DWasPassword=waspassword -Dmigration.vmm.database.admin.password=vmmdminpassword -Dmigration.wmm.database.admin.password=wmmadminpassword -DoldProfile=oldserverprofilename

   • UNIX:
     ./WPmigrate.sh portal-post-upgrade -DbackupDirectory=dirname -DPortalAdminId=adminid -DPortalAdminPwd=adminpassword -DWasUserid=wasid -DWasPassword=waspassword -Dmigration.vmm.database.admin.password=vmmdminpassword -Dmigration.wmm.database.admin.password=wmmadminpassword -DoldProfile=oldserverprofilename

   • i:
     WPmigrate.sh portal-post-upgrade -DbackupDirectory=dirname -DPortalAdminId=adminid -DPortalAdminPwd=adminpassword -DWasUserid=wasid -DWasPassword=waspassword -Dmigration.vmm.database.admin.password=vmmdminpassword -Dmigration.wmm.database.admin.password=wmmadminpassword
   where:
   backupDirectory
   The directory where the portal-pre-upgrade task stored the data that it exported from the earlier server.
   
   PortalAdminId
   The administrator ID for the earlier portal server. Not required if it is already specified in wkplc.properties. Specify the login form of the administrator ID rather than the fully qualified name; for example, specify wpsadmin rather than uid=wpsadmin, o=defaultWIMFileBasedRealm
   
   PortalAdminPwd
   The administrator ID password for the earlier portal server.
   
   WasUserid
   The administrator ID for WAS used by the new portal server. Not required if it is already specified in wkplc.properties. Specify the login form of the administrator ID rather than the fully qualified name; for example, specify wasadmin rather than uid=wasadmin, o=defaultWIMFileBasedRealm

   The administrator ID that the new portal installation uses must match the administrator ID that the earlier portal version uses.

   
   WasPassword
   The password for the WAS administrator ID.

   The administrator password for the new portal installation must match the administrator password used in the earlier portal version.

   
   migration.vmm.database.admin.password
   The administrator password for the VMM database that the new WebSphere Portal version uses. Not required if it is already specified in WP_PROFILE/ConfigEngine/properties/WmmVmmDBMigration.properties.
   
   migration.wmm.database.admin.password
   The administrator password for the WMM database that the new WebSphere Portal version uses.Not required if it is already specified in WP_PROFILE/ConfigEngine/properties/WmmVmmDBMigration.properties.
   
   oldProfile
   The earlier portal server's profile name. The profile name must already exist in the backup directory specified above.

   This value is required if the earlier portal server's profile name is different from the new portal server's profile name.

   The following properties are optional:
   SkipAiMigration
   Suppresses migration of composite applications when set to any value. Composite applications are included in migration when this property is omitted.

6. Verify the migrated portal.

   1. Start the portal server, if it is not running.

   2. Open a web browser and enter the URL for the migrated portal.
      The migrated portal URL takes this form:

      http://host_name:port_number/original-context-root_migrated/portal

      For example, if original portal URL is http://www.example.com:10040/wps/portal, the URL for the migrated portal is http://www.example.com:10040/wps_migrated/portal. During migration, the following changes are made to wkplc.properties stored in the WP_PROFILE/ConfigEngine/properties directory:

      • The property WpsContextRootOriginal is set to the original value of the context root before migration was performed. This property is for reference only and is not used by the migrated portal.

      • The value of the WpsContextRoot property is set to the migrated value original-context-root_migrated (for example, wps_migrated).

7. If you have not yet created an empty virtual portal for each virtual portal that you want to migrate, use the create-virtual-portal ConfigEngine task to create empty virtual portals with the corresponding name and URL context. For information on the create-virtual-portal task, see Virtual portals reference.

8. For each virtual portal that you want to migrate, run the portal-post-upgrade task, as described above, and include the additional VirtualPortal property:

   • Windows:
     WPmigrate.bat portal-post-upgrade -DbackupDirectory=dirname -DPortalAdminId=adminid -DPortalAdminPwd=adminpassword -DWasUserid=wasid -DWasPassword=waspassword -Dmigration.vmm.database.admin.password=vmmdminpassword -Dmigration.wmm.database.admin.password=wmmadminpassword -DoldProfile=oldserverprofilename -DVirtualPortal=URL context -DWpsHomePage=homepageuniquename

   • UNIX:
     ./WPmigrate.sh portal-post-upgrade -DbackupDirectory=dirname -DPortalAdminId=adminid -DPortalAdminPwd=adminpassword -DWasUserid=wasid -DWasPassword=waspassword -Dmigration.vmm.database.admin.password=vmmdminpassword -Dmigration.wmm.database.admin.password=wmmadminpassword -DoldProfile=oldserverprofilename -DVirtualPortal=URL context -DWpsHomePage=homepageuniquename

   • i:
     WPmigrate.sh portal-post-upgrade -DbackupDirectory=dirname -DPortalAdminId=adminid -DPortalAdminPwd=adminpassword -DWasUserid=wasid -DWasPassword=waspassword -Dmigration.vmm.database.admin.password=vmmdminpassword -Dmigration.wmm.database.admin.password=wmmadminpassword -DVirtualPortal=URL context -DWpsHomePage=homepageuniquename
   where:
   VirtualPortal
   The context extension for the virtual portal URL. See the URL Context description row in the Virtual Portal Manager portlet.
   
   WpsHomePage
   The unique page name that you want to assign to the home page in the virtual portal.

   Virtual portals must be imported individually, one at a time; you cannot import a collection of virtual portals at once.

9. If you cloned the FileServer portlet in the earlier version and supplied HTML files in the wp_old_root/installedApps/FileServer_PA_1_0_4H.ear/FileServer.war/FileServerPortlet/html directory, copy those files to the $PORTAL_HOME/installedApps/cell_name/PA_FileServer.ear/FileServer.war/FileServerPortlet/html directory, after running the portal-post-upgrade task and before restarting the server, to make the files accessible in the new version.
   For i, the directories are wp_user_old_root and PORTAL_HOME_user, respectively.

10. Complete the following steps on the new version only:

    1. Open a command prompt and change to the following directory:
       Windows: WP_PROFILE/bin

       UNIX: WP_PROFILE/bin

       IBM i: WP_PROFILE/bin

    2. Enter the following command to stop the WebSphere_Portal server, where WebSphere_Portal is the name of the WebSphere Portal server:
       Windows: stopServer.bat WebSphere_Portal -username admin_userid -password foo

       UNIX: ./stopServer.sh WebSphere_Portal -username admin_userid -password foo

       IBM i: stopServer WebSphere_Portal -username admin_userid -password foo

    3. Enter the following command to start the WebSphere_Portal server, where WebSphere_Portal is the name of the WebSphere Portal server:
       Windows: startServer.bat WebSphere_Portal

       UNIX: ./startServer.sh WebSphere_Portal

       IBM i: startServer WebSphere_Portal

11. If the new portal server is running on AIX, Linux, Solaris, or i, reset the ulimit to the earlier value that you noted before you ran the portal-post-upgrade task.
    If needed, see the reference documentation for OS for more information on ulimit.

The portal-post-upgrade task changes the admin user ID and password settings for WebSphere Portal but not for WAS. If needed, you can manually update the WAS admin user ID and password. For instructions, see the topic on changing passwords.

Parent

Migrate to a remote server
Installation, configuration, and migration logs

Related tasks

Suppressing migration of composite applications
Virtual portals reference

Update user ID and passwords

  Submitted by Megan Crouch on Nov 10, 2010 11:29:57 AM

Import configuration for migration to a remote machine: wp7

According to development: "The answer should be no this is not a typo, the Prev* values are the fully qualified DN and are specified in the WmmVmmDBMigration.properties file. The value that needs to specified in step 5 is the logon id of the portal admin." Submitted by Bryant Poole on Oct 26, 2010 12:13:51 PM

Import configuration for migration to a remote machine: wp7

Is this a typo?

PortalAdminId

The administrator ID for the EARLIER portal server.

Other steps use the form PrevPortalAdminId when referring to the previous portal ID. Submitted by Bryant Poole on Oct 26, 2010 12:09:57 PM

Import configuration for migration to a remote machine: wp7

In step 5, is this a typo?

PortalAdminId

The administrator ID for the EARLIER(?) portal server.

Other steps have a flag called PrevPortalAdminId when it means to use the previous portal ID.

+

Search Tips   |   Advanced Search