Virtual portals in the PAA file
There are many situations where a user might want to install the applications contained in a Portal Application Archive (PAA) file directly to a virtual portal.
No additional configuration steps are needed when creating the PAA file. The Solution Installer takes advantage of the virtual portal-related properties available in wkplc.properties when it connects to the portal server. The Solution Installer checks the value of the VirtualPortalHostName and VirtualPortalContext properties. If one or more of these properties are set, then their values are used when it creates a connection. However, if neither of these properties are set, it is assumed the PAA file content is installed to the base WebSphere Portal. These properties can be set in wkplc.properties or included on the command line with a prefix of '-D' when running the deployment. For example, '-DVirtualPortalContext=testVP'. In addition, when you remove resources from a virtual portal, these properties must also be set.
The properties and parameters must be set before running the installer to deploy the PAA application. There is no facility to install individual components of the PAA file to different virtual portals during a single run of the deploy-paa task. Therefore, run the deployment for the specific components required for each virtual portal separately. All components listed for deployment are installed to the same location.