Set up a virtual portal in a portal farm

Additional steps that are recommended to have a successful virtual portal within a portal farm environment. If this procedure is not followed, the virtual portal artifacts have different object ID's in each Portal farm member, which can cause problems if the initial HTTP requests prior to establishing a session end up getting routed to different Portal farm members. This procedure ensures that all Portal farm members can service these initial HTTP requests.

To set up a virtual portal in a portal farm

These instructions only apply if we create a farm with independent servers, each with its own Release database.

1. Create and configure the virtual portal.

2. Export content from the virtual portal:
   cd WP_PROFILE/PortalServer/bin
   xmlaccess.bat -in ExportRelease.xml -user wpsadmin -password mypwd -url http://hostname:port/wps/config/virtualportalContext -out virtualportal_output.xml

   The exported configuration is stored in virtualportal_output.xml.

3. Run the create-virtual-portal configuration task on each portal farm to create an empty virtual portal, using the same name as the virtual portal created in the first step.

4. Import content from the first virtual portal into the virtual portals created on each portal farm:
   xmlaccess.bat -in virtualportal_output.xml -user wpsadmin -password wpsadminpwd -url http://hostname:port/wps/config/virtualportalContext -out Output.xml

Parent Set up farm instances as unique installations