Messaging Server Example

The following figure shows a basic logical architecture for a deployment of Messaging Server. This logical architecture shows only the logically distinct components required for Messaging Server. Later figures illustrate the relationships among these components.

---

Note –

Typically, a deployment of Messaging Server is part of an enterprise solution that includes other Java Enterprise System components, as illustrated in Identity-Based Communications Example.

---

Figure 4–4 Logical Architecture for Messaging Server Deployment

The following table describes the components depicted in Messaging Server Example.

Table 4–5 Components in Messaging Server Logical Architecture

Component	Description
Email clients	Client applications for reading and sending email.
Messaging Server MTA	Messaging Server configured as a message transfer agent (MTA) to receive, route, transport, and deliver email messages.
Messaging Server MMP	Messaging Server configured as a message multiplexor (MMP) to route connections to appropriate message stores for retrieval and storage. MMP accesses Directory Server to look up directory information to determine the proper message store.
Messaging Server STR	Messaging Server configured as a message store for retrieval and storage of email messages.
Directory Server	Provides access to LDAP directory data.

The logical architecture does not specify replication of services for the Messaging Server components. For example, enterprise deployments typically create separate inbound and outbound MTA instances but Messaging Server Example shows only one MTA component. The replication of logical components into multiple instances is a design decision that you make during the deployment design phase.

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.

Use 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.

   

Use 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.

   

Use 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.