Windows azure bcs
•Download as PPTX, PDF•
1 like•361 views
A presentation about consuming Windows Azure Data inside SharePoint via Business Connectivity Services (BCS for short).
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Windows azure bcs
Similar to Windows azure bcs (20)
More from Kiril Iliev
Recently uploaded
Recently uploaded (14)
Windows azure bcs
- 1. (This starts the presentation.)
- 3. Leveraging Windows Azure Data with SharePoint Business Connectivity Services KIRIL ILIEV : SHAREPOINT APPLICATION DEVELOPER IN PG kiliev@infragistics.com / @kiliev / @infragistics
- 4. Agenda 1 / Overview of Windows Azure Datamarket 2 / Overview of SharePoint Business Connectivity Services 3 / Present the WCF service 4 / DEMO: Consume the service in SharePoint External List 5/ Tips and Tricks 6 / Resources & Wrap Up 7/Q&A
- 5. Windows Azure Datamarket premium datasets / SaaS applications / diverse content type
- 6. Windows AzureTM Datamarket provides a wide range of authoritative datasets
- 7. Prerequisites for developing Windows Azure Applications Windows Live ID Developer account at https://datamarket.azure.com/ Add dataset(s) to your account
- 8. (Demo the EDR dataset.)
- 9. SharePoint Business Connectivity Services business connectivity services / external content type
- 10. SharePoint BCS External Content Types Reusability Simplified access to external systems Built-in SharePoint behavior Secure access Simplified maintenance *Source: MSDN Blog
- 12. (Demo the WCF service.)
- 13. Two possible solutions for creating the ECT.
- 14. Tips and Tricks
- 15. (This starts the presentation of the tricks on a VM.)
- 16. Resources and Wrap up 1 / Overview of Windows Azure Datamarket 2 / Overview of SharePoint Business Connectivity Services 3 / Present the WCF service 4 / DEMO: Consume the service in SharePoint External List 5/ Tips and Tricks
- 18. Q&A
Editor's Notes
- Windows Azure Marketplace DataMarket offers a wide range of content from authoritative commercial and public sources in a single marketplace. Using the SharePoint BCS we will consume the data inside our SharePoint application to provide up-to-date information.
- Briefly explain the requirements for developing Azure applications.
- Demonstrate the dataset to be used.For the purpose of this demonstration we will be using the EDR’s Environmental Hazard Rank dataset.Present the dataset in the browser:https://datamarket.azure.com/dataset/d8161344-f755-4a86-83e6-db9a89f06efdExplain about the query:https://datamarket.azure.com/dataset/explore/d8161344-f755-4a86-83e6-db9a89f06efdExplain about the input parameters
- Reusability An external content type is a reusable data definition of a business entity. After you create it, you can use it with any of the Presentation Features in BCS to provide a rich user experience to interact with external data.Simplified access to external systems External content types enable information workers to assemble business solutions without having to handle the complexities of those systems, such as connectivity information or programmability interfaces. After an experienced user or a developer creates an external content type, it is available to any user for use in any way they need (provided they have the permissions to perform that operation and access the external data). However, the user does not need to know anything about the location of the external data or how to connect to it.Built-in SharePoint behavior External content types provide SharePoint behaviors (such as lists and Web Parts) and capabilities (such as the ability to search or work offline) to external data and services, so users can work in their familiar work environments without having to hunt for data or learn and interact with different (and proprietary) user interfaces.Secure access External content types adhere to the security put in place by both the external system and SharePoint products and technologies. You can have full control of who accesses what data by configuring security in SharePoint.Simplified maintenance Because external content types can be created once and used by multiple solutions in various scenarios, you can manage them easily. For example, you can manage their access permissions and connection and data definitions in one central location.
- Demo in the following order:1/ Show the solution in VS11 BETA. HINT (if there is enough time): Show what’s new in Publishing window2/ Explain about the service and Azure authentication (Unique User ID and Windows Live ID)3/ The service will be deployed in the local IIS site. NOTE: Emphasis that the IIS site that will be running the service must be running on .NET Framework 4
- Now once the service is deployed, we have a couple of solutions to consume it in SharePoint.SharePoint Designer – declaratively created and directly saved into the BDC Metadata Store in SharePoint.Visual Studio – More flexible and structured approach. Deployed as a .NET assembly into the SharePoint farm, then added as a feature to SharePoint and ECT is also added to the BDC Metadata Store. Requires farm administrator (i.e. more permissions) for deployment. Advantages are that it gives more possibilities for managing and verifying the data.Show the BDC model pre-configured in the SharePoint Designer.In our case, we will use Visual Studio 2011 BETA developing a BDC model.
- Trick 1: If your data messages are is too large, you will need to add <bindings> <webHttpBinding> <binding name="msgSize" maxReceivedMessageSize="20971520" maxBufferSize="20971520" /> </webHttpBinding> </bindings>You can also use the ChannelFactoryclass inside your code.In <system.serviceModel> in your web.config file for the SharePoint application.Trick 2: Demonstrate how to access External list as anonymous user.Sometimes you might have a public-facing SharePoint web application and you want to allow anonymous users to see your external list. OK, for this purpose you add the NT Authority user in your BCS, right? Well, if you try to do that in Central Administration, SharePoint will not find the user. For this purpose, you will need to add a fictive users to your ECT, then export it and open it with a text-compatible viewer – in our case this is NotePad++. Find and Replace the fictive user with the “NT Authority/Anonymous User”, then import it back to the metadata store. Test it!