How to create empty virtual portal using configuration Task

This post is more in continuation of my last blog entry regarding changing host name for your existing virtual portal. Fulfilling this task requires you to create an empty virtual portal as mentioned in a separate step.

Here is how you can create virtual portal with the help of configuration task create-virtual-portal.

1. Back up wkplc.properties file under /WebSphere/wp_profile/ConfigEngine/properties folder.

2. Modify it for the following configuration properties and save.

# Title of the Virtual Portal
VirtualPortalTitle=
# Realm of the Virtual Portal
VirtualPortalRealm=
# Hostname of the Virtual Portal.If you set the hostname, the portal sets the hostname, and the portal
parameter context is ignored.
VirtualPortalHostName=
# Context of the Virtual Portal
VirtualPortalContext=
# File which contains language specific information for the Virtual Portal
VirtualPortalNlsFile=
# VirtualPortalObjectId: ObjectId of the Virtual Portal
# The ObjectId is needed to modify, delete Virtual Portals and
# can be obtained by running task list-all-virtual-portals
# Note: Do not delete the default Virtual Portal (ObjectId ends with _0)
VirtualPortalObjectId=

3. Run the following command to create an empty virtual portal using above mentioned parameters.
./ConfigEngine.sh create-virtual-portal

4. Execute the ./ConfigEngine.sh list-all-virtual-portals task to make sure that the virtual portal is created on the target environment.

5. You can access virtual portal through http://localhost:10040/wps/portal/ URL. You will get a blank page with message "Error 404: There is no content available."

In my next blog I will show you how you can populate empty virtual portal.