| Author |
Message
|
| Pozzo |
 Posted: Fri Nov 12, 2004 7:52 am Post subject: New version of SendMail (IA07) |
 |
|
Novice
Joined: 19 Aug 2004
Posts: 16
|
Hello, I'm trying to install the updated version of IA07 for WBIMBv5. I downloaded the zip file today (Nov 12), but it's contents don't seem to match the pdf on ibm's website (ftp://ftp.software.ibm.com/software/integration/support/supportpacs/individual/ia07.pdf). The documentation in the zip file says version 1.7, while the online documentation says version 1.8 and lists some files that don't appear in the zip file. Am I accessing an earlier version? Here's the link I followed...
http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg24000600&loc=en_US&cs=utf-8&lang=en
Thanks... |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Nov 12, 2004 8:00 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I got the same versions on both of them.
Try again. |
|
| Back to top |
|
|
| Pozzo |
| Posted: Fri Nov 12, 2004 1:12 pm Post subject: |
|
|
Novice
Joined: 19 Aug 2004
Posts: 16
|
Yes, you're right.
I wonder what I was looking at before.
So, the reason I was updating to the new version was that I was having trouble sending attachments. I receive the email just fine, but not with the attachment I was expecting.
After installing version 1.8 of the node, I still have the same problem. Here's the code from my Compute node that feeds into the SendMail node:
| Code: |
SET OutputRoot.XML.Message.To = 'jsfuller77@hotmail.com';
SET OutputRoot.XML.Message.Subject = 'Attachment Email';
SET OutputRoot.XML.Message.Body = 'See attached file.';
SET OutputRoot.XML.Message.EncodingBase64.(XML.Attribute)ContentType = 'text/plain';
SET OutputRoot.XML.Message.EncodingBase64.(XML.Attribute)Name = 'attachment.txt';
SET OutputRoot.BLOB.BLOB = InputRoot.BLOB.BLOB;
|
I've also tried:
| Code: |
SET OutputRoot.XML.Message.To = 'jsfuller77@hotmail.com';
SET OutputRoot.XML.Message.Subject = 'Attachment Email';
SET OutputRoot.XML.Message.Body = 'See attached file.';
SET OutputRoot.XML.Message.EncodingBase64.(XML.Attribute)ContentType = 'application/octet-stream';
SET OutputRoot.XML.Message.EncodingBase64.(XML.Attribute)Name = 'attachment.txt';
SET OutputRoot.XML.Message.EncodingBase64.(XML.CDataSection) = Cast(InputRoot.BLOB.BLOB as CHAR);
|
I get the email with subject and body correct, but no attachment. What's wrong? |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Nov 24, 2004 4:11 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
When I did this quite a while ago I had to make sure the fields were in the correct order otherwise the attachment was ignored. Here is the end of my 'costruct email' esql
| Code: |
/* Explicitly copy across the attachment since setting the MailBody to NULL initially means these fields
* are out of order therefore the Sendmail node ignores the attachment. */
IF ("OutputRoot"."MRM"."MailBase64" IS NOT NULL) THEN
-- Declare the dynamic reference
DECLARE AttachRef REFERENCE TO "OutputRoot"."MRM"."MailBase64";
-- Move the dynamic reference to the next item in the array
DETACH AttachRef;
ATTACH AttachRef TO "OutputRoot"."MRM"."MailBody" AS NEXTSIBLING;
END IF; |
Note I was using the MRM and then a RCD node to convert to generic XML but still the field name is different. Is the one you are using valid for the version of the node you have?
HTH,
Vicky |
|
| Back to top |
|
|
| Pozzo |
| Posted: Wed Nov 24, 2004 7:09 am Post subject: |
|
|
Novice
Joined: 19 Aug 2004
Posts: 16
|
Thanks for the reply.
I'm using version 1.8, so the field names are based on the documentation included in that version. I wasn't using a RCD node because the documentation says "The data input for the base64 encoding must be provided in InputRoot.BLOB.BLOB" So I was just setting the XML fields as above and passing the BLOB along. The elements are in the order that the node is expecting, according to the documentation.
After reading your post I tried it with a RCD and got the same result...email but no attachment.
Same or similar problems have gone unanswered here, here and here. Seems like a tough nut to crack! |
|
| Back to top |
|
|
| rkford11 |
| Posted: Wed Nov 24, 2004 9:48 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| Pozzo wrote: |
Thanks for the reply.
I'm using version 1.8, so the field names are based on the documentation included in that version. I wasn't using a RCD node because the documentation says "The data input for the base64 encoding must be provided in InputRoot.BLOB.BLOB" So I was just setting the XML fields as above and passing the BLOB along. The elements are in the order that the node is expecting, according to the documentation.
After reading your post I tried it with a RCD and got the same result...email but no attachment.
Same or similar problems have gone unanswered here, here and here. Seems like a tough nut to crack! |
I have the same problem pozzo. Able to receive email but not attachment .
you are correct, seems like a tough nut to crack
Thanks |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Nov 24, 2004 12:20 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| Sorry, my point was that the fields need to be in the right order. Can you post a sample trace of your message? |
|
| Back to top |
|
|
| Pozzo |
| Posted: Mon Nov 29, 2004 6:38 am Post subject: |
|
|
Novice
Joined: 19 Aug 2004
Posts: 16
|
Here's the message as it appears on the output queue after the email is sent:
<Message><To>josh.fuller@state.mn.us</To><Subject>Email attachment</Subject><Body>See attached file.</Body><EncodingBase64 ContentType="text/plain" Name="attachmt.txt"/></Message>attachment text
The "attachment text" at the end is the BLOB which is supposed to contain the data to be encoded. I can also put this before the XML...
attachment text<Message><To>josh.fuller@state.mn.us</To><Subject>Email attachment</Subject><Body>See attached file.</Body><EncodingBase64 ContentType="text/plain" Name="attachmt.txt"/></Message>
...it makes no difference to the outcome. Like I said, the XML elements are in the order that the documentation specifies. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue Nov 30, 2004 5:23 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Sorry if this is an obvious question, but it your attachment data a CDATA section within the EncodingBase64 tags?
Maybe your examples were just type in wrong, but they show the attachment text outside the top level xml tags which I would expect the node to ignore or abend with. see the examples in IA07.pdf. |
|
| Back to top |
|
|
| Pozzo |
| Posted: Tue Nov 30, 2004 6:18 am Post subject: |
|
|
Novice
Joined: 19 Aug 2004
Posts: 16
|
I've also tried a CDATA section inside the XML and didn't have any luck, but the way I understand it the new version has the capability to encode whatever is in InputRoot.BLOB.BLOB. Page 22 of ia07.pdf:
| Quote: |
Encoding done by the plug-in
<Message>
<From>mqsi@nlrg119</From>
<To>Arjan@nlrg119</To>
<Subject>An e-mail with attachment</Subject>
<Body>See attached file: attachment.xml)</Body>
<EncodingBase64 ContentType="text/plain" Name="attachment.xml"/>
</Message>
The data input for the base64 encoding must be provided in InputRoot.BLOB.BLOB |
It's unclear if it matters whether the BLOB is "before or after" the XML, but I've tried it both ways. |
|
| Back to top |
|
|
|
|
