What is SP site?
A SharePoint site is a Web site that provides a central storage and collaboration space for documents, information, and ideas. A SharePoint site is a tool for collaboration, just like a telephone is a tool for communication, or a meeting is a tool for decision making. A SharePoint site helps groups of people (whether work teams or social groups) share information and work together. For example, a SharePoint site can help you:
* Coordinate projects, calendars, and schedules.
* Discuss ideas and review documents or proposals.
* Share information and keep in touch with other people.
SharePoint sites are dynamic and interactive -- members of the site can contribute their own ideas and content as well as comment on or contribute to other people.
* Coordinate projects, calendars, and schedules.
* Discuss ideas and review documents or proposals.
* Share information and keep in touch with other people.
SharePoint sites are dynamic and interactive -- members of the site can contribute their own ideas and content as well as comment on or contribute to other people.
What are the advanced features of MOSS 2007?
- User Interface (UI) and navigation enhancements
- Document management enhancements
- The new Workflow engine
- Office 2007 Integration
- New Web Parts
- New Site-type templates
- Enhancements to List technology
- Web Content Management
- Business Data Catalog
- Search enhancements
- Report Center
- Records Management
- Business Intelligence and Excel Server
- Forms Server and InfoPath
- The “Features” feature
- Alternate authentication providers and Forms-based authentication
How can I make my site public? By default, all sites are created private.
If you want your site to be a public Web site, enable anonymous access for the entire site. Then you can give out your URL to anybody in your business card, e-mail or any other marketing material. The URL for your Web site will be: http:// yoursitename.wss.bcentral.com
Hence, please take special care to name your site. These Web sites are ideal for information and knowledge intensive sites and/or sites where you need to have shared Web workspace. Remember: Under each parent Web site, you can create up to 10 sub-sites each with unique permissions, settings and security rights.
How do I make my site non-restricted?
If you want your site to have anonymous access enabled (i.e., you want to treat it like any site on the Internet that does not ask you to provide a user name and password to see the content of the site), follow these simple steps:
- Login as an administrator
- Click on site settings
- Click on Go to Site Administration
- Click on Manage anonymous access
- Choose one of the three conditions on what Anonymous users can access:
- Entire Web site
- Lists and libraries
- Nothing
Default condition is nothing; your site has restricted access. The default conditions allow you to create a secure site for your Web site.
What security levels are assigned to users?
Security levels are assigned by the administrator who is adding the user. There are four levels by default and additional levels can be composed as necessary.
- Reader - Has read-only access to the Web site.
- Contributor - Can add content to existing document libraries and lists.
- Web Designer - Can create lists and document libraries and customize pages in the Web site.
- Administrator - Has full control of the Web site.
· organization has a Web presence.
· A site or workspace is when you want a new place for collaborating on Web pages, lists and document libraries. For example, you might create a site to manage a new team or project, collaborate on a document or prepare for a meeting.
What does partial trust mean the Web Part developer?
· If an assembly is installed into the BIN directory, the code must be ensured that provides error handling in the event that required permissions are not available. Otherwise, unhandled security exceptions may cause the Web Part to fail and may affect page rendering on the page where the Web Part appears.
What are the two base classes a Web Part can inherit from?
There are two base classes that a WebPart which is going to be consumed by SharePoint can inherit from, either the SharePoint WebPart Base class or the ASP.NET 2.0 WebPart base class. When inheriting from the SharePoint WebPart Base class your derived WebPart class will inherit from Microsoft.SharePoint.WebPartPages.WebPart. When inheriting from the ASP.NET 2.0 WebPart base class your derived WebPart class will inherit from System.Web.UI.WebControls.WebParts.WebPart. It is considered good practice to use the ASP.NET WebPart base class since the old base class is meant for backwards compatibility with previous version of SharePoint, however there are four exception when it is better to leverage functionality from the SharePoint WebPart base class:Cross page connections
Connections between Web Parts that are outside of a Web Part zone
Client-side connections (Web Part Page Services Component)
Data caching infrastructure
The SPSite object represents a collection of sites (site collection [a top level sites and all its subsites]). The SPWeb object represents an instance SharePoint Web, and SPWeb object contains things like the actual content. A SPSite object contains the various subsites and the information regarding them.
What does a SPWebApplication object represent?
The SPWebApplication objects represents a SharePoint Web Application, which essentially is an IIS virtual server. Using the class you can instigate high level operations, such as getting all the features of an entire Web Application instance, or doing high level creation operations like creating new Web Applications through code
.
What are event receivers?
Event receivers are classes that inherit from the SpItemEventReciever or SPListEventReciever base class (both of which derive out of the abstract base class SPEventRecieverBase), and provide the option of responding to events as they occur within SharePoint, such as adding an item or deleting an item.
What is a content type?
A content type is an information blueprint basically that can be re-used throughout a SharePoint environment for defining things like metadata and associated behaviors. It is basically an extension of a SharePoint list, however makes it portable for use throughout an instance regardless of where the instantiation occurs, ergo has location independence. Multiple content types can exist in one document library assuming that the appropriate document library settings are enabled. The content type will contain things like the metadata, listform pages, workflows, templates (if a document content type), and associated custom written functionality.
37) Can a content type have receivers associated with it?
Yes, a content type can have an event receiver associated with it, either inheriting from the SPListEventReciever base class for list level events, or inheriting from the SPItemEventReciever base class. Whenever the content type is instantiated, it will be subject to the event receivers that are associated with it.
38) What two files are typically (this is kept generally) included when developing a content type, and what is the purpose of each?
There is generally the main content type file that holds things like the content type ID, name, group, description, and version. There is also the ContentType.Fields file which contains the fields to include in the content type that has the ID, Type, Name, DisplayName, StaticName, Hidden, Required, and Sealed elements. They are related by the FieldRefs element in the main content type file.
What is a SharePoint site definition? What is ghosted (uncustomized) and unghosted (customized)?
SharePoint site definitions are the core set of functionality from which SharePoint site are built from, building from the SiteTemplates directory in the SharePoint 12 hive. Site definitions allow several sites to inherit from a core set of files on the file system, although appear to have unique pages, thereby increasing performance and allowing changes that happen to a site propagate to all sites that inherit from a site definition. Ghosted means that when SharePoint creates a new site it will reference the files in the related site definition upon site provisioning. Unghosted means that the site has been edited with an external editor, and therefore the customizations are instead stored in the database, breaking the inheritance of those files from the file system.
Features
Features are a collection of elements that modify, override, and extend the plotform. These elements can contain infrastructure component (definitions, templates, and so on) and can create instances of content items (lists, pages, and so on).
· Create the folder “NewFeature”: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\NewFeature
· Install the feature: stsadm -o installfeature -name NewFeature
· Activate the feature
· Reset IIS
2. Site Definitions and Templates
Site Definition:
Site definitions provide the bluuprints used to provision SharePoint product and Technologies sites; they are the instructions that orchestrate site creation.
Site Definitions are located in the following folder on the SharePoint server:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates
Site Definitions are registered with SharePoint and made available via the
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\1033\XML\WEBTEMP<NAME OF SITE DEFINITION>.XML file
Site Template:
The easiest options of replicating a site with the same look and feel is to turn it into a site template and then use that template to create other sites. Use the SharePoint Designer 2007 to wrap all the files and create a single .STP file. Customized master pages, layout pages, applied thems, custom CSS files, and optionally content stored in site lists and libries are all included. Limit is 10MB, but you can increase using STSADM. http://blah.winsmarts.com/2007-7-All_you_ever_wanted_to_know_about_SharePoint_2007_Site_Templates.aspx
3. Enterprise Search
Content Sources: SharePoint content, Web content, File share content, Exchange folder content, Business data content
Shared Scopes: Address, Property Query, Content Source
Index Server Default File Location: D:\Microsoft Office Servers\12.0\Data\Office Server\Applications
4. Shared Services Provider (SSP)
The services include:
· Search (Search Settings and Usage Reports)
· Audience
· User profiles and My Sites(User profiles and properties, Profile services policies, My Site settings, Trusted My Site host locations, Published links to Office client applications, Personalization site links, Personalization services permissions )
· Office SharePoint Usage Reporting
· Business Data Catalogue (Enterprise Edition)
· Excel Services (Enterprise Edition)
5. SharePoint Databases
· SharePoint_Config
· SharePoint_AdminContent_....<UniqueID>
· SSP_Config
· SSP_DB
· SSP_SearchDB
· mySites_Content
· SiteCollection_DB
6. Service Accounts involved with SharePoint 2007
| Setup Account: | Full access to the server |
| SQL Server Service Account: | SQL_Service - Admin(Machine), SecurityAdmin(SQL Server), DBCreator(SQL Server) |
| SharePoint Administrator Account: | MOSS Admin - Admin(Domain), SecurityAdmin(SQL Server), DBCreator(SQL Server) |
| Shared Service Provider Service Account: | SSP#_Service - User (Domain). The # is to match the SSP number i.e. SSP1 |
| MOSS Search Service Account: | Index _Service - User(Domain), Admin(Machine) |
| WSS Search Service Account: | WSS_Index_Service - User(Domain) |
| SSP Content Index Service Account: | SSP#_Index_Service - User(Domain), Content DB Read Access (SQL Server) |
| Extranet Service Account: | SP_Extranet_Service App Pool- User(Domain) |
| Intranet Service Account: | SP_Intranet_Service App Pool- User(Domain) |
See how to create MOSS VPC Image http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/Post.aspx?ID=14
7. SharePoint Farms
· Single Server: 1 Physical or Virtual Server (WFE, APP, and Database all on one server)
· Small Server: 2 Physical or Virtual Server (1 for App & WFE, and another for DB)
· Medium Server: 4-5 Physical or Virtual Server (2 WFEs, 1 App, 1-2 SQL)
· Large Server: 6 or more Physical or Virtual Server (2 WFE, 2-4 Search, 1-4 Index, 1-n SQL)
8. HTTP Status Codes
100 – 101: Informational (100 Continue, 101 Switching Protocol)
200 – 206: Success (200 Okay, 201 Created, 202 Accepted, 203 Non Auth Info, 204 No content, 205 Reset Content)
300 – 307: Redirection (302 Object moved, 304 Not Modified, 307 Temp Redirect)
400 – 423: Client Error (400 Bad request, 401 Access Denied, 401.1 Login Failed, 401.2 Login Failed due server configuration)
500 – 505: Server Error (500 Internal server error, 500.12 App is busy, 500.13 web server is busy, 503 Server Unavailable, 505 HTTP version not supported)
9. WSS 3.0 Authentication
Windows: Anonymous, Basic, Digest, Certificates, Kerberos (Integrated Windows), NTLM (Integrated Windows)
ASP.Net Forms: Lightweight Directory Access Protocol (LDAP), SQL Database or other Database, Other ASP.NET-based forms authentication solns)
Single Sign On (SSO): Active Directory Federation Services (AD FS), Other identity management systems
10. Web Service basics and protocols for Web Services
· XML Web Services expose useful functionality to Web users through a standard Web protocol. In most cases, the protocol used is SOAP.
· XML Web services provide a way to describe their interfaces in enough detail to allow a user to build a client application to talk to them. This description is usually provided in an XML document called a Web Services Description Language (WSDL) document.
· XML Web services are registered so that potential users can find them easily. This is done with Universal Discovery Description and Integration (UDDI).
11. ASP.Net Session Management
Client-side state management :
· Cookies
· Hidden Field
· View State
· Query Strings
Server-side state management:
· Aplication object
· Session object
· Database
12. MOSS 2007 Overview
Microsoft Office SharePoint Server 2007 Capabilities Collaboration
· Portal
· Enterprise Search
· Content Management
· Business Forms
· Business Intelligence
13. What is the diffrence between Collaborative portal and publishing portal?
The Colloborative Portal presents content info on individual pages, but it is also presents the organizational structure of other sites along with the links to easily access those sites
The Publishing Portal, however, is designed to present information withing the site pages themseleves and possibly withing subsites of the Publishing Portal.
14. Will document conversion service work on domain controller?
You should not install Web Server on a domain controller. If you place member of SharePoint farm running the document conversion service on a domain controller, it will not work, at all ever. This occurs because the converter is executed in the context of a local account, and there are no local accounts on a domain controller.
15. What are the variations?
Maintaining a number of different versions, or "variations," of publishing sites or pages is difficult and time consuming because it can be difficult to coordinate the creation and updating of content between the variations.
To simplify this process, site owners can define a series of site variations and mark one as the primary, or source, variation. Changes to the source variation can be automatically or manually propagated to target variations. Updates to the source variation ensures that the changes are made in all other target variations. To enable integration with third-party translations services, this system is integrated with workflow and the import and export of content. When translation is completed, updates can be imported and sent for final approval through the workflow system.
16. What is the web part?
Web parts are a type of composite Web control called server control. A web part is a container for other Web controls, such as label, text boxes, and buttons. In addition to containing child controls, Web parts are designed to exist on Web part pages and to allow customization and personalization of those pages.
· Microsoft.SharePoint.WebPartPages
· Microsoft.SharePoint. WebPartPages.SPWebPartManager
17. What is AppDomain?
AppDomainis a virtual location in memory where a process runs. Usually, each process runs in it's own space and if one process (A) is making a call to another process (B), and if B crashes, so does A. In pre-.NET days, this cross-process communication was achieved thru DCOM. Also, since each of the processes are directly dependent, if one crashes, the other crashes too.
18. List “Feature” scope levels?
· Web
· Site
· Web Application
· Farm
19. What is Workflow?
· A workflow is a natural way to organize and run a set of work units, or activities, to form an executable representation of a work process.
Workflow Type:
• Sequential workflows Represents a workflow as a procession of steps that execute in order until the last activity completes. However, sequential workflows are not purely sequential in their execution. Because they can receive external events and include parallel logic flows, the exact order of activity execution can vary.
• State machine workflows Represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. The state machine can have a final state that determines the end of the workflow.
20. What are the upgrade options available with SPS?
· In-place upgrade
· Gradual upgrade of site collections
· Content database migration
21. What is CAML?
Stands for Collaborative Application Markup Language and is an XML-based language that is used in Microsoft Windows SharePoint Services to define sites and lists, including, for example, fields, views, or forms, but CAML is also used to define tables in the Windows SharePoint Services database during site provisioning.
22. What is the difference between Themes and CSS?
Themes and CSS are often used interchangeably, but they are actually different. Themes are related to CSS because they are a collection of alternate CSS, image, and Skin files that can be applied to a site
23. What is search propagation?
A portal site can have multiple content indexes. When you create the portal site, Microsoft Office SharePoint Portal Server 2003 automatically creates two indexes. One index is for portal site content, and the other index is for non-portal site content. For more information about indexes, see About Content Indexes.
By using SharePoint Portal Server, you can propagate indexes from the index management server to the search server (the server dedicated to processing user search queries). Propagation allows you to distribute your resources. You can limit the resource-intensive processes required to create indexes to the index management server. This allows SharePoint Portal Server to create extensive indexes without affecting the performance of the search server.
Propagation automatically occurs at the end of the indexing process. You might want to force propagation in a situation where indexing is paused, or where propagation fails for some reason, such as network problems.
24. What is the Web Garden?
WebGarden means a machine with multiple processors running IIS
25. SharePoint Object Model
26. What is Information Policy Management?
An information management policy is a set of rules for a certain type of important content. Policy enables administrators to control and evaluate who can access the information, how long to retain information, and how effectively people are complying with the policy itself. The most common creators and enforcers of policy are compliance officers, records managers, IT staff, and others with similar responsibilities.http://msdn.microsoft.com/en-us/library/ms499244.aspx
Microsoft Office SharePoint Server 2007 includes four information management policy features to help you manage your content: Expiration, Auditing, Document Labels, and Document Bar Codes.
· Expiration
· Auditing
· Document Labels
· Document Bar Codes
- What is a DWP?
The file extension of a web part.
- What is the GAC?
Global Assembly Cache folder on the server hosting SharePoint. You place your assemblies there for web parts and services.
29. What is Content Type?
Content types, a core concept used throughout the functionality and services offered in Windows SharePoint Services 3.0, are designed to help users organize their SharePoint content in a more meaningful way. A content type is a reusable collection of settings you want to apply to a certain category of content. Content types enable you to manage the metadata and behaviors of a document or item type in a centralized, reusable way.
For example, consider the following two types of documents: software specifications and legal contracts. It is reasonable that you might want to store documents of those two types in the same document library. However, the metadata you would want to gather and store about each of these document types would be very different. In addition, you would most likely want to assign very different workflows to the two types of documents. For more info, click on http://msdn.microsoft.com/en-us/library/ms472236.aspx
30. What is Site Column?
Windows SharePoint Services 3.0 introduces a new innovation named Site Columns that allows users and developers to create standalone field types that can be reused across lists and document libraries.
31. HTTP Handlers and HTTP Modules in ASP.NET?
An ASP.NET HTTP handler is the process (frequently referred to as the "endpoint") that runs in response to a request made to an ASP.NET Web application. The most common handler is an ASP.NET page handler that processes .aspx files. When users request an .aspx file, the request is processed by the page via the page handler.
To create a custom HTTP handler, you create a class that implements the IHttpHandler interface to create a synchronous handler or the IHttpAsyncHandler to create an asynchronous handler. Both handler interfaces require you to implement the IsReusable property and the ProcessRequest method. The IsReusable property specifies whether the IHttpHandlerFactory object (the object that actually calls the appropriate handler) can place your handlers in a pool and reuse them to increase performance, or whether it must create new instances every time the handler is needed. The ProcessRequest method is responsible for actually processing the individual HTTP requests. http://www.15seconds.com/issue/020417.htm
32. Smart Web Parts?
Some of the web parts that come with SPS allow you to add a web part to a page that actually takes the users outlook info (calendar, inbox, contacts, tasks) and put them into the page.
33. Alternate Access Mapping (AAP)?
Each Web application can be associated with a collection of mappings between internal and public URLs. Both internal and public URLs consist of the protocol and domain portion of the full URL (for example, https://www.fabrikam.com). A public URL is what users type to get to the SharePoint site, and that URL is what appears in the links on the pages. Internal URLs are in the URL requests that are sent to the SharePoint site. Many internal URLs can be associated with a single public URL in multi-server farms (for example, when a load balancer routes requests to specific IP addresses to various servers in the load-balancing cluster).
Each Web application supports five collections of mappings per URL; the five collections correspond to five zones (default, intranet, extranet, Internet, and custom). When the Web application receives a request for an internal URL in a particular zone, links on the pages returned to the user have the public URL for that zone. For more information, see Plan alternate access mappings (Office SharePoint Server). http://technet.microsoft.com/en-us/library/cc263208.aspx
34. Managed Paths?
Enables SharePoint Products and Technologies to determine where site collections can be created, and to help the system interpret URLs to determine site paths.
35. What are event receivers?
Windows® SharePoint® Services (WSS) 3.0 offers developers many significant improvements for building custom business solutions based on SharePoint sites. One of the biggest developer-focused enhancements has to do with a new infrastructure for handling server-side events. For example, when a user performs an action that modifies content in a SharePoint site—say, uploading a new document or deleting an item from a list—there is an opportunity for a developer to respond to this user action with an event handler that executes server-side logic written in C# or Visual Basic®.
Important Paths:
SharePoint DLL:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\Microsoft.SharePoint.dll.
Features:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\NewFeature
Site Definitions:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates
Web Part Steps:
· Create the ASP.Net Web Application
· using Microsoft.SharePoint.WebPartPages;
· Set the inheritance of the class to WebPart: public class WebParticle: WebPart
· Override the RenderContents method
· Signing and Building the Project.
· Copy the ASCX Web User Control to your /UserControls/ directory (or your selected directory)
· Copy the compiled DLL into the Global Assembly Cache (GAC)
· Discover the publicKeyToken property of our assembly using .Net reflector
· Add the appropriate SafeControl entries for each of our classes in SharePoint's Web.Config file
· Add an assembly element to the assemblies section of SharePoint's Web.Config file
· Create a SmartParticles.WebPart XML file with necessary information for deployment to SharePoint
· Upload the SmartParticles.WebPart XML file to SharePoint's WebPart gallery
