Panel | ||
---|---|---|
| ||
|
Launch Aspire (if it's not already running). See:
To specify exactly what shared folder to crawl, we will need to create a new "Content Source".
To create a new content source:
In the "General" tab in the Content Source Configuration window, specify basic information for the content source:
After selecting a Scheduled, specify the details, if applicable:
Info |
---|
You can add more schedules by clicking in the Add New option, and rearrange the order of the schedules. |
Info |
---|
If you want to disable the content source just unselect the the "Enable" checkbox. This is useful if the folder will be under maintenance and no crawls are wanted during that period of time. |
Note |
---|
Real Time and Cache Groups crawl will be available depending of the connector. |
In the "Connector" tab, specify the connection information to crawl the Confluence
Domain Username Password
In the "Workflow" tab, specify the workflow steps for the jobs that come out of the crawl. Drag and drop rules to determine which steps should an item follow after being crawled. This rules could be where to publish the document or transformations needed on the data before sending it to a search engine. See Workflow for more information.
After completing this steps click on the Save then Done and you'll be sent back to the Home Page.
Now that the content source is set up, the crawl can be initiated.
The status will show RUNNING while the crawl is going, and CRAWLED when it is finished.
If there are errors, you will get a clickable "Error" flag that will take you to a detailed error message page.
If you only want to process content updates from the Confluence (documents which are added, modified, or removed), then click on the "Incremental" button instead of the "Full" button. The Confluence connector will automatically identify only changes which have occurred since the last crawl.
If this is the first time that the connector has crawled, the action of the "Incremental" button depends on the exact method of change discovery. It may perform the same action as a "Full" crawl crawling everything, or it may not crawl anything. Thereafter, the Incremental button will only crawl updates.
Info |
---|
Statistics are reset for every crawl. |
Group expansion configuration is done on the "Advanced Connector Properties" of the Connector tab.
Here are examples of JSON requests for various types of updates:
Code Block | ||
---|---|---|
| ||
{ "contentSource": "Aspire_Confluence_Source", "documents": [ { "url": "http://10.89.26.110:8090/rest/api/space/NELA", "action": "update", "metadata": { "connectorSpecific": { "field": [ { "@name": "spaceKey", "$": "NELA" } ] } } } ] } |
Code Block | ||
---|---|---|
| ||
{ "contentSource": "Aspire_Confluence_Source", "documents": [ { "url": "http://10.89.26.110:8090/rest/api/content/8159239", "action": "update", "metadata": { "connectorSpecific": { "field": [ { "@name": "confluenceId", "$": "8159239" } ] } } } ] } |
Code Block | ||
---|---|---|
| ||
{ "contentSource": "Aspire_Confluence_Source", "documents": [ { "url": "http://10.89.26.110:8090/download/attachments/8159239/test.txt?version=1&modificationDate=1538982092437&api=v2", "action": "update", "metadata": { "connectorSpecific": { "field": [ { "@name": "confluenceId", <------ attachment Id "$": "10848196" }, { "@name": "parentType", <------- page or blogpost. The type of the item where we have attachment "$": "page" }, { "@name": "parentContainerId", <------- Item id of page or blogpost with the attachment "$": "8159239" } ] } } } ] } |
Code Block | ||
---|---|---|
| ||
{ "contentSource": "Aspire_Confluence_Source", "documents": [ { "url": "http://10.89.26.110:8090/rest/api/content/3145758", "action": "update", "metadata": { "connectorSpecific": { "field": [ { "@name": "confluenceId", "$": "3145758" } ] } } } ] } |
Code Block | ||
---|---|---|
| ||
{ "contentSource": "Aspire_Confluence_Source", "documents": [ { "url": "http://10.89.26.110:8090/rest/api/content/3145752", "action": "delete" } ] } |