Wednesday, 26 June 2013

Sharepoint -Choose the Role you want to be!

                                                    Sharepoint Roles and Responsibility
The Roles are
  • SharePoint Administrator
  • SharePoint Developer
  • SharePoint Designer
  • SharePoint Architect

  • SharePoint Administrator
    The role of SharePoint administrator includes setting up the SharePoint infrastructure with servers and services; SharePoint 2007/2010, Exchange Server, Active Directory, Windows 2003 and 2008 Servers, SQL Server 2005/2008, IIS 6.0 and 7.0, network infrastructure, ISA server, etc. He is responsible for maintaining and optimizing the SharePoint farm.
    A SharePoint administrator requires knowledge of both SQL Server and Windows Server. Since SharePoint stores all of its data in SQL Server databases, DBA knowledge is critical. However, the Windows Server knowledge required to build and maintain a SharePoint farm is considerable. The administrator role is often split between two people who work closely together: a Windows Server administrator and a SQL Server DBA.The DBA skills required are the standard set required for any SQL Server but the features of Windows Server that a SharePoint Administrator needs to have some knowledge of include:
    • Good knowledge in IIS and the architecture of it
    • Windows Server Manager
    • Active Directory (LDAP,ADLDS,ADAM etc)
    • DNS and SMTP
    • Network Load Balancing (NLB)
    • Firewall (Hardware and software NLB)
    • Event Viewer and Performance Monitor
    • PowerShell scripting will be added advantage if looking in SharePoint 2010

    But I suggest some knowledge of SharePoint development experience will add extra benefits to this role.

    SharePoint Developer

    The main role of a developer is developing custom web parts and component for SharePoint. They should have experience in,, web parts, master pages, Ajax developer, detailed knowledge of the SharePoint 2007 object model / 2010 client object model, JavaScript experience etc. A SharePoint developer should be well versed on .NET frame work and windows workflow foundations (WFF). The Developer should have a solid understanding of C# and or and a solid understanding of the SharePoint API as a whole. Building workflows from a completely custom Visual studio direction as well as custom coding SQL and SQL server manipulation and maintenance also required so some knowledge in DB side also needed. XML/XSLT knowledge will also provide some extra value in development. Since most things in SharePoint are xml based or can be converted and fed as xml/xsl, these are just another set of skills are another way that the developer can increase their value. A solid understanding of IIS and editing web config files are needed for a developer.
    However, the main thing is to understand the out-of-the-box functionality and SharePoint web services well enough so that you don't program something SharePoint has Out of the box. SharePoint development involves tuning functionality that SharePoint has out of the box. So we should explain how to achieve project requirements with the least amount of programming.

    SharePoint Designer

    There are some wiles that a SharePoint Designer is really needed for the SharePoint project. But as per my experience it is good to have a Designer in your team so the developers can focus on programming no need to waste their time on customization. Designers are responsible for all the "non-programming" customization of the SharePoint solution. Good understanding of SharePoint and the different out of the box web parts and their functionality are needed for this role. Experience with html, style sheet, caml, xml, xslt, java script, SharePoint Designer 2007/2010 and InfoPath 2007/2010 are the main areas they have to focus.

    SharePoint Architect

    A SharePoint Architect needs to have a thorough understanding of SharePoint (admin, developing, functions) including when and how new components/web parts should be developed. Also Microsoft Technologies in general, especially .NET 3.5, C#, Exchange, Active Directory, Office 2007/2010, IIS and infrastructure in general. Pivotal specialized role is of SharePoint architect. This is the person who can:
    1. Collect, transform, validate and map functional and non-functional requirements
    2. Plan and architect infrastructure integration
    3. Define solution
    4. Map MOST of solution requirements to existing configurable features of SharePoint
    5. Architect and POC custom code as needed.
    The Architect also needs to set up the projects environments. In some cases this can be a full blown Development, Staging and Production environment. If that is the case it's very important to have all the environments match as close as possible if not be exact. The Architect also needs to understand fail over's, clustering and load balancing, for large farms. A SharePoint Architect also needs a solid understanding of alternate access mapping in MOSS, host headers, DNS entries, Kerberos configuration and multiple forms of authentication (forms auth, ntml etc).

    Saturday, 22 June 2013

    Sharpoint Catalogue-Training

    Sharepoint Catalogue

    Below is the list of the sharepoint community or training material which will help a novice,beginner ,intermediate and an expert to enhance Sharepoint knowledge-

    This site is a social network that has been built to serve the wider needs of the SharePoint community. Think of it as a LinkedIn or Facebook that's purely focused on SharePoint and is moderated by a group of folks that know SharePoint very well. By becoming a member you can take part in forums, chat, blogs, lists, events and competitions
    -Below is the few screenshots from the site

    3. is a leading provider of on-demand SharePoint Training (Individual and Corporate) and SharePoint Consulting. End Users, Administrators and Developers learn SharePoint skills and best practices from our online subscription service, DVD video tutorial packages, corporate packages for multiple users, and remote consulting.

    Below is the few screenshots from the site

    4. is an online portal which gives you complete set of tutorial on following topics: SharePoint , ASP.Net , Java , Java Script , HTML and other programming languages. Readers of this website can also find Sharepoint/MOSS learning material here -> Sharepoint Learning. All the articles in this site will be given by pesonal experience, from a website or e-books.

    Below is the few screenshots from the site

    Below is the few screenshots from the site


    Sharepoint Architecture


    The SharePoint platform is a flexible, n-tier service-oriented architecture (SOA). It can be scaled down to operate entirely from one machine, or scaled up to be managed across hundreds of machines.


    A SharePoint farm is a logical grouping of SharePoint servers that share common resources.A farm will typically operate stand-alone, but it can also subscribe to functionality from another farm, or provide functionality to another farm. Each farm has its own central configuration database, which is managed through either a PowerShell interface, or a Central Administration website (which relies partially on PowerShell's infrastructure). Each server in the farm is able to directly interface with the central configuration database. Servers use this to configure services (e.g. IIS, windows features, database connections) to match the requirements of the farm, and to report server health issues, resource allocation issues, etc.

    Web applications

    Web Applications (WAs) are top-level containers for content in a SharePoint farm, and are typically the interface through which a user interacts with SharePoint. A web application is associated with a set of access mappings or URLs which are defined in the SharePoint central management console, then automatically replicated into the IIS configuration of every server configured in the farm. WAs are typically independent of each other, have their own application pools, and can be restarted independently in Internet Information Services.

    Site collections

    A site collection is used to provide a grouping of 'SharePoint Sites'. Each web application will typically have at least one site collection. Site collections may be associated with their own content databases, or they may share a content database with other site collections in the same web application.

    Service applications

    Service Applications (SAs) provide granular pieces of SharePoint functionality to other web and service applications in the farm. Examples of service applications include the User Profile Sync service, and the Search Indexing service. An SA can be turned off, exist on one server, or be load-balanced across many servers in a farm. SAs are designed to be as independent as possible, so that — depending on the SA — restarting an SA, experiencing an SA failure, or misconfiguring an SA may not necessarily prevent the farm from operating. Each SA enabled on the farm typically has its own process that requires a certain amount of RAM to operate, and typically also has its own configuration database and Active Directory (AD) service account. SharePoint Server and SharePoint Enterprise include all the SharePoint Foundation SAs, as well as additional SAs.

    Administration and security

    The modular nature of SharePoint's architecture enables a secure 'least-privileges' execution permission best practice.
    SharePoint Central Administration (the CA) is a web application that typically exists on a single server in the farm, however it is also able to be deployed for redundancy to multiple servers.This application provides a complete centralized management interface for web & service applications in the SharePoint farm, including AD account management for web & service applications. In the event of the failure of the CA, Windows PowerShell is typically used on the CA server to reconfigure the farm.
    The structure of the SharePoint platform enables multiple WAs to exist on a single farm. In a shared (cloud) hosting environment, owners of these WAs may require their own management console. The SharePoint 'Tenant Administration' (TA) is an optional web application used by web application owners to manage how their web application interacts with the shared resources in the farm.