Creating Business Data Catalog Entities in SharePoint Server 2007
Summary: Learn how to create Business Data Catalog entities in Microsoft Office SharePoint Server 2007.
Applies to: 2007 Microsoft Office System, Microsoft Office SharePoint Server 2007
John Peltonen, 3Sharp
April 2007
The Business Data Catalog is a Microsoft Office SharePoint Server 2007 feature that exposes and incorporates line-of-business (LOB) data into other baseline portal functionality, such as lists and enterprise search. To incorporate this data into your portal, you must build an XML file that identifies where the data is stored (either Microsoft SQL Server or a Web service) and what the data looks like (for example, what the data types and primary keys are).
This section walks through building a Business Data Catalog metadata file that defines a simple LOB data entity. The prerequisites are as follows:
To build a Business Data Catalog metadata file that defines a simple LOB data entity, follow these instructions: 1. Create an Empty XML File Begin by creating an empty XML file. To create an empty XML file
2. Define the LOB System Add the following XML to the file (below the XML declaration) to define the LobSystem top-level parameters: <LobSystem Type="Database" Version="1.0.0.01" Name="CRM" xmlns="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog"> </LobSystem> 3. Define Top Level Security Parameters Note: This is optional. You can also configure these parameters in the Business Data Catalog admin pages. Add the following XML to the end of the LobSystem element (before the </LobSystem> end tag). Note that you must update the Principal attribute values with the correct domain and user or group names. <AccessControlList> <AccessControlEntry Principal="your domain\you"> <Right BdcRight="Execute"/> <Right BdcRight="Edit"/> <Right BdcRight="SetPermissions"/> <Right BdcRight="SelectableInClients"/> </AccessControlEntry> <AccessControlEntry Principal="your domain\your BDC users"> <Right BdcRight="Execute"/> <Right BdcRight="SelectableInClients"/> </AccessControlEntry> </AccessControlList> 4. Define the LOB System Instance With a database, the system instance defines the database connection parameters that the Business Data Catalog uses. Add the following XML as a child of the LobSystem element (after the AccessControlList element). Note that you must replace the text your_server_name with the actual server name. <LobSystemInstances> <LobSystemInstance Name="CRMDB"> <Properties> <Property Name="AuthenticationMode" Type="System.String"> PassThrough</Property> <Property Name="DatabaseAccessProvider" Type="System.String"> SqlServer</Property> <Property Name="RdbConnection Data Source" Type="System.String"> your_server_name</Property> <Property Name="RdbConnection Initial Catalog" Type="System.String"> AdventureWorks</Property> <Property Name="RdbConnection Integrated Security" Type= "System.String">SSPI</Property> </Properties> </LobSystemInstance> </LobSystemInstances> Note: A drawback to using pass-through authentication is that the operating system exposes only the user name and password. Therefore, if a company uses two-factor authentication (that is, users are required to have some specific—private—information in addition to a user name and password), you cannot use pass-through authentication. Despite these drawbacks, its simplicity makes pass-through authentication a good candidate for use in a testing environment. If your company is using two-factor authentication and you want to connect the Business Data catalog to a SQL Server database, you can use Single Sign On (SSO). To use SSO, follow either these instructions Step 6 (Optional): Use Single Sign-On to Connect to the AdventureWorks2000 Database (WindowsCredentials), or these instructions How to: Adapt the Samples to Connect to Oracle and Other Databases (RdbCredentials). 5. Define the Customer Entity An entity consists of a title (defined in the Properties element), a unique identifier (which equates to a primary key), and methods that both define the fields of an entity and indicate to the Business Data Catalog how to pull the entity data out of the LOB system. The following steps define an entity named Customer. To define the customer entity
6. Upload the Completed Metadata File into the Shared Service Provider The next step is to upload the completed metadata file into the shared service provider. To upload the completed metadata file to the shared service provider
7. Use the Business Data List Web Part to Show the Customer Data The next step is to use the Business Data List Web Part to show the customer data. To use the Business Data List Web Part to show customer data
The Business Data Catalog is a Microsoft Office SharePoint Server 2007 feature that allows you to include LOB data that is hosted outside of the portal in such items as lists and enterprise search. The Business Data Catalog requires an XML metadata file that defines the connection parameters to the external data source, the various queries (or Web service method calls), and both the input and output parameters of each query or method. To build the metadata file, it is important to understand its structure. However, understanding entities is the most important part of understanding the Business Data Catalog. Entities consist of:
|
Length: 16:33 | Size: 11.0 MB | Type: WMV file
|
- 8/2/2010
- kurobenko
- 5/27/2008
- Ricardo Wilkins
- 6/24/2010
- Thomas Lee
: The metadata object with Name CRMDB and of Type 'LobSystemInstance' has a Property with Name 'AuthenticationMode' that has either an invalid value or Type
- 1/21/2008
- ChandraSekhar Pandyaram
- 8/26/2009
- MuradAkram
I am new to BDC. If the main purpose of the BDC is to get data from database and display on the page, can we just use SP Designer to do it? It can be done in minute. We have to use the right tool for the right job. We don't NEED to write all those xml because we know HOW to do it.
Correct me if I am wrong. :)?
- 11/26/2008
- adfasdf3
- 8/26/2009
- MuradAkram
Hi,
I tried to create BDC by following the steps above by always getting error. Then just remove the AccessControlList block to make it work.<AccessControlList>
<AccessControlEntry Principal="your domain\you">
<Right BdcRight="Execute"/>
<Right BdcRight="Edit"/>
<Right BdcRight="SetPermissions"/>
<Right BdcRight="SelectableInClients"/>
</AccessControlEntry>
<AccessControlEntry Principal="your domain\your BDC users">
<Right BdcRight="Execute"/>
<Right BdcRight="SelectableInClients"/>
</AccessControlEntry>
</AccessControlList>
You can easily set the permission again after successfully upload the BDC.
Thanks,
Alfes
- 10/9/2008
- Alfes
The embedded query in the method element uses "customerID" instead of "CustomerID". This caused the BDC to fail after importing to SSP. Only error message you get is generic. Nice. Transfer the code to a query in SQL Server 2005 Management Studio and you will get an error running the query. Took me 2 hours to figure this out. That and the problem mentioned above -- very sloppy, Microsoft.
I've found the entire BDC learning experience extremely frustrating when relying on Microsoft tutorials.
- 10/2/2008
- HairCompletelyPulledOut

