getting started sharepoint “2013” web view10/07/2014 · sharepoint 2013 has a...

Prepared by

Sriram BalaSharePoint Practice

Microsoft SharePoint 2013 -

CreatingBusiness Continuity ServicesVerified Against Build #15.0.4128.1014

Configuring Business Continuity Services 2

Table of Contents

Configuring Business Continuity Services.............................................................................3Components of BCS...........................................................................................................3Using external content types in BCS.................................................................................4

Developing solutions using BCS............................................................................................5About Business Connectivity Services installation scenarios.............................................5Prerequisites......................................................................................................................6On-premises deployment..................................................................................................6What these procedures help you deploy...........................................................................6

How to use these procedures and a roadmap of the procedures.........................................8Cloud-only deployment.........................................................................................................9What these procedures help you deploy............................................................................10Hybrid deployment.............................................................................................................12

What these procedures help you deploy.........................................................................12How to use these procedures..........................................................................................14

Roadmap of the procedures.........................................................................................15


Configuring Business Continuity ServicesSharePoint 2013 has a hub for creating rich productivity and collaboration solutions that can work with a variety of external systems. Business Connectivity Services (BCS) provides the infrastructure that enables SharePoint 2013 to bring data from those external systems into a central system. By providing a flexible and extensible means to describe the external system data source and how to interact with it, BCS makes a compelling argument for using SharePoint 2013 as the central interface for working with legacy business systems in addition to new apps for SharePoint.BCS provides mechanisms to enable experienced users, developers, and business unit IT professionals

to do the following much more easily:

Reveal external data from enterprise applications, web services, and OData services in

SharePoint Server 2013 and in rich-client Office applications.

Provide Office-type behaviors (such as Contacts, Tasks, and Appointments) and capabilities to

external data and services.

Provide complete interaction with the data, including write-back capabilities from Office

applications and SharePoint Server to the underlying external system data and business objects.

Enable offline use of external data and processes.

Bridge the unstructured world of documents and people and the appropriate structured data that

is locked in external systems.

Components of BCS


Figure Business Connectivity Services feature set

Using external content types in BCSExternal content types are the core of BCS. They enable you to manage and reuse the metadata and

behaviors of a business entity, such as Customer or Order, from a central location. They enable users to

interact with that external data and process it in a more meaningful way.

For example, consider a business entity, such as a customer. You want to be able to pull data from your

proprietary database and work with it in SharePoint. You also want to be able to allow your field

salespeople to take data offline in Outlook 2013. Or, you might want the user to be able to choose a


customer from a list of customers in an orders contract document inside Microsoft Word. To make all

this possible, you can create a single external content type and then reuse it anywhere you need it.

Developing solutions using BCSYou can build a broad spectrum of solutions in SharePoint 2013 by using BCS. These include simple

solutions that rely on native capabilities with little or no customization, intermediate solutions that

involve customizing features in SharePoint 2013 and Office 2013, and advanced solutions that enable

complex scenarios and rich applications that extend their functionality. Advanced solutions involve

writing code using Visual Studio. They can be either complete end-to-end solutions, or reusable code-

based components that are included in an intermediate solution.

BCS empowers business users to quickly and easily address a broad array of external data needs by

using a web browser and a Microsoft Office client application, such as Word or Excel. Without writing

code, users can assemble composite solutions by using BCS features, such as external lists and external

data columns, and reusable BCS components, which are created by developers and approved by IT, in

Office client applications and SharePoint sites. These solutions enable business users (and their teams)

to work with external data as easily as with SharePoint data, either offline or connected, or directly in

Office 2013.

About Business Connectivity Services installation scenariosEvery Business Connectivity Services solution is unique because each business has unique data

integration problems that it solves with Business Connectivity Services. The solutions can range from

something simple and straightforward that a power user or IT professional (who has the appropriate

permissions) can perform by themselves, to complex solutions that require developer, IT professional,

and end-user solution development involvement. This guide presents the configuration procedures in

common scenarios.

On-premises deployment All the Business Connectivity Services components are under your

organizations control behind your firewall.

Cloud-only deployment All the Business Connectivity Services components are in SharePoint

Online.

http://technet.microsoft.com/en-us/library/fp161283(v=office.15).aspx#sectioncloud

http://technet.microsoft.com/en-us/library/fp161283(v=office.15).aspx#sectiononprem


Hybrid deployment SharePoint Online uses Business Connectivity Services to connect to data

that lives in the cloud.

PrerequisitesBefore you begin with any Business Connectivity Services scenario configuration, make sure that you

have read Overview of Business Connectivity Services in SharePoint 2013 and completed the steps in

Plan a Business Connectivity Services solution in SharePoint 2013.

On-premises deploymentThe procedures in Deploy a Business Connectivity Services on-premises solution in SharePoint 2013

show you how to deploy a solution that involves the following:

A Business Connectivity Services infrastructure that is on your corporate network.

Information workers who access the Business Connectivity Services solution are on your

corporate network.

External content that is surfaced in SharePoint as an external list.

External content that is synchronized into Outlook for offline use.

Accessing external data that is in SQL Server database on your corporate network.

SharePoint Designer 2013 to create the external content type for the SQL Server data source.

The Secure Store Service to manage mapping of user credentials to group credentials for

accessing the external systems.

What these procedures help you deploy

Business Connectivity Services is a centralized infrastructure in SharePoint 2013 and Office 2013 that

enables you to integrate data that is not in SharePoint products and Office 2013 into SharePoint products

and Office 2013. BCS implementations take many different forms, including the on-premises form.

These procedures show you how to install and configure BCS to integrate data from an on-premises

SQL data source into a SharePoint products external list and into Outlook. For the purposes of building

out this scenario, we use the AdventureWorks sample SQL database. The solution looks as shown in the

following diagram.

Figure: On-premises BCS solution

http://technet.microsoft.com/en-us/library/jj219584(v=office.15).aspx


http://technet.microsoft.com/en-us/library/ee661740(v=office.15).aspx

http://technet.microsoft.com/en-us/library/fp161283(v=office.15).aspx#sectionhybrid


1. A user goes to an external list on a SharePoint site. The external list creates a request for data by

using the user’s Windows credentials.

2. The request is sent to the BDC runtime in the SharePoint farm.


3. The BDC runtime accesses the external content type for the list (in the BDC Metadata Store) to

see how to access the external system and which operations can be performed. By using either

the user’s credentials or the credentials from the Secure Store (as defined in the external content

type), the BDC runtime passes the request to a connector that can handle the request, in this case

the SQL connector.

4. The SQL connector accesses the external data source and retrieves the data, and applies any

formatting and filtering as specified in the external content type. The data is passed back through

the request chain to the list where the user can interact with it.

5. The user wants to take this data on a portable computer in Outlook so the user can use the

Connect to Outlook feature on the external list to take the data offline.

6. The Click Once installation runs and installs the required BDC model on the client. This lets the

BDC Client-Side Runtime access the external data directly.

7. Outlook then connects to the external data by using the configuration in the BDC model and

synchronizes it into an Outlook SharePoint external list, formatted as a contacts list.

8. The user can then interact with the contact data, and any changes that the user makes can be

written back to the external data source either by an on-demand synch or by waiting six hours for

the automated synchronization.

How to use these procedures and a roadmap of the proceduresThe steps to completely deploy this scenario are presented in smaller procedures. Some of the

procedures are on TechNet, some are on Office.com, and some are on MSDN. Each procedure is

numbered indicating its position in the overall sequence. At the beginning and end of each procedure,

links direct you to the preceding and following steps. The following list contains links to all of the

procedures, in proper order, for your reference. You must follow them in sequence to build out the

scenario. You can also use these procedures individually to build out your own unique scenarios. When

you are assembling individual procedures to build out your own scenarios, be sure to test the entire set

of procedures, in order, in a lab setting before you attempt them in production.

1. Prerequisites for deploying a Business Connectivity Services on-premises solution in SharePoint

2013




2. Create database logins for a Business Connectivity Services on-premises solution in SharePoint

2013

3. Start the Business Data Connectivity service for a Business Connectivity Services on-premises

solution in SharePoint 2013

4. Create the Business Data Connectivity service application in SharePoint 2013

5. Set permissions on the BCS Metadata Store for a Business Connectivity Services on-premises


6. Configure the Secure Store Service for a Business Connectivity Services on-premises solution in

SharePoint 2013

7. Create an external content type for a Business Connectivity Services on-premises solution in

SharePoint 2013

8. Configure permission on an external content type for a Business Connectivity Services on-

premises solution in SharePoint 2013

9. Create an external list for a Business Connectivity Services on-premises solution in SharePoint

2013

10. Manage user permissions on an external list for a Business Connectivity Services on-premises


11. Connect an external list to Outlook for a Business Connectivity Services on-premises solution in

SharePoint 2013

12. Verify offline access and synchronization of external data in Outlook for a Business

Connectivity Services on-premises solution in SharePoint 2013

Cloud-only deployment

The procedures in Deploy a Business Connectivity Services cloud-only solution in SharePoint 2013

show you how to deploy a solution that involves a Business Connectivity Services infrastructure that is

in SharePoint Online.

The following scenario shows how to create a Microsoft Business Connectivity Services solution in

SharePoint Online to access Windows Azure SQL Database. You will learn how to:

Configure the Business Connectivity Services in SharePoint Online.

Configure a Secure Store Service target application to map credentials between SharePoint

Online and SQL Database.
























Create an external content type by using SharePoint Designer 2010.

Create an external list in SharePoint Online.

Grant permissions to manage the external content type.


Business Connectivity Services is a shared service in SharePoint Online. In SharePoint Online you can

make external data visible through external lists or through apps for SharePoint. In this example, we use

external lists. The solution looks as shown in the following diagram.

Figure: Cloud-only BCS solution


1. The user logs on to SharePoint Online and opens an external list that the user has rights to.

2. The Business Data Connectivity service runtime queries the external content type for the list in

the Business Data Connectivity service metadata store to learn how to access the external

system, which operations can be performed, and which credentials to use. The external content

type tells the Business Data Connectivity service runtime to retrieve the necessary credentials

from the Secure Store.


3. The Business Data Connectivity service runtime passes the request (SOAP over HTTP) to the

endpoint of the SQL Azure Windows Communication Foundation (WCF) service.

4. The SQL Azure service returns the data in a SOAP envelope.

5. The SharePoint Online site displays the external list in the user’s browser. The user can then

perform all the configured operations on the data source for which the user has permissions.

Hybrid deployment

The procedures in Deploy a Business Connectivity Services hybrid solution in SharePoint 2013 shows

you how to publish on-premises data to an external list or app for SharePoint in SharePoint Online.

The Microsoft Business Connectivity Services (BCS) hybrid deployment scenario allows you to

securely publish on-premises data to an external list or app for SharePoint in SharePoint Online. From

there users can view and edit the data, depending on the permissions that they have.

The BCS hybrid scenario requires successful deployment of either a one-way inbound or a two-way

SharePoint hybrid configuration. For more information about how to plan and configure a SharePoint

Server 2013 hybrid environment, see Hybrid for SharePoint Server 2013.

To configure a hybrid SharePoint environment, you must have a combination of expert skills and significant hands-on experience with SharePoint Server 2013, SharePoint Online, and related products and technologies. We recommend that you engage Microsoft Consulting Services to provide technical guidance and support during the design and deployment of your hybrid environment.For more information about Microsoft Consulting Services, see Microsoft Services.You must have a successful implementation of the base SharePoint hybrid scenario before you can continue with the BCS hybrid implementation. If you don’t, see Hybrid for SharePoint Server 2013.


Business Connectivity Services (BCS) is a centralized infrastructure in SharePoint Server 2013, Office

2013, and SharePoint Online that enables you to integrate data that is not in SharePoint products and

Office 2013 into SharePoint products. BCS implementations take many forms. This includes this hybrid

form that uses SharePoint Online and SharePoint 2013 on-premises. These procedures show how to



http://www.microsoft.com/en-us/microsoftservices/deploy.aspx


http://technet.microsoft.com/en-us/library/dn197239(v=office.15).aspx


install and configure BCS to integrate data from an on-premises OData service endpoint into a

SharePoint Online tenancy. For this scenario, we use the AdventureWorks sample SQL database and

created an OData service head for the database. The solution looks as shown in the following diagram.

For more information about SharePoint hybrid configurations and how data and authentication flow in

the SharePoint BCS hybrid solution, see Hybrid for SharePoint Server 2013.

Figure: Hybrid BCS solution

1. An information worker logs on to the SharePoint Online tenancy by using the information

worker's federated account and opens an app for SharePoint or external list that needs data from

an on-premises OData data source. OData is an open protocol that is used to query and update

data. For more information about OData, see Introducing OData: Data Access for the Web, the

cloud, mobile devices and more in the MSDN Library.

http://go.microsoft.com/fwlink/p/?LinkId=245650

http://go.microsoft.com/fwlink/p/?LinkId=245650

http://go.microsoft.com/fwlink/?LinkID=271740


2. The external list creates a request for the data and sends it to Business Connectivity Services.

Business Connectivity Services looks at the connection settings object to see how to connect to

the data source and which credentials to use.

3. Business Connectivity Services retrieves two sets of credentials.

1. Business Connectivity Services retrieves the Secure Channel certificate from the Secure

Store in SharePoint Online. This is used for SharePoint Online authentication to the

reverse proxy.

2. Business Connectivity Services retrieves an OAuth token from the Windows Azure AD

Service. This is used for user authentication to the SharePoint 2013 on-premises farm.

You gain access to the Windows Azure AD service with your SharePoint Online

subscription. It is a security token service that manages security tokens for users of

SharePoint Online. For more information about the Access Control Service, see Access

Control Service 2.0 in the MSDN Library.

4. Business Connectivity Services sends an HTTPS request to the published endpoint for the data

source. The request includes the client certificate from the Secure Store and the OAuth token and

a request for the data. The reverse proxy authenticates the request by using the client certificate

and forwards it to the on-premises SharePoint 2013 farm. For more information about publishing

SharePoint to the Internet, see SharePoint publishing solution guide in the Forefront Technical

Library.

5. The on-premises farm retrieves the user’s cloud identity from the OAuth token (for example,

[email protected]), and through the Client Side Object Model (CSOM) code, maps it to

their on-premises identity (for example, Contoso\user123). The on-premises credentials are

mapped to credentials that have access to the external data via a Secure Store target application.

6. The on-premises Business Connectivity Services forwards the request to the OData Service

endpoint. The OData Service authenticates the request (via IIS) and returns the data, which is

passed back through the chain to the external list for the user to work with.

How to use these procedures

The steps to completely deploy this scenario are presented in smaller procedures. Some of the

procedures are on TechNet, some are on Office.com, and some are on MSDN. Each procedure is

http://go.microsoft.com/fwlink/?LinkId=253268




numbered indicating its position in the overall sequence. At the beginning and end of each procedure,

links direct you to the previous and following steps. The following list contains links to all of the

procedures, in required order, for your reference. Be aware that this list includes the steps to deploy an

external list and an app for SharePoint. You can deploy one or the other or both depending on your

needs. You should skip the steps for whichever configuration that you don’t want to deploy. You must

follow them in sequence to build out the scenario. You can also use these procedures individually for

your own unique scenarios. When you assemble individual procedures to build out your own scenarios,

it is important that you test the complete set of procedures, in order, in a lab setting before you try them

in production.

If you only want to deploy the BCS hybrid scenario by using an external list, perform all the procedures

in the following order.

Prepare the on-premises environment for the Business Connectivity Services hybrid scenario

Create an external list for the Business Connectivity Services hybrid scenario

Validate the Business Connectivity Services hybrid scenario

If you only want to deploy the BCS hybrid scenario by using an app for SharePoint, perform all the

procedures in the following order.

Prepare the on-premises environment for the Business Connectivity Services hybrid scenario

Create an external list for the Business Connectivity Services hybrid scenario

Deploy the Business Connectivity Services hybrid scenario as an app for SharePoint

Validate the Business Connectivity Services hybrid scenario

If you want to use both external lists and an app for SharePoint, perform all of the steps in order and do

not skip any steps.

Roadmap of the proceduresStep number

Link to procedure Description of procedureWhere the procedure is performed

1 Prepare the on-premises

environment for the

Business Connectivity

Prepare the on-premises account that

you use to access the OData service

endpoint (ODataAccount) and the

In your on-premises Active

Directory domain.











Services hybrid scenario

Windows group (ODataGroup) that

you use to control access to the OData

service endpoint.

2

Create an on-premises

Secure Store Service

target application for the



Associate the security group

(ODataGroup) to the account

(Account) that you created in step 1

via a Secure Store Service target app.

In your on-premises Secure

Store.

3

Create and configure an

OData service endpoint

for the Business

Connectivity Services

hybrid scenario

Create the OData service endpoint,

assign permissions and verify that the

OData service endpoint is publishing

the external data.

You create the OData

endpoint with Visual Studio

2012 in your on-premises

environment and you browse

to it from inside your

company intranet.

4

Prepare the SharePoint

Online environment for

the Business Connectivity


Identify or create the SharePoint

Online site where users will interact

with the external data and create an

App Catalog if it is necessary.

Prepare a site in your

SharePoint Online tenancy

for the app for SharePoint or

external list.

5

Configure permissions on

the SharePoint Online

BDC Metadata Store for



Prepare the Business Data

Connectivity (BDC) Metadata store

for manually imported BDCM

models.

You set permissions on the

BDC metadata store in your

SharePoint Online tenancy.

6

Validate external access to

reverse proxy published

URL for the Business


hybrid scenario

Browse to the externally published

address and log on as a federated user.

You browse to the externally

published site through the

Internet from a client

computer that is outside your

company intranet.

7 Create and configure the Create a connection settings object You create the connection



















connection settings object

for the Business


hybrid scenario

that BCS in your SharePoint Online

tenancy will use to connect to the on-

premises OData service endpoint.

settings object in your


8

Create and configure the

external content type for



Use Visual Studio 2012 to create and

configure the external content type for

the OData service endpoint.

You create the external

content type with Visual

Studio 2012 from inside your

company intranet.

9.0

Deploy the Business


hybrid scenario as an

external list

If you are creating an external list for

the on-premises data, then follow

steps 9.1, 9.2 and 9.3.

9.1

Extract an external content

type to a BDCM file for


Services hybrid Scenario

Manually extract the BDCM model to

a file and prepare to import it into

your SharePoint Online tenancy.

In Visual Studio 2012 in

your on-premises

environment.

9.2

Import the BDCM file into

SharePoint Online BDC

Metadata Store for the



Import the BDCM into the BDC

metadata store of your SharePoint

Online tenancy.

In the metadata store of your


9.3

Create an external list for



Create an external list and associate it

with the external content type that you

imported in step 9.2. After you finish

this step go to Validate the Business

Connectivity Services hybrid

scenario.

You create this list in the

SharePoint Online site that

you prepared in step 4.

10.0 Deploy the Business


If you are deploying an app for

SharePoint for users to access the
























hybrid scenario as an app

for SharePoint

external data, follow steps 10.0 and

10.1.

10.1

Deploy an app for

SharePoint to SharePoint

Online by using Visual

Studio for the Business


hybrid scenario

Deploy the app for SharePoint to the

App Catalog. After you finish this

step, go to Validate the Business

Connectivity Services hybrid

scenario.

You use Visual Studio 2012

from your on-premises

environment to automatically

deploy the app for

SharePoint.

11

Validate the Business


hybrid scenario

Validate read and write access to the

on-premises data through your

external list or app for SharePoint,

and test security.












getting started sharepoint “2013” web view10/07/2014 · sharepoint 2013 has a...

Documents