16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

458 Part VI: Administration of <strong>Microsoft</strong> Office SharePoint Portal Server 2003<br />

always default to the same server as the configuration database server <strong>and</strong> cannot<br />

be changed here. This database name will end with _PROF. Using the same<br />

example as before, the database would be named Woodgrov1_PROF.<br />

■ Global E-Mail Server. Even though this is not a database server, it appears in<br />

this section <strong>and</strong> should be configured for the farm. The farm can operate without<br />

having an e-mail server defined; however, the alert feature will not function.<br />

The alert feature allows users to subscribe to lists <strong>and</strong> documents <strong>and</strong> be<br />

alerted via e-mail when those lists or documents change. The configuration<br />

page allows you to set the SMTP e-mail server name or IP address (which can<br />

be <strong>Microsoft</strong> Exchange, the IIS SMTP service, or any third-party SMTP server<br />

that accepts Anonymous connections) that the alerts should show the change<br />

notification as coming from <strong>and</strong> to whom replies will be sent, as well as the<br />

character set used for the e-mails. Keep in mind that this is a global setting for<br />

the farm. If a certain server needs to be pointed to a different e-mail server<br />

(such as for a portal server residing outside of a firewall), that server can have<br />

its e-mail server setting changed on its Windows SharePoint Services Central<br />

Administration page.<br />

■ Single Sign-On Credentials. If you are wondering about Single Sign-On<br />

credentials, they too do not have anything to do with databases <strong>and</strong> are configured<br />

with an optional setting used in highly customized portal site implementations.<br />

Single Sign-On allows you to store <strong>and</strong> map an application’s<br />

account credentials to user account credentials. This prevents users from having<br />

to sign on again when portal-based applications retrieve information from<br />

business applications, such as third-party enterprise resource planning <strong>and</strong><br />

customer relations management (CRM) systems.<br />

By using Single Sign-On, you can centralize information from multiple backend<br />

applications through a single portal site that uses application definitions. By<br />

using application definitions, you can minimize <strong>and</strong> automate the sign-on process to<br />

these applications in a more secure environment. In addition, SharePoint Portal<br />

Server 2003 provides an easy interface for developers to create <strong>and</strong> extend this<br />

feature.<br />

Component Assignments<br />

The Component Assignments area lists all servers that have been assigned some role<br />

in the server farm. Servers that are assigned as database servers or e-mail servers will<br />

not have a hyperlink, while servers that play one of the following key component<br />

roles will have a hyperlink: Web, Search, Index, <strong>and</strong> Job. This makes sense because<br />

the hyperlink leads to the SharePoint Central Administration pages as serviced by the<br />

virtual server on that server, which of course requires SharePoint Portal Server 2003<br />

to be installed on that server.<br />

To assign or change the component roles that the listed servers will play, click<br />

the Change Components button at the bottom of the page. This can be useful if, for

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!