OmniFind: Dump collected documents by a seedlist crawler

• Create a file with name seedlistcrawler_ext.xml which contains the following:

<?xml version="1.0" encoding="UTF-8"?> <ExtendedProperties><AppendChild Xpath="/Crawler/DataSources/Server" Name="HttpTraceSeedlist">/tmp/seed.log</AppendChild> </ExtendedProperties>

• Put the file into ES_NODE_ROOT/master_config/<Crawler ID>/ 
• Restart the crawler session, and then perform full crawl.
• All HTTP activities regarding seedlist should be logged in the specified file (/tmp/seed.log ). It will contain dumps of all pages.

Portal: View Retriever Factories

To view the retriever factories deployed on a Portal server including custom factories, use the following URL:

http://<portal_host>:<port>/seedlist/myserver

Lotus connections: seedlist URLs

Lotus connections seedlists can be accessed from browser using the following URLs:

http://<host>:<port>/blogs/seedlist/myserver

http://<host>:<port>/activities/seedlist/myserver

http://<host>:<port>/dogear/seedlist/myserver

http://<host>:<port>/communities/seedlist/myserver

http://<host>:<port>/communities/seedlist/forum/myserver

http://<host>:<port>/files/seedlist/document/community

http://<host>:<port>/files/seedlist/document/personal

http://<host>:<port>/wikis/seedlist/myserver

Those URLs are useful to trace integration problems with OmniFind.

OmniFind: Dropped documents log location

Question:
Where are dropped documents logs are located on OmniFind server ?

Answer:
Those log files are not stored in the normal OmniFind log file path as they are stored under the collection specific folder as follows:

$ES_NODE/data/<collection_id>/dropped_doc_logs/

Portal: Invalidate Portal seedlist Cache

Add parameter Range=0 to the seedlist URL to invalidate the cache as shown below:

 https://<host>:<port>/seedlist/myserver?Action=GetDocuments&SeedlistId=&Source=com.ibm.workplace.wcm.plugins.seedlist.retriever.WCMRetrieverFactory&Range=0

OmniFind: Quickr crawler exception

Problem:

FFQD5911E The crawler could not establish a socket connection to the server: dstindiai14.in.ibm.com port: 443.

Resolution:

File LotusQuickr-config.xml was updated to change

<sloc:serviceReference enabled="true" serviceName="login" ssl_enabled="false" isIncludedInMainNav="false">

<sloc:href>

<sloc:hrefPathPrefix>/Redirect/LoginIntegrator</sloc:hrefPathPrefix>

<sloc:static href="http://dstindiai14.in.ibm.com:10080" ssl_href="https://dstindiai14.in.ibm.com:10080" />

</sloc:href>

</sloc:serviceReference>

was changed to:

<sloc:serviceReference enabled="true" serviceName="login" ssl_enabled="false" isIncludedInMainNav="false">

<sloc:href>

<sloc:static href="http://dstindiai14.in.ibm.com:10080" ssl_href="https://dstindiai14.in.ibm.com:10080" />

</sloc:href>

</sloc:serviceReference>

In other words, we removed the LoginIntegrator(shown below) from the login service: <sloc:hrefPathPrefix>/Redirect/LoginIntegrator</sloc:hrefPathPrefix>

This caused the link http://<host>:<port>/places/myplaces  to break and I am currently working on a PMR to resolve this.

OmniFind: Verify Portal/Quickr ESPAC application is up and running

Open browser and try to access the following URL on your Portal or Quickr server:

http://<host>:<port>/ESRemotePAC/RemotePACServlet

If results is a blank page without errors then it is working properly

OmniFind: Lotus connections crawler error with basic authentication

Problem:

The following sample error shows in OmniFind log after trying to crawl Lotus connections:

FFQD5910E The crawler could not log on to the server with basic authentication. The URL is <host>:9447/blogs/seedlist/myserver.

Resolution:

Make sure the user used for crawling is mapped correctly to search-admin role for all Lotus connections applications.

For more information consult the following tech-note:

http://www-01.ibm.com/support/docview.wss?uid=swg27018069&aid=1