Tài liệu Module 9: Message Flow in Microsoft Exchange 2000 pdf

Message Mail Flow Architecture IIS SMTP Advanced Queuing Engine Message Categorizer Routing Information Store EXIPC Each component of the message flow architecture performs a specific fu

Contents

Overview 1

Exchange 2000

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, Active Directory, BackOffice, Jscript, NetMeeting, Outlook, Windows, and Windows

NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries

Other product and company names mentioned herein may be the trademarks of their respective owners

Program Manager: Steve Thues

Product Manager: Megan Camp

Instructional Designers: Bill Higgins (Volt Technical), Jennifer Morrison, Priya Santhanam

(NIIT (USA) Inc), Samantha Smith, Alan Smithee

Instructional Software Design Engineers: Scott Serna

Subject Matter Experts: Krista Anders, Megan Camp, Chris Gould (Global Logic Ltd),

Janice Howd, Elizabeth Molony, Steve Schwartz (Implement.Com), Bill Wade (Wadeware LLC)

Technical Contributors: Karim Batthish, Paul Bowden, Kevin Kaufman, Barry Steinglass,

Jeff Wilkes

Graphic Artist: Kimberly Jackson (Independent Contractor)

Editing Manager: Lynette Skinner

Editor: Kelly Baker

Production Manager: Miracle Davis

Build Manager: Julie Challenger

Production Support: Marlene Lambert (Online Training Solutions, Inc)

Test Manager: Eric Myers

Courseware Testing: Robertson Lee (Volt)

Creative Director, Media/Sim Services: David Mahlmann

Web Development Lead: Lisa Pease

CD Build Specialist: Julie Challenger

Localization Manager: Rick Terek

Operations Coordinator: John Williams

Manufacturing Support: Laura King; Kathy Hershey

Lead Product Manager, Release Management: Bo Galford

Lead Product Manager, Messaging: Dave Phillips

Group Manager, Courseware Infrastructure: David Bramble

Group Product Manager, Content Development: Dean Murray

General Manager: Robert Stewart

Instructor Notes

This module provides students with an understanding of the architecture upon which messaging is built, how messages arrive at their destinations when they are sent from various clients, how to work with failed links, and how to track messages After completing this module, students will be able to:

! Describe the mail flow architecture in Exchange 2000, including how messages flow

! Describe how Exchange handles failed links, including how Exchange recovers a link and how Exchange reroutes messages

! Outline how the Message Tracking Center tracks messages, and enable message tracking as well as subject logging

Materials and Preparation

This section provides the materials and preparation tasks that you need to teach this module

Required Materials

To teach this module, you need the following materials:

! Microsoft® PowerPoint® file 1572A_09.ppt

Preparation Tasks

To prepare for this module, you should:

! Read all of the materials for this module

! Complete the labs

! Practice the presentation with the PPT slides, noting the animation slides especially

! Review the multimedia

Presentation:

90 Minutes

Lab:

30 Minutes

Module Strategy

Use the following strategy to present this module:

! Message Flow Architecture This topic focuses on the architecture used to send and receive messages Make sure students understand the difference between intraserver message flow, inbound message flow, and outbound message flow

Much of the material in this section, and several of the following sections, is theoretical because the system performs most of the work It is important that students understand how the system functions to be able to optimize usage

! Working With Failed Links This topic focuses on how Exchange handles failed links, including the factors causing a DOWN link state connector status, the process of restoring links, and rerouting messages

Expect students to want to discuss situations in which messages are blocked because connectors are down It is important to pace this section so that you can address these questions without disrupting the overall flow of the module

! Message Tracking This topic focuses on the details of message tracking Explain what information is available about tracked messages, how to enable message tracking, and how to enable subject logging and display

Customization Information

This section identifies the lab setup requirements for a module and the configuration changes that occur on student computers during the labs This information is provided to assist you in replicating or customizing Microsoft Official Curriculum (MOC) courseware

The lab in this module is also dependent on the classroom configuration that is specified in the Customization Information section at the

end of the Classroom Setup Guide for course 1572A, Implementing and Managing Microsoft Exchange 2000

! Complete the labs for Module 2, “Installing Microsoft Exchange 2000,” in course 1572A, Implementing and Managing Microsoft Exchange 2000

! Install Exchange 2000 at D:\Program Files\Exchsrvr on each server into an organization named Northwind Traders Components installed are Microsoft Exchange Messaging and Collaboration Services, Microsoft Exchange System Management Tools, and Microsoft Exchange Instant Messaging Service Have the students create a custom MMC in the C:\Documents and Settings\All Users\Desktop that is saved as your_firstname Console The MMC contains the Active Directory Users and Computers snap-in and the Exchange System snap-in

! Complete the labs for Module 3, “Administering Microsoft Exchange 2000,” in course 1572A, Implementing and Managing Microsoft Exchange

Important

Setup Requirement 3

The lab in this module requires a second routing group and a routing group connector to be created To prepare student computers to meet this requirement, perform one of the following actions on each server in the organization:

! Complete the labs for Module 8, “Message Routing,” in course 1572A, Implementing and Managing Microsoft Exchange 2000

! For each organization in the classroom, create a routing group named Second Routing Group that contains all member servers of the applicable domain Then, choose a bridgehead server in the second routing group and create a routing group connector between the two routing groups

Lab Results

Performing the lab in this module introduces the following configuration changes:

! All servers are moved to the first routing group

! The routing group connector and second routing group are deleted

! Message tracking and subject logging are enabled for all servers

Overview

! Message Flow Architecture

! Working With Failed Links

! Message Tracking

Several components in Exchange 2000 work with components in Windows

2000 to provide message flow Understanding how these components work together enables you to understand the underlying architecture, how messages flow between their sources and their destinations, how to work with failed links, and how to track messages along their routes

After completing this module, you will be able to:

! Describe the message flow architecture in Exchange 2000

! Describe how Exchange handles failed links, including recovering a link and rerouting messages

! Enable message tracking as well as subject logging, and explain how to use tracking to troubleshoot message delivery

# Message Flow Architecture

! Message Mail Flow Architecture

! Intraserver Message Flow

! Outbound Message Flow

! Inbound Message Flow

There are several components in Exchange 2000 and Windows 2000 that work together to send and receive messages These components run on each server running Exchange 2000 After you understand the underlying architecture, you will be able to describe intraserver, outbound, and inbound message flow

Message Mail Flow Architecture

IIS

SMTP

Advanced Queuing Engine Message Categorizer Routing

Information Store

EXIPC

Each component of the message flow architecture performs a specific function when sending and receiving messages Within Exchange, message flow involves routing, queuing, categorizing, and communication between protocols and the Information Store

EXIPC

The Exchange InterProcess Communication (EXIPC) provides a queuing layer that enables IIS and store processes (Inetinfo.exe and Store.exe) to quickly move data back and forth The ability to move data quickly is required to achieve the best possible performance between the protocols and database services on a server running Exchange 2000

IIS

The client access protocols in Exchange 2000 are part of Internet Information Services (IIS) The IIS process is the protocol engine Incorporating the protocols into IIS enables you to host Exchange 2000 subsystems (protocol, storage, and directory) on virtual servers on either the same computer or on different computers, which makes Exchange 2000 more scalable

Managing incoming and

outgoing message traffic is

important for effective

message handling

Advanced Queuing Engine

The Advanced Queuing Engine defines and manages queues for message delivery, such as domain and link queues that you can query for transport information When the Advanced Queuing Engine receives an SMTP Mailmsg object, it forwards the Mailmsg object to the Message Categorizer, which returns the message destination The Advanced Queuing Engine then queues the Mailmsg object for delivery based on the routing information provided by the routing engine

Message Categorizer

The Message Categorizer is a plug-in to the Advanced Queuing Engine It is a collection of event sinks that perform advanced address resolution on every Mailmsg object that travels through the Advanced Queuing Engine It may also

perform bifurcation for messages with two types of recipients, RTF and MIME Bifurcation creates multiple Mailmsg objects, one for all RTF recipients and the

other for all MIME recipients These messages may be intended for the local information store, a remote host through the message transfer agent (MTA), or

a remote host through SMTP

The Message Categorizer is turned off by default in Windows 2000 Installing Exchange 2000 activates the Message Categorizer

Routing

The routing engine adds link state routing capabilities by providing accurate next hop information to the Advance Queuing Engine The routing engine creates and maintains link state information for the server running Exchange

2000

SMTP

The SMTP service processes incoming traffic from SMTP clients, such as Microsoft Outlook Express, and other SMTP hosts, such as another Exchange server Windows 2000 also uses this transport to perform certain operations, such as directory replication in Active Directory

Delivery Tip

Ask students to explain what

determines whether a

message is handed off to

the local Information Store

driver or the local SMTP

stack

Intraserver Message Flow

IIS

SMTP

Advanced Queuing Engine Message Categorizer Routing

Information Store

EXIPC

1

2 3

6

Exchange Store Driver

MAPI Client

The Information Store receives messages

When users send messages to users on the same server, the Information Store receives the messages and then passes them to IIS IIS processes the messages and returns them to the Information Store

Exchange routes a message sent by a sender on the same server as the recipient through the following steps:

1 A MAPI client, such as Outlook, sends a message to a local recipient The outbound message is first received in the Information Store

2 The MailMsg object is passed to the Advanced Queuing Engine regardless

pre-5 Because the recipient is local, the Message Categorizer then places the message in the local delivery queue

6 The Exchange store driver associates a pointer from the message to the recipient’s mailbox

The MailMsg object is similar to a message header and does not contain the body of the message

Topic Objective

To describe how a message

originating on the same

server flows through the

architecture

Lead-in

When a recipient of a

message is on the same

server as the sender, the

message is delivered

directly

Delivery Tip

Ask students to describe the

purpose of the

pre-categorizer queue

Note

Outbound Message Flow

IIS

SMTP

Advanced Queuing Engine Message Categorizer Routing

Information Store

EXIPC

1

2 3

6

Exchange Store Driver

MAPI Client

The following steps outline the message flow process for outbound SMTP messages:

1 A MAPI client, such as Outlook, sends a message to a remote recipient The outbound message is first received in the Information Store

2 The MailMsg object is passed to the Advanced Queuing Engine regardless

of the recipient

3 In the Advanced Queuing Engine, the Message Categorizer processes the MailMsg object, including bifurcation If the message is addressed to both RTM and MIME recipients, bifurcation will divide the message into multiple identical MailMsg objects, one for each type of recipient

4 The Message Categorizer expands groups when appropriate, checks sender and recipient limits, and sets the appropriate content type for each recipient

that are defined on the Internet Message Formats object under global

settings The MailMsg object is then passed to the appropriate destination domain queue inside the Advanced Queuing Engine

5 The Advanced Queuing Engine passes the destinations for the message to

the routing engine, which returns next-hop identifiers

6 SMTP initiates an SMTP session with the remote SMTP hosts that are identified by the routing engine

7 After an SMTP session has been established with the remote host, the Information Store driver retrieves the body of the message from the Information Store, which converts the message as necessary for each bifurcated message

8 SMTP streams the message from the queue to the remote host

Topic Objective

To describe how an

outbound message flows

through the architecture

Lead-in

An outbound SMTP

message differs from an

instraserver message

For Your Information

Bifurcation is the process of

dividing a message into two

identical messages of

different message formats

Exchange 2000 converts the message to TNEF if destined for another Exchange 2000 server, or MIME if destined for the Internet

Outbound Messages to X.400 Recipients

Exchange routes outbound messages destined for X.400 recipients as local recipients and places them into the MTS-OUT store folder The MTA retrieves the outbound X.400 messages and delivers them to their next hop

Note

Inbound Message Flow

IIS

SMTP

Advanced Queuing Engine Message Categorizer Routing

Information Store

1

SMTP Host Queue

SMTP receives inbound messages for local users and processes them through IIS before they reach the Information Store for delivery

The following steps outline the basic inbound message flow process in an Exchange 2000 Server:

1 An SMTP server/client establishes an SMTP session with the SMTP host

2 The SMTP host streams the message to the Queue directory on the NTFS

file system Once complete, the message is committed, confirming that the

entire message was received

3 The Advanced Queuing Engine then retrieves a portion of the message, the MailMsg object, from NTFS and places it in the pre-categorizer queue

4 In the Advanced Queuing Engine, the Message Categorizer retrieves the MailMsg object from the pre-categorizer queue and processes the message The Message Categorizer also expands groups when appropriate, checking sender and recipient limits, and determining mailbox locations

5 The Message Categorizer then places the MailMsg object in a domain queue inside the Advanced Queuing Engine, or places the MailMsg object in the local delivery queue if the recipient is local

destination-6 The routing engine creates a next-hop identifier for their destination for messages being routed out through SMTP

7 The Information Store retrieves messages intended for local recipients from the local delivery queue

Inbound Messages From X.400 Recipients

Messages sent from X.400 recipients arrive through the Message Transfer Agent (MTA) When an X.400 system sends a message to Exchange 2000, the MTA receives it and places the message in the MTS-IN store folder This folder

is commonly referred to as a hidden mailbox The Information Store then handles the message exactly like all other messages

Ask students to explain what

it means when a message is

committed

# Working With Failed Links

! Determining Link Failure

! Rerouting Messages

! Recovering a Link

After Exchange determines that a link has failed, Exchange reroutes the message and attempts to recover the failed link Understanding the process involved in each of these actions enables you to more effectively track messages and troubleshoot message delivery issues