AdventureWorks SQL Server 2000 Sample

  • Article

To get you started authoring metadata, the Microsoft Office SharePoint Server 2007 software development kit (SDK) provides sample XML that defines the metadata for the Customers, SalesOrders, and Products mini-scenario in AdventureWorks2000, a sample Microsoft SQL Server 2000 database.

The AdventureWorks2000 sample XML defines three entities: Product, Customer, and SalesOrder. To keep the sample easy to understand, the Customer entity is based on the Individual table in the AdventureWorks2000 database. The Product and SalesOrder entities are based on the Product and SalesOrder tables, respectively. There is an association between the Customer and SalesOrder entities to get the sales orders for a given customer. The Product entity defines an IDEnumerator method for indexing purposes. Product and Customer entities also define some actions.

The following topics walk you through the concepts described in Business Data Catalog: Metadata Model and help you write your own AdventureWorks2000 metadata for the scenario previously described:

Important

The default installation of SQL Server 2000 does not include the AdventureWorks2000 database. Download the Adventure Works Cycles Database 2000 sample database from the Microsoft Download Center. Also, install the database on the same computer on which Office SharePoint Server 2007 is installed, to make it easier to set up authentication.

This SDK also provides the complete XML for the AdventureWorks2000 mini-scenario in the following sample topics: Sample: AdventureWorks2000 PassThrough Metadata and Sample: AdventureWorks2000 Single Sign-On Metadata. We provide two versions of the XML because one uses PassThrough authentication for authenticating to the AdventureWorks database. This version is easier for new users to set up and test. The other sample uses single sign-on (SSO), which is a slightly more complex scenario to set up.

Note

From a metadata authoring perspective, the only difference between the two samples is in the metadata for the LOBSystemInstance object. The LOBSystemInstance object defines the connection parameters and the authentication settings. The rest of the metadata is identical in both samples. .

Testing the Metadata provides instructions for testing the metadata by creating Business Data Web Parts and Business Data columns.

The following procedures help you register the AdventureWorks2000 metadata in the Business Data Catalog and test the business data features.

To test the AdventureWorks sample metadata using PassThrough authentication

  1. Create a text file and save it as AdventureWorks2000.XML.

  2. Open the text file for editing in your text editor.

  3. Copy and paste the metadata XML from Sample: AdventureWorks2000 PassThrough Metadata.

  4. In the LOBSystemInstance metadata, replace the name of the computer running SQL Server that hosts the AdventureWorks2000 database in the Rdb Connection Source property accordingly. If you use a SQL Server instance, use the format, SQLServer\Instance.

  5. Save the XML file.

  6. Add the application definition to the Business Data Catalog. For details, see How to: Add an Application Definition to the Business Data Catalog.

  7. Test the metadata as described in Testing the Metadata.

To test the AdventureWorks sample metadata using single sign-on

  1. Create a text file and save it as AdventureWorks2000.XML.

  2. Open the text file for editing in your text editor.

  3. Copy and paste the metadata XML from Sample: AdventureWorks2000 Single Sign-On Metadata.

  4. In the LOBSystemInstance metadata, replace the name of the computer running SQL Server that hosts the AdventureWorks2000 database in the Rdb Connection Source property accordingly. If you use a SQL Server instance, use the format, SQLServer\Instance.

  5. Save the XML file.

  6. Configure single sign-on. To configure single sign-on for the first time, complete the following tasks:

    1. Determine and set up necessary Windows accounts.

    2. Enable the single sign-on service on the job server.

    3. Configure the single sign-on settings.

    4. Create a new application definition. The name should match the SSOApplicationId property defined in the metadata.

    5. Provide account information for the application definition.

    6. Enable the single sign-on service on the front-end servers.

  7. Add the application definition to the Business Data Catalog. For details, see How to: Add an Application Definition to the Business Data Catalog.

  8. Test the metadata as described in Testing the Metadata.

See Also

Tasks

How to: Get Started with Using the Runtime Object Model
How to: Get Started with Using the Administration Object Model

Concepts

Business Data Catalog: Metadata Model
Business Data Catalog: Architecture
FAQ: Business Data Catalog
Business Data Catalog: Glossary