EmailNotification business object

Note:
EmailNotification Business Object (InterChange Server Integration Broker Only)

If your integration broker is InterChange Server then a business object named EmailNotification is automatically created by the system to support error notification. When an error occurs, the EmailNotification business object is instantiated by the system and sent to the e-Mail adapter. The adapter extracts the message information from the business object, creates the e-mail message, and sends the message.

The EmailNotification business object contains the attributes listed in Table 10. The only supported verb for this business object is Create.

Table 10. EmailNotification business object attributes

Name Description Required?
RecipientName Message recipient. For more information, see "Specifying valid e-mail addresses". Yes
MessageSubject Description of e-mail content. Value set in business object by collaboration. Yes. If empty, the adapter uses the default value.
MessageContent Content of the e-mail message. Value set in business object by collaboration. Yes. If empty, the adapter uses the default value.
MessageAttachment File to be attached with the message. Optional. If empty, no attachment is sent with the message. To include a file attachment with an e-mail message, set this attribute to the complete filename including the path.
FromAddress Recipient of undelivered messages. Value defined in business object as part of configuration. For more information, see "Specifying valid e-mail addresses". Optional. If empty, no undelivered messages are returned. To have undelivered messages delivered to an administrator, specify the desired e-mail address in this attribute and enable its Required attribute property.
BusinessObjectMimeCharset The character set for business objects contained in the e-mail. For more information about this property, see the description for the identical property at the level of the adapter definition in BusinessObjectMimeCharset. No
BusinessObjectMimeEncoding The encoding for business objects contained in the e-mail. For more information about this property, see the description for the identical property at the level of the adapter definition in BusinessObjectMimeEncoding. No
MessageContentMimeCharset The character set for the message content. For more information about this property, see the description for the identical property at the level of the adapter definition in MessageContentMimeCharset. No
MessageContentMimeEncoding The encoding for the message content. For more information about this property, see the description for the identical property at the level of the adapter definition in MessageContentMimeEncoding. No
MessageHeaderMimeCharset The character set for the message header. For more information about this property, see the description for the identical property at the level of the adapter definition in MessageHeaderMimeCharset. No
MessageHeaderMimeEncoding The encoding for the message header. For more information about this property, see the description for the identical property at the level of the adapter definition in MessageHeaderMimeEncoding. No
Note:
No e-mail is sent if an attachment filename is incorrect, an attachment file does not exist, or an attachment is not readable. If the file resides on another machine, specify the file name using the UNC naming convention. For example, if the file resides on a machine named Ernesto, the path name should be specified as: \\Ernesto\Email\EmailMessage. You can also map a network drive to the machine and specify the file name as F:\Email\EmailMessage.

At runtime, the adapter extracts the attribute values from the business object and inserts the values into an e-mail message as follows:

Copyright IBM Corp. 1997, 2004