+

Search Tips   |   Advanced Search

Indexing web content

To search for web content, the content must first be indexed by the HCL WebSphere Portal search engine. Once the content is indexed, we can run searches using the search center or using a search component. We see search results for published documents only. Unpublished pending changes in a project are not included in the results.


Create a content source for a site area

The HCL WebSphere Portal search engine defines content sources that index the web content. All the child site areas and content items of the selected site area is included in the index. Related content sources are grouped in a search collection.

  1. Click...

  2. Select or create a new collection.

    The default search collection named WebContentCollection is provided by default.

  3. Click New Content Source.

  4. Select WCM site as the content source type.

  5. Enter a name in the Content Source Name field.

  6. Enter the following URL in the Collect documents linked from this URL field:

      For a stand-alone server:

        http://hostname:port/wps/seedlist/myserver?SeedlistId=library/sitearea1/childsitearea2&Source=com.ibm.workplace.wcm.plugins.seedlist.retriever.WCMRetrieverFactory&Action=GetDocuments

      Replace hostname, port, library, and site area with values appropriate for the site. If the library name or site area names contain spaces, replace the spaces with a "+" symbol. For example, the path...

        library one/site area one

      ...would instead be defined as...

        library+one/site+area+one

      For a cluster:
      In this case us to use the host and port of the HTTP server:

        http://httpserver:port/wps/seedlist/myserver?SeedlistId=library/sitearea1/childsitearea2&Source=com.ibm.workplace.wcm.plugins.seedlist.retriever.WCMRetrieverFactory&Action=GetDocuments

      Replace httpserver, port, library, and site area with values appropriate for the site. If the library name or site area names contain spaces, replace the spaces with a "+" symbol. For example, the path...

        library one/site area one

      ...would instead be defined as...

        library+one/site+area+one

      For a virtual portal configured to use the URL Context as its access point:

        http://httpserver:port/wps/seedlist/myserver/vpContext?SeedlistId=library/sitearea1/childsitearea2&Source=com.ibm.workplace.wcm.plugins.seedlist.retriever.WCMRetrieverFactory&Action=GetDocuments

      Replace httpserver, port, vpContext, library, and site area with values appropriate for the site. If the library name or site area names contain spaces, replace the spaces with a "+" symbol. For example, the path...

        library one/site area one

      ...would instead be defined as...

        library+one/site+area+one

      For a virtual portal configured to use a different hostname as its access point:

        http://vphost:port/wps/seedlist/myserver/?SeedlistId=library/sitearea1/childsitearea2&Source=com.ibm.workplace.wcm.plugins.seedlist.retriever.WCMRetrieverFactory&Action=GetDocuments

      Replace vphost, port, library, and site area with values appropriate for the site. If the library name or site area names contain spaces, replace the spaces with a "+" symbol. For example, the path...

        library one/site area one

      ...would instead be defined as...

        library+one/site+area+one

    The seedlist ID can be any of the following:

    • library
    • library/site area
    • library/site area/sub-site area/...
    • the JCRID of a site area

  7. If the content to be indexed is secured, go to the Security tab. Then enter the user name and password of the user used to access the secured site. Then click Create on the search tab itself.

  8. If the site uses remote actions, filter these actions out of the search index. Go to the Filter tab:

    1. Type a name in the Rule Name field
    2. Select Apply rule while Collecting documents
    3. Select the rule type of Exclude
    4. Select the rule basis of URL text
    5. Type *&wcmAuthoringAction=* in the URL text field
    6. Click Create in the Filter tab

  9. Click Create.

If we have multiple parent site areas and want the searches to run across all site areas, create a content source for each of them in the same collection. If we do not want the searches to run across all parent site areas, create a separate collection for each parent site area or group of related parent site areas.


Search web content in a virtual portal

Search services and search collections are separate for individual virtual portals and are not shared between individual virtual portals. We set up an individual search service and separate search collections for each virtual portal. These collections can be used to crawl and search the same set of documents.

For a website shared across virtual portals, then to search that website in a virtual portal environment we must:

  1. Create new search collection for the virtual portal. We can create a new content source by copying the URL from the original search collection.
  2. Create new search component, or copy an existing search component, and configure it to use the new virtual portal search collection created in step 1.
  3. Create new search form, using an HTML component, which is configured to use the search component created in step 2.
  4. Create new content item to display the HTML component created in step 3.

We must do these steps for each virtual portal in your system.


Parent Search

Previous topic: Plan for Portal Search

Next topic: Configure Web Content Manager search options