As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
For various reasons we are using an HTTP post to send data, including an attachment, to our iSM channel. We can see the file is being sent in the message body, as expected, but as the message is a multi-part form request we're struggling with how to properly isolate just the attachment to work with it. Are there any guides on how to do this or anyone who can point us in the right direction? Thanks!This message has been edited. Last edited by: Tamra,
We will wait to see if anyone responds to your request from the Focal Point Forum members and then determine what action to take. Usually within 3 days if there has been no response we will request that you open a case with IBI at InfoResponse Online Information Builders Techsupport
Thank you for participating in the Focal Point Forum.
Kindest regards, Tamra Colangelo iWay Focal Point Moderator
WebFOCUS 8x - BI Portal, Developer Studio, App Studio, Excel, PDF, Active Formats and HTML5
Posts: 487 | Location: Toronto | Registered: June 23, 2009
The XDMultiPartForNHTTP preparser is not recognizing the attachments in the POST body. The example in the documentation has the Content-Disposition listed as attachment, but in our POST request it's form-data. We have our XDAttachmentToDocAgent setup and tested using the attachment number, which didn't work as it didn't think the message had an attachment, and we tried using the Content-ID, but our POST request doesn't have a Content-ID so we used the name of the parameter containing the zip file.
Our attachment is being treated as a String and writing the output to a file is an XML file and not as a zip file. We have Keep Message Flat set to true, so why is it converting our zip file into an XML of a large string? Is there something we need to do to get the XDAttachmentToDocAgent to identify the attachment? FYI, there will only ever be one attachment in the request. If the Content-ID is not in the request are we up the creek? We do not have control over the request.
Here's some raw output showing an error during the attachment capture:
I do hope you are nHTTP as your listener type. The preparser "Multi Part For NHTTP" is configured with all its preoprties left as default. The XDAttachmentToDocAgent should be configured for the following properties:
Attachment number: 0 Keep document Flat: true [if XML is your in-line content, use XDToXML later to XMLise] Delete Attachment: true [if not needed any further]
If you are facing problems at multi part stage, then paste the error relevantly.