„#Describe the advantages Exchange 2000 receives from Internet information services IIS.. „#Exchange 2000 Internet Information Services Point out another major change from Exchange 5.5:
Trang 2Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended
to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property
2000 Microsoft Corporation All rights reserved
Microsoft, MS-DOS, MS, Windows, Windows NT, Active Directory directory service, ActiveX, BackOffice, FrontPage, Hotmail, MSN, Outlook, PowerPoint, SQL Server, Visual Studios, and Win32, are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries
The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted
Other product and company names mentioned herein may be the trademarks of their respective owners
Project Lead: David Phillips
Instructional Designers: Lance Morrison (Wasser), Janet Sheperdigian, Steve Thues
Lead Program Manager: Mark Adcock
Program Manager: Lyle Curry, Scott Hay, Janice Howd, Steve Schwartz (Implement.Com), Bill Wade (Wadeware LLC)
Graphic Artist: Kimberly Jackson, Andrea Heuston (Artitudes Layout and Design)
Editing Manager: Lynette Skinner
Editor: Elizabeth Reese (Write Stuff)
Copy Editor: Ed Casper (S&T Consulting), Carolyn Emory (S&T Consulting), Patricia Neff
(S&T Consulting), Noelle Robertson (S&T Consulting)
Online Program Manager: Debbi Conger
Online Publications Manager: Arlo Emerson (Aquent Partners)
Online Support: Eric Brandt
Multimedia Developer: Kelly Renner (Entex)
Compact Disc Testing: Data Dimensions, Inc
Production Support: Ed Casper (S&T Consulting)
Manufacturing Manager: Bo Galford
Manufacturing Support: Rick Terek
Lead Product Manager, Development Services:
Lead Product Manager: David Bramble
Group Product Manager: Robert Stewart
Trang 3Information Services, and event support for customizing mail-enabled software
At the end of this module, students will be able to:
„#Explain the architectural changes made from Microsoft Exchange Server 5.5
to Exchange 2000
„#Describe the benefits of the new information store architecture
„#Describe the advantages Exchange 2000 receives from Windows 2000 Active Directory™directory service
„#Describe the advantages Exchange 2000 receives from Internet information services (IIS)
„#Describe the new options developers receive from the event support in Exchange 2000
0DWHULDOV#DQG#3UHSDUDWLRQ#
This section provides you with the materials and preparation needed to teach this module
0DWHULDOV#
To teach this module, you need the following materials:
• Microsoft PowerPoint® file 1569A_04.ppt 3UHSDUDWLRQ#
To prepare for this module, you should:
• Read all the materials for this module
Trang 4LY# # 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH#
0RGXOH#6WUDWHJ\#
Use the following strategy to present this module:
„#Overview of the Exchange 2000 Architecture Present a general overview of the architecture of Exchange 2000
„#Exchange 2000 Information Store Process This section describes the new information store in Exchange 2000 Stress that Exchange 2000 supports multiple stores and that each one is made up of two databases, one for messages in Rich Text Format and one for messages
in their native format
„#Exchange 2000 Internet Information Services Point out another major change from Exchange 5.5: IIS has been pulled into the operating system and manages all client access protocols
„#Exchange 2000 Events Describe the new capability to hook an Exchange event from a program and then modify the message or event If this section does not seem applicable
to the majority of your students, take a higher-level pass through it and let interested students study it on their own Events are not mentioned elsewhere in the course
„#Exchange 2000 Message Flow Use the diagrams in this section to trace the path of messages through Exchange 2000
Trang 5At the end of this module, you will be able to:
„#Explain the architectural changes made from Microsoft Exchange Server 5.5
to Microsoft Exchange 2000
„#Describe the benefits of the new information store architecture
„#Describe the advantages Exchange 2000 receives from Microsoft Windows 2000 Active Directory directory service
„#Describe the advantages Exchange 2000 receives from IIS
„#Describe the new options developers receive from the event support in Exchange 2000
Trang 65# # 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH#
2YHUYLHZ#RI#WKH#([FKDQJH#5333#$UFKLWHFWXUH#
Store.exe
Information Store
Information Store MAPI
ESE
Logs Database
HTTP-Protocol Stubs
The major architectural changes introduced in Exchange 2000 involve switching to Active Directory from the dedicated directory used in previous versions of Exchange, extending the functions of the Extensible Storage Engine (ESE) database, and moving protocol management to the Windows 2000 IIS process
([FKDQJH#5333#,QWHJUDWLRQ#ZLWK#$FWLYH#'LUHFWRU\#
Unlike previous versions of Exchange Server, Exchange 2000 no longer has a dedicated directory Instead, Exchange 2000 integrates with Windows 2000 Active Directory
Exchange 2000 uses Active Directory to store all directory information This includes:
„#Exchange 2000 configuration (stored in the Active Directory configuration partition)
„#Mailboxes
„#Server and site information
„#Mail recipients (stored in the Active Directory domain partition as Active Directory objects)
Trang 7# 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH# # 6#
,QIRUPDWLRQ#6WRUH#3URFHVV#
The information store in Exchange 2000 is a service that stores data in an ESE database The Exchange 2000 information store includes new features that make access to data easier and faster The information store brings the Web, the file system, and the collaboration server together into a single place for storing information and deploying applications It takes the best features of the information store in previous versions of Exchange Server (transaction logging, single-instance storage, rollback recovery, and online maintenance) and melds them with Web technology to provide customers with more integrated
information management options
Components of the information store include XAPI, which provides X.400 messaging services to previous version of Exchange Public Folder replication, which manages the instances of public folders replicated to the local store MAPI support is also provided by the information store for Outlook and other MAPI clients
,QWHUQHW#,QIRUPDWLRQ#6HUYLFHV#
In Exchange 2000, the client access protocols are part of the IIS process, which has become the protocol engine Incorporating the protocols into the IIS process enables system architects to host Exchange 2000 subsystems (protocol, storage, and directory) on virtual servers on either the same computer or on different computers This makes Exchange 2000 more scalable than previous versions of Exchange
([FKDQJH#,QWHUSURFHVV#&RPPXQLFDWLRQV#/D\HU#
The Exchange Interprocess Communications Layer (EXIPC) provides a queuing layer that enables the IIS and store processes (Inetinfo.exe and Store.exe) to shuttle data back and forth very quickly This is required to achieve the best possible performance between the protocols and database services on an Exchange 2000 server Conventional applications require the processor to switch contexts when transferring data between two processes
Trang 9Information Store
Information Store
%HQHILWV#RI#WKH#1HZ#,QIRUPDWLRQ#6WRUH#$UFKLWHFWXUH#
Support for multiple information stores provides Exchange 2000 with the best
of two worlds: the ability to create very large databases for large-scale enterprises and the option of splitting a single logical database into separate physical databases to increase overall system reliability, enable much faster backup, and speed up the recovery process in the event of hardware failure For example, if the hardware running a part of the overall e-mail database fails, only that database is affected during repair, while the others continue to serve their e-mail users, even though the database is administered as a single unit
By storing messages in their native formats, Exchange 2000 server avoids the overhead required to convert each arriving message into RTF, as it had to do in earlier versions Storing messages in their native formats enables
Exchange 2000 to support non-MAPI clients effectively without sacrificing performance
Trang 109# # 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH#
)HDWXUHV#RI#WKH#,QIRUPDWLRQ#6WRUH#
The information store includes:
„#A database managed as a hierarchical file system of folders and items
„#Support for various types of native Web content
„#Accessibility to all information by using common URLs
„#Consistent access to the information store through Outlook, other e-mail clients, Windows Explorer, and any Internet browser
„#Built-in content indexing and search
„#Several protocols and APIs for remote client access
Trang 11Store Store
Store Store
Store
ESE
In previous versions of Exchange, the number of users a server could host was limited by the time required to back up and restore large databases When an Exchange server database became too large to back up or restore in a reasonable amount of time, another Exchange server was required to share the load
Database size became the bottleneck in the number of users an Exchange server could manage
6XSSRUW#IRU#0XOWLSOH#'DWDEDVHV#
Exchange 2000 overcomes the database size limitations of previous Exchange versions by introducing support for multiple databases and storage groups on the same server Although each instance of a database runs under the same information store process (there can be only one information store process running per server), you can mount or dismount individual databases dynamically This means you can restore an individual database from backup while other database instances service client requests
0XOWLSOH#GDWDEDVHV#RQ#D#VLQJOH#GLVN#
Creating multiple Exchange 2000 databases on a single disk does not protect against catastrophic failure If you have five 10GB databases on a single disk and the disk fails, all five databases will have to be restored However, if one of the five databases becomes corrupt, that single database can be restored while the other databases remain online
0XOWLSOH#GDWDEDVHV#RQ#D#GLVN#DUUD\#
One of the most common fault tolerant solutions is redundant array of independent disks (RAID) 5 By creating multiple databases on a hardware RAID partition, a disk can be replaced while the databases remain online, and a database can be restored while the other databases remain online
The goal of having multiple databases is to allow companies to increase the number of simultaneous users that can be maintained on a
Exchange 2000 is not designed to hold a single mailbox per database This type of deployment would be costly and resource-intensive to maintain
Trang 12;# # 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH#
6WRUDJH#*URXSV#
Exchange 2000 information stores are organized in storage groups A storage
group is a set of databases that share the same set of transaction log files and can be managed either as a group or independently by the administrator An administrator can create up to 15 storage groups per Exchange 2000 server Each storage group can host up to six information stores
There can actually be up to 16 storage groups per Exchange 2000 server However, one storage group is reserved for system use
'HSOR\PHQW#6FHQDULRV#IRU#0XOWLSOH#'DWDEDVHV#
You need to consider many performance and resource implications when deciding how to configure multiple databases on a computer running Exchange 2000 Before you decide on the disk layout for your server, consider the reasons and benefits for configuring more than one database
0XOWLSOH#&RPSDQ\#6FHQDULR#
When you need to host multiple companies on the same computer running Exchange 2000, you can use a different collection of databases for each one You can then configure each database with different policies, such as storage and retention limits In addition, you can back up and restore each database independently
6XSSRUW#IRU#9,3#0DLOER[#6FHQDULR#
Although the information store is not designed for a single mailbox per database, you can host a limited number of smaller databases without incurring heavy resource costs This enables those users who require short restore times
to be grouped together in a limited user database designed to be quickly restorable
6HUYLFH#/HYHO#$JUHHPHQW#6FHQDULR#
It is common for medium and large companies to have service level agreements (SLA), which define reasonable downtime The SLA usually commits a company to have services restored within a certain amount of time Of course, this varies from company to company and depends on how critical a company views messaging information
You need to consider what database configuration scenario will yield the highest availability for users in your company and at what cost Calculating the maximum time it would take to perform a disaster recovery with your hardware and software will help to determine the conditions of the SLA
It is important to define what corporate data is stored in Exchange 2000 Through the Exchange Installable File System, it is possible to host file shares
on Exchange 2000 You will need to define under what SLA these shares fall
1RWH#
1RWH#
Trang 13Heade r
Heade r Header & Body
Internet Message Stream
Previous versions of Exchange only stored messages in message database encapsulated format (MDBEF) This is the native format for Outlook clients When a non-MAPI client requested a message, the information store had to convert the contents from MDBEF to the appropriate format based on what the client requested This conversion consumed processor bandwidth and slowed server performance To reduce this overhead, the information store in Exchange 2000 is split into the following two types of storage files:
„#Native content store (.stm file) When Exchange 2000 receives a message
from a client other than Outlook (MAPI), Exchange stores the message in its native format, either Multipurpose Internet Mail Extensions (MIME) or non-MIME format, in the native content storage file If an Outlook client tries to read data from the native content store, Exchange 2000 converts the data from MIME content into MAPI content and passes it back to the Outlook client
„#Rich-text store (.edb file) Messages from MAPI clients such as Outlook are
stored in the rich-text store, as they were in previous versions of Exchange Server MAPI clients can then access these messages without conversion However, if an Internet protocol-based client attempts to read a rich-text message, then the message is converted to the requested format
Trang 1443# # 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH#
2Q0'HPDQG#&RQWHQW#&RQYHUVLRQ#LQ#([FKDQJH#5333#
Exchange 2000 does not perform content conversion until a client requests a message from the native store that is in a format it cannot read—this is known
as on-demand content conversion For example, when a client receives a
message through an Internet protocol, Exchange 2000 sends the data to the native content store When another Internet protocol-based client attempts to read the data, it streams directly out of the native content store without ever being converted
On-demand content conversion occurs when a client tries to read a message from a data store not native to the client For example, when an Outlook client reads a message that is stored in the native content store, the message is converted and passed to the Outlook client The message is not moved from the native content store to the rich-text store, and the conversion is done very quickly in memory
The message will be copied between stores if a client that is reading the message makes a change For example, if an Outlook client opens a message that is stored in the native content store, makes a change, and then saves the message, the saved message will be written to the rich-text store instead of back
to the native store
1DWLYH#&RQWHQW#6WRUDJH#'DWDEDVH#)RUPDW#
The native content store is an ESE database Just like the rich-text store, it uses
4 KB pages and is capable of allocating data between non-contiguous areas Additionally, like the rich-text store, the native content store defragments and compacts the data it contains
6L]H#RI#WKH#'DWDEDVH#
The information store size is a combination of both the rich-text store and the native content store size, along with the associated transaction logs Backup products use the backup API to call the data out of the database so you will not see two separate files
During a database restoration, both storage files must be restored, as there are some properties that are shared between the two databases
Trang 15Information Store
Exchange 2000
SMB
The information store is a repository for all types of data, not just e-mail messages One method of storing data in Exchange is to post it through the Exchange clients, such as Outlook 2000 This is the traditional method of placing data in public folders and private folders, but it does not offer much interoperability with applications such as Microsoft Office
([FKDQJH#,QVWDOODEOH#)LOH#6\VWHP#2YHUYLHZ#
Another method for users and applications to access data stored in Exchange 2000 is through the Exchange Installable File System The Exchange Installable File System (IFS) exposes folder and item objects to normal network client redirectors as a file share The benefit of this is that you can connect to any public folder, or even your own mailbox, just as if it were any other network resource Because your local computer can assign a drive letter to these resources, standard applications, such as Windows Explorer and Office 2000, can read and write data directly to the native content store
7KH#0%;#)ROGHU#
Although the MBX folder is the root for all mailboxes on the server, the folder (mailbox) names are invisible Win32® clients that have been granted the appropriate access permissions can still access the mailbox folders by using explicit folder names that equate to mailbox alias names
You can also access all objects in the Inbox from the Command Prompt with standard DOS commands
Trang 17Store.exe Information Store
Information Store
MAPI
EXIPC Protocol Stubs
(6(
Logs Database
Large public e-mail systems, such as HotMail®, are built by separating components on to different servers Separating the components increases the reliability for any size organization by isolating system failures in one server from other components hosted on other servers For example, a set of protocol servers can be hosted on servers without redundant array of independent disks (RAID) controllers to reduce cost and prevent protocol failures from affecting the information store or Active Directory Because Exchange 2000 does not require that directory services be hosted on each computer, you have more flexibility in how you deploy Exchange Server
3URWRFRO#6XSSRUW#LQ#([FKDQJH#5333#
Exchange 2000 supports several client protocols, including Post Office Protocol version 3 (POP3), Internet Message Access Protocol version 4 (IMAP4), Simple Mail Transfer Protocol (SMTP), Network News Transfer Protocol (NNTP), and Web Distributed Authoring and Versioning (Web-DAV)
Exchange 2000 installs and manages the POP3 and IMAP4 client access protocols, but uses the SMTP and NNTP protocol stacks provided by Windows 2000
Trang 1847# # 0RGXOH#7=#([FKDQJH#5333#$UFKLWHFWXUH#
When you install Exchange 2000 it extends (not replaces) the SMTP and NNTP protocol stacks in Windows 2000 with additional command verbs and advanced routing components to provide all of the functionality required by an enterprise-class messaging and collaboration system The following paragraphs briefly describe the Exchange 2000 Internet protocol stacks
„#POP3 The most basic message retrieval protocol is POP3 POP3 is only
capable of accessing the user’s inbox folder Exchange 2000 supports POP3 for access by POP3 clients
„#IMAP4 Another message retrieval protocol, IMAP4, is used for accessing
mailbox information IMAP4 is more advanced than POP3 because it supports basic online capabilities and access to folders other than the Inbox
In addition to providing access to user mailboxes, the Exchange 2000
implementation of IMAP4 provides:
• The ability to access public folders
• The ability to grant delegate access to another user’s mailbox
• The ability for the administrator to allow anonymous access to specific
IMAP account names
„#SMTP Exchange 2000 uses SMTP as its primary messaging protocol
SMTP is used to move messages between servers in the same routing group, and is the preferred protocol for moving messages between routing groups The enhancements made by Exchange 2000 to the Windows 2000 SMTP stack include:
• Commands that support fault-tolerant routing
• An advanced queuing engine
• An enhanced message categorization agent
The X.400 message transfer agent (MTA) is used to connect to foreign X.400 messaging systems rather than native message transfer between computers running Exchange 2000
„#NNTP The Exchange 2000 implementation of NNTP includes the following
added functionality to NNTP:
• Content indexing to provide search functionality to public folders
• The ability to accept a full newsfeed regardless of the choice of storage,
file system or public folder on the back-end
• MAPI or NNTP clients can read or post to newsgroups supported by the
information store
„#Web-DAV Web-DAV is an extension to the Hypertext Transfer Protocol
(HTTP) that provides a Web interface to the Exchange 2000 information
store
1RWH#