How to build a Sharepoint Silverlight Beta 2 Webtart?
If anyone is in need of the above topic pls add your comments.
Configure the primary Shared Services Provider
Create the Shared Services Provider
1. On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.
2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
3. On the Manage this Farm's Shared Services page, click New SSP.
Note: If you have not created a Web application for the SSP administration site, you need to create one before you create the SSP. If you have already created a Web application for the SSP administration site, skip to step 14.
4. On the New Shared Services Provider page, click Create a new Web application.
5. On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site , and do not modify the default settings in this section.
6. In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify the default settings in the remainder of this section.
Note : By default, the authentication provider is set to NTLM. Use the Negotiate (Kerberos) setting only if Kerberos is supported in your environment. This option will require configuring a Service Principal Name for the domain user account, for which you must have Domain Administrator credentials. For more information about configuring Kerberos, see Microsoft Knowledge Base article KB 832769: HOW TO: Configure Windows SharePoint Services to Use Kerberos Authentication (http://support.microsoft.com/?kbid=832769).
7. In the Load Balanced URL section, do not modify the default settings.
8. In the Application Pool section, click Create new application pool.
9. In Application pool name, enter the name of your application pool or use the default name.
10. Click Configurable, and in User name and Password, type the user name and password for the user account that you want to act as the application pool identity for your SSP Web application.
The user account must be a domain user account, but the user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Microsoft Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
11. In the Database Name and Authentication section, verify the database information and make sure that Windows Authentication (recommended) is selected.
12. In the Search Server section, do not modify the default settings.
13. Click OK.
Upon successful creation of the Web application, the New Shared Services Provider page appears.
14. In the SSP Name section, in Web Application , select the Web application that you created for the SSP, and do not modify any of the default settings in this section.
15. In the My Site Location section, do not modify any of the default settings.
16. In the SSP Service Credentials section, in User name and Password, type the user name and password for the user account under which you want the SSP to run.
The user account must be a domain user account, but the user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
17. In the SSP Database section, you can either accept the default settings (recommended), or specify your own settings for the database server, the database name, or the SQL authentication credentials.
18. In the Search Database section, you can either accept the default settings (recommended), or specify your own settings for the search database server, the database name, or the SQL Server authentication credentials.
19. In the Index Server section, in Index Server , click the server on which you configured the Search service.
If there is no index server listed in the Index Server section, then no server in your farm has been assigned the index server role. To assign the index server role to a server in your farm, follow the instructions in the "Configure the Search service" section earlier in this topic.
20. In the SSL for Web Services section, click No.
21. Click OK .
Upon successful creation of the SSP, the Success page appears.
22. On the Success page, click OK to return to the Manage this Farm's Core Services page.
For information about how to perform this procedure using the Stsadm command-line tool, see Shared Services Provider: Stsadm operations (Office SharePoint Server).
Create a new SSP
Note : To configure an SSP, you must have already configured an index server for the farm. Without an index server, creation of a new SSP will fail. For more information about configuring an index server, see the topic Chapter overview: Configure the primary Shared Services Provider.
To create and configure a new SSP:
1. In a Web browser, open the Central Administration page for your farm.
2. On the top navigation bar, click Application Management.
3. On the Application Management page, under Office SharePoint Server Shared Services, click Create or configure this farm's shared services.
4. On the Manage this Farm's Shared Services page, on the top navigation bar, click New SSP.
5. In the SSP Name section, specify a unique, descriptive name for this SSP. This name will be used to identify the SSP in administration pages.
6. In the My Site location section, select the Web application for this SSP.
7. In the SSP Service Credentials section, specify the credentials which will be used by SSP Web services for inter-server communication and for the SSP timer service to run jobs.
8. In the SSP Database section, specify the database server and database name for storing session data. Use of the default database server and database name is recommended for most cases.
9. In the Index Server section, select the index server which will crawl content in all Web applications associated with this SSP. You may also specify the path on the index server where the indexes will be located if you do not want to use the default path.
10. In the SSL for Web Services section, choose whether or not to use SSL to protect communications to and from Web services.
Note: If you choose to enable SSL for Web services, you must add the certificate on each server in the farm by using the IIS administration tool. Until this is done, the Web services will not be available.
11. Click OK to create the SSP.
Associate an SSP with a Web application
A Web application may be associated with only one SSP, but each SSP may be associated with multiple Web applications.
To associate an SSP with a Web application:
1. On the taskbar, click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
2. In the Quick Launch, click Shared Services Administration.
3. On the Manage this Farm's Shared Services page, on the top navigation bar, click Change Associations.
Note : In the SSP Name column in the SSP list, you will see all the Web applications with which each SSP is currently associated.
4. On the Change Association between Web Applications and SSPs page, under Shared Services Provider, select the SSP you want to configure.
5. In the Web applications section, select the Web applications you want to associate with the SSP.
6. Click OK to associate the SSP with the selected Web applications.
MOSS 2007 can be installed as a Stand-alone Server application or as a Server farm or as a Web Front End. MOSS 2007 installs WSS v3.0 automatically.
If you have only one server, you have no option but to install Stand-alone Type, this will install desktop database engine (SQL Server 2005 Express Edition) along. It will be an independent instance of SQL Server just for the SharePoint application. But this will result in very poor performance. And can only be used by a very small user group or just for learning purpose.
If you have to use it in a relatively larger setup you must install SharePoint farm (atleast one Complete - Install all components Server Type) with database on a different dedicated database server.
In this post I will show the steps for installing MOSS 2007 SharePoint farm:
Prerequisites: Please read this before installing Beta 2
Step 1: Start the installation by clicking the Setup.exe in the x86/x64(for 64 bit machine), and the installation starts with the following screen. Select the Complete Server Type option and click the Install Now button. This will take few minutes and will install the basic components.
Step 11: Now the Create New Web Application Screen will open. Fill the appropriate values. By default it will show some Port number but since I wanted to host the application on 80 port I changed it to 80. Also there please remember the following
Create the site collection and that's it.
You can create multiple Web-Applications(at different Port) and multiple Site-Collections in every Web-Application
Working With the Data View Web Part
What is the Data View?
Data View Web Part is the primary component used for data presentation when building data-driven Web sites using FrontPage 2003 and Windows SharePoint Services. When you create a data-driven Web site, you select data sources from a Data Source Catalog and use Data View Web Parts to present data. Data View Web Parts render data by using Extensible Stylesheet Language Transformation (XSLT).
FrontPage 2003 has many features for building live, data-driven webs. Central to any data-driven Web page is the ability to collect and present live customer data on the fly on a page – that is, you are effectively building a page based on data (hence the term data-driven). These features fall into two categories:
· Sites based on ASP or ASP.NET: using the Database Results Wizard and the Database Interface Wizard. You can create Web pages that display interactive views of desktop-based or server-based data by using ASP code or ASP.NET controls.
· Sites based on Windows SharePoint Services: using the Data Source Catalog and Data View Task panes. You can access a wide range of data sources, including desktop-based and server-based databases, XML files, Web services, and SharePoint Services-based lists.
In this document, we focus on the second set of features.
When working with a Windows SharePoint Services-based site, FrontPage 2003 allows live views of customer data from a variety of different sources:
· SharePoint Services-based Lists and Libraries
· OLEDB data sources, including Microsoft SQL Server
· XML Web Services
· XML FilesThe key technology enabling this versatile data access is the data retrieval service, which is a new data binding mechanism in Windows SharePoint Services. A data retrieval service enables data consumers and data sources to communicate with each other through Simple Object Access Protocol (SOAP) and XML. In essence, it is an XML Web service that returns XML data from different data sources or manipulates data against those data sources. A data retrieval service is installed and runs on a server running Microsoft Windows SharePoint Services. Windows SharePoint Services includes a default set of data retrieval services for working with data in SharePoint Services-based lists, OLEDB, and XML data sources.
The Data View Web Part is a special Web Part which acts as a client to the data retrieval service as it can retrieve and manipulate data from any data source supported by data retrieval services. As we mentioned before, the data retrieval service is a Web service, thus, it returns data in the form of XML. The Data View uses Extensible Stylesheet Language Transformations (XSLT) on this XML to format the data.
A key feature of the Data View is that it provides WYSIWYG authoring of XSLT to produce formatted views of data. The visual editor produces XSLT; the XSL transformation code is inserted directly into the HTML of your page. Once inserted on your page, you can use any WYSIWYG formatting tools from within the Data View in FrontPage 2003, such as adding table columns with certain font formatting, and FrontPage 2003 will generate the new XSLT on the fly. You can also change or add to the XSLT in the CODE view of the FP 2003 editor
Because of the data retrieval services architecture, live data is available at authoring time; furthermore, data is available as XML regardless of how it is stored at the data source. Recall that the data retrieval service is an XML Web service.
Data Views can be connected to build rich pages that combine data from multiple sources, and/or provide rich views on top of hierarchical data (such as master-detail).
FrontPage 2003: Overview of Web Parts Framework
FrontPage 2003: Customizing Web Parts
FrontPage 2003: Working with Web Part Libraries
FrontPage 2003: Connecting Web Parts
FrontPage 2003: Working with Web Part Pages
FrontPage 2003: An Architectural Introduction to Web Parts and ASP.NET
Other Microsoft Resources
Microsoft FrontPage 2003 Customization Kit Web: http://www.sharepointcustomization.com
Microsoft FrontPage Web site:http://www.microsoft.com/frontpage/default.htm
Microsoft FrontPage Add-in Center: http://www.microsoft.com/frontpage/downloads/addin/default.asp
Microsoft SharePoint Products and Technologies:http://www.microsoft.com/sharepoint/default.asp
SharePoint Products and Technologies Web Component Directory:http://www.microsoft.com/sharepoint/downloads/components/default.asp