Create a virtual portal
- Click the "New Virtual Portal" button, then enter...
Virtual portal title Title of the virtual portal. Limited to 255 characters. Virtual portal description Description of the virtual portal. Limited to 255 characters. URL Context Last part of the URL of the virtual portal. Preceded by... http://www.myco.com/wps/portal/
Virtual portal URL contexts are built from the root context for the portal server and must be unique. We cannot use sub-contexts. For example, this URL is invalid:
http://www.myco.com/wps/portal/vp1/vp2
Correct format:
http://www.myco.com/wps/portal/vp2
Virtual portal hostname We cannot use the same virtual portal host name twice in the same portal installation. The host name must be unique for the portal installation. Host names must be valid host names that are either registered on the local DNS, or internally using the "hosts" file. Host names must be registered on the system before creating a virtual portal. User realm Select a realm from the list. This pulldown appears only if realms are enabled on the environment. The default realm is portal. We can select other realms that we might have created. If we have realms enabled, but we do not want to use them for the virtual portals, we can deselect realms by selecting the blank option line from the pulldown list. Initial administrative user group Enter the name of an administrative user group, or search for a group. To search for a group:
- Click the Search icon.
- Select the search type from the Search by: drop-down menu. The Search: field appears.
- Enter the search parameters in the Search field.
- Click Search.
- Select the appropriate user group and click OK to continue.
Default theme Select from the drop down list. Select the Preview icon to see a preview of the selected theme.
- After providing all the information, click OK to create the virtual portal.
Completing the steps to create a virtual portal also creates the virtual portal entity and calls xmlaccess.sh script that creates the initial content tree.
Use a custom XML script to create the content
To use a custom XML script to create content of a virtual portal, create an XML script file that specifies the initial content for virtual portals. Before creating the new virtual portal, add the XML file with the custom XML script to a WebSphere Application Server asset and then specify the asset and file name in the Configure mode of this portlet. Alternatively, we can also copy the asset VirtualPortal.zip provided with the portal under a different name and modify it as required. Do not modify the original VirtualPortal.zip provided with the portal.
JCR Search Collection
When we create a virtual portal, the creation of the JCR search collection depends on whether we create the virtual portal with or without content:
- If we create the virtual portal with content, the portal creates the JCR collection by default.
- If we create only the virtual portal and add no content to it, the portal creates no JCR collection with it. It will get created only when content is added to the virtual portal.
We can view the URL of the JCR collection in the virtual portal administration portlet. The URL looks as follows...
http://host:port/seedlist/server?Action=GetDocuments&Format=ATOM&Locale=en_US&Range=100&Source=com.ibm.lotus.search.plugins.seedlist.retriever.jcr.JCRRetrieverFactory&Start=0&SeedlistId=wsid@ootb_crawlerwsid
...where wsid is the actual workspace ID of the virtual portal. The workspace ID is the identifier of the workspace in which the content item is created, stored and maintained. For example, if the workspace ID of the virtual portal is 10, then the URL looks as follows:
http://host:port/seedlist/server?Action=GetDocuments&Format=ATOM&Locale=en_US&Range=100&Source=com.ibm.lotus.search.plugins.seedlist.retriever.jcr.JCRRetrieverFactory&Start=0&SeedlistId=10@ootb_crawler10