Wednesday, June 16, 2010

Transport Pipeline 2010

Transport pipeline is a collection of Exchange 2010 server roles, connections, components, and queues that work together to route all messages to the categorizer on a Hub Transport server inside the organization. Messages from outside the organization enter the transport pipeline through a Receive connector on an Edge Transport server and are then routed to a Hub Transport server inside the organization. Messages inside the organization enter the transport pipeline on a Hub Transport server in one of the below ways:

• Through a Receive connector.
• From the Pickup directory or the Replay directory.
• By direct placement in the Submission queue by the store driver.
• Through agent submission

First all messages must be categorized on the HUB before message route and delivered. after categorized every message delivered to the mailbox in the same active directory site, HUB server on which the message was categorized to the recipient in the different active directory site or forest.

Following component is working on transport process:

SMTP Receive:
When messages are received at a Hub Transport server from Edge server , transport rules are applied and, if anti-spam and antivirus agents are configured, these agents provide an additional layer of anti-spam and antivirus protection. SMTP session start with series of the events that work together. After message has passed completely through SMTP receive and is not rejected by receive events and it put in the Submission queue.

Submission
Submission is the process of putting messages into the Submission queue. The categorizer picks up one message at a time for categorization through SMTP submission, Pickup directory, Store drive and by Submission by an agent.

Categorizer
it picks up one message at a time from submission queue. After categorized message is put on the delivery queue. On HUB transport server the categorizer completes recipient resolution, expansion, bifurcation , Routing resolution and Content conversion. After categorized message put in to mailbox delivery queue of the local mailbox by using the store drive. Remote delivery message to the remote recipient through SMTP connector.



There are some key components to Exchange 2010 routing :

Active Directory Sites – Used as a routing boundary for Hub Transport Servers
AD IP Site Links – Define logical routing paths and least cost routes between hub transports in different AD Sites.
Send Connectors – Primary used to route to external SMTP address space.
Routing Groups – Used as a routing boundary for Exchange 2003.
Routing Group Connectors – Define logical routing paths between Exchange 2010 and Exchange 2003.
Microsoft Exchange Transport Service – The Simple Mail Transfer provider for Exchange 2010 for inbound and outbound mail
Microsoft Exchange Active Directory Topology Service – Service responsible for locating and querying the Global Catalog and Domain Controller servers.
Routing Tables – A map of the topology used by the routing component to make routing decisions.
DNS – Exchange 2010 uses both a standard and enhanced DNS client to perform next hop name resolution. Enhanced DNS supports load-balancing for transport server roles.
SMTP – Protocol used for communications between transport server roles
RPC – Remote Procedure Calls are used by hub transport servers to submit mail to Mailbox Server roles within the same active directory site.



The files available for download are:

Exchange2010_HubTransportExtensibility.pdf
Exchange2010_HubTransportRoleArchitecture.pdf
Download here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6eb8c09a-6ea4-442a-9faa-de33265ceb84&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29#filelist

No comments:

Post a Comment