Toggle mobile navigation

Toggle search

Close search

BCS, External & LOB Systems Integration Strategies for SharePoint 2013 & Office 365

Posted by Errin O'Connor on Mar, 13, 2015 03:03

BCS, External & LOB Systems Integration Strategies for SharePoint 2013 & Office 365

SharePoint Business Connectivity Services (BCS) provides for the ability to integrate with data that is stored outside of SharePoint in to SharePoint 2013 as well as Office 365 and Microsoft solutions.

The BCS enables for data to be integrated into SharePoint, Office 365, SharePoint Online and other Microsoft solutions in reports or lists for BI initiatives or into SharePoint 2013’s search to be able to provide your users with search results from data across the enterprise using native elements such as the SharePoint 2013 search’s connector framework, as shown in image below.

The following image is an overview of SharePoint 2013 search’s connector framework and its integration with the BCS:

BCS, External & LOB Systems Integration Strategies for SharePoint 2013 & Office 365

SharePoint Business Connectivity Services (BCS) provides for the ability to integrate with data that is stored outside of SharePoint in to SharePoint 2013 as well as Office 365 and Microsoft solutions.

The BCS enables for data to be integrated into SharePoint, Office 365, SharePoint Online and other Microsoft solutions in reports or lists for BI initiatives or into SharePoint 2013’s search to be able to provide your users with search results from data across the enterprise using native elements such as the SharePoint 2013 search’s connector framework, as shown in image below.

The following image is an overview of SharePoint 2013 search’s connector framework and its integration with the BCS:

The BCS provides for the management of managing of authentication to external systems and can also indexing data in external systems for searching on through SharePoint 2013 while being able to still “security trim” search results to only users with access to “their specific data.”

There has also been a major update around the BCS being compatible with the cloud and hybrid cloud to be able to provide support for the notification of events in external systems as well as the inclusion of BCS support in apps.

Office 365 supports both WCF and OData based BCS entities which are the most scalable approach and architecture for systems that are on separate environments and accessed via HTTP or HTTPS.

Office 365 also support the secure store service and the BCS and secure store are managed at a tenant level which will meet your scalability as well as hybrid cloud federated security requirements for any future initiatives.

BCS and External Events “from the Trenches”

SharePoint 2013 adds a model for subscribing to events triggered in external systems as you can develop custom code for these event receivers in a similar manner to how a SharePoint event receiver would be developed.

With the ability to subscribe to events triggered in external systems with custom event receivers as well as thee capability to access applications and data sources that are exposed and accessible via WCF services as well as OData endpoints, as shown in image below, you now have the ability to take most any BI, reporting or enterprise-wide search initiative.

SharePoint 2013 apps can include external content type definitions and the accompanying BCS models within them although they are limited to one per app and you should keep in mind that the OData connector is the only connector allowed for this type of connection.

The image below is an overview of the BCS connecting with external events.

The BCS and OData

There are several factors to keep in mind when planning the user of OData with the BCS which are as follows:

■  OData is an available source in Visual Studio but is not available in SharePoint Designer 2013

■  OData provides the ability for a lighter payload of data which benefits the underlying network latency and cloud, hybrid cloud as well as mobile initiatives

■  An OData feed can be created via a WCF data Service as well as via a WebAPI