They are called Content Sources in the graphical user interface of SharePoint and Search Query Content Source when using PowerShell. A content source is basically pointing to a source of data that can be indexed in the search database. Because the data is indexed, when later users run queries the result is returned almost instantaneous. It is very easy to add a content source by using SharePoint Central Administration, but you might need to create a long list of content sources in a batch for example as part of a disaster recovery process or many other reasons. Here is one way I do it in a PowerShell script.
$contentSourceConfig = @(
@{
Name = "Articles"
StartAddresses = "http://mydomain1/site1/fr,http://mydomain1/site1/nl,http://mydomain1/site1/en"
},
@{
Name = "Technical"
StartAddresses = "http://mydomain1/site2/fr,http://mydomain1/site2/nl,http://mydomain1/site2/en"
}
)
foreach($config in $contentSourceConfig) {
$contentSourceName = $config.Name
$startAddresses = $config.StartAddresses
$contentSource = Get-SPEnterpriseSearchCrawlContentSource $contentSourceName -SearchApplication $ssa -ErrorAction SilentlyContinue
if ($contentSource) { $contentSource.Delete() }
$contentSource = New-SPEnterpriseSearchCrawlContentSource $contentSourceName -Type "Web" -StartAddresses $startAddresses -SearchApplication $ssa
Write-Host "Search crawl content source: $contentSourceName created successfully."
}
As you see in the above example I have put all the required configuration in one array of custom objects. If you need to add more content sources you may simply copy-past one and change the properties. This way the configuration is separated and easier to read or change while still it is in the same file with the script so you won’t have to rely on extra XML file(s) to put beside the script.
If you are more comfortable by separating the configuration from the script. You can cut the first part and past it to another script file or use the XML approach.
For more details about the cmdlets I’ve used I suggest you have a look on the following MSDN articles:
