Page History

...

# sharepoint connector 
"transform":{
  "conn_url_prop_name": "serverUrl",
  "source_url_prop_name": "siteCollectionsToCrawl:siteCollectionUrl",
...

#smb connector
"transform":{
  "conn_url_prop_name": "host",
  "source_url_prop_name": "urls",
..

#file system connector
"transform":{
  "conn_url_prop_name": "url",
  "source_url_prop_name": "urls",
..

We can see that are created keys "conn_url_prop_name", "source_url_prop_name" which are pointing to json connection property name and xml tag in content-source.xml.

...

Users add in UI only path to the file and in the file content-source.xml is xml tag

# sharepoint connector
<seedsFilePath>${aspire.config.dir}/${app.name}/urls.txt</seedsFilePath>

#smb connector
<fileUrl>C:\tmp\ups.txt</fileUrl>

#filesystem connector
<fileUrl>C:\tmp\ups.txt</fileUrl>

 The file path xml tag is not standardized for all connectors, so we created similar mechanism as for urls to deal with that.

# sharepoint connector
"transform":{
  "source_fileurl_prop_name": "seedsFilePath",
...
#smb connector
"transform":{
  "source_fileurl_prop_name": "fileUrl",
...
#filesystem connector
"transform":{
  "source_fileurl_prop_name": "fileUrl",
...

Script read urls from "content-source.xml" file or txt file , splits them Script read urls, split them to connection part and seed part and create them several connections and seeds by HTTP API call.

Related articles

...