Step 2:

Plugin Setup

1. Under the \config folder, locate the file named configurationParameters.xml and open it in a file editor.
2. In the xml structure, under StagerBDCModel specify the following values:
   • stagingRepositoryUrl: The
   Host:Port
   • host port where the STageR is running
   • sharePointServiceUrl: The
   Host:
   • host port where the SharePoint
   2013
   • Central Administration is running
   • searchServiceApplicationName: The name of the search service application within SharePoint
3. stagerFolderPath: The path to the root directory of STageR
4. Open SharePoint Management Shell as an administrator and go to the \scripts folder.

5. Run the following script for the corresponding SharePoint version:

   Code Block
   language bash theme FadeToGrey
   .\DeployStagerPlugin_2013.ps1 -configurationFilePath ..\config\configurationParameters.xml .\DeployStagerPlugin_2016.ps1 -configurationFilePath ..\config\configurationParameters.xml

6. If all went well it should present the following:

Image Modified

Step 3: Model and Content Source Setup

1. Under the \config folder, locate the file named configurationParameters.xml (The the one you modified in the previous step) and create a copy of it.
2. Modify the following fields in the new copy:
   • contentSourceName: The name of the content source that will appear under Search Service Application in SharePoint
   • storageUnitName: The name of the Storage Unit within STageR
   where
   • from which the content will be extracted
   from
   • storageUnitScope: The scope within the Storage Unit.
    The
   • The value of 'publisher' is
   recomended 
   • recommended. 
   • maxBatchesToProcess: The maximum number of batches processed by the
   plug-in
   • plugin per execution
   • batchSize: The maximum number of documents per batch processed
   • certPath: The path to the .p12 or .pfx file if SSL is needed.
    Leave empty if not
   • If not, leave the field empty.
   • certPassword:  The password to the .p12/.pfx file if SSL is needed.
    Leave empty if not
   •  If not, leave the field empty.
   • claimsIssuer:  The issuer of the access claims.
    Accepted
   • Accepted values are 'public' for no issuer, 'aspire' to use the Aspire Group Expansion or 'windows'.
   • useFullName:  Specifies if claims should use full name (
   i.e.
   • domain/name) when sent to the group expander
3. Open the SharePoint Management Shell as an administrator and go to the \scripts folder.

4. Run the following script for the corresponding SharePoint version:

   Code Block
   language bash theme FadeToGrey
   .\DeployModel_2013.ps1 -configurationFilePath ..\config\<the file name of the new xml> .\DeployModel_2016.ps1 -configurationFilePath ..\config\<the file name of the new xml>

5. If all went well, it should present the following:

Image Modified

Step 4: Content Processing Module setup

1. Under the \config folder, locate the file named configurationParameters.xml and open it in a file editor.
2. In the xml structure, under StagerBDCModel specify the following values:
   • stagerFolderPath: The local path to the root directory of STageR
3. Open SharePoint Management Shell as an administrator and go to the \scripts folder.

4. Run the following:

   Code Block
   language bash theme FadeToGrey
   .\DeployContentProcessingModule.ps1 -configurationFilePath ..\config\<the file name of the new xml>

5. No error should appear if all went well.

Step 4a: Manual Setup

This applies for non-Windows operating systems.

1. Copy the SharePointBCSMapping.js file to STageR's \process_modules directory.

2. From a REST client run the following command:

   Code Block
   theme FadeToGrey
   http://<host:port>/admin/setContentProcessingModules/<Storage Unit Name> {"modules" : {"<Storage Scope Name>":[{"module" : "SharePointBCSMapping"}]}}

Step 5: Schedule the Content Source

Crawls

1. Go to SharePoint Central Admin → Admin > Manage Service Applications → Applications > Search Service Application (the name specified in the configuration) →  > Content Sources
2. Locate the Content Source content source you configured in the previous step.
3. Hover the mouse over it and click the dropdown
4. Here From the drop-down, you can trigger crawls directly, but to . To schedule automatic crawls, select Edit.
5. In the new page, scroll down to Crawl Schedules and set the schedule as needed.

Uninstallation

In order to remove the StageR BDC Plugin, there are two options: manual and automatic removal 

Manual Removal

Step 1:  Remove Content Source

1. Go to SharePoint Central Admin → Admin > Manage Service Applications → Applications > Search Service Application (the name specified in the configuration) →  > Content Sources
2. Locate the Content Source content source you want to remove.
3. Hover the mouse over it and click the dropdown
4. Select From the drop-down, select Delete and confirm.

Step 2: Remove Model

1. Go to SharePoint Central Admin → Admin > Manage Service Applications → Applications > Business Data Connectivity Service
2. From the top dropdown drop-down, select BDC Models.
3. Select the Model model you want to remove. (its Its name should be similar to the Content Sourcecontent source's name.)
4. Click Delete and confirm.

Automatic Removal

Step 1: Remove Content Source and Model

1. Open SharePoint Management Shell as administrator.

   Note
   A machine and farm administrator user is needed for this.

2. Go to the Deploy\scripts directory.

3. Run the following:

   Code Block
   language bash theme FadeToGrey
   .\RemoveModelAndContentSource.ps1 -configurationFilePath ..\config\<The configurationContent file name for the Content Source>Source configuration>.xml

   Note
   Make sure the configuration file you specified is the same one you used when creating the Content Source content source you want to remove.

4. Both the Content Source content source and Model model should have been removed.

Step 2: Remove

Plugin

1. Open SharePoint Management Shell as administrator.

   Note
   A machine and farm administrator user is needed for this.

2. Go to the Deploy\scripts directory.

3. Run the following script for the corresponding SharePoint version:  

   Code Block
   language bash theme FadeToGrey
   .\RemoveStagerPlugin_2013.ps1 -configurationFilePath ..\config\configurationParameters.xml .\RemoveStagerPlugin_2016.ps1 -configurationFilePath ..\config\configurationParameters.xml

4. The farm solution should have been removed.

Custom Content Configuration

The plugin uses the content processing capability of STageR to normalize the content that is stored in STageR, but the structure and data may be different depending on the source.
The content is processed by SharePointBCSMapping.js after the file is in the STageR's processing_modules directory and the storage unit has been configured to use it. For more information, go Configure Storage Unit.
The SharePointBCSMapping.js file can be modified to add, rename, update or delete fields that will be uploaded to SharePoint.  However, the following fields are expected by the BDC connector and therefore cannot be changed:

• action
• docId
• name
• claims_issuer
• use_full_name
• author
• last_modified
• title
• description
• url
• text
• acls

Security Pre-Trimmer Installation