Re-indexing Required for Most Upgrades

If you are only using the Information Server graphical interface spider (GUI Spider), you can continue to use it in Information Server V3.6 to create new meta collections and to maintain all of your existing meta collections.

If you have been using the Verity Spider (command-line), and will continue to do so, then there are collection upgrade issues which you must be aware of when using the Verity Spider V3.6.

Collections built with Verity Spider V3.5 must be re-indexed using Verity Spider V3.6.
Meta collections built with Verity Spider V3.1 must be upgraded to universal collections. For more information, see Chapter 1 and Appendix B in the Verity Spider User's Guide.

For Collections Built with Verity Spider V3.5

There has been an architectural change in the way Verity Spider V3.6 performs DNS-based duplicate detection. Due to this change from the functionality of Verity Spider V3.5 in Information Server Service Pack 3, it is possible that Verity Spider V3.6 will index duplicates into a collection created by Verity Spider V3.5. To avoid the possible duplication, you must use Verity Spider V3.6 to re-create your collections presently built with Verity Spider V3.5 from Service Pack 3.

NOTE: Verity Spider V3.5 and V3.6 both use the new universal collection format.

For Meta Collections Built with Verity Spider V3.1

Meta collections can be searched by Information Server, but they cannot be updated using Verity Spider V3.6. Meta collections built with Verity Spider V3.1 must be re-indexed to be compatible with Verity Spider V3.6. Instead of the five-collections-in-one meta collection built by Verity Spider V3.1, the Verity Spider V3.6 builds a single, universal collection containing all document types. This greatly increases the performance of indexing.

For more information regarding collection compatibility and re-indexing, see Chapter 1 and Appendix B in the Verity Spider User's Guide.

Copyright © 1998, Verity, Inc. All rights reserved.