LobSystemInstance

Switch View :

LobSystemInstance

The main purpose of the LobSystemInstance object is to provide authentication and connection string information to the Infrastructure component of Business Data Catalog. The Infrastructure component provides run-time connection management for Business Data Catalog clients. The LobSystemInstance object must have a unique name.

Client Impact

The Entity Picker in Microsoft Office SharePoint Server 2007 lists the available LobSystemInstance objects in the Business Data Catalog for which you have permissions, and enables you to pick entities when adding Web Parts and Business Data columns.

Remarks

The LobSystemInstance object allows you to associate two sets of instance-specific data such as connection parameters and authentication settings with a single system definition - one for Web clients and one specifically for search. This is extremely useful when you have different sets of security credentials to access data using Web clients and to crawl search.

Examples

The following examples show the XML for the metadata for the LobSystemInstance object. This object takes different sets of properties for databases and Web services. The first two tables following the code examples list the properties that the LobSystemInstance object allows.

Database using PassThrough Authentication

Xml

  <LobSystemInstances>
    <!-- An LobSystem can have only one LobSystemInstance. The LobSystemInstance defines the connection and authentication parameters. -->
    <LobSystemInstance Name="AdventureWorksSample">
      <Properties>
        <Property Name="AuthenticationMode" Type="System.String">PassThrough</Property>
        <!--AuthenticationMode can be set to PassThrough, RevertToSelf, RdbCredentials, or WindowsCredentials. -->
        <Property Name="DatabaseAccessProvider" Type="System.String">SqlServer</Property>
        <!-- Can be SQL Server, OlEDB, Oracle, or ODBC for database systems. -->
        <Property Name="RdbConnection Data Source" Type="System.String">YourAdventureWorks2000ServerNameHere</Property>
        <!-- The name of your server hosting the database or the name of the SQL Server instance in the format SQLServer\Instance. -->
        <Property Name="RdbConnection Initial Catalog" Type="System.String">AdventureWorks2000</Property>
        <!-- The name of the database.> -->
        <Property Name="RdbConnection Integrated Security" Type="System.String">SSPI</Property>
        <Property Name="RdbConnection Pooling" Type="System.String">false</Property>
       </Properties>
    </LobSystemInstance>
  </LobSystemInstances>

Database Using Single Single-On

Xml

<LobSystemInstances>
    <LobSystemInstance Name="AdventureWorksSampleSSO">
      <Properties>
        <Property Name="AuthenticationMode" Type="System.String">WindowsCredentials</Property>
        <Property Name="DatabaseAccessProvider" Type="System.String">SqlServer</Property>
        <Property Name="RdbConnection Data Source" Type="System.String">YourAdventureWorks2000ServerNameHere</Property>
        <Property Name="RdbConnection Initial Catalog" Type="System.String">AdventureWorks2000</Property>
        <Property Name="RdbConnection Integrated Security" Type="System.String">SSPI</Property>
        <Property Name="RdbConnection Pooling" Type="System.String">false</Property>
        <Property Name="SsoApplicationId" Type="System.String">AdventureWorks</Property>
        <Property Name="SsoProviderImplementation" 
            Type="System.String">Microsoft.SharePoint.Portal.
            SingleSignon.SpsSsoProvider, 
            Microsoft.SharePoint.Portal.SingleSignon, 
            Version=12.0.0.0, Culture=neutral, 
            PublicKeyToken=71e9bce111e9429c</Property>
      </Properties>
    </LobSystemInstance>
  </LobSystemInstances>

Web Service

Xml

  <LobSystemInstances>
    <LobSystemInstance Name="AWSECommerceService">
      <Properties>
        <Property Name="WebServiceAuthenticationMode" Type="System.String">PassThrough</Property>
       </Properties>
    </LobSystemInstance>
  </LobSystemInstances>

Properties

Following are the properties that the LobSystemInstance object accepts for database systems.

Property	Type	Required	Default Value	Limits/Accepted Values	Comments
AuthenticationMode	Microsoft.Office.Server.ApplicationRegistry.SystemSpecific.Db.DbAuthenticationMode	No	RevertToSelf	PassThrough RevertToSelf Credentials WindowsCredentials
DatabaseAccessProvider	Microsoft.Office.Server.ApplicationRegistry.SystemSpecific.Db.DbAccessProvider	No	SqlServer	SqlServer OleDb Oracle Odbc
SsoProviderImplementation	System.String	Yes, if AuthenticationMode is Credentials or WindowsCredentials	None	Microsoft Single Sign-on provider	Fully qualified type name of the ISsoProvider implementation that stores credentials used to log in to the database.
SsoApplicationId	System.String	No	None		ID of the SSO enterprise application definition that stores credentials used to connect to the database.
RdbConnection Data Source RdbConnection Initial Catalog RdbConnection Integrated Security RdbConnection Pooling	System.String	No	None		Properties prefixed with RdbConnection become database connection properties. For example, the "RdbConnection Data Source" property becomes the "Data Source" property on the database connection.
NumberOfConnections	System.Int32	No	-1	-1 or a positive number	Maximum number of simultaneous connections to allow to the system. If the value is -1, there is no maximum.
SecondarySsoApplicationId	System.String	No	None		ID of the SSO enterprise application definition that stores credentials used by the filters: Username and Password.

Following are the properties that the LobSystemInstance object accepts for Web service systems.

Property	Type	Required	Default Value	Limits/Accepted Values	Comments
WebServiceAuthenticationMode	System.String	No	RevertToSelf	PassThrough RevertToSelf Credentials WindowsCredentials	Authentication mode used to invoke Web service methods.
SsoProviderImplementation	System.String	Yes, if WsdlFetchAuthenticationMode is Credentials or WindowsCredentials	None	Microsoft Single Sign-on provider	Fully qualified type name of the ISsoProvider implementation that stores credentials used to call the Web service.
WebServiceSsoApplicationId	System.String	Yes, if WsdlFetchAuthenticationMode is Credentials or WindowsCredentials	None		ID of the SSO enterprise application definition that stores credentials used to call the Web service.
WebProxyServerConfiguration	System.String	No	None		Proxy server URL. Requests to fetch WSDL or invoke Web service methods are routed through this proxy server.
NumberOfConnections	System.Int32	No	-1	-1 or a positive number	Maximum number of simultaneous connections to allow to the system. If the value is -1, there is no maximum.
SecondarySsoApplicationId	System.String	No	None		ID of the SSO enterprise application definition that stores the username and password for the Username and Password filters and HTTP and SOAP headers.
WebServiceUrlOverride	System.String	No	None		Overrides the URL used to access the Web service. The default behavior is to use the Web service URL defined in the WSDL file.

Other Resources

Business Data Catalog Authentication
AdventureWorks SQL Server 2000 Sample
How to: Get Started with Using the Runtime Object Model
How to: Get Started with Using the Administration Object Model
FAQ: Business Data Catalog
Business Data Catalog: Glossary

Tags :

Community Content

Owen79

Other properties

You can also supply the following properties;

RdbConnection User Id System.String Not Required No Default
RdbConnection Password System.String Not Required No Default

Tags :

ginolee

Where are these options defined ?

Where are these options defined ? I just spent 15 minutes search on this msdn site for an explanation of

what each of these options mean. There should be a link on this page to further explain each of these options.

PassThrough

RevertToSelf

Credentials

WindowsCredentials

Tags :

ginolee

Please be more precise in your specifications

I just spent the past 20-25 minutes searching for a definition of each of these terms, but was unsuccessful

so far. All this information should either be on this page or this page should link to a page that explains these terms in sufficient detail.

PassThrough

RevertToSelf

Credentials

WindowsCredentials

Tags :

eHaze

Specification Details?

Pass-Through (Database and Web Service Systems)

Pass-through authentication refers to the ability of the operating system to pass a client's authentication information to the back-end server. The Business Data Catalog supports pass-through authentication for both database and Web service connections. When you use pass-through authentication, you simply authenticate as the identity of the end user.

When the Business Data Catalog is accessed from a Web page, it runs in the Microsoft Internet Information Services (IIS) worker process, w3wp.exe. The identity of this process is the IIS application pool account impersonating the logged-on user. To avoid losing the logged-on user’s identity when the Business Data Catalog authenticates to the back-end server, you must enable Kerberos delegation between the server running IIS and the other computer. Kerberos delegation enables a receiving server to send the authentication request to the proper location.

When the Business Data Catalog is used for crawling, it runs in the filter daemon process, mssdmn.exe. To access the back-end content source, the threads in the filter daemon process impersonate as the content access account associated with that back-end content source.

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, simplicity of use makes pass-through authentication a good candidate for use in a testing environment. You might also use it if the destination server uses anonymous authentication or SSL connections.

RevertToSelf (Database and Web Service Systems)

If a user logs on with Windows Authentication, IIS impersonates that particular account. So while IIS runs under the Application Pool Identity, it impersonates the logged-on user, and the request runs under the user’s impersonation before it is passed forward.

RevertToSelf authentication allows you to revert this impersonation and authenticate as the underlying account that is configured for the IIS Application Pool.

WindowsCredentials (Database and Web Service Systems)

Microsoft Office SharePoint Server 2007 authenticates by using Microsoft Windows credentials from its default single sign-on (SSO) service.

RdbCredentials (Database Systems Only)

In RdbCredentials mode, Office SharePoint Server 2007 authenticates by using database credentials from its default SSO service. Office SharePoint Server 2007 adds the database credentials to the connection string and transmits the credentials to the database server.

Credentials (Web Service Systems Only)

Office SharePoint Server 2007 authenticates Web service systems by using credentials other than those from Windows Authentication from its default SSO service. These credentials are used for basic or digest authentication, depending on the configuration of the Web services server. Because basic and digest authentication do not adequately protect credentials, you should use SSL or IPSec or both to secure communication between the Web services server and the server running the Business Data Catalog.

http://msdn.microsoft.com/en-us/library/ms566523.aspx

Tags :