Step 2. Add a New Content Source
- For this step please follow the step from the Configuration Tutorial of the connector of you choice, please refer to the Connector list.
Once you've clicked Add, it will take a moment for Aspire to download all of the necessary components (the Jar files) from the Maven repository and load them into Aspire. After that's done, the publisher will appear in the Workflow Tree.
For details on using the Workflow section, please refer to Workflow introduction.
Step 4. Run a test
The SharePoint 2013 Endpoint must be up and running before performing this test.
Change the indexing mode to Test by clicking on the indexing mode (this will cycle through the values Incremental, Full and Test). After the test has run, these things will have happened on the SharePoint server:
- A directory [Content Source name] will have been created in the Shared Repository folder.
- An External Content Type [Content Source name]-Model-ECT will have been created in the SharePoint Business Data Service Application.
- A Content Source [Content Source name] will have been created in the SharePoint Search Service Application.
- Crawled Properties will have been created in the Business Data category for every
<field>entry found in the XML batch.
Step 5. Map Crawled Properties to Managed Properties
Per configuration default, every Crawled Property in the Business Data category is mapped to the indexed document's full text. Thus, every indexed document is searchable, per se. If you need to use different titles, store the size, or assign file types, then you need to adjust the property mappings.
- Open SharePoint Central Administration and click Manage Service Applications, Search Service Application, Search Schema, Categories and Business Data.
- Check the list of Crawled Properties and add a mapping to Managed Properties, where needed.
- Make sure your Crawled Property is in a good position in the mapping list in case the value of the first non-empty Crawled Property is used to populate the Managed Property.