When to Use Oracle Secure Enterprise Search Crawler Plug-in API?

While Timothy is engrossed in resolving some Database issues, his manager enters his office with a list of tasks for his next project.

The users of Oracle Secure Enterprise Search now have some new business requirements.

	The HR department uses an application, which is a one stop shop for all their work. They are frequent users of Oracle SES, and they would want to crawl their application using SES. Source type for that application is not available out-of-the-box with SES, and hence they would want to develop a crawler plug-in for the same.
	The HR Manager would like to be able to search different files on the file systems using Oracle SES. The default Oracle SES file crawler handles public files only. The HR Manager wants to enforce file-level access control, so that only he should be able to view certain files with names that inlcude the term "resume." Hence, they need a plug-in to gather ACL for the file, thus enforcing security.
	Every user of Oracle Secure Enterprise Search would like to be able to search the corporate employee directory. Some of the users are particular about the way the search results are displayed. Therefore, the need for a plug-in is inevitable. This would help them view the organization structure prevalent at Oracle Corporation as per their needs.

Timothy analyzes these requirements and determines that the best way to meet them is to develop crawler plug-ins to enable the crawling of the new application and other file systems. He proposes this solution to his manager and obtains his support to pursue this initiative.