Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

 

Introduction


The

STageR

StageR BDC

Plug-In

Plugin for SharePoint

2013 

2013 and 2016 will enable both SharePoint 2013 and 2016 to absorb documents into its index through a .Net

Assembly BDC Connector

Assembly Business Data Connectivity (BDCconnector

Features

Some of the features of

the STageR Plug-In

the StageR Plugin include:

  • Tried and tested approach of using a .Net Assembly SharePoint BDC Connector as a means of integration.
  • Encapsulated functionality.
 SharePoint
  • SharePoint is agnostic of the underlying implementation within the
plug-in
  • plugin.
  • Secure communication with
STageR
  • StageR via SSL certificates.
  • Flexible configuration of fields that
get
  • are ingested into SharePoint.


 

Panel

On this page:

Table of Contents

Restrictions

Important limitations and assumptions of the plugin:

  • Installation of the plug-in plugin requires administrator Administrator permissions to run the deployment scripts from the SharePoint Management Shell (PowerShell).
  • While a single installation of the plug-inplugin's .wsp file is necessary, a separate execution of the model deployment script is needed for each different Content Source that was is published into STageRStageR.


Architecture


Image RemovedImage Added

SharePoint

2013

Components

StagerBDCPlugin

The plugin is deployed as a .wsp file that gets deployed as a global farm solution.  It It implements the SharePoint 's BDC standard for custom connectors and gets executed from a SharePoint content source to extract the contents from STageR StageR and hand them to SharePoint for indexing.

Security Trimming

Security trimming is available within SharePoint 2013 itself. To make this work, a SecurityTrimmerPre interface must be created (see SharePoint Security Pre-Trimmer 3.2).

, see [security trimming for Search in SharePoint Server 2013]. The ISecurityTrimmerPre interface adds "claims" to the query , prior to the security trimming, so it executes “pre” (prior to) the security trimmer. With the exception of deny ACLs, the function of the ISecurityTrimmerPre module is always to add always add results to the result set, not rather than to remove them. In this sense, it is the opposite of a security trimmer.What

Warning

It is critical to understand

is,

that if the ISecurityTrimmerPre interface malfunctions, then you get no secure search results. (If it

were doing

performed "classic" security trimming

,

and

it

malfunctioned, then you would get back extra unauthorized results.) On each search request, the Security Pre-Trimmer is invoked to enhance the search query with ACL information. This information is retrieved from an Aspire

group expander

Group Expander (LDAP, Lotus Notes ...)