SharePoint anpassen
Artikel
Configuring Sharepoint Portal Server 2003
As a classic example of a multitiered distributed architecture, Microsoft Office SharePoint Portal Server 2003 presents some unique administration requirements. While the administration tools provided with Microsoft Windows SharePoint Services discussed in the previous two chapters serve to configure and manage each server individually, they do not suffice when faced with the multitude of servers that are usually involved in using SharePoint Portal Server 2003. If multiple database servers, Web servers, and other component servers are present in this environment, each will require a single place to go that allows for configuration and management of the individual servers and of the farm as a whole.
The Web-based tool provided with SharePoint Portal Server 2003 is called SharePoint Central Administration. By maintaining a list of all portal sites in the farm, this tool allows the administrator to configure the many services provided by each portal site on a per-portal-site basis. Furthermore, by using the list of all servers in the farm, the administrator is able to quickly navigate to those servers to perform server-level management of the servers’ portal site services. It also allows the administrator to perform ongoing management tasks such as portal site management, which includes site content and security administration, user profile and personal site management, audience creation and management, as well as search and index management.
This chapter will concentrate on showing the portal site configuration tasks an administrator will have to perform both after installation and on an ongoing basis as new servers are added or removed from the farm. This will include the configuration of virtual servers and the subsequent creation of portal sites on those virtual servers.
Managing Sharepoint Portal Server 2003
In this chapter, we first will learn how a portal system administrator can make use of and manage Sharepoints additional features. Starting on the Site Settings page of the portal site, we will look at some differences between portal-level security and team site security and the special considerations that should be made when managing portal-level security. We will also cover the management tasks related to the alert feature. This topic will show how an administrator can help individual users manage their alerts. We will then look at how to change the default look of the portal site to a customized one by assigning custom logos and custom cascading style sheet files. From there, we will see how to manage portal site content with respect to area pages, the Topic Assistant, and audience targeted links. Finally, we will look at how to manage audience recalculation and show how administrators can manage users’ personal sites. For a discussion on searching and indexing, please refer to Chapter 21, “The Architecture of the Gatherer,” and Chapter 22, “Managing External Content in Microsoft Office SharePoint Portal Server 2003.”
Managing External Content in Microsoft Office Sharepoint Portal Server 2003
One requirement for building a robust information management system is to pull together information that is located in disparate data islands. Microsoft Office SharePoint Portal Server 2003 does an outstanding job of helping you pull that information into the portal site without having to actually move it to the portal site’s database.
SharePoint Portal Server accomplishes this through the crawling and indexing features—features that enable us to extract data from external sources of content (called content sources) and then place that extracted data in text files (that cannot be edited) that can be searched with the results displayed in a result set. Therefore, by simply crawling and indexing information, you can greatly expand the usefulness of the portal site in assisting users when they need to find information quickly and easily.
The tools that we’ll discuss in this chapter focus on both administrative and user- oriented subjects. For administrators, we’ll focus on the creation and management of content sources, search scopes, source groups, and index files. We’ll also discuss ways to craft the result set for your end users, including the use of the thesaurus, the noise word file, keywords, and Best Bets.
From an end-user’s perspective, we’ll focus on how queries are executed in the Search Web Part and outline some considerations when training your end users for this activity in the portal site. First, let’s start by differentiating between Basic Search Administration Mode and Advanced Search Administration Mode in the Search Administration pages.
Personalization Services in Sharepoint Products and Technologies
As the body of corporate knowledge on a portal site increases, it becomes increasingly difficult for individuals to find relevant information, and to have it presented in an intuitive way. Content presented on home pages for corporate and divisional portal sites is typically general in focus and forces workers to access multiple pages to view role-specific and user-specific content.
Microsoft Office SharePoint Portal Server 2003 creates a portal site that knows who you are and what information you care about and work with, thus providing a personal context for users. Based on Web Part Pages technology, SharePoint Portal Server delivers customization and personalization that is flexible, secure, and reliable. SharePoint Portal Server provides a rich set of features focused on ensuring that users have easy access to relevant information from a variety of entry points.
Using Microsoft Office Frontpage 2003 to Customize Sharepoint Products and Technologies Sites
Customizing your SharePoint site using Microsoft Office FrontPage 2003 can be done without coding, a degree in Web design, experience with XML or XSLT, or an understanding of database technologies. The WYSIWYG authoring environment combined with dynamic Web templates, auto-updating data views, prebuilt Web Parts, and Web connectors and built-in conditional formatting capabilities streamline the Web design and development process. With FrontPage 2003, site administrators and even end users themselves can rapidly extend and customize their SharePoint sites in hours—rather than days or weeks.
The combination of design and coding tools in FrontPage 2003 provides more control and greater flexibility over the layout of text, tables
Microsoft Outlook 2003 Integration with Sharepoint Products and Technologies
Just as Microsoft SharePoint Products and Technologies has been evolving, so has its level of integration with compatible e-mail and calendar applications such as Microsoft Outlook. For Microsoft Outlook 2000 and Microsoft Outlook 2002, there were two main points of SharePoint integration. The first point of integration was the ability to display a SharePoint Team Services or SharePoint Portal Server site page when the user switched to a particular Outlook folder. The second point of integration was Outlook Web Access Web Parts that displayed data from a user’s Microsoft Exchange mailbox. Microsoft Office Outlook 2003 provides much richer SharePoint integration, including the ability to display a local read-only copy of SharePoint events and contacts lists and the option to create Meeting and Document Workspace sites related to message file attachments and meeting requests.
This chapter discusses the many ways in which Outlook 2003 and SharePoint Products and Technologies work together.
Integrating Exchange Server 2003 with Sharepoint Products and Technologies
Although Microsoft SharePoint Products and Technologies do not require any particular mail server, the tightest integration is available with Microsoft Exchange Server 2003. Web Parts distributed with Microsoft Office SharePoint Portal Server 2003 can display a user’s Inbox folder, Tasks folder, a list of upcoming appointments from the Calendar folder, or the contents of any other mailbox folder. An alternative technique is to use the Page Viewer Web Part to display any Exchange folder using the folder’s Microsoft Office Outlook Web Access URL. Another approach available for Exchange 2003—and Exchange 2000 as well—is the automatic transfer of attachment files from an Exchange public folder into a Microsoft Windows SharePoint Services document library. Exchange content, of course, can also be included in SharePoint Portal Server indexes, as discussed in Chapter 22, “Managing External Content in Microsoft Office SharePoint Portal Server 2003.”
Use Windows Sharepoint Services as a Platform for Building Collaborative Applications
Use Windows Sharepoint Services as a Platform for Building Collaborative Applications Part 2
These articles discuss:
- SharePoint architecture
- Configuration and content databases
- SharePoint integration with IIS 6.0 and ASP.NET
- Site collections and virtual servers
- Administration of WSS and SPS
Customizing Sharepoint Sites and Portals: Part 1
The first of three companion articles. Learn ways you can customize a SharePoint site and an area; manage users, sites, and templates; change the structure of pages in a site; manage user access; and optimize style sheets.
Customizing Sharepoint Sites and Portals: Using Templates and Site Definitions: Part 2
In this article, we provide more details by creating and editing a site using templates and site definitions.
Customizing Sharepoint Sites and Portals: Style Sheet Class Reference Tables: Part 3
Part 3 provides valuable style sheet class reference tables to use as you customize your sites and portals.
Customizing Personal Sites in Sharepoint Portal Server 2003
The personal sites available in Microsoft Office SharePoint Portal Server 2003 are a potentially powerful tool with which users in an organization can define themselves to the larger organization. This paper explores several options for customizing personal sites to get the most out of the My Site features of SharePoint Portal Server 2003.