Search This Blog

Friday, October 10, 2014

Some Difference Of Sharepoint

                 What Is SharePoint 
  1. " Business Collaboration Software developed by Microsoft".
  2. It is a Web based application allows the people in an organization to collaborate or work together more efficiently.
  3.  "Information Centrally stored." Hence the time is less which increases efficiency.
                 Version Of SharePoint
1.   Microsoft Content Management Server (CMS) (Year 2002)
2.    SharePoint Portal Server (Year 2003)
3.   Windows SharePoint Services 3.0 (Year 2003) – Free Ware
4.   Microsoft Office Share Point Server (MOSS) (Year 2007) (Built on .NET 2.0) – Combination of CMS and SharePoint Portal Server  
5.   Combination of CMS and SharePoint Portal Server
6.   SharePoint Foundation Server (Year 2010) – Free Ware
7.   Microsoft SharePoint Server (Year 2010)            
Pillars Of SharePoint  2010
                                   
        

        SharePoint 2013 Feature Added

1.New Minimal UI
2. SharePoint and Office Apps model.
3. Social and Collaboration Features (Interactive feed,Community Site,Follow People,Follow Sites ..)
4. Improved Search
5. Cross-Site Publishing (Improved ECM)
6. Shredded Storage
7. Out-of-Box PDF support
8. Minimal Download Strategy (Improve Performance)
9. Dual SharePoint 2013 License
          SharePoint Database  
Configuration Database:- Whenever we installed the SharePoint on any machine then the installation files automatically creates an configuration database. where all the configurations of SharePoint were installed.
Content Database:- Whenever we create any site collection. After creating a web application. then the content database will create.  which contains all the information regarding that particular site collection.
Conclusion:- There can be only one configuration database on a machine. But can be multiple content database on single machine.
                     Configuration Database
The configuration database contains data about SharePoint 
  1. Databases,
  2. Internet Information Services (IIS) Web sites,
  3. Web applications,
  4. trusted solutions,
  5. Web Part packages,
  6. site templates, and
  7. Web application and farm settings

                  Content databases

Content databases store all content for a Site Collection including 
  1. site documents or
  2. files in document libraries,
  3. list data,
  4. Web Part properties,
  5. audit logs, and
  6. sandboxed solutions, in addition to
  7. user names and rights.
All the data for a specific site collection resides in one content database on only one server. A content database can be associated with more than one site collection.
                                Other Databases
                         Business Data Connectivity database
The Business Data Connectivity service application database stores external content types and related objects.

                               Application Registry database

It stores backward-compatible information that is used to connect to information that is used by the Microsoft Office SharePoint Server 2007 Business Data Catalog API.When you have finished migrating an application from the Office SharePoint Server 2007 Business Data Catalog, the Application Registry service application can be disabled and the database can be deleted.  
Note:
When you have finished migrating an application from the Office SharePoint Server 2007 Business Data Catalog, the Application Registry service application can be disabled and the database can be deleted.

                                           State database

The State service application database stores temporary state information for InfoPath Forms Services, the chart Web Part, and Visio Services.
               Search service application Administration database
The Administration database hosts the Search service application configuration and access control list (ACL), and best bets for the crawl component. This database is accessed for every user and administrative action. 

                        Web Analytics Reporting database

The Reporting database stores aggregated standard report tables, fact data aggregated by groups of sites, date and asset metadata, and diagnostics information for the Web Analytics service application.

                       Search service application Property database

The Property database stores information that is associated with the crawled data, including properties, history, and crawl queues.

                       User Profile service application Profile database

The Profile database stores and manages users and associated information. It also stores information about a user's social network in addition to memberships in distribution lists and sites. 

                      User Profile service application Synchronization database

The Synchronization database stores configuration and staging data for use when profile data is being synchronized with directory services such as Active Directory.

                      User Profile service application Social Tagging database

The Social Tagging database stores social tags and notes created by users, along with their respective URLs.

                       Managed Metadata database

The Managed Metadata service application database stores managed metadata and syndicated content types.

Difference between site pages and application pages in sharepoint 2010

Site Pages
Application Page
·         Site Pages are Site or Web Scoped
·         Application Pages are farm scoped
·         User can customize Site Pages.
·         No customization can be done by the user.
·         Site Pages are stored in Content Database
·         Application Pages are stored in WFE(Web Front End) in _layouts folder
·         You cannot have custom code in Site Pages.
·         You can have custom code in your Application Pages.
·         Site Pages are Un-ghosted Pages
·         Application Pages are Ghosted Pages.

Site Pages:
1.    Pages that support user customization are known as site pages and storedin the content database.
Ex. Site pages default.aspx, NewForm.aspx, and EditForm.aspx.
2.    Site pages customization provides flexibility but can also impact
performance and scalability Each page would also have to be individually parsed and loaded into memory..
3.    Site pages do not support in-line code under the default security
 policy enforced by WSS.





Application pages:
1.    Application pages do not support customization, which gives them two
distinct advantages over site pages.
1.           First, each application page is always compiled into a single DLL so that it performs and scales better than a site page.
2.      Second, application pages are allowed to have in-line code.
Ex. Settings.aspx, uagedetails.aspx.
       Application pages are deployed as physical files on file system of front end
web server on the server’s file system.
An application page, such as settings.aspx, can be accessed by adding its
relative path within the _layouts directory to the end of a site’s URL.

Ghosted pages: Pages which are on file system and not on content db.
Unghosted pages : pages which are on content db.
Application Pages : normal asp.Net pages stored on file system.
site pages : Normal content pages stored in db.
According to these definations Site pages should always be Unghosted and Application pages should always be Ghosted.





                                   Differences Between BDC &BCS
Difference between Web Application, Site Collection
Web Application
1.    On top of the hierarchy is the web application.
2.    In technical terms, this is a web site in IIS (with an associated application pool). 
3.    A default web site listens for incoming HTTP requests on port number 80.
4.    But we can create additional web sites, having different port numbers or IP addresses.
5.    We can configure each IIS web application independently.
6.    We can have one web application configured in anonymous access one in integrated authentication etc.
7.    The SPWebApplication objects represent a SharePoint Web Application, which essentially is an IIS virtual server. Using this class we can do some high level operations.
8.    Please find some of the actions you can perform.
  1. Create a web application
  2. Collect all the features in a particular web application
  3. Delete a web application
  4. Some administrative task for the web application.
Site Collection
1.     The Site Collection is the root site of the web site.
2.     Below the Site Collection, there can be one or more Sites.
3.     A Site Collection is a collection of SharePoint sites;  i.e. a SharePoint site collection is a logical grouping of multiple SharePoint sites.
There are many reasons to go with separate site collection in SharePoint. Some of the features are listed below.
  1. Dedicated Recycle bins
  2. Dedicated usage Reports
  3. Site collection administrator option for each site collection
  4. We can set search scopes, keywords, etc
  5. We can deploy features specific to a site collection
  6. Each site collection has Galleries for web parts, master pages, content Type etc
  7. Administrators can set Site quota templates for Site collection (Max Size of the Site collection)
  8. Database maintenance options
  9. Backup / Restore abilities
  10. Content Deployments optionns
Note:
1.     SiteCollection is, as the name indicates, a collection of sites. A WebApplication is a collection of SiteCollections.
2.     SiteCollections are used to group Sites together to make it easier for you to, for example, share data between these sites.
3.     WebApplications are useful when you need to share data between different SiteCollections.
4.     The most important thing to remember about a web application is that it’s a division in ISS.
5.     Web applications are created to separate parts of a SharePoint server for reasons such as performance and security.
6.     A web application can contain a collection of site collections, but a web application might also be used for a single site collection.
7.     A site collection is a collection of sites. And I like MSerejo’s description “SiteCollections are used to group Sites together to make it easier for you to, for example, share data between these sites.”

Difference between Data View Web Part and Content Query Web Part

Data View Web Par

  1. Need SharePoint Designer to configure it
  2. Displays data/Items with in sub site
  3. Displays data ( items) from only one List/Library
  4. Binds to List/Library GUID
  5. XSLT Style Templates store on Web Part itself
  6. Available on all template
Content Query Web Part
  1. Can be configurable from Browser
  2. Displays data/Items from Site Collection Level
  3. Displays data (items) based on Content Type
  4. Binds to Content Type
  5. XSLT Style templates stores on ItemsStyle.xsl
  6. Available on Publishing Portal template

What is the GAC
1.     The GAC (Global Assembly Cache) contains libraries of code that can be accessed by any program on your computer. 

2.     SharePoint uses the GAC  because it is dispersed all over your server, there are aspects of it in your inetpub directory and in the 14/15 (hive) directory and the GAC is a central place for all shared libraries.

Where is the GAC and how to install anything to it.
.NET Less than 4
The GAC for these assemblies is located in “C:/Windows/assembly”.
It is possible that you can just drag and drop your assembly into this folder to install it. If this works for you then you are done, if it does not you need to run a gacutil executable. If you have no idea where this executable is then go to the section in this blog about finding the gacutil.
.NET 4.0 and up
For some reason Microsoft decided to move the GAC for these to C:/Windows/Microsoft.NET/assembly. Then there are 3 directories here.  I think by default your assemblies will be installed into GAC_MSIL.
The way to install to this folder is to use the gacutil. If you are using the Windows SDK’s for the gacutil please refer to the following section.
The commands
To Install > gacutil -I “C:\AuthenticationDM.dll”
To Uninstall > gacutil -U “AuthenticationDM.dll”

Finding The gacutil.
Visual Studio - The developer command prompt has the gacutil in it.
Windows SDK’s 7.1 – Download from Microsoft 
There are two gacutils here 
For .NET 3.0 or less you can use the gacutil found in “C:\Program Files\Microsoft SDKs\Windows\v7.1\bin”
For .NET 4.0 or higher you need to use the gacutil found in “C:\Program Files\Microsoft SDKs\Windows\v7.1\bin\NETFX 4.0 Tools” if you use the other one you will get “This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.”  error.

References :-
 http://skdeveloper.wordpress.com/2013/07/31/difference-between-web-application-site-collection/
http://skdeveloper.wordpress.com/2013/07/29/difference-between-site-template-and-site-definition/
http://skdeveloper.wordpress.com/2013/07/29/difference-between-list-definition-list-template-and-list-instance/
http://skdeveloper.wordpress.com/2013/07/29/differance-between-bcs-and-bdc/
http://skdeveloper.wordpress.com/2013/07/31/difference-between-site-pages-and-application-pages-in-sharepoint-2010/
http://skdeveloper.wordpress.com/2013/09/16/classic-mode-vs-claims-based-authentication-in-sharepoint-2010/
http://skdeveloper.wordpress.com/2013/09/16/supported-object-models-in-sharepoint-2010/

Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)