In some cases when using the local search or remote search, you receive the message: "Didn't find SeedList in HTML, not a SeedList URL." The error is generated when trying to verify the address of content source.
There are two probable causes for this problem:
(1) If the error is received after successfully installing and configuring remote search service:
There is a hidden page off the root of the portal called "wp.search.seedlist" that needs to have the "Manage Seed List" portlet deployed to it. Without this portlet deployed, the remote search service cannot generate a proper seedlist URL.
(2) If the error still exists after deploying the portlet or if you are using local search when you get this error:
There is a maximum size for a page that can be fetched by the crawler. The default size is 0.2 MB (256 KB). Refer to the technote "Portal Search Engine unable to crawl documents over 256 KB in size (1238898)" for more information.
Resolving the problem
There are two possible solutions for this problem
(1) If, the error is received after successfully installing and configuring remote search service:
Deploy the seedlist portlet by performing the following steps:
1. Edit the page layout of "wp.search.seedlist" and add the "Manage Seed List" portlet.
2. Create a new content source. The previous error message should be replaced by a green "Site is OK" message.
Note: If installing the WebScannerSoap application into a portal topology that uses an IBM® HTTP Server, be sure to "Update the Web Server Plugin" to allow the remote search to work through IBM HTTP Server.
(2) If, the error still exists after deploying the portlet or if you are using local search when you get this error.
a) The parameter "HTTP_NON_APPL_MAX_BODY_SIZE_MB" was introduced with PK05370 and allows for configuration of this maximum page size. First make sure that the current version of portal has this interim fix installed or integrated.
Note: The fix for this APAR is integrated in WebSphere® Portal versions 220.127.116.11 and above.
b) Add the parameter "HTTP_NON_APPL_MAX_BODY_SIZE_MB" in the "Manage Search Collections" portlet by going in the configuration mode of the portlet and set it to value of 4
c) Stop and restart the portal server. Create a new collection and test if the problem is solved.
|Organizational Productivity- Portals & Collaboration||WebSphere Portal End of Support Products||Problem Determination||AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS||18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 5.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 5.0.2, 5.0||Enable, Experience, Extend, Express|