Topic
3 replies Latest Post - ‏2012-11-01T02:50:04Z by TeruoKoyanagi
SystemAdmin
SystemAdmin
197 Posts
ACCEPTED ANSWER

Pinned topic Can't install plug-in for web crawler

‏2012-10-22T17:47:04Z |
Hi, I'm not able to install a prefetch or postparse plug-in for my web crawler. I'm running ICA v3 on Suse Enterprise Server 11. I followed the advice in the help manual, beginning here:

http://pic.dhe.ibm.com/infocenter/analytic/v3r0m0/index.jsp?topic=%2Fcom.ibm.discovery.es.nav.doc%2Fwelcome.htm

and in two previous forum postings:

https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14777051&#14777051 (particularly with the zip file)
https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14640486&#14640486

to no avail. The server displays the following error in the log file:

Timestamp: Monday, October 22, 2012 1:24:49 PM EDT
Severity: Error
Component: wc
Session:
Message: FFQD4924E An error occurred when calling Web crawler plug-in class com.ibm.wc.pi.MyPrefetchPlugin.
Line number: 252
Function name: com.ibm.es.wc.pi.PluginManager.init
File name: PluginManager.java
Process ID: 13884
Thread ID: 16
Server name: gt-stip

I can't find a more detailed stack trace unfortunately.

Thank you,
Sanjay
Updated on 2012-11-01T02:50:04Z at 2012-11-01T02:50:04Z by TeruoKoyanagi
  • SystemAdmin
    SystemAdmin
    197 Posts
    ACCEPTED ANSWER

    Re: Can't install plug-in for web crawler

    ‏2012-10-31T18:24:18Z  in response to SystemAdmin
    Bump... has anyone else come across this issue? I see the same error message in ICA v3 on Windows Server 2008.
    • bfoyle
      bfoyle
      60 Posts
      ACCEPTED ANSWER

      Re: Can't install plug-in for web crawler

      ‏2012-10-31T18:41:58Z  in response to SystemAdmin
      I haven't seen this...perhaps this one warrants a call to support ?
  • TeruoKoyanagi
    TeruoKoyanagi
    8 Posts
    ACCEPTED ANSWER

    Re: Can't install plug-in for web crawler

    ‏2012-11-01T02:50:04Z  in response to SystemAdmin
    It seems that the web crawler failed to load the plug-in class. Could you double check the class path and the class name of your plug-in?