WPMigrate

The Migration process runs bunch of scripts to migrate your data from previous version to WPS 6.1.0.1. The migration process can be divided into two major steps

Exporting the configuration from WebSphere Portal 6011 environment


In order to do this you should Navigate to \migration directory of your WebSphere Portal 6.1 server and run the following migration task.

PortalServer\migration>WPmigrate.bat portal-pre-upgrade
-DbackupDirectory=C:\mybackup
-DcurrentPortalDirectory=C:\ibm\PortalServer
-DcurrentPortalAdminId=wasadmin
-DcurrentPortalAdminPwd=wasadmin
-DDbPassword=db2admin
-DgroupExport="true"

The WPMigrate command takes following set of properties as command line argument

  • backupDirectory: is the directory where data from the WebSphere
    Portal 6.0.1.1 server will be stored for subsequent use with the portalpost-
    upgrade task. If this directory does not exist, the portal-preupgrade
    task creates it. Migration task stores the data under the
    mybackup directory.

  • currentPortalDirectory: is the directory where the WebSphere Portal 6.0.1.1
    server is installed.

  • currentPortalAdminId:is the administrator ID for WebSphere Portal 6.0.1.1
    portal server. This value is not required if it is already specified in the
    wpconfig.properties file of WebSphere Portal 6.0.1.1 environment

  • currentPortalAdminPwd is the administrator password for the WebSphere
    Portal 6.0.1.1 portal server.

  • DbPassword is th DBMS user password for the WebSphere Portal
    6.0.1.1 portal server. This value is not required if it is already specified
    in the wpconfig.properties file for the parameter/property name
    “DbPassword.” of WebSphere Portal 6.0.1.1 environment

  • groupExport: This is optional property with default value equal to false. If you set this property to true then websphere portal wont export groups



When you execute this task make sure that you get build successful message.If it
is successful, then you would see three files – allout.xml, vrout.xml and testexport.xml – created in backupdirectory/PortalServer/migration/work/default
directory where backupDirectory is the location that you specified in the previous
step. Check allout.xml for any warning or error messages, and address any issues
before moving on.

Now execute the portal-pre-upgrade task once for each of the virtual portals that you wish to export. You can do that by adding -DVirtualPortal command line parameter with value equal to the URL context of the virtual portal.

Important: The portal-pre-upgrade task uses the IBM WebSphere Application
Server WASPreUpgrade command in conjunction with special WebSphere
Portal parameters to migrate WebSphere Application Server configuration
information from the earlier WebSphere Portal installation to the new
WebSphere Portal installation. To avoid problems, do not attempt to migrate
WebSphere Application Server information yourself through manual use of
this command. For information on WASPreUpgrade, see the WebSphere
Application Server Information Center.

Importing the configuration into WebSphere Portal 6.1 environment



This WPMigrate task uses the allout.xml and vrout.xml that was generated
during the portal-pre-upgrade task, modifies it as required for WebSphere
Portal 6.1, and then imports the resulting configuration to the WebSphere
Portal 6.1 server environment using xmlaccess.

Navigate to <portal_server_root>\migration dir of your WebSphere Portal 6.1
server and run the following migration task.


PortalServer\migration>WPmigrate.bat portal-post-upgrade
-DbackupDirectory= C:\mybackup
-DPortalAdminId=wpadmin
-DPortalAdminPwd=wpadmin
-DWasUserid=wasadmin
-DWasPassword=wasadmin
-Dmigration.vmm.database.admin.password=db2admin
-Dmigration.wmm.database.admin.password=db2admin
-DoldProfile=wp_profile
-DprofileName=wp_profile


The portal-post-upgrade task takes following set of properties

  • backupDirectory is the directory where the portal-pre-upgrade task
    stored the data that it exported from WebSphere Portal 6.0.1.1 server.

  • PortalAdminId is the administrator ID for the WebSphere Portal 6.0.1.1 portal
    server. This value is not required if it is already specified in the
    wpconfig.properties file.

  • PortalAdminPwd is the administrator ID password for the WebSphere Portal
    6.0.1.1 portal server. This value is not required if it is already specified in the
    wpconfig.properties file on the earlier WebSphere Portal server.

  • WasUserid is the administrator ID for WebSphere Application Server that is
    used by the WebSphere Portal 6.0.1.1 server. This value is not required if it is
    already specified in the wpconfig.properties file

  • WasPassword is the password for the WebSphere Application Server administrator ID by the WebSphere Portal 6.0.1.1 server. This value is not required if it is already specified in the wpconfig.properties file


  • migration.vmm.database.admin.password is the administrator password for the VMM database that the WebSphere Portal 6.1 version uses. This value is not required if it is already specified in wp_profile_root/ConfigEngine/properties/WmmVmmDBMigration.properties


  • migration.wmm.database.admin.password is the administrator password for the WMM database that the WebSphere Portal 6.1 version uses. This value is not required if it is already specified in
    wp_profile_root/ConfigEngine/properties/WmmVmmDBMigration.properties

  • oldProfile is the earlier WebSphere Portal server's profile name. The profile
    name must already exist in the backup directory specified above.

  • ProfileName is the portal server's profile name in WebSphere Portal 6.1
    environment. Specify this property value to migrate to a specific existing
    profile in the new server if you do not want to use the default profile. If no
    value is specified, the portal-post-upgrade task uses the new server's default
    profile name.



Now execute the portal-post-upgrade migration task for each of the virtual portal that you want to import in you WPS 6.1.0.1 server by setting -DVirtualPortal property.

3 comments:

srjwebsolutions said...


We are leading responsive website designing and development company in Noida.
We are offering mobile friendly responsive website designing, website development, e-commerce website, seo service and sem services in Noida.

Responsive Website Designing Company in Noida
Website Designing Company in Noida
SEO Services in Noida
SMO Services in Noida

Vikas Chaudhary said...

Battery Mantra is Authorized exide car battery dealer in Noida and Greater Noida. We are providing our service in Indirapuram, Delhi, Ashok Nagar.

Exide Battery Dealer in Noida
Battery Dealer in Noida
Authorized Battery Dealer in Noida
Car Battery Dealer in Noida
Car Battery Dealer
Exide Battery Dealer

EG MEDI said...

Egmedi.com is online medical store pharmacy in laxmi nagar Delhi. You can Order prescription/OTC medicines online.
Cash on Delivery available. Free Home Delivery


Online Pharmacy in Delhi
Buy Online medicine in Delhi
Online Pharmacy in laxmi nagar
Buy Online medicine in laxmi nagar
Onine Medical Store in Delhi
Online Medical store in laxmi nagar
Online medicine store in delhi
online medicine store in laxmi nagar
Purchase Medicine Online
Online Pharmacy India
Online Medical Store