Thursday, June 5, 2008

Introduction to Sharepoint 2007-part1

After a long time i come back to my home site.While this around last one year lot of things happend.
from now onwords i have been blogging...
From this blog on words i posted my learning MOSS stuff step -by-step.This is Categerized Chapters N Parts.
I hope MOSS hunters will Enjoy through my posts and my Chapters will stop digging MOSS...
Start Machiiiiii...start
Chapter 1
Getting Started
SharePoint technologies provide an effective solution for creating team sites to facilitate collaboration in a LAN-based environment and make it easier to manage content in an Internet-facing site that can scale to accommodate thousands of users in a Web farm environment.
Windows SharePoint Services as a development platform.
Our goal is to teach you how to create, debug, and deploy the fundamental building blocks such as Features, Site Definitions, Page Templates,Web Parts, List Schemas, Content Types, Event Handlers, and Workflow Templates.
Site Provisioning
WSS is a site provisioning engine.
The act of provisioning (a fancy word for creating) a site in WSS can be accomplished by any member of the IT department in less than a minute by filling in the required information in a browser-based form and clicking the OK button. There’s no need for a database administrator to create a new database or any new tables. There’s no need
for an ASP.NET developer to create a new ASP.NET Web site. There’s no need for a system administrator to copy any files or configure any IIS settings on the front-end Web server.

Microsoft Office SharePoint Server 2007
WSS is included as a part of the Windows Server 2003 operating system while MOSS is a separate product . You should think of WSS as the underlying platform and think of MOSS as a value-added set of components and services that has been built on top of this platform.
WSS does not have its own licensing model. Instead, the use of WSS is controlled through Windows Server 2003 licenses. MOSS, on the other hand, has its own licensing model.

farm is a set of one or more server computers working together to provide WSS functionality to clients. Each WSS farm runs a single SQL Server database known as the configuration database. The configuration database tracks important farm-wide information. For example, the configuration database tracks which front-end Web servers are associated with the farm as well as which users have been assigned administrative permissions within WSS at the farm level.
WSS is built on top of Internet Information Services 6.0 (IIS). In particular, WSS relies on IIS Web sites to handle incoming HTTP requests. Therefore, you need to understand exactly what an IIS Web site really is. An IIS Web site provides an entry point into the IIS Web server infrastructure. For example, the Default Web Site created automatically by IIS listens for incoming HTTP requests on port 80. You can create additional IIS Web sites to provide additional entry points using different port numbers, different IP addresses, or different host headers.
An IIS Web site must be specially configured when it is used to serve up WSS sites.
An IIS Web site that has been specially configured to run WSS sites is known as a Web application.Every WSS site runs in the context of a specific Web application.
The installation of WSS creates and configures a Web application named the WSS 3.0 Central Administration application. The WSS 3.0 Central Administration application provides pages that allow you to perform administrative chores such as converting a standard IIS Web site into a WSS Web application. The WSS Central Administration application also provides the option to create a new IIS Web site and automatically configure it to be a WSS Web application as well, all without having to use any of the IIS administration tools directly.

Default Web Site can be configured as a WSS Web application to make WSS sites available through the standard HTTP port 80. You might decide to create additional Web applications within the farm such as an intranet Web application on port 1000. WSS configuration data is stored on a farm-wide basis in the configuration database, and the data associated with WSS sites is tracked in another type of database known as a content database. When you create a new Web application with the WSS 3.0 Central Administration application, WSS creates a new content database. If you stick with a simple deployment model, your farm will include one content database for each Web application,as shown in Figure 1-2.

Sites and Site Collections
What is a WSS site? First, a WSS site is a storage container for content. Site content is primarily stored in the form of lists, document libraries, and child sites. Second, a site is a securable entity whose content is accessible to a configurable set of users.
Note that WSS doesn’t actually perform user authentication. Instead, WSS relies on the underlying layers within IIS and the ASP.NET authentication provider infrastructure to accomplish that. However, WSS does take charge when it comes to authorization. WSS provides user interface elements and supporting code that allows privileged users to configure authorization to various elements within their sites.
Every WSS site must be provisioned within the scope of an existing Web application. Instead, every WSS site must also be created inside the scope of a site collection. A site collection is a container of WSS sites. Each site collection requires a top-level site. In addition to the required top-level site, a site collection can contain a hierarchy of child sites. Figure 1-3 shows several possible site collections.

WSS architecture sees each site collection as an island with respect to security configuration.
The STSADM.EXE Command Line Utility
Here’s an example of a command line instruction to create a new site collection at a specific URL.
STSADM.EXE –o CreateSite –url http://localhost/sites/Sales
-ownerlogin LitwareServer\BrianC
-sitetemplate STS#0
c:\program files\common files\microsoft shared\web server extensions\12 called as system directory.
Users can also create several types of custom site elements for reuse across all the sites within a site collection. For example, if you create a site column within a top-level site, then this site column is reusable in all the child sites down below. This allows you to define the column characteristics such as formatting, validation, or a choice list one time and then to use this reusable column type across many lists within the site collection.
The standard Site Settings page for a top-level site is shown in Figure 1-8.

The Site Actions menu also provides the Create menu command, which takes you to the Create Page, as shown in Figure 1-9.

Customization changes are seen by all users. Personalization changes are seen by only the user who made them.
A site customization never requires touching the front-end Web server. WSS development, on the other hand, involves working with files that must be deployed to the file system of the front-end Web server. WSS development includes creating page templates and list definitions, as well as creating components deployed in compiled assemblies such as custom Web Parts, event handlers, and workflow templates. WSS development at this level is also referred to as developing provisioning components.
A site column is a reusable column definition that can be used across multiple lists. A site column defines the name for a column, its underlying field type, and other characteristics such as the default value, formatting, and validation.
A content type is a flexible and reusable WSS type definition that defines the columns
and behavior for an item in a list or a document in a document library
. For example, you can create a content type for a customer presentation document with a unique set of columns, an event handler, and its own document template. You can create a second content type for a customer proposal document with a different set of columns, a workflow, and a different document template. A content type deal with heterogeneous types of content in lists and document libraries.
WSS is built on top of Microsoft’s new Windows Workflow Foundation that is part of the .NET Framework 3.0.WSS adds an extra dimension on top of the Windows Workflow Foundation to provide a foundation for attaching business logic to list items and documents in a WSS site.
Both WSS and MOSS ship with workflows that are installed and ready to use. WSS includes a simple routing workflow for things such as moderation and approval.

No comments: