Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Hints and tips for using Portal Search

Content Model has only one search collection

At this time the Content Model Search Service has only one search collection. This search collection is provided with the installation by default. You cannot modify this default Content Model search collection or create additional search collections under the Content Model Search Service. The content model search service is listed because you can include it in scopes.

Users cannot see portal site search results in their preferred language

If the preferred language of the crawler user ID does not match the language of the search collection, users might not see search results in their language. Therefore, set the preferred language of the portal site crawler user ID to match the language of the portal site search collection that it crawls. If you do this after you started a crawl on the portal site search collection, you need to reset the portal site collection. Refer to Creating or resetting the portal site collection.

If your portal site is multilingual and your users use different languages to search WebSphere Portal Express, set the portal site collections up as described under Crawling a multilingual portal site.

Using the Search Center with external search services with different languages

In order to use external search services such as Google and Yahoo! with an English search keyword, a URL such as the sample URL mentioned in the Search Center portlet help for configuring the portlet works fine as is: http://www.google.com/search?q= . However, if you search in other languages, consult the documentation of the remote search service that you use to ensure that the Web interface is set up and used appropriately for the language that you use for your search. This can avoid problems with the displayed results, depending on the combination of languages set for WebSphere Portal Express, your browser, and the search.

How Portal Search handles special characters when indexing

• The hash or pound sign ( # ).
• The percent sign ( % ).
• The plus sign ( + ).
• The asterisk ( * ).

Blank or white space; this includes the tab

Blanks separate words and are not indexed. Example: The string key board is indexed as two separate words key and board .

Line break or new line

Line breaks separate words and are not indexed unless they are preceded by a dash ( - ). Examples:

• The string

  key 
  board

  is indexed as two separate words key and board .
• The string

  key-
  board

  is indexed as one word keyboard.

Dot or sentence end period ( . ) and comma ( , )

Dots and commas separate words and are not indexed, unless they are both preceded and followed by a letter or digit. Example: The string www.ibm.com is indexed as www.ibm.com and not as three separate words.

Question mark ( ? ) and exclamation mark ( ! )

Question marks and exclamation marks separate words and are not indexed unless they are followed by a letter.

Other punctuation: ( ) { } [ ] < > ; : / \ | " _ -

These characters separate words and are not indexed.

Other characters

All other characters are removed from the strings in which they appear but do not separate words.

1. All characters that split words are discarded during indexing and searching.
2. The statements made above apply to indexing. However, in a search query all characters that can be part of the search syntax are treated in that capacity and not as part of the search query. These are the plus ( + ) and minus ( - ) signs, double quotation marks ( " ), and the asterisk wild card character ( * ). If users want to include such characters in their search query, they must enclose them in double quotation marks. For example "+hello" searches for the string +hello; "*Hello*" searches for the string *Hello*.

Time required for crawls and imports and availability of documents

The following search administration tasks can require extended periods of time:

• Crawling a content source. During the crawl documents might not be immediately available for searching or browsing.
• Indexing the documents fetched by a crawl. When a crawl has been complete and all documents have been collected, building the index takes some more time.
• Importing a search collection. When you import data to a collection, it can take some time until the content sources for the collection are shown in the Content Sources in Collection box and the documents of the imported collection are available for crawling.

These tasks are put in a queue. It might therefore take several minutes until they are executed and the respective time counters start, for example, the crawl Run time and the timeout for the crawl set by the option Stop collecting after (minutes): . The time required for these tasks is further influenced by the following factors:

• The number of documents in the content source that is being crawled
• The size of the documents in the content source that is being crawled
• Speed and availability of your processors, hard drive storage systems, and network connection.
• The value that you selected from the Stop collecting after (minutes): drop-down menu when you created or edited the content source.

Therefore both the time limits that you can specify and the times that are shown for these processes work as fuzzy time limits. This applies, for example, to the following scenarios:

• When you start a crawl by selecting a content source in the Content Sources in Collection box and clicking Start collecting.
• When you import a search collection and when you start a crawl on the imported search collection.
• When an installation is complete and you initialize the pre-configured portal site collection by selecting the portal site content source and clicking Start collecting.
• The time shown under Last update completed in the collection status information is later than you might assume by just adding the crawler time limit specified by Stop collecting after (minutes): to the crawling start time. This delay is caused by the additional time required by building the index.

Furthermore, this influences other status indicators given in the Manage Search portlet. For example, the number of documents shown for a content source can show with an unexpectedly low figure or even at zero ( 0 ) until the crawl on that content source has been completed.

Memory required for crawls

Crawling can require large amounts of memory. This depends on your Portal Search environment. Therefore, before you start a crawl, make sure that WebSphere Portal Express has enough free memory. Memory shortage can cause a corrupted search collection and eventually lead to a system freeze.

To resolve this problem, raise the limit to the number of open files by using the ulimit command as root administrator.

Crawling a portal site for the first time can result in a message

     EJPJP0009E: Wrong root url for Portal site crawler: https://root_url

To resolve this problem, edit the content source, select the General Parameters tab, and the set the parameter Stop fetching documents after (seconds): to a value of 90 seconds.

Uninstalling WebSphere Portal Express does not delete search collections

When you uninstall WebSphere Portal Express, the directories and files for the search collections are not deleted. Therefore, before you uninstall WebSphere Portal Express, delete all search collections by selecting the collections individually and clicking the option Delete Collection. If you do not do this, these files and directories remain on the hard drive. If you want to delete the search collection data after uninstalling WebSphere Portal Express, you need to do this manually. The directory path of a search collection is determined by what you typed in the field Location of Collection when you created the search collection. You can look up the collection location by performing the following steps:

1. Select the page Administration.
2. Select the Search Administration portlet.
3. From the Search Collections box select the collection that you want to configure for local search service.
4. The collection location is shown in the Search Collections box under Collection Status > Collection location. If the Collection Status is collapsed, expand it by clicking the plus sign (+ ).

HTTP crawler does not support JavaScript

The HTTP crawler of the Portal Search Service does not support JavaScript. Therefore some text of Web documents might not be accessible for search by users. This depends on how the text is prepared for presentation in the browser. Specifically text that is generated by JavaScript might or might not be available for search.

Linux operating systems might require higher limit of open files for Portal Search to work properly

     ulimit -n 4096

Creating the portal site search collection fails

Problem: If the file path length for the location of search collections exceeds its limit, the collection cannot be created. This can occur particularly when the portal site collection is created under Linux operating systems.

• The installation directory path. Under Linux operating systems the installation directory path name can be longer than under other operating systems.
• By default, the search collection for the portal site content is created under the path your_portal_install_directory/PortalServer/collections.
• The name of the virtual portal.
• The name of the search collection.

1. Change the default directory location for the portal site search collection to a shorter path, so that the complete path and file name does not exceed a length of 118 characters. For details about how to do this refer to Configuring the default location for search collections.
2. Recreate the portal site search collection. For details about how to do this refer to Creating or resetting the portal site collection.

Increase JVM heap size when using categorizer

1. Start server1 and log in.
2. Navigate to Servers, > Application Servers > WebSphere_Portal > Process Definition > Java Virtual Machine.
3. Determine the configured maximum heap size; for example, this might be 512 MB.
4. Increase the maximum heap size to at least 1024 MB.Notes:

   • When more memory is allocated than the physical memory in the system, paging will occur, and this can result in very poor performance.
   • On i5/OS, the JVM max heap size is set to 0 by default, indicating that there is no maximum. This setting should not be changed on i5/OS.
5. Restart WebSphere Portal Express.

Search collection is unavailable for Search and Browse portlet

Problem: A Search and Browse portlet cannot access the search collection to which you configured it.

Cause: If you migrated from a previous version of WebSphere Portal Express, the parameter for specifying the target search collection has been changed in the configuration for the Search and Browse portlet. The parameter IndexName has been replaced by CollectionLocation.

Solution: If you migrate from previous versions and have the Search and Browse portlet deployed, transfer the value from the old to the new parameter manually. For details about this refer to Migrating the Search and Browse portlet from version 5.x to 6.x.

Search collections unavailable in cluster if failover occurs

Problem: If a cluster member in a cluster fails, users who were using the affected cluster member when the failover occurred can no longer access search collections. This can occur with horizontal scaling when a node fails or with vertical scaling when a particular cluster member fails.

Solution: Users who are logged into the cluster member that failed must log out of WebSphere Portal Express and then log back in before they will be able to access search collections again.

Search can return documents based on metadata

Search can return documents based on metadata of these documents, not just on words found in the fields or actual text of the document. It might appear to Portal Search users that their searches return documents which do not appear to match the search criteria.

Cause: Meta-data for documents is also indexed for search. Therefore if the meta-data of documents matched the search criteria, these documents are also returned as results for the search.

Solution: This works as designed and is usually considered to be of benefit.

Documents from deleted content source can remain available under scope

If you delete a content source, then the documents that were collected from this content source will remain available for search by users under all scopes which included the content source before it was deleted.

Cause: These documents will be available until their expiration time ends.

Solution: The expiration time can be specified under Links expire after (days): under General Parameters when you created the content source.

Portal Search portlets are not compatible with WSRP

The Portal Search portlets cannot be provided as WSRP services, as some additional and more advanced WebSphere Portal Express concepts and features are not reflected by the current WSRP standard yet. This includes the Portal Search portlets Manage Search, Taxonomy Manager, Search and Browse, and the Search Center portlets.