When using the static e-mail configuration, the e-mail server (Smarthost) that sends the e-mail needs to be defined in the deployment & component diagram, and not by using tagged values in an action node of an activity diagram. The aliasEMailAlias links the physical definition in the deployment view with the logical definition in the activity diagram. In the activity diagram, the alias EMailAlias is defined by specifying the tagged value alias on the SMTP adapter (see action node static content in figure Static E-mail above). The Smarthost is defined in the deployment & component diagram (see figure below).

Figure: Static E-mail Compoment Diagram

Image Removed

The SMTPService artifact SMTPServiceArtifact is stereotyped <<SMTPServiceDeployment>> and has two optional tagged values port (default value 25) and protocol (default value SMTP).
The SMTPAccount artifact SMTPAccountArtifact represents the user's e-mail account on the e-mail server. The alias EMailAlias links it with the service EMailExample, which contains the operation that is assigned the activity diagram including the SMTP adapter.

Figure: Static E-mail Deployment Diagram

Image Removed

In the deployment diagram, the node instance of the e-mail server (in the example above mail.fixnetdata.ch) must be defined as backend. The name of the node instance (mail.fixnetdata.ch) must be a valid SMTP server.