Library Path and Java Class Path
During the development of a crawler plug-in, if Timothy has to add other
Java classes that are needed by the plug-in, he should include them in
the plug-in .jar file. Timothy notes this point. Other than this, there
are other important points that he considers:
| 1. | Paths could be added for the additional .jar files needed by the plug-in into the classpath of the MANIFEST.MF file within the plug-in .jar file. |
| Java classes should be included in the plug-in .jar file because Oracle SES automatically adds the plug-in .jar file to the crawler Java classpath. Also, Oracle SES does not let Timothy add other classpaths from the administration interface. | |
| 2. | If the plug-in code also relies on a particular library file such as a .dll file on Windows or a .so file on UNIX, then the library path environment variable (PATH on Windows, LD_LIBRARY_PATH on UNIX) must contain the path to it. |
| 3. |
Timothy should ensure that on Windows, Oracle services are set as system variables; and on UNIX they are set before running the command "searchctl startall". |
| 4. | The crawler automatically inherits all environment variables from Oracle, including the library path, as it is spawned by the Oracle process. |
