Basic Setup

Step 1: Download plug-in deployment package

The deployment package zip is located here.  Download it and unzip it.

The following is the directory structure within the zip file:

Image Added

Step 2: Plug-In Setup

Setup steps

Step 2: Model and Content Source 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:
   1. stagingRepositoryUrl: The Host:Port where the STageR is running
   2. sharePointServiceUrl: The Host:port where the SharePoint 2013 Central Administration is running
   3. searchServiceApplicationName: The name of the search service application within SharePoint
   4. stagerFolderPath: The 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
   .\DeployStagerPlugin.ps1 -configurationFilePath ..\config\configurationParameters.xml

   
   

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

Step 3: Model and Content Source Setup

1. Under the \config folder, locate the file named configurationParameters.xml (The one you modified in the previous step) and create a copy of it.
2. Modify the following fields in the new copy:
   1. contentSourceName: The name of the content source that will appear under Search Service Application in SharePoint
   2. storageUnitName: The name of the Storage Unit within STageR where the content will be extracted from
   3. storageUnitScope: The scope within the Storage Unit.  The value of 'publisher' is recomended 
   4. maxBatchesToProcess: The maximum number of batches processed by the plug-in per execution
   5. batchSize: The maximum number of documents per batch processed
   6. certPath: The path to the .p12 or .pfx file if SSL is needed.  Leave empty if not
   7. certPassword:  The password to the .p12/.pfx file if SSL is needed.  Leave empty if not
   8. claimsIssuer:  The issuer of the access claims.  Accepted values are 'public' for no issuer, 'aspire' to use Aspire Group Expansion or 'windows'
   9. 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:

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

   
   

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

Step 4: Schedule the Content Source crawls

1. Go to SharePoint Central Admin