ApplicationRegistry, classe (Microsoft.Office.Server.ApplicationRegistry.MetadataModel)

Article
02/01/2010

Provides access to all the line-of-business (LOB) systems and LOB system instances registered in the Business Data Catalog. This is the top-level object in the Business Data Catalog's object model. It enables you to read all the metadata objects including LOB system, entities, and methods.

Espace de noms : Microsoft.Office.Server.ApplicationRegistry.MetadataModel
Assembly : Microsoft.SharePoint.Portal (dans microsoft.sharepoint.portal.dll)

Syntaxe

'Déclaration
<SharePointPermissionAttribute(SecurityAction.LinkDemand, ObjectModel:=True)> _
Public NotInheritable Class ApplicationRegistry
'Utilisation
Dim instance As ApplicationRegistry

[SharePointPermissionAttribute(SecurityAction.LinkDemand, ObjectModel=true)] 
public sealed class ApplicationRegistry

Remarques

The Business Data Catalog is implemented as an Office SharePoint Server 2007 core service and is shared across a Shared Resource Provider. Therefore, before you can use the ApplicationRegistry object, you must specify the Shared Resource Provider associated with the Business Data Catalog.

Exemple

The following code example shows how to display the names of the systems that are registered in the Business Data Catalog. Specifying the Shared Services Provider (SSP) is one of the first step sin a console application to work with the Business Data Catalog.

After you specify the Shared Services Provider, you can use the ApplicationRegistry object to get the LobSystemInstance objects that are registered with the Business Data Catalog, as shown in the following example.

Prerequisites

Ensure a Shared Services Provider is already created.
Replace the constant value EnterYourSSPNameHere in the code with the name of your Shared Resource Provider.

Project References

Add the following Project References in your console application code project before running this sample:

Microsoft.SharePoint
Microsoft.SharePoint.Portal
Microsoft.Office.Server

using System;
using System.Collections.Generic;
using System.Text;
using System.Data;
using Microsoft.Office.Server.ApplicationRegistry.MetadataModel;
using Microsoft.Office.Server.ApplicationRegistry.Runtime;
using Microsoft.Office.Server.ApplicationRegistry.SystemSpecific;
using Microsoft.Office.Server.ApplicationRegistry.Infrastructure;
using WSSAdmin = Microsoft.SharePoint.Administration;
using OSSAdmin = Microsoft.Office.Server.Administration;

namespace Microsoft.SDK.SharePointServer.Samples
{
    class GetStartedAndDisplaySystems
    {
        const string yourSSPName = "EnterYourSSPNameHere";

        static void Main(string[] args)
        {
            SetupBDC();
            DisplayLOBSystemsinBDC();
            Console.WriteLine("Press any key to exit...");
            Console.Read();
        }
        static void SetupBDC()
        {
            SqlSessionProvider.Instance().SetSharedResourceProviderToUse(yourSSPName);
        }
        static void DisplayLOBSystemsinBDC()
        {
            NamedLobSystemInstanceDictionary sysInstances = ApplicationRegistry.GetLobSystemInstances();
            Console.WriteLine("Listing system instances...");
            foreach (String name in sysInstances.Keys)
            {
                Console.WriteLine(name);
            }
        }
    }
}

Hiérarchie d'héritage

System.Object
Microsoft.Office.Server.ApplicationRegistry.MetadataModel.ApplicationRegistry

Sécurité des threads

Les membres statiques publics de ce type (Shared en Visual Basic) sont sécurisés au niveau des threads. Il n'est pas garanti que les membres d'instance soient sécurisés au niveau des threads.

Voir aussi

Référence

Membres ApplicationRegistry
Microsoft.Office.Server.ApplicationRegistry.MetadataModel, espace de noms

Partager via