Test Topic for Preview only
In this article:
Before you can design your sites based on Windows SharePoint Services 3.0, you need to identify what you want to accomplish. This article helps you identify some primary objectives for your SharePoint sites and consider the environments in which the sites will be used.
Document storage sites or document storage sections of other sites often include the following features:
The ability to check documents in or out, track changes to documents, and keep multiple versions of documents.
The ability to route documents for approval or through specific processes before publishing them to a larger audience.
Windows SharePoint Services 3.0 includes a workflow capability that you can use to create a custom workflow process to route documents for approval.
The ability to tag documents with metadata, so that documents can be more efficiently sorted and managed.
In this procedure, many problems are solved.
Create a new Web application by using Central Administration
On the Create New Web Application page, in the IIS Web Site section, you can configure the settings for your new Web application.
In the Host Header box, type the zoom_boom to set the IIS host header binding. This is an optional field.
In general, this field is not set unless you want to have two or more IIS Web sites using port 80 on the same server, and DNS has been configured to point multiple server names to the same server.
In the Path box, type the path to the home directory on the server. If you are creating a new Web site, this field is populated with a suggested path. If you are using an existing Web site, this field is populated with the current path.
In the Load Balanced URL section, type the URL for the domain name for all sites that users will access in this Web application.
The Zone box is automatically set to Default for a new Web application. To change the zone for a Web application, see 为 Web 应用程序创建区域 (Windows SharePoint Services).
In the Database Name and Authentication section, choose the database server, database name, and authentication method for your new Web application.
Type the name of the database server and Microsoft SQL Server instance you want to use in the format <SERVERNAME\instance>.You can also use the default entry.
Type the name of the database, or use the default entry.
Choose whether to use Windows authentication (recommended) or SQL authentication.
If you want to use Windows authentication, accept the default.
If you want to use SQL authentication, select SQL authentication. In the Account box, type the name of the account you want the Web application to use.
Click OK to create the new Web application, or click Cancel to cancel the process and return to the Application Management page.
Type the following command, and then press ENTER:
stsadm -o deletecontentdb -url <URL name> -databasename <database name>
Consider which of the environments described in the following table are applicable to your sites.
|Type of site||Factors that influence the number of sites or type of sites||Examples|
The size of your organization
The mix of users, and use of hosting
After you integrate the Web service into the SharePoint _vti_bin directory, you must modify the master page to add an ASP.NET AJAX
<ScriptManager> tag. Inside that tag, you define a Services entry point for the custom Web service we are using; in this example, the custom Web service is named
ListData.asmx. Following is the complete tag that is added to the master page.
<asp:ScriptManager runat="server" ID="ScriptManager1"> <Services> <asp:ServiceReference Path="_vti_bin/ListData.asmx" /> </Services> </asp:ScriptManager>
With the Web service configured so that it can be called from the SharePoint _vti_bin directory and the
<ScriptManager> tag added to the master page with a reference to the custom Web service, the ASP.NET AJAX Web service client components can now communicate with it.
The Fiddler capture indicates that the request and response from doing a post back style rendering of the list data sent a total of 79,424 bytes across the network. Alternatively, Figure 7 shows a Fiddler capture when the ASP.NET AJAX-enabled Web Part was used to retrieve the same data via the custom Web service by using XML.
Web Part retrieved same data via custom Web service by using XML