Sun Java Enterprise System Deployment Planning Guide

Messaging Server Use Cases

Use cases help identify the relationships among the logical components in an architecture. By mapping the interactions between the components according to the use cases, you get a visual picture of component interaction that is helpful in deployment design.

Typically, you analyze each use case to determine the interaction of components prior to deployment design. The following three use cases are typical for Messaging Server and show interactions among the logical components.

ProcedureUse Case 1: User Logs in Successfully to Messaging Server

  1. Email client sends login information to Messaging Server Multiplexor (MMP)

  2. MMP requests verification of user ID and password from Directory Server.

  3. Directory Server returns verification to MMP.

  4. MMP requests message list from Messaging Server Message Store (STR).

  5. STR requests user’s LDAP record from Directory Server.

  6. Directory Server returns user’s LDAP record to STR.

  7. STR returns message list to MMP.

  8. MMP forwards message list to email client.

    Diagram illustrating data flow among Messaging Server components
for Use Case 1.

ProcedureUse Case 2: Logged-In User Reads and Deletes Mail

  1. Email client requests message to read from Messaging Server Multiplexor (MMP).

  2. MMP requests message from Messaging Server Message Store (STR).

  3. STR returns message to MMP.

  4. MMP forward message to email client.

  5. Email client sends deletes message action to MMP.

  6. MMP forwards delete message action to STR.

  7. STR deletes message from database and sends confirmation to MMP.

  8. MMP forwards delete confirmation to email client.

    Diagram illustrating data flow among Messaging Server components
for Use Case 2.

ProcedureUse Case 3: Logged-In User Sends Email Message

  1. Email client sends message composed in client to Messaging Server Message Transfer Agent (MTA).

  2. MTA requests verification of user ID and password from Directory Server.

  3. Directory Server returns verification to MTA.

  4. MTA checks Directory Server for the destination domain for each recipient.

  5. Directory Server returns to MTA the destination domain for each recipient.

  6. MTA forwards message to each recipient.

  7. MTA forwards message to Messaging Server Message Store (STR) to store message in outbox.

  8. MTA sends confirmation to email client.

    Diagram illustrating data flow among Messaging Server components
for Use Case 3.