WebSphere Portal 6.1 Virtual Portal Creation

The below steps were validated in RHEL 5 64 bit environment

1. Export the configuration using xmlaccess from the existing virtual portal

./xmlaccess.sh -user wpsadmin -password {password} -url http://existingvp.test.com:10040/wps/config -in /opt/IBM/WebSphere/PortalServer/doc/xml-samples/Export.xml -out /home/wasadmin/newvp-export.xml

2. Create an empty virtual portal
Edit /opt/IBM/WebSphere/wp_profile/ConfigEngine/properties/wkplc.properties with the following values:
VirtualPortalTitle=Virtual Portal Cloning
VirtualPortalRealm=realm-vptest
VirtualPortalHostName=newvp.test.com
VirtualPortalContext={leave it empty}
VirtualPortalNlsFile={leave it empty}
VirtualPortalObjectId={leave it empty}

Run /opt/IBM/WebSphere/wp_profile/ConfigEngine/ConfigEngine.sh create-virtual-portal

3. Import the configuration using xmlaccess to new virtual portal
./xmlaccess.sh -user wpsadmin -password {password} -url http://newvp.test.com:10040/wps/config -in /home/wasadmin/newvp-export.xml -out /home/wasadmin/newvp-import-results.xml

Tips:
1) Manually edit the exported xml file for any changes.
2) If the update portlet fails for your custom portlets because of this message.


com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: An error occurred while creating or updating the resource. [url-mapping-context ....
com.ibm.wps.command.mappingurl.MappingURLCommandException: EJPEC0622E: A resource of a virtual portal can only be mapped to a context of the same virtual portal.

make the following change.

url-mapping-context action="update"
to
url-mapping-context action="locate"

3) Find and change existingvp.test.com to newvp.test.com in the exported xml file