Exporting configuration for migration to a remote machine

 

+

Search Tips   |   Advanced Search

 

To back up server artifacts, extract database information, and export content from an earlier version of IBM WebSphere Portal, use the WAS Network Deployment V6.1 Supplements CD to run...

WPmigrate portal-pre-upgrade

The WAS ND Version 6.1 Supplements CD is not intended for use when performing a remote migration on IBM i5/OS. To perform a remote migration on i5/OS...

  1. Install the new version of WebSphere Portal on the same server as the earlier version

  2. Follow the steps in the topic that explains how to export core information for migration to the same machine.

  3. After running the portal-pre-upgrade task, move the backup directory containing exported information to the remote machine where the new portal version that you want to use is installed

  4. Continue the migration process following the steps in the topic that explains how to import core information for migration to a remote machine.

If you are using a 32-bit database driver on a 64-bit machine, use the 32-bit WAS ND V6.1 Supplements CD; if you have a 64-bit database driver on a 64-bit machine, use the 64-bit WAS ND V6.1 Supplements CD.

Prerequisites

Migration log output for the portal-pre-upgrade is stored in WebSphere Portal logs several different log files that you can view using a text editor.

The portal-pre-upgrade uses the WASPreUpgrade command in conjunction with special WebSphere Portal parameters to migrate WAS configuration information from the earlier portal installation to the new portal installation. To avoid problems, do not attempt to migrate WAS information yourself through manual use of this command.

 

Procedure

  1. Stop the WAS and WebSphere Portal servers (server1 and WebSphere_Portal) in the new portal installation.

  2. Start the earlier WebSphere Portal server and ensure that it is accessible to the network.

  3. On the machine where the earlier portal installation is located, insert the WAS Network Deployment V6.1 Supplements CD into the CD-ROM drive, and then change to...

    CD_root/migration/portal_migration

  4. To export the base server, run the portal-pre-upgrade as follows:

    Operating System Command
    Windows 
     WPmigrate.bat portal-pre-upgrade 
             -DbackupDirectory=dirname 
             -DcurrentPortalDirectory=dirname 
             -DcurrentPortalAdminId=adminid 
             -DcurrentPortalAdminPwd=adminpassword 
             -DDbPassword=dbpassword 
             -DGroupExport="true"
    UNIX 
    ./WPmigrate.sh portal-pre-upgrade 
             -DbackupDirectory=dirname 
             -DcurrentPortalDirectory=dirname 
             -DcurrentPortalAdminId=adminid 
             -DcurrentPortalAdminPwd=adminpassword 
             -DDbPassword=dbpassword 
             -DGroupExport="true"
    i5/OS 
     WPmigrate.sh portal-pre-upgrade 
             -DbackupDirectory=dirname 
             -DcurrentPortalDirectory=dirname 
             -DcurrentPortalAdminId=adminid 
             -DcurrentPortalAdminPwd=adminpassword 
             -DDbPassword=dbpassword 
             -DGroupExport="true"

    ...where...

    backupDirectory

    Directory where data from the earlier server will be stored for subsequent use with the portal-post-upgrade task. If this directory does not exist, the portal-pre-upgrade task creates it.

    For example, if you specify mybackup, the migration stores the data under the mybackup.

    currentPortalDirectory

    Directory where the earlier portal server is installed.

    currentPortalAdminId

    Administrator ID for the earlier portal server. This value is not required if it is already specified in the wpconfig.properties file on the earlier portal server.

    currentPortalAdminPwd

    Administrator password for the earlier portal server.

    DbPassword

    The DBMS user password for the earlier portal server. Specify this property value in the command line only if the property is not already specified as follows:

    • In WebSphere Portal V5.1.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, or 5.1.0.5, the property value is specified in the wpconfig.properties file, next to the property name DbPassword.

    • In WebSphere Portal V6.0.1.1 or later, the property value is specified in the wpconfig_dbdomain.properties file, next to the property name release.DbPassword.

    All other database properties must be specified in the properties file.

    The following properties are optional:

    GroupExport

    Exports groups from the earlier version when the value is set to true.

    This property is set by default to false.

    The ability to export groups from the earlier portal depends on the number of groups and the amount of time specified in the EJB transaction setting. If the number of groups is too high to export within the amount of time specified in the EJB transaction setting, the portal-pre-upgrade may report an error. Try increasing the wmmAPP EJB transaction time.

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

    Operating System Command
    Windows 
     WPmigrate.bat portal-pre-upgrade 
            -DbackupDirectory=dirname 
            -DcurrentPortalDirectory=dirname 
            -DcurrentPortalAdminId=adminid 
            -DcurrentPortalAdminPwd=adminpassword 
            -DDbPassword=dbpassword 
            -DGroupExport="true" 
            -DVirtualPortal=URL context
    UNIX 
    ./WPmigrate.sh portal-pre-upgrade 
            -DbackupDirectory=dirname 
            -DcurrentPortalDirectory=dirname 
            -DcurrentPortalAdminId=adminid 
            -DcurrentPortalAdminPwd=adminpassword 
            -DDbPassword=dbpassword 
            -DGroupExport="true" 
            -DVirtualPortal=URL context
    i5/OS 
     WPmigrate.sh portal-pre-upgrade 
            -DbackupDirectory=dirname 
            -DcurrentPortalDirectory=dirname 
            -DcurrentPortalAdminId=adminid 
            -DcurrentPortalAdminPwd=adminpassword 
            -DDbPassword=dbpassword 
            -DGroupExport="true" 
            -DVirtualPortal=URL context

    ...where...

    VirtualPortal

    The context extension for the virtual portal URL. See the URL Context description row in the Virtual Portal Manager portlet.

    The backup directory specified for the virtual portal must be the same backup directory specified in the previous step to export the base server.

    Base server migration must be done before virtual portal migration.

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

  6. Check allout.xml for any warning or error messages, and address any issues before moving on.

    If you are migrating from V5.1.x, look for allout.xml in backupdirectory/PortalServer/migration/work/default directory where backupDirectory is the location that you specified in the previous step.

    If you are migrating from version V6.0.1.1 or 6.0.1.3, look for allout.xml in the backupDirectory/profiles/<profile dir>/PortalServer/migration/work/default directory where backupDirectory is the location specified in the previous step.

    If allout.xml contains messages with the ID EJPXA0185W or EJPXA0186W see Technote 1300236 for additional information.

    If an Out of Memory condition occurs during the export process, see Technote 1299190.

 

Parent topic

Migrating to a remote machine

Next topic:

Updating database properties for migration

 

Related concepts

WebSphere Portal logs

 

Related tasks

Run migration tasks for composite applications

 

Related information

Technote 1300236

Technote 1299190

WAS Information Center