###BeginCaseStudy###
Topic 1, Tailspin Toys
Background
You are planning a SharePoint deployment. The new farm will host several business solutions including:
www.TailspinToys.com
Tailspin360.TaiIspinToys.com
MyTailspin.TailspinToys.com
All employees have Active Directory Domain Service (AD DS) accounts. Members of the SalesUsers AD DS
security group are the only users with permissions to create My Sites sites.
Business Requirements
www.TailspinToys.com
www.TailspinToys.com is an Internet business site that will provide eCommerce capabilities including a product
catalog, a shopping cart, and an account settings page.
Tailspin360.TailspinToys.com
Tailspin360.TailspinToys.com provides a business intelligence (BI) solution for the Sales team. It must allow
users to share Microsoft Excel workbooks and build dashboards.
Tailspin360.TailspinToys.com accesses data that is located in various repositories including Microsoft SQL
Server.
MyTailspin.TailspinToys.com
MyTailspin.TailspinToys.com is a social collaboration environment that provides micro-blogging, file and video
sharing, and the ability to create personal blogs and wikis for Tailspin Toys employees.
Technical Requirements
General
The farm must be made fault tolerant by using virtualization.
The farm must include two front-end web servers.
Page requests must be distributed equally across the front-end web servers.
All content must remain available to users if one of the front-end web servers becomes unavailable.
All Sales department employees are members of the SalesUsers group.
All customer, order, and product information will be stored in tables in a Microsoft SQL Server database.
The User Profile service application is provisioned but not configured.
www.TailspinToys.com
You must create a version of the site that provides an optimized experience for Windows Phone devices.
You have created a device channel that detects the user-agent.
The website must support English (United States), Spanish (Mexico), and German (Germany). All content is
authored in English and then translated into Spanish and German by an outside vendor. Translations are
performed by humans.
Tailspin360.TailspinToys.com
The site must be accessible only to members of the Sales team.
Users must be able to access order information that is stored in a SQL Server database.
Developers must be able to import Business Connectivity Services (BCS) models by using Central
Administration.
The salesAccess shared domain account has permissions to read data from the database.
Excel workbooks published to a document library app must be opened in a browser. Excel workbooks in
other locations must open in Excel.
MyTailspin.TailspinToys.com
You need to provision a SharePoint environment that supports My Sites for an enterprise.
You need to ensure the SharePoint Server configuration supports the ability to create individual site
collections the first time a user accesses the My Site page.All users need permissions to create My Sites sites.
###EndCaseStudy###
You need to configure the BCS model to access data.
What should you do?
A.
Create an external content type and enter the target application friendly name in the Secure Store
Application ID field
B.
Create an external content type and enter the target application ID in the Secure Store Application ID field.
C.
Create an external content type and choose the Connect with impersonated custom identity option. Enter
the target application friendly name of the Secure Store target application.
D.
Create an external content type and choose the Connect with user’s identity option.
Explanation:
Create an external content type for a Business Connectivity Services on-premises solution in SharePoint 2013
1. Add a connection using SQL Server as the External Data Source Type.
2. In the Set the Database Server box, enter <The name of the database server> and in the Set the Database
Name box, enter AdventureWorks2008R2.
3. Optionally, in the Name box, enter AdventureWorks Sample Database.
4. Select Connect with Impersonated Custom Identity.
5. In the Secure Store Application ID box, enter AWTargetAppID.
http://technet.microsoft.com/en-us/library/jj683110.aspx
Creating the External Content Types
External content types are stored and managed by the Business Data Connectivity (BDC) service application.
You can create external content types by using interactive tools in SharePoint Designer 2010. Alternatively, you
can import predefined external content types by uploading a Business Data Connectivity Model (.bdcm) file to
the Central Administration Web site.
Note: The install script for the external list reference implementation uses a .bdcm file to create the external
content types required by the solution. You can export your external content types as a .bdcm file from
SharePoint Designer 2010 or the SharePoint Central Administration web site.
Essentially, an external content type consists of two components: a connection to an external data source, and
a series of operation definitions (commonly referred to as stereotyped operations) on the external data. When
you create a connection, you first identify the type of data source.NET type, SQL Server, or Windows
Communication Foundation (WCF) Service. For a SQL Server data source, you must specify the database
server, the database name, and the type of impersonation. SQL Server connections can use the following
different types of impersonation:
1. Connect with user’s identity. The BDC uses the identity of the SharePoint user who requested the external
data to authenticate with the data source.
2. Connect with impersonated Windows identity. The BDC sends the identity of the caller to the Secure Store
Service (SSS). The SSS supplies the Windows credentials that are mapped to the identity of the caller. The
BDC uses the mapped Windows credentials to authenticate with the data source.
3. Connection with impersonated custom identity. The BDC sends the identity of the caller to the Secure StoreService (SSS). The SSS supplies a set of custom credentialssuch as a Forms authentication username and
passwordthat are mapped to the identity of the caller. The BDC uses the mapped custom credentials to
authenticate with the data source.
Note: If you want to use an impersonated Windows identity or an impersonated custom identity, you must
specify the target application ID when you configure the connection. The SSS uses the target application ID to
organize credential mappings.
The external list reference implementation could not use the connect with user’s identity approach because the
requests for external data originate from the sandbox. When the BDC receives a request that originates from
the sandbox, the request is made using the identity of the user code proxy service, rather than the identity of
the user. Instead, we used the connect with impersonated Windows identity approach to authenticate to the
Vendor Management database. The following image shows the connection properties for the external content
types in the external list reference implementation.
http://msdn.microsoft.com/en-us/library/ff798448.aspx