Skip to main content

SharePoint 2010 data structures.


SharePoint provide services for data and contents.

1.     Modeling
1.     You can define a data model using SharePoint data structures such as lists and content types.
2.     You can define a data model in an external data source, such as a relational database, and then create a set of external content types to expose the data to SharePoint through the Business Connectivity Services (BCS) component. Alternatively, you could create a Web service to wrap the data source and create your external content types from the Web service.
3.     You can create a set of external content types to model and integrate an existing data source, such as a database, a Windows Communication Foundation (WCF) service, or a .NET type, to expose the data to SharePoint through the BCS.
2.     Manipulation
1.     SharePoint 2010 using server and client object model and the differences of using different model to query your data. Also, Using LINQ is one of the most favorite features for .NET developers in SharePoint 2010
3.     Storage.
1.     Windows File system
2.     SQL Server
Note: Storage details are invisible for the users and abstract for the developer. 
API’s for working with data.


1. CAML (Collaborative Application Markup Language): Collaborative Application Markup Language (CAML) is the XML-based language that is used to build and customize Web sites based on SharePoint™ Team Services from Microsoft.
a. CAML can be used to do the following:
b. Provide schema definition to the Web site provisioning system about how the site looks and acts.
c. Define views and forms for data and page rendering or execution.
d. Act as a rendering language that performs functions in the DLL like pulling a value from a particular
e. Provide batch functionality for posting multiple commands to the server using protocol.
2. Managed code via Microsoft.SharePoint.dll
        SharePoint Classes name start with SP. Following the list of classes are.
    • SPWebApplication
    • SPContentDatabase
    • SPSite
    • SPWeb
    • SPList
    • SPListItem
    • SPField

3.  Client libraries.
         Following two Client .dll used
  • Microsoft.SharePoint.Client.Runtime
  • Microsoft.SharePoint.Client
Name of the client libraries classes are same as the SharePoint Managed code library but here is a slit diff. Name not staring with SP. Following the list of the classes are

    • Site
    • List
    • Web


4. Various web Services(SOAP, WCF, REST)

  • SOAP services  
    • http://Server_Name/Subsite_Name/_vti_bin/Lists.asmx (Under _vit_bin foder)
    • http:// MyServer:Port_Number/_vti_adm/Admin.asmx (Admin services under _vti_admin)
  • WFC Services
    • http://<sharepoint-server>/_vti_bin/ListData.svc
  • REST
    • http://<sharepoint-server>/_vti_bin/ListData.svc/<ListName> 
ex. http://sp2010/_vti_bin/ListData.svc/Tasks
API's Supports

  1. Deployment of data and contents
  2. Definition and management of data structure.
  3. Definition and Data Structure of data Store.
  4. Retrieval and management of data and contents.   

Comments

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis