The biggest change in how Search works comes from the new concept of the Search Project and the elimination of the old Content Template taskflow in favor of a simpler configuration process.
The process for adding content to your searchable data has been simplified. Many seldom-used UI options have been moved so that while still accessible, if you do not need them they are easily skipped over.
ATG Search 2006.3 and earlier releases only allowed one indexing job to run per ATG Search installation. This generally required a separate ATG Search installation per site to work around this limitation. ATG Search 9.3 allows concurrent indexing jobs.
After identifying the content you want to make searchable, the procedures can be compared thus:
Step | ATG Search 2006.3 | ATG Search 9 |
|---|---|---|
Create a project | N/A | The new Search Project provides a central place to keep track of everything you need to index and deploy content: the content itself, associated configuration, information about where and how it should be deployed, etc. |
Acquire content | Create content connectors using data extractors and data renderers. | Add content directly to your Search Project. |
Customize content | Build topics, dictionaries, and other tools to help end-users find answers successfully. | The new Search Workbench provides a centralized, standardized way to create and test customizations, which can then be associated with one or more projects. |
Index content | Create a job script and procedures, and run the script. | Index your project, either immediately or by creating schedule rules. |
Note: A customization data type in previous versions of ATG Search known as “File Handling Options”, which specified how file extensions were interpreted with respect to file types, has been replaced by Advanced Settings options on the content itself.
