You may want to duplicate a project if you need to set up another index using similar content and customizations. Linked search projects use the same content sets as the original project. Linked projects are automatically updated for any changes in content set names or labels you make in the Production project. However, note that changes to the content items within the sets are not automatically carried over; this allows you to experiment with changes to your content during testing.
Note: Use linking if you are setting up a staging environment. Linking ensures that the two projects are configured identically, which reduces the chance of configuration errors.
When you copy a production project that includes indexed repository content, before indexing you must do the following:
Update the name of the
IndexingOutputConfigcomponent in the linked project to point to the staging version of the component. The copied version of the project uses your initialIndexingOutputConfigcomponent but appends _COPY to the name.Update the host name in the linked project. The copied version of the project uses your initial host name but appends _COPY to the name.
Remove or update any remote post-indexing customization adapters that refer to the production version.
To copy a search project:
On the Projects tab, click Projects.
Click the Copy & Link link for the project.
Provide a name and description for the project.
Select the project’s target type. (See Before You Begin—Global Settings for target type information.)
Click OK.
Customizations associated with your production project are not duplicated, but the same customizations are associated with the new project as with the original.
