Sending an Email Message
Use this procedure to configure sending of emails for file actions.
To send an email message
1. In My webMethods: Administration > Integration > Managed File Transfer > Event Management.
3. Click the tab containing the event for which you are creating the file operation action (Post-Processing Events or Scheduled Events).
4. Select the event in the event list.
5. In the Actions section, click the Select Action list.
6. In the resulting dialog box, click the Select Category list, select Send Email, and then click OK.
7. In Source Filter, type the name of the file whose transfer will trigger this event. By default, ActiveTransfer Server considers all files.
Note:
You can use wildcard characters to filter the file names. For example, enter *.zip to trigger the event only when zip files are uploaded or downloaded. To trigger an event based on a name string in the zip files, use the name string in the Source Filter box, preceded and followed by wildcard characters. For example, enter *invoice*.zip to trigger the event based on the file URLs, when zip files containing the character string invoice in their file names are uploaded or downloaded. If you define a Source Filter for an action, the action acts only on the files that are filtered out.
For information on the use of wildcards in
ActiveTransfer Server, see
Use of Special Characters in Search.
8. If you want to use a regular expression in the source filter, specify a valid regular expression in Source Filter and select Use regular expression.
Examples for regular expressions:
(.(?!purchaseorder))* | Excludes files with the file URL containing purchaseorder |
.*/out/.* | Include files with the file URL containing the folder out |
^a bc(.*)123$ | Includes anything that starts with abc and ends with 123. Matches abc123, abcxyz123, but not abcxyz123def |
NEW-((*.doc)|(*_backup_*)) | Includes anything starting with NEW- that either ends in .doc, or is followed by the string _backup_ |
9. Address the email by entering valid email addresses in the From, To, CC, and BCC boxes.
The value you specify for
From overrides the value specified in the mft.user.email.from parameter for this action. For more information about this parameter, see
Server Configuration Parameters.
10. In the Subject box, enter text to appear in the subject line of the email (for example, Disconnect:?User %user_name%).
The value you specify overrides the value specified in the mft.user.email.subject parameter for this action. For more information about this parameter, see
Server Configuration Parameters.
11. To assist you in completing the body of the email, several examples of common email messages are available. Select the appropriate template from the Variables/Template list.
12. Modify the content in the Body box, or type your own text.
You can use variables in the body of the email. For more information, see
Server Variables
Server Configuration Parameters and
Variables.
13. If you want to execute an error action if the file operation fails, select Execute error action.
14. Click Save.
15. If you selected the Execute error action check box, define an error action as described in
Defining an Error Action. 16. If you are finished defining actions for this event, activate the event as described in
Activating an Event. Result:
Based on the name of files specified in the source filter, the send email action sends emails to the recipients configured in a file action. Transfer of the specified files triggers the send email action.
In single-thread, sequential processing, ActiveTransfer runs the send email action only once for all files of an event, and includes the information for all files in a single, consolidated email. Therefore, each event results in one email. However, if the send email action occurs after parallel processing of files starts in an event, the number of emails ActiveTransfer sends depends on the number of threads in the event. Let us consider the example of an event having three parallel threads for processing. When the event execution completes, ActiveTransfer sends one email for each thread, resulting in a total of three emails for the event.