Installation of Sp

8/2/2019 Installation of Sp

1/38

History of portals

Key Share Point Features1. Understanding Business Scenarios

2. Augmenting Personal Productivity3. Increasing Team Productivity4. Supporting Remote Workers5. Integrating with partners and customers6. Analysis and design consideration7. Documenting the business vision8. Documenting policies and practices9. Allowing external activities10. Managing content

Server Requirements

Prerequisites

SPS Controller

1. Microsoft windows server 2003, Enterprise edition2. Active directory

3. Microsoft Exchange 2003

SPSPortal

1. Microsoft windows server 2003, Enterprise edition(with all update pack)2. Microsoft Office 2003, Including InfoPath and Front page3. Microsoft Visual studio.Net 20034. Microsoft Sql server 2003 (with sql server service pack 4)5. Microsoft Sharepoint Portal server 2003(with service pack)

SPSClient

1. Microsoft Windows XP Professional2. Microsoft office 2003, Including InfoPath and Front page

SharePoint Services


2/38

SharePoint Portal Server

Webcomponents

IndexComponent

SearchComponent

Job Server

Site and Sub sites

Web SitesLists

SharePoint ServicesDocument Repository

W

O

RK

S

PA

C

ES

M

S

O

FF

IC

E


3/38

Custom Web Parts for SharePoint Portal 2007

Developing and Deploying Custom Web Parts for SharePoint Portal 200

Overview and difference with SPS 2003:

Developing Web Part for SharePoint Portal 2007 is different as compared todeveloping for SPS 2003. Web Parts Developed in .Net 1.1 for SPS 2003 used SharePoint.WebPartPages namespace, however the Web Part in ASP.Net 2.found under the System.Web.UI.WebControls.WebParts.

Development of Web Part in VS 2005To Get Started with creating Custom Web Part for MOSS 2007 in Microsoft VisStudio 2005, Open the IDE and create a new C# project, Select Class Library

Project Type. Name It as NewWebPart.


4/38

Add a reference to the System.Web from .Net components into the project. TSystem.Web dll contains the required namespace ofSystem.Web.UI.WebControls.WebParts .

In The Project explorer view rename the Class1.cs with NewWbPart.cs to beconsistent with this example; this will result in renaming the Class name as weWith the help of using keyword include the namespaces as shown in the codexample below. Derive / Extend the NewWebPart Class from the WebPart Clas( System.Web.UI.WebControls.WebParts.WebPart), and add the code as showbelow. The CreateChildren Control is same as in .Net 1.1, that it would create add controls to this Web Part Class,. In this case I have only added aWebControl.Calender Object. The RenderControl Method is an override for theWebPart Base Class and calls the RenderChildren Method, this causes the ChildControls to be rendered on the Particular HtmlTextWriter passed as a parametthe method.

using System;using System.Collections.Generic;


5/38

using System.Text;

using System.Web;using System.Web.UI;

using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;

namespace NewWepPart{

public class NewWebPart : WebPart{

protected override void CreateChildControls()

{Calendar cldr = new Calendar();cldr.Enabled = true;cldr.ShowGridLines = true;cldr.ShowTitle = true;cldr.EnableViewState = true;

cldr.SelectedDate = DateTime.Now;

Controls.Add(cldr); ?

?}

public override void RenderControl(HtmlTextWriter writer){

RenderChildren(writer);}

}}

Build the project and on successful built you are ready to Deploy the Web Partthe Portal Site.


6/38

Deployment of Web Part:In order to deploy a web part to a SharePoint portal 2007 site, we must have URL of the site to which we want our web part needs to be deployed (displayefact). As it is mentioned earlier that the Web Parts developed in .Net 2.0

environment does have a .CAB project , instead an assembly is created on buiproject. Now there are two choices to deploye the assembly to the SharePointdirectory.

Deploy the assembly to the Assembly Folder (GAC) (requires the assembbe stron named).

Put the assembly to the bin folder of the portal directory.

For the sake of simplicity, the later choice is being demonstrated in this exampPutting Assembly in Bin Folder:The MOSS 2007 creates every portal in the inetpub\wwwroot\wss folder. The eway to find the bin folder from these folder hierarchies is to go from inetmgrconsole. Locate the appropriate portal (for which u want to deploy the web padentified with the port number. Right click and have Properties. Under the HDirectory Tab, note the path in Local path text box. Verify if the bin folder en the specified path by opening it in browser. If the folder doesnt exist then cone. Now copy the assembly form the project output folder and paste it in bin of portal.


7/38

However there is another work around for putting the assembly in to the portafolder again ad again each time the Web Part Project is built with changes.

Right click on the project name (NewWebPart) in the VS.Net 2005 IDE and properties. Under the Build page paste the same path copied from inetmgrconsole into the Output Path. As shown in figure below. This will result in theassembly automatically deployed to the bin folder every time the project is bu


8/38

Adding the Safe Control Entry:Even though the assembly is present in the Portals Bin folder, there is anotherequired to make the Control (Web Part) assembly usable on the Portal Pages.the control will need to render on multiple machines in different browsers withmany user accounts as the organizations have. There is a need to declare thecontrol as safe. To do so open the web.config file placed under the portalsdirectory in the VS.Net 2005 IDE.


9/38

Then edit the file in the section of SafeControls, create a new SafeControl entrour assembly as shown below. Save the file and close it.

.

.

.

SafeControls>


10/38

Configuring Portal to use NewWebPartSince now the web part have been written and deployed to the desired portaldirectory. The next task is to use the web part on the Portals Site. The Web P

Deployed to the portal can be placed on any site within that Portal. For conventhis NewWebPart is demonstrated to be placed on the home page of default PoOpen the portal site in the internet explorer; in this case http://oss1 is the URthe default portal, ensuring that the current logged in user has the administratrights on the portal site.

To begin with, the first step is to add the newly deployed web to the Portals wpart gallery, since the portal is using the configuration databases to keep recothe contents of the portal, our newly created web parts information doesnt ex

the database. We need to add the web part to the Web Part Gallery before weuse it.

To do so, the following steps should be followed.

1. Click on the Site Actions button and then select Site Settings.
http://oss1/http://oss1/


11/38

2. On the site settings page under Galleries column click on the Web Part


12/38

3. On the Web Part Gallery Page click on the New button, to add the new part assembly to the gallery.


13/38

4. On the New Web Parts page locate the NewWebPart in the list, check check box on the left and click on the Populate Gallery button the top of the This will result in the Web Part entry creation in the Web Part Gallery list, and t can be used from now on from the gallery. It can be notices easily that the W

Parts developed form the new Frame work of 2.0 have an extension of.webpaafter their names. Whereas in earlier versions, it was a .dwp file. Both the.webpart and .dwp files are the XML definition of the Web Part.


14/38

5. Until this step the web part is ready to be used on the site by selecting itWeb Part Gallery. Click on the Site Actions button on the page and then selecPage, this will modify the appearance of the page to enable the edit view. In tview Web Part Zones are highlighted so that a user can add a web part to the

Click on the Add a Web Part button in the left zone to add the Web Part.


15/38

6. Select the NewWebPart from the web part list . it is found under the Miscsection and then click on?Advanced Web Part gallery and options.


16/38

7. In the?Add Web Part Pane at right , select Home Gallery and then dra

NewWebPart from the pane into the Web Part Zone.


17/38

8. Click on the Exit Edit Mode link on the page and the site will return to thview mode.


18/38


19/38

nstallation

Installing a New Microsoft Office SharePoint Server 2007 Portal: Step-by-Step Instructions

n this post, I'll demonstrate with words and screen shots how to install and geworking a portal using Microsoft Office SharePoint Server 2007. Installing thisproduct is not difficult, but it does require some forethought and planning. Yocan use this post as a reference for getting your version of MOSS 2007 installe

You need to have downloaded the software from Microsoft's site. For informaton how to do that, please go here. Once you have registered and downloadedthe software, you're ready to start.

First, you'll need Windows 2003 Server, fully patched and ready to go. I believ've seen blog postings recently that indicate that you can install MOSS07 on a

Vista server. I'll leave that discussion for other threads and posts.

Once you have the operating system ready to go, you'll want to start by runninthe setup.exe for MOSS 2007. Figure 1 illustrates that after you start thenstallation process, you'll need to enter a valid product identification key codeThis key code can be found on the download site and should have been a part what you did to get the software in the first place.
http://mindsharpblogs.com/bill/archive/2006/06/27/1153.aspxhttp://mindsharpblogs.com/bill/archive/2006/06/27/1153.aspxhttp://www.microsoft.com/office/preview/beta/getthebeta.mspx?showIntro=nhttp://mindsharpblogs.com/bill/archive/2006/06/27/1153.aspxhttp://mindsharpblogs.com/bill/archive/2006/06/27/1153.aspxhttp://www.microsoft.com/office/preview/beta/getthebeta.mspx?showIntro=n


20/38

Figure 1: Product Identification Key Code Input Screen

After entering the product identification key code, click Continue. The nextscreen is the licensing agreement screen. Now, I always recommend that youread the licensing agreement since it is a legal document and you are bound bts' terms. But I also recognize that in the 10+ years I've been in this industry've never seen an agreement that I didn't agree with.............if you get my

drift.


21/38

Figure 2: Licensing Agreement Screen.

Be sure to select the "I accept the terms of this agreement" check box and theclick Continue.

The next screen will give you the chance to select which type of installation yowish to commit. The Basic installation is used for those who:

Need to install everything on a single server

Do not need to grow into a multi-server farm

Need a quick, easy deployment during installation with lead administrativeffort


22/38

The Advanced option is selected by those who wish to install MOSS 2007selecting some of the customizable features. In this illustration, we'll select thAdvanced option and follow that route.

Figure 3: Installation Type Selection Screen

After clicking on the Advanced button, you'll find that the selections default toStandAlone (Figure 4). However, we'll choose Complete. The meaning of thethree options is as follows:

Complete: Enables all of the options for one server to offer the entire ranof MOSS 2007 services and features to the network. You can scale out thdeployment, start and stop services on this server and use a SQL server thost your databases.
http://www.microsoft.com/sqlhttp://www.microsoft.com/sql


23/38

Web Front End: Enables only those options that allows the server to run a web front end server. What this means is that server is merely the entand exit point (or one of them among the other WFE servers) for the farmThe actual servers that users will consume will be hosted on other server

(presumably). This cannot be the first choice of a farm unless you plan oinstalling other servers in the farm to offer the services and features thatusers will want to consume.

Stand-Alone: Similar to complete, this option enables all of the servicesand features for the MOSS 2007 farm, but assumes that there is no SQLserver, so the MSDE engine is installed locally on this server. You cannotscale out this server into a larger MOSS 2007 farm.

Note that in reality, all of the MOSS 2007 binaries are installed in all three

choices. All these choices really do is (pragmatically, not technically) turn onand off the code that is required for the server to fulfill the functions that havebeen assigned to it. Note also that you can select the location where thebinaries should be installed in the File Location tab and then sign up to givefeedback directly to Microsoft if you'd like to do this.

Make your selections, then click Install Now.


24/38

Figure 4: Server Type Selection Screen

During the installation, you'll be presented with a status bar that is illustrated Figure 5.


25/38

Figure 5: Installation Status Screen

After installation has completed, you'll be given the chance to run through theSharePoint Products and Technologies Configuration Wizard (Figure 6). You'lluse this wizard to commit the initial configuration options for your newSharePoint farm.


26/38


27/38

Figure 7: Informational Pop-Up Box

The following set of screens in the SPPT Configuration Wizard are design to heyou setup the farm. In Figure 8, you'll be able to create a new farm or join anexisting farm. Farm membership, at the server level, is determined by whichservers are using the same configuration database in SQL and which servers anot. In my illustration, I want to create a new farm, so I select the "No, I wanto create a new server farm" radio button. If I had wanted to connect to anexisting farm, I would have selected the other radio button.


28/38

Figure 8: Connect to a server farm configuration screen in the SPPTWizard

After making our selection in Figure 8 and then clicking Next, I'm taken to thenext screen illustrated in Figure 9. On this screen, I can enter the followingconfiguration values:

The SQL database server name. I'm not clear if this is the host name ornetbios name, but I suspect this is the host name. However, you don'tneed the FQDN here, but you do need name resolution to this server or SInstance.

The farm configuration database name is needed in the next input box.Note that the screen just asks for a name, but you need to understandyou're entering the most persistent database name for the entire farm - t
http://www.microsoft.com/sqlhttp://www.microsoft.com/sqlhttp://www.microsoft.com/sqlhttp://www.microsoft.com/sql


29/38

farm configuration database name. Be sure this name supports yourdatabase naming convention. You should decide the name of this databain advance of getting to this screen

The database access account will need to be a member of the local admin

group on each SharePoint server along with having db_creator anddb_security permissions in SQL. I would suggest you have an accountsetup just for this purpose in your Active Directory and that you have astrong password associated with this account.

Figure 9: Configuration Database Settings Screen in the SPPT Wizard

n Figure 10, you'll be asked to decide which type of security settings you wantto use for your farm. First, you can specify a pre-selected port number forcentral administration to run on or you can allow the wizard to randomly assig


30/38

port number. As you can see, this instance of the wizard randomly selected17386 as the port number for Central Administration (CA). If you want CA torun on a different port, then select the check box and enter the desired portnumber.

The issue of NTLM vs. Kerberos is one that you may at some point wish toconsider. Do you want the CA application to run using NTLM (NT Lan Managerfor security authentication or Kerberos? If the latter, there are some specialconfigurations you'll need to complete for your Active Directory (AD) beforeKerberos will work. I'm finding that most administrators are happy with NTLMthough those in a larger and more secure implementations are increasingly usKerberos. For purposes of my illustration here, I'm selecting NTLM.

Figure 10: Configure SharePoint Web Application configuration screen SPPT Wizard


31/38

After you click Next, you'll be given a status bar that indicates how theSharePoint configuration is going. Depending on the type of server you'renstalling and the options you're installing, you could have as few as seven tasor as many as eleven. Figure 11 illustrates the progress screen. Note that the

caption below the status bar will inform you about the configuration actions thare being executed during this process.

Figure 11: Configuration status bar screen in the SPPT Wizard

After the configurations have been executed and committed to the SQL Serverdatabase, we finally get to CA where we can further configure our farm. We cstart and stop services (Figure 12) on this server and then create webapplications. In order to have portal, you'll first need to start the OfficeSharePoint Server Search service and then create a Shared Services Provider(SSP). I'll start the search service.


32/38

Figure 12: Services configuration screen in CA

When the search service is started, you're presented with another web page fo

search configuration administration that needs to be completed before thesearch service can start. The configuration options are pretty clear. Out of thshoot, you'll use this server for both indexing and servicing queries from usersuntil you can get enough servers in your farm to quarantine those options inyour farm. Select a location that has enough disk space for your indexes. Youshould plan on a space allotment of 20% relative to the amount of informationyou wish to index. You'll also need to input an email address, a service accounand whether or not there is a dedicated WFE for all crawling activities. For nown my illustration, since this is the first server in the farm, I'll accept the defau

and click OK.


33/38

Figure 13: Search configuration screen

After starting the search service, the next thing I need to do is create a SSP. order to do this, I'll navigate to the Application tab in CA, click Create or


34/38

Extend a Web Application, then click Create a New Web Application, themake the configurations necessary that you see in Figure 14. Most of this ispretty self-explanatory, so I won't go through each input in detail. Suffice to sthat I've done two things not illustrated here. First, after creating this web

application, I then web back into CA, selected the Create or Configure CoreFarm Services, then selected New SSP (Figure 15) and then filled in theconfiguration information for the new SSP. All of the options on that page areself-explanatory, except that you must select an Index server for the SSP tooperate.

Backtracking just a bit, you can't have an Index server unless the Searchservices is started. So, that's why I illustrated starting the search services firsthen creating an SSP, then creating a portal.


35/38

Figure 14: Configuring the new web application to host the portal


36/38

Figure 15: Illustration of the SSP management interface where you canselect to create a New SSP.

Once the SSP is created and the web application for the portal has been createyou can then create the portal. The way to do this is to navigate to CA and th

click Create Site Collection. Be sure the http://portal is selected in the dropdown list in the upper right-hand portion of the screen (Figure 16). Note thaton this screen, you'll need to ensure that you are creating the site collection atthe root by selecting the "Create Site at this URL" where the URL path is "rootnot in the Sites managed path. Also, if you scroll down, you'll need to select tCorporate Intranet Site under the Publishing tab. Microsoft has renamed the
http://portal/http://portal/


37/38

Portal to Corporate Intranet Site and placed it under the Publishing tab for webcontent publishing purposes. BTW, even though I don't illustrate it here, be suto give the site a title.

Figure 16: Create Site Collection Screen


38/38

At this point, you should now have a new portal, ready to aggregate, organizeand present content for your enterprise, division or department.

Documents

Installation of Sp