The E-Mail component type wraps the SMTP protocol. It can be invoked synchronously or asynchronously. The configuration allows you to specify either the addresses (From, To, and so forth) from the XML should be dynamically retrieved or sent to a static address.
<xsl:comment>CONTENT_TYPE=text/
html</xsl:comment>, so the transformed HTML has a comment: <!--CONTENT_TYPE=text/html-->
The framework uses this information to set the content_type to text/html, if this comment is not present the content_type is set to text/plain.
The following are the properties of this node:
Property | Description |
---|---|
E-mail Server | Enter the name or IP address of the mail server. |
E-mail Server Listener Port | Enter the port number of the mail server. |
Subject | Enter what you want to appear in the subject line of the e-mail. If you specify XML in the format of xml://<ElementName>/@<AttributeName>, it is replaced dynamically with the value from the input XML data. For example, the text “Thank you for your online Order xml://Order/@OrderNo” is a combination of static and dynamic text that results as “Thank you for your online Order MyOrder005”. |
Body Template | XSL file that contains formatting to apply to the body of the message. Sterling Selling and Fulfillment Foundation supplies the <INSTALL_DIR>/repository/xapi/template/merged/email/orders_mail.xsl file. |
From | Can be static or dynamic with the XML path specified as xml://<ElementName>/@<AttributeName>. Use semi-colons as a delimiter between addresses. |
To | Required. Can be static or dynamic with the XML path specified as xml://<ElementName>/@<AttributeName>. Use semi-colons as a delimiter between addresses. |
CC | Can be static or dynamic with the XML path specified as xml://<ElementName>/@<AttributeName>. Use semi-colons as a delimiter between addresses. |
BCC | Can be static or dynamic with the XML path specified as xml://<ElementName>/@<AttributeName>. Use semi-colons as a delimiter between addresses. |
These are the connection properties of this node:
Connection | Node Connection Rules |
---|---|
Can be the first node after the start node | Only for services invoked synchronously |
Can be placed before |
|
Can be placed after |
|
Passes data unchanged | Yes |
The yfs.smtp.session.reaptime property in the yfs.properties file is used to set the JMS session reaptime. To modify this property, add an entry for it in the <INSTALL_DIR>/properties/customer_overrides.properties file.